[registry-facade] pulls twice on cache miss
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Bug description
When we pull from US, this does so from EU. Therefore, pulling twice due to a cache miss (and missing cache often) becomes expensive.
Steps to reproduce
This could be related a cache miss for a workspace-image (perhaps because we pushed new base images), or a cache miss on a newly built workspace image (for which we just built and pushed via image-builder-mk3).
Workspace affected
No response
Expected behavior
@aledbf were you able to socialize possible options with @csweichel for this last week? It's okay to say no, I know you two were working the S3 bucket issue instead.
Example repository
No response
Anything else?
Need analysis and design work, not ready to be picked up.
This is tech debt from the introduction of IPFS to cache images (to accelerate image pulls).
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
No file or test is named. Start by locating the registry-facade pull path and tracing cache misses for workspace images and newly built workspace images, including the US-to-EU and IPFS cache behavior. Done means producing an agreed analysis and design for avoiding the duplicate pull.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100