mihran113

Sure, will have look and get back with updates.

@jiyuanq thanks for the detailed report, you've done the heavy work here. 🙌 I've made the changes, we'll ship them with the next patch release.

hey @Aonnghus! Sorry for the late response. Taking into consideration the fact that the performance degradation was started from `v3.12.0`, our guess is that it might have to do something...

Hey @Aonnghus. Glad that helped! One more question: have you ever encountered warnings like this when using aim version > 3.11.2? ``` Using soft file locks to avoid potential data...

> Yes such warnings appeared in stdout Got it. Thanks! We'll include this change in the `v3.14.0` as well, as a workaround for now. In the meanwhile we'll try to...

hey @Aonnghus. One more question regarding your setup, what protocol did you use to mount your home directory?

Hey @spacegoing! You can filter runs based on the metric's `last_step` value. Here is an example for that: ``` run.metrics['name', {"some": "context"}].last_step > 1000 ``` You can also check out...

Hey @creinders! There's a workaround to delete sequences from runs via SDK. You can have a look at it here: https://discord.com/channels/1047782741736968202/1093472675470528562/1095733594963587192 We'll try to add a much better way to...

Hey @hstojic! Thanks for the report. From the logs above it seems that something goes wrong when using SSL and grpc (we're using grpc for tracking server). I've done some...

Hey @PeterSulcs! Sorry for such a long delay. Could you please try out this version of `aim` and see if it successfully collects data for MIG GPU instance? ``` pip...