Think about what happens when `fetch` is run twice concurrently for a single cache directory

Open
  • Is something wrong?
#32 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
rust
Domain
backend

Research direction

Locate the fetch entry point and the code that reads or writes the cache directory. Run or add a concurrent-fetch test for a single cache directory, then determine whether both operations complete safely and capture the expected behavior in regression coverage.

Written by the indexing model from the issue text.

Description

I don't believe currently two fetch operations will work if they are racing each other? Needs some testing/analysis.

Dominant language
Rust
Stars
181
Forks
14
Avg merge
14h 16m
Merged PRs (30d)
21

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rustls/upki

All issues in rustls/upki

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.