nats-server
https://github.com/nats-io/nats-server
Go
High-Performance server for NATS.io, the cloud and edge native messaging system.
Triage Issues!
When you volunteer to triage issues, you'll receive an email each day with a link to an open issue that needs help in this project. You'll also receive instructions on how to triage issues.
Triage Docs!
Receive a documented method or class from your favorite GitHub repos in your inbox every day. If you're really pro, receive undocumented methods or classes and supercharge your commit history.
Go not yet supported2 Subscribers
Add a CodeTriage badge to nats-server
Help out
- Issues
- Do not require "seq" field on DIRECT GET with "max_bytes" supplied
- NATS Message Consumption Issue After Pod (NATS cluster) Restart in OpenShift
- Allow sync consumer config options for sources and mirrors
- Why not ? add delay option when sending messages?
- NATS consumers not pulling messages from Jetstream. Restarting NATS server solved the problem
- push consumer deliver_subject does not match wildcarded subscription
- AWS Fargate Memory slowly increasing/leak over time
- Consistent memory leak through versions 2.10.9 -> 2.10.17 -> 2.10.20.
- De-flake `TestNRGCandidateDontStepdownDueToLeaderOfPreviousTerm`
- Falling behind in health check. JetStream is not current with the meta leader. [v2.10.21]
- Docs
- Go not yet supported