websocket · Issues· 82 open
Open on GitHubLocally synced open issues (discussions stay on GitHub)
- #1002
[BUG] runtime: out of memory: cannot allocate 187650799566848-byte block (1389953024 in use) fatal error: out of memory
bugUpdated Sep 1, 2026 - #1016
This project is dead again
bugUpdated Aug 31, 2026 - #1024
Documented: math/rand → crypto/rand mask key fix (CWE-338, never CVE'd)
Updated Aug 25, 2026 - #1025
Code Health Audit — 66 findings
Updated Aug 15, 2026 - #1006
[FEATURE] Release 1.5.4 with https proxy support
Updated May 11, 2026 - #983
[BUG] unit test fails with Go 1.24
bugUpdated Apr 14, 2026 - #1009
[BUG] Confusing cluster nam
bugUpdated Mar 11, 2026 - #1004
[BUG] sometimes uses incomplete IPv6 addresses as node names
bugUpdated Jan 27, 2026 - #859
[BUG] websocket on compress close duplicate
bugUpdated Nov 13, 2025 - #994
[FEATURE] Option to control client's buffer for non-101 response body
Updated Oct 18, 2025 - #997
[Question] Close connections on server shutdown
bugUpdated Sep 26, 2025 - #991
Bug Report: Transitive Vulnerability via golang.org/x/net — Please Upgrade to v0.41.0
bugUpdated Sep 13, 2025 - #996
DialContext doesn't give back TLS information
Updated Sep 6, 2025 - #990
[BUG] v1.5.3 release notes say hideTempErr has been removed under #894, but it isn't
bugUpdated Jul 16, 2025 - #993
add memory pool to alternative option
Updated Jul 15, 2025