Proxy: one ordered list of checks, cheapest first
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 32/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- backend, backend-api-design
Research direction
This is blocked by #312. Locate every place that currently decides check order on the request path (gates, guards, detectors, breakers) and introduce a single ordered table that matches today's sequence with no behaviour change. Confirm by running the existing replay tests so they stay identical. Done when one table owns the order and each check still returns a typed result (pass, refusal, tool/model/infrastructure error).
Written by the indexing model from the issue text.
Description
What needs doing
The request path has about 85 checks (gates, guards, detectors,
breakers), and their order is decided in about 16 separate places.
Put the order in one table. First step: the table reproduces today's
order exactly, with no behaviour change (the replay tests show it).
Each check returns a typed result: pass, a refusal by a guard, a tool
error, a model error, or an infrastructure error.
Why
With the order in many places, an expensive step can run before a
cheap check that then throws its work away, and nobody sees it. One
table makes the order reviewable, and the typed results let later
fixes treat a refusal differently from a failure.
Done when
- One table owns the order of the checks in the request path.
- The replay tests are identical before and after.
Blocked by: #312
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 197
- Avg merge
- 14h 1m
- Merged PRs (30d)
- 201
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from inferstep/ATLAS
-
Bootstrap: the last two steps run as the user who owns the installMay be free again @assassinationss claimed this 18 days ago, and no pull request is open. Openarea/install reliability
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
inferstep/ATLAS#412 · 4 comments ·
Maintainers usually reply within 1 day
-
area/cli
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
area/cli area/lens status/ready
Difficulty 2/5 Half a day Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
area/ci status/ready
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
inferstep/ATLAS#245 · 4 comments ·
Maintainers usually reply within 1 day
-
area/docs documentation help wanted
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
Similar issues
-
[oblt-aw][autodoc] Update docs for security org scaffolding and Docs AI menu permission changesPossibly taken @github-actions claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
external integration integration-submission
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
langchain-ai/docs#7077 ·
Maintainers usually reply within 1 day
-
author-page correction
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
acl-org/acl-anthology#10623 · 1 comment ·
Maintainers usually reply within 1 day
-
Use context to recognize personal initials and lowercase namesPossibly taken @lipikaramaswamy claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
NVIDIA-NeMo/Anonymizer#340 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
btclib-org/btclib-node#2083 ·
Maintainers usually reply within 1 day