#1748 closed defect (duplicate)
412 server error for relations is not flagged
Reported by: | Owned by: | framm | |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | Core | Version: | |
Keywords: | Cc: |
Description
When an upload of a relation fails with a 412 error (precondition failed) only for a short time a message is displayed. When the user is away from the computer or is not paying attention this might go unnoticed.
Also the title bar indicates there are no changes to upload. Retrying an upload also gives the message that there are no changes to upload. The data on the server is unchaged (for that relation)
One relation that causes a 412 (for now) is 3665
Using JOSM version 1065
Attachments (0)
Change History (7)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
comment:4 by , 16 years ago
#1766 and #1782 are different.
I did not split ways. I was able to reproduce at the time by:
- Download data containing a part of the relation from OSM
- Open the relation editor.
- Download all incomplete ways
- Exit the relation editor with OK (which marks the relation as modified)
- Attempt upload to server.
On upload a message is displayed in the upload progress dialog for about 5 seconds.
No messagebox is shown (staying on screen) indicating a partial failure of the upload.
The local data is marked as unmodified (no * in title bar, "no changes to upload")
When the user misses the 5 second message they are unaware that their changes have not been stored on the server.
Relation 3665 has been fixed so by someone, so I can't use that for testing anymore.
comment:6 by , 16 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
at least related to #1748 (maybe #1748 should be tagged as duplicate)