Terminal hangs for like 10 seconds
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- cli
Research direction
Start by running notify --title "Doing stuff" --message "Hang on" and compare its behavior with v1.1.2 or earlier. Trace why the command waits about 10 seconds and prints timeout; done means the notification is sent while the terminal remains available for other tasks.
Written by the indexing model from the issue text.
Description
Was hoping to send a notification, and carry on with some other tasks, but found that this hangs in the terminal. It used to work how I was hoping from v1.1.2 and earlier though, so I'll use that for now.
Input:
notify --title "Doing stuff" --message "Hang on"
Output after 10 seconds or so:
timeout
- Dominant language
- JavaScript
- Stars
- 153
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from mikaelbr/node-notifier-cli
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Add --wait optionOpen
Difficulty 3/5 1-2 days Newbie friendliness 20/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
mikaelbr/node-notifier-cli#22 · 1 comment · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
mikaelbr/node-notifier-cli#9 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in mikaelbr/node-notifier-cli
Similar issues
-
channels:add check:passed
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 9 days
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/gh-aw-workshop#4496 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
swc-project/swc#12516 ·
Maintainers usually reply within 1 day
-
Opening Files on a demo drive logs you outPossibly taken @RChang06 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
feature-request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
omegaup/omegaup#10323 · 1 comment ·
Maintainers usually reply within 5 days