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

umputun / remark42 / 38166422441
84%

Build:
DEFAULT BRANCH: master
Ran 11 Oct 2026 07:06PM 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

11 Oct 2026 07:03PM UTC coverage: 84.493% (+0.005%) from 84.488%
38166422441

push

github

web-flow
Fix the /web demo on instances that do not serve site remark (#2264)

* Fill the configured site into the demo pages the binary serves

The build emits the demo, counter and last-comments pages for site
remark. The docker image replaces that with the first configured site
at container start, but the binary served them as built, so on an
instance serving another site the demo's API requests failed with
"site not found" and its widget asked about a site the reader was not
signed in to.

The file server now fills in the first configured site the same way,
in the html files the docker image rewrites, and the site is part of
the cache validator so a changed SITE is not answered with 304. The
release build fails if those pages lose the site_id:"remark" literal
the server replaces and the docker image's pattern expects.

* Keep the session when a request is refused with 403

The fetcher cleared the auth cookies on 403 as well as 401. The server
answers 403 to a valid session that may not do something, such as one
issued for another site served from the same remark42 host, an
anonymous user, or a non-admin. Clearing the shared XSRF cookie then
could sign the reader out of the other sites using those cookies too.

Cookies are now cleared only on 401, which is what an invalid session
gets. Logout is the one place a 403 can mean the session is over: an
expired token sent as a header is refused there, so logout now forgets
the local session whatever the server answers.

* Finish signing out when the server refuses the logout

The logout request dropped the local session and then rejected, and
the signout action clears the signed-in user only after it resolves,
so a refused logout, such as an expired header token answered with 403,
left the widget showing the reader as signed in without credentials.
The request failure is now ignored once the session is dropped.

18 of 20 new or added lines in 3 files covered. (90.0%)

6086 of 7203 relevant lines covered (84.49%)

31.95 hits per line

Uncovered Changes

Lines Coverage ∆ File
2
90.32
-2.27% backend/app/rest/api/webfiles.go
Jobs
ID Job ID Ran Files Coverage
1 38166422441.1 11 Oct 2026 07:06PM UTC 54
84.49
GitHub Action Run
Source Files on build 38166422441
  • Tree
  • List 54
  • Changed 3
  • Source Changed 0
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • 505364bd on github
  • Prev Build on master (#38165872331)
  • 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