install:debugbar reads the package folder from the working directory and uses the default storage adapter
Maintainers usually reply within 1 day
@armanist is already working on this.
Since Nov 21, 2026.
Assessment
This issue has not been assessed yet.
Description
Summary
php qt install:debugbar reads the php-debugbar package folder relative to the current working directory and works through the application's default storage adapter, so it fails in two setups where it should publish the assets. A few smaller issues of the same code and of the cache adapters, found while reviewing #687, are fixed alongside.
Problems
- Working directory: the vendor path
vendor/php-debugbar/php-debugbar/resourcesis relative. Run from another folder (cd public && php ../qt install:debugbar), the command throwsFileSystemException("directory does not exist") although the package is installed. Paths should resolve from the application base directory, as the target folder already does throughassets_dir(). - Storage adapter: the command copies local files through
FileSystemFactory::get(), which returns the application's default adapter. Withfs.defaultset todropboxorgdrive, it checks the local vendor folder in the cloud and fails. It should use the local adapter (FileSystemType::LOCAL). - Error message: a file that cannot be copied is reported as "The directory … is not writable", which hides the cause (for example a locked or unreadable file). The message should name the file.
- Typo: "The debug ber already installed" should read "The debug bar is already installed".
- Cache docblocks: the
@methodannotations of theCachefacade are untyped (get($key, $default = null)), while the adapters declare the PSR-16 v3 types, so static analysis acceptscache()->get(42), which throws aTypeError. The*Multiple()methods of the four adapters do not list@throws InvalidCacheKeyException.
Scope
src/Console/Commands/DebugBarCommand.php: vendor path frombase_dir(), the local adapter, a message that names the file, the typo; tests for the first three.src/Cache/Cache.phpand the four cache adapters: docblocks only.
Out of scope
- All-or-nothing behaviour of the
*Multiple()methods: PSR-16 does not require it. - Memcached and an expired TTL: a separate bug that also affects 3.1.x.
- Dominant language
- PHP
- Stars
- 43
- Forks
- 22
- Avg merge
- 54m
- Merged PRs (30d)
- 57
Getting set up
- No Dockerfile or Docker Compose file
- No 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 quantum-php/framework
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
quantum-php/framework#692 ·
Maintainers usually reply within 1 day
-
routing testing
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
quantum-php/framework#547 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 72/100
quantum-php/framework#694 ·
Maintainers usually reply within 1 day
-
refactoring tech debt
Difficulty 5/5 Over a week Newbie friendliness 20/100
quantum-php/framework#693 ·
Maintainers usually reply within 1 day
-
console enhancement
Difficulty 4/5 3-5 days Newbie friendliness 74/100
quantum-php/framework#688 ·
Maintainers usually reply within 1 day
All issues in quantum-php/framework
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
ajeetraina/awesome-docker-sbx#559 ·
-
dependencies enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
novalo-dev/Prestashop-MCP-Server#329 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
bug origin:interactive status:available
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Ultimate-Multisite/ultimate-multisite#2131 ·
Maintainers usually reply within 1 day
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day