Skip to content

prevent scheduler crash on non-ASCII DAG/TaskGroup names with OTel metrics enabled#68124

Open
bujjibabukatta wants to merge 2 commits into
apache:mainfrom
bujjibabukatta:fix/#68018
Open

prevent scheduler crash on non-ASCII DAG/TaskGroup names with OTel metrics enabled#68124
bujjibabukatta wants to merge 2 commits into
apache:mainfrom
bujjibabukatta:fix/#68018

Conversation

@bujjibabukatta
Copy link
Copy Markdown
Contributor

Fixes #68018

Addresses all points raised in the previous review:

  • Added missing from ..exceptions import InvalidStatsNameException so the except clause in name_is_otel_safe() correctly catches the exception instead of raising NameError
  • Added TestNameIsOtelSafe regression tests — non-ASCII names return False without raising, valid ASCII names still return True
  • Imported name_is_otel_safe in the test file so the new tests can run

… False instead of crashing scheduler on non-ASCII DAG/TaskGroup names (apache#68018)
@shahar1
Copy link
Copy Markdown
Contributor

shahar1 commented Jun 6, 2026

Could you please rename the PR's title to a meaningful name? (for example, "Fix non-ascii...")

@bujjibabukatta bujjibabukatta changed the title Fix/#68018 prevent scheduler crash on non-ASCII DAG/TaskGroup names with OTel metrics enabled Jun 6, 2026
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.

Scheduler crashes with InvalidStatsNameException for non-ASCII DAG/TaskGroup names when OTel metrics are enabled

2 participants