-
Notifications
You must be signed in to change notification settings - Fork 21
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
Last hotfix broke luna for me: ParseError #71
Comments
Heya! Thanks for letting me know (also for the fact that I didn't change the versions). I'll have a look at this as soon as I can and will let you know if I should require more information. |
Not an inconvenience at all. I am only grateful for the great addon. |
@wackerl91 thats not an problem at all, im glad the older version is working! good luck with your exames! |
I've had a look at this and while I can't reproduce the error on my machines (Note: I can't update GFE on my notebook past 2.10.x as my notebook's GPU is not supported and I had to patch the exe to get it running) I might have a somewhat 'hacky' solution for now by catching the error you guys were seeing and re-trying the old behaviour present in 0.6.1. However before releasing it I'd like to make sure that this is indeed working. The only file which has changed is nvhttp and for testing purposes you should be able to just replace it:
If Luna was running for some reason close it completely (go back to Kodi's 'programs' view), start it again and try whatever you were doing when it failed during 0.6.2. Please let me know how it goes or if you have additional questions :) Specifically @Langoor2: You mentioned that you're unable to set a controller map in your original issue, but didn't provide logs for this particular problem. If you're able to get your game list (i.e. the above change did indeed fix the error present in the logs) but you're still unable to set a controller map I'd kindly ask you to open a new issue so we can investigate that further. Setting a controller map should not be related to the game list in any way, though to be fair I can't rule that out completely as Luna's current architecture grew on demand and wasn't prepared to handle all that stuff it currently does - read: it's a huge mess, which is why I'm rebuilding it more or less from ground up. |
Hi Wacker, Thank you very much for this amazing addon. I've been using this for about two weeks as a complete Raspberry Pi newbie, and it's been working great. I had this exact error, and the fix above completely worked for about five minutes. When I tried to access my games list again, however, I got booted from Luna and couldn't make it back to the addon without getting the "Check log for errors" message again. Edit: Sorry to edit again. I've tried reinstalling everything from scratch, and I've been able to reproduce the error. If I install Luna, but make sure that nothing is paired, and then use your fix, I can get into Luna but get the error that it can't find any games (Which makes sense, because I'm not paired to my computer). As soon as I pair, I can't get back into Luna and I just get the "Check the log" error again. Hope that helps. |
Heya @Kampher, Back to the ugly stuff, though: I tried following the steps you listed above to the letter and I still can't reproduce this on my end. This is what I did:
There's two things I'd like to note about this:
Unfortunately this means we have to go full circle on this, and believe me: I like that even less than you do ;)
In case you don't know (you mentioned being new to all of this) you can just follow the log output inside the terminal window by calling
The first error (unsecure request warning) can be ignored, that's just in there because I needed to disable request validation for requests made to the GFE host because the certificate in use would fail this validation (I'd need to write my own validator for this step and will do so at some point in the future, but it's only a minor inconvenience and nothing to worry about right now). In your case it should(!) fail after the second last line and instead log an error saying "Building ETree from XML failed: ParseError" followed by the XML it tries to parse at that point. If I'm not right with above assumption then just send me the entire log from the last action Luna logged (and therefore successfully completed) and the entire error stack trace (please use pastebin for this as well, as the formatting for longer logs in GitHub is a pain to read). Should you get a parse error but it's not being followed by an XML string however then we need to wait for the other three guys to try the very same while I'll think of some easy to follow instructions so we can get that information. |
Hi @wackerl91, Ok, so I tried your steps and it still won't work for me. Here's the info you need.
I hope this gives you a clue as to what might be going wrong. I tried version 0.6.1 but I'm getting the same results. Thanks again for a great addon! Like I mentioned earlier, I had no problems with this until I reinstalled a fresh OSMC onto a new SD card and reinstalled everything. Thank you for the support. |
Heya @Kampher, This entire encode / decode stuff is such a mess without strict standards and it's obviously giving me a hard time, especially since GFE sometimes specifies UTF-8 as encoding and sometimes UTF-16. Anyway, I took another shot at it by just trying to decode and then encode the string in every possible format (in this context at least). If the decode fails as ASCII, UTF-8 and UTF-16 it will ultimately fail, log the offending string and raise an exception. Similarly, if I'm not able to encode the string as either UTF-8 or UTF-16 it will again log the string and raise an exception. If the string passes the decode / encode stage but still can't be interpreted properly it will fail for good and log the offending string. Again this change works for me (using special characters in at least one game's name). I'd be glad if you could give it a try:
I'm so sorry that this turned out to be such a clusterf..., yet I want to thank you for your patience and help while resolving this issue (hopefully for good this time!) - really means a lot. P.S.: Please make sure to include some lines above the actual error next time. I'm logging pretty much (though not as much as I'd like to, but this will change in the future) which helps me to put errors in context. It wasn't an issue this time as it's pretty clear where this is happening, just a heads-up for the future :) Most devs love to have as much context as possible. |
That did the trick! Thanks for such a speedy and well thought out reply. Next time I'll be sure to add some more to the error log. I figured you didn't want the other lines because you mentioned that you knew of the errors mentioned above. |
Awesome! Admittedly it's kind of a crowbar solution, but I'm glad it's working now. Since I'm not at home right now I'll make sure to publish a bug fix release either tonight or tomorrow. If you should have any other issues or feature requests in the future please let me know :) Cheers! |
Luna 0.6.3 contains the fix for this. Again, thanks for all your help and understanding. If you encounter any other issues and / or have feature requests (or anything else, really) just let me know. It was a pleasure talking to you guys! |
Hi,
0.6.1 alpha works well, 0.6.2 (for which you forgot to change the version in addon.xml btw.) doesn't.
Here's what happens:
The text was updated successfully, but these errors were encountered: