mihran113
mihran113
Hey @saurabhgssingh! The main purpose of using `sqlite` for `aim` was to ship the package as a whole and not require any external stuff. With the next major release we...
Hey @andychisholm! Thanks a lot for opening the issue. Previously custom run hashes were allowed, but we restricted that as there have been issues on that See here: #2007 Setting...
Hey @2-5! Huge thanks for the effort. Could you please push the latest changes as well? I'll build it on my local windows machine and try to investigate the issue....
Thanks a lot, I'll have a look. What about logs, it's enabled by adding a `--log-level=info` argument to the command.
Hey @cwognum! Thanks a lot for detailed report. I'll have a look at it. Will keep posted here once any updates.
@cwognum that's actually expected when lot of data is tracked, as when the `fit()` finishes `aim` is trying to clean up the queue of pending values to be tracked as...
so the problem is not in the patch, it's kind of expected anyways when using remote tracking
Hey @igor-byel! The messages on server side indicate that some runs were terminated forcefully, or the network was gone for a long period of time. Is the client process log...
Hey @Alexponomarev7! Thanks a lot for the report. Can I ask you which version of `sqlalchemy` are you using on server side?
And also, is your server-side `aim` on `3.16.2` version?