[BUG] Creating a runbook in a subfolder fails

[vkosnar]

Bug Description

Creating a new runbook inside a subfolder fails with Failed to create runbook: Failed to create runbook.

Steps to Reproduce

1. Create an empty workspace.
2. Create an empty folder in the workspace.
3. Right click the folder and select 'New Runbook'.
4. See error

Expected Behavior

A new runbook should be created inside the empty folder.

Actual Behavior

A new runbook is not created.

Environment

• OS: Ubuntu 24.04.3 LTS
• Atuin Desktop Version: 0.1.11
• Atuin CLI Version: none
• Shell: bash
• Terminal: GNOME

Screenshots/Logs

Failed to create runbook: Failed to create runbook

Workaround

Creating a runbook in the top level workspace works + it creates all the "failed" runbooks retroactively.

[BinaryMuse]

Hi @vkosnar - does this happen on only an online or offline workspace, or workspaces of either type?

[vkosnar]

Hi, this happens on offline workspaces. Unfortunately can't test online ones.

[BinaryMuse]

Since the runbooks are actually being created, it makes me think this is related to the file watcher. I'm checking into a few things, but if nothing else I'll have some improved logging soon that can help track down what's really going on.

[vkosnar]

I also noticed a similar thing happens when I try to delete runbooks from the folder - I click delete and they stay there until I create a new runbook in the top level workspace.

[BinaryMuse]

Okay, so seems like it's related specifically to subdirectory watching.

@ellie I'll look into it but do you have any thoughts?

[BinaryMuse]

@vkosnar By any chance is your workspace directory a subdirectory of a symlinked directory?

You can check with realpath . or something like diff -is <(pwd -L) <(pwd -P)

[BinaryMuse]

I'm hoping this is fixed in v0.2.3 but there's a chance the root cause is different

[vkosnar]

@vkosnar By any chance is your workspace directory a subdirectory of a symlinked directory?

@BinaryMuse Nope, just a regular directory.