-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: strange ini parse key causes segfault, at U2F #5526
Comments
There is already issue for this |
i'll close please tell me what its the issue number, i search previously and i not found easyle! and then i'll close |
seems for you duplicate of #4692 but i think its not! due i report agains stable version.. as i put in the blog! more releases and more releases and open new bugs, i have a gitea open issue about the documentation with some questions not yet answered, that will help in each release to parse some "exceptions" and then users and administrators can deploy witout "surprises" also u ask in the debian-package repository some others questions to send pull's to that.. but that repository will still active ? |
Closing as same issue as #4692. Even though the original poster of that ticket is using a different version than you, it is the same bug that is present. Please remember that maintainers of Gitea are all volunteer, and give as much time as they can to this project, however we aren't able to respond to everything right away. Gitea is focused on adding new features AND fixing bugs. Just today 6 PRs were merged for bug fixes, as well as we soon will merge support for automated testing of MSSQL so we can have better testing coverage to catch even more bugs. As mentioned before if you need support or features right away, you are free to pay someone. |
my questions are for contribute too! i cannot help if i dont know how and what i help! right? please some one to help with #5466 |
[x]
):Description
I try to understand why the gitea crash when a no valid U2F are set or not set, by example if i do not set the email, gitea property crash with indicated error:
2018/12/11 16:24:04 [...s/setting/setting.go:1504 newMailService()] [E] Invalid mailer.FROM (): mail: no address
but that its not the case for the
U2F
, instead gitea crash abrupted and does not specify why and when.. and user must debug to make this issue, log error of crash debug are at end of the issue.. i tested by removing the part "bad configured" and gitea does not crash! (also the crash are not very helpfull!)also documentation are very very ambigous! documentations says at gitea docs:
The config example file said something not very similar:
...
log
The text was updated successfully, but these errors were encountered: