Make checkpoint loading more informative. Remove incorrect Metric type check. Make TableWriter expect a path instead of dir.

[ibro45]

Description

Time for v0.0.3 https://github.com/project-lighter/lighter/issues/118

Related Issue

https://github.com/project-lighter/lighter/issues/125 https://github.com/project-lighter/lighter/issues/121 https://github.com/project-lighter/lighter/issues/90

Type of Change

• [ ] 📚 Examples / docs / tutorials / dependencies update
• [ ] 🔧 Bug fix (non-breaking change which fixes an issue)
• [ ] 🥂 Improvement (non-breaking change which improves an existing feature)
• [ ] 🚀 New feature (non-breaking change which adds functionality)
• [ ] 💥 Breaking change (fix or feature that would cause existing functionality to change)
• [ ] 🔐 Security fix

Checklist

• [ ] I've read the CODE_OF_CONDUCT.md document.
• [ ] I've read the CONTRIBUTING.md guide.
• [ ] I've updated the code style using make codestyle.
• [ ] I've written tests for all new methods and classes that I created.
• [ ] I've written the docstring in Google format for all the methods and classes that I used.

Summary by CodeRabbit

• New Features

  • Enhanced flexibility in specifying save paths, which can now be directories or files, for data logging and saving.

• Bug Fixes

  • Improved consistency in path handling across distributed environments to prevent potential errors during training and prediction phases.

• Refactor

  • Updated internal logic for setting and validating paths, ensuring smoother and more reliable operation.

• Improvements

  • Enhanced error messages for better troubleshooting during model state dictionary loading.

[coderabbitai[bot]]

Walkthrough

The recent updates enhance the lighter framework by replacing the directory parameter with a more versatile path parameter across several classes, offering flexibility in specifying either file or directory paths. This change necessitates corresponding updates to the initialization and setup logic. Additionally, the framework's handling of state dictionaries and logging metrics has been refined to improve functionality and maintainability.

Changes

Files	Change Summary
lighter/callbacks/writer/base.py and lighter/callbacks/writer/table.py	Replaced directory with path in constructors and initialization logic for more flexible path specification. Updated methods to use self.path instead of deprecated variables.
lighter/system.py	Removed a type check for Metric instances before logging metrics in the _log_stats function.
lighter/utils/model.py	Revised logic for checking overlap between checkpoint and model state_dicts, including enhancing error messages with more key details.

In paths and logs, we find our way, With more freedom, less dismay. Refined the checks, and keys relay, To keep our system in bright array.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.