How to use RetryableJobError?

[schiggi]

Any pointers how to correctly use RetryableJobError in order to retry a db trigger?

Atm, I set a DB trigger which calls an external endpoint.

def handle_db(record):
  result = session.put(
[...]
    )
    
  if result.json()['success'] == 1:
    [...]
  else:
    raise RetryableJobError('Must be retried later')

I am getting the following error

Traceback (most recent call last):
  File ".../odoo_base/odoo/tools/safe_eval.py", line 330, in safe_eval
    return unsafe_eval(c, globals_dict, locals_dict)
  File "", line 16, in <module>
  File "", line 13, in handle_db
odoo.addons.queue_job.exception.RetryableJobError: Must be retried later

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File ".../production/addons-14/queue_job/controllers/main.py", line 73, in runjob
    self._try_perform_job(env, job)
  File ".../production/addons-14/queue_job/controllers/main.py", line 32, in _try_perform_job
    job.perform()
  File ".../production/addons-14/queue_job/job.py", line 506, in perform
    self.result = self.func(*tuple(self.args), **self.kwargs)
  File ".../production/addons-14/sync/models/sync_task.py", line 135, in run
    result = self._eval(code, function, args, kwargs, eval_context)
  File ".../production/addons-14/sync/models/sync_task.py", line 164, in _eval
    safe_eval(
  File ".../odoo_base/odoo/tools/safe_eval.py", line 346, in safe_eval
    raise ValueError('%s: "%s" while evaluating\n%r' % (ustr(type(e)), ustr(e), expr))
ValueError: <class 'odoo.addons.queue_job.exception.RetryableJobError'>: "Must be retried later" while evaluating
[...]

[yelizariev]

It's another feature we documented, but didn't test 😬

So, built-in safe_eval transforms original exception into ValueError.
We need to implement opposite transformation somewhere here:

sync-addons/sync/models/sync_task.py

Line 135 in ab94a2f

result = self._eval(code, function, args, kwargs, eval_context)

[yelizariev]

I made an issue for this: #340

[schiggi]

Ah, ok. Thanks!

[schiggi]

Was this fixed/implemented in the newest "Magic" Sync v16?