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

umputun / remark42 / 42592897879
87%

Build:
DEFAULT BRANCH: master
Ran 09 Nov 2026 09:24AM 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:22AM UTC coverage: 85.354% (+0.1%) from 85.219%
42592897879

push

github

web-flow
Fix cleanup escaping, avatar uri store, setup errors, RSS cap, image retries and docs (#2290)

* Fix query escaping in cleanup, the avatar uri store and setup errors

The cleanup command put the site id and post URL into request queries
unescaped, so a post URL with its own query lost everything after the
first parameter (?id=1&lang=en arrived as ?id=1) and the command listed,
deleted or retitled comments of the wrong page.

The avatar command offered uri for --src.type and --dst.type but only
handled fs and bolt, so uri failed as unsupported. It now shares one
store constructor with the server.

A setup failure was logged at PANIC level, which prints a goroutine dump
and exits before the error is returned. It is now returned to main,
which logs it as an error, and the signal goroutine stops when Execute
returns.

* Cap the post RSS feed, stop retrying refused images and abandoned waits

The post RSS feed checked its limit after appending each item and only
when the index was already past it, so it returned 22 items, not 20.

The image proxy retried a download five times a second apart, including
when the SSRF-safe transport refused a private address, so every such
request took four seconds to fail. The refusal is now a sentinel error
that ends the retries at once; network errors are still retried.

The migrator wait endpoint polled on a background context, so after the
client disconnected it kept polling until the 15 minute timeout. It now
waits on the request context and stops when the client goes.

* Fix the counts route in the API docs and flag handling in the example

The API docs listed POST /api/v1/count, while the route is
POST /api/v1/counts.

The memory_store example listed every user with any stored meta as
verified, replaced the whole user meta on each flag change, so blocking
a user dropped their email and verification and verifying dropped the
block, and logged all user metas, emails included, at INFO on every
blocked-users listing.

26 of 26 new or added lines in 6 files covered. (100.0%)

6224 of 7292 relevant lines covered (85.35%)

34.0 hits per line

Jobs
ID Job ID Ran Files Coverage
1 42592897879.1 09 Nov 2026 09:24AM UTC 54
85.35
GitHub Action Run
Source Files on build 42592897879
  • Tree
  • List 54
  • Changed 6
  • Source Changed 0
  • Coverage Changed 6
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • 4d63ed34 on github
  • Prev Build on master (#42591871490)
  • Next Build on master (#42593069414)
  • 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