-
Notifications
You must be signed in to change notification settings - Fork 177
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
Failure to parse some repos #1325
Comments
Try with |
I have Python 3.11.2 --fatal log:
|
Please provide more information about your system. Also, does this work for you?
|
It's a custom fork of KISS Linux, recompiling python without the "--without-doc-strings" flag fixed the issue. Thanks for helping me figure this out! |
Historically, we've had fetcher and parser args mixed up in the same config dict like this: fetcher: FooFetcher parser: BarParser some_fetcher_arg: 34 some_parser_arg: 12 so we've had to check which arguments parser/fetcher constructor actually understands and pass only accepted args when spawning a class. Currently, parser and fetcher specifications are separate: fetcher: class: FooFetcher some_fetcher_arg: 34 parser: class: BarParser some parser_arg: 12 and, apart from the class name, (should) only contain valid constructor arguments, thus inspect.getfullargspec machinery is no longer needed, so remove it, especially given that it's known to break in some cases (#1325). This also makes parser/fetcher argument handling stricter, which has revealed one problem with amazon linux repo config, specifying args which are not really supported by the parser.
I doubt |
I have installed all the listed dependencies but still get an error while parsing some repos:
Apr 04 06:46:59 parsing arch
Apr 04 06:46:59 ERROR: failed: unsupported callable
Apr 04 06:47:27 parsing ataraxia
Apr 04 06:47:27 ERROR: failed: unsupported callable
It doesn't happen with every repo, for example AUR works fine:
Apr 04 06:47:13 parsing aur
Apr 04 06:47:26 done
Apr 04 06:47:30 parsing calculate
Apr 04 06:47:30 done
I don't see any other errors in the logs
The text was updated successfully, but these errors were encountered: