-
Notifications
You must be signed in to change notification settings - Fork 335
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
Error when appending to existing run through remote tracker #2125
Comments
@mihran113 could you please take a look at this? |
Hey @jiyuanq. Thanks a lot for the report. That seems to be a typo actually. Will do the fix ASAP and we'll ship it with the next patch release. |
Thank you for the quick fix! Do we have a test case that covers this scenario? If not, it might be a good idea to add one |
Unfortunately not, we don't have test cases for remote tracking for now. |
Hey @jiyuanq. The fix has been shipped with Aim v3.13.1. Thanks for reporting! |
🐛 Bug
To reproduce
With pytorch lightning, first run training, and then run evaluation with the same AimLogger and the same run hash.
I checked the code (https://github.com/aimhubio/aim/blob/main/aim/storage/treeviewproxy.py#L149), is it actually a typo? I guess it should be 'last_key' instead of 'last'
Expected behavior
It should work correctly like non-remote tracker case
Environment
The text was updated successfully, but these errors were encountered: