bootandy/archived-dust
1
0
Fork 0
mirror of https://github.com/bootandy/dust.git synced 2026-06-08 11:29:05 +03:00
Code Issues 21 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #260] ThreadPoolBuildError: Resource temporarily unavailable #109

New Issue
Closed
opened 2026-06-08 11:25:43 +03:00 by zhus · 1 comment
zhus commented 2026-06-08 11:25:43 +03:00
Owner
Copy Link
Copy Source

Originally created by @WesleyAC on GitHub (Aug 28, 2022).
Original GitHub issue: https://github.com/bootandy/dust/issues/260

When attempting to run the dust-v0.8.2-x86_64-unknown-linux release (both musl and gnu) on Debian 4.19.181-1, I get the following error:

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ThreadPoolBuildError { kind: IOError(Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }) }', src/main.rs:161:10

Running with --help works fine, but running with no arguments gets that error. RUST_BACKTRACE=full does not give any useful info, presumably since the debug symbols are stripped? I unfortunately don't have the time to dig further, sorry :(

In case it helps, here is a strace of a failed run: https://hack.wesleyac.com/dust-strace.txt

Originally created by @WesleyAC on GitHub (Aug 28, 2022). Original GitHub issue: https://github.com/bootandy/dust/issues/260 When attempting to run the `dust-v0.8.2-x86_64-unknown-linux` release (both musl and gnu) on `Debian 4.19.181-1`, I get the following error: ``` thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ThreadPoolBuildError { kind: IOError(Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }) }', src/main.rs:161:10 ``` Running with `--help` works fine, but running with no arguments gets that error. `RUST_BACKTRACE=full` does not give any useful info, presumably since the debug symbols are stripped? I unfortunately don't have the time to dig further, sorry :( In case it helps, here is a `strace` of a failed run: https://hack.wesleyac.com/dust-strace.txt
zhus closed this issue 2026-06-08 11:25:43 +03:00
zhus commented 2026-06-08 11:25:44 +03:00
Author
Owner
Copy Link
Copy Source

@WesleyAC commented on GitHub (Aug 28, 2022):

Oh, this is a dupe of #256, looks like. Sorry for not looking closely enough!

<!-- gh-comment-id:1229269708 --> @WesleyAC commented on GitHub (Aug 28, 2022): Oh, this is a dupe of #256, looks like. Sorry for not looking closely enough!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 windows help wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
zhus (Sergey Zhukov)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bootandy/archived-dust#109
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?