Changes with large bounding boxes incorrectly showing no changes (due to a timeout in the underlying information source)

[haukepribnow]

I'm submitting a bug report

Brief Description

Navigating to https://osmcha.org/changesets/124718243/ causes the spinning wheel (indicating a loading process) to spin for an unusually long amount of time and then leads OSMCha to indicate that basically nothing was changed as part of this Changeset even though there actually were changes (as can be checked on https://www.openstreetmap.org/changeset/124718243).

What is the current behaviour, (attach relevant screenshots) ?

• https://osmcha.org/changesets/124718243/ takes quite long to load.
• OSMCha does not report any nodes being created as part of this Changeset under "Other Features"

What is the expected behaviour ?

• OSMCha should report the nodes that had been created as part of the Changeset under "Other Features".
• OSMCha should load the Changeset faster (i.e. similarly quickly like most other ones of this size)

When does this occur ?

Only found Changeset 124718243 as the trigger for this behavior.

How do we replicate the issue ?

1. Navigate to https://www.openstreetmap.org/changeset/124718243
2. Note that Nodes 9944358837-9944358851 all have version 1, i.e. were created as part of this Changeset
3. Navigate to https://osmcha.org/changesets/124718243/
4. Note that it takes an unusually long amount of time until loading has been completed
5. Click "Other Features"
6. Note that OSMCha does not report any nodes being created as part of this Changeset

Please tell us about your environment:

• Google Chrome 104.0.5112.81 (Official Build) (64-bit) (cohort: Stable)
• Windows 11

Other Information / context:

While I'm using Nodes not being listed by OSMCha as an example, please also note that the other OSMCha functions like "Tag Changes" etc. also incorrectly don't show any data.

[mmd-osm]

The issue is caused by a timeout after 180s in the underlying engine providing the data. That in turn is triggered by a fairly large bounding box, a rather frequent issue when people map on a continent or global scale.

However, for testing purposes you can resort to either https://dev.overpass-api.de/changeset-map/#124718243 or https://dev.overpass-api.de/achavi/index.html?relations=true&changeset=124718243

Most of the changes were made in Finland close to a place called Nastola.

[haukepribnow]

Thanks for the information. I've updated the title of this bug report accordingly.

With this new information, there could be a "second best" way to address this problem (in case solving the root cause of the timeout is non-trivial): Showing a proper error message that explains why no data is shown for the respective Changeset.