troubleshoot the limits validation timing during start with local network #654
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.
the 'limits' config file path validation when' local' network was referring to PROTOCOL_VERSION before
start
had a chance to fully qualify it when not explicitly set from env or param, i.e. it will then set PROTOCOL_VERSION based on current core runtime default version reported after process start.resolves e2e test failures on stellar-rpc - https://github.com/stellar/stellar-rpc/actions/runs/12363207197/job/34504081784