Joaquin Vanschoren

If it reduces the number of API calls this would be useful (even if the API call is a tiny bit slower). If we do this it doesn't really matter...

This is just a warning. The test server is supposed to show these. The production server doesn't. Did you actually have a problem uploading the dataset?

Hi Seb, I recently fixed a number of issues with the test server. Can you please check if this issue is now resolved? Thanks!

The SSL certificate expired while we were waiting for a new one. Hopefully fixed tomorrow. We’re upgrading the dataset hosting, those transient errors should no longer occur then. For now,...

Yes, exactly.

The SSL issue is fixed now. Again apologies for the inconvenience! Please close the issue if everything is working for you again.

Hi Hilde, today I worked on some API bottlenecks, I hope this resolves the issue to a large extent. Later this week I will look at load balancing between our...

Hi Hilde, Apologies again - we're doing a lot of work in the backend to set up Kubernetes and load balancing. I hope these issues will soon be a thing...

Thanks. We're working on the server load issue right now. Also see here: https://github.com/openml/OpenML/issues/1092 It seems that we indeed misinterpreted the meaning of status code 412, but this is meant...

Indeed, this get_csv call was meant as a convenience function rather than a production-ready feature. We're currently moving to a new data infrastructure, based on S3 buckets, in which datasets...