-
Notifications
You must be signed in to change notification settings - Fork 9
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
Produce helpful error message on upload timeout failure #65
Comments
I wasn't able to replicate this bug on the live site or my local copy. |
Based on the Heroku logs, and my ability to reproduce only on public connections (like hotel lobbies), it appears to be a timeout issue:
We should make this failure more graceful. @ondrae what was your suggestion from earlier going to be? |
You can upload direct to S3 from the client instead of to Heroku first. There might some way to put it into a separate process too. You can notify the user when the file is uploaded, or just show it on screen when its finished. |
Direct to S3 is probably the way to go here. The feature is called something like Signed POST, and triggers a callback. A smart thing to use, and cuts down on one complete round trip. |
I’ve implemented this before in PHP, can help as needed. |
This seems like an improvement that may be warranted in advance of UC—I can Take this one as you see fit @migurski. On Mon, Jul 14, 2014 at 6:50 PM, migurski [email protected] wrote:
t: @alanjosephwilli |
Good point, I will attempt to implement this. |
On the production open-trails.herokuapp.com (but not locally), the Validator crashes when the the full set of OpenTrails data describing the Ohio system (which is 1.6 MB, with all five files included) is uploaded.
The text was updated successfully, but these errors were encountered: