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

Better test coverage for consensus adapter max_in_flight behavior #21569

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mystenmark
Copy link
Contributor

Attempt to find bugs in which pending consensus transactions are never marked as processed.

@mystenmark mystenmark requested a review from a team as a code owner March 21, 2025 18:16
@mystenmark mystenmark requested review from andll, aschran and mwtian March 21, 2025 18:16
Copy link

vercel bot commented Mar 21, 2025

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

Name Status Preview Comments Updated (UTC)
sui-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 21, 2025 8:22pm
2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
multisig-toolkit ⬜️ Ignored (Inspect) Visit Preview Mar 21, 2025 8:22pm
sui-kiosk ⬜️ Ignored (Inspect) Visit Preview Mar 21, 2025 8:22pm

@mystenmark mystenmark temporarily deployed to sui-typescript-aws-kms-test-env March 21, 2025 18:16 — with GitHub Actions Inactive
Copy link
Contributor

@andll andll left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's hard to predict if this will have any false positives but we can go with trial and error approach

@@ -691,6 +692,31 @@ impl ConsensusAdapter {
.ok(); // result here indicates if epoch ended earlier, we don't care about it
}

async fn acquire_submit_semaphore(&self) -> SemaphorePermit {
loop {
match tokio::time::timeout(Duration::from_secs(5), async {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This (5s) seems inconsistent with the error message later (30s). I think it is safer to use 30s which should still be low enough in tests.

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.

4 participants