Skip to content

[draft][ENG-12182] fix: more consistent naming of celery tasks - #11916

Draft
aaxelb wants to merge 1 commit into
CenterForOpenScience:developfrom
aaxelb:fix/low-pri-task-names
Draft

[draft][ENG-12182] fix: more consistent naming of celery tasks#11916
aaxelb wants to merge 1 commit into
CenterForOpenScience:developfrom
aaxelb:fix/low-pri-task-names

Conversation

@aaxelb

@aaxelb aaxelb commented Sep 11, 2026

Copy link
Copy Markdown
Collaborator

Ticket

Purpose

for celery tasks defined under osf/management/commands/, use task names that begin with the full python module path (use celery's default task name in most cases)

specifically, this fixes a problem where tasks were expected to be "low priority" based on matching CeleryConfig.low_pri_modules, but would instead go in the default queue

Changes

low_pri_modules entries with mismatched task names that went to the default queue instead:

  • osf.management.commands.daily_reporters_go
  • osf.management.commands.delete_withdrawn_or_failed_registration_files
  • osf.management.commands.ingest_cedar_metadata_templates (note: not an actual module, just a task name)
  • osf.management.commands.migrate_deleted_date
  • osf.management.commands.migrate_pagecounter_data
  • osf.management.commands.monthly_reporters_go
  • osf.management.commands.populate_branched_from (note: not an actual module, just a task name)

Side Effects

QE Notes

CE Notes

Documentation

for celery tasks defined under `osf/management/commands/`, use task
names that begin with the full python module path (use celery's
default task name in most cases)

specifically, this fixes a problem where tasks were expected to be "low
priority" based on matching `CeleryConfig.low_pri_modules`, but would
instead go in the default queue
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 this pull request may close these issues.

1 participant