Empty Replay on a blank lake points to the CLI, not to Setup

Open
  • Is something wrong?
#37 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
62/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
cli, frontend

Research direction

Start with flashpoint serve and the Replay view, which shows the empty-state text that says to run flashpoint report. Find where that message is rendered and where the app chooses its opening view. Check how Setup reports failing checks, since the new message needs that count and a link to #view=setup. Also check the History and Anomalies empty states. Done when a blank lake sends the user to Setup, and the report message appears only when logs exist but no match has been built.

Written by the indexing model from the issue text.

Description

enhancement

Found walking through setup on a blank lake and blank config (flashpoint serve on main at 8369dff).

What happens

serve opens on Replay, which says:

No Replay data. No match has been built yet. On the laptop that holds the lake, run: flashpoint report

On a blank lake, flashpoint report builds nothing: there are no logs yet, and Setup shows two failing checks (Team, Robot for 2026). The page sends a new student to the command line and leaves out the two things they need to do first.

Expected

When the lake has no imported logs (or Setup has failing checks), the empty Replay state points to Setup:

  • a link to #view=setup, plus the count of failing checks ("2 setup problems");
  • the first step in order: set the team number, import a match (flashpoint ingest <folder>), draft a robot, build;
  • the current "run flashpoint report" message only when logs exist but no match has been built.

Possibly also: open on Setup instead of Replay when there are setup problems and no data.

Notes

  • History and Anomalies have empty states too; check that they also point to Setup.
  • Relates to #24 (team setup) and its 9.4 [HUMAN] new-team walkthrough.
Dominant language
Python
Stars
0
Forks
1
Avg merge
18h 37m
Merged PRs (30d)
15

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IgniteRobotics/flashpoint

All issues in IgniteRobotics/flashpoint

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.