fix(lumabot): item pulado por falta de busca nativa não chega às métricas da IA
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- node.js, typescript
- Domain
- backend-api-design, observability
Research direction
Start at apps/lumabot/src/plugins/ai/ai.ts near line 299, where a requested nativeSearch is skipped by a provider that lacks it. Trace how attempt(...) outcomes reach summary.ts and its successRate, then ensure the skip is emitted as a distinct unsupported outcome and counted with unregistered attempts. No test file is named, so add or locate coverage around these two files that verifies the metrics and dashboard totals.
Written by the indexing model from the issue text.
Description
Encontrado na revisão do #386.
Em apps/lumabot/src/plugins/ai/ai.ts (linha ~299), o item da cadeia pulado por não ter busca nativa (nativeSearch pedido e provider sem ela) só gera um warn no log: não chama attempt(...). Já o item sem provider registrado emite outcome: 'unregistered'.
Resultado: ai-metrics e dashboard não veem esses pulos, e uma cadeia de busca mal configurada (sem nenhum Gemini) aparece só como falha da web-search, sem a causa. Sugestão: emitir uma tentativa com outcome próprio (ex.: 'unsupported') e contá-lo como o unregistered no successRate do summary.ts.
- Dominant language
- JavaScript
- Stars
- 26
- Forks
- 6
- Avg merge
- 43m
- Merged PRs (30d)
- 136
Getting set up
- Ships a Dockerfile or Docker Compose file
- No 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 murillous/LumaBot
-
area:plugin good first issue type:bug
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
area:plugin good first issue type:debt
Difficulty 3/5 1-2 days Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:plugin type:bug
Difficulty 3/5 1-2 days Newbie friendliness 54/100
Maintainers usually reply within 1 day
-
area:plugin type:feature
Difficulty 4/5 1-2 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
-
area:plugin type:bug
Difficulty 3/5 1-2 days Newbie friendliness 72/100
Maintainers usually reply within 1 day
All issues in murillous/LumaBot
Similar issues
-
task
Difficulty 1/5 Under an hour Newbie friendliness 83/100
TAMULib/fw-registry#550 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
-
NWCWalletService.subscribe: response is never published if the handler finishes after unsubscribe (regression in 8.1.0)Possibly taken @ajaysehwal claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
bigskysoftware/htmx#4151 ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100