New node not uploaded before way using new node

[malenki]

What is one supposed to do with this?

PUT ​http://www.openstreetmap.org/api/0.6/changeset/2799279... OK
POST ​http://www.openstreetmap.org/api/0.6/changeset/2799279/upload... Bad Request
Error header: Placeholder node not found for reference -13 in way -12
org.openstreetmap.josm.io.OsmApiException: ResponseCode=400, Error Header=<Placeholder node not found for reference -13 in way -12>

at org.openstreetmap.josm.io.OsmApi.sendRequest(OsmApi.java:562)
at org.openstreetmap.josm.io.OsmApi.sendRequest(OsmApi.java:462)
at org.openstreetmap.josm.io.OsmApi.uploadDiff(OsmApi.java:423)
at org.openstreetmap.josm.io.OsmServerWriter.uploadChangesAsDiffUpload(OsmServerWriter.java:116)
at org.openstreetmap.josm.io.OsmServerWriter.uploadOsm(OsmServerWriter.java:163)
at org.openstreetmap.josm.actions.UploadAction$UploadPrimitivesTask.realRun(UploadAction.java:594)
at org.openstreetmap.josm.gui.PleaseWaitRunnable.doRealRun(PleaseWaitRunnable.java:62)
at org.openstreetmap.josm.gui.PleaseWaitRunnable.run(PleaseWaitRunnable.java:116)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

The "wtf"-subject expresses all one is told to do.
$User will see this message and think: yes, so what now?

JOSM-Version 2255

[Gubaer]

Did you run a normal upload or "upload selection"?

Do you still have the data you tried to upload? Can you post it here?

[malenki]

I tried a "normal" upload.
Sorry, the data I don't have anymore. I can't remember doing anything unusual while editing with Josm. A pity for the big edit I threw away...

For your changing of the tickets subject: if there is a better description of the error, why not putting it into the error message instead of some cryptic windows-like stuff (that is really how I felt)?

Though I still don't get
*what this error really _means_ and
*how it is to be _avoid_ or
*how one can resolve it.

Atm it's just the poor user getting a sign: Here you are! Have fun or don't!

[Gubaer]

For your changing of the tickets subject: if there is a better description of the error,
why not putting it into the error message instead of some cryptic windows-like stuff (that is really how I felt)?

Believe me, nobody is doing this on purpose. Let me explain what my current understanding is:

When the OSM server detects an error situation it aborts the request with an error code and sometimes includes a short explanation in an error header. There isn't an exhaustive specification of these error messages, in general we don't know what error message is sent back to JOSM. By trial and error, when I get to know about a certain error message, because I run into it, because it is documented somewhere by chance or because somebody like you reports it, I try to catch it in the JOSM code and transform it into a more user friendly text (including translation).

Here's how you could help if you care to improve the situation:

• scan the ​ruby code for situation where error messages are generated and replied
• create a documentation on the wiki (either the OSM wiki or the JOSM wiki)

Or find an already existing documentation, this would help too, of course. Perhaps it's available somewhere and I simply don't know about it.

Regarding the error itself: JOSM was uploading a new way (with temporary id -12) which included a node (with temporary id -13). The defect is that the way was uploaded before the node or that the way was uploaded withouth the node, which shouldn't happen. That's why I'd like to see the data. I suppose it's a defect in JOSM and at the momemnt I neither see a way to avoid nor to resolve it.

[malenki]

Thank you for the verbose explanation. Placed it at ​Josm wiki.

btw: If there is a way to collapse the submenus at ​this place it would enhance the outline of this page.

Sorry for deleting the data. At that moment I was fed up with being stuck again and wanted to go on. *promising_betterment*

[stoecker]

Don't link to tickets from documentation pages. These pages should be self-understanding. All texts and relevant information should be included in the help text and written in a non-personal way.

[malenki]

The link is meant as reference. The text itself is imo self-understanding. Unpersonalizing: don't really know how to do that with the c&p-ed text without messing it up.

[Gubaer]

Replying to malenki:

btw: If there is a way to collapse the submenus at ​this place it would enhance the outline of this page.

done

[malenki]

Nice work, thanks!