prometheus / prometheus/client_ruby
Validate behaviour of `DirectFileStore` in the presence of existing files
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 558
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Description
We (GoCardless) run our services in containers, which means a clean file system every time we boot the app.
We should look at what the behaviour is like for people who have file systems that persist between versions of the app. If so, we should look at what mitigations we can implement to make DirectFileStore work by default.
Any edge-cases should be added to the DirectFileStore’s docs.
Contributor guide
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 locating the DirectFileStore implementation and its documentation, then examine how it behaves when files persist across application versions. Reproduce relevant existing-file edge cases and document them; done means the expected behavior and any suitable default mitigations are agreed and recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100