Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default to cores max protocol version in local mode when no default specified #603

Merged
merged 1 commit into from
Apr 29, 2024

Conversation

leighmcculloch
Copy link
Member

@leighmcculloch leighmcculloch commented Apr 29, 2024

What

Default to cores max protocol version in local mode when no default specified.

Why

In #594 I removed the automatic default and replaced it with an explicit default because nearing protocol releases we have versions of software being updated in quickstart without coordination, which is good, and having local always startup a network based on core's max supported protocol version meant that in some cases it would start networks that the image as a whole was not ready to run.

When I removed the automatic default I made it so that an explicit default had to be set. That requirement was somewhat unnecessary. For most uses of quickstart simply using what core thinks the version should be is fine, and it's those edge cases where we need it specified.

I'd like to keep it as so so that in other uses of quickstart, like the system-tests, don't need to also coordinate the default version in their default configuration and can rely on quickstart figuring it out for the common case.

Related:

start Show resolved Hide resolved
@leighmcculloch leighmcculloch merged commit 5bb379c into master Apr 29, 2024
158 checks passed
@leighmcculloch leighmcculloch deleted the add-back-default-protocol branch April 29, 2024 21:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants