-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[DOCS] Fix Sphinx Warning: the target found for cross-reference #4925
Conversation
The log shows 25 warnings including 4 undefined labels. Could you take a look and fix them? Other major warnings are related to lex python. You can also try to fix it, or I’ll take a look next week. Sent with GitHawk |
Hi @comaniac Thanks for the review. I solve the undefined label warnings and the output file as shown below link: https://gist.github.com/cchung100m/f8bdef470b1a41c2408895610ee3b03e |
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.
LGTM. I verified this PR locally and now we only have 3 warnings left:
WARNING: error while formatting arguments for tvm.relay.op.OpPattern: <class 'tvm.relay.op.op.OpPattern'> is a builtin class
WARNING: error while formatting arguments for tvm.intrin: module 'tvm.intrin' has no attribute '__mro__'
WARNING: error while formatting arguments for tvm.relay.vision.nms: module 'tvm.relay.op.vision.nms' has no attribute '__mro__'
@tqchen PTAL.
Thansk @comaniac @cchung100m |
…he#4925) * [DOCS] Fix Sphinx Warnings: the target found for cross-reference warnings * Fix the warning: undefined label
…he#4925) * [DOCS] Fix Sphinx Warnings: the target found for cross-reference warnings * Fix the warning: undefined label
…he#4925) * [DOCS] Fix Sphinx Warnings: the target found for cross-reference warnings * Fix the warning: undefined label
…he#4925) * [DOCS] Fix Sphinx Warnings: the target found for cross-reference warnings * Fix the warning: undefined label
Hi @tqchen @comaniac
Following issue #4908 and our discussion, this PR is going to fix the following two errors
I would appreciate that if you could help to review/manage it, thanks.