Closed asgrim closed 1 year ago
Our suspicion is that this extension does not correctly work on PHP 8.1 yet - we are still seeing a segfault, and wonder if the API in PHP changed significantly enough that something in this extension is not compatible yet.
We've tried this using PHP 8.0 instead - it removed the deprecation notice, but sadly we are still receiving the segfault when we call headBucket
(as described above).
We are working around the issue by using a bucket name instead of ARN, so that the Signature V4a is not used, and therefore the aws-crt-php extension is not required. There was definitely a segfault coming from the extension, but as we are not requiring the extension any more, I'm afraid we can't provide further information.
Confirm by changing [ ] to [x] below to ensure that it's a bug:
Describe the bug
When calling
headBucket
like this:We are receiving an error
This appears to be
awslabs/aws-crt-php
internal issue, as thenull
mentioned is coming from this on Line 16:https://github.com/awslabs/aws-crt-php/blob/541b3c8952d164e0a852b38ca358e263403419d4/src/AWS/CRT/Auth/Signing.php#L12-L16
There does not appear to be a way to provide the required
$user_data
parameter.SDK version number
We are building the
aws/aws-crt-php
extension using:Platform/OS/Hardware/Device
AWS Lambda running a custom Docker image, with PHP 8.1 - the Dockerfile is here
To Reproduce (observed behavior)
Expected behavior
We expect the
headBucket
call to return information about the bucket.Logs/output
Note: no stack trace is displayed, and the script seems to terminate with a segfault, although we have not confirmed if this is the extension or not. I suspect if the extension does not accept null, then there may be some memory being accessed or written illegally