Closed ilario closed 1 year ago
According to https://github.com/libremesh/lime-app/issues/378#issuecomment-1523018493, it could happen because my node does not have any other connected node. I should be able to confirm within a few days. @selankon can you try if it happens to you?
I can confirm that seems the same issue reported in #378: as soon as there is a peer connected, the lime-app is working again.
This is a JS error given because the backend don't return a most active iface. The JS error have to be fixed on one hand, preventing the backend error to let limeapp continue working without this info.
On the other hand, we have to find the backend problem of why this call fail to find any iface.
Duplicate of #378. Happens on OpenWrt 22.03 but not on 19.07
This is fixed on develop https://github.com/libremesh/lime-app/issues/378#issuecomment-1547881158
On a YouHua WR1200JS, I have compiled LibreMesh on top of both OpenWrt 19.07 and OpenWrt 22.03. In both cases I have the same problem: only the upper menu is rendered, and the sandwitch menu button on the top right is unresponsive. I made sure to reproduce the error with the default configuration (empty /etc/config/lime-node)
On the node running OpenWrt 19.07, the error messages reported from Firefox are:
On the node running OpenWrt 19.07, the error messages reported from Chromium are:
(ignoring the missing favicon error) The first error seems caused my the lack of definition of
node.most_active.iface
that then gets used here: https://github.com/libremesh/lime-app/blob/7efec0e9c137e2dfc0fe545dcab32012d0171ac9/plugins/lime-plugin-rx/src/rxPage.js#L99something similar was mentioned in this fix: https://github.com/germanferrero/lime-app/commit/428f2670e8a89f6de7f1254129a23ce72988b37f
The last errors complains about some setTimeout, maybe this is a consequence of the previous error?