132be7fdd5
tests / pest (push) Failing after 7m32s
Details
tests / assets (push) Successful in 21s
Details
tests / release (push) Has been skipped
Details
Reported as "the folder arrives empty". It was not empty. The folder was 0700 and owned by the account that wrote it, so the account that COLLECTS — an rsync over ssh, a backup agent, anything that is not the writer — could not enter it, and an unreadable directory looks exactly like an empty one. The invoice had been sitting in it the whole time. The cause is that the default follows the process umask, so under a restrictive one 0755 quietly becomes 0700. The permissions are declared on the disk now rather than left to inherit, and a test writes under umask 0077 and asserts the mode — the ordinary umask hides this completely, which is why it was found on a server and not here. Two mistakes of mine on the way to it, both worth recording. I read the folder as the wrong user, got no entries back, and concluded the file had been deleted — it was a permission failure reading as an unprivileged account, not a missing file. And the first fix was a chmod on a variable that does not exist in that method, silenced by an @ so it failed without a word. Flysystem takes its permissions from configuration; a chmod afterwards was the wrong layer even before it was the wrong variable. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| Billing | ||
| Deployment | ||
| Devices | ||
| Dns | ||
| Env | ||
| Maintenance | ||
| Monitoring | ||
| Proxmox | ||
| Secrets | ||
| Ssh | ||
| Stripe | ||
| Traefik | ||
| Traffic | ||
| Wireguard | ||