Closed Yi-FanLi closed 1 month ago
[!WARNING]
Rate Limit Exceeded
@Yi-FanLi has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 49 minutes and 48 seconds before requesting another review.
How to resolve this issue?
After the wait time has elapsed, a review can be triggered using the `@coderabbitai review` command as a PR comment. Alternatively, push new commits to this PR. We recommend that you space out your commits to avoid hitting the rate limit.How do rate limits work?
CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our [FAQ](https://coderabbit.ai/docs/faq) for further information.Commits
Files that changed from the base of the PR and between b89b97bee00c685274f9e8b3657d6b8a51f5839b and e46b23208c5178c8372e9aa52ad1a0178f994f3e.
The recent update enhances the BatchSizeManager
class in batch_size.py
by including a log message in its __init__
method. This log message is designed to assist users in dealing with a specific TensorFlow memory access error, aiming to improve the user experience by providing relevant troubleshooting guidance directly in the code.
File Path | Change Summary |
---|---|
deepmd/utils/batch_size.py |
Added a log message in the __init__ method of the BatchSizeManager class to guide users on handling a TensorFlow memory access error. |
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?
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 82.48%. Comparing base (
8cd3cba
) to head (e46b232
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
But what is "illeagle"?
But what is "illeagle"?
My bad lol. I have renamed this branch and opened a new PR.
When using the GPU version of the neighbor stat code, one may encounter the following issue and the training will stop:
This should be due to some issue of TensorFlow. One may use the environment variable
DP_INFER_BATCH_SIZE
to avoid this issue.This PR remind the user to set a small
DP_INFER_BATCH_SIZE
to avoid this issue.Summary by CodeRabbit