Recovery after no space left error/clipboard_history.json corruption

[Dziksonn]

Hello. Here is all the info I gathered. If you'll need anything more I'm open to help.
I was able to run into it few times by accident (my disk gets full alot), never reproduced intentionally.

Assumed reproduction:

1. Get your disk full
2. Copy something
   2026/03/31 17:07:20 logger.go:19: ERROR: failed to add new item `( REDACTED )` | failed writing to file: write /home/dziks0nn/.config/clipse/clipboard_history.json: no space left on device
3. Free up space
4. Clipse crashes due to corrupted clipboard_history.json, and never recovers from it.

2026/03/31 17:07:30 logger.go:19: ERROR: EOF
[...] Same thing over and over
2026/04/02 20:08:50 logger.go:19: ERROR: EOF

Temporary fix:

Deleting clipboard_history.json fixes it

Additional logs:

[dziks0nn@nixos:~]$ clipse -v
clipse v1.1.0

[dziks0nn@nixos:~]$ clipse
goroutine 1 [running]:
runtime/debug.Stack()
	runtime/debug/stack.go:26 +0x5e
runtime/debug.PrintStack()
	runtime/debug/stack.go:18 +0x13
github.com/savedra1/clipse/utils.HandleError({0x6c5f28, 0x8400b0})
	github.com/savedra1/clipse/utils/err.go:11 +0x2c
github.com/savedra1/clipse/config.GetHistory()
	github.com/savedra1/clipse/config/history.go:65 +0x9d
github.com/savedra1/clipse/app.NewModel()
	github.com/savedra1/clipse/app/model.go:72 +0x65
main.launchTUI()
	github.com/savedra1/clipse/main.go:95 +0x2a
main.main()
	github.com/savedra1/clipse/main.go:50 +0xc5

[savedra1]

Hi @Dziksonn there was a fix implemented for this since v1.1.0. Have you tried the latest version?

Thanks

[Dziksonn]

Hey @savedra1, yes I built from latest and tested it. I thought the fix wasn't there but that was my bad. I was using a custom mount point with limited disk space instead of / so the space check didn't trigger for me and I overlooked it in code. My bad.

The check does exist, but it's hardcoded to / rather than the path actually being used, so it'd silently miss cases like mine. Opened a PR (#349) to address that along with a redundant check I mistakenly added. It is probably edge-case, and Im fine with closing this issue if you don't want to handle it.

Sorry for the confusion and I appreciate your response.