Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

precheck: with no built binary it prints 'cat: .../N.log: No such file or directory'

Closed Beginner friendly
#1,782 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

A pull request for this has already been merged.

  • #1786 by @facelessdevhack — merged

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
85/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
bash

Research direction

The stray error comes from the serial loop in tools/precheck.sh that calls cat "$OUT/$i.log" right after run_gate. When the self-test row is skipped for lack of a binary, run_gate writes only the .st file, so the cat has nothing to read. Run bash tools/precheck.sh with no built binary to reproduce the message, then make the log print only when the file exists. Done when that run shows no cat: line and the row still reads SKIP, and a run with a binary still prints the self-test log.

Written by the indexing model from the issue text.

Description

area:gates bug good first issue

On a tree with no built eigenscript, bash tools/precheck.sh (or make precheck) prints this before its table:

cat: /tmp/eigs_precheck.XXXXXX/18.log: No such file or directory

Without a binary, run_gate skips the self-test row (selftest|tools/selftests.sh --changed $BASE). It writes only the row's .st status file (SKIP) and no .log. The serial loop that runs that row then prints the log unconditionally: cat "$OUT/$i.log" right after run_gate "$i" "$class" $cmd in tools/precheck.sh.

The table is still right (... 3 skipped), so this is noise. But it is the first line a contributor sees from make precheck on a fresh clone, and it reads like an error.

Done when

  • With no binary, bash tools/precheck.sh prints no cat: error, and the skipped row still reads SKIP ... no eigenscript binary.
  • With a binary, the self-test row's log is still printed.

Generated by Claude Code

Dominant language
C
Stars
3
Forks
7
Avg merge
8h 41m
Merged PRs (30d)
254

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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 InauguralSystems/EigenScript

All issues in InauguralSystems/EigenScript

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.