RFC 0020: admit a research stage now that the research binding form exists
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 22/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- json
- Domain
- documentation
Research direction
Start with RFC 0020 §4 and its unresolved question 2, which currently say research bindings are deferred, then read RFC 0018 §4.4 and its round-8 amendment (judgment-pack-spec#173, issue #171). Done means RFC 0020 admits research-source stages as a Draft amendment, with the round recorded on the pull request, and the §11 fixture is left as the operation construction until judgment-pack-runner#88 lands.
Written by the indexing model from the issue text.
Description
What this asks
Revise RFC 0020 (Draft) so that it admits a stage whose dialect has a research source, now that RFC 0018's round-8 amendment (judgment-pack-spec#173, issue #171) gives the research kind an unbound form and a binding document under §4.4's model. RFC 0020 §4 still says "Only operation has that unbound form. This version does not extend it to research" and that a published research recipe's portable binding "is deferred", and its unresolved question 2 says the research binding remains open. #173 states, within its own text, that workflow version 1 admits no stage with a research source and that those sentences are superseded pending this revision; the two readings must not stand side by side longer than needed.
Scope
- §4: a research source in a stage's dialect is bound at import under RFC 0018 §4.4 as extended; the stage's expansion names the research binding's profiles; the generated class and the admission lever of #168's M2 apply to a research stage's outputs as to an operation's.
- Unresolved question 2 resolved by reference to RFC 0018's amendment; §11's fixture may name a research stage once a Runner prepares the kind (Judgment-Pack/judgment-pack-runner#88); until then the fixture stays the operation construction.
- Compatibility: workflow version 1's document form unchanged; the companion equal to the Specification.
Acceptance
- The revision as a Draft amendment with its round recorded on the pull request.
- Recorded on this issue and on #160 when it lands.
- Dominant language
- Python
- Stars
- 5
- Forks
- 6
- Avg merge
- 6h 15m
- Merged PRs (30d)
- 69
Getting set up
- No 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 Judgment-Pack/judgment-pack-spec
-
RFC 0018 §9.3: the dependencies row still says absent for a local filePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 Under an hour Newbie friendliness 72/100
Judgment-Pack/judgment-pack-spec#200 ·
Maintainers usually reply within 1 day
-
Cover a rule's or an exception's reference list written without its array, or with a repeated entryOpengood first issue
Difficulty 2/5 Half a day Newbie friendliness 76/100
Judgment-Pack/judgment-pack-spec#158 ·
Maintainers usually reply within 1 day
-
RFC 0018: define portable page bindings for multiple discovered endpointsPossibly taken @kikashy claimed this today. Open
Judgment-Pack/judgment-pack-spec#199 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
Judgment-Pack/judgment-pack-spec#172 · 3 comments ·
Maintainers usually reply within 1 day
-
RFC 0018: the research kind's result contract, its binding form and the reconciliation of sourcesOpen
Difficulty 5/5 Over a week Newbie friendliness 8/100
Judgment-Pack/judgment-pack-spec#171 · 2 comments ·
Maintainers usually reply within 1 day
All issues in Judgment-Pack/judgment-pack-spec
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
omegaup/omegaup#10353 · 1 comment ·
Maintainers usually reply within 5 days
-
bot-triaged module: LrScheduler module: optimizer triaged
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
documentation glm5 llm-model
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vllm-project/vllm-ascend#19062 ·
Maintainers usually reply within 1 day
-
author-page correction
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
acl-org/acl-anthology#10496 · 1 comment ·
Maintainers usually reply within 1 day