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

nats-io / nats-server / 12326964845
83%

Build:
DEFAULT BRANCH: main
Ran 14 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

14 Dec 2024 12:35AM UTC coverage: 85.478% (+0.09%) from 85.384%
12326964845

push

github

web-flow
[FIXED] Websocket: handling of close message frame without status (#6260)

The server was incorrectly sending back a close message frame with
status 1005 when not receiving a status in the close message frame from
the client. This was wrong. This status was to be used internally to
keep track that no status was received and therefore the server should
not send a status back.

Also, the server was sending status 1006 in some error conditions, while
the spec also states that this status must not be used to set the
status, instead it was to internally keep track that there was an error
condition.

Resolves #6259

Signed-off-by: Ivan Kozlovic <ivan@synadia.com>

68337 of 79947 relevant lines covered (85.48%)

1155367.72 hits per line

Jobs
ID Job ID Ran Files Coverage
1 12326964845.1 14 Dec 2024 05:42AM UTC 0
85.48
GitHub Action Run
Source Files on build 12326964845
Detailed source file information is not available for this build.
  • Back to Repo
  • Github Actions Build #12326964845
  • 3646ef95 on github
  • Prev Build on main (#12309740565)
  • Next Build on main (#12335908620)
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