New demo for changeset upload available

Posted by mmd on 4 July 2018 in English (English)

the changeset upload is known to take quite some time for larger changesets, sometimes resulting in timeouts and unclear overall status. Luckily, JOSM already covers some of those issues via its chunked upload, still there’s always room for improvement.

Test period ended

Thank you for your interest. The test period on a dedicated server has come to an end. There will be a separate announcement once this feature is available again for testing. Thanks everyone for participating in the tests!


(Image by zerebubuth, original source(defunct), mirror)

Comment from MikeN on 7 July 2018 at 19:49

I was able to make a few tests, quite impressive! One error test case I uploaded resulted in a proper error message from JOSM.

Is the test server running cgimap or golang?

Comment from mmd on 9 July 2018 at 18:51

Thanks a lot for taking the time to test different scenarios and providing some feedback here. Much appreciated.

This project started in December 2017 as a complete redesign of the current Rails based implementation with a special focus on backwards compatibility and performance. It leverages mass database operations wherever possible. My main motivation to start this project was probably my dissatisfaction with the current performance.

The idea to move the changeset upload to cgimap is not really new: it was first mentioned in some 2011 EWG chat protocols and later appeared in the GSoC 2017 + 2018 proposals, which unfortunately nobody accepted as a challenge. This project is pretty much independent of any GSoC, though. zerebubuth was helping quite a bit to fit the new implementation into the current cgimap, and getting it technically “ready for deployment”.

PS: Everyone can still help out! The more testers we have, the more potential issues we can discover at an early stage! Thanks to all testers providing feedback so far.

Comment from spiregrain on 24 July 2018 at 22:42

Has this been implemented in Production? I find iD on is not allowing uploads, presenting an error message with raw HTML visible as follows:

Sometimes like this: <!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.01 Transitional//EN” “”> <html> <body> <div style="float:left;"> <h1>Application error</h1> <p>The OpenStreetMap server encountered an unexpected condition that prevented it from fulfilling the request (HTTP 500)</p> <p>Feel free to contact the OpenStreetMap community if your problem persists. Make a note of the exact URL / post data of your request.</p> <p>This may be a problem in our Ruby On Rails code. 500 occurs with exceptions thrown outside of an action (like in Dispatcher setups or broken Ruby code)</p> </div> </body> </html>

and sometimes like this: <!doctype html> <html lang="en"> <head> We're sorry, but something went wrong: Web application could not be started </head> <body> <header> <div class="column"> <h1>We’re sorry, but something went wrong.</h1> <p class="subtitle">The issue has been logged for investigation. Please try again later.</p> </div> </header> <div class="column"> Technical details for the administrator of this website <div id="operator_info"> <div class="left"> <h3>Error ID:</h3> bcafa58d <h3>Details:</h3> <p>Web application could not be started by the Phusion Passenger application server.</p> <p class="bold">Please read the Passenger log file (search for the Error ID) to find the details of the error.</p> <p>You can also get a detailed report to appear directly on this page, but for security reasons it is only provided if Phusion Passenger is run with environment set to development and/or with the friendly error pages option set to on.</p> <p>For more information about configuring environment and friendly error pages, see:</p> <ul> <li>Nginx integration mode</li> <li>Apache integration mode</li> <li>Standalone mode</li> </ul> </div> </div> </div> <footer> <div class="column"> This website is powered by Phusion Passenger®, the smart application server built by Phusion®. </div> </footer> </body> </html>

Comment from mmd on 25 July 2018 at 04:39

No, it’s not in production. You’re getting some Rails issue here, probably due to the server move.

Comment from mmd on 22 September 2018 at 09:09

Testing continues on the OSM Dev server now:

See this link for details.

Login to leave a comment