Check flow tools reports LibreLane and the PDK missing under the Nix launcher, though runs work
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
The Settings > Engines > Check flow tools handler in the Dart app and the engine-probe service behind it are the entry points; compare them with how Tools > Run Flow Entry resolves the Nix launcher and PDK root. Three fixes to scope: accept a LibreLane flake directory as a valid launcher path, resolve the default PDK under ~/.ciel the way LibreLane does, and report non-empty stderr from nextpnr as a probe failure rather than a version string. Done means the check agrees with the working Met run on the same settings, with probe tests covering each of the three cases.
Written by the indexing model from the issue text.
Description
On macOS with SimCrux 1.2.0, Settings > Engines > Check flow tools reports problems that aren't real when LibreLane runs through Nix.
Setup: LibreLane launcher set to Nix, LibreLane path set to a LibreLane 3.0.17 checkout (the flake directory), PDK root empty (~/.ciel holds sky130A).
The check reports:
librelane: not found. The path is a flake directory, not an executable, and the check looks for an executable.No PDK was found. Set the PDK root above.But~/.cielholds the PDK that LibreLane itself uses by default.- For nextpnr, a green tick next to text that is really an error (
mkdir: …/.local/share: Permission denied). The tool's stderr is shown as if it were a version string.
Meanwhile Tools > Run Flow Entry with these same settings runs LibreLane 3.0.17 and finishes Met in 36 s. So the check contradicts a working setup.
Expected: under the Nix launcher, check that the path is a LibreLane flake (and optionally that nix develop resolves); resolve the default PDK location the way LibreLane does; show a tool's probe failure as a failure.
- Dominant language
- Dart
- Stars
- 0
- Forks
- 0
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from Ferrite-Engineering/simcrux
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 3/5 Half a day Newbie friendliness 74/100
All issues in Ferrite-Engineering/simcrux
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
ccch1mneyyy/dsh-Go#1682 ·
Maintainers usually reply within 1 day
-
help wanted
Difficulty 1/5 Under an hour Newbie friendliness 76/100
pesaclarity/ujumbe-parsers#64 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
patarapolw/lingua_srs#278 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
dreautall/waterfly-iii#890 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day