-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Reimplemented 'latest_version()' to fix #12663 and make it more readable + better debug-able. #12670
Conversation
Test PASSed. |
Test FAILed. |
@UtahDave can you please take a look here? At first glance it all looks good, but you are the man here |
Test Failed. If the failures are unrelated to your code, don't stress, a core developer will know these apart. |
Test FAILed. |
…ore readable + better debug-able.
Test Failed. If the failures are unrelated to your code, don't stress, a core developer will know these apart. |
Test Failed. If the failures are unrelated to your code, don't stress, a core developer will know these apart. |
Test FAILed. |
Test Failed. If the failures are unrelated to your code, don't stress, a core developer will know these apart. |
Test FAILed. |
@thatch45 No problem… the wait was actually worth it and the PR had to ripen a bit. Found a bug which I fixed and |
Any updates on a review for this one? I'd like to make sure this goes into Helium as fix for #12663. |
Yeah, I'll test this morning. Thanks for your work on this!
|
Reimplemented 'latest_version()' to fix #12663 and make it more readable + better debug-able.
`latest_version' caused some trouble as outlined in #12663
Part of the problem was not using
versions_as_list=True
for retrieving the list of installed package (resulting in version strings of joined single versions like15.0.4420.1017,15.0.4569.1506
), but also a bit convoluted implementation.This re-implementation works fine for me, but a review + test would be appreciated to make sure we don't break anything.