When reporting a bug, it is important to actually describe the issue instead of pasting parts of a discussion that was months ago, because there were many changes in the c code and troubleshooting is not longer the same. Also, digging in archives takes time and support here is offered in a best effort manner. If the issue is reported properly, it has chances to be investigated. If the reporter expects the developers to do all the work to understand the problem, then it has lower chances to be approached.

Describe the bug as you face it these days, what happens with the latest versions in the supported branches, paste the logs and network traces if they are relevant.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.