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

umputun / remark42 / 42734289690
87%

Build:
DEFAULT BRANCH: master
Ran 10 Nov 2026 01:16AM 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

10 Nov 2026 01:13AM UTC coverage: 85.97% (-0.03%) from 85.995%
42734289690

push

github

web-flow
Fix backup restore loops, lost metadata, votes and Telegram details (#2291)

* Stop restoring at an unreadable backup record and keep its metadata

Previously, a truncated or malformed record in a backup made restore loop
forever: the JSON decoder returns the same error on every call, so the
loop never reached the end of the stream and the site stayed busy. Such
a record was also counted as failed twice. And when any comment failed
to save, restore returned before applying the users and posts metadata,
so one rejected comment dropped every block, verified flag, read-only
post and stored email.

Restore now reads each record as raw JSON first. It stops at the first
record the decoder cannot read past and reports it with the number of
records read before it, while a well-formed record with a wrong value
is counted as failed and skipped, as before. The metadata is applied in
every case, and the comment errors are returned alongside.

* Back up comments as stored, without reader-side changes

Previously, the native export read comments through the same path the
widget uses for an admin reader. That path hides the voters list and
marks comments of currently blocked users as blocked, so a backup lost
every vote, and restoring it saved the blocked mark into the comments
themselves, where it stayed after the user was unblocked.

Export now reads comments as the engine stores them, keeping the voters
list and leaving out the voters' IP hashes, which backups never held.
Restore clears the blocked mark inside comments, since blocks come from
the users metadata, so backups made by earlier versions restore
correctly too. The backup format is unchanged: the votes field was
already part of the comment record, and earlier versions restore the new
backups as before, with the votes kept.

* Restore Telegram usernames from a backup

Previously, a backup carried each user's email and Telegram details, but
restore saved only the email, so users subscribed through Telegram... (continued)

23 of 29 new or added lines in 2 files covered. (79.31%)

1 existing line in 1 file now uncovered.

6054 of 7042 relevant lines covered (85.97%)

36.72 hits per line

Uncovered Changes

Lines Coverage ∆ File
6
90.29
-0.78% backend/app/store/service/service.go

Coverage Regressions

Lines Coverage ∆ File
1
95.65
-0.87% backend/app/notify/notify.go
Jobs
ID Job ID Ran Files Coverage
1 42734289690.1 10 Nov 2026 01:16AM UTC 54
85.97
GitHub Action Run
Source Files on build 42734289690
  • Tree
  • List 54
  • Changed 3
  • Source Changed 0
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • 28439e1d on github
  • Prev Build on master (#42733903350)
  • Next Build on master (#42760018167)
  • 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