Changes between Version 3 and Version 14 of Ticket #21570


Ignore:
Timestamp:
2022-03-19T15:22:47+01:00 (4 years ago)
Author:
gaben
Comment:

I tried that in the past. The refresh button does nothing even after a minute or two, unfortunately. Also, the server is available and returns the expected data when occurs, verified multiple times in Postman.

Yeah, the code duplication doesn't help either. I tried debugging the relevant code, but when launched with .jar it never occurred. It has something to do with WebStart. I'm using OAuth.

Updated the possible reproduction steps.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #21570

    • Property Component Core → Core Webstart

  • Ticket #21570 – Description

    v3 v14  
    11==== What steps will reproduce the problem?
     21. Use JOSM JNLP distribution (WebStart)
    231. Make some changes, upload and don't close the changeset
    342. Make changes again
    … …  
    67
    78==== What is the expected result?
    8 The changeset created in 1. step shows up in the upload dialog changeset list, upload to the same changeset possible. The changeset refresh button works.
     9The changeset created in step 2 shows up in the upload dialog changeset list, upload to the same changeset possible. The changeset refresh button works.
    910
    1011==== What happens instead?
    11 The changeset doesn't show up, as if it would be closed. Clicking on the changeset refresh button results in a dialog, saying "No open changesets" or similar.
     12Sometimes the changeset doesn't show up, as if it would be closed. Clicking on the changeset refresh button results in a dialog, saying "No open changesets" or similar.
    1213
    1314==== Please provide any additional information below. Attach a screenshot if possible.
    1415After JOSM restart, the (still open) changesets ''always'' show up.
    15 It's not always reproducible.
    16 Also, it's a long-standing issue.
    17 #19780 may be related.
     16It's a long-standing issue and #19780 may be related.
    1817In Postman, the OSM API returns the expected result in reasonable time.
    1918