[Bug] Missing static root is still not caught for root_dir, reload and bound arguments
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start with the cited paths src/Worker/ServerWorker.php:157 and src/Http/HttpRequestHandler.php:117, then trace how Runner validates server roots and how the compiler pass obtains service definitions. Add tests for the serve_files root, reload after directory deletion, and roots supplied through defaults or parent/child definitions. Done means missing roots produce one clear error or keep old workers, without a restart loop.
Written by the indexing model from the issue text.
Description
Problem
PR #976 stops start and restart when the root directory of a StaticFilesMiddleware service does not exist. Some cases are still not covered. In these cases the workers restart again and again.
How to see it
- The old
serve_files+root_dirpath has the same problem (src/Worker/ServerWorker.php:157,src/Http/HttpRequestHandler.php:117). - The server runs, the directory is deleted, then
reload(or the file monitor) restarts the workers: the workers fail in a loop. - A root set only through
_defaults.bindor a parent/child service definition is not seen by the compiler pass. - In prod, an old config cache has an old
static_rootslist untilcache:clear.
Fix idea
Check root_dir of every server in Runner too. For reload, keep the old workers or stop with one message. For the definition cases, read the argument after the container is compiled.
Done when
-
serve_fileswith a missingroot_dirstopsstartwith one clear error. - A reload with a missing directory does not start a restart loop.
- Tests for each case.
- Dominant language
- PHP
- Stars
- 2
- Forks
- 3
- Avg merge
- 39m
- Merged PRs (30d)
- 105
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from crazy-goat/workerman-bundle
-
[Tests] Strengthen '0'/'-5' warmup-timeout rejection assertions to include got suffixPossibly taken @rootsiemen claimed this 1 day ago. Opengood first issue priority:low type:refactor
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
crazy-goat/workerman-bundle#1065 ·
Maintainers usually reply within 1 day
-
[Code Quality] CacheWarmupTimeoutConfig throws bare InvalidArgumentException instead of typed InvalidCacheWarmupTimeoutExceptionPossibly taken @rootsiemen claimed this 1 day ago. Openpriority:low type:refactor
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
crazy-goat/workerman-bundle#1063 · 1 comment ·
Maintainers usually reply within 1 day
-
[Tests] Matrix sed rewrite class [a-z-]+ excludes digits — future symfony/foo2bar silently skippedOpenpriority:low type:refactor
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
crazy-goat/workerman-bundle#1060 ·
Maintainers usually reply within 1 day
-
[Code Quality] Test helper captureFingerprintForPid() duplicates MasterFingerprint UID readPossibly taken @rootsiemen claimed this 2 days ago. Opengood first issue priority:low type:refactor
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
crazy-goat/workerman-bundle#1057 ·
Maintainers usually reply within 1 day
-
[Code Quality] SfxDownloader extract path has no destination-writability pre-check for cached zipsOpenpriority:low type:refactor
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
crazy-goat/workerman-bundle#1052 ·
Maintainers usually reply within 1 day
All issues in crazy-goat/workerman-bundle
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
codeigniter4/CodeIgniter4#10616 ·
Maintainers usually reply within 1 day
-
bug code quality
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SemanticMediaWiki/SemanticMediaWiki#7149 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
google/site-kit-wp#13825 ·
Maintainers usually reply within 3 days
-
Made by AI module: MCP type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day