Hey awesome dashboard!! Suggestion to add a print statement in cli.py right before the scan starts print("Token Dashboard: scanning projects... (this may take a moment on first run)", flush=True)
I have about 667 MB of .jsonl logs across over 400 files in that directory, the initial scan takes quite a bit of time, and since the script wasn't printing anything while it was running, it appeared as if it was hung or had failed. So I had AI check out the code and confirmed nothing was wrong, then was able to figure out it was just taking some time on my macbook.
"Subsequent runs will be almost instantaneous since the scanner incrementally checks timestamps, but the initial parse always takes a while.
Summary of Fix: I have added a print statement in cli.py right before the scan starts print("Token Dashboard: scanning projects... (this may take a moment on first run)", flush=True). This way, whenever you or anyone else runs it for the first time or after a large influx of logs, you'll know that it is actively processing data rather than failing silently.
If you'd ever like to completely skip the initial scan and just start the server up immediately, you can pass the --no-scan flag: python3 cli.py dashboard --no-scan. The server will still scan changes asynchronously in the background."
Hey awesome dashboard!! Suggestion to add a print statement in cli.py right before the scan starts print("Token Dashboard: scanning projects... (this may take a moment on first run)", flush=True)
I have about 667 MB of .jsonl logs across over 400 files in that directory, the initial scan takes quite a bit of time, and since the script wasn't printing anything while it was running, it appeared as if it was hung or had failed. So I had AI check out the code and confirmed nothing was wrong, then was able to figure out it was just taking some time on my macbook.
"Subsequent runs will be almost instantaneous since the scanner incrementally checks timestamps, but the initial parse always takes a while.
Summary of Fix: I have added a print statement in cli.py right before the scan starts print("Token Dashboard: scanning projects... (this may take a moment on first run)", flush=True). This way, whenever you or anyone else runs it for the first time or after a large influx of logs, you'll know that it is actively processing data rather than failing silently.
If you'd ever like to completely skip the initial scan and just start the server up immediately, you can pass the --no-scan flag: python3 cli.py dashboard --no-scan. The server will still scan changes asynchronously in the background."