QRCode is not beign generated
Maintainers usually reply within 9 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Reproduce the reconnect flow with version 0.7.1 in the Docker environment: create an instance, connect with the QR code, disconnect, and try to connect again or update the QR code. Inspect the resulting behavior and any available container logs; done means the QR code loads after reconnecting instead of remaining stuck in loading.
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?
I created an instance and successfully connected it using the QR code. After disconnecting the instance, I tried to connect again, but the QR code is not being generated/loaded anymore.
And updating the qrcode the same error occurs
What did you expect?
The qrcode
What did you observe instead of what you expected?
The qrcode stuck in loading
Screenshots/Videos
No response
Which version are you using?
0.7.1
What is your environment?
Docker
If applicable, paste the log output
No response
Additional Notes
No response
- Dominant language
- Go
- Stars
- 929
- Forks
- 499
- 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 9 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
evolution-foundation/evolution-go#104 ·
Maintainers usually reply within 9 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
evolution-foundation/evolution-go#101 ·
Maintainers usually reply within 9 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 9 days
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 42/100
evolution-foundation/evolution-go#217 ·
Maintainers usually reply within 9 days
All issues in evolution-foundation/evolution-go
Similar issues
-
scaleway_lb_frontend: updating a frontend with external_acls = true deletes all scaleway_lb_aclOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
scaleway/terraform-provider-scaleway#4485 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Add SolentaPossibly taken @sharmao07 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
slavakurilyak/awesome-ai-agents#760 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100