Skip to content

docs: add quickstart - #52

Merged
ethanholz merged 8 commits into
mainfrom
docs/quickstart
Aug 13, 2026
Merged

docs: add quickstart#52
ethanholz merged 8 commits into
mainfrom
docs/quickstart

Conversation

@ethanholz

Copy link
Copy Markdown
Collaborator

This PR will followup from the work in #47 to move our "micro-dashboard" to a more usable walkthrough.

@codecov

codecov Bot commented Aug 12, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.06%. Comparing base (1ab8406) to head (cccd606).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #52   +/-   ##
=======================================
  Coverage   99.06%   99.06%           
=======================================
  Files           6        6           
  Lines         532      532           
=======================================
  Hits          527      527           
  Misses          5        5           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@ethanholz
ethanholz marked this pull request as ready for review August 12, 2026 21:22
@ethanholz
ethanholz requested a review from atravitz August 12, 2026 21:23
@atravitz

atravitz commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

this is great, but can you add some example output for the code snippets? (output of the print statements, for example)

Comment thread docs/quickstart/index.rst
Co-authored-by: Alyssa Travitz <31974495+atravitz@users.noreply.github.com>
@ethanholz

Copy link
Copy Markdown
Collaborator Author

this is great, but can you add some example output for the code snippets? (output of the print statements, for example)

@atravitz I like this idea. Should we create the example as a "complete" Python file so that we can run this independently? We can even link to it at the end as a complete example.

@atravitz

Copy link
Copy Markdown
Contributor

this is great, but can you add some example output for the code snippets? (output of the print statements, for example)

@atravitz I like this idea. Should we create the example as a "complete" Python file so that we can run this independently? We can even link to it at the end as a complete example.

yeah go for it!

@atravitz

Copy link
Copy Markdown
Contributor

looks great, but when I run locally I get the following error:

sqlalchemy.exc.IntegrityError: (sqlite3.IntegrityError) UNIQUE constraint failed: tasks.taskid
[SQL: INSERT INTO tasks (taskid, status, last_modified, tries, max_tries, task_type) VALUES (?, ?, ?, ?, ?, ?), (?, ?, ?, ?, ?, ?), (?, ?, ?, ?, ?, ?)]
[parameters: ('download-data', 1, None, 0, 3, '', 'analyze-data', 0, None, 0, 3, '', 'write-report', 0, None, 0, 3, '')]
(Background on this error at: https://sqlalche.me/e/20/gkpj)

Comment thread docs/index.rst Outdated
@ethanholz

Copy link
Copy Markdown
Collaborator Author

looks great, but when I run locally I get the following error:

sqlalchemy.exc.IntegrityError: (sqlite3.IntegrityError) UNIQUE constraint failed: tasks.taskid
[SQL: INSERT INTO tasks (taskid, status, last_modified, tries, max_tries, task_type) VALUES (?, ?, ?, ?, ?, ?), (?, ?, ?, ?, ?, ?), (?, ?, ?, ?, ?, ?)]
[parameters: ('download-data', 1, None, 0, 3, '', 'analyze-data', 0, None, 0, 3, '', 'write-report', 0, None, 0, 3, '')]
(Background on this error at: https://sqlalche.me/e/20/gkpj)

This generally occurs because you run the script twice consecutively. This makes sense because task-ids are unique to inserting a duplicate ID should fail. I debated whether or not we should name task databases in the example with UUIDs because it enables us to just keep running the script over and over. The other alternative is to use an in-memory database instead of one on disk.

The code-block:: sh directives had too many arguments on the same line, causing RST parsing errors. Fixed by using proper RST syntax with the language/class specified on the directive line and the content indented on following lines.

Assisted-by: Pi:opencode/nemotron-3.5-lightning-free
@atravitz

Copy link
Copy Markdown
Contributor

looks great, but when I run locally I get the following error:

sqlalchemy.exc.IntegrityError: (sqlite3.IntegrityError) UNIQUE constraint failed: tasks.taskid
[SQL: INSERT INTO tasks (taskid, status, last_modified, tries, max_tries, task_type) VALUES (?, ?, ?, ?, ?, ?), (?, ?, ?, ?, ?, ?), (?, ?, ?, ?, ?, ?)]
[parameters: ('download-data', 1, None, 0, 3, '', 'analyze-data', 0, None, 0, 3, '', 'write-report', 0, None, 0, 3, '')]
(Background on this error at: https://sqlalche.me/e/20/gkpj)

This generally occurs because you run the script twice consecutively. This makes sense because task-ids are unique to inserting a duplicate ID should fail. I debated whether or not we should name task databases in the example with UUIDs because it enables us to just keep running the script over and over. The other alternative is to use an in-memory database instead of one on disk.

ah, very possible. Is it possible to have nicer error handling for this in general? But yeah UUIDs might be good.

non-blocking though, I think this is a significant improvement!

@ethanholz

Copy link
Copy Markdown
Collaborator Author

Going to add a nicer error and then merge.

@ethanholz
ethanholz merged commit 9cfe24e into main Aug 13, 2026
9 checks passed
@ethanholz
ethanholz deleted the docs/quickstart branch August 13, 2026 22:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants