Opened 15 years ago
Closed 15 years ago
#3489 closed defect (fixed)
Confusing conflict message
Reported by: | bilbo | Owned by: | team |
---|---|---|---|
Priority: | critical | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | Cc: |
Description
I tried to upload data to dataset I thought was open (I found later that it was automatically closed due to inactivity) and I was present with "Conflict detected" dialog, telling me server have newer version of the stuff I am trying to upload. This is very confusing.
In console I see:
WARNING: Warning: error header "The changeset 2475838 was closed at Sun Sep 13 23:26:17 UTC 2009" did not match expected pattern "Version mismatch: Provided (\d+), server had: (\d+) of (\S+) (\d+)"
I guess the case of changeset getting somehow closed behind JOSM's back should be detected and more appropriate dialog presented to the user instead (like "Changeset is already closed, do you wish to open new one?")
Attachments (1)
Change History (5)
comment:1 by , 15 years ago
Priority: | major → critical |
---|
comment:2 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:3 by , 15 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Seems to be still broken:
PUT http://www.openstreetmap.org/api/0.6/changeset/2500779... Conflict
Error header: The changeset 2500779 was closed at Wed Sep 16 18:56:20 UTC 2009
Sep 16, 2009 9:49:36 PM org.openstreetmap.josm.actions.UploadAction handleUploadConflict
WARNING: Warning: error header "The changeset 2500779 was closed at Wed Sep 16 18:56:20 UTC 2009" did not match expected pattern "The changeset (\d+) was closed at (.*)"
And in the source ... err.... if you change the pattern you have to compile it too :)
See attached patch for fix
comment:4 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
I think very confusing for new users, changing priority.