k9s exits silently if screenDumpDir cannot be created.

[njanceski-pluto]

Describe the bug
If you copy a ~/.config/k9s/config.yml with a screenDumpDir setting that cannot be created, it will fail silently with exit code 1. On macOS installed k9s with homebrew.

To Reproduce
in ~/.config/k9s/config.yml add

  screenDumpDir: /var/folders/hz/vt7_1v7n2c1ck3jpyvf3r_7w0000gn/T/k9s-screens-user

This was never set by the user originally and the config file is generated by k9s the first time it is run. If you copy this config to another macOS machine where that directory cannot be created, then the error will occur.

In the k9s log file:

9:52AM INF 🐶 K9s starting up...
9:52AM FTL Unable to create dir "/var/folders/hz/vt7_1v7n2c1ck3jpyvf3r_7w0000gn/T" mkdir /var/folders/hz: permission denied

Expected behavior
k9s to function normally until a screenDump is performed.

Workaround
Move the ~/.config/k9s/config.yml to another location so that k9s will create a new file on startup. Diff the new file with your previous version to preserve your settings.

Versions (please complete the following information):

• OS: Ventura 13.1
• K9s: v0.26.7

Additional context
I love k9s but I had no idea about the ~/.config/k9s/config.yml creating that screenDumpDir setting. Hopefully the workaround will help another person. It took me an hour to figure out to remove all my configs for k9s to get it working, then I diffed the offending file to find the issue at the bottom.

[vallard]

thanks! This helped me debug my issue!

[derailed]

@njanceski-pluto Thank you for this issue and helping others!!
I will change the logic to flash a friendly error instead.
Also there is a #1321 is also an option big thanks to Vlasoc Artem!!

[derailed]

@njanceski-pluto I think this should be fixed in v0.27.0. Tx!