-
Notifications
You must be signed in to change notification settings - Fork 0
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 md files causing github pages to fail #178
Comments
I used kramdown to test which md files have difficulty being converted into html files, upon reading kramdown is one of the ways github pages convert md files to html. This is the ruby script I used:
Based on this, there were 4 html files that caused "stack level too deep" errors. I tested removing a significant portion of one these files and that was able to generate html files. These are the 4 files:
I removed these 4 files and tested my branch. I noticed that pages build-and-deployment workflow is passing successfully: link However, there are 2 questions:
|
Things seem to be working now that I added index.md under docs: https://docs.tenstorrent.com/tt-torch/ A couple remarks:
The successful workflow is here |
There are certain md pages breaking github pages build-and-deployment. These can be tested using kramdown, md to html converter. generate_md.py is changed to address this. Now, md files have tables with 600 rows max, and each file size is 500MB max (due to github pre-commit). After hitting these restrictions, a new file is created. Furthermore, github pages landing page is added (docs/index.md)
There are certain md pages breaking github pages build-and-deployment. These can be tested using kramdown, md to html converter. generate_md.py is changed to address this. Now, md files have tables with 600 rows max, and each file size is 500MB max (due to github pre-commit). After hitting these restrictions, a new file is created. Furthermore, github pages landing page is added (docs/index.md)
There are certain md pages breaking github pages build-and-deployment. These can be tested using kramdown, md to html converter. generate_md.py is changed to address this. Now, md files have tables with 600 rows max, and each file size is 500MB max (due to github pre-commit). After hitting these restrictions, a new file is created. Furthermore, github pages landing page is added (docs/index.md)
There are certain md pages breaking github pages build-and-deployment. These can be tested using kramdown, md to html converter. generate_md.py is changed to address this. Now, md files have tables with 600 rows max, and each file size is 500MB max (due to github pre-commit). After hitting these restrictions, a new file is created. Furthermore, github pages landing page is added (docs/index.md)
There are certain md pages breaking github pages build-and-deployment. These can be tested using kramdown, md to html converter. generate_md.py is changed to address this. Now, md files have tables with 600 rows max, and each file size is 500MB max (due to github pre-commit). After hitting these restrictions, a new file is created. Furthermore, github pages landing page is added (docs/index.md)
There are certain md pages breaking github pages build-and-deployment. These can be tested using kramdown, md to html converter. - generate_md.py changed - md files have tables with max 600 rows. - pre-commit large file check removed. - landing page added (docs/index.md)
There are certain md pages breaking github pages build-and-deployment. These can be tested using kramdown, md to html converter. - generate_md.py changed - md files have tables with max 600 rows. - pre-commit large file check removed. - landing page added (docs/index.md)
@vmilosevic has enabled tt-torch github pages to be deployed from
ddilbaz/fix-pages-build-and-deployment
Therefore, we can make changes to this branch and trigger a pages build which can help with debugging. This issue is related to #169md files seem to result in "Stack level too deep" error after ~600 rows in md tables. Should adjust generate_md.py to fix this. The solution is to have multiple tables back to back with each having ~600 rows (no headers in between)
Tagging @AleksKnezevic for reference
The text was updated successfully, but these errors were encountered: