reuse/api
9
3
Fork 2
Code Issues 32 Pull Requests 1 Activity

Scheduler should be a singleton #151

New Issue
Open
opened 2026-01-14 16:41:32 +00:00 by fkobi · 0 comments
fkobi commented 2026-01-14 16:41:32 +00:00
Owner
Copy Link

The app should have one task queue, one set of threads and so on.
The simplest way to achieve that is to ensure that scheduler is a singleton.

The app should have one task queue, one set of threads and so on. The simplest way to achieve that is to ensure that scheduler is a singleton.
fkobi added the bughelp wanted
component
backend
prio
high
1.0 labels 2026-01-14 16:41:32 +00:00
fkobi changed title from Scheduler should be a singleton to `Scheduler` should be a singleton 2026-01-26 18:10:43 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
1.0
Problems that do not concern the 2.0 rewrite, probably should be ignored
component
backend
Issues concerning the backend (logic connecting frontend with the database)
component
database
Issues concerning the database
component
docs
Issues regarding documentation
component
frontend
Issues concerning the frontend
prio
high
High priority
prio
low
Low priority
prio
maybe
Lowest priority
prio
mid
Medium priority
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label 1.0
component
backend
prio
high
 bug help wanted
Milestone
No items
No Milestone
Assignees
Clear assignees
carmenbianca fkobi florian.vuillemot floriansnow git-robot linus max.mehl nico.rikken reinhard renovate-bot tobiasd
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: reuse/api#151
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?