Closed dberenbaum closed 8 months ago
Attention: 130 lines
in your changes are missing coverage. Please review.
Comparison is base (
8406920
) 88.79% compared to head (2f81b3f
) 86.81%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Great work! Thanks, @dberenbaum for pushing forward integrations. Some comments as I'm reviewing / running it:
mypy
CI errors@dberenbaum looks good to me overall (I didn't review really deep the Fabric existing loggers to actually deeply review the implementation, but overall it looks fine). I've enabled mypy back + left a comment about VS Code to review, probably also Studio needs to be reviewed / tried out.
Should mypy be included in https://github.com/iterative/dvclive/blob/main/.pre-commit-config.yaml?
I would ask @skshetry and the team on what the current state of the art for this :)
@skshetry How should mypy checks be handled?
ping @skshetry
I would ask @skshetry and the team on what the current state of the art for this :)
We use nox
for environment management on py-template based projects. So, you can pip install nox
and then nox -s lint
will take care of everything related to linting.
Since dvclive seems to have removed nox, you can try adding mypy to pre-commit but up to you. Look into dvc's pre-commit config.
Depends on #757 now. The remaining test failure is unrelated.
Closes #742. Fabric is Pytorch Lightning's attempt to abstract out the lightweight parts of their codebase so users can benefit from those without having to entirely adapt Lightning.
The existing Lightning logger was updated to inherit from this one. To make everything work with the existing Lightning logger, I added a
sync
method that decouplesnext_step
from saving all the info to Studio, dvc.yaml, etc. I made it public, but no strong opinion on whether it should be public or documented.See the Tensorboard logger in lightning for an example of another logger: