build support#1
Merged
Merged
Conversation
add pre-commit configuration add gh actions add dependabot configuration
Member
|
Thanks! |
lvca
pushed a commit
that referenced
this pull request
Sep 7, 2021
Get latest commits from main project
mergify Bot
added a commit
that referenced
this pull request
Aug 29, 2025
….3.8 to 0.3.13 in /studio [skip ci] Bumps [@jridgewell/gen-mapping](https://github.com/jridgewell/sourcemaps/tree/HEAD/packages/gen-mapping) from 0.3.8 to 0.3.13. Changelog *Sourced from [`@jridgewell/gen-mapping`'s changelog](https://github.com/jridgewell/sourcemaps/blob/main/packages/gen-mapping/CHANGELOG.md).* > [0.3.13] - 2025-08-12 > ===================== > > * Use `default` subpath export: <jridgewell/sourcemaps@aab8d72> > * Transform `export default` into `module.exports =` in UMD plugin: <jridgewell/sourcemaps@cf85c75> > > **Full Changelog**: <jridgewell/sourcemaps@gen-mapping/0.3.12...gen-mapping/0.3.13> > > [0.3.12] - 2025-07-01 > ===================== > > * Use `Object.assign` to avoid polyfill in old Node versions: <jridgewell/sourcemaps@dd0615a> > * Optimize UMD wrapper: <jridgewell/sourcemaps@557ca37> > * Reorder subpath exports to improve import usage: [#35](https://github.com/jridgewell/sourcemaps/tree/HEAD/packages/gen-mapping/issues/35) > > **Full Changelog**: <jridgewell/sourcemaps@gen-mapping/0.3.11...gen-mapping/0.3.12> > > [0.3.11] - 2025-06-30 > ===================== > > * Update UMD Wrapper to fix webpack build issue: [#33](https://github.com/jridgewell/sourcemaps/tree/HEAD/packages/gen-mapping/issues/33) > * Add `getOwnPropertyDescriptors` polyfill to support Node v6: [#34](https://github.com/jridgewell/sourcemaps/tree/HEAD/packages/gen-mapping/issues/34) > > **Full Changelog**: <jridgewell/sourcemaps@gen-mapping/0.3.10...gen-mapping/0.3.11> > > [0.3.10] - 2025-06-30 > ===================== > > * Remove `require(esm)` support to fix bug with Node v22: <jridgewell/sourcemaps@e957842> > > **Full Changelog**: <jridgewell/sourcemaps@gen-mapping/0.3.9...gen-mapping/0.3.10> > > [0.3.9] - 2025-06-29 > ==================== > > * Fix package types for CJS and ESM imports: <jridgewell/sourcemaps@a924ed3> > * fix: use stable version of sourcemap-codec dependency: [#26](https://github.com/jridgewell/sourcemaps/tree/HEAD/packages/gen-mapping/issues/26) (thanks [`@benmccann`](https://github.com/benmccann)) > * Add `module-sync` exports type for [require(esm)](https://joyeecheung.github.io/blog/2024/03/18/require-esm-in-node-js/): <jridgewell/sourcemaps@3836f6c> > * Add type declaration source maps to assist go-to-definition: <jridgewell/sourcemaps@9a02665> > * Temporarily remove scopes/ranges APIs: <jridgewell/sourcemaps@7575b63> > * Include set-array source directly in gen-mapping project: [#1](https://github.com/jridgewell/sourcemaps/tree/HEAD/packages/gen-mapping/issues/1) (thanks [`@benmccann`](https://github.com/benmccann)) > > **Full Changelog**: <jridgewell/sourcemaps@gen-mapping/0.3.5...gen-mapping/0.3.9> > > [0.3.5] - 2024-03-01 > ==================== > > * Add `ignoreList` support: <jridgewell/gen-mapping@9add0c2> > > **Full Changelog**: <jridgewell/gen-mapping@v0.3.4...v0.3.5> > > [0.3.4] - 2024-02-24 > ==================== > > **Full Changelog**: <jridgewell/gen-mapping@v0.3.3...v0.3.4> > > [0.3.3] - 2023-04-07 > ==================== ... (truncated) Commits * [`a969b67`](jridgewell/sourcemaps@a969b67) gen-mapping/0.3.13 * [`aab8d72`](jridgewell/sourcemaps@aab8d72) Use default subpath condition for fallback * [`c780a90`](jridgewell/sourcemaps@c780a90) Update links to point to monorepo * [`e2fa5d7`](jridgewell/sourcemaps@e2fa5d7) remapping/2.3.4 * [`26fe89d`](jridgewell/sourcemaps@26fe89d) gen-mapping/0.3.12 * [`a1c0fa0`](jridgewell/sourcemaps@a1c0fa0) Reorder subpath exports * [`dd0615a`](jridgewell/sourcemaps@dd0615a) gen-mapping: Use `Object.assign` to avoid needing `getOwnPropertyDescriptors`... * [`82195c5`](jridgewell/sourcemaps@82195c5) gen-mapping/0.3.11 * [`58ea44b`](jridgewell/sourcemaps@58ea44b) Update changelogs * [`e0c7250`](jridgewell/sourcemaps@e0c7250) Why isn't GH autolinking commit SHAs? * See full diff in [compare view](https://github.com/jridgewell/sourcemaps/commits/gen-mapping/0.3.13/packages/gen-mapping) [](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
Oct 12, 2025
…4 [skip ci] Bumps [org.jacoco:jacoco-maven-plugin](https://github.com/jacoco/jacoco) from 0.8.13 to 0.8.14. Release notes *Sourced from [org.jacoco:jacoco-maven-plugin's releases](https://github.com/jacoco/jacoco/releases).* > 0.8.14 > ------ > > New Features > ------------ > > * JaCoCo now officially supports Java 25 (GitHub [#1950](https://redirect.github.com/jacoco/jacoco/issues/1950)). > * Experimental support for Java 26 class files (GitHub [#1870](https://redirect.github.com/jacoco/jacoco/issues/1807)). > * Branches added by the Kotlin compiler for default argument number 33 or higher are filtered out during generation of report (GitHub [#1655](https://redirect.github.com/jacoco/jacoco/issues/1655)). > * Part of bytecode generated by the Kotlin compiler for elvis operator that follows safe call operator is filtered out during generation of report (GitHub [#1814](https://redirect.github.com/jacoco/jacoco/issues/1814), [#1954](https://redirect.github.com/jacoco/jacoco/issues/1954)). > * Part of bytecode generated by the Kotlin compiler for more cases of chained safe call operators is filtered out during generation of report (GitHub [#1956](https://redirect.github.com/jacoco/jacoco/issues/1956)). > * Part of bytecode generated by the Kotlin compiler for invocations of suspendCoroutineUninterceptedOrReturn intrinsic is filtered out during generation of report (GitHub [#1929](https://redirect.github.com/jacoco/jacoco/issues/1929)). > * Part of bytecode generated by the Kotlin compiler for suspending lambdas with parameters is filtered out during generation of report (GitHub [#1945](https://redirect.github.com/jacoco/jacoco/issues/1945)). > * Part of bytecode generated by the Kotlin compiler for suspending functions and lambdas with suspension points that return inline value class is filtered out during generation of report (GitHub [#1871](https://redirect.github.com/jacoco/jacoco/issues/1871)). > * Part of bytecode generated by the Kotlin Compose compiler plugin for pausable composition is filtered out during generation of report (GitHub [#1911](https://redirect.github.com/jacoco/jacoco/issues/1911)). > * Methods generated by the Kotlin serialization compiler plugin are filtered out (GitHub [#1885](https://redirect.github.com/jacoco/jacoco/issues/1885), [#1970](https://redirect.github.com/jacoco/jacoco/issues/1970), [#1971](https://redirect.github.com/jacoco/jacoco/issues/1971)). > > Fixed bugs > ---------- > > * Fixed handling of implicit else clause of when with String subject in Kotlin (GitHub [#1813](https://redirect.github.com/jacoco/jacoco/issues/1813), [#1940](https://redirect.github.com/jacoco/jacoco/issues/1940)). > * Fixed handling of implicit default clause of switch by String in Java when compiled by ECJ (GitHub [#1813](https://redirect.github.com/jacoco/jacoco/issues/1813), [#1940](https://redirect.github.com/jacoco/jacoco/issues/1940)). > Fixed handling of exceptions in chains of safe call operators in Kotlin (GitHub [#1819](https://redirect.github.com/jacoco/jacoco/issues/1819)). > > Non-functional Changes > ---------------------- > > * JaCoCo now depends on ASM 9.9 (GitHub [#1965](https://redirect.github.com/jacoco/jacoco/issues/1965)). Commits * [`2eb2483`](jacoco/jacoco@2eb2483) Prepare release v0.8.14 * [`de76181`](jacoco/jacoco@de76181) KotlinSerializableFilter should filter more methods ([#1971](https://redirect.github.com/jacoco/jacoco/issues/1971)) * [`89c4bd5`](jacoco/jacoco@89c4bd5) Fix NPE in KotlinSerializableFilter ([#1970](https://redirect.github.com/jacoco/jacoco/issues/1970)) * [`0981128`](jacoco/jacoco@0981128) Migrate release staging to the Central Publisher Portal ([#1968](https://redirect.github.com/jacoco/jacoco/issues/1968)) * [`d07bc6b`](jacoco/jacoco@d07bc6b) Add filter for bytecode generated by Kotlin serialization compiler plugin ([#1](https://redirect.github.com/jacoco/jacoco/issues/1)... * [`5e35fd5`](jacoco/jacoco@5e35fd5) Upgrade maven-dependency-plugin to 3.9.0 ([#1966](https://redirect.github.com/jacoco/jacoco/issues/1966)) * [`c2fe5cc`](jacoco/jacoco@c2fe5cc) Upgrade ASM to 9.9 ([#1965](https://redirect.github.com/jacoco/jacoco/issues/1965)) * [`b0f8e23`](jacoco/jacoco@b0f8e23) KotlinSafeCallOperatorFilter should filter "unoptimized" safe call followed b... * [`c7bd3f4`](jacoco/jacoco@c7bd3f4) Upgrade spotless-maven-plugin to 3.0.0 ([#1961](https://redirect.github.com/jacoco/jacoco/issues/1961)) * [`faa289d`](jacoco/jacoco@faa289d) KotlinSafeCallOperatorFilter should not be affected by presence of pseudo ins... * Additional commits viewable in [compare view](jacoco/jacoco@v0.8.13...v0.8.14) [](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 1, 2025
…in /studio [skip ci] Bumps [swagger-ui-dist](https://github.com/swagger-api/swagger-ui) from 5.30.2 to 5.30.3. Release notes *Sourced from [swagger-ui-dist's releases](https://github.com/swagger-api/swagger-ui/releases).* > v5.30.3 > ------- > > [5.30.3](swagger-api/swagger-ui@v5.30.2...v5.30.3) (2025-11-25) > ------------------------------------------------------------------------------------------ > > ### Bug Fixes > > * **deps:** update vulnerable `@release-it/conventional-changelog` to 10.0.2 ([#10645](https://redirect.github.com/swagger-api/swagger-ui/issues/10645)) ([6acfc6e](swagger-api/swagger-ui@6acfc6e)) > * **deps:** update vulnerable dependencies (js-yaml & glob) ([#10644](https://redirect.github.com/swagger-api/swagger-ui/issues/10644)) ([03cf01b](swagger-api/swagger-ui@03cf01b)) > * **utils:** handle sanitizing multi-level relative paths ([#10640](https://redirect.github.com/swagger-api/swagger-ui/issues/10640)) ([58aff59](swagger-api/swagger-ui@58aff59)), closes [#4107](https://redirect.github.com/swagger-api/swagger-ui/issues/4107) Commits * [`199761a`](swagger-api/swagger-ui@199761a) chore(release): cut the 5.30.3 release * [`6acfc6e`](swagger-api/swagger-ui@6acfc6e) fix(deps): update vulnerable `@release-it/conventional-changelog` to 10.0.2 ([#1](https://redirect.github.com/swagger-api/swagger-ui/issues/1)... * [`03cf01b`](swagger-api/swagger-ui@03cf01b) fix(deps): update vulnerable dependencies (js-yaml & glob) ([#10644](https://redirect.github.com/swagger-api/swagger-ui/issues/10644)) * [`8d9142e`](swagger-api/swagger-ui@8d9142e) chore(deps): bump actions/checkout from 5 to 6 ([#10643](https://redirect.github.com/swagger-api/swagger-ui/issues/10643)) * [`58aff59`](swagger-api/swagger-ui@58aff59) fix(utils): handle sanitizing multi-level relative paths ([#10640](https://redirect.github.com/swagger-api/swagger-ui/issues/10640)) * [`85f0c5f`](swagger-api/swagger-ui@85f0c5f) chore(deps): bump js-yaml from 4.1.0 to 4.1.1 ([#10637](https://redirect.github.com/swagger-api/swagger-ui/issues/10637)) * [`7f75ee3`](swagger-api/swagger-ui@7f75ee3) chore(deps): bump actions/setup-node from 5 to 6 ([#10608](https://redirect.github.com/swagger-api/swagger-ui/issues/10608)) * [`2067270`](swagger-api/swagger-ui@2067270) chore(deps): bump github/codeql-action from 3 to 4 ([#10595](https://redirect.github.com/swagger-api/swagger-ui/issues/10595)) * See full diff in [compare view](swagger-api/swagger-ui@v5.30.2...v5.30.3) [](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)
This was referenced Jan 27, 2026
This was referenced Feb 15, 2026
Merged
This was referenced Jul 6, 2026
fix(#4953,#4954,#4961): async executor stall detector, shutdown draining, concurrency cleanups
#5062
Merged
This was referenced Jul 7, 2026
2 tasks
robfrank
added a commit
that referenced
this pull request
Jul 7, 2026
…lback - Collapse getLeaderBoltAddress/getReplicaBoltAddresses into one getBoltRoutingTable() snapshot computed from a single getLeaderId() read, eliminating the writer/reader TOCTOU window and the CSV round-trip (Claude #1). - handleRoute: when HA is active but the leader is unknown, advertise this node as READ+ROUTE only (never WRITE), so a driver never writes to a follower during a leader-unknown window; true single-node still advertises all roles (Claude #3). - deriveBoltAddress: explicit null guard for raftAddress (Gemini). - Bolt5002RoutingTableIT.awaitRoutingTable: retry through transient connection errors during failover (Gemini).
3 tasks
robfrank
added a commit
that referenced
this pull request
Jul 7, 2026
- handleRoute now requires an authenticated (READY) session: ROUTE enumerates every peer's Bolt endpoint, so an unauthenticated caller (Bolt 5.1+ deferred-auth window, pre-LOGON) is refused. Adds routeBeforeLogonIsRejected regression (Claude #1). - BoltRoutingTable readers returned as List.copyOf to honor the immutability contract (Claude #2). - Reconcile design spec + plan with the final getBoltRoutingTable design, auth gate, and three-way fallback (Claude #4). Claude #3 (brief stale-leader window on a follower right after failover) is an accepted, self-healing behavior (driver recovers via routing TTL); no code change.
This was referenced Jul 7, 2026
hoogenbj
pushed a commit
to Locstat/arcadedb
that referenced
this pull request
Jul 7, 2026
…ack record state; tx-layer cleanups Issue ArcadeData#4940: on any commit2ndPhase failure the finally called reset(), which releases locks but skips the two record-restoration steps rollback() performs: reloading the records in modifiedRecordsCache to their committed content and resetting the identity of records created in the transaction (ArcadeData#4562). User-held MutableDocuments from the failed tx kept an optimistically-assigned RID pointing at a record that was never persisted; re-saving them in a retry was treated as an update of a missing record (which ArcadeData#4959's first fix now turns into a conflict, but before it was a silent lost insert). The finally now distinguishes durability: a failure BEFORE the transaction reaches the WAL calls rollback() (nothing durable exists - behave exactly like a phase-1 failure); a failure AFTER the WAL append keeps reset() (the tx is durable, recovery replays it, so the assigned RIDs remain valid and must not be reverted). This composes with PR ArcadeData#5053's point-of-no-return reordering, which adds fencing to the same post-append branch. Issue ArcadeData#4959 (low-severity transaction cleanups, all four items): - Silent dropped update: a deferred updatedRecords entry whose record was deleted by a concurrent transaction (page loaded after the delete committed, so the MVCC page-version check cannot see it) was logged at WARNING and skipped while the rest of the transaction committed - a silent partial commit. It now fails the whole transaction with a retryable ConcurrentModificationException. An in-tx delete removes the entry from updatedRecords (LocalBucket -> removeRecordFromCache) and never hits this path. - Futile duplicate-key retries: transaction() retried a deterministic DuplicatedKeyException through all TX_RETRIES attempts plus TX_RETRY_DELAY sleeps before surfacing it. Only a concurrency-induced duplicate can succeed on retry, and one retry disambiguates: the second identical failure is now rethrown immediately. - Requester identity: executeLockingFiles hardcoded Thread.currentThread() while file locks are keyed by requester (thread or session), so a thread acting for a session timed out (5s) on locks its own session already held. It now locks on behalf of the current transaction's requester (TransactionContext.getRequester(), widened to public); a same-requester re-acquisition is ALREADY_ACQUIRED and is not released on exit, only the locks actually acquired are. - Isolation contract: documented on Database.TRANSACTION_ISOLATION_LEVEL that page-level MVCC performs no read-set validation (write skew and phantoms possible under both levels, READ_COMMITTED may observe a concurrent multi-page commit partially, REPEATABLE_READ's per-tx page cache is unbounded), and pinned it with TransactionIsolationContractTest so any future contract change is a conscious one. Red-first evidence (all five fix-targeting tests fail on unfixed code): - Issue4940Phase2FailureRollbackTest.phase2FailureBeforeWalAppendResetsCreatedRecordIdentity: "identity must be reset after a pre-durability phase-2 failure - expected: null but was: ArcadeData#1:0" - Issue4940Phase2FailureRollbackTest.phase2FailureBeforeWalAppendReloadsModifiedRecords: "expected: 'committed' but was: 'uncommitted'" - Issue4959TransactionCleanupsTest.deferredUpdateOfConcurrentlyDeletedRecordFailsTheCommit: "Expecting code to raise a throwable" (the commit succeeded, silently dropping the update) - Issue4959TransactionCleanupsTest.deterministicDuplicatedKeyIsRetriedAtMostOnce: "expected: 2 but was: 10" - Issue4959TransactionCleanupsTest.executeLockingFilesUsesTheTransactionRequester: LockTimeoutException after the 5000ms timeout The two TransactionIsolationContractTest write-skew tests pass before and after (they pin existing, now-documented behavior). Tests: com.arcadedb.database.** (all 38 classes), ACIDTransactionTest, ExplicitLockingTransactionTest, LocalTransactionExplicitLockRetryTest, MVCCTest: 123 tests, 0 failures, 0 errors.
5 tasks
5 tasks
This was referenced Jul 8, 2026
Merged
robfrank
added a commit
that referenced
this pull request
Jul 10, 2026
…ag; doc JUL caveat Claude review #1: the core per-value converter toGrpcValue(Object, ProjectionConfig) still logged eagerly at its entry and in every projection-encoding branch, on the same read hot path. Guard all of them behind a single hoisted isDebugEnabled() boolean. Nit: hoist the debug flag above the per-property loops in convertToGrpcRecord and convertResultToGrpcRecord. Review #2: document the JUL-vs-debug-flag gating caveat.
This was referenced Jul 10, 2026
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
2 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.
add pre-commit configuration
add gh actions
add dependabot configuration