Merge upstream changes to linc neuroglancer #16
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…er is deleted (google#669) removed disposed method on SharedDisjointUint64Sets to prevent potential "cannot read properties of undefined" errors as garbage collection benefit is likely insignificant
* ome.ts: update with dev2 version from the ngff challenge The current proposal for updating OME-Zarr to support Zarr v3 wraps the NGFF metadata in the Zarr metadata within an "ome" block. This checks for that block and if it exists unwraps the necessary metadata. This format is **not** finalized. see: https://forum.image.sc/t/ome2024-ngff-challenge/97363 * Check zarrVersion rather than ome's definition * Raise exception rather than check version * Also update frontend * Fix formatting * Fix format with prettier --------- Co-authored-by: Norman Rzepka <[email protected]>
This is expected to be faster and also reduces the bundle size.
This was accidentally broken by the change to use `CompressionStream`. Fixes google#679.
CancellationToken was introduced before `AbortSignal` was supported by browsers. This commit also unifies handling of authentication status messages and popup windows. Some features previously supported only for middleauth are now supported for all credential providers: - Display authentication status message in "modal" mode by default - Detecting when authentication popup window is closed - Closing the popup if the user navigates away from the page without completing authentication.
This aligns with native JavaScript class properties and improves compatibility with other transpilers/bundlers, like swc and rspack, like that can have varying behavior when `useDefineForClassFields=false`.
This avoids the possibility of hangs when requesting a chunk via the Python API that is already in a FAILED state.
Previously, the playback toggle button in the position widget dropdown did not correctly toggle the display of the playback controls.
Previously, the position widget did not correctly perform dimension indexing when in single-dimension mode (as used only for the DimensionTool). In particular, it always displayed the position of the first dimension, rather than the dimension actually selected.
Previously, panels that were scrolled out of view were not correctly tracked.
Previously, the position widget displayed "undefined" and other undesirable text until the CoordinateSpace is marked `valid` (i.e. at least one data source loads).
Tool palettes are additional side panels that contain tools added from any number of layers.
This avoids pulling in unnecessary transitive dependencies, and avoids issues the vite dev-server has with transitive CommonJS dependencies.
…nstall The vite examples previously worked only when using a symlinked Neuroglancer (as in the tests used in this repo), but not when the Neuroglancer dependency was installed normally. The vite dev server special-cases symlinked dependencies in a way that made its optimizeDeps step work when Neuroglancer is symlinked in `node_modules` but not otherwise. Additional optimizeDeps options have now been added to the vite example configs to ensure the build works when Neuroglancer is installed as a normal dependency. Fixes google#683
- New datasource URL syntax based on ZEP 8 proposal (zarr-developers/zeps#48) - Support for ZIP archives
oxlint is much faster than eslint, completing in about 0.5 seconds, compared to eslint completing in about 15 seconds. It is still missing some important rules, but critically, it supports "import/no-cycle", which is the one rule that is incompatible with per-file caching. Consequently, eslint can now be run with caching enabled, which greatly improves iteration time.
This fixes issues with Neuroglancer precomputed sources at the root of a kvstore and with ".." relative path components.
In 93a57ab a bug was introduced that prevented default annotation subsources from rendering if they were enabled, then disabled, then enabled again.
Previously, sliceview/frontend.ts reused the same message object for multiple worker RPC calls. When the code was originally written, that was fine (although still not likely to be helpful for performance or readability) because all messages were sent immediately (which involved structurally cloning the object). However, 2cdc1f3 introduced a queue of messages used while waiting for the chunk worker to initialize, which made this message object reuse problematic. Fixes google#701.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.