-
Notifications
You must be signed in to change notification settings - Fork 1
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
Valkyrie: Importer and Exporter index page error #758
Comments
Slack Thread: https://assaydepot.slack.com/archives/C0313NK5NMA/p1726166493597369 https://datatables.net/manual/tech-notes/7 related Issue: this occurs in /exporters tables too |
Pulls in fixes bulkrax datatable sort. - #758
Confirmed: it as expected for importers and exporters when I try to sort and page through on multiple staging tenants. |
Folks, the importer "last run" sort feature was fixed on staging, but post cutover, it's not working correctly on prod. I can tell it isn't working correctly because we have at least 27 importers that I recorded myself as running between April 2024 and the present, and the sort that should show most recent importers at the top is only showing one from 2024. Importer page prior to any sort: |
In prod we needed to run a command to fix this. I just ran it, could you try again and let me know if you still see the problem @KatharineV for future self: |
cc @KatharineV actually I still see the issue. We'll need to have a closer look dev noteref: samvera/bulkrax#977 do we need to wrap this task to check for Hyku and account.switch! if so? example:
|
|
@KatharineV Please try again: demo |
@ShanaLMoore yes, I can confirm I see the Last Run sort working on prod now. Thanks! |
When I try to sort importers on ADL Staging, the Last Run and Next Run sort features don't work. They generate the following error message. We need these sort features to work because we use them frequently while managing our importers, and they worked prior to the latest upgrade.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: