Skip to content

Logically incorrect await statement could cause deadlock at some point #1305

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.

Sign up for GitHub

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

Jump to bottom
Closed
sdd opened this issue May 9, 2025 · 1 comment
Closed

Logically incorrect await statement could cause deadlock at some point #1305

sdd opened this issue May 9, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@sdd
Copy link
Contributor

sdd commented May 9, 2025

Apache Iceberg Rust version

None

Describe the bug

We're awaiting on a spawned task that should proceed concurrently rather than being awaited upon. This could cause deadlock at some point (I experienced this whilst working on #1011 and thought it best to backport the fix).

To Reproduce

No response

Expected behavior

No response

Willingness to contribute

I can contribute a fix for this bug independently
@sdd sdd added the bug Something isn't working label May 9, 2025
@sdd sdd mentioned this issue May 9, 2025
Closed
@sdd
Copy link
Contributor Author

sdd commented May 10, 2025

Turns out this was not the cause of deadlock. Closing

@sdd sdd closed this as completed May 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: incorrectly added statement could cause deadlock sdd/iceberg-rust
1 participant
@sdd