Check flow tools reports LibreLane and the PDK missing under the Nix launcher, though runs work

Open
#66 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
dart
Domain
desktop, tooling

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 ~/.ciel holds 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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Ferrite-Engineering/simcrux

All issues in Ferrite-Engineering/simcrux

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.