gleam-lang/gleam

Low quality error message coming from version resolution library

Open

#4560 opened on May 5, 2025

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

Description

gleam 1.10.0

When running gleam CLI under a proxy with a GLEAM_CACERTS_PATH wrongly set, the error is too ambiguous and is unclear that this is the problem.

What happens now:

> gleam run 
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: 

Unable to determine package versions: file operation failed

Suggested:

> gleam run 
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: 

Unable to determine package versions: certificate error
Hint: are you sure the certificates are correct?

or something along those lines

Contributor guide

Tech stack
rust
Domain
clideveloper experience
Issue type
feature
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.
mostly clear
Prerequisites
basic Rust knowledgefamiliarity with Gleam CLI structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
The issue describes a misleading error message when `GLEAM CACERTS PATH` is misconfigured. The error originates from the version resolution library. Look for the string 'Unable to determine package versions: file operation failed' in the codebase, likely in the version resolver module. Replace it to include a certificate error and add a hint about checking certificates. The suggested output is provided in the issue. Ensure the change is consistent with error handling patterns in the project.