github-starred/cs249r_book
2
0
Fork 0
mirror of https://github.com/harvard-edge/cs249r_book.git synced 2026-07-16 23:24:55 -05:00
Code Issues 276 Packages Projects Releases 26 Wiki Activity

[GH-ISSUE #1612] [Bug] tito module status wrong milestone 3 advertisement #10816

New Issue
Closed
opened 2026-05-12 18:49:58 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-12 18:49:58 -05:00
Owner
Copy Link

Originally created by @AndreaMattiaGaravagno on GitHub (Apr 30, 2026).
Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/1612

Area

TinyTorch

Location

tito module status

Description

tito module status advertises milestone 3 as ready to be unlocked after module 6, even if you still need to complete modules 7 and 8

Expected Behavior

tito module status should advertise milestone 3 as ready to be unlocked after module 8 completion

Environment (TinyTorch bugs only)

Tiny🔥Torch v0.1.10
Python 3.12.3
/home/andre/tinytorch/.venv

Originally created by @AndreaMattiaGaravagno on GitHub (Apr 30, 2026). Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/1612 ### Area TinyTorch ### Location tito module status ### Description tito module status advertises milestone 3 as ready to be unlocked after module 6, even if you still need to complete modules 7 and 8 ### Expected Behavior tito module status should advertise milestone 3 as ready to be unlocked after module 8 completion ### Environment (TinyTorch bugs only) Tiny🔥Torch v0.1.10 Python 3.12.3 /home/andre/tinytorch/.venv
GiteaMirror added the javascripttype: bugpriority-higharea: tinytorch labels 2026-05-12 18:49:58 -05:00
GiteaMirror commented 2026-05-12 18:50:01 -05:00
Author
Owner
Copy Link

@profvjreddi commented on GitHub (Apr 30, 2026):

Fixed in #1616 (merged to dev as 7ba91628e). Stale duplicate of milestone→modules map in _check_milestone_readiness was saying M3 needed [1..6] instead of [1..8]. Same drift hit M4/M5/M6 (missing module 7 and/or 8). Aligned to canonical MILESTONE_SCRIPTS table.

<!-- gh-comment-id:4356772824 --> @profvjreddi commented on GitHub (Apr 30, 2026): Fixed in #1616 (merged to dev as 7ba91628e). Stale duplicate of milestone→modules map in `_check_milestone_readiness` was saying M3 needed [1..6] instead of [1..8]. Same drift hit M4/M5/M6 (missing module 7 and/or 8). Aligned to canonical `MILESTONE_SCRIPTS` table.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area: book
area: collabs
area: kits
area: labs
area: socratiq
area: staffml
area: tinytorch
area: tools
area: website
bug
dependencies
format: epub
format: pdf
javascript
link-health
link-rot
priority-high
pull-request
Mirrored from GitHub Pull Request
 staffml
type: bug
type: citation
type: code
type: errata
type: improvement
type: new
type: question
vault-sli
No Label area: tinytorch javascript priority-high type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/cs249r_book#10816
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?