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 fanout to filesystem #1499

Merged
merged 7 commits into from Mar 15, 2022
Merged

Conversation

karajan1001
Copy link
Contributor

Looks like #1280 is stale?

filesystem transport lacks of fanout support.

  1. Add fanout support to filesystem transport.
  2. Add a unit test for it.

@lgtm-com
Copy link

lgtm-com bot commented Mar 3, 2022

This pull request introduces 1 alert when merging 06fb0e5 into 22adaaa - view on LGTM.com

new alerts:

  • 1 for Unused import

Copy link
Member

@thedrow thedrow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for contributing the tests. Please address @matusvalo's code review in #1280 and we can move ahead with merging this PR.

filesystem transport lacks of fanout support.

1. Add fanout support to filesystem transport.
2. Add a unit test for it.
@karajan1001
Copy link
Contributor Author

BTW, the modifications between this PR and the #1280 are not a small one. So maybe the previous review will play only a limited role?

@matusvalo
Copy link
Member

matusvalo commented Mar 7, 2022

I have added feedback but:

  1. unittests are failing - did not go in deep why but they need to be fixed
  2. The PR contains also formatting changes. They should be not part of this PR.

1. Remove all of refactoring work
2. make the test pass

@contextmanager
def _get_exchange_file_obj(self, exchange, mode="rb"):
file = self.control_folder / f"{exchange}.exchange"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use pathlib for path management. but didn't expand this to other parts.

@matusvalo
Copy link
Member

LGTM for me except two small points:

  • control_folder is not documented in docstring in the beginning of the file.
  • I am not 100% sure whether @cachedproperty on top of control_folder is good idea. We had several problems with cached_property. Is there any reason to have it there? Does it make sense to have there only @property instead?

Copy link
Member

@auvipy auvipy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

control_folder is not documented in docstring in the beginning of the file.
I am not 100% sure whether @cachedproperty on top of control_folder is good idea. We had several problems with cached_property. Is there any reason to have it there? Does it make sense to have there only @property instead?

@karajan1001 karajan1001 requested a review from auvipy March 15, 2022 09:18
@auvipy auvipy merged commit 0282e14 into celery:master Mar 15, 2022
@matusvalo
Copy link
Member

Thank you @karajan1001 !

@karajan1001
Copy link
Contributor Author

Excuse me, is there any schedule for the next release?

@thedrow
Copy link
Member

thedrow commented Apr 14, 2022

Not yet but I'm working on it.

@pmrowla
Copy link

pmrowla commented May 18, 2022

@thedrow are there any updates on when the next kombu release will be available? We are getting close to being ready to release our own downstream product that depends on this feature

@auvipy
Copy link
Member

auvipy commented May 18, 2022

@thedrow are there any updates on when the next kombu release will be available? We are getting close to being ready to release our own downstream product that depends on this feature

wait next week please

@pmrowla
Copy link

pmrowla commented Jun 1, 2022

@auvipy any updates?

@auvipy
Copy link
Member

auvipy commented Jun 1, 2022

this week or week end for sure

@pmrowla
Copy link

pmrowla commented Jun 21, 2022

@auvipy I see that the 5.3 milestone for celery+kombu keeps getting pushed back, is there any chance we could just get a limited 5.2.x kombu release with this patch included?

@auvipy
Copy link
Member

auvipy commented Jun 21, 2022

@auvipy I see that the 5.3 milestone for celery+kombu keeps getting pushed back, is there any chance we could just get a limited 5.2.x kombu release with this patch included?

no, 5.3a1 this week.

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

Successfully merging this pull request may close these issues.

None yet

6 participants