Commit68a5228
Add ky.retry() to force retries from afterResponse hooks
Pull request#779
Add ky.retry() to force retries
Issue#778
Simplify forcing a retry in afterResponse hook?
Discussion#778
4 comments: sholladay, sindresorhus, MrSquaare
source/core/constants.ts
263export const retry = (options) => new RetryMarker(options);
The reason exists. It's just scattered.
How it works
Map any codebase.
99 files found · surveying
How it works
01Paste a repo
Any public GitHub repository.
02Agents survey it
Readers work in parallel; a Verifier checks every quote.
03A map you can trust
Every arrow cites the line that proves it.
04Ask why
Click an arrow. Get the commit, PR and issue behind it.
05See what breaks
Pick a part. Everything that depends on it lights up.
06Follow it, keep it true
Play a request end to end. Every push is re-checked.
The proof
Built on Zetaris, Meterless and NVIDIA.
01 / 04
Zetaris
Build a USL · query it · add a DQ rule
Every line, commit, pull request and issue in one semantic layer.
1 · Nine tables, one provenance layer
repository
id
head_sha
source_file
id
repo_id →
path
line_origin
file_id →
line_start
commit_sha →
code_change
sha
subject
pr_id →
file_change
commit_sha →
file_id
pull_request
id
title
issue_count
pr_issue
pr_id →
issue_id →
issue
id
title
discussion
parent_id →
author
lightning.metastore.cartograph.provenance
01 / 04
Zetaris
Build a USL · query it · add a DQ rule
Every line, commit, pull request and issue in one semantic layer.
1 · Nine tables, one provenance layer
2 · One query from a line to its reason
3 · A rule that scores explainability
02 / 04
Meterless H-MEM
An engine in a working feature
Cartograph's memory: it keeps approved answers, and knows when they go stale.
1 · An approved answer becomes a memory
Answer · Core → Retry Engine
Added in #779 so hooks can force a retry, as issue #778 asked.
Critic approved
H-MEM · long-term
ky.retry() creates a RetryMarker to signal forced retries.
source critic-approved
confidence 0.85
refs constants.ts:263
remembered, with its sources
02 / 04
Meterless H-MEM
An engine in a working feature
Cartograph's memory: it keeps approved answers, and knows when they go stale.
1 · An approved answer becomes a memory
2 · The next question starts from it
3 · Code changes, the memory is set aside
03 / 04
Meterless Runtime
Primary AI provider
Every agent call goes through Nightshift first. NVIDIA answers only if it's offline.
1 · Live status in the desk
Powered by
- Meterless Nightshiftprimary AI providerprimary
- NVIDIA Nemotronthe modelsworking
- Zetarisprovenance USLworking
- Meterless H-MEMmemory engineworking
live in the desk header
03 / 04
Meterless Runtime
Primary AI provider
Every agent call goes through Nightshift first. NVIDIA answers only if it's offline.
1 · Live status in the desk
2 · Agent → Nightshift → Nemotron
3 · Runtime offline, NVIDIA steps in
04 / 04
NVIDIA Nemotron
Nemotron in every agent
Ultra plans and judges. Lightning reads and writes. Every call is checked.
1 · Every agent, its model
Scout
plans the survey
Nemotron Ultra
Readers
read files in parallel
Nemotron Lightning
Cartographer
joins the map
Nemotron Ultra
Verifier
checks every quote
plain code
Reviewer
reviews each push
Nemotron Ultra
Tracer
answers on the map
Nemotron Lightning
Writer
drafts the why
Nemotron Lightning
Critic
checks every claim
Nemotron Ultra
04 / 04
NVIDIA Nemotron
Nemotron in every agent
Ultra plans and judges. Lightning reads and writes. Every call is checked.
1 · Every agent, its model
2 · Two tiers, every call logged
3 · Output is validated, never trusted
Draw your codebase.
Any public GitHub repository · a map in about three minutes