Skip to content

Conversation

@anuunchin
Copy link
Contributor

@anuunchin anuunchin commented Oct 24, 2025

This PR introduces a new pipeline run section to the dashboard app which uses a simple html snippet.
Screenshot 2025-10-28 at 15 36 26

@anuunchin anuunchin force-pushed the feat/pipeline-run-dashboard branch from 8054e89 to 21c3dd6 Compare October 24, 2025 14:39
@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Oct 24, 2025

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
❌ Deployment failed
View logs
docs b029cfa Oct 28 2025, 02:48 PM

@anuunchin anuunchin self-assigned this Oct 24, 2025
@anuunchin anuunchin force-pushed the feat/pipeline-run-dashboard branch 2 times, most recently from c7eaaa4 to 65991c7 Compare October 28, 2025 14:36
@rudolfix
Copy link
Collaborator

terminology (from https://www.notion.so/dlthub/dlt-Entities-their-Lifecycles-and-Relations-2679fb8e23cf80169921c4ea069bfff8?source=copy_link#2679fb8e23cf8109b9c3eee928a2a377). definitions are pretty clear and you can easily refer to code

  • pipeline run succeeded or failed (correct your status)

Idea display status of load package(s) as boxes like the "COMPLETED"

  • pipeline created load packages: collect packages from all steps to get load id and package
  • display color coded states of all packages (with load ids on it): pending | loaded | aborted
  • package can be "partially loaded" (I think in pending and aborted states). there's a method on package info. I hope we have it in trace. if you see it - it should be a red color ie: "load_id: partially loaded in aborted"

schema indicators

  • look for "applied schema update" if it is found in the trace - display "migration" box

for later

  • detect state sync (loaded job with state table name)
  • detect dev_mode (I do not think we have it in trace but we could use dataset name)
  • detect full refresh type (I do not think we hace it in trace)

feedback to current UI
experiment: if we have trace just put it on top, without "Pipeline Run" and switch. Also you do not need to repeat pipeline name, it is already on top

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.

3 participants