• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

umputun / remark42 / 42593069414
87%

Build:
DEFAULT BRANCH: master
Ran 09 Nov 2026 09:26AM UTC
Jobs 1
Files 54
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

09 Nov 2026 09:23AM UTC coverage: 85.504% (+0.2%) from 85.354%
42593069414

push

github

web-flow
Consolidate the bolt engine's bookkeeping and stop user details leaking between users (#2285)

* Drop the no-op delete from the last bucket on comment removal

Keys in the last bucket are timestamps, so deleting by comment ID never
matched anything. Removed comments stay referenced there and are skipped
by lastComments because they are marked deleted.

* Add view and update helpers to the bolt engine

Most methods looked up the site's db and opened a transaction with the
same four lines. The helpers keep the site-not-found error and leave the
early checks where a method must fail before doing anything else.

* Simplify flag handling in the bolt engine

Flags now share one bucket map and one key helper, and setting a flag
writes the timestamp in one place.

Listing blocked users looked up each user's name with Find while its own
read transaction on the blocks bucket was still open. In bbolt a nested
read transaction can deadlock against a concurrent write that has to
remap the growing file. The ids are now collected inside the transaction
and the names read after it.

* Collect a user's comments for deletion in one read transaction

Deleting a user listed every post through Info, which also loaded each
post's metadata, and then opened a separate read transaction per post.
One transaction now walks the post buckets directly, and a post missing
its metadata entry no longer stops the deletion.

* Read user details through one loader and fix entries leaking into each other

Listing user details unmarshalled every entry into the same struct, and
the email field is omitted from JSON when empty. A user with only a
Telegram detail therefore came back with the email of the user listed
before. Backups export that list, so a restore could save the other user's
address, and that user's notifications would then go to it.

Each entry is now decoded into its own struct. Reading, setting and
deleting a detail share one loader, and setting or deleting one runs in
a sin... (continued)

113 of 128 new or added lines in 1 file covered. (88.28%)

8 existing lines in 1 file now uncovered.

6164 of 7209 relevant lines covered (85.5%)

34.76 hits per line

Uncovered Changes

Lines Coverage ∆ File
15
82.01
1.24% backend/app/store/engine/bolt.go

Coverage Regressions

Lines Coverage ∆ File
8
82.01
1.24% backend/app/store/engine/bolt.go
Jobs
ID Job ID Ran Files Coverage
1 42593069414.1 09 Nov 2026 09:26AM UTC 54
85.5
GitHub Action Run
Source Files on build 42593069414
  • Tree
  • List 54
  • Changed 1
  • Source Changed 0
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • df477162 on github
  • Prev Build on master (#42592897879)
  • Next Build on master (#42733211156)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc