[go: nahoru, domu]

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

[23.0] celery_extended doesn't update disk usage for work dir outputs. #14055

Draft
wants to merge 1 commit into
base: release_23.0
Choose a base branch
from

Conversation

jmchilton
Copy link
Member

So far just a test case to demonstrate disk usage update for work dir outputs is broken with celery_extended - the test case works by default but fails for celery_extended.

Discovered this working on quota stuff.

Open questions...

  • True of non-work dir outputs?
  • How to fix?

How to test the changes?

(Select all options that apply)

License

@mvdbeek mvdbeek changed the title [WIP] celery_extended doesn't update disk usage for work dir outputs. celery_extended doesn't update disk usage for work dir outputs. Oct 17, 2022
@mvdbeek mvdbeek marked this pull request as draft October 17, 2022 09:02
@github-actions github-actions bot added this to the 23.1 milestone Oct 17, 2022
@dannon dannon changed the title celery_extended doesn't update disk usage for work dir outputs. [23.0] celery_extended doesn't update disk usage for work dir outputs. Jan 23, 2023
@dannon dannon changed the base branch from dev to release_23.0 January 23, 2023 02:07
@classmethod
def handle_galaxy_config_kwds(cls, config):
super().handle_galaxy_config_kwds(config)
config["metadata_strategy"] = "celery_extended"
Copy link
Contributor

Choose a reason for hiding this comment

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

I was just trying this, as suggested by Marius, to see if this was somehow related to a possible issue when using Celery that I'm currently investigating (#15821).

What I found out about this is that when the metadata_strategy is set to directory or directory_celery both test success, and they fail with extended and extended_celery so it seems that Celery is not the cause of this problem but something with the extended metadata strategy itself.

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

2 participants