-
Notifications
You must be signed in to change notification settings - Fork 5
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
Remove limit on number of results returned from get_filter_values()
.
#21
Conversation
428a363
to
c9470cc
Compare
c9470cc
to
806a2ae
Compare
806a2ae
to
068f338
Compare
I am having an issue with
However when I use the It is probably out of scope for this PR, but I just wanted to mention with that being the only test breaking for this. |
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.
I was able to reinstall this branch of xdmod-data
in a JupyterLab server. I already had a Notebook running that previously failed to find a specific filter for an Allocation. After reinstalling, I restarted the kernel and successfully managed to grab the information for the allocation.
I also ran all of the available tests. Specifically, the newly added test_get_data_filter_user()
passed.
@connersaeli thanks for reviewing, |
@aaronweeden That was the issue thanks! Sorry about that I elevated my Top Role for something else after I last tried this. |
@connersaeli No problem, thanks again for reviewing. |
Description
This PR removes the limit on the number of results returned from the
get_filter_values()
method. The limit was arbitrary and unnecessary.Tests performed
This PR adds a new regression test to make sure more than 10,000 (the previous limit) results are returned.
Types of changes
Checklist:
CHANGELOG.md
has been updateddocs/developing.md
) produces no errorsxdmod-notebooks
repository as necessary, and the notebooks all run successfully