github-starred/cs249r_book
2
0
Fork 0
mirror of https://github.com/harvard-edge/cs249r_book.git synced 2026-07-15 21:28:33 -05:00
Code Issues 276 Packages Projects Releases 26 Wiki Activity

[GH-ISSUE #1849] [Bug] Community Dashboard Does Not Reflect Synced CLI Progress #35282

New Issue
Open
opened 2026-07-15 22:41:28 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-07-15 22:41:28 -05:00
Owner
Copy Link

Originally created by @pelinbalci on GitHub (Jun 8, 2026).
Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/1849

Area

TinyTorch

Location

TinyTorch Community Dashboard / Progress Sync

Description

I successfully completed Modules 01 and 02 and synced my progress from the TinyTorch CLI.
Authentication via tito community login was successful.

The CLI correctly reports:

            ##   Module                  Status      Next Action                    
         ──────────────────────────────────
            01   01_tensor              ✅ Done      ─                              
            02   02_activations         ✅ Done      ─                              
            03   03_layers             🚀 Working    tito module complete 03        
            04   04_losses             🔒 Locked     Complete module 03 first

However, the Community Dashboard / Journey page still shows:

  • 0% Complete
  • Current Module: 01 Tensors

and does not reflect the synced progress.

I first noticed this issue approximately one week ago and checked again today after successfully authenticating via tito community login. The issue persists and the dashboard still does not reflect the CLI progress.

Expected Behavior

The dashboard should display:

2 completed modules
Current module should be Module 03 (or the next available module)

Environment (TinyTorch bugs only)

TinyTorch: v0.1.12
Python: 3.10.0
Virtual Environment: C:\Users\pelin\projects\tinytorch.venv
OS: Windows
Browsers: Chrome, Microsoft Edge

Image
Originally created by @pelinbalci on GitHub (Jun 8, 2026). Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/1849 ### Area TinyTorch ### Location TinyTorch Community Dashboard / Progress Sync ### Description I successfully completed Modules 01 and 02 and synced my progress from the TinyTorch CLI. Authentication via `tito community login` was successful. The CLI correctly reports: ``` ## Module Status Next Action ────────────────────────────────── 01 01_tensor ✅ Done ─ 02 02_activations ✅ Done ─ 03 03_layers 🚀 Working tito module complete 03 04 04_losses 🔒 Locked Complete module 03 first ``` However, the Community Dashboard / Journey page still shows: - 0% Complete - Current Module: 01 Tensors and does not reflect the synced progress. I first noticed this issue approximately one week ago and checked again today after successfully authenticating via tito community login. The issue persists and the dashboard still does not reflect the CLI progress. ### Expected Behavior The dashboard should display: 2 completed modules Current module should be Module 03 (or the next available module) ### Environment (TinyTorch bugs only) TinyTorch: v0.1.12 Python: 3.10.0 Virtual Environment: C:\Users\pelin\projects\tinytorch\.venv OS: Windows Browsers: Chrome, Microsoft Edge <img width="1812" height="829" alt="Image" src="https://github.com/user-attachments/assets/803d7a28-dd2a-4b70-bdaa-1dd188a87c25" />
GiteaMirror added the area: tinytorchpriority-hightype: bug labels 2026-07-15 22:41:29 -05:00
GiteaMirror commented 2026-07-15 22:41:31 -05:00
Author
Owner
Copy Link

@Huaian666 commented on GitHub (Jun 12, 2026):

confirmed on my end. ubuntu 22.04 if that helps narrow it down

<!-- gh-comment-id:4692048311 --> @Huaian666 commented on GitHub (Jun 12, 2026): confirmed on my end. ubuntu 22.04 if that helps narrow it down
GiteaMirror commented 2026-07-15 22:41:31 -05:00
Author
Owner
Copy Link

@choyrim commented on GitHub (Jun 15, 2026):

yes, I am experiencing the same issue using tito v0.1.12 on windows bash. journey on dashboard does not match local module status.

<!-- gh-comment-id:4704655838 --> @choyrim commented on GitHub (Jun 15, 2026): yes, I am experiencing the same issue using tito v0.1.12 on windows bash. journey on dashboard does not match local module status.
GiteaMirror commented 2026-07-15 22:41:32 -05:00
Author
Owner
Copy Link

@profvjreddi commented on GitHub (Jun 15, 2026):

Hey folks, thanks for letting me know. We'll take a look into it.

<!-- gh-comment-id:4708973706 --> @profvjreddi commented on GitHub (Jun 15, 2026): Hey folks, thanks for letting me know. We'll take a look into it.
GiteaMirror commented 2026-07-15 22:41:32 -05:00
Author
Owner
Copy Link

@profvjreddi commented on GitHub (Jun 15, 2026):

Update: I found a cause on the CLI side for this, and I am working on it.

The automatic sync (the prompt after tito module complete) was being skipped on any terminal where Python sees stdin as a non interactive stream. On Windows Git Bash and MinTTY, and in some IDE terminals, sys.stdin.isatty() returns False even in a real interactive session, so the local module status updated correctly but nothing was ever uploaded, and no error was shown. That matches the Windows reports here, and likely the others depending on terminal setup.

Fix in progress on branch fix/tito-progress-sync:

  1. Sync no longer depends on having a TTY. A logged in user always syncs; only the confirmation prompt is skipped when there is no usable terminal.
  2. Added tito community sync so anyone can upload their progress again on demand, and login now offers to sync progress that was completed before signing in.
  3. The CLI now shows an honest warning when the server accepts an upload but does not confirm it was saved, instead of always printing success.

@kai4avaya one open question is on the backend. The upload-progress and get-profile-details functions live in Supabase, not in this repo, so I could not check them here. Could you look at whether uploads from these users actually landed, and whether synced_modules is coming back null on a 2xx response? That tells us if a server side fix is also needed. Happy to pair on it.

<!-- gh-comment-id:4710740884 --> @profvjreddi commented on GitHub (Jun 15, 2026): Update: I found a cause on the CLI side for this, and I am working on it. The automatic sync (the prompt after `tito module complete`) was being skipped on any terminal where Python sees stdin as a non interactive stream. On Windows Git Bash and MinTTY, and in some IDE terminals, `sys.stdin.isatty()` returns False even in a real interactive session, so the local module status updated correctly but nothing was ever uploaded, and no error was shown. That matches the Windows reports here, and likely the others depending on terminal setup. Fix in progress on branch `fix/tito-progress-sync`: 1. Sync no longer depends on having a TTY. A logged in user always syncs; only the confirmation prompt is skipped when there is no usable terminal. 2. Added `tito community sync` so anyone can upload their progress again on demand, and login now offers to sync progress that was completed before signing in. 3. The CLI now shows an honest warning when the server accepts an upload but does not confirm it was saved, instead of always printing success. @kai4avaya one open question is on the backend. The `upload-progress` and `get-profile-details` functions live in Supabase, not in this repo, so I could not check them here. Could you look at whether uploads from these users actually landed, and whether `synced_modules` is coming back null on a 2xx response? That tells us if a server side fix is also needed. Happy to pair on it.
GiteaMirror commented 2026-07-15 22:41:33 -05:00
Author
Owner
Copy Link

@kai4avaya commented on GitHub (Jun 15, 2026):

Hi Team,
I'll check on this.

@pelinbalci are you able to share your TinyTorch login name with me so I can also check your account.

<!-- gh-comment-id:4710945569 --> @kai4avaya commented on GitHub (Jun 15, 2026): Hi Team, I'll check on this. @pelinbalci are you able to share your TinyTorch login name with me so I can also check your account.
GiteaMirror commented 2026-07-15 22:41:33 -05:00
Author
Owner
Copy Link

@pelinbalci commented on GitHub (Jun 16, 2026):

Hi Team, I'll check on this.

@pelinbalci are you able to share your TinyTorch login name with me so I can also check your account.

Hello, thank you for your help. My login name is: balci.pelin

<!-- gh-comment-id:4715860142 --> @pelinbalci commented on GitHub (Jun 16, 2026): > Hi Team, I'll check on this. > > [@pelinbalci](https://github.com/pelinbalci) are you able to share your TinyTorch login name with me so I can also check your account. Hello, thank you for your help. My login name is: balci.pelin
GiteaMirror commented 2026-07-15 22:41:34 -05:00
Author
Owner
Copy Link

@Chufeng-Jiang commented on GitHub (Jun 17, 2026):

Same here!

Display name is: Chufeng_Jiang

userID is jiangchufengjcf@gmail.com

Thanks!

<!-- gh-comment-id:4725665638 --> @Chufeng-Jiang commented on GitHub (Jun 17, 2026): Same here! Display name is: Chufeng_Jiang userID is jiangchufengjcf@gmail.com Thanks!
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 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#35282
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?