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

[Consensus] start service with unspecified IP #16658

Merged
merged 6 commits into from
Mar 14, 2024
Merged

[Consensus] start service with unspecified IP #16658

merged 6 commits into from
Mar 14, 2024

Conversation

mwtian
Copy link
Contributor

@mwtian mwtian commented Mar 14, 2024

Description

Receive the network service IP from the host, instead of specifying it when starting the service. Among other reasons, this helps with binding to the same IP and port after stopping the service in sim tests.

Also,

  • Allow the Mysticeti workflow to run from a branch or commit.
  • Use warn for not finding archive reader.
  • Avoid spurious lint issues when running simtest.

Test Plan

CI
https://github.com/MystenLabs/sui/actions/runs/8276357969/job/22644782845


If your changes are not user-facing and do not break anything, you can skip the following section. Otherwise, please briefly describe what has changed under the Release Notes section.

Type of Change (Check all that apply)

  • protocol change
  • user-visible impact
  • breaking change for a client SDKs
  • breaking change for FNs (FN binary must upgrade)
  • breaking change for validators or node operators (must upgrade binaries)
  • breaking change for on-chain data layout
  • necessitate either a data wipe or data migration

Release notes

Copy link

vercel bot commented Mar 14, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
explorer ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 14, 2024 6:20am
multisig-toolkit ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 14, 2024 6:20am
mysten-ui ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 14, 2024 6:20am
sui-core ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 14, 2024 6:20am
sui-kiosk ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 14, 2024 6:20am
sui-typescript-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 14, 2024 6:20am

@mwtian
Copy link
Contributor Author

mwtian commented Mar 14, 2024

cc @sadhansood for the logging level change in crates/sui-network/src/state_sync/mod.rs.

@mwtian mwtian enabled auto-merge (squash) March 14, 2024 06:34
@mwtian mwtian disabled auto-merge March 14, 2024 06:35
@mwtian mwtian merged commit f5ee962 into main Mar 14, 2024
43 of 44 checks passed
@mwtian mwtian deleted the consensus-service branch March 14, 2024 06:47
@akichidis
Copy link
Contributor

Nice!

tx-tomcat pushed a commit to tx-tomcat/sui-network that referenced this pull request May 30, 2024
## Description 

Receive the network service IP from the host, instead of specifying it
when starting the service. Among other reasons, this helps with binding
to the same IP and port after stopping the service in sim tests.

Also,
- Allow the Mysticeti workflow to run from a branch or commit.
- Use `warn` for not finding archive reader.
- Avoid spurious lint issues when running simtest.

## Test Plan 

CI

https://github.com/MystenLabs/sui/actions/runs/8276357969/job/22644782845

---
If your changes are not user-facing and do not break anything, you can
skip the following section. Otherwise, please briefly describe what has
changed under the Release Notes section.

### Type of Change (Check all that apply)

- [ ] protocol change
- [ ] user-visible impact
- [ ] breaking change for a client SDKs
- [ ] breaking change for FNs (FN binary must upgrade)
- [ ] breaking change for validators or node operators (must upgrade
binaries)
- [ ] breaking change for on-chain data layout
- [ ] necessitate either a data wipe or data migration

### Release notes
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.

3 participants