Modify ↓
Opened 3 years ago
#21187 new defect
Command Stack deleted after unsuccessful upload and conflict not found in first place
Reported by: | skyper | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | template_report upload selection conflict deleted object parent command stack | Cc: |
Description
What steps will reproduce the problem?
- Delete some nodes outside downloaded area
- Search
type:node modified
with "all objects" enabled - Upload selection
- Get no problem with check on parents of deleted objects
- Start upload in upload dialog
- Conflicts with invisible object reported
What is the expected result?
- Why do I get conflicts only during the actual upload and after creating a changeset but not from the first check for parent objects?
- After the download of additional data the command stack should still have the content of my last edits. Even after a successful upload of any kind the command stack should still have content.
What happens instead?
- No conflicts detected on the first run
- Command Stack is empty
Please provide any additional information below. Attach a screenshot if possible.
Relative:URL: ^/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2021-08-02 02:41:28 +0200 (Mon, 02 Aug 2021) Revision:18114 Build-Date:2021-08-02 01:31:32 URL:https://josm.openstreetmap.de/svn/trunk Last errors/warnings: - 07040.496 E: org.openstreetmap.josm.io.OsmApiException: ResponseCode=412, Error Header=<Precondition failed: Node 807734013 is still used by ways 24402957,110804645.> - 07040.505 E: Object still in use - <html><strong>Failed</strong> to delete <strong>node 807734013</strong>. It is still referred to by ways [24402957, 110804645].<br>Please load the ways, remove the reference to the node, and upload again.<br><br>Click <strong>Prepare conflict resolution</strong> to load them now.<br>If necessary JOSM will create conflicts which you can resolve in the Conflict Resolution Dialog.</html> - 07076.851 W: java.net.SocketTimeoutException: Read timed out - 07076.852 E: java.net.SocketTimeoutException: Read timed out - 07076.853 E: java.util.concurrent.ExecutionException: org.openstreetmap.josm.io.OsmTransferException: Could not connect to the OSM server. Please check your internet connection.. Cause: org.openstreetmap.josm.io.OsmTransferException: Could not connect to the OSM server. Please check your internet connection.. Cause: java.net.SocketTimeoutException: Read timed out - 07076.853 E: org.openstreetmap.josm.io.OsmTransferException: Could not connect to the OSM server. Please check your internet connection.. Cause: java.net.SocketTimeoutException: Read timed out - 07076.853 E: org.openstreetmap.josm.io.OsmTransferException: Could not connect to the OSM server. Please check your internet connection.. Cause: java.net.SocketTimeoutException: Read timed out - 07180.329 E: Error header: Precondition failed: Node 807734013 is still used by ways 24402957,110804645. - 07180.440 E: org.openstreetmap.josm.io.OsmApiException: ResponseCode=412, Error Header=<Precondition failed: Node 807734013 is still used by ways 24402957,110804645.> - 07180.447 E: Object still in use - <html><strong>Failed</strong> to delete <strong>node 807734013</strong>. It is still referred to by ways [24402957, 110804645].<br>Please load the ways, remove the reference to the node, and upload again.<br><br>Click <strong>Prepare conflict resolution</strong> to load them now.<br>If necessary JOSM will create conflicts which you can resolve in the Conflict Resolution Dialog.</html>
Attachments (0)
Note:
See TracTickets
for help on using tickets.