VirtualFlyBrain/geppetto-vfb: v2.2.11.1 — term info and queries built in the client

Le résumé fourni par la source

Term info and queries are now built in the browser too, completing the move off the websocket for read paths. Phases 2 and 3 of VFB2 #502, following the meshes in v2.2.11.0. A term's info is fetched from v3-cached and its model built locally — the server's term-info processor ported to JavaScript — and queries run against v3-cached with the result table assembled client-side (geppetto-client VFBv2.4.3.4, DirectTermInfo and DirectQueries). The two go together: the server cannot run a query against a term it never built. A failed fetch still falls back to the server, and ?direct=0 switches a session back for comparison. Checked against the live v2 server before release: 114 terms returned identical info, and 48 query runs differed only in the image references described below. Fixes found while testing on v2-dev Term info opened on the wrong term when a URL listed several ids — the scene's template was whatever resolved first, a 5-second retry re-selected without checking what had focus, and ids still loading were dropped from i=, so a reload came back without them. Images aligned to the loaded template were wrongly reported as aligned to another one. The opening 3D view framed whichever mesh arrived first, leaving the camera sitting on a single neuron until you pressed Home; it now frames once the template mesh is in. The Layers row menu took the whole app down for any term without geometry. Every slide of a multi-alignment carousel carried the same reference, so clicking the VNC slide loaded the brain one. Compound queries from a URL failed on mismatched headers, and paged results both repeated rows and stopped short of the full count. The error dialog's Report button did nothing. Analytics — query runs and row counts, term load outcomes, startup timings, oversized-mesh and error-report events, so the direct paths and the site's responsiveness can be watched in GA. CI — pull requests now build and test without publishing images, branch names containing a slash no longer break the Docker tag, the dead sync workflow is gone, and this session's regressions are covered by new tests in batches 2, 3 and 4.

Ce résumé expose les affirmations des auteurs. BNTIC ne l’interprète pas comme une validation indépendante des résultats.