Looking for something bigger than a good-first-issue? Three open, unclaimed #103
tishachawla-jg
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
The last two `good first issue`s (#84, #86) got picked up within a day, thanks @SurajPatelPro and @HeaTTap — both merged and shipped in 0.2.1. Appreciated.
If you want something with more surface area than a papercut, three `help wanted` issues are open right now and unclaimed:
(Detector, Policy)pair plus abuild()factory, no core changes needed. The issue lists six concrete candidates with the moment andActionKindalready worked out —time_budget(wall-clock ceiling, the natural sibling ofstep_cap) is probably the smallest single one to start with.CANCELis declared but unimplemented.ActionKinddeclares eight kinds; seven are wired end to end,CANCELhas zero references outside its own enum member. It's the one action that would let a degenerating stream get cut off mid-flight with only the consumed tokens billed, instead of paying for the whole response or a full retry. Two separable pieces, take either.src/tokenops/adapters/langchain.pyis ~140 lines and a clean template: normalize messages in/out plus usage, plug intowrap_complete. Raw OpenAI, GHCP, and other stacks don't have one yet.All three ask you to comment before starting so scope gets agreed on first — that comment counts as a contribution on its own if you're not sure yet.
All reactions