MatterMiners / MatterMiners/lapis
RemoteConnection should not be shared by all Resources
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
The current simulation setup for simulating caching does create only one connection object for all pools and clusters. It should be possible to create differing connection objects to have separate RemoteConnections (so not shared with cache nodes).
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
Start by tracing the simulation setup that creates one connection for all pools and clusters, then identify where resources obtain their RemoteConnection. Confirm how cache nodes and other resources are grouped. Done means separate connection objects can be configured so cache nodes do not share a RemoteConnection with other resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100