feat(lifecycle): manage own Stellar node for local/CI parity#24
Merged
feat(lifecycle): manage own Stellar node for local/CI parity#24
Conversation
The lifecycle test now starts its own Stellar quickstart container with --limits unlimited, ensuring identical behavior locally and in CI: - Contract events are captured in both environments - No dependency on an externally-running Stellar node - Dedicated port (8028) avoids collisions with other local-dev services config.ts simplified to just paths — network config is derived from the managed node. provider.ts now manages Stellar + PostgreSQL + provider-platform as a single infrastructure stack.
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.
Summary
--limits unlimitedcontract_initialized,provider_added,provider_removed) are verified in both local and CI — identical behaviorconfig.tssimplified to just paths; network config derived from the managed nodeRoot cause of event skip
The previous local runs used an external Stellar node (without
--limits unlimited), which didn't capture contract events. Additionally, the locale2e/wasms/had pre-event-emission WASMs. Both are now fixed — managed node ensures--limits unlimited, and local WASMs should be downloaded from the release (gh release download).Test plan
deno task lifecyclepasses locally with all 3 events verified (~200s including Stellar startup)