Skip to content
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

Fix data size not getting set correctly on the second update in RawImgePlanarMetadata class #400

Open
mohammedzakikochargi opened this issue Feb 28, 2025 · 0 comments · May be fixed by #328

Comments

@mohammedzakikochargi
Copy link
Collaborator

Describe the bug
The issue occurred because nextPtrOffset was being initialized in the rawImagePlanarMetadata class when setting the data size for the first time. As a result, the condition checking if the value was the same as the declared value prevented the data size from being updated correctly on the second attempt.

To Reproduce

  1. Set the data size for the first time.
  2. Attempt to update the data size again.
  3. Observe that the value does not change as expected.

Expected behavior
Ensured that nextPtrOffset is handled correctly so that the data size can be updated multiple times

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Version [e.g. chrome, safari]
  • Cuda Version [e.g. 22]
  • Architecture [e.g. x86_64, arm64]

Additional context
Add any other context about the problem here.

Would you like to work on the issue?
Please state if this issue should be assigned to you or who you think could help to solve this issue.

@mohammedzakikochargi mohammedzakikochargi changed the title Fix data size not getting set correctly on the second update Fix data size not getting set correctly on the second update in RawImgePlanarMetadata class Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant