crashappsec / crashappsec/chalk
Don't keep emitting chalk info in `chalk extract` when a file doesn't even exist
- Dominant language
- Nim
- Stars
- 436
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
## Description
It is very confusing that I get this output that kind of looks like chalk succeeded in doing something even when a file doesn't even exist.
I'd expect it to exit as soon as it gets this error.
```
admin@ubuntu:~$ ./chalk extract flubber
warn: Disabling docker codec as docker command is not available
info: Installed bash auto-completion file to: /home/admin/.local/share/bash_completion/completions/chalk.bash
info: Added sourcing of autocomplete to ~/.bash_completion file
warn: docker: no command found in PATH. `chalk docker` not available.
error: flubber: No image or container found
warn: No chalk marks extracted
info: /home/admin/.local/chalk/chalk.log: Open (sink conf='default_out')
info: Full chalk report appended to: ~/.local/chalk/chalk.log
[
{
"_OPERATION": "extract",
"_DATETIME": "2026-03-31T19:53:22.430+00:00",
"_ENV": {
```
I'd expect it to do something like:
```
admin@ubuntu:~$ ./chalk extract flubber
warn: Disabling docker codec as docker command is not available
info: Installed bash auto-completion file to: /home/admin/.local/share/bash_completion/completions/chalk.bash
info: Added sourcing of autocomplete to ~/.bash_completion file
warn: docker: no command found in PATH. `chalk docker` not available.
error: flubber: No image or container found
admin@ubuntu~$
```
## Impact
Not low.
## Steps to Reproduce
Run `chalk extract` on any non-existing file.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by running `chalk extract` with a non-existing file such as `flubber`, then trace the `extract` command's error handling and subsequent output. The change is done when the command stops after reporting that no image or container was found, without emitting the no-marks warning, log information, or report output shown in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nim
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100