-
Notifications
You must be signed in to change notification settings - Fork 8k
ext/phar: assert function are not passed NULL pointers #19356
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
Conversation
dabaffb
to
c618444
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks mainly good. For the future it would be good to defer zend_string refactors to another PR because it's just another thing to check, and I already had to reason "recursively" to check the validity for these changes, so less context switching is better
c618444
to
6b0acde
Compare
CI failure is legit. It's probably because of code that was added/changed in the meantime. |
Yeah, but I wanted to extract some of the changes into a different PR which is now done in #20162 I'll rebase after that is merged and fix the NULL pointer attributes :) |
6b0acde
to
4e923ee
Compare
4e923ee
to
4892ece
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The test changes and C changes should likely be committed separately
Right, I forgot about them as I used them to debug my test failures. But those were just caused due to my OpenSSL not being able to verify the signature |
This simplifies some of the logic and makes the assumptions clear
4892ece
to
aa3d4d5
Compare
This simplifies some of the logic and makes the assumptions clear