Opened 5 years ago
Last modified 5 years ago
#20416 new defect
Download (incomplete) members: Cancel does not work and timeouts while download relation with members works — at Version 3
| Reported by: | skyper | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | template_report cancel download members | Cc: | Don-vip, simon04 |
Description (last modified by )
I have some network issues lately:
What steps will reproduce the problem?
- Have a relation without any members downloaded
- Download members from relation or selection panel context menu
- Download starts but hangs after downloading some objects
- Click on "Cancel"
- Click on "Cancel"
- Click on "Cancel"
- Close download window
- Download some area with download dialog
What is the expected result?
The download is canceled.
What happens instead?
Download is not cancel and the second download is not executed until the first download eventually finishes or time-outs.
Please provide any additional information below. Attach a screenshot if possible.
The same is true for downloading only incomplete members.
On thing I noticed: Downloading the whole relation with members using "Download object" works like a charm. So in the situation of mostly incomplete members, it might be smarter if "Download members" would download the whole relation with members instead of each member on its own.
Relative:URL: ^/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2021-01-21 23:33:21 +0100 (Thu, 21 Jan 2021) Revision:17474 Build-Date:2021-01-22 02:30:49 URL:https://josm.openstreetmap.de/svn/trunk Last errors/warnings: - 02626.639 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 - 02626.646 E: IO Exception - <html>Failed to upload data to or download data from<br>'https://api.openstreetmap.org/api/0.6/nodes?nodes=3984729218,4051554686,4121566639,2047310593,3209094977,4121566626,265486042,265486043,693919829,4121566371,2045088239,265486040,2045088238,265486041,291055957,2047310603,833399228,3226528064,4051554668,2045088244,957280287,3226528065,4102782104,3226528067,833464505,659570246,659570247,3505983713,4060297753,833399222,4102782352,833399216,3505983717,833399218,833399219,4102782100,100091095,7148425780,7148425777,7148425776,7148425778,693541246,4121566594,4102782115,4102782114,3505983698,4102782374,793146984,100162775,4821390926,1506585084,4121566619,4102782138,1506585086,2047134518,951484546,4121566622,4102782142,4031093107,4031093106,4055970038,4121566608,4060244542,1506585075,4102782132,4060244546,4121566442,5842431356,4060244544,1303940603,5842431358,249780135,963078179,100162750,949471454,2426710510,2044432784,1286948350,454411096,4055974028,1926863767,4051554605,7668156766,306424594,4055974032,7668156765,309924651,713313232,693919753,693919754,306424597,1506584987,4121566461,4055974038,1884334089,4102782167,3629187340,2034977044,1776583045,4121566664,2045088129,1624584381,925972313,306424619,963078159,3264033764,1919132169,3226528062,3264033763,2109089241,3264033762,3629187390,3226528063,1286948314,1369370862,4051554575,3629187362,4055173318,1884334117,3209094974,2109089229,1436366108,454411159,1436366101,959510971,434696574,4051554794,2845483322,1436366140,7153666759,1436366138,1436366132,1436366135,2845483318,3629187327,3226527968,4144263092,3209037815,4055177473,7153666770,1776583000,1436366112,1436366115,2034977160,4022384402,1450716843,693541248,4051554730,454411208,1992148578,2232223212,2520305369,2520305370,2047310562,2232223210,4022384423,1448904372,4051554709,1448904374,2520305365,3271533073,2520305366,3271533072,2520305367,1782043335,2520305355,4051554697,4663753996,2047134458,1776582939'<br>due to a problem with transferring data.<br>Details (untranslated): Read timed out</html> - 02629.560 W: java.net.SocketTimeoutException: Read timed out - 02629.561 E: java.net.SocketTimeoutException: Read timed out - 02687.031 W: java.net.SocketTimeoutException: Read timed out - 02687.031 E: java.net.SocketTimeoutException: Read timed out - 02714.858 W: java.net.SocketTimeoutException: Read timed out - 02714.858 E: java.net.SocketTimeoutException: Read timed out - 02714.859 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 - 02714.859 W: Ignoring exception because task was canceled. Exception: org.openstreetmap.josm.io.OsmTransferException: Could not connect to the OSM server. Please check your internet connection.
Change History (3)
follow-up: 2 comment:1 by , 5 years ago
comment:2 by , 5 years ago
Replying to GerdP:
On thing I noticed: Downloading the whole relation with members using "Download object" works like a charm. So in the situation of mostly incomplete members, it might be smarter if "Download members" would download the whole relation with members instead of each member on its own.
Yes, downloading a relation with all members is typically much faster (a single api call), but you wanted it to download the members that are visibile in the editor (#20091) unless I got you wrong?
You got me wrong, I am talking about "Download members" from relation or selection panel context menu. No relation editor involved!.
comment:3 by , 5 years ago
| Description: | modified (diff) |
|---|
Yes, downloading a relation with all members is typically much faster (a single api call), but you wanted it to download the members that are visibile in the editor (#20091) unless I got you wrong?