gleam-lang/gleam

Unable to refetch a release when release is replaced on hex

Open

#3,268 opened on Jun 12, 2024

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (960 forks)batch import
discussionhelp wanted

Repository metrics

Stars
 (21,417 stars)
PR merge metrics
 (Avg merge 10d 19h) (69 merged PRs in 30d)

Description

After replacing a version on hex, gleam is unable to find the new tarball for the version, and continues to serve the old one.

Steps to reproduce:

  • Download the tarball for a version of the package.
  • Put that tarball in the cache folder (~/Library/Caches/gleam/hex/hexpm/packages on macOS)
  • Rename it with the latest version (i.e. rename lustre-4.2.4.tar to lustre-4.2.5.tar)
  • Try to build, old code should be served

Environment:

  • Gleam 1.2.1
  • Erlang/OTP 26
  • Node v18.14.0

Contributor guide

Research direction
Investigate the caching logic in Gleam's Hex package fetch. The issue is that when a package version is updated on Hex, the local cache is not invalidated. Look for how the cache key is generated and if there is any mechanism to check for updates.
Tech stack
rust
Domain
build system
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GleamGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70