Skip to content

Comments

Truncate large coro repr in retry log output#9197

Open
ernestprovo23 wants to merge 1 commit intodask:mainfrom
ernestprovo23:fix-retry-excessive-logs
Open

Truncate large coro repr in retry log output#9197
ernestprovo23 wants to merge 1 commit intodask:mainfrom
ernestprovo23:fix-retry-excessive-logs

Conversation

@ernestprovo23
Copy link

Summary

  • When retry() falls back to str(coro) for log messages, truncate the representation to 200 characters to prevent excessively large logs
  • This was observed in P2P shuffles where functools.partial repr includes serialized binary data (see Fix excessive logging on P2P retry #8511)
  • Added test verifying truncation behavior

Closes #8529

Test plan

  • New test test_retry_truncates_large_coro_repr verifies 500-char repr is truncated
  • Existing retry tests unaffected (no truncation when repr is small)
  • Explicit operation parameter bypasses truncation (preserves full user-provided descriptions)

🤖 Generated with Claude Code

When retry() falls back to str(coro) for the log message, truncate
the representation to 200 characters to prevent excessively large
logs. This was observed in P2P shuffles where functools.partial repr
includes serialized binary data.

Closes dask#8529
@github-actions
Copy link
Contributor

Unit Test Results

See test report for an extended history of previous test failures. This is useful for diagnosing flaky tests.

    31 files  ± 0      31 suites  ±0   11h 16m 57s ⏱️ + 9m 23s
 4 114 tests + 1   4 008 ✅ + 3    104 💤 ±0  2 ❌  - 2 
59 651 runs  +15  57 175 ✅ +18  2 474 💤 ±0  2 ❌  - 3 

For more details on these failures, see this check.

Results for commit 30ddcdc. ± Comparison against base commit 4fb4814.

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.

retry can produce excessively large logs

1 participant