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.

Sign up for GitHub

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

Jump to bottom

Celery process raises dbm.error #1491

Closed
mikkonie opened this issue Sep 9, 2024 · 1 comment
Closed

Celery process raises dbm.error #1491

mikkonie opened this issue Sep 9, 2024 · 1 comment
Assignees
@mikkonie
Labels
bug Something isn't working environment Issues of dependencies, CI, deployment etc.
Milestone
v1.0.2

Comments

@mikkonie
Copy link
Collaborator

mikkonie commented Sep 9, 2024 •
edited
Loading

Running make celery outputs the following error in dev:

dbm.error: db type is dbm.gnu, but the module is not available

This can be fixed by adding python3.11-gdbm into system dependencies. I'll also have to do it for the Docker env.
@mikkonie mikkonie added the environment Issues of dependencies, CI, deployment etc. label Sep 9, 2024
@mikkonie mikkonie added this to the v1.0.2 milestone Sep 9, 2024
@mikkonie mikkonie self-assigned this Sep 9, 2024
@mikkonie mikkonie changed the title Ensure Celery process works as intended after v1.0 upgrades Celery process raises dbm.error Sep 9, 2024
@mikkonie mikkonie added the bug Something isn't working label Sep 9, 2024
mikkonie added a commit that referenced this issue Sep 9, 2024
@mikkonie
fix celery warnings (#1491, #1493)
c56a958
@mikkonie
Copy link
Collaborator Author

mikkonie commented Sep 9, 2024

Fixed.

@mikkonie mikkonie closed this as completed Sep 9, 2024
@mikkonie mikkonie mentioned this issue Sep 9, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mikkonie mikkonie

Labels
bug Something isn't working environment Issues of dependencies, CI, deployment etc.
Projects
None yet
Milestone
v1.0.2
Development

No branches or pull requests
1 participant
@mikkonie