SocketCluster / SocketCluster/socketcluster
Socketcluster 16.x stopped working due to underlying library update
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.2k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
Crossposting here for visibility to whomever, like me, is still using socketcluster 16 and noticed that your containers on k8s stopped working properly all of a sudden SocketCluster/ag-simple-broker#2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin with the linked SocketCluster/ag-simple-broker#2 report and the SocketCluster 16.x dependency and container setup; no repository file or test is named here. Reproduce the Kubernetes failure and trace the underlying library update, with done defined as SocketCluster 16.x containers working correctly again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, kubernetes, nodejs
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100