-
-
Notifications
You must be signed in to change notification settings - Fork 559
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
Add interface information #3143
Conversation
Signed-off-by: DL6ER <[email protected]>
Signed-off-by: DL6ER <[email protected]>
Signed-off-by: DL6ER <[email protected]>
Signed-off-by: DL6ER <[email protected]>
I still think the
|
The combination of those branches makes the web interface non responding and triggers a constant FTL restart.
|
What did you try exactly? I'm on the same combination of the three branches, yet, I can see no delay/unexpected starting at all. If you can reproduce it reliably, it'd be interesting to see what an attached
Even when this is not a crash,
|
Only accessing the web interface (login page). It is reproducible.
|
Thanks for the backtrace, this is already very helpful. We're faced with a bug in the LUA library itself. More precisely, an infinite loop when it tries to log
The first two placeholders should be replaced by the file and line and this is where it gets interesting. They want to print I'm afraid I'd need two things from you:
My hope is still to find that this bug is actually caused by CivetWeb and fixable without having to deal with the LUA code itself. Chances are low but anyway. |
@yubiuser I did just push a commit that adds additional debugging output to Memo for myself: What I am concerned about here is that
The two former are fine, the two latter don't make much sense to me right now and are both wrong (in different ways). Interestingly enough: Why don't I get the error message myself?... |
Here you go. In the I find it more interestingly that it is caused by a new |
Regarding the used architecture
|
The bug is that error reporting is not working. Somehow the error doesn't seem to be reported for you on ... thinking ... okay, after staring at the code for some time, I realized that a necessity to trigger the issue is not using HTTPS when accessing the web interface. Without HTTPS, I can - at least - see that the web interface doesn't load properly - even when I can still not reproduce the crash and neither receive the error message itself. |
Another interesting detail I found midway: The hundreds of thousands of iterations you have seen above ("many many lines") cause a stack overflow deep inside LUA code. This also seems to be the reason why I don't see the error message. The errors happens, LUA tried to report it, gets caught in some infinite loop, corrupts its own stack, then somehow leaves the infinite loop and thinks nothing bad has ever happened... Investigation ongoing... |
Update: It turned out to be a hard-to-find but thankfully easy-to-fix bug in Civetweb. See civetweb/civetweb#1296 |
…emes using a semi-tranparent color Signed-off-by: RD WebDesign <[email protected]>
I added a commit fixing the CSS for all current themes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add bstreeview
to the package.json
(so dependabot can inform us about an update if it will ever happen)
Line 111 in 7acf464
"dependencies": { |
Signed-off-by: DL6ER <[email protected]>
Signed-off-by: DL6ER <[email protected]>
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
Signed-off-by: DL6ER <[email protected]>
Conflicts have been resolved. |
What does this implement/fix?
This PR implements a Discourse feature request. The particular implementation is up for discussion and possible further improvements therewhile.
Needs pi-hole/FTL#2009 (branch
tweak/api_network_info
) to work.Related issue or feature (if applicable): https://discourse.pi-hole.net/t/list-ip-v4-and-v6-address-in-web-interface/70981/11 and also #3076
Pull request in docs with documentation (if applicable): N/A
By submitting this pull request, I confirm the following:
git rebase
)Checklist:
developmental
branch.