id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
2429	Unable to upload/download 0.6 data after cancelling upload	avarab@…	avarab@…	"Running [1545] I did the following:

 1. Downloaded an area
 2. Traced a building (added a few nodes & a way)

I then pressed ""Upload"" and specified a commit message.

Since the server was slow at that time the upload dialog just hung there, eventually I pressed cancel on it which didn't close the dialog, after which I closed the dialog (by pressing X in my Window Manager).

This leaves JOSM in a state where I can neither upload or download data.

If I select a download area on the slippy map and press ""OK"" the download dialog closes  immediately and nothing happens.

If I press upload I get the ""Upload changes?"" dialog which shows all the nodes / way I initially tried to upload, but when I press ""Upload changes"" the dialog closes immediately and nothing happens, and tcpflow -i eth0 -c port 80 that the OSM server isn't contacted.

So, at this point I saved the incomplete .osm file (attached) and opened it in JOSM again.

Once JOSM had been restarted it pressing ""Upload"" initially worked as expected, i.e. it displayed the changes AND asked me for a commit message, I then uploaded all these changes:

{{{
172.016.005.015.35923-128.040.058.203.00080: POST /api/0.6/changeset/879225/upload HTTP/1.1
Authorization: Basic XXXXXXXXXXXXXXX
User-Agent: JOSM/1.5 (1545 SVN en) Java/1.6.0_13
Host: www.openstreetmap.org
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
Content-type: application/x-www-form-urlencoded
Content-Length: 1836

<osmChange version=""0.6"" generator=""JOSM"">
<create version=""0.6"" generator=""JOSM"">
  <node id='-1' action='modify' visible='true' changeset='879225' lat='64.16504243242191' lon='-22.022018770479963' />
  <node id='-2' action='modify' visible='true' changeset='879225' lat='64.16497837930153' lon='-22.022019731164363' />
  <node id='-3' action='modify' visible='true' changeset='879225' lat='64.16501522033002' lon='-22.02190444903572' />
  <node id='-4' action='modify' visible='true' changeset='879225' lat='64.1649852991611' lon='-22.02192743326594' />
  <node id='-5' action='modify' visible='true' changeset='879225' lat='64.1649749402301' lon='-22.02198482139045' />
  <node id='-6' action='modify' visible='true' changeset='879225' lat='64.1649852991611' lon='-22.022042209514964' />
  <node id='-7' action='modify' visible='true' changeset='879225' lat='64.16501030781689' lon='-22.022065980454453' />
  <node id='-8' action='modify' visible='true' changeset='879225' lat='64.16503531645012' lon='-22.02204220951496
172.016.005.015.35923-128.040.058.203.00080: 4' />
  <node id='-9' action='modify' visible='true' changeset='879225' lat='64.1650456753586' lon='-22.02198482139045' />
  <node id='-10' action='modify' visible='true' changeset='879225' lat='64.16503531645012' lon='-22.02192743326594' />
  <node id='-11' action='modify' visible='true' changeset='879225' lat='64.16501030781689' lon='-22.021903662326444' />
  <way id='-12' action='modify' visible='true' changeset='879225'>
    <nd ref='-4' />
    <nd ref='-5' />
    <nd ref='-2' />
    <nd ref='-6' />
    <nd ref='-7' />
    <nd ref='-8' />
    <nd ref='-1' />
    <nd ref='-9' />
    <nd ref='-10' />
    <nd ref='-3' />
    <nd ref='-11' />
    <nd ref='-4' />
    <tag k='building' v='yes' />
    <tag k='name' v='Gr..ttuviti' />
    <tag k='man_made' v='lighthouse' />
  </way>
</create>
</osmChange>
}}}

While JOSM is waiting for a '''200 OK''' I try to press Cancel on the upload dialog again, but the Cancel button is unresponsive, it can be pressed but it's like it doesn't have an assigned close handler. Pressing it doesn't do anything.

So I close it again (using X), but JOSM doesn't care and will proceed to close the changeset anyway after getting an OK from the server:

{{{
128.040.058.203.00080-172.016.005.015.35923: HTTP/1.1 200 OK
Server: nginx/0.6.34
Date: Tue, 21 Apr 2009 12:42:34 GMT
Content-Type: text/xml; charset=utf-8
Connection: keep-alive
X-Runtime: 0.42271
ETag: ""7ed7c02ffc6b6f6e5905101cc15ad17b""
Cache-Control: private, max-age=0, must-revalidate
Content-Length: 798

<?xml version=""1.0"" encoding=""UTF-8""?>
<diffResult version=""0.6"" generator=""OpenStreetMap server"">
  <node old_id=""-1"" new_id=""379025368"" new_version=""1""/>
  <node old_id=""-2"" new_id=""379025369"" new_version=""1""/>
  <node old_id=""-3"" new_id=""379025370"" new_version=""1""/>
  <node old_id=""-4"" new_id=""379025371"" new_version=""1""/>
  <node old_id=""-5"" new_id=""379025372"" new_version=""1""/>
  <node old_id=""-6"" new_id=""379025373"" new_version=""1""/>
  <node old_id=""-7"" new_id=""379025374"" new_version=""1""/>
  <node old_id=""-8"" new_id=""379025375"" new_version=""1""/>
  <node old_id=""-9"" new_id=""379025377"" new_version=""1""/>
  <node old_id=""-10"" new_id=""379025378"" new_version=""1""/>
  <node old_id=""-11"" new_id=""379025379"" new_version=""1""/>
  <way old_id=""-12"" new_id=""33327256"" new_version=""1""/>
</diffResult>

172.016.005.015.35924-128.040.058.203.00080: PUT /api/0.6/changeset/879225/close HTTP/1.1
Authorization: Basic XXXXX
User-Agent: JOSM/1.5 (1545 SVN en) Java/1.6.0_13
Host: www.openstreetmap.org
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
Content-Length: 0
}}}

But after the changeset has been closed [http://openstreetmap.org/browse/changeset/879225 and the data has appeared on the server] JOSM displays the ""Uploading.."" dialog (which I manually killed earlier) again. Seemingly waiting for nothing."	defect	closed	critical		Core	latest	fixed		Gubaer