-
Notifications
You must be signed in to change notification settings - Fork 24
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
Data related infos not working with latest minio version #25
Comments
Can you clarify what version of MinIO you're using? And have you replicated the issue with the version we host below? |
I used that one for the screenshot: https://canlogger.csselectronics.com/cancloud/#/status-dashboard/ |
Do you need more informations ? I can do some more tests if you want. Or try with my dev instance in docker as explained in issue #24 |
We'll have to do some testing of this, it's not something that can be quickly solved necessarily. But we'll look into this next week. |
Arh I see now, I misunderstood the issue. This is working as intended: To avoid excessively loading data from S3, the default view will only populate if there are less than 10 devices. For more devices you'll have to manually specify that you wish to update the view. This could be changed to show the top 10, but that would be a bit arbitrary. |
I understand but the fact is that if for example I have 13 devices, and I select "weekly" only 7 devices updated recently so only 7 items is displayed in the device list at the bottom. This script uses the main device list for this query so it still takes the 13 devices thus returning an empty array and doing nothing. Wouldnt it be better to use the device list filtered in the table so I have 7 devices (which is under the 10 limit)? |
Thanks for the suggestions - we'll review and consider adjusting the behavior in an upcoming update |
It seems like the data related does not work anymore in the latest version of minio. I jumped from a ayear old revision so it's hard to pinpoint exactly where it startted to fail:
It's behaving the same on my local version, your online copy and a self build with an nginx server/dockerfile.
The text was updated successfully, but these errors were encountered: