orcaLog in

Pipelines

mojo_repos

Progress

Runs at onceRuns of this pipeline going now, out of the most the scheduler starts at once (max_runs); the others wait in the queue. Fill runs come on top, up to fill_max_runs. Docs ↗
0 running of 1, 0 queued
FollowingA sensor runs the partitions of the tables it reads as they get snapshots. This is how many of those partitions it has done, and the ones it hasn't: going, failed, or not queued yet (a backfill queues them). They are behind on Coverage. Docs ↗
gharchive (gharchive.candidates): 1037 of 1408 days done; 371 behind: 371 not queued yet
CoverageHow much of the pipeline is done: its days or months done of those in its range so far (its first partition through the last that has ended), or a keyed pipeline's keys done of the keys its dataset has. Done means every step succeeded in a run of its current code, as on the calendar; failed, skipped, queued and running ones aren't. A dash means it has none to count yet. Docs ↗
1037 / 1408 days done (73%)

Coverage

MonthYear
June 2025
  • 1, 2025-06-01 done
  • 2, 2025-06-02 done
  • 3, 2025-06-03 done
  • 4, 2025-06-04 done
  • 5, 2025-06-05 done
  • 6, 2025-06-06 done
  • 7, 2025-06-07 done
  • 8, 2025-06-08 done
  • 9, 2025-06-09 done
  • 10, 2025-06-10 done
  • 11, 2025-06-11 done
  • 12, 2025-06-12 done
  • 13, 2025-06-13 done
  • 14, 2025-06-14 done
  • 15, 2025-06-15 done
  • 16, 2025-06-16 done
  • 17, 2025-06-17 done
  • 18, 2025-06-18 done
  • 19, 2025-06-19 done
  • 20, 2025-06-20 done
  • 21, 2025-06-21 done
  • 22, 2025-06-22 done
  • 23, 2025-06-23 done
  • 24, 2025-06-24 done
  • 25, 2025-06-25 done
  • 26, 2025-06-26 done
  • 27, 2025-06-27 done
  • 28, 2025-06-28 done
  • 29, 2025-06-29 done
  • 30, 2025-06-30 done

30 done · 0 failed · 0 running or queued · 0 behind what it follows · 0 not run · 0 outside the pipeline's range

Behind: gharchive.candidates has it, but no run of this pipeline has done it, failed on it or is going; a backfill queues it.

Start runs docs

Queues a run for each day in the range that hasn't succeeded and isn't in a queued or running run.

Queues a single run over every day in the range, done or not; refused while a queued or running run has one of them.

From the command line:

orca login <url> && orca --remote <url> backfill mojo_repos <range>

Stop runs

Cancelling stops runs that are queued or waiting to be retried, and asks running ones to stop before their next step. Pausing stops the scheduler starting its runs, which stay queued; runs already going go on.