-
Notifications
You must be signed in to change notification settings - Fork 337
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
tests: Fix `/status' endpoint to cater for lists #1371
Conversation
ac000
commented
Jul 25, 2024
•
edited
Loading
edited
Previously, there were no lists in
|
This seems to effect at least Python 3.6 and 3.7. I don't have this issue with Python 3.12 (tested with multiple wasm modules), as it's coming through as a
It's when having Python 3.x and 2.x modules built that I'm seeing it fail on RHEL 8 and AmazonLinux 2. But yes... |
A few Python versions from random buildbot VMs that reproduce the issue:
|
Actually I do... |
Fix commit message
|
Side note: The order of elements in lists is important when comparing them ( |
Where do these two lists even come from? |
Both lists come from GET requests to The reason |
Hmm, of course, they are already sorted by Unit... (by module name, then by version) |
Just to clarify, I'm happy with this patch, whether it's 100% the right thing or not, it solves the immediate issue and merely extends on a previous fix for a similar issue... |
We can now get list objects from the /status endpoint in the case of having different versions of the same language module. That led to this error > return d1 - d2 E TypeError: unsupported operand type(s) for -: 'list' and 'list' We already cover a similar case for when we have simple strings so add this to that. Signed-off-by: Andrew Clayton <[email protected]>
Rebase with master
|