-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
check_already_uploaded seems not work properly #55
Comments
Also seen this behaviour. Even if the upload finishes and there is some error, throws back an error on line 1020 "error_callback function undefined" or something like that. I don't think that's working properly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I would like to know how mule-uploader handle the file have been uploaded completely when user select the same file again.
I saw the behavior on sample site (http://mule-uploader.com/) is:
NoSuchUpload
,The specified upload does not exist. The upload ID may be invalid, or the upload may have been aborted or completed.
Then I tried to remove the force parameter at my environment to see if it will handle the uploaded file checking, I got errors. The flow as below:
NoSuchUpload
,The specified upload does not exist. The upload ID may be invalid, or the upload may have been aborted or completed.
Uncaught TypeError: Cannot read property 'region' of undefined
line: 759 (it incheck_already_uploaded function
)So, what the purpose of check_already_uploaded? How does it check the file uploaded? is this a issue or just un-support this kind of scenario?
And I got the same exception when uploading timeout, it seems the error_callback not work properly.
Its network har file: https://dl.dropboxusercontent.com/u/52456752/localhost.har
its console log: https://dl.dropboxusercontent.com/u/52456752/check_already_uploaded_error.log
The text was updated successfully, but these errors were encountered: