Repository navigation
Closed
Description
Filed by the coordinator of epic #154, at the operator's request (2026-11-18). The 2026-11-18 05:47Z idle check found the new minors. This issue's body is the brief.
Why
- cannobserv tagged v0.49.0 and v0.50.0 at 2026-11-17T17:32Z and 21:44Z. Both are on the co-pypi index for
co-core,co-core-aioandco-core-sync. That was read unbounded asco-pypi-reader@, newest first0.50.0, 0.49.0, 0.48.2, at 05:47Z [measured]. - The repo rule is to pin the current minor (AGENTS.md, Environment & Tooling). The pins at
pyproject.toml:485-487read>=0.48.0,<0.49. - Two minors at once, in Catch up co-core 0.46 → 0.48 (0.48.2) #206's shape.
co-core-aioandco-core-sync0.50.0 requireco-core>=0.50,<0.51, so the three packages move together. 0.49 adds nothing we'd stop at.
What 0.49 and 0.50 change [stated by CHANGELOG.md at v0.50.0]
- 0.49.0 is a breaking minor,
outside co-core(corrected 2026-11-18 by the coordinator, from the implementer's review: itsInformationModel.sourceremoval is in co-core's ownpure/models/information.py, outside this closure [measured in the 0.48.2 wheel]).- It retires
cannobserv.ext.google_cloud_speech(#690), the legacycannobserv.model.transcript, andInformationModel.source(#673). - It adds
co_core.pure.util.audacity(#674). - It fixes a sync transport race (#714): a retry sleep that overran
CO_HTTP_DEADLINEnow raises a markedConnectTimeout, instead of returning a late response.
- It retires
- 0.50.0 is a breaking minor (#703). The storage framework moves from
cannobserv.storageintoco_core.pure.storageandco_core_sync.storage, and the legacy names are re-exported. It also:- removes
StorageConfig.from_toml; - makes
SourceRevisionVars.extrenderbinfor an absent media type; - adds the vocabulary Archiver and Observo share.
- removes
- Replicator uses none of it [traced]. No
cannobserv.*import exists here, and the closure diff below adds no module.
The closure diff, already run [measured 2026-11-18T06:0xZ by the coordinator]
The wheels were fetched with bash scripts/co-pypi.sh uv run --no-project python scripts/co_pypi_wheels.py --dest <dir> --version 0.48.2 --version 0.49.0 --version 0.50.0 co-core co-core-aio co-core-sync. Then scripts/co_core_closure_diff.py 0.48.2 0.50.0 --wheels <dir> printed:
58 files at 0.48.2, 58 at 0.50.0. 6 not identical:
- `version-only` co_core/__init__.py
- `docstrings-only` co_core/pure/models/changes.py
- `version-only` co_core_aio/__init__.py
- `version-only` co_core_sync/__init__.py
- `changed` co_core_sync/drivers/gdrive.py
- `changed` co_core_sync/drivers/transport.py
Requires-Dist:
- co_core: unchanged
- co_core_aio: removed `co-core<0.49,>=0.48`; added `co-core<0.51,>=0.50`
- co_core_sync: removed `co-core<0.49,>=0.48`; added `co-core<0.51,>=0.50`
Third-party imports (at 0.50.0): google, google_auth_oauthlib, googleapiclient, httpx, pydantic, redis, requests, urllib3 (unchanged).
Dynamic imports: the same two co-core-sync `drivers/` sites.
Both changed files were read with --diff [measured]:
drivers/gdrive.py: everyfiles()call now goes throughexecute_drive_request, which retries only methods inRETRY_METHODS. Replicator has no Drive writer:gdriveis refused asprovider_disabled(src/worker/aliases.py,src/worker/replicate.py), as on Catch up co-core 0.46 → 0.48 (0.48.2) #206.drivers/transport.py: this is 0.49.0's #714 fix. It adds_refuse_spent_attempton connect and request, and a pool mixin that drops the socket from the call budget.It's in the closure only because(Corrected 2026-11-18, from the implementer's review:co_core_sync.drivers/__init__re-exports its names.drivers/__init__.py:41imports it eagerly, so importing the worker loads it, as at 0.48.2 [measured by the implementer].) Nothing is mounted at import; a caller mounts it withmount_resilient_adapterorresilient_adapter.git grepfinds noresilient_adapter,mount_resilient_adapter,HttpDriver,DeadlineRetryorCO_HTTP_DEADLINEinsrc,scriptsortests(exit 1).GcsBlobStoretalks togoogle.cloud.storagedirectly (drivers/blobstore/gcs.py:61). So the behaviour fix has no call site here [traced].
changes.pyis docstrings-only.FetchPolicyState.generationis stillGeneration | None = None(changes.py:1974), so Fetch policy: retire the unordered path once nothing can publish a frame without a generation #163 B stays parked. Archiver is still on>=0.38,<0.39[measured].
No code change is expected. Re-run the diff from the wheels you lock, read both changed files yourself, and paste the report into the pin comment.
Steps
- List the index unbounded first (a lock probe at
<1). If anything newer than 0.50.0 has appeared, widen to it and say so here. - Move all three pins to
>=0.50.0,<0.51. The lock will take 0.50.0.- Nothing here depends on 0.50.0's additions, so the floor is the minor's
.0. - Run
uv lock --upgrade-packagefor the three packages throughbash scripts/co-pypi.sh uv …, in an isolated venv (Converge storage on the cluster content-addressed model #114; the worktree steps are in DEPENDENCIES.md). - Expect the lock diff to be the three
co-core*entries plus therequires-distmirror. If anything else moves, say why. 0.49 droppedcannobserv's own dependencies, and Replicator doesn't installcannobserv.
- Nothing here depends on 0.50.0's additions, so the floor is the minor's
- Update every literal of the current minor.
git grep -nE '0\.48|<0\.49|0\.49' -- ':!uv.lock' ':!docs/plans'ona072ba5lists them [measured]:AGENTS.md:29;docs/DEPENDENCIES.md:96(the pin), and:100("At 0.48.2 that's co-core-sync's two lazy__getattr__sites"; still two at 0.50.0);.socraticodecontextartifacts.json:166, which owes acodebase_updatein the same change (AGENTS.md, Code Exploration Notes);pyproject.toml:10-70, the pin comment: replace the 0.46.1 → 0.48.2 report with the 0.48.2 → 0.50.0 one;tests/test_dependency_index.py:63,72. Its bound moves to>=0.51and its docstring gets today's reading. It goes red on the lock move, which is expected: Catch up co-core 0.41 → 0.44 (three minors on the co-pypi index; widened from 0.42 at review) #184, Catch up co-core 0.44 → 0.45 (co-pypi index; closure diff version-only) #192, Catch up co-core 0.45 → 0.46 (co-pypi index; closure diff version-only) #199 and Catch up co-core 0.46 → 0.48 (0.48.2) #206 moved the same line.- Ignore
docs/reference/tailscale.md:72, which is a latency of 10.48 ms.
- Gates. Save the full output of each to files.
- The default suite. The baseline on
a072ba5is 2062 passed, 1 skipped, both clean and loaded [measured 2026-11-17 by the coordinator]. -m integrationon a scratch broker.-m browserin the delegated scope.-m gcs.tests/ci(44 ona072ba5), and the host deploy tests (tests/deploy tests/ci tests/test_deploy.py tests/test_load_env.py, run in the foreground; a detached run skipstest_deploy.py:1049).- ruff.
- CI green by job.
- The real-wheel closure test, with
REPLICATOR_TEST_CLOSURE_WHEELSfilled at 0.36.0 and 0.37.0 by the fetcher.
- The default suite. The baseline on
How it ships, since #208
.skills/merge_modeispr. Push the branch, open a PR, and merge it on GitHub with a merge commit (docs/DEPLOYMENT.md, "maintakes pull requests").- This issue concerns what production runs, so the PR body says
Refs #<this>, notCloses. The post-merge pass closes it after the deploy exits 0. - This is the first deploy of a GitHub merge commit.
deploy.sh's CI gate needs the merge commit's ownpushrun. Switch to shipping-work's pr merge mode (.skills/merge_mode) #208 measured that the run exists. Deploy the merge commit, not the branch tip. - The weekly measurement PR may be open beside yours (
context/weekly-measurement). Its files don't overlap with this change.
Done when
- The lock holds 0.50.0 ×3 from the index, with hashes, and
uv lock --checkis clean. - The deploy (via shipping-work's post-merge pass) has put the merge commit live, and on that build:
worker readyshowscapture,browser_fetchandpersistasenabled;- the release venv (
/srv/replicator/live/.venv) has 0.50.0 ×3; - the fetch-policy replay is clean;
- the worker runs as
replicatorwithNRestarts=0.
- The pin comment carries the closure-diff report.
The deploy restarts the worker.
Child of #154.
Metadata
Metadata
Assignees
Labels
No labels
Activity
gregoryfoster commentedon Nov 18, 2026
Brief review against
origin/main(pickup, 2026-11-18T13:1xZ)The brief holds. One wording correction and three notes; none of them changes the plan.
Base.
origin/mainis796186f, nota072ba5. The only change between them is #210's weekly measurement, which touches.skills/context-*alone [measured:git diff --stat]. So every line number in the brief still holds.Index, listed unbounded. At 13:13Z, a scratch lock with all three pins at
>=0.48.0,<1took 0.50.0 ×3 [measured]. Nothing newer than 0.50.0 is on the index, so the target stands.Correction:
drivers/transport.pyis loaded, not just re-exported. Importingsrc.worker.mainloadsco_core_sync.drivers.transport, along withdrivers.httpandrequests[measured, 0.50.0 venv]. That's becauseco_core_sync/drivers/__init__.py:41imports it eagerly, as it already did at 0.48.2. The brief's conclusion still holds: the #714 fix has no effect here.DeadlineRetry,TimeoutRetryHTTPAdapterand the_Deadline*Poolclasses. In the three 0.50.0 wheels, onlyresilient_adapterandmount_resilient_adapterconstruct them. Outsidedrivers/__init__'s re-export, nothing in those wheels calls either function [measured: grep of the extracted wheels].src,scriptsortestscalls them either [git grep, exit 1]._install_watched_poolscopies urllib3's mapping rather than mutating it.Per minor [measured, closure diff per step]:
changedfiles, plus threeversion-only.changes.py,docstrings-only, plus threeversion-only.Drive. Drive is settled by measurement, as on #206:
googleapiclientisn't installed (ModuleNotFoundError).co_core_sync.drivers.gdrive.RETRY_METHODSincludes GET and DELETE, sodelete,getandlistkeepDRIVE_NUM_RETRIES.create,updateandcopy(POST/PATCH) still get 0.Lock. The diff is as the brief predicted: three
versionlines, the threerequires-distspecifiers, and their url and hash lines. Each 0.50.0 wheel's sha256 appears inuv.lock.Not verified: "Archiver is still on
>=0.38,<0.39". It doesn't bear on this change.gregoryfoster commentedon Nov 18, 2026
Post-merge host steps (PR #213)
PR #213 is CI-green by job on
b464c83: lint, test, gcs and browser. It waits on the operator before the merge.Refs #211;closingIssuesReferencesis[].git -C /home/exedev/replicator pull --ff-only, then note the merge commit asM=$(git -C /home/exedev/replicator rev-parse --short=12 HEAD).pushCI run to go green:gh run list --repo CannObserv/replicator --commit $M.deploy.sh's gate needs that run, not the PR's. This is the first deploy of a GitHub merge commit (Switch to shipping-work's pr merge mode (.skills/merge_mode) #208)./home/exedev/replicator, runsetsid -w scripts/deploy.sh $M(shipping-work's post-merge pass). This restarts the worker. Rollback isscripts/deploy.sh <previous sha12>.readlink /srv/replicator/live→releases/$M.sudo journalctl -u replicator -o cat --since -10min | grep '"worker ready"'shows build$M, withcapture,browser_fetchandpersistallenabled./srv/replicator/live/.venv/bin/python -I -c 'import co_core, co_core_aio, co_core_sync as s; print(co_core.__version__, co_core_aio.__version__, s.__version__)'→0.50.0 0.50.0 0.50.0.sudo journalctl -u replicator --since -10min | grep -E 'replaying the fetch policy stream|fetch policy replay complete'. Both lines are there, withtracked_hostsmatching the previous boot's and no poison skip.systemctl show replicator -p User -p NRestarts→User=replicator,NRestarts=0.bash scripts/co-pypi.sh uv sync --frozenin/home/exedev/replicator. It's dev only: the release builds its own venv.codebase_updatefrom the main checkout, since this change edited.socraticodecontextartifacts.json(AGENTS.md, Code Exploration Notes). Running it from the worktree would embed nothing useful, because the index is keyed on the main checkout's path.git -C /home/exedev/replicator worktree remove --force ../replicator-211, then delete the branch locally and on origin.gregoryfoster commentedon Nov 18, 2026
Shipped: PR #213, merge commit
753ecb9, deployed>=0.50.0,<0.51, and the lock holds 0.50.0 ×3 from the index, with hashes. The lock diff is only the three entries and therequires-distmirror.changedfiles. The outside-the-closure paragraph comes from a whole-wheel diff.test_dependency_index.py, whose bound is now>=0.51.b464c83(the change) and753ecb9(the GitHub merge commit).Gates. All of these ran in the worktree, on an isolated venv:
796186f.-m integration: 57.-m browser: 31.-m gcs: 17.tests/ci: 44. The host deploy tests: 181, with 0 skipped.753ecb9's ownpushrun (44323517457): green on all four jobs,lint,test,gcsandbrowser.The deploy.
setsid -w scripts/deploy.sh 753ecb9609a0…exited 0. The previous live release was59fb24082f7e. On build753ecb9609a0[measured 14:25–14:27Z]:/srv/replicator/livepoints toreleases/753ecb9609a0.worker readyshowscapture,browser_fetchandpersistallenabled.co_core,co_core_aioandco_core_syncat 0.50.0 ×3.tracked_hosts10, the same as the 2026-11-15 boot, over 507 messages, with 0 stricter and no poison skip. The journal has no warnings or errors since the deploy.User=replicator, withNRestarts=0andActiveState=active.Host steps. The dev venv was re-synced from main (0.50.0), and
codebase_updateran from the main checkout. Thedependency-contractartifact is indexed with the new description.Known limits:
>=0.38,<0.39" was not re-measured. It doesn't bear on this change.For #163:
FetchPolicyState.generationis stillGeneration | None = Noneat 0.50.0 (co_core/pure/models/changes.py:1974), so B stays parked.For #154:
InformationModel.sourceremoval outside co-core. It also calleddrivers/transport.pyre-exported only, when the worker imports it at start.gregoryfoster commentedon Nov 18, 2026
Verified (coordinator, epic #154, 2026-11-18T14:5xZ)
I read all of this in this check-in [measured]:
796186f..753ecb9, which isb464c83plus PR #211 Catch up co-core 0.48 → 0.50 (0.50.0) #213's GitHub merge commit753ecb9(merged 14:22:17Z). The diff touches the pins and their comment, the lock (24 lines), AGENTS.md, DEPENDENCIES.md, the manifest andtest_dependency_index.py. The main checkout is clean at753ecb9. The worktree and both branches are gone.b464c83, and on753ecb9in its ownpushrun (44323517457), plusupdate-uv-graph./srv/replicator/livepoints toreleases/753ecb9609a0, and the previous release is59fb24082f7e.build-id.envreadsBUILD_ID=753ecb9609a0.replicator, withNRestarts=0.worker readyshows build753ecb9609a0. The replay read 507 messages and applied 10 hosts, 0 stricter.journalctl -t replicator-failureis empty, and no unit has failed. Root disk is at 60%.753ecb9, run by me in the foreground:test_co_core_closure_diff.py:433.ruff check,ruff format --checkanduv lock --checkare all clean. The dev venv reads 0.50.0.codebase_context_searchreturns DEPENDENCIES.md at>=0.50.0,<0.51and the new pin comment.Corrections accepted, and fixed in place in the issue body (both of them mine):
InformationModel.sourceis in co-core's ownpure/models/information.py. I confirmed that in the 0.48.2 wheel. It is outside this closure, so the conclusion stands.drivers/transport.pyis loaded at worker import, not only re-exported. The #714 fix still has no call site here.Carried to the epic:
generationis still optional at 0.50.0).pr-mode run opened PR chore: update skills submodules #212 at 13:13Z: only thegregoryfoster-skillspointer, CI green by job, andmaindidn't move. That discharges its verification-debt row.Nothing is owed.