Repository navigation
Bump netty-all from 4.1.60.Final to 4.1.67.Final - #10
Merged
Merged
Conversation
Contributor
|
@dependabot rebase |
Bumps [netty-all](https://github.com/netty/netty) from 4.1.60.Final to 4.1.67.Final. - [Release notes](https://github.com/netty/netty/releases) - [Commits](netty/netty@netty-4.1.60.Final...netty-4.1.67.Final) --- updated-dependencies: - dependency-name: io.netty:netty-all dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/maven/io.netty-netty-all-4.1.67.Final
branch
from
August 31, 2021 22:22
c4238e2 to
a78e0d3
Compare
dependabot
Bot
deleted the
dependabot/maven/io.netty-netty-all-4.1.67.Final
branch
September 1, 2021 07:01
mergify Bot
added a commit
that referenced
this pull request
Dec 8, 2025
Bumps [at.yawk.lz4:lz4-java](https://github.com/yawkat/lz4-java) from 1.10.0 to 1.10.1. Release notes *Sourced from [at.yawk.lz4:lz4-java's releases](https://github.com/yawkat/lz4-java/releases).* > lz4-java v1.10.1 > ---------------- > > Contains fix for [CVE-2025-66566](GHSA-cmp6-m4wj-q63q)! > > What's Changed > -------------- > > * Add test for corrupted LZ4 block input stream by [`@Marcono1234`](https://github.com/Marcono1234) in [yawkat/lz4-java#7](https://redirect.github.com/yawkat/lz4-java/pull/7) > * Update documentation for checksum registration by [`@yawkat`](https://github.com/yawkat) in [yawkat/lz4-java#8](https://redirect.github.com/yawkat/lz4-java/pull/8) > * Migrate to maven-git-versioning-extension by [`@yawkat`](https://github.com/yawkat) in [yawkat/lz4-java#10](https://redirect.github.com/yawkat/lz4-java/pull/10) > * Add workflow\_dispatch trigger to multi-platform build to allow testing without release by [`@yawkat`](https://github.com/yawkat) in [yawkat/lz4-java#13](https://redirect.github.com/yawkat/lz4-java/pull/13) > * Copy native libraries to target/classes instead of src/resources by [`@yawkat`](https://github.com/yawkat) in [yawkat/lz4-java#14](https://redirect.github.com/yawkat/lz4-java/pull/14) > > **Full Changelog**: <yawkat/lz4-java@v1.10.0...v1.10.1> Commits * [`33d180c`](yawkat/lz4-java@33d180c) Merge commit from fork * [`da95a00`](yawkat/lz4-java@da95a00) Copy native libraries to target/classes instead of src/resources ([#14](https://redirect.github.com/yawkat/lz4-java/issues/14)) * [`1e9bf8c`](yawkat/lz4-java@1e9bf8c) Add workflow\_dispatch trigger to multi-platform build to allow testing withou... * [`89c02be`](yawkat/lz4-java@89c02be) Migrate to maven-git-versioning-extension ([#10](https://redirect.github.com/yawkat/lz4-java/issues/10)) * [`d948832`](yawkat/lz4-java@d948832) Update documentation for checksum registration ([#8](https://redirect.github.com/yawkat/lz4-java/issues/8)) * [`02bbbf0`](yawkat/lz4-java@02bbbf0) Add test for corrupted LZ4 block input stream ([#7](https://redirect.github.com/yawkat/lz4-java/issues/7)) * See full diff in [compare view](yawkat/lz4-java@v1.10.0...v1.10.1) [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
mergify Bot
added a commit
that referenced
this pull request
Dec 8, 2025
…ne [skip ci] Bumps [at.yawk.lz4:lz4-java](https://github.com/yawkat/lz4-java) from 1.10.0 to 1.10.1. Release notes *Sourced from [at.yawk.lz4:lz4-java's releases](https://github.com/yawkat/lz4-java/releases).* > lz4-java v1.10.1 > ---------------- > > Contains fix for [CVE-2025-66566](GHSA-cmp6-m4wj-q63q)! > > What's Changed > -------------- > > * Add test for corrupted LZ4 block input stream by [`@Marcono1234`](https://github.com/Marcono1234) in [yawkat/lz4-java#7](https://redirect.github.com/yawkat/lz4-java/pull/7) > * Update documentation for checksum registration by [`@yawkat`](https://github.com/yawkat) in [yawkat/lz4-java#8](https://redirect.github.com/yawkat/lz4-java/pull/8) > * Migrate to maven-git-versioning-extension by [`@yawkat`](https://github.com/yawkat) in [yawkat/lz4-java#10](https://redirect.github.com/yawkat/lz4-java/pull/10) > * Add workflow\_dispatch trigger to multi-platform build to allow testing without release by [`@yawkat`](https://github.com/yawkat) in [yawkat/lz4-java#13](https://redirect.github.com/yawkat/lz4-java/pull/13) > * Copy native libraries to target/classes instead of src/resources by [`@yawkat`](https://github.com/yawkat) in [yawkat/lz4-java#14](https://redirect.github.com/yawkat/lz4-java/pull/14) > > **Full Changelog**: <yawkat/lz4-java@v1.10.0...v1.10.1> Commits * [`33d180c`](yawkat/lz4-java@33d180c) Merge commit from fork * [`da95a00`](yawkat/lz4-java@da95a00) Copy native libraries to target/classes instead of src/resources ([#14](https://redirect.github.com/yawkat/lz4-java/issues/14)) * [`1e9bf8c`](yawkat/lz4-java@1e9bf8c) Add workflow\_dispatch trigger to multi-platform build to allow testing withou... * [`89c02be`](yawkat/lz4-java@89c02be) Migrate to maven-git-versioning-extension ([#10](https://redirect.github.com/yawkat/lz4-java/issues/10)) * [`d948832`](yawkat/lz4-java@d948832) Update documentation for checksum registration ([#8](https://redirect.github.com/yawkat/lz4-java/issues/8)) * [`02bbbf0`](yawkat/lz4-java@02bbbf0) Add test for corrupted LZ4 block input stream ([#7](https://redirect.github.com/yawkat/lz4-java/issues/7)) * See full diff in [compare view](yawkat/lz4-java@v1.10.0...v1.10.1) [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/ArcadeData/arcadedb/network/alerts).
This was referenced Jan 27, 2026
Merged
This was referenced Apr 13, 2026
mergify Bot
added a commit
that referenced
this pull request
May 3, 2026
…in /studio [skip ci] Bumps [swagger-ui-dist](https://github.com/swagger-api/swagger-ui) from 5.32.4 to 5.32.5. Release notes *Sourced from [swagger-ui-dist's releases](https://github.com/swagger-api/swagger-ui/releases).* > v5.32.5 > ------- > > [5.32.5](swagger-api/swagger-ui@v5.32.4...v5.32.5) (2026-04-27) > ------------------------------------------------------------------------------------------ > > ### Bug Fixes > > * **deps:** bump swagger-client to v3.37.3 ([#10858](https://redirect.github.com/swagger-api/swagger-ui/issues/10858)) ([74e48ce](swagger-api/swagger-ui@74e48ce)) > * **style:** markdown list items default text color in Dark Mode ([#10790](https://redirect.github.com/swagger-api/swagger-ui/issues/10790)) ([#10791](https://redirect.github.com/swagger-api/swagger-ui/issues/10791)) ([3608eaa](swagger-api/swagger-ui@3608eaa)) > > ### Reverts > > * Revert "Accessibility: Easier to access Authorization ([#10692](https://redirect.github.com/swagger-api/swagger-ui/issues/10692))" ([#10850](https://redirect.github.com/swagger-api/swagger-ui/issues/10850)) ([8d17c78](swagger-api/swagger-ui@8d17c78)) Commits * [`dcb493c`](swagger-api/swagger-ui@dcb493c) chore(release): cut the 5.32.5 release * [`74e48ce`](swagger-api/swagger-ui@74e48ce) fix(deps): bump swagger-client to v3.37.3 ([#10858](https://redirect.github.com/swagger-api/swagger-ui/issues/10858)) * [`8d17c78`](swagger-api/swagger-ui@8d17c78) Revert "Accessibility: Easier to access Authorization ([#10692](https://redirect.github.com/swagger-api/swagger-ui/issues/10692))" ([#10850](https://redirect.github.com/swagger-api/swagger-ui/issues/10850)) * [`3608eaa`](swagger-api/swagger-ui@3608eaa) fix(style): markdown list items default text color in Dark Mode ([#10790](https://redirect.github.com/swagger-api/swagger-ui/issues/10790)) ([#10](https://redirect.github.com/swagger-api/swagger-ui/issues/10)... * [`7ff52ab`](swagger-api/swagger-ui@7ff52ab) chore(deps): bump dompurify from 3.3.2 to 3.4.0 ([#10843](https://redirect.github.com/swagger-api/swagger-ui/issues/10843)) * See full diff in [compare view](swagger-api/swagger-ui@v5.32.4...v5.32.5) [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
lvca
added a commit
that referenced
this pull request
Jun 17, 2026
…nput, MATLAB_COLUMN (#4642) * feat: [#3099] vector quantization ergonomics, asSparse(), RRF array input, MATLAB_COLUMN Follow-up to #3099 addressing the remaining actionable review items. int8 quantization ergonomics (#8/#9/#10/#11): - vectorDequantizeInt8 accepts the result of vectorQuantizeInt8() directly (single-arg form), so min/max no longer have to be unpacked by hand. The (bytes, min, max) form still works. - vectorApproxDistance infers INT8 vs BINARY from the result objects, making the type string optional. Raw byte arrays still require an explicit type. - "ranking preserved" reworded to "preserves the top-k ordering". asSparse() method (#4): the method form of vector.denseToSparse(), consistent with the asString()/asVector() conversion-method family. Delegates to the function so the dense->sparse logic stays in one place. RRF array input (#14): vectorRRFScore also accepts the ranks grouped in a single array/list (plus optional { k }), consistent with vector.multiScore. MATLAB_COLUMN format (#21): semicolon-separated column vector [1.0; 2.0; 3.0] for vector.toString()/asString(). The asVector()/string parser now also splits on semicolons so it round-trips. Adds coverage in SQLFunctionVectorEnhancementsTest. * fix: [#3099] address PR review - approxDistance mixed-type, RRF rank validation, asSparse singleton - vectorApproxDistance.inferType: detect mixed INT8/BINARY result objects and throw a clear "Cannot mix INT8 and BINARY quantization results" error instead of routing to the wrong distance and surfacing a misleading "Expected BinaryQuantizationResult" message. - vectorRRFScore: unify the variadic and array forms so both skip null ranks (item absent from that ranking list) and validate every present rank as a positive integer. The array form no longer accepts fractional ranks, and the variadic form no longer silently truncates them. - SQLMethodAsSparse: reuse a shared stateless SQLFunctionVectorDenseToSparse instance instead of allocating one per call. - SQLFunctionVectorDequantizeInt8.getSyntax(): disambiguate the two overloads. Adds tests for mixed-type inference, null-rank parity, and non-integer rank rejection. * fix: [#3099] address 2nd PR review - approxDistance inference guard, docs, test coverage - vectorApproxDistance.inferType now requires BOTH 2-arg arguments to be quantization result objects; mixing a result object with a raw array (which inference can't do reliably) is rejected with a clear message pointing at the explicit 3-arg form. - Clarify in the class Javadoc that BINARY requires the BinaryQuantizationResult (raw packed bits are not enough), while INT8 accepts a result or a raw byte array. - Tidy getSyntax() of vectorDequantizeInt8 (drop the repeated function name). - Tests: add non-zero distance assertions for both INT8 and BINARY inference, the 3-arg explicit form with result objects, and the result-object/raw-array mismatch rejection. * fix: [#3099] address 3rd PR review - getSyntax clarity, primitive-array RRF, no boxing - vectorDequantizeInt8.getSyntax(): repeat the function name on both alternatives so neither reads as a bare tuple. - vectorRRFScore: iterate primitive rank arrays (int[]/long[]/float[]/double[]) directly instead of boxing them into an Object[], per the engine's GC-awareness policy. Object[]/List still skip nulls. Validation (positive integer) is shared by both forms via rankTerm(). * fix: [#3099] vectorDequantizeInt8 3-arg form accepts the result object too The single-arg form already accepted a QuantizationResult, but the issue's literal example uses the (result, min, max) form: vectorDequantizeInt8(vectorQuantizeInt8([...]), 1.0, 3.0). The 3-arg path now extracts the bytes from a QuantizationResult as well, so that exact query works instead of throwing "Quantized vector must be an array or list, found: QuantizationResult". * fix: [#3099] address 4th PR review - dequantizeInt8 min/max correctness, RRF NaN guard, edge cases - dequantizeInt8 3-arg form with a QuantizationResult now uses the result's own authoritative min/max instead of the explicit scalars, so passing a wrong min/max alongside the result object no longer silently dequantizes with the wrong scale. Removed the now-dead QuantizationResult branch in toByteArray. - RRFScore rankTerm now guards NaN/Infinity up front with a dedicated 'must be finite' message instead of letting them fall through to the misleading 'must be integers' error. - approxDistance INT8 path gives a helpful error naming the expected INT8 inputs when a BinaryQuantizationResult is passed (mixed types in the explicit 3-arg form). - Clarified inferType comment ('each argument must be a recognized result object'). - Documented the intentional separator leniency in VectorUtils string parsing. - Documented SQLMethodAsSparse shared-instance thread-safety; asSparse Javadoc arrow nit. - Tests: result-own-min/max wins, non-finite ranks rejected, explicit-type mixed-type message, and the SQL asSparse() path now asserts the returned SparseVector value (45 tests). * test: fix phase6VectorStatistics type witness (AVG returns Double, not Float) AVG() returns a Double (issue #4518), so result.<Float>getProperty(...) on the AVG-wrapped avg_magnitude/sparsity_pct columns threw a ClassCastException. Use the matching <Double> witness. * fix: [#3099] address 5th PR review - dequantizeInt8 null-scalar ordering bug - BUG: dequantizeInt8(result, null, null) returned null instead of using the result object's embedded min/max, because the scalar null-guard fired before the QuantizationResult check. Moved the QuantizationResult early-exit above the null-guard so embedded min/max always win, even with null/wrong explicit scalars. - getSyntax() compacted to a single form (NAME + '(<result> | <quantized_bytes>, <min>, <max>)'), matching the convention used by approxDistance. - Documented why float[]/double[] rank arrays are safe (rankTerm rejects any non-integer regardless of array type, so a precision-lost float cannot slip through). - Tests: (result, null, null) uses embedded min/max; explicit 'BINARY' with INT8 result objects surfaces a CommandSQLParsingException naming BinaryQuantizationResult (not a raw ClassCastException). Replaced fully-qualified java.util names with imports (47 tests). * fix: [#3099] address 6th PR review - rrfFromArray docs/AssertionError, dequantizeInt8 syntax hint, no-space semicolon test * fix: [#3099] address 7th PR review - dequantizeInt8 syntax/Javadoc, RRF rejects float[]/double[] rank arrays, inferType readability * test: [#4643] update SEARCH_FIELDS_MORE nonExistentRID expectation to function's own "Record not found" message (missing-bucket lookup no longer throws after #4643) * fix: [#3099] address 8th PR review - document Object[] inclusion in RRF isArrayLike, skip unused separator computation for PRETTY format * fix: [#3099] address 9th PR review - dequantizeInt8 getSyntax shows both forms + clarified ignored-scalar contract, RRF short[] note, tighter binary error assertion * fix: [#3099] address 10th PR review - dequantizeInt8 rejects conflicting (non-matching) explicit min/max with a result, 2-arg comment, stateless contract on denseToSparse * docs: [#3099] address 11th PR review - explain why rankTerm uses Math.rint over a (long) cast for the integer check * fix: [#3099] address 12th PR review - tighten+document dequantize tolerance (1e-5), clarify isArrayLike/RRF syntax/denseToSparse contract comments, test annotations
tae898
referenced
this pull request
in humemai/arcadedb-embedded-python
Jun 28, 2026
…y-all-4.1.67.Final Bump netty-all from 4.1.60.Final to 4.1.67.Final
tae898
referenced
this pull request
in humemai/arcadedb-embedded-python
Jun 28, 2026
Bumps [at.yawk.lz4:lz4-java](https://github.com/yawkat/lz4-java) from 1.10.0 to 1.10.1. Release notes *Sourced from [at.yawk.lz4:lz4-java's releases](https://github.com/yawkat/lz4-java/releases).* > lz4-java v1.10.1 > ---------------- > > Contains fix for [CVE-2025-66566](GHSA-cmp6-m4wj-q63q)! > > What's Changed > -------------- > > * Add test for corrupted LZ4 block input stream by [`@Marcono1234`](https://github.com/Marcono1234) in [yawkat/lz4-java#7](https://redirect.github.com/yawkat/lz4-java/pull/7) > * Update documentation for checksum registration by [`@yawkat`](https://github.com/yawkat) in [yawkat/lz4-java#8](https://redirect.github.com/yawkat/lz4-java/pull/8) > * Migrate to maven-git-versioning-extension by [`@yawkat`](https://github.com/yawkat) in [yawkat/lz4-java#10](https://redirect.github.com/yawkat/lz4-java/pull/10) > * Add workflow\_dispatch trigger to multi-platform build to allow testing without release by [`@yawkat`](https://github.com/yawkat) in [yawkat/lz4-java#13](https://redirect.github.com/yawkat/lz4-java/pull/13) > * Copy native libraries to target/classes instead of src/resources by [`@yawkat`](https://github.com/yawkat) in [yawkat/lz4-java#14](https://redirect.github.com/yawkat/lz4-java/pull/14) > > **Full Changelog**: <yawkat/lz4-java@v1.10.0...v1.10.1> Commits * [`33d180c`](yawkat/lz4-java@33d180c) Merge commit from fork * [`da95a00`](yawkat/lz4-java@da95a00) Copy native libraries to target/classes instead of src/resources ([#14](https://redirect.github.com/yawkat/lz4-java/issues/14)) * [`1e9bf8c`](yawkat/lz4-java@1e9bf8c) Add workflow\_dispatch trigger to multi-platform build to allow testing withou... * [`89c02be`](yawkat/lz4-java@89c02be) Migrate to maven-git-versioning-extension ([#10](https://redirect.github.com/yawkat/lz4-java/issues/10)) * [`d948832`](yawkat/lz4-java@d948832) Update documentation for checksum registration ([#8](https://redirect.github.com/yawkat/lz4-java/issues/8)) * [`02bbbf0`](yawkat/lz4-java@02bbbf0) Add test for corrupted LZ4 block input stream ([#7](https://redirect.github.com/yawkat/lz4-java/issues/7)) * See full diff in [compare view](yawkat/lz4-java@v1.10.0...v1.10.1) [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
tae898
referenced
this pull request
in humemai/arcadedb-embedded-python
Jun 28, 2026
…ne [skip ci] Bumps [at.yawk.lz4:lz4-java](https://github.com/yawkat/lz4-java) from 1.10.0 to 1.10.1. Release notes *Sourced from [at.yawk.lz4:lz4-java's releases](https://github.com/yawkat/lz4-java/releases).* > lz4-java v1.10.1 > ---------------- > > Contains fix for [CVE-2025-66566](GHSA-cmp6-m4wj-q63q)! > > What's Changed > -------------- > > * Add test for corrupted LZ4 block input stream by [`@Marcono1234`](https://github.com/Marcono1234) in [yawkat/lz4-java#7](https://redirect.github.com/yawkat/lz4-java/pull/7) > * Update documentation for checksum registration by [`@yawkat`](https://github.com/yawkat) in [yawkat/lz4-java#8](https://redirect.github.com/yawkat/lz4-java/pull/8) > * Migrate to maven-git-versioning-extension by [`@yawkat`](https://github.com/yawkat) in [yawkat/lz4-java#10](https://redirect.github.com/yawkat/lz4-java/pull/10) > * Add workflow\_dispatch trigger to multi-platform build to allow testing without release by [`@yawkat`](https://github.com/yawkat) in [yawkat/lz4-java#13](https://redirect.github.com/yawkat/lz4-java/pull/13) > * Copy native libraries to target/classes instead of src/resources by [`@yawkat`](https://github.com/yawkat) in [yawkat/lz4-java#14](https://redirect.github.com/yawkat/lz4-java/pull/14) > > **Full Changelog**: <yawkat/lz4-java@v1.10.0...v1.10.1> Commits * [`33d180c`](yawkat/lz4-java@33d180c) Merge commit from fork * [`da95a00`](yawkat/lz4-java@da95a00) Copy native libraries to target/classes instead of src/resources ([#14](https://redirect.github.com/yawkat/lz4-java/issues/14)) * [`1e9bf8c`](yawkat/lz4-java@1e9bf8c) Add workflow\_dispatch trigger to multi-platform build to allow testing withou... * [`89c02be`](yawkat/lz4-java@89c02be) Migrate to maven-git-versioning-extension ([#10](https://redirect.github.com/yawkat/lz4-java/issues/10)) * [`d948832`](yawkat/lz4-java@d948832) Update documentation for checksum registration ([#8](https://redirect.github.com/yawkat/lz4-java/issues/8)) * [`02bbbf0`](yawkat/lz4-java@02bbbf0) Add test for corrupted LZ4 block input stream ([#7](https://redirect.github.com/yawkat/lz4-java/issues/7)) * See full diff in [compare view](yawkat/lz4-java@v1.10.0...v1.10.1) [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/ArcadeData/arcadedb/network/alerts).
tae898
referenced
this pull request
in humemai/arcadedb-embedded-python
Jun 28, 2026
…in /studio [skip ci] Bumps [swagger-ui-dist](https://github.com/swagger-api/swagger-ui) from 5.32.4 to 5.32.5. Release notes *Sourced from [swagger-ui-dist's releases](https://github.com/swagger-api/swagger-ui/releases).* > v5.32.5 > ------- > > [5.32.5](swagger-api/swagger-ui@v5.32.4...v5.32.5) (2026-04-27) > ------------------------------------------------------------------------------------------ > > ### Bug Fixes > > * **deps:** bump swagger-client to v3.37.3 ([ArcadeData#10858](https://redirect.github.com/swagger-api/swagger-ui/issues/10858)) ([74e48ce](swagger-api/swagger-ui@74e48ce)) > * **style:** markdown list items default text color in Dark Mode ([ArcadeData#10790](https://redirect.github.com/swagger-api/swagger-ui/issues/10790)) ([ArcadeData#10791](https://redirect.github.com/swagger-api/swagger-ui/issues/10791)) ([3608eaa](swagger-api/swagger-ui@3608eaa)) > > ### Reverts > > * Revert "Accessibility: Easier to access Authorization ([ArcadeData#10692](https://redirect.github.com/swagger-api/swagger-ui/issues/10692))" ([ArcadeData#10850](https://redirect.github.com/swagger-api/swagger-ui/issues/10850)) ([8d17c78](swagger-api/swagger-ui@8d17c78)) Commits * [`dcb493c`](swagger-api/swagger-ui@dcb493c) chore(release): cut the 5.32.5 release * [`74e48ce`](swagger-api/swagger-ui@74e48ce) fix(deps): bump swagger-client to v3.37.3 ([ArcadeData#10858](https://redirect.github.com/swagger-api/swagger-ui/issues/10858)) * [`8d17c78`](swagger-api/swagger-ui@8d17c78) Revert "Accessibility: Easier to access Authorization ([ArcadeData#10692](https://redirect.github.com/swagger-api/swagger-ui/issues/10692))" ([ArcadeData#10850](https://redirect.github.com/swagger-api/swagger-ui/issues/10850)) * [`3608eaa`](swagger-api/swagger-ui@3608eaa) fix(style): markdown list items default text color in Dark Mode ([ArcadeData#10790](https://redirect.github.com/swagger-api/swagger-ui/issues/10790)) ([#10](https://redirect.github.com/swagger-api/swagger-ui/issues/10)... * [`7ff52ab`](swagger-api/swagger-ui@7ff52ab) chore(deps): bump dompurify from 3.3.2 to 3.4.0 ([ArcadeData#10843](https://redirect.github.com/swagger-api/swagger-ui/issues/10843)) * See full diff in [compare view](swagger-api/swagger-ui@v5.32.4...v5.32.5) [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
robfrank
pushed a commit
that referenced
this pull request
Aug 14, 2026
…nput, MATLAB_COLUMN (#4642) * feat: [#3099] vector quantization ergonomics, asSparse(), RRF array input, MATLAB_COLUMN Follow-up to #3099 addressing the remaining actionable review items. int8 quantization ergonomics (#8/#9/#10/#11): - vectorDequantizeInt8 accepts the result of vectorQuantizeInt8() directly (single-arg form), so min/max no longer have to be unpacked by hand. The (bytes, min, max) form still works. - vectorApproxDistance infers INT8 vs BINARY from the result objects, making the type string optional. Raw byte arrays still require an explicit type. - "ranking preserved" reworded to "preserves the top-k ordering". asSparse() method (#4): the method form of vector.denseToSparse(), consistent with the asString()/asVector() conversion-method family. Delegates to the function so the dense->sparse logic stays in one place. RRF array input (#14): vectorRRFScore also accepts the ranks grouped in a single array/list (plus optional { k }), consistent with vector.multiScore. MATLAB_COLUMN format (#21): semicolon-separated column vector [1.0; 2.0; 3.0] for vector.toString()/asString(). The asVector()/string parser now also splits on semicolons so it round-trips. Adds coverage in SQLFunctionVectorEnhancementsTest. * fix: [#3099] address PR review - approxDistance mixed-type, RRF rank validation, asSparse singleton - vectorApproxDistance.inferType: detect mixed INT8/BINARY result objects and throw a clear "Cannot mix INT8 and BINARY quantization results" error instead of routing to the wrong distance and surfacing a misleading "Expected BinaryQuantizationResult" message. - vectorRRFScore: unify the variadic and array forms so both skip null ranks (item absent from that ranking list) and validate every present rank as a positive integer. The array form no longer accepts fractional ranks, and the variadic form no longer silently truncates them. - SQLMethodAsSparse: reuse a shared stateless SQLFunctionVectorDenseToSparse instance instead of allocating one per call. - SQLFunctionVectorDequantizeInt8.getSyntax(): disambiguate the two overloads. Adds tests for mixed-type inference, null-rank parity, and non-integer rank rejection. * fix: [#3099] address 2nd PR review - approxDistance inference guard, docs, test coverage - vectorApproxDistance.inferType now requires BOTH 2-arg arguments to be quantization result objects; mixing a result object with a raw array (which inference can't do reliably) is rejected with a clear message pointing at the explicit 3-arg form. - Clarify in the class Javadoc that BINARY requires the BinaryQuantizationResult (raw packed bits are not enough), while INT8 accepts a result or a raw byte array. - Tidy getSyntax() of vectorDequantizeInt8 (drop the repeated function name). - Tests: add non-zero distance assertions for both INT8 and BINARY inference, the 3-arg explicit form with result objects, and the result-object/raw-array mismatch rejection. * fix: [#3099] address 3rd PR review - getSyntax clarity, primitive-array RRF, no boxing - vectorDequantizeInt8.getSyntax(): repeat the function name on both alternatives so neither reads as a bare tuple. - vectorRRFScore: iterate primitive rank arrays (int[]/long[]/float[]/double[]) directly instead of boxing them into an Object[], per the engine's GC-awareness policy. Object[]/List still skip nulls. Validation (positive integer) is shared by both forms via rankTerm(). * fix: [#3099] vectorDequantizeInt8 3-arg form accepts the result object too The single-arg form already accepted a QuantizationResult, but the issue's literal example uses the (result, min, max) form: vectorDequantizeInt8(vectorQuantizeInt8([...]), 1.0, 3.0). The 3-arg path now extracts the bytes from a QuantizationResult as well, so that exact query works instead of throwing "Quantized vector must be an array or list, found: QuantizationResult". * fix: [#3099] address 4th PR review - dequantizeInt8 min/max correctness, RRF NaN guard, edge cases - dequantizeInt8 3-arg form with a QuantizationResult now uses the result's own authoritative min/max instead of the explicit scalars, so passing a wrong min/max alongside the result object no longer silently dequantizes with the wrong scale. Removed the now-dead QuantizationResult branch in toByteArray. - RRFScore rankTerm now guards NaN/Infinity up front with a dedicated 'must be finite' message instead of letting them fall through to the misleading 'must be integers' error. - approxDistance INT8 path gives a helpful error naming the expected INT8 inputs when a BinaryQuantizationResult is passed (mixed types in the explicit 3-arg form). - Clarified inferType comment ('each argument must be a recognized result object'). - Documented the intentional separator leniency in VectorUtils string parsing. - Documented SQLMethodAsSparse shared-instance thread-safety; asSparse Javadoc arrow nit. - Tests: result-own-min/max wins, non-finite ranks rejected, explicit-type mixed-type message, and the SQL asSparse() path now asserts the returned SparseVector value (45 tests). * test: fix phase6VectorStatistics type witness (AVG returns Double, not Float) AVG() returns a Double (issue #4518), so result.<Float>getProperty(...) on the AVG-wrapped avg_magnitude/sparsity_pct columns threw a ClassCastException. Use the matching <Double> witness. * fix: [#3099] address 5th PR review - dequantizeInt8 null-scalar ordering bug - BUG: dequantizeInt8(result, null, null) returned null instead of using the result object's embedded min/max, because the scalar null-guard fired before the QuantizationResult check. Moved the QuantizationResult early-exit above the null-guard so embedded min/max always win, even with null/wrong explicit scalars. - getSyntax() compacted to a single form (NAME + '(<result> | <quantized_bytes>, <min>, <max>)'), matching the convention used by approxDistance. - Documented why float[]/double[] rank arrays are safe (rankTerm rejects any non-integer regardless of array type, so a precision-lost float cannot slip through). - Tests: (result, null, null) uses embedded min/max; explicit 'BINARY' with INT8 result objects surfaces a CommandSQLParsingException naming BinaryQuantizationResult (not a raw ClassCastException). Replaced fully-qualified java.util names with imports (47 tests). * fix: [#3099] address 6th PR review - rrfFromArray docs/AssertionError, dequantizeInt8 syntax hint, no-space semicolon test * fix: [#3099] address 7th PR review - dequantizeInt8 syntax/Javadoc, RRF rejects float[]/double[] rank arrays, inferType readability * test: [#4643] update SEARCH_FIELDS_MORE nonExistentRID expectation to function's own "Record not found" message (missing-bucket lookup no longer throws after #4643) * fix: [#3099] address 8th PR review - document Object[] inclusion in RRF isArrayLike, skip unused separator computation for PRETTY format * fix: [#3099] address 9th PR review - dequantizeInt8 getSyntax shows both forms + clarified ignored-scalar contract, RRF short[] note, tighter binary error assertion * fix: [#3099] address 10th PR review - dequantizeInt8 rejects conflicting (non-matching) explicit min/max with a result, 2-arg comment, stateless contract on denseToSparse * docs: [#3099] address 11th PR review - explain why rankTerm uses Math.rint over a (long) cast for the integer check * fix: [#3099] address 12th PR review - tighten+document dequantize tolerance (1e-5), clarify isArrayLike/RRF syntax/denseToSparse contract comments, test annotations (cherry picked from commit 9013ffb)
This was referenced Oct 3, 2026
lvca
added a commit
to shaunpatterson/arcadedb
that referenced
this pull request
Nov 20, 2026
…cts the RID the client now decodes Main's toGrpcValueRecordWithIdentityIsALink (issue ArcadeData#12197) asserts that a link encoded and decoded again is the String "ArcadeData#10:5", which is the decoding this PR replaces: a link reads back as a RID, as the embedded engine answers it. Textually the two do not conflict, so only the merge of main into the branch shows it. Adds decode tests for a list and a map of links, and for text that merely looks like a rid.
lvca
added a commit
that referenced
this pull request
Nov 20, 2026
…perty back as a RID (#12228) Fixes #12195. ## Problem A LINK stored in a property the schema does not declare was read back by both Java remote clients as a `String` (`"#1:0"`), and lists and maps of links as strings. `(Identifiable) doc.get("friend")` threw `ClassCastException`. The HTTP client also disagreed with itself: a projection of the same single link answered a `RID`. ## Change HTTP (`engine` `JsonSerializer`): - An element row already carried an `@props` hint for an undeclared property whose value is non-finite (#10905), since nothing else tells the client what the JSON text stands for. A link is in the same position: it goes out as its `"#12:0"` text. So an undeclared property holding a link, or a list or map of links only, now gets its hint too (`friend:11`, `friends:9(11)`, `byName:10(11)`). Every other element row keeps its shape. As before, hints are only emitted when the request asks for them (`typeHints`, which `RemoteDatabase` sends). - `appendTypeHint()` adds LINK as an element type for a LIST/MAP whose non-null items are all links, so a projected list of links is typed too. - No client change was needed for HTTP: `RemoteImmutableDocument` already applies `@props` to undeclared properties, and converts a LINK hint (and a LINK element hint) to `RID`. A string that only looks like a RID (`'#1:0'` stored as text) gets no hint and stays a String. gRPC (`grpc-client`): - `ProtoUtils.fromGrpcValue()` decodes `LINK_VALUE` as a `RID` instead of its text, for record properties and projections alike. - Two places that cast what they received to `String` now accept a `RID`. One is `RemoteImmutableEdge` for `@out`/`@in`, which the server sends as links. The other is `RemoteImmutableDocument` for `@rid`, when a projection row carries it as a property. ## Tests - `server` `Issue12195RemoteLinkReadBackIT` (HTTP): link, list of links and map of links read back as `RID` through `lookupByRID()`, a query row and `iterateType()`, plus the `Identifiable` cast; a projected list of links is a list of `RID`; a string that looks like a RID stays a string. - `grpc-client` `Issue12195GrpcLinkReadBackIT`: link and list of links read back as `RID` through `lookupByRID()` and a projection; edges still resolve `getOut()`/`getIn()`, `countEdges()` works, and `SELECT @Rid, @type, name` keeps its identity. Failing first: with `engine/src/main`, `network/src/main` and `grpc-client/src/main` reverted to `origin/main`: 3 of the 5 tests fail as described in the issue (`"#1:0"` instead of `#1:0` for the HTTP record read and projected list, and for the gRPC record read); the two guards (a RID-looking string stays a string, edges and `@rid` projections over gRPC) pass both before and after. Regression run: `-pl engine,network,server,grpc-client -am test -Dtest='com/arcadedb/serializer/**,com/arcadedb/remote/**,com/arcadedb/server/http/handler/**,*TypeHint*,*Issue5812*,*Issue10905*,*Issue4267*,*Issue4849*' -DexcludedGroups=benchmark,slow`: 372 classes, 3,089 tests, 1 failure: `ProtoUtilsTest.fromGrpcValueLink`, which asserted the old decoding (`"#10:5"`). It now expects `new RID(10, 5)`, the behavior this PR introduces; `com/arcadedb/remote/grpc/utils/**` is green after that change (64 tests). End to end with the differential harness (server and client jars from this branch): HTTP: `friend` (LINK) reads back as `RID #1:0` from `lookupByRID()` and a projection, `friends` as `[RID #1:0]`, `byName` as `{x=#1:0}` (RID), `(Identifiable) d.get("friend")` works. gRPC: `ridValue`/`ridList` read back as RID. The differential graph and supernode probes (P2, P4) report the same set of differences before and after, over HTTP and over gRPC. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> <!-- coderabbit-ai-generated:v1 --> ## Summary by CodeRabbit * **Bug Fixes** * Remote and gRPC reads now preserve database links as RID values, including links nested in lists and maps, instead of returning them as text. * Remote edge endpoints and document identities correctly handle RID values. * JSON type hints now identify undeclared links and homogeneous collections or maps of links, including projected results. Strings that resemble RIDs and mixed-value collections remain distinguishable. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: lvca <l.garulli@arcadedata.com>
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.
Bumps netty-all from 4.1.60.Final to 4.1.67.Final.
Commits
b785fa9[maven-release-plugin] prepare release netty-4.1.67.Final7903a44Revert "[maven-release-plugin] prepare release netty-4.1.67.Final"ec23189Revert "[maven-release-plugin] prepare for next development iteration"76c55ca[maven-release-plugin] prepare for next development iterationf773733[maven-release-plugin] prepare release netty-4.1.67.Final056eba4server h2c upgrade fail when request doesn't have connection header (#11569)f750e2eAdd support for client-side TCP FastOpen to KQueue MacOS (#11560)699549dImprove test failure reporting of EpollSocketChannelConfigTest (#11570)beb4588Inline variables to make code more readable (#11565)3c27e00Some small improvements (#11564)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)