-
Notifications
You must be signed in to change notification settings - Fork 71
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
ValueError: Expected query, key, and value to all be be jagged at dimension 2, but got query._ragged_idx: 1, key._ragged_idx: 1 and value._ragged_idx: 1 instead. #99
Comments
@sanshe316 I'm able to reproduce this error for both the 2.2 RC and current nightly. cc @jbschlosser @soulitzer . |
#114164 broke this and sadly landed the last day of the 2.2 RC. I'm working on a fix. |
Addresses the regression for Segment Anything Fast in pytorch-labs/segment-anything-fast#99 Pull Request resolved: #115636 Approved by: https://github.com/soulitzer, https://github.com/ani300
Ok @sanshe316 I just reran the snippet on the latest nightly (December 13th) and also landed #105 to make sure it works on CPU (in case that was your intention). We'll make sure the fix also makes it into 2.2. Thank you for opening the issue! Could I kindly ask you to try again? Thank you. |
Addresses the regression for Segment Anything Fast in pytorch-labs/segment-anything-fast#99 Cherry-pick of #115636 into release/2.2 Approved by: https://github.com/soulitzer, https://github.com/ani300
After upgrading from torch-2.2.0.dev20231206+cu121 -> torch-2.3.0.dev20231217+cu121, the problem fixed. Thank you |
Addresses the regression for Segment Anything Fast in pytorch-labs/segment-anything-fast#99 Pull Request resolved: pytorch#115636 Approved by: https://github.com/soulitzer, https://github.com/ani300
Addresses the regression for Segment Anything Fast in pytorch-labs/segment-anything-fast#99 Pull Request resolved: pytorch#115636 Approved by: https://github.com/soulitzer, https://github.com/ani300
Reproduce:
Error stack:
collect_env:
It seems a problem with nested_tensor, but I don't know what causes it and how to fix it.
The text was updated successfully, but these errors were encountered: