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 (21,417 stars) (960 forks)batch import
discussionhelp wanted

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

Tech stack
rust
Domain
build systemtooling
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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Rust programmingGleam build processFile system caching
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Investigate the cache logic in the Gleam compiler's hex package fetching module. Look at how the cache is checked and updated. The issue indicates that the cache does not invalidate when the remote tarball changes. A potential fix could involve comparing version metadata or using a checksum. Review the code in src/hex.rs or similar file. The maintainer may provide further guidance on the expected behavior.
Unable to refetch a release when release is replaced on hex · gleam-lang/gleam#3268 | Good First Issue