[BugFix] Reject invalid ReplayBuffer generations - #4043
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/rl/4043
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 1a289eb with merge base 82a2593 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
6b96677 to
6b16ca6
Compare
6b16ca6 to
b8bf0a7
Compare
|
Rebased onto current main and #4046, resolved the obsolete generation-stamp history, and marked this ready for review. The focused core, Ray, and doctest coverage passes locally. I do not have permission to request reviewers or apply labels; @vmoens, could you review and add the |
|
Reviewed rebased head One blocking correctness issue is at Targeted result: all 14 |
b8bf0a7 to
00375a9
Compare
|
Since #4049 landed the conditional-update feature on main, I rebased this PR down to the reported correctness fix. Negative current or captured generations are now always stale, with a never-written-slot regression. Focused result: 30 passed. |
Rejects never-written replay slots from
update_if_presentwhen both generation values are-1.Test:
pytest test/rb/test_rb_core.py -k TestUpdateIfPresent