runbot/forwardport
Xavier Morel b177361f20 [IMP] forwardport: locking during creation of fw batch
Not sure why I didn't think about it previously (in #357), but it
would make sense for the entire batch creation to be atomic and thus
under the same lock.

The commit during forward porting also makes a lot less sense: it was
a failed early attempt at resolving the problem by hoping we'd win the
race with the webhook (commit before the webhook hit). By locking the
PRs table to update, we actually resolved it.

But since all that happens then is a few updates and then a commit by
the cron itself (it commits per batch), it's probably good enough to
leave the entire thing under the same lock. This means we lock out
other interactions a bit longer, but since the span is still just the
forward port of a single batch it should not be too much of an issue
outside of post-freeze recovery thingie.
2024-05-16 09:32:03 +02:00
..
changelog [ADD] *: changelog entries I forgot 2023-08-14 09:28:19 +02:00
data [CHG] runbot_merge: perform stagings in a local clone of the repo 2023-08-25 15:33:25 +02:00
migrations [CHG] *: move repo cache from forwardbot to mergebot 2023-08-25 15:04:48 +02:00
models [IMP] forwardport: locking during creation of fw batch 2024-05-16 09:32:03 +02:00
tests [FIX] forwardport: suppress warning when closing unmanaged PR 2024-03-19 11:46:36 +01:00
__init__.py [ADD] mergebot, forwardbot: changelog 2021-10-20 15:16:48 +02:00
__manifest__.py [CHG] *: move repo cache from forwardbot to mergebot 2023-08-25 15:04:48 +02:00
controllers.py [IMP] rewrite /forwardport/outstanding 2023-07-10 15:23:31 +02:00