-
Notifications
You must be signed in to change notification settings - Fork 192
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
bugfix/data bands list ungrouped #5050
bugfix/data bands list ungrouped #5050
Conversation
035d32f
to
fa83575
Compare
Codecov Report
@@ Coverage Diff @@
## develop #5050 +/- ##
===========================================
+ Coverage 80.89% 80.90% +0.02%
===========================================
Files 536 536
Lines 37069 37073 +4
===========================================
+ Hits 29982 29989 +7
+ Misses 7087 7084 -3
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
fa83575
to
cca46fd
Compare
So that answers that long standing question of "who the hell uses these old abstract queries" 😄 To be honest though, I always felt that these shouldn't really be in EDIT: I see now that this is actually used by the |
cca46fd
to
c9ba160
Compare
rebased and test added for the first half of the |
The query relied on `BandsData` nodes to be in a `Group` due to the way the query was constructed because the join always happened through `Group` regardless if the arguments specified group filters. This resulted in ungrouped `BandsData` nodes to never be matched. Co-Authored-By: Sebastiaan Huber <mail@sphuber.net>
c9ba160
to
a60c239
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @dev-zero . I have updated the tests to use pytest
style instead. The AiidaTestCase
method is being phased out.
Fixes #5049