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

nats-io / nats-server / 12218915667
83%

Build:
DEFAULT BRANCH: main
Ran 08 Dec 2024 05:42AM 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

06 Dec 2024 07:35PM UTC coverage: 85.369% (-0.03%) from 85.402%
12218915667

push

github

web-flow
[FIXED] Subject state consistency (#6226)

Subject state would not always remain consistent given a specific
pattern of message removals.

There were three bugs:
- `recalculateFirstForSubj` in memstore would do `startSeq+1`, but
filestore would always just start at `mb.first.seq`. These are now
consistent.
- `recalculateFirstForSubj` was not called when `ss.Msgs == 1`, which
could mean we had a stale `ss.FirstSeq` if it needed to be recalculated.
- If after recalculation it turns out `ss.FirstSeq` equals the message
we're trying to remove, we need to `recalculateFirstForSubj` again,
since `ss.Last` is also lazy and could be incorrect.

Apart from that, filestore and memstore are now both equivalent when it
comes to first updating per-subject state and then removing the message,
as well as `removeSeqPerSubject` and how it updates the subject state.


Signed-off-by: Maurice van Veen <github@mauricevanveen.com>

68242 of 79938 relevant lines covered (85.37%)

1478767.69 hits per line

Jobs
ID Job ID Ran Files Coverage
1 12218915667.1 08 Dec 2024 05:42AM UTC 0
85.37
GitHub Action Run
Source Files on build 12218915667
Detailed source file information is not available for this build.
  • Back to Repo
  • Github Actions Build #12218915667
  • 60e2982d on github
  • Prev Build on main (#12193095589)
  • Next Build on main (#12229104575)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc