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 #256] panicked at 'called Result::unwrap() #111

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

Originally created by @AminurAlam on GitHub (Aug 24, 2022).
Original GitHub issue: https://github.com/bootandy/dust/issues/256

$ export RUST_BACKTRACE=full

$ dust
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ThreadPoolBuildError { kind: IOError(Os { code: 11, kind: WouldBlock, message: "Try again" }) }', src/main.rs:161:10
stack backtrace:
   0: 0xe7c35e34 - <unknown>
   1: 0xe7bd64be - <unknown>
   2: 0xe7c1f300 - <unknown>
   3: 0xe7c36836 - <unknown>
   4: 0xe7c3709c - <unknown>
   5: 0xe7c36e2a - <unknown>
   6: 0xe7c36df6 - <unknown>
   7: 0xe7c36dcc - <unknown>
   8: 0xe7bd4e58 - <unknown>
   9: 0xe7bd9ea6 - <unknown>
  10: 0xe7ba09cc - <unknown>
  11: 0xe7b87540 - <unknown>
  12: 0xe7ba13b6 - <unknown>
  13: 0xe78be0b6 - <unknown>

$ dust -V
Dust 0.8.2

this started happening after the update
installed dust from my package manager on termux

Originally created by @AminurAlam on GitHub (Aug 24, 2022). Original GitHub issue: https://github.com/bootandy/dust/issues/256 ``` $ export RUST_BACKTRACE=full $ dust thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ThreadPoolBuildError { kind: IOError(Os { code: 11, kind: WouldBlock, message: "Try again" }) }', src/main.rs:161:10 stack backtrace: 0: 0xe7c35e34 - <unknown> 1: 0xe7bd64be - <unknown> 2: 0xe7c1f300 - <unknown> 3: 0xe7c36836 - <unknown> 4: 0xe7c3709c - <unknown> 5: 0xe7c36e2a - <unknown> 6: 0xe7c36df6 - <unknown> 7: 0xe7c36dcc - <unknown> 8: 0xe7bd4e58 - <unknown> 9: 0xe7bd9ea6 - <unknown> 10: 0xe7ba09cc - <unknown> 11: 0xe7b87540 - <unknown> 12: 0xe7ba13b6 - <unknown> 13: 0xe78be0b6 - <unknown> $ dust -V Dust 0.8.2 ``` this started happening after the update installed dust from my package manager on termux
zhus closed this issue 2026-06-08 11:25:44 +03:00
zhus commented 2026-06-08 11:25:44 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Aug 24, 2022):

:-(.

Thanks for the info.

From the line you've provided it seems Rayon is having trouble getting the threads.

I'm doing a naked unwrap on that line so I'll change it to a log to stderr and handle the error.

<!-- gh-comment-id:1226171350 --> @bootandy commented on GitHub (Aug 24, 2022): :-(. Thanks for the info. From the line you've provided it seems Rayon is having trouble getting the threads. I'm doing a naked unwrap on that line so I'll change it to a log to stderr and handle the error.
zhus commented 2026-06-08 11:25:44 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Aug 24, 2022):

https://github.com/rayon-rs/rayon/issues/694

<!-- gh-comment-id:1226176526 --> @bootandy commented on GitHub (Aug 24, 2022): https://github.com/rayon-rs/rayon/issues/694
zhus commented 2026-06-08 11:25:44 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Aug 24, 2022):

Does this always happen or only sometimes? Is this machine a single core, is it under heavy load? Or is there anything odd about the machine you are running on? Thanks, @AminurAlam

<!-- gh-comment-id:1226185509 --> @bootandy commented on GitHub (Aug 24, 2022): Does this always happen or only sometimes? Is this machine a single core, is it under heavy load? Or is there anything odd about the machine you are running on? Thanks, @AminurAlam
zhus commented 2026-06-08 11:25:44 +03:00
Author
Owner
Copy Link
Copy Source

@AminurAlam commented on GitHub (Aug 25, 2022):

this happens everytime, and i'm running on android 8.1 with 8 cores

<!-- gh-comment-id:1226795516 --> @AminurAlam commented on GitHub (Aug 25, 2022): this happens everytime, and i'm running on android 8.1 with 8 cores
zhus commented 2026-06-08 11:25:44 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Aug 26, 2022):

@AminurAlam does the code here fix it? https://github.com/bootandy/dust/pull/259 ?

<!-- gh-comment-id:1228697594 --> @bootandy commented on GitHub (Aug 26, 2022): @AminurAlam does the code here fix it? https://github.com/bootandy/dust/pull/259 ?
zhus commented 2026-06-08 11:25:44 +03:00
Author
Owner
Copy Link
Copy Source

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

I'm seeing this every time on a single-cpu DigitalOcean droplet. If you can send me a binary version of #259, I'd be happy to try it out, @bootandy.

<!-- gh-comment-id:1229270124 --> @WesleyAC commented on GitHub (Aug 28, 2022): I'm seeing this every time on a single-cpu DigitalOcean droplet. If you can send me a binary version of #259, I'd be happy to try it out, @bootandy.
zhus commented 2026-06-08 11:25:44 +03:00
Author
Owner
Copy Link
Copy Source

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

@AminurAlam does the code here fix it? #259 ?

nope still broken
20220829_011939

<!-- gh-comment-id:1229540652 --> @AminurAlam commented on GitHub (Aug 28, 2022): > @AminurAlam does the code here fix it? #259 ? nope still broken ![20220829_011939](https://user-images.githubusercontent.com/64137875/187091946-ae3bbaf5-0dbf-4776-a90f-b57044997538.jpg)
zhus commented 2026-06-08 11:25:44 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Aug 29, 2022):

This seems to be something to do with the stack-size.

I increased the stack-size to handle the case where a directory has a huge number of sub-directories. However small boxes can't allocate that much memory to stack-size and so it blows up.

<!-- gh-comment-id:1230089564 --> @bootandy commented on GitHub (Aug 29, 2022): This seems to be something to do with the stack-size. I increased the stack-size to handle the case where a directory has a huge number of sub-directories. However small boxes can't allocate that much memory to stack-size and so it blows up.
zhus commented 2026-06-08 11:25:44 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Aug 29, 2022):

https://github.com/rayon-rs/rayon/issues/900

<!-- gh-comment-id:1230574765 --> @bootandy commented on GitHub (Aug 29, 2022): https://github.com/rayon-rs/rayon/issues/900
zhus commented 2026-06-08 11:25:44 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Aug 29, 2022):

https://github.com/bootandy/dust/pull/261

This PR should fix it.

Branch: https://github.com/bootandy/dust/tree/fix_error_on_thread_creation5

<!-- gh-comment-id:1230575736 --> @bootandy commented on GitHub (Aug 29, 2022): https://github.com/bootandy/dust/pull/261 This PR should fix it. Branch: https://github.com/bootandy/dust/tree/fix_error_on_thread_creation5
zhus commented 2026-06-08 11:25:44 +03:00
Author
Owner
Copy Link
Copy Source

@AminurAlam commented on GitHub (Aug 31, 2022):

yep, #261 is working
thanks for fixing the issue

<!-- gh-comment-id:1232567964 --> @AminurAlam commented on GitHub (Aug 31, 2022): yep, #261 is working thanks for fixing the issue
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#111
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?