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
FS#2779 - Feature request: Display name of file in /etc/config if uci can't parse it #7584
Comments
adrianschmutzler: +1 This is completely independent from Luci, and should be addressed directly in uci project most probably. |
richb-hanover: Hi Adrian, Thanks for thinking about this. I'm confused, though. I filed a feature request at openwrt/luci#3569 but was told (I think) to file the request over here. Where should this request go? Many thanks. Rich |
adrianschmutzler: It's okay here, as the uci system is part of OpenWrt. |
richb-hanover: That's great. Thank you. |
adrianschmutzler: Those two lines are relevant. https://git.openwrt.org/?p=project/uci.git;a=blob;f=libuci.c;h=140edf2adbb0817ad89fdbb2d78984290d3017ca;hb=HEAD#l33 I will have a look whether I can manage to write pure C code ... |
adrianschmutzler: Will test this when I have time on device:
|
adrianschmutzler: Looks like it's not that easy. |
adrianschmutzler: Seems like it's more complicated: The problem is that the information about the requested data is not in the uci_context struct (ctx), but in an ubi_ptr struct. Definitions here: So, one would have to create a field for the failed ptr or package string, and then write content to it for each situation where UCI_ERR_NOTFOUND is triggered. That seems to be what's done for the parsing error right now ... This looks to me like it will require a lot of testing, and I do not have the time to implement it ATM. |
richb-hanover:
In LuCI issues #3567 on Github (openwrt/luci#3567) I asked about the "uci: Entry not found" message. The problem was that there was an unusual (non-standard) file present in /etc/config
I created a feature request there (openwrt/luci#3569), but I understand that this report/request should be filed here.
Request: It would be good if that error message could include more information, perhaps the file name of the offending file. Thank you.
The text was updated successfully, but these errors were encountered: