Repository navigation
Conversation
dumpme 2.0.0 → 2.1.0-dev.1 and koncorde 4.7.0 → 4.8.0-beta.1, which brings boost-geospatial-index 1.5.0-beta.1 and kuzzle-espresso-logic-minimizer 2.3.0-beta.1. All three addons are now N-API ports that ship prebuilt binaries for linux-x64/arm64 (glibc 2.31+) and darwin-x64/arm64 inside their tarballs, so `npm install` compiles none of them and downloads no Node headers; each was proven identical to its previous release by a seeded differential test in its own CI. Pinned exactly while they are prereleases. CI: - check-prebuilt-addons.sh, run in the `build` job after `npm ci`, fails if any of the three was compiled instead of loaded from its prebuild. - The install-packages action goes, with its 16 call sites: it only installed libunwind, which nothing links since node-segfault-handler was dropped (dumpme never linked it). - with-retry.sh stays, for re2's install-time download. Refs #2839 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
feat: native addons from prebuilt binaries, no compiler at install time
koncorde 4.8.0-beta.1 → 4.8.0-beta.2, with boost-geospatial-index 1.5.0-beta.2 (kuzzleio/boost-geospatial-index#29, kuzzleio/koncorde#84). The geospatial index sometimes failed to remove a shape, whose id then kept matching without a subfilter behind it, and Koncorde#test threw "subfilters is not iterable". The notifier awaits that match on every document write (document:create → core:realtime:document:notify → notifyDocuments → _test), so the write request answered with an internal error after the document had been written, and no notification was sent. Reproduced on 2.56.0's koncorde 4.7.0: 2 000 geoDistance subscriptions, half removed, 5 000 documents → 62 throws on Node 22, 460 on Node 24. tests/util/koncordeCompat.test.ts runs that scenario through koncordeTest, the notifier's entry point. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…a status Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
fix: realtime matching no longer throws after geospatial unsubscriptions
|
|
🎉 This PR is included in version 2.57.0-beta.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 2.57.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
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.
Native addons prebuilt, no compiler at install time (#2938, closes #2839), and realtime matching no longer throws after geospatial unsubscriptions (#2939).