Modify

Opened 10 years ago

Closed 10 years ago

Last modified 9 years ago

#12809 closed defect (wontfix)

After updating JOSM and plugins, a "you have encountered a bug in JOSM" message appears

Reported by: anonymous Owned by: Upliner
Priority: minor Milestone:
Component: Plugin reverter Version:
Keywords: template_report Cc:

Description

What steps will reproduce the problem?

  1. Run JOSM
  2. Attempt to revert http://www.openstreetmap.org/changeset/36549076
  3. See message on screen

What is the expected result?

No "you have encountered a bug in JOSM" message

What happens instead?

"you have encountered a bug in JOSM" message

Please provide any additional information below. Attach a screenshot if possible.

At around about the same time, OSM API map calls were failing.

<SomeoneElse> Odd - API map calls seem to be failing [09:57]
<zere> yup, the replica server fell over. we're trying to fix it [09:59]
<SomeoneElse> Ta. [10:00]
<zere> server should be coming back shortly, apologies for the delay. [10:09]
<osmbot> [osm-chef-public|master|Tom Hughes] Move all load to katla

http://git.osm.org/chef.git/commitdiff/dce9660 [10:16]

<zere> thanks TomH. i think that means we're back now. [10:18]

(the JOSM error occurred between 10:09 and 10:16)

Note - after 10:18 I exited JOSM and restarted it, and the problem did not occur, suggesting it's related to failing API calls only.

URL:http://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2016-04-28 12:48:16 +0200 (Thu, 28 Apr 2016)
Build-Date:2016-04-28 10:51:36
Revision:10161
Relative:URL: ^/trunk

Identification: JOSM/1.5 (10161 en_GB) Windows 7 64-Bit
Memory Usage: 399 MB / 875 MB (154 MB allocated, but free)
Java version: 1.8.0_77-b03, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
Dataset consistency test: No problems found

Plugins:
- continuosDownload (1446070193)
- reverter (32005)
- todo (29154)
- undelete (31895)

Last errors/warnings:
- 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
- E: java.util.concurrent.ExecutionException: org.openstreetmap.josm.io.OsmApiException: ResponseCode=503, Error Body=<<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
- E: java.util.concurrent.ExecutionException: org.openstreetmap.josm.io.OsmApiException: ResponseCode=503, Error Body=<<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
- E: java.util.concurrent.ExecutionException: org.openstreetmap.josm.io.OsmApiException: ResponseCode=503, Error Body=<<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
- E: java.lang.IllegalStateException: Missing merge target of type node with id 1,949,536,818

java.lang.IllegalStateException: Missing merge target of type node with id 1,949,536,818
	at reverter.DataSetCommandMerger.getMergeTarget(DataSetCommandMerger.java:61)
	at reverter.DataSetCommandMerger.mergeNode(DataSetCommandMerger.java:81)
	at reverter.DataSetCommandMerger.merge(DataSetCommandMerger.java:172)
	at reverter.DataSetCommandMerger.<init>(DataSetCommandMerger.java:45)
	at reverter.ChangesetReverter.getCommands(ChangesetReverter.java:344)
	at reverter.RevertChangesetTask.realRun(RevertChangesetTask.java:110)
	at org.openstreetmap.josm.gui.PleaseWaitRunnable.doRealRun(PleaseWaitRunnable.java:93)
	at org.openstreetmap.josm.gui.PleaseWaitRunnable.run(PleaseWaitRunnable.java:161)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)

Attachments (0)

Change History (2)

comment:1 by bastiK, 10 years ago

Resolution: wontfix
Status: newclosed

Thanks for reporting. As you noted, it is probably related to a temporary server problem.

I think to handle all kinds of server failures, is too much to ask as these downtimes shouldn't be very common and the task of reverting a changeset is rather advanced.

comment:2 by mdk, 9 years ago

#12809, #12829, #13981, #13986 and #13987 are failing with same callstack.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Upliner.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.