/user/avatar
Maintainers usually reply within 5 days
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
Research direction
Reproduce the POST request to /user/avatar using the documented body and API key on version 0.70, then inspect the Docker logs and the code path that reports "info query timed out." Done means the endpoint no longer returns HTTP 500 for the reported request and returns the expected API response.
Written by the indexing model from the issue text.
Description
Welcome!
- Yes, I have searched for similar issues on GitHub and found none.
What did you do?
Eu tento fazer o post na rota /user/avatar com body correto, conforme manual. E apikey revisada. Não tem reposta, dá timeou. Não vi erros no log do docker. O envio e recebimento de mensagens via api está ok, webhook também funcionando.
http status 500 {
"error": "info query timed out"
}
What did you expect?
a api não retorna conforme esperado.
What did you observe instead of what you expected?
.
Screenshots/Videos
No response
Which version are you using?
0.70
What is your environment?
Linux
If applicable, paste the log output
No response
Additional Notes
No response
- Dominant language
- Go
- Stars
- 918
- Forks
- 488
- Avg merge
- 5m
- 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 evolution-foundation/evolution-go
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
evolution-foundation/evolution-go#193 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
evolution-foundation/evolution-go#104 ·
Maintainers usually reply within 5 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
evolution-foundation/evolution-go#101 ·
Maintainers usually reply within 5 days
-
POST /group/participant always returns 400 "participants is required and cannot be empty" (wrong validation middleware on route)Possibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
evolution-foundation/evolution-go#97 · 2 comments ·
Maintainers usually reply within 5 days
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 42/100
evolution-foundation/evolution-go#217 ·
Maintainers usually reply within 5 days
All issues in evolution-foundation/evolution-go
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
LanternOps/breeze#8353 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
prime-radiant-inc/evener#4223 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
input.Scanner.Scan loops forever when the input reaches EOF, hanging every ConfirmAction promptPossibly taken @mlliarm claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
elastic/cloud-sdk-go#521 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
open-telemetry/opentelemetry-go-compile-instrumentation#1467 ·
Maintainers usually reply within 3 days