mojo_issues
Log in to pauseProgress
- 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
- Next runWhen the schedule fires next, in UTC, and the partition that run fills. Next runs, further down, lists the next five. Docs ↗
2026-11-11T08:00:00Z, fills 2026-11-11- 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 ↗
- — · The calendar
Config
- PartitionsHow the work is split: each run does some partitions (months, days, hours or named keys), from the first one on. Backfills and the coverage calendar count in partitions. Docs ↗
- daily from 2026-11-11
- ScheduleThe cron line the scheduler fires on, in its time zone, and the partition each fire runs. None means runs start only from a sensor, a backfill or a person. Docs ↗
0 8 * * *UTC, fills the current partition- Run retriesHow many more times the scheduler starts a run that failed before leaving it failed for a person. A step's own retries, inside a run, come first. Docs ↗
- 3
- PlacementWhere its runs go: control is the scheduler's own host, ec2 an instance launched for the run, worker:<pool> a remote orca worker of that pool, and default the scheduler's runner (ORCA_RUNNER). Docs ↗
- default (the scheduler's runner)
- BinaryThe program each run starts: the pipeline's Mojo code built into one executable, as orca register recorded it. Docs ↗
/opt/ orca/ pipelines/ mojo_issues
CodeThe functions this pipeline is made of, at the commit it's registered with. Hover a name to see its source; click it to open the file on its host. Docs ↗
- PipelineWhere the pipeline is declared: its Pipeline[...] line. Docs ↗
- mojo_issues
- StepsEach step's function, in the order the steps run. The Steps table below has what each reads and writes. Docs ↗
- fetch
Code hash 0x25d1c7ae61fde1cA hash of what the binary says about itself: its steps, partitions and schedule. It changes when they do, not on every build. Docs ↗
ResourcesWhat its latest runs used, as the median (p50) and the most of them: what a run of it needs. A run's peak is its attempts' largest, its CPU their sum. Docs ↗
None of its runs has been measured yet: the scheduler measures the runs it starts here (local and control-placed), a worker the ones it runs; runs on EC2 and Kubernetes aren't.
- RequestedWhat it asks for (cpus and memory_gb in orca.toml): its runs start once the least of it fits on their host, each granted up to the most. Set it from the peaks above. Docs ↗
- memory auto
| StepA step of the pipeline: a function that runs once per partition (mapped) or once over all of them (gather). | KindHow the step runs: mapped, once per partition, or gather, once over all of them. Hover a kind for more. | AfterThe steps this one waits for: it starts once they have succeeded. | ReadsThe datasets the step reads. | WritesThe datasets the step commits to. |
|---|---|---|---|---|
| fetch pipelines/mojo_issues.mojo:48 | mapped | mojo.repos, mojo.issues | mojo.issues |
Next runs docs
| UTCWhen the schedule fires, in UTC. | Wall clockThe same moment in the pipeline's time zone. | FillsThe partition that run fills. |
|---|---|---|
| 2026-11-11T08:00:00Z | 2026-11-11T08:00:00 | 2026-11-11 |
| 2026-11-12T08:00:00Z | 2026-11-12T08:00:00 | 2026-11-12 |
| 2026-11-13T08:00:00Z | 2026-11-13T08:00:00 | 2026-11-13 |
| 2026-11-14T08:00:00Z | 2026-11-14T08:00:00 | 2026-11-14 |
| 2026-11-15T08:00:00Z | 2026-11-15T08:00:00 | 2026-11-15 |
Configuration
Registered from /opt/orca/orca.toml @ 0df475ab1b3c of https://github.com/magmalake/mojo-census, sha256 90779b3a8c16.
| KeyThe setting's name, as orca.toml and orca register's flags call it. Hover the name for what it sets. | ValueThe value it is registered with. | FromWhere the value came from: the code's default, orca.toml (and which table), a flag of orca register, or the scheduler's environment. A link opens the line that sets it. |
|---|---|---|
placementWhere its runs start: default (the scheduler's runner), control, ec2, or worker:<pool>. | default | code default the scheduler's runner, local |
head_typeThe EC2 instance type of a run's dista head. | c7g.large | code default the ec2 runner's |
worker_typeThe EC2 instance type of each dista worker. | c7g.xlarge | code default the ec2 runner's |
workersHow many dista workers a run asks for, or min..max to scale between. | 0 | code default the pipeline has no tasks |
worker_procsDista worker processes on each worker instance; auto for one per core. | 1 | code default |
max_runsThe most runs of the pipeline the scheduler starts at once. | 1 | orca.toml [defaults] |
memory_gb | auto | orca.toml [pipelines.mojo_issues] |
fillsall: the scheduler fills the whole range by itself. since_registration: from registration on. | since_registration | code default |
secrets.GITHUB_TOKENA secret put in its runs' environment, by its id in the secret store; its value is never shown. | orca/github-token | orca.toml [pipelines.mojo_issues] |
env.ORCA_PUBLIC_WAREHOUSEA variable set in its runs' environment. | s3://census-mlake-dev/warehouse | environment ORCA_RUN_ENV |