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

Add support for the async Active Job backend used by default in Rails #32

Closed
rosa opened this issue Jan 29, 2024 · 1 comment · Fixed by #195
Closed

Add support for the async Active Job backend used by default in Rails #32

rosa opened this issue Jan 29, 2024 · 1 comment · Fixed by #195

Comments

@rosa
Copy link
Member

rosa commented Jan 29, 2024

Mostly so that this can be run in development, even if it's not super useful.

@matiassalles99
Copy link
Contributor

matiassalles99 commented Apr 13, 2024

What's the expected behavior with the async Active Job adapter? From what I saw it doesn't support most (if not any) of the features, it seems to work with one queue only but it has no name, and you can only access the number of completed jobs.

I might be wrong but those were my main takeaways from looking into the async adapter source code, and I just want to fully understand the expected behavior before working on the integration with mission-control :)

rosa added a commit that referenced this issue Nov 6, 2024
So that it doesn't crash when started for an app using the async adapter
in development.

Closes #32
@rosa rosa closed this as completed in #195 Nov 6, 2024
rosa added a commit that referenced this issue Nov 6, 2024
So that it doesn't crash when started for an app using the async adapter
in development.

Closes #32
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 a pull request may close this issue.

2 participants