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

umputun / remark42 / 44859892219
87%

Build:
DEFAULT BRANCH: master
Ran 21 Nov 2026 03:15AM UTC
Jobs 1
Files 57
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

21 Nov 2026 03:12AM UTC coverage: 86.997% (+0.02%) from 86.977%
44859892219

push

github

web-flow
Write the automatic backup at start when the day has none (#2355)

* Write the automatic backup at start when the day has none

The automatic backup waited a full day after start before its first
export, and a restart began the wait again, so an instance restarted
more often than once a day never wrote one.

At start, each site now gets a backup unless it already has the file of
the current day, so further restarts that day write no other; after
that, one is written every 24 hours as before. The backup runs in the
background and does not hold up the server.

On shutdown the server cancels a backup in progress and waits up to ten
seconds for it before it closes the data store. The export stops at its
next write, and a stopped backup leaves the earlier files as they were.
The wait is bounded because an export reads from the store before it
writes, and a remote store that has stopped answering holds each read
for the rpc timeout.

The backup page now says when backups are written and how they are
named.

* Stop a null result from a remote store crashing the server

A remote store written in Go answers with "result": null for a nil
slice, as the memory_store example does for a site without user
details. The RPC clients dereferenced the missing result, so the server
crashed, and the backup at start triggered this whenever the backup of
the day was absent.

The calls of the remote engine and the remote admin store that return a
list now read a missing result as an empty list. The calls that have to
return a value return an error for it, so a missing comment, ID or
signing key cannot pass for a real one. The remote admin store also
refuses an empty key, as the static one does: it signs the tokens.

* Keep existing backups when the backup at start has no comments

A server started on an empty store, as it is before a restore, wrote an
empty backup at start. With MAX_BACKUP_FILES=1 that replaced the only
recovery point, and the restore command needs the server... (continued)

119 of 139 new or added lines in 4 files covered. (85.61%)

6891 of 7921 relevant lines covered (87.0%)

50.49 hits per line

Uncovered Changes

Lines Coverage ∆ File
15
75.86
2.53% backend/app/migrator/backup.go
2
88.29
-0.03% backend/app/cmd/server.go
2
69.49
15.21% backend/app/store/admin/remote.go
1
76.7
7.08% backend/app/store/engine/remote.go
Jobs
ID Job ID Ran Files Coverage
1 44859892219.1 21 Nov 2026 03:15AM UTC 57
87.0
GitHub Action Run
Source Files on build 44859892219
  • Tree
  • List 57
  • Changed 4
  • Source Changed 0
  • Coverage Changed 4
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • a2e7a68f on github
  • Prev Build on master (#44859011597)
  • Next Build on master (#44860455944)
  • 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