Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
lmc-base-classes
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Jira
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
LOFAR2.0
lmc-base-classes
Commits
4286656b
Unverified
Commit
4286656b
authored
3 years ago
by
SKAJohanVenter
Browse files
Options
Downloads
Patches
Plain Diff
SAR-275
Updated docs
parent
57e83a95
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/ska_tango_base/base/task_queue_component_manager.py
+2
-2
2 additions, 2 deletions
src/ska_tango_base/base/task_queue_component_manager.py
with
2 additions
and
2 deletions
src/ska_tango_base/base/task_queue_component_manager.py
+
2
−
2
View file @
4286656b
...
@@ -58,7 +58,7 @@ Simple example:
...
@@ -58,7 +58,7 @@ Simple example:
* **is_aborting_event**: can be check periodically to determine whether
* **is_aborting_event**: can be check periodically to determine whether
the queue tasks have been aborted to gracefully complete the task in progress.
the queue tasks have been aborted to gracefully complete the task in progress.
The thread will stay active and
`
once is_aborting_event` has been unset,
The thread will stay active and once
`
is_aborting_event` has been unset,
new tasks will be fetched from the queue for execution.
new tasks will be fetched from the queue for execution.
.. code-block:: py
.. code-block:: py
...
@@ -104,7 +104,7 @@ QueueManager
...
@@ -104,7 +104,7 @@ QueueManager
The queue manager class manages the queue, workers and the update of properties.
The queue manager class manages the queue, workers and the update of properties.
The number of worker threads can be specified.
The number of worker threads can be specified.
In the case of no worker threads
, tasks that are enqueued will *not* be put on the queue,
When `num_workers` is 0
, tasks that are enqueued will *not* be put on the queue,
but will simply be executed and thus block until done. No worker threads are started in this case.
but will simply be executed and thus block until done. No worker threads are started in this case.
As tasks are taken off the queue and completes, the properties below will be updated. An optional callback
As tasks are taken off the queue and completes, the properties below will be updated. An optional callback
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment