New repo: lage doesn't work
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 816
- Forks
- 88
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Scaffold a new repo, run lage build, throws rust exception:
D:\git\pgo-bundling-tools>yarn build
lage - Version 2.7.13 - 15 Workers
thread '<unnamed>' panicked at 'Failed to read file: Failed to read file', src\hasher.rs:87:48
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
To Reproduce
Steps to reproduce the behavior:
- Create new git repo, clone
- Set up some packages
- run yarn in the workspace to link them
- Run yarn lage build from root
Expected behavior
Builds successfully.
Environment/Troubleshooting
Once I merged, this problem went away. This only happens if we haven't yet merged changes to the new repo.
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the failure by creating a new git repository, setting up workspace packages, running yarn, and then running yarn lage build from the root. Start by inspecting src/hasher.rs around the reported line and compare behavior before and after changes are merged; done means the new repository builds successfully without the Rust exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, typescript
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100