termux / termux/termux-api-package
Background jobs: Occasional hang
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1.7k
- Forks
- 523
- PR merge metrics
- No merged PRs in 30d
Description
Problem description
I have a number of scripts set to run via daily or twice-daily scheduled jobs, and at the end they send a notification if they've done any work. Sometimes this final notification step hangs (with the task remaining running until I manually go and kill it).
Steps to reproduce
This isn't consistently reproducible (happens maybe once a week/fortnight), but may be down to two scripts trying to send notifications simultaneously? I've tried the likes of termux-notification -c A & termux-notification -c B but can't immediately reproduce it.
They each end with something like:
[ $? -eq 0 ] && termux-notification -c "Backup complete"
Additional information
$ termux-info
Termux Variables:
TERMUX_APP_PACKAGE_MANAGER=apt
TERMUX_MAIN_PACKAGE_FORMAT=debian
TERMUX_VERSION=0.118.0
Packages CPU architecture:
aarch64
Subscribed repositories:
# sources.list
deb https://mirror.accum.se/mirror/termux.dev/termux-main stable main
Updatable packages:
All packages up to date
termux-tools version:
1.32.0
Android version:
12
Kernel build information:
Linux localhost 4.19.157-perf+ #1 SMP PREEMPT Sat Sep 17 00:13:28 CST 2022 aarch64 Android
Device manufacturer:
OnePlus
Device model:
EB2103
I'll try and grab a logcat next time it happens.
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
Start with the termux-notification command and the report's example of two notifications running simultaneously. Reproduce the occasional hang if possible and capture the promised logcat output when it occurs. Done means the cause of the notification hang is identified and the command no longer remains running indefinitely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, shell
- Domain
- cli, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100