#7142 closed defect (duplicate)
Precondition failed cryptic error
| Reported by: | arun.planemad@… | Owned by: | team |
|---|---|---|---|
| Priority: | major | Component: | Core |
| Version: | latest | Keywords: | precondition failed changeset conflict |
| Cc: |
Description
I got the following error while uploading the last few objects out of a 3000 object changeset while doing some offline mapping in a remote part of India. I have no idea what it means or what can be done.
Uploading to server failed because your dataset violates a precondition. ResponseCode=412, Error Header=<Precondition failed: Way requires the node with id in (XXXX,XXXX...) which either does not exist or are not visible.>
There must atleast be an option to exclude the affected objects from the changeset so that it can be resolved at a ater time or just dropped off completely if it is trivial. I have had such precondition failed messages before and I resolve it with great difficulty by manually editing out such objects from the .osm file by searching for them with specified id#. And because i cannot copy past text from the error dialog box, the task is extremely tedious and frustrating.
I can just imagine the frustration of someone new who has done a lot of mapping and suddenly faced with this error with no further information on how it can be resolved.
Attachments (0)
Change History (8)
comment:1 follow-up: ↓ 6 Changed 18 months ago by NE2
comment:2 Changed 18 months ago by anonymous
(By the way, the easiest way for you to handle this currently is by searching in JOSM (ctrl-F) for id:[number] and then updating with ctrl-alt-U.
comment:3 Changed 18 months ago by arun.planemad@…
Ideally, josm should skip uploading these conflicting objects and continue to upload the rest. It is both intimadting and frustrating that a lot of your edits which took a long time and effort to create cannot be uploaded to the server and is at risk of being lost if i did not have the time or knowledge to know how to resolve these conflicts. I have been frustrated by the conflict manager numerous times in the past and would just trash my edits because i had no idea how to work through the problem.
Conflicts are frustrating and are scary for someone new. If a changeset has conflicts, upload the rest of the non conflicting objects and let the user try to resolve the conflicts later if he wants to. Blocking the upload of 2000 nodes because one node in between has a conflict is ridiculous. Its much more easier for the user to discard that node altogether and manually correct it later.
comment:4 Changed 18 months ago by arun.planemad@…
noting down 8 digit id numbers of 20 objects and finding it one by one in josm is a pain. i cant even copy and paste the id numbers from the error dialog. and on my netbook i need to resize the dialog so that i can even see the message completely. its just silly that i have to put in so much of effort into a task that can easily be automated by a computing machine
comment:5 Changed 18 months ago by arun.planemad@…
- Keywords conflict added
comment:6 in reply to: ↑ 1 Changed 18 months ago by skyper
- Resolution set to duplicate
- Status changed from new to closed
Replying to NE2:
This used to bring up the conflict manager. Something must have changed recently.
It never happened to me.
One reason I stop working offline with JOSM !!!
comment:7 Changed 18 months ago by skyper
Closed as duplicate of #4093.
comment:8 Changed 18 months ago by skyper
@arun.planema
Sorry, I can not add you to the cc: of #4093. You have to do that yourself if wished.



This used to bring up the conflict manager. Something must have changed recently.