-
Notifications
You must be signed in to change notification settings - Fork 127
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
Error when publishing to GitHub Pages #820
Comments
I tried to use the new toolchain
to build the DocCTest documentation for GitHub Pages.
messages when looking at the generated documentation, as you will see if you click https://leif-ibsen.github.io/DocCTest/documentation/docctest There were no errors during the build but many warnings like
|
The error occurs when you click the following operators: / /= % %= < <= > >= << <<= >> >>= | |= ^ ^= ~ The following operators work ok:
|
The bug is documented and can be reproduced at this location: https://leif-ibsen.github.io/DocCTest/documentation/docctest The DocCTest source code is here: |
I don't know how I can reproduce this. If I build documentation for that repo with the Xcode 15.3 release build I can view all those pages. At first I thought that it could be an issue with the static hosting files being different but if I locally serve the built documentation with |
If I preview the documentation (using Xcode 15.3) with the command
everything work okay. I can see all the pages locally on my computer. However, if I build for GitHub Pages (also using Xcode 15.3) with the command
and then push the build to GitHub, then the error occurs. Look at the documentation
and if you click, say the BInt operator /, you should see
That's what I experience. |
If I preview the documentation (using Xcode 15.3) with the command
swift package --disable-sandbox preview-documentation --target DocCTest
everything work okay. I can see all the pages locally on my computer.
However, if I build for GitHub Pages (also using Xcode 15.3) with the command
swift package --allow-writing-to-directory ./docs generate-documentation \
--target DocCTest --disable-indexing --transform-for-static-hosting \
--hosting-base-path DocCTest --output-path ./docs
and then push the build to GitHub, then the error occurs. Look at the documentation
at the location
https://leif-ibsen.github.io/DocCTest/documentation/docctest
and if you click, say the BInt operator /, you should see
The page you're looking for can't be found.
That's what I experience.
… Den 8. mar. 2024 kl. 16.07 skrev David Rönnqvist ***@***.***>:
I don't know how I can reproduce this.
If I build documentation for that repo with the Xcode 15.3 release build I can view all those pages. At first I thought that it could be an issue with the static hosting files being different but if I locally serve the built documentation with python3 -m http.server 8080 I can still browse all those pages.
—
Reply to this email directly, view it on GitHub <#820 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANEVD3A62VBQTA2WKYXHV6DYXHHZZAVCNFSM6AAAAABDBKUHF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBVHA2TSMZXGA>.
You are receiving this because you authored the thread.
|
The issue is marked with 'needs more information'. As I have explained, if I build the documentation and view it locally on my PC, However, when the documentation is pushed to GitHub Pages and viewed there, I have documented that at the location
Is there more information I can provide to help solve this? The operators that produce the error on GitHub Pages, are: / /= % %= | |= ^ ^= ~ << <<= >> >>= < <= > >= |
Description
The problem is described in issue #808.
Please, see my last comment from 8. of february in that issue.
Checklist
main
branch of this package.Expected Behavior
The bug is documented and can be reproduced at this location:
https://leif-ibsen.github.io/DocCTest/documentation/docctest
Actual behavior
Steps To Reproduce
The bug is documented and can be reproduced at this location:
https://leif-ibsen.github.io/DocCTest/documentation/docctest
Swift-DocC Version Information
No response
Swift Compiler Version Information
No response
The text was updated successfully, but these errors were encountered: