Vladimir Sementsov-Ogievskiy writes:
> On 04.04.25 17:13, Markus Armbruster wrote:
[...]
>> So, auto-finalize=true is silently ignored when another job in the same
>> transaction has auto-finalize=false?
>
> Yes, at least, it looks like so:
>
> static void job_completed_txn_success_locked(Job *
Vladimir Sementsov-Ogievskiy writes:
> On 04.04.25 09:20, Markus Armbruster wrote:
>> Vladimir Sementsov-Ogievskiy writes:
[...]
>>> +
>>> +``block-job-finalize`` (since 10.1)
>>> +''
>>> +
>>> +Use ``job-finalize`` instead.
>>> +
>>
>> block-job-finalize's doc
On 04.04.25 17:13, Markus Armbruster wrote:
Vladimir Sementsov-Ogievskiy writes:
On 04.04.25 09:20, Markus Armbruster wrote:
Vladimir Sementsov-Ogievskiy writes:
[...]
+
+``block-job-finalize`` (since 10.1)
+''
+
+Use ``job-finalize`` instead.
+
block-jo
On 04.04.25 09:20, Markus Armbruster wrote:
Vladimir Sementsov-Ogievskiy writes:
For change, pause, resume, complete, dismiss and finalize actions
corresponding job- and block-job commands are almost equal. The
difference is in find_block_job_locked() vs find_job_locked()
functions. What's dif
Vladimir Sementsov-Ogievskiy writes:
> For change, pause, resume, complete, dismiss and finalize actions
> corresponding job- and block-job commands are almost equal. The
> difference is in find_block_job_locked() vs find_job_locked()
> functions. What's different?
>
> 1. find_block_job_locked()
On Tue, Apr 01, 2025 at 18:57:30 +0300, Vladimir Sementsov-Ogievskiy wrote:
> For change, pause, resume, complete, dismiss and finalize actions
> corresponding job- and block-job commands are almost equal. The
> difference is in find_block_job_locked() vs find_job_locked()
> functions. What's diffe
For change, pause, resume, complete, dismiss and finalize actions
corresponding job- and block-job commands are almost equal. The
difference is in find_block_job_locked() vs find_job_locked()
functions. What's different?
1. find_block_job_locked() do check, is found job a block-job. This OK
whe
