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

Pypi package 0.11.0 broken #123

Closed
milonline-eu opened this issue Jun 13, 2022 · 5 comments
Closed

Pypi package 0.11.0 broken #123

milonline-eu opened this issue Jun 13, 2022 · 5 comments

Comments

@milonline-eu
Copy link

It seems like pypi 0.11.0 package is broken. It doesn't follow settings for a RabbitMQ server and uses 127.0.0.1 instead.
@crios586
Copy link

@milonline-eu
It seems the package is setup to be used with RabbitMQ locally.
Which is why it is configured to use the local host IP Address (127.0.0.1) and rabbitmq-server default port (5672), according to the readme.
If you have your RabbitMQ server running somewhere else, try changing the IP address and maybe port accordingly.

@q0w
Copy link

q0w commented Jul 24, 2022

I also get errors like this Bogdanp/dramatiq#168 with 0.11.0 only, redis backend

@yuzhay
Copy link

yuzhay commented Jul 30, 2022

It seems like pypi 0.11.0 package is broken. It doesn't follow settings for a RabbitMQ server and uses 127.0.0.1 instead.

Redis as well

@skorokithakis
Copy link

I am seeing the inability to find actors as well. It appears that the broker is being reinitialized between modules.

amureki added a commit to codingjoe/joeflow that referenced this issue Oct 28, 2022
@amureki
Pin django-dramatiq instead of dramatiq version
b5d833e 
I believe, the core problem was in django_dramatiq package:
Bogdanp/django_dramatiq#123
Version 0.11 is not fully uploaded to PyPI or there is a bug in that version.

Also, there are no incompatibility issues raised in dramatiq repo:
https://github.com/Bogdanp/dramatiq/issues

Thus, I am changing pins in this PR to freeze django-dramatiq package.
@amureki amureki mentioned this issue Oct 28, 2022
Merged
amureki added a commit to codingjoe/joeflow that referenced this issue Oct 28, 2022
@amureki
Pin django-dramatiq instead of dramatiq version
36f4a61 
I believe, the core problem was in django_dramatiq package:
Bogdanp/django_dramatiq#123
Version 0.11 is not fully uploaded to PyPI or there is a bug in that version.

Also, there are no incompatibility issues raised in dramatiq repo:
https://github.com/Bogdanp/dramatiq/issues

Thus, I am changing pins in this PR to freeze django-dramatiq package.
codingjoe pushed a commit to codingjoe/joeflow that referenced this issue Oct 28, 2022
@amureki @codingjoe
Pin django-dramatiq instead of dramatiq version
e331179 
I believe, the core problem was in django_dramatiq package:
Bogdanp/django_dramatiq#123
Version 0.11 is not fully uploaded to PyPI or there is a bug in that version.

Also, there are no incompatibility issues raised in dramatiq repo:
https://github.com/Bogdanp/dramatiq/issues

Thus, I am changing pins in this PR to freeze django-dramatiq package.
This was referenced Oct 31, 2022
Closed
Merged
Bogdanp pushed a commit that referenced this issue Nov 5, 2022
@amureki @Bogdanp
Test scenario for #123
f66c22c 
This commit itself will break test suite, so we can later address issue in #123.
This bug was introduced in #103 where django_dramatiq started benefitting from `AppConfig.ready()` functionality.
There was a research done in #100 explaining the underlying issue.
@Bogdanp Bogdanp closed this as completed in 1d7911b Nov 5, 2022
@amureki
Copy link
Collaborator

amureki commented Nov 11, 2022

@milonline-eu happy to announce that 0.11.1 is released!
It should resolve this issue.

Best,
Rust

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@skorokithakis @amureki @yuzhay @milonline-eu @q0w @crios586