Skip to content

fix: add missing f-string prefix in POW registration retry message#921

Open
Grizouforever wants to merge 5 commits intolatent-to:stagingfrom
Grizouforever:fix/registration-retry-fstring
Open

fix: add missing f-string prefix in POW registration retry message#921
Grizouforever wants to merge 5 commits intolatent-to:stagingfrom
Grizouforever:fix/registration-retry-fstring

Conversation

@Grizouforever
Copy link
Copy Markdown

Summary

The POW registration retry message at registration.py:669 is missing the f prefix, causing it to display the literal text {attempts}/{max_allowed_attempts} instead of the actual retry count.

Changes

Add f prefix to the string in bittensor_cli/src/bittensor/extrinsics/registration.py line 669.

Before: :satellite: Failed registration, retrying pow ...({attempts}/{max_allowed_attempts})
After: :satellite: Failed registration, retrying pow ...(2/3)

ibraheem-abe and others added 4 commits March 19, 2026 17:04
The retry message shows literal '{attempts}/{max_allowed_attempts}'
instead of actual values because the string is missing the f prefix.
@thewhaleking thewhaleking changed the base branch from main to staging April 13, 2026 18:58
@thewhaleking
Copy link
Copy Markdown
Contributor

Hi, thanks for the contribution. We require commits to be signed to merge. Please squash and sign for both your prs

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.

3 participants