Add limit to rephrase on_fail action
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by locating the rephrase on_fail action and the code that invokes it for successive queries; the issue names no files or tests. Determine where per-query invocation counts are tracked and what existing tests cover, then verify that repeated harmful input stops after a defined limit without creating an endless loop.
Written by the indexing model from the issue text.
Description
Which feature or component needs enhancement?
The rephrase on_fail action has no limits of calling. In each successive iteration, harmful text can keep on getting detected and in the worse case, it might mean an endless loop of nudging the user / LLM to rephrase their response. We need to put a limit on how many times this can be called for a single query.
Describe the current behavior
We have added a custom on_fail action called "rephrase" which nudges the user or LLM to rephrase their query since we have detected harm in the message. However, we don't have a limit as to how many times this "rephrase" on_fail action can be called if it keeps on detecting harmful text.
- Dominant language
- Python
- Stars
- 5
- Forks
- 4
- Avg merge
- 11d 19h
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No 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 ProjectTech4DevAI/kaapi-guardrails
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Callback Enhancement: Include intermediate responsesPossibly taken @Prajna1999 claimed this 26 days ago. Open
ProjectTech4DevAI/kaapi-guardrails#158 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
All issues in ProjectTech4DevAI/kaapi-guardrails
Similar issues
-
needs-human needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
gke-labs/kube-agents#2400 · 1 comment ·
Maintainers usually reply within 1 day
-
Device Details tables: FS/SF columns contradict each other (nfet_01v8 Vt row, pfet_01v8 Idsat row)Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
google/skywater-pdk#450 ·
-
Drained trajectory arrays are overwritten when the sequence buffer is reusedPossibly taken @sylvesterkaczmarek claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
google-deepmind/bsuite#56 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
LearningCircuit/local-deep-research#7206 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
chingu-voyages/V62-tier3-team-33#285 ·
Maintainers usually reply within 1 day