38714156087
94%

Ran 15 Oct 2026 09:39AM UTC

Jobs 1

Files 83

Run time 1min

Badge

Embed ▾

Committed 15 Oct 2026 09:36AM UTC coverage: 93.354%. Remained the same

Build # 38714156087

Build Type

push

github

Committed by

web-flow

Commit Message

Keep message modified from going backwards when confirmations are added (#302)

* Keep message modified from going backwards when confirmations are added

add_confirmations set the message's modified to the newest confirmation
date. Live sync copies confirmation dates from the legacy service, so a
confirmation older than the message moved modified back. Clients poll on
modified to find changes, so they could miss the new confirmation.

Messages now only move modified forward, like transactions do since #271.

Both repositories now apply the max in SQL with GREATEST. Computing it in
Python from the row read at the start still let two concurrent writers
move modified back: the second one overwrote the first with an older
value.

* Address review: AGENTS.md follow-up and accurate comments

Coverage Stats

3315 of 3551 relevant lines covered (93.35%)

0.93 hits per line

Coverage Regressions

Lines	Coverage	∆	File
5	96.3	0.0%	app/datasources/db/repositories/multisig_transaction_repository.py
1	97.8	0.0%	app/datasources/db/repositories/safe_message_repository.py

Jobs

ID	Job ID	Ran	Files	Coverage
1	38714156087.1	15 Oct 2026 09:39AM UTC	83	93.35	GitHub Action Run

safe-global / safe-queue-service / 38714156087
94%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Coverage Regressions

Jobs

Source Files on build 38714156087

safe-global / safe-queue-service / 38714156087 94%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Coverage Regressions

Jobs

Source Files on build 38714156087

safe-global / safe-queue-service / 38714156087
94%

README BADGES
x