-
-
Notifications
You must be signed in to change notification settings - Fork 719
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
Fix doc build #8892
Fix doc build #8892
Conversation
still failing. FWIW I'm also fine with nuking the in-comment typing. We have type annotations and they are also rendered in sphinx. We don't have a consistent style guideline for this |
I've just removed it for now to get doc build passing
…On Tue, Oct 15, 2024 at 12:25 PM Florian Jetter ***@***.***> wrote:
still failing. FWIW I'm also fine with nuking the in-comment typing. We
have type annotations and they are also rendered in sphinx. We don't have a
consistent style guideline for this
—
Reply to this email directly, view it on GitHub
<#8892 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOYQZGEGK5IIXP6EFLE2YQLZ3TUPZAVCNFSM6AAAAABP6YAOSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJTGQ4TQMZQHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I actually think that the type hint is the problem :( |
This reverts commit 8d69b28.
We actually have 2 WorkerState classes, which is something that confuses Spinx. I clarified the import now, so things are good |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
Closes #xxxx
pre-commit run --all-files