fix(street-level): a tile fetch every client has left is cancelled, or never started

A client drops the tiles a camera move leaves behind; their fetches no
longer run on or hold the six upstream slots ahead of the tiles in view.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
German KhokhlovandClaude Opus 5.5 committed 2026-10-08 16:44:28 +04:00
1 parent 99264e80d6
commit 777aa62586
4 files changed
+203 -32

No files matched your search

+2 -1
View File
@@ -3048,7 +3048,8 @@ The server proxy (`server/providers/mapillary.js`) adds the token to
coverage-tile requests (the browser holds it too, for MapillaryJS and the Graph
API), serves only z11–14 coverage, refuses upstream redirects, strips the
unused `image` layer, coalesces concurrent requests, runs at most six Mapillary
fetches at once and keeps tiles in a 24 h memory cache.
fetches at once (a fetch every client has left is cancelled, or never started)
and keeps tiles in a 24 h memory cache.
MapillaryJS loads on the first photo. Opening one frames it with a single
camera flight through the application's deferred navigation (`begin` /