Closed unkcpz closed 1 year ago
@unkcpz just a quick question, is your fix compatible with both the old and new aiidalab
package versions? I think it needs to be, otherwise it's a mess for the users.
@unkcpz just a quick question, is your fix compatible with both the old and new aiidalab package versions?
Nope, but I see your point. I'll make a change. Thanks for the head up.
It support the old version of aiidalab
. But the test_fingerprint_parser
pass without hitting the correct code path. In the test, it still using the old aiidalab since we didn't release a new version yet.
This is a issue with unit test because of the load_profile()
we used in __init__.py
, I don't have very clear clue why that happened but that need the fix from aiida-core I assume. The workaround is moving the import clause into the test functions. @yakutovicha encounter the same issue in his PR, we need investigate more and then open the issue in aiida-core.
For this PR, I think it is ready to review.
I also move the fixtures in this PR with are duplicate as @yakutovicha did in https://github.com/aiidalab/aiidalab-widgets-base/pull/441/files#diff-e52e4ddd58b7ef887ab03c04116e676f6280b824ab7469d5d3080e5cba4f2128 Let's discuss how we manage these on Thursday.
I also move the fixtures in this PR with are duplicate as @yakutovicha did in https://github.com/aiidalab/aiidalab-widgets-base/pull/441/files#diff-e52e4ddd58b7ef887ab03c04116e676f6280b824ab7469d5d3080e5cba4f2128 Let's discuss how we manage these on Thursday.
I wouldn't worry too much about this. If your PR is merged first, I will adapt mine. If mine - then the other way around. It is really about moving some chunk of code, nothing more than this.
Patch coverage: 100.00
% and project coverage change: +0.47
:tada:
Comparison is base (
76e31cb
) 39.21% compared to head (9fa6dff
) 39.69%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
I am aware that this might not by DRY or whatever, but let's be pragmatic here and define our own simplified local find_installed_packages (without using the Package class). WDYT?
I was worried about it not DRY, but after trying it is very clean. After all, we just need a very simple help function.
Will you take care of cherry-picking this on the 1.x branch and releasing a new version?
Sure I'll do that now.
fixes #445
Note: after this PR is merged, it needs to backport to
1.4.x
as well.