I just experienced this locally, while working on #42:
repository-audit % rm -Rf output
repository-audit % node .
Executing Query #1...
repository-audit % tree output
output [error opening dir]
0 directories, 0 files
repository-audit %
I've not noticed this in CI yet, but I find it troublesome that this could happen. We have other checks downstream that would fail the CI run if they don't find report output, however I would have expected to have seen an error thrown in the JS code. 🤔
Simply running again immediately after resulted in the expected outcome:
repository-audit % node .
Executing Query #1...
Executing Query #2...
Queried Repository Count: 181
repository-audit % tree output
output
├── commit-message.txt
├── internal
│ └── ably.md
└── public
└── ably.md
2 directories, 3 files
repository-audit %
@owenpearson any suggestions of what might have been going on here? 😕
If it helps, and for clarity, my zsh prompt shows me exit code at the start of line - for example the ?1 here:
repository-audit % true
repository-audit % false
?1 repository-audit %
I keep my terminal configuration very simple - in this case showing exit codes via this in ~/.zshrc:
PROMPT='%(?..%F{red}?%? )%f%B%F{240}%1~%f%b %# '
I just experienced this locally, while working on #42:
I've not noticed this in CI yet, but I find it troublesome that this could happen. We have other checks downstream that would fail the CI run if they don't find report output, however I would have expected to have seen an error thrown in the JS code. 🤔
Simply running again immediately after resulted in the expected outcome:
@owenpearson any suggestions of what might have been going on here? 😕
If it helps, and for clarity, my zsh prompt shows me exit code at the start of line - for example the
?1here:I keep my terminal configuration very simple - in this case showing exit codes via this in
~/.zshrc:PROMPT='%(?..%F{red}?%? )%f%B%F{240}%1~%f%b %# '