n0-computer / n0-computer/sendme
Unable to exit with ctrl-c
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
Running the latest version from source (529ebc1f9932af204822e2b7ea5af6e6dc44c882) on Linux.
achin@bbx in sendme on main is 📦 v0.14.0 🦀 took 8s
❯ cargo run -- send README.md
Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.36s
Running `target/debug/sendme send README.md`
imported file README.md, 1.60 KiB, hash 71b399b0882c06904b8fbbadc42f01e1727083f630fbbe52738232dc31651ee5
to get this data, use
sendme receive blobhashremovedforgithub
⠄ [00:00:18] waiting for requests
At this point, pressing ctrl-c doesn't exit sendme. Sending an explicit SIGINT doesn't kill the program, but a SIGTERM and SIGKILL will kill it
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with cargo run -- send README.md on Linux and observe the waiting state. Trace the entry point and signal-handling path for Ctrl-C and SIGINT, then verify that the command exits cleanly while SIGTERM and SIGKILL retain their reported behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100