gleam-lang/gleam

Stale manifest.toml preventing correct dependency resolution

Open

#3,891 opened on Nov 25, 2024

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (21,417 stars) (960 forks)batch import
help wanted

Description

Version: gleam@1.6.2 (OTP26)

Building upon this issue: https://github.com/gleam-lang/gleam/issues/3890

Clone this version of lustre

git clone https://github.com/lustre-labs/lustre.git
cd lustre
git checkout 969f77de72ca9502aa160e637d2f4fce86f94053
cd test-apps/vdom-test-templates

Now in test-apps/vdom-test-templates/gleam.toml change the gleam_stlidb dependency to ">= 0.43.0 and < 2.0.0" like so:

name = "app"
version = "1.0.0"
target = "javascript"

[dependencies]
gleam_stdlib = ">= 0.43.0 and < 2.0.0"
lustre = { path = "../../" }

Now run the build for that project:

~/Projects/lustre/test-apps/vdom-test-templates → gleam build
  Resolving versions
error: Dependency resolution failed

An error occurred while determining what dependency packages and
versions should be downloaded.
The error from the version resolver library was:

An unrecoverable error happened while solving dependencies: gleam_stdlib is
specified with the requirement `>= 0.43.0 and < 2.0.0`, but it is locked to
0.37.0, which is incompatible.

This error is resolved by just deleting manifest.toml and running build again. The root cause might be the same as https://github.com/gleam-lang/gleam/issues/3890

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.
3
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.
mostly clear
Prerequisites
familiarity with Gleam's manifest.tomlunderstanding of dependency resolutionbasic Rust knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue describes a stale manifest.toml causing dependency resolution to fail when a version requirement is changed. The fix likely involves ensuring manifest.toml is invalidated or updated correctly when dependencies change. Look at the code that handles manifest locking, likely in the build system (e.g., `src/manifest.rs` or similar). Compare with the related issue #3890 for potential root cause. Check if there are existing tests for manifest update scenarios.