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

Fixes issue with the worker defaulting to the illuminate queue manager #2481

Merged
merged 3 commits into from
Dec 2, 2020

Conversation

luceos
Copy link
Member

@luceos luceos commented Dec 1, 2020

We are instantiating our own queue handling factory which returns the
flarum.queue.connection binding no matter what. The queue Worker and
other queue related code rely on this manager to get its thing going.
Therefor we need to re-use our own factory everywhere, including in
the worker.

luceos and others added 2 commits December 1, 2020 20:03
We are instantiating our own queue handling factory which returns the
flarum.queue.connection binding no matter what. The queue Worker and
other queue related code rely on this manager to get its thing going.
Therefor we need to re-use our own factory everywhere, including in
the worker.
[ci skip] [skip ci]
@askvortsov1
Copy link
Sponsor Member

Tests are failing?

@askvortsov1
Copy link
Sponsor Member

I suspect that the failing tests were fixed in 984f751, rebasing might help here.

@luceos
Copy link
Member Author

luceos commented Dec 2, 2020

Yeah that fixed it 👍

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

Successfully merging this pull request may close these issues.

3 participants