bundle: own lifecycle and update Anytype v0.12 - #75
Merged
Conversation
Validate MongoDB URIs with the driver without rewriting operator-owned values. Derive only the consensus URI owned by the bundle. Cover the historical local and S3 shapes that share bundle format 1, including compatibility defaults for region and storage limits.
Use one root cancellation path for startup, service failure, and embedded process exits. Shut services down in reverse order, signal MongoDB and Redis together, and always reap owned children. Keep the application watchdog and Compose grace periods under one shutdown policy while preserving startup and cleanup failures.
Keep tests for repository-owned storage and container boundaries while removing duplicate checks of dependency behavior. Exercise S3 request signing and the complete all-in-one shutdown path instead of treating startup markers as sufficient proof.
Use Go 1.26.4 consistently across modules, containers, CI, and developer documentation. Give one Linux runner the race-enabled behavior gate while retaining representative portability, release-build, Docker, and Nix coverage.
Describe the repository-owned lifecycle, configuration, storage, and verification boundaries for contributors and agents. Give operators the matching container stop timeout and require a completed clean shutdown before backup. Limit the compatibility promise to bundle configuration format 1.
Update the Anytype node modules to compatibility timestamp 1784291832 and register the coordinator invite store required by the v0.12 bootstrap. Keep the wrapper aligned with upstream component ownership by starting shared transports last and retaining the composite filenode store lifecycle contract. Make Badger acknowledgements durable, propagate deletion failures, and join its GC goroutine before releasing the database. Preserve exact operator cancellation during MongoDB initialization and validate MongoDB, Redis, and S3 inputs with the same parsers used at runtime. Restore a full-bundle custom-region S3 integration check and document clean backup and shutdown bounds. Refresh Go, Nix, Compose, and maintenance metadata for Go 1.26.4. Closes #74
Merging this branch will increase overall coverage
Coverage by fileChanged files (no unit tests)
Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code. Changed unit test files
|
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
1 participant
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.
1784291832, register the v0.12 coordinator invite store, retain upstream S3, and harden the bundle-owned Badger store's durability and goroutine shutdown.This also aligns Go, Nix, Docker, CI, and contributor documentation with Go 1.26.4 and documents clean shutdown and backup behavior.
Closes #74
GPT5.6 Sol used