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
More glib errors when updating appstream cache #141
Comments
|
Can you maybe generate a backtrace for this? (Install debuginfo, set a breakpoint on g_error) |
|
|
Can you check if the patch above changes anything? I am just guessing here, but I think you might have an empty |
|
The patch fixes the GLib-ERROR and the second GLib-CRITICAL. Still getting lots of the first GLib-CRITICAL though |
|
Can you set a breakpoint on |
|
With g_critical it doesn't break. With g_log: You can find the xmls that trigger this on https://sources.archlinux.org/other/packages/archlinux-appstream-data/20170929/ |
|
Yeah, it breaks on a debug statement now (you'd need to forward until you hit the critical warning). I will test with your XML later tonight, that's probably the easiest way to debug this (and also makes writing a unittest easier). |
|
Another try... |
|
@antonio-rojas That does it, thanks! I did not anticipate GVariantBuilder being annoyed by trying to add an empty array or other type.
This only ever happens for broken or incomplete metadata, which happens to be the case here (and the pre-validation wasn't as excessive for screenshots as it is for other types). |
|
@antonio-rojas Okay, this should be fixed now. But there are a few other changes I want to do to catch these issues earlier (this should not even hit the cache). The things on the todo list now are to make the validator more strict about screenshot tags and to make the generator not output useless screenshot entries. |
|
Here it is: Any plans for a release soon with the latest fixes? |
|
I'll do a release of both asgen and AppStream as soon as I have made the changes mentioned here :-) (so, likely next week) |
|
@antonio-rojas Did you disable metadata validation in your asgen run? |
|
Yes. I don't remember the reason TBH, but I've had it disabled for a long time. |
|
@antonio-rojas Ah, that cofused me a lot here, because I thought there was something wrong with the generator not producing any warnings for this ^^ |
When updating the appstream cache with the metadata generated by asgen 0.6.6 and appstrem 0.11.5, we're getting errors:
The text was updated successfully, but these errors were encountered: