Repository navigation
Fixed issue with replication and schema changes - #108
Merged
Merged
Conversation
mergify Bot
added a commit
that referenced
this pull request
Dec 8, 2025
…2.8.32 to 2.9.4 in /studio [skip ci] Bumps [baseline-browser-mapping](https://github.com/web-platform-dx/baseline-browser-mapping) from 2.8.32 to 2.9.4. Release notes *Sourced from [baseline-browser-mapping's releases](https://github.com/web-platform-dx/baseline-browser-mapping/releases).* > v2.9.3 - remove `process.loadEnvFile()` > --------------------------------------- > > What's Changed > -------------- > > * Remove process.loadEnfFile() from main script by [`@tonypconway`](https://github.com/tonypconway) in [web-platform-dx/baseline-browser-mapping#112](https://redirect.github.com/web-platform-dx/baseline-browser-mapping/pull/112) > > **Full Changelog**: <web-platform-dx/baseline-browser-mapping@v2.9.2...v2.9.3> > > v2.9.2 - fix browser support bug > -------------------------------- > > What's Changed > -------------- > > * Fix browser support bug by [`@tonypconway`](https://github.com/tonypconway) in [web-platform-dx/baseline-browser-mapping#111](https://redirect.github.com/web-platform-dx/baseline-browser-mapping/pull/111) > **Full Changelog**: <web-platform-dx/baseline-browser-mapping@v2.9.1...v2.9.2> > > v2.9.0 - Reduce frequency of data staleness warnings > ---------------------------------------------------- > > This version introduces a number of changes to data staleness warnings in response to [#105](https://redirect.github.com/web-platform-dx/baseline-browser-mapping/issues/105) , [#107](https://redirect.github.com/web-platform-dx/baseline-browser-mapping/issues/107) and [#109](https://redirect.github.com/web-platform-dx/baseline-browser-mapping/issues/109) > > * Data staleness warnings are now only shown if the `getCompatibleVersions()` or `getAllVersions()` functions are called - previously they were shown whenever the module was loaded, which meant many `browserslist` consumers were seeing the warning despite not targeting Baseline, especially those who were consuming `browserslist` in a pre-compiled format via `next.js`. > * Adds new conditions for these warnings to be displayed which should only warn users for whom data freshness is critical: > + The feature cut off data must be within the last two months, i.e. `widelyAvailableOnDate: today + >2 years and 4 months` or `newly available` in a `browserslist` query. > + The module data must be more than 2 months old. > * Introduces suppression options for these warning via the `options` objects and environment variables: > + Adds a new `suppressWarnings` boolean to the `getCompatibleVersions()` and `getAllVersions()` > + Respects the existing [`BROWSERSLIST_IGNORE_OLD_DATA`](browserslist/browserslist@0ae7155) environment variable. > + Respects a new `BASELINE_BROWSER_MAPPING_IGNORE_OLD_DATA` environment variable. > * Adds [explanatory text to the README](https://github.com/web-platform-dx/baseline-browser-mapping?tab=readme-ov-file#keeping-baseline-browser-mapping-up-to-date) for how to avoid such warnings when reproducible builds are a requirement. > * Change warning text to be package manager agnostic and mention the possibility of pre-compiled data. Commits * [`73c8429`](web-platform-dx/baseline-browser-mapping@73c8429) Patch to 2.9.4 because browser or feature data changed * [`079e1d9`](web-platform-dx/baseline-browser-mapping@079e1d9) Browser or feature data changed * [`3553f31`](web-platform-dx/baseline-browser-mapping@3553f31) Remove process.loadEnfFile() from main script ([#112](https://redirect.github.com/web-platform-dx/baseline-browser-mapping/issues/112)) * [`5972583`](web-platform-dx/baseline-browser-mapping@5972583) Bump version from 2.9.1 to 2.9.2 * [`0ab0d6f`](web-platform-dx/baseline-browser-mapping@0ab0d6f) Fix browser support bug ([#111](https://redirect.github.com/web-platform-dx/baseline-browser-mapping/issues/111)) * [`b326475`](web-platform-dx/baseline-browser-mapping@b326475) Patch to 2.9.1 because browser or feature data changed * [`9ee8cbe`](web-platform-dx/baseline-browser-mapping@9ee8cbe) Browser or feature data changed * [`226fd01`](web-platform-dx/baseline-browser-mapping@226fd01) Reduce frequency of data staleness warnings ([#108](https://redirect.github.com/web-platform-dx/baseline-browser-mapping/issues/108)) * [`6d43e5a`](web-platform-dx/baseline-browser-mapping@6d43e5a) Updating static site * See full diff in [compare view](web-platform-dx/baseline-browser-mapping@v2.8.32...v2.9.4) [](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
Fixed issue with replication and schema changes
tae898
referenced
this pull request
in humemai/arcadedb-embedded-python
Jun 28, 2026
…2.8.32 to 2.9.4 in /studio [skip ci] Bumps [baseline-browser-mapping](https://github.com/web-platform-dx/baseline-browser-mapping) from 2.8.32 to 2.9.4. Release notes *Sourced from [baseline-browser-mapping's releases](https://github.com/web-platform-dx/baseline-browser-mapping/releases).* > v2.9.3 - remove `process.loadEnvFile()` > --------------------------------------- > > What's Changed > -------------- > > * Remove process.loadEnfFile() from main script by [`@tonypconway`](https://github.com/tonypconway) in [web-platform-dx/baseline-browser-mapping#112](https://redirect.github.com/web-platform-dx/baseline-browser-mapping/pull/112) > > **Full Changelog**: <web-platform-dx/baseline-browser-mapping@v2.9.2...v2.9.3> > > v2.9.2 - fix browser support bug > -------------------------------- > > What's Changed > -------------- > > * Fix browser support bug by [`@tonypconway`](https://github.com/tonypconway) in [web-platform-dx/baseline-browser-mapping#111](https://redirect.github.com/web-platform-dx/baseline-browser-mapping/pull/111) > **Full Changelog**: <web-platform-dx/baseline-browser-mapping@v2.9.1...v2.9.2> > > v2.9.0 - Reduce frequency of data staleness warnings > ---------------------------------------------------- > > This version introduces a number of changes to data staleness warnings in response to [#105](https://redirect.github.com/web-platform-dx/baseline-browser-mapping/issues/105) , [#107](https://redirect.github.com/web-platform-dx/baseline-browser-mapping/issues/107) and [#109](https://redirect.github.com/web-platform-dx/baseline-browser-mapping/issues/109) > > * Data staleness warnings are now only shown if the `getCompatibleVersions()` or `getAllVersions()` functions are called - previously they were shown whenever the module was loaded, which meant many `browserslist` consumers were seeing the warning despite not targeting Baseline, especially those who were consuming `browserslist` in a pre-compiled format via `next.js`. > * Adds new conditions for these warnings to be displayed which should only warn users for whom data freshness is critical: > + The feature cut off data must be within the last two months, i.e. `widelyAvailableOnDate: today + >2 years and 4 months` or `newly available` in a `browserslist` query. > + The module data must be more than 2 months old. > * Introduces suppression options for these warning via the `options` objects and environment variables: > + Adds a new `suppressWarnings` boolean to the `getCompatibleVersions()` and `getAllVersions()` > + Respects the existing [`BROWSERSLIST_IGNORE_OLD_DATA`](browserslist/browserslist@0ae7155) environment variable. > + Respects a new `BASELINE_BROWSER_MAPPING_IGNORE_OLD_DATA` environment variable. > * Adds [explanatory text to the README](https://github.com/web-platform-dx/baseline-browser-mapping?tab=readme-ov-file#keeping-baseline-browser-mapping-up-to-date) for how to avoid such warnings when reproducible builds are a requirement. > * Change warning text to be package manager agnostic and mention the possibility of pre-compiled data. Commits * [`73c8429`](web-platform-dx/baseline-browser-mapping@73c8429) Patch to 2.9.4 because browser or feature data changed * [`079e1d9`](web-platform-dx/baseline-browser-mapping@079e1d9) Browser or feature data changed * [`3553f31`](web-platform-dx/baseline-browser-mapping@3553f31) Remove process.loadEnfFile() from main script ([#112](https://redirect.github.com/web-platform-dx/baseline-browser-mapping/issues/112)) * [`5972583`](web-platform-dx/baseline-browser-mapping@5972583) Bump version from 2.9.1 to 2.9.2 * [`0ab0d6f`](web-platform-dx/baseline-browser-mapping@0ab0d6f) Fix browser support bug ([#111](https://redirect.github.com/web-platform-dx/baseline-browser-mapping/issues/111)) * [`b326475`](web-platform-dx/baseline-browser-mapping@b326475) Patch to 2.9.1 because browser or feature data changed * [`9ee8cbe`](web-platform-dx/baseline-browser-mapping@9ee8cbe) Browser or feature data changed * [`226fd01`](web-platform-dx/baseline-browser-mapping@226fd01) Reduce frequency of data staleness warnings ([#108](https://redirect.github.com/web-platform-dx/baseline-browser-mapping/issues/108)) * [`6d43e5a`](web-platform-dx/baseline-browser-mapping@6d43e5a) Updating static site * See full diff in [compare view](web-platform-dx/baseline-browser-mapping@v2.8.32...v2.9.4) [](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
Sep 19, 2026
…no longer blocks a size #108 amends #103b and #103c. #103c's "one size by default" was the wrong default: on a 10.6x corpus the five graph queries moved 11.1x, 11.2x, 8.9x, 2.4x and 1.0x, and one point cannot tell those apart. The important half is what it repairs. #103b makes a raise REPLACE a tier, so a table switches only when every engine has a row at the new size. In September's extension one SurrealDB embedded envelope failure held back two tables on which nine and three other engines had already measured. Under #108 the large size is a row group, not a replacement, and an engine absent from it is a declared outcome under #103g -- censored, envelope failure, or failed inside budget -- which is the censored-observation standard we already hold ourselves to and strictly more informative than withholding good rows. Those September rows do not carry over: rule 3 gives one engine commit per table, so October re-measures them at October's pin. Also records #106a: a budget derived from the survivors of a looser bound is withheld, because it measures its own selection. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JB6Hg77dQVqABoTJmiUnV2
tae898
referenced
this pull request
in humemai/arcadedb-embedded-python
Sep 19, 2026
Neither branch could run the October campaign alone. october-instrument had the whole per-query budget apparatus (budget_lookup, budgets, derive_budgets, abandon, per-query censoring in l1_tpc/l2_graph/l4_tsbs), the expanded query sets (14 graph analytics queries with LSQB's nine, 5 document, 6 time series), the durability axis, the answer digests and equivalence_check, the MongoDB and MongoDB-Search arms, and the October re-pin. main had the raised tiers with their memory and heap tables, land_stage's commit verification, page_check's coverage and condition rules, the streamed TPC-H line-item loader that tpch10 needs, and the #108 sizes. This is both halves. Resolved by union except where the two sides said the same thing twice. The judgement calls, each because the merged tree makes one side's statement false: * The cold/warm, GAV-build, PostgreSQL-memory, last-point and Milvus-segment condition sentences take october's, because october GENERATES them from the rows (_gen, _cold_note, _gav_build_note, _pg_memory_note, _l4_lastpoint_note) where main typed them by hand. main's de-numbering of the same sentences is carried by the generators. * FAIRNESS F6's DuckDB row takes october's: every lane in this tree now sets PRAGMA threads from sched_getaffinity, so main's "l1_tpc, l3d and l4 still run oversubscribed" is no longer true of it. * build_images.sh and every server_image digest take october's: they are the October re-pin of 2026-09-19, and COMPARATORS.md's re-pin table is its record. No engine was dropped; each moved to a newer digest. * PROTOCOL's relaxed-class summary row becomes october's six per-engine rows. * FAIRNESS's close-cost rule is renumbered F11 -> F13, because october's F11 and F12 are the two rules above it. fairness_check still prints its header as F11; that mismatch predates this merge and is now written down. Two duplicate dict keys were created by the union itself and removed: export_web.DISPLAY and make_paper_tables.NAMES each bound memgraph_graph, falkordb_graph and one more key twice, same value both times. That is the defect ef6acf2 fixed in runner.TIMEOUT_BY_SCALE a day ago; every dict literal in every changed file is now checked for it. _withheld_recall_notes (main) now goes through _gen (october). Without it the sentence is unregistered prose on an October table, which page_check refuses outright, and its two numbers read as UNPINNED on a September one. PAGE-SPEC's "disagreeing answers" row loses its OCTOBER ONLY marker: after this merge refresh_web_page.GATES is four gates on main, equivalence_check included. Verified by running: compile() clean on all 36 changed .py; no duplicate key in any dict literal; TIMEOUT_BY_SCALE/MEM_BY_SCALE/HEAP_BY_SCALE carry all 19 tiers with tpch10 2h, sf1full 2h, ts1000 3h, e2_500k 2h; OLAP_QUERIES is 14; NOT_PRINTED is 25 (pattern, reason) tuples; the four gates import and run; queue_lint clean. End to end on the laptop, the graph lane at a capped LDBC SF1 slice (300 persons, 77,605 message vertices, 131,402 message edges), ArcadeDB embedded and LadybugDB one at a time: all 14 analytics digests AGREE across the two engines, every query on both rows carries <q>_budget_s and <q>_budget_source (6 measured from budgets.py's sf1full entries, 22 on the lane default), and nothing was abandoned or censored. l3d_dense, l3_sparse, e2_hybrid and l5_lifecycle still have no budget mechanism on either side. Left alone; it is a known gap, not this merge's. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JB6Hg77dQVqABoTJmiUnV2
tae898
referenced
this pull request
in humemai/arcadedb-embedded-python
Sep 21, 2026
DECISIONS #108 (2026-09-19, the user: "sounds good") makes every table carry two sizes, the large one a ROW GROUP rather than a replacement. PAPER_SCALES never learned it. It still listed one tier per lane for four lanes, under a comment implementing #103b's retired rule that a raise replaces a tier once every engine has landed. Measured, not hypothetical: 78 October rows currently reach no table, no figure and no gate. l4/ts1000 56 rows, already paid for by qOC e2/e2_500k 21 rows and climbing, while qOD spends ~16 h on it l2/sf1full 1 row, with qOB2's full set due l1tpc/tpch10 joins them when qOE runs That is the same silent discard the comment above PAPER_SCALES already describes for LANES -- "117 lifecycle rows worth ~18 h of bench time ... every row was discarded here before any table, figure or gate saw it" -- happening to SIZES, and nothing would have said so until the campaign ended and the tables came up one size short. The rendering was never the problem: l3d has carried small+deep10m and l3s three tiers all along, so multi-size tables work. These four lanes were just never added. SEPTEMBER MUST NOT GAIN THEM, and does not. Its store holds tpch10 and sf1full rows from the qEA/qEB extension, measured at September's pin under the replacement rule, and a full switch never happened. Adding the tiers unconditionally would change the live page without a decision -- the trap F72 documented. OCTOBER_LARGE_SCALES is applied only when the instrument says October, and September's payload regenerates byte-identical with all six gates clean. export_web gets the one split this needs. Graph analytics is the single one-size table (#108: "SF10 full network is not feasible"), so l2olap moves to {sf1full} under October and keeps September's two projection tiers; and the INTERACTIVE table now names {sf1, sf10} instead of inheriting the lane's, because it draws from the same lane and would otherwise print the persons-and-KNOWS projection beside the full network -- two corpora in one table, which is PAGE-SPEC rule 4's whole subject. After: 0 October rows dropped, from 78. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JB6Hg77dQVqABoTJmiUnV2
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.
Fixed issue on replication reported by Jim