On the live HTML page for Data Engineering, just above Definition 1.1 , figure/table references are not resolved correctly. I was just looking where I had left off the last time, so I think this is new.
Expected Behavior
There should probably be links to tthe figures
Environment (TinyTorch bugs only)
No response
Originally created by @asgalon on GitHub (May 22, 2026).
Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/1794
### Area
Book — Volume I
### Location
Data Engineering
### Description
On the live HTML page for [Data Engineering](https://mlsysbook.ai/vol1/contents/vol1/data_engineering/data_engineering.html), just above Definition 1.1 , figure/table references are not resolved correctly. I was just looking where I had left off the last time, so I think this is new.
<img width="1781" height="709" alt="Image" src="https://github.com/user-attachments/assets/1b08d93d-27ba-482b-817f-4f221eaee0ef" />
### Expected Behavior
There should probably be links to tthe figures
### Environment (TinyTorch bugs only)
_No response_
Same effect is visible on other pages, such as ML Workflow just under ML Workflow Lifecycle:
"ML systems are composed of the three interacting elements shown in ?@fig-ai-triad: Data,"
The browser is the current Firefox on OSX. Same in Chrome.
<!-- gh-comment-id:4518179084 -->
@asgalon commented on GitHub (May 22, 2026):
Same effect is visible on other pages, such as ML Workflow just under ML Workflow Lifecycle:
"ML systems are composed of the three interacting elements shown in **?@fig-ai-triad**: Data,"
The browser is the current Firefox on OSX. Same in Chrome.
Thans for catching these, I did resolve them in the dev branch, and will push an update to the live site soon!
<!-- gh-comment-id:4519539841 -->
@profvjreddi commented on GitHub (May 22, 2026):
Thans for catching these, I did resolve them in the `dev` branch, and will push an update to the live site soon!
The three cross-references (@sec-ml-workflow, @fig-ds-time, @tbl-dam-taxonomy) are all valid and exist within vol1. The broken rendering on the live site is a stale-build artifact — our resolve_cross_references.py post-render script handles cross-chapter refs, and a clean rebuild + deploy will resolve them. Leaving open until confirmed on the live site after next deploy.
<!-- gh-comment-id:4534969436 -->
@profvjreddi commented on GitHub (May 25, 2026):
The three cross-references (`@sec-ml-workflow`, `@fig-ds-time`, `@tbl-dam-taxonomy`) are all valid and exist within vol1. The broken rendering on the live site is a stale-build artifact — our `resolve_cross_references.py` post-render script handles cross-chapter refs, and a clean rebuild + deploy will resolve them. Leaving open until confirmed on the live site after next deploy.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @asgalon on GitHub (May 22, 2026).
Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/1794
Area
Book — Volume I
Location
Data Engineering
Description
On the live HTML page for Data Engineering, just above Definition 1.1 , figure/table references are not resolved correctly. I was just looking where I had left off the last time, so I think this is new.
Expected Behavior
There should probably be links to tthe figures
Environment (TinyTorch bugs only)
No response
@asgalon commented on GitHub (May 22, 2026):
Same effect is visible on other pages, such as ML Workflow just under ML Workflow Lifecycle:
"ML systems are composed of the three interacting elements shown in ?@fig-ai-triad: Data,"
The browser is the current Firefox on OSX. Same in Chrome.
@profvjreddi commented on GitHub (May 22, 2026):
Thans for catching these, I did resolve them in the
devbranch, and will push an update to the live site soon!@profvjreddi commented on GitHub (May 25, 2026):
The three cross-references (
@sec-ml-workflow,@fig-ds-time,@tbl-dam-taxonomy) are all valid and exist within vol1. The broken rendering on the live site is a stale-build artifact — ourresolve_cross_references.pypost-render script handles cross-chapter refs, and a clean rebuild + deploy will resolve them. Leaving open until confirmed on the live site after next deploy.