Skip to content

Commit a437fe0

Browse files
committed
[BOT] post-merge updates
1 parent c449ef1 commit a437fe0

File tree

2 files changed

+2
-31
lines changed

2 files changed

+2
-31
lines changed

queue_job/README.rst

Lines changed: 1 addition & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Job Queue
1111
!! This file is generated by oca-gen-addon-readme !!
1212
!! changes will be overwritten. !!
1313
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
14-
!! source digest: sha256:58f9182440bb316576671959b69148ea5454958f9ae8db75bccd30c89012676d
14+
!! source digest: sha256:a07940f8fcee639bd0a0aa1c017dd2fb98875dae25db6586fcfde309b66f7654
1515
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
1616
1717
.. |badge1| image:: https://img.shields.io/badge/maturity-Mature-brightgreen.png
@@ -627,21 +627,6 @@ Known issues / Roadmap
627627
628628
- After creating a new database or installing ``queue_job`` on an
629629
existing database, Odoo must be restarted for the runner to detect it.
630-
- When Odoo shuts down normally, it waits for running jobs to finish.
631-
However, when the Odoo server crashes or is otherwise force-stopped,
632-
running jobs are interrupted while the runner has no chance to know
633-
they have been aborted. In such situations, jobs may remain in
634-
``started`` or ``enqueued`` state after the Odoo server is halted.
635-
Since the runner has no way to know if they are actually running or
636-
not, and does not know for sure if it is safe to restart the jobs, it
637-
does not attempt to restart them automatically. Such stale jobs
638-
therefore fill the running queue and prevent other jobs to start. You
639-
must therefore requeue them manually, either from the Jobs view, or by
640-
running the following SQL statement *before starting Odoo*:
641-
642-
.. code:: sql
643-
644-
update queue_job set state='pending' where state in ('started', 'enqueued')
645630
646631
Changelog
647632
=========

queue_job/static/description/index.html

Lines changed: 1 addition & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -372,7 +372,7 @@ <h1>Job Queue</h1>
372372
!! This file is generated by oca-gen-addon-readme !!
373373
!! changes will be overwritten. !!
374374
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
375-
!! source digest: sha256:58f9182440bb316576671959b69148ea5454958f9ae8db75bccd30c89012676d
375+
!! source digest: sha256:a07940f8fcee639bd0a0aa1c017dd2fb98875dae25db6586fcfde309b66f7654
376376
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->
377377
<p><a class="reference external image-reference" href="https://odoo-community.org/page/development-status"><img alt="Mature" src="https://img.shields.io/badge/maturity-Mature-brightgreen.png" /></a> <a class="reference external image-reference" href="http://www.gnu.org/licenses/lgpl-3.0-standalone.html"><img alt="License: LGPL-3" src="https://img.shields.io/badge/license-LGPL--3-blue.png" /></a> <a class="reference external image-reference" href="https://github.com/OCA/queue/tree/18.0/queue_job"><img alt="OCA/queue" src="https://img.shields.io/badge/github-OCA%2Fqueue-lightgray.png?logo=github" /></a> <a class="reference external image-reference" href="https://translation.odoo-community.org/projects/queue-18-0/queue-18-0-queue_job"><img alt="Translate me on Weblate" src="https://img.shields.io/badge/weblate-Translate%20me-F47D42.png" /></a> <a class="reference external image-reference" href="https://runboat.odoo-community.org/builds?repo=OCA/queue&amp;target_branch=18.0"><img alt="Try me on Runboat" src="https://img.shields.io/badge/runboat-Try%20me-875A7B.png" /></a></p>
378378
<p>This addon adds an integrated Job Queue to Odoo.</p>
@@ -928,21 +928,7 @@ <h2><a class="toc-backref" href="#toc-entry-11">Known issues / Roadmap</a></h2>
928928
<ul class="simple">
929929
<li>After creating a new database or installing <tt class="docutils literal">queue_job</tt> on an
930930
existing database, Odoo must be restarted for the runner to detect it.</li>
931-
<li>When Odoo shuts down normally, it waits for running jobs to finish.
932-
However, when the Odoo server crashes or is otherwise force-stopped,
933-
running jobs are interrupted while the runner has no chance to know
934-
they have been aborted. In such situations, jobs may remain in
935-
<tt class="docutils literal">started</tt> or <tt class="docutils literal">enqueued</tt> state after the Odoo server is halted.
936-
Since the runner has no way to know if they are actually running or
937-
not, and does not know for sure if it is safe to restart the jobs, it
938-
does not attempt to restart them automatically. Such stale jobs
939-
therefore fill the running queue and prevent other jobs to start. You
940-
must therefore requeue them manually, either from the Jobs view, or by
941-
running the following SQL statement <em>before starting Odoo</em>:</li>
942931
</ul>
943-
<pre class="code sql literal-block">
944-
<span class="k">update</span><span class="w"> </span><span class="n">queue_job</span><span class="w"> </span><span class="k">set</span><span class="w"> </span><span class="k">state</span><span class="o">=</span><span class="s1">'pending'</span><span class="w"> </span><span class="k">where</span><span class="w"> </span><span class="k">state</span><span class="w"> </span><span class="k">in</span><span class="w"> </span><span class="p">(</span><span class="s1">'started'</span><span class="p">,</span><span class="w"> </span><span class="s1">'enqueued'</span><span class="p">)</span>
945-
</pre>
946932
</div>
947933
<div class="section" id="changelog">
948934
<h2><a class="toc-backref" href="#toc-entry-12">Changelog</a></h2>

0 commit comments

Comments
 (0)