OSMCha / osmcha-frontend

Frontend for the osmcha-django REST API
https://osmcha.org
ISC License
121 stars 37 forks source link

alert: "Changeset: ######### Map failed." #740

Closed rkiddy closed 2 weeks ago

rkiddy commented 2 months ago

Have not come to osmcha for a while. Clicked on first change in the list. Got an alert. Ouch. :--)

Changeset 153380982

See snap. Screenshot from 2024-06-30 11-33-17

rkiddy commented 2 months ago

And the "Retry" button does not stop the error.

FransS1945 commented 1 month ago

Same issue here. Check this link

https://osmcha.org/changesets/154919969 image

batpad commented 1 month ago

Hmm @willemarcel @sunu - it seems to me like requests to the s3 bucket for real-changesets are failing, for example a changeset from a day ago: https://real-changesets.s3.us-west-2.amazonaws.com/154916228.json

This is causing all changeset queries to fallback to Overpass and making things slow / throwing occasional errors. Or at least, I think that's what's going on?

Can we try and take a look at the real-changesets pipeline and see if we can figure out why either the real changeset JSON is not making it to s3, or .. ?

willemarcel commented 1 month ago

@batpad Our requests to osm servers were blocked yesterday for some hours (#742). That changeset was not ingested in the database, but I'm backfilling it now.

literannn commented 2 weeks ago

I have the same error on ALL changesets since yesterday ^((

tastrax commented 2 weeks ago

Likewise - every changeset errors out for me

image

image

abdullahO2 commented 2 weeks ago

same here: Changeset:155770447 Map failed r.elements is undefined image

martien-176 commented 2 weeks ago

Tried multiple random changesets, all with same error, see screenshot.

error

CAM-Gerlach commented 2 weeks ago

I can also consistently reproduce the issue for the past couple days, tested on many different changesets (mine, custom filters, global, direct links, etc), tested in regular and safe + Incognito mode on both Firefox and Chrome (Windows), logging out and back in again, clearing cache, etc. Additionally, I have not updated my OS, browsers, extensions or settings between when it worked and when it didn't (nor even restarted my machine).

image

Here's the web console output, which appears to be behind the failing calls on the frontend given the direct link to the error message output.

155799022:1 -1

beacon.min.js:1          Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
console.js:35 Changeset:155799022 Map failed: Cannot read properties of undefined (reading '0')
    at https://osmcha.org/static/js/3.27dd8914.chunk.js:2:220118
e.<computed> @ console.js:35

155799022:1 Access to fetch at 'https://rksbsqdel4.execute-api.us-east-1.amazonaws.com/testing?action=names&id=19254040' from origin 'https://osmcha.org' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

rksbsqdel4.execute-api.us-east-1.amazonaws.com/testing?action=names&id=19254040:1          Failed to load resource: net::ERR_FAILED

console.js:35 TypeError: Failed to fetch
    at raven.js:1474:16
    at Rs (whosthat.js:5:10)
    at index.js:290:7
    at a._initFetching (fetch_data_enhancer.js:45:26)
    at y (index.js:160:19)
    at k (index.js:207:14)
    at w (index.js:195:14)
    at o (raven.js:376:21)
e.<computed> @ console.js:35

console.js:35 Changeset:155799022 Map failed: Cannot read properties of undefined (reading '0')
    at https://osmcha.org/static/js/3.27dd8914.chunk.js:2:220118
e.<computed> @ console.js:35
willemarcel commented 2 weeks ago

This issue is now fixed.

CAM-Gerlach commented 2 weeks ago

Can confirm per my testing. Thanks!

NeatNit commented 2 weeks ago

This issue didn't get resolved for me until I did a hard refresh (Ctrl+Shift+R). Is this tolerable? Who knows how many users think OSMCha is still broken..