Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

php artisan queue:failed-table is failing. (Affects every Illuminate\Console\MigrationGeneratorCommand). #1273

Closed
Kudze opened this issue Dec 17, 2023 · 3 comments

Comments

@Kudze
Copy link

Kudze commented Dec 17, 2023

Lumen Version

10.0.2

PHP Version

8.3.0

Database Driver & Version

No response

Description

CLI queue:failed-table fails to execute on (10.x). (Did not check from which version its broken)

image

I did some initial digging and the reason for it to not execute is because there is no joinPathsmethod in Lumen Application class. However, joinPaths method exists in Laravel Application class.

This method is being used from MigrationGeneratorCommand.

I would love an opportunity to appear in contributors list, therefore I could push pull request that resolves this issue.

By the way, the method is not mentioned in ApplicationContract. Maybe it should be mentioned inside contract if its used from another composer package?

So I would just add joinPaths methods to Lumen Application class. (I would also update other path functions to utilise this function when merging paths like in Laravel Application class)

Steps To Reproduce

  1. Create new lumen project: composer create-project --prefer-dist laravel/lumen blog
  2. Execute the (example) cli: php artisan queue:failed-table
@driesvints
Copy link
Member

We'd appreciate a PR here 👍

By the way, the method is not mentioned in ApplicationContract. Maybe it should be mentioned inside contract if it's used from another composer package?

I don't think we should take immediate action here.

Copy link

Thank you for reporting this issue!

As Laravel is an open source project, we rely on the community to help us diagnose and fix issues as it is not possible to research and fix every issue reported to us via GitHub.

If possible, please make a pull request fixing the issue you have described, along with corresponding tests. All pull requests are promptly reviewed by the Laravel team.

Thank you!

@crynobone
Copy link
Member

Hi there,

Can you please upgrade to latest console and filesystem releases, this issue should be fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants