Potlatch 3 (on two different Windows 11 machines) is giving the following error:
It was working fine 9 days ago. Both are Windows 11, but one has been updated, and one not, so I don’t think it’s a Windows issue. The amount of data to download is small, so I don’t expect it’s an account issue. Other editors can download similarly sized areas, so it’s not that data cannot be read from the OSM API at all.
Did see mention of an API issue “last night” OpenStreetMap Ops Team: "The #OpenStreetMap.org website and API are curren…" - OSM Town | Mapstodon for OpenStreetMap, which then apparently also affected StreetComplete?
No idea if that was all possibly connected?
More info in ApiClientException - Answer not uploaded · Issue #6626 · streetcomplete/StreetComplete · GitHub
The unclear bit is … while removing cloudflare uncovered these latent bugs in cgimap and SC … and maybe P3*, why did things work before we had to put the API behind cloudflare, that isn’t so far back that you would expect things to degrade so fast.
* for the not software devs … “this never worked” bugs are among the most annoying ones, but still happen all the time.
The cgimap bug at least was only present from August 2024 on onwards but I don’t know about the second part where a deflate response is sent but can’t be decoded but possibly that same change also changed which option it selects when there is no preference expressed?
Hopefully I’ve now disable Potlatch 3 from deflate as well so I’d be interested in knowing if it now works again.
Yes the old code defaulted to a quality of 0 for anything that didn’t specify a quality and then it never chooses deflate (or gzip) unless they have a non-zero quality while the new code defaults to a quality of 1 for things that don’t specify and hence does choose compression.
I’ve not had chance to test an edit, but the download of data via the api works.
Edit: Yes, editing via P3 works.
