Opened 15 years ago
Closed 8 years ago
#4370 closed defect (fixed)
Close open changesets shows stale information
Reported by: | Ldp | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | |
Keywords: | changeset | Cc: |
Description
Open a changeset, upload to it, wait until it's autoclosed (or close from outside the JOSM session). Then go to the Close open changesets menu. It seems to talk to the API to fetch open changesets, but the closed changeset also shows up. Trying to close that pops up the 'already closed' message. Even if you acknowledge that popup, and go to Close open changesets again, that changeset is still shown.
Attachments (0)
Change History (8)
follow-up: 3 comment:1 by , 15 years ago
comment:2 by , 15 years ago
Restarting JOSM, then doing "Close open changesets" gives the correct open changesets, as in the API result above.
comment:3 by , 15 years ago
Replying to Ldp:
The actual result when I run the last URL from Firefox:
The '-' in the output are due to the way Firefox shows XML. They are of course not present in the actual response.
comment:8 by , 8 years ago
Keywords: | changeset added |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Don't know when exactly this bug has been fixed in the past 6 years, but I cannot reproduce it now.
After a long editing session, with lots of changesets, this is what I get:
The actual result when I run the last URL from Firefox:
Attempting to close any of the 7 actually closed changesets results in an error:
Doing "Close open changesets" again gives me the same 9 changesets again. So even the one (3987860) for which I got the error isn't removed.
Creating a layer and a single node, then going to the upload dialog, I see the same 9 changesets in the Changesets tab. If I refresh the open changesets from that tab, there is no change either.