Merge upstream google fork #1
Open
Conversation
This file contains hidden or 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
…branch in this repo
This is not provided by jsdom. It is not clear why the tests didn't fail previously.
This allows a single binary wheel to be used for all Python versions.
Also update Github actions configuration for ngauth_server to use newer action versions.
This allows the macOS arm64 package to be tested.
Bumps [golang.org/x/net](https://github.com/golang/net) from 0.8.0 to 0.17.0. - [Commits](golang/net@v0.8.0...v0.17.0) --- updated-dependencies: - dependency-name: golang.org/x/net dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [google.golang.org/grpc](https://github.com/grpc/grpc-go) from 1.53.0 to 1.56.3. - [Release notes](https://github.com/grpc/grpc-go/releases) - [Commits](grpc/grpc-go@v1.53.0...v1.56.3) --- updated-dependencies: - dependency-name: google.golang.org/grpc dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
…edirect pages Fixes #543, but breaks auth when using the dev server. That limitation will be addressed in a later commit by switching from vite to webpack.
Instead just load data files using regular Node.js `fs` library.
This enables webworkers to perform asynchronous initialization before setting an `onmessage` handler, and avoids potential bundler-dependent issues wih lost messages.
The main advantage of vite is that the dev-server avoids bundling, but this leads to a lot of inconsistency between the dev-server and bundled version. In particular, there did not seem to be any non-hacky way to override the path of the oauth redirect html pages when using the dev-server. Additionally, in practice the webpack dev-server is just as fast once the time spent by the browser loading the non-bundled sources is taken into account.
…the same bounding box (leaves_many)
tsx is no longer used for the build scripts, as a subset of typescript is supported natively by node>=22.18. Lint and typecheck are no longer included in build_tools/cli. These were previously enabled by default, but in most cases it was inconvenient to have these steps slowing down the build. Additionally, the existing integrations did not support tsgo or oxlint.
…rrently displays Loading...) temp fix for layertools not rendering in tool palette
Previously, offsets were not calculated correctly for the zip64 end of central directory locator, leading to an error for files larger than 65557 bytes. See ome/ngff#364 (comment) for details.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
22 participants
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.