-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Can't interrupt bytes at with an infinite stream #13530
Copy link
Copy link
Closed
Labels
A:signal-cancelProblems with how executions react to signals or attempts at cancellation (CTRL-C)Problems with how executions react to signals or attempts at cancellation (CTRL-C)category:bugSomething isn't workingSomething isn't workingstatus:needs-triageAn issue that hasn't had any proper lookAn issue that hasn't had any proper look
Description
Describe the bug
It's impossible to interrupt an infinite binary stream, which is being sliced with bytes at.
How to reproduce
~> open /dev/urandom | into binary | bytes at ..10
^C^C^C^CExpected behavior
I expected interrupts to work. They function normally with first and last:
~> open /dev/urandom | into binary | first 10
Length: unknown (stream) | printable whitespace ascii_other non_ascii
00000000: c5 e1 dc 36 1c 4b f5 10 73 f8 ×××6•Kוs×
~> open /dev/urandom | into binary | last 10
^CError: × Operation interrupted
╭─[entry #5:1:1]
1 │ open /dev/urandom | into binary | last 10
· ──┬─
· ╰── This operation was interrupted
╰────Screenshots
No response
Configuration
| key | value |
|---|---|
| version | 0.96.0 |
| major | 0 |
| minor | 96 |
| patch | 0 |
| branch | |
| commit_hash | |
| build_os | linux-x86_64 |
| build_target | x86_64-alpine-linux-musl |
| rust_version | rustc 1.80.0 (051478957 2024-07-21) (Alpine Linux 1.80.0-r0) |
| cargo_version | cargo 1.80.0 (376290515 2024-07-16) |
| build_time | 2024-07-29 21:29:54 +00:00 |
| build_rust_channel | release |
| allocator | mimalloc |
| features | default, sqlite, system-clipboard, trash |
| installed_plugins | endecode 0.1.0 |
Additional context
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A:signal-cancelProblems with how executions react to signals or attempts at cancellation (CTRL-C)Problems with how executions react to signals or attempts at cancellation (CTRL-C)category:bugSomething isn't workingSomething isn't workingstatus:needs-triageAn issue that hasn't had any proper lookAn issue that hasn't had any proper look