-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Problem with bytes &size=self.offset() #1842
Labels
Bug
Something isn't working
Comments
sethhall
changed the title
Expressions in &size?
Problem with bytes &size=self.offset()
Aug 27, 2024
Oh ... Never thought about this but the way |
It's a different issue actually: it's the |
rsmmr
added a commit
that referenced
this issue
Sep 27, 2024
With `&parse-at/from` we were updating the internal state on our current position immediately, meaning they were visible already when evaluating other attributes on the same field afterwards, which is unexpected. Closes #1842.
Ok, that bug is pretty unintuitive. :) |
rsmmr
added a commit
that referenced
this issue
Sep 30, 2024
With `&parse-at/from` we were updating the internal state on our current position immediately, meaning they were visible already when evaluating other attributes on the same field afterwards, which is unexpected. Closes #1842.
rsmmr
added a commit
that referenced
this issue
Sep 30, 2024
* origin/topic/robin/gh-1842-offset: Fix when input redirection becomes visible.
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
I'm not sure if this is related to some expression parsing issue in &size attributes on bytes fields or something else, but I'm seeing a weird behavior...
This works as you might expect (parse 3 bytes then calculate the crc32 for those bytes)...
But this doesn't work (even though
self.offset()
returns 3)...It seems that self.offset() used in the &size field ends up returning zero?
The text was updated successfully, but these errors were encountered: