carbontwelve revised this gist 1 month ago. Go to revision
1 file changed, 2 insertions, 1 deletion
README.md
| @@ -6,4 +6,5 @@ For the time being I have downgraded us to v1.66.0 of gRPC. | |||
| 6 | 6 | ||
| 7 | 7 | - https://github.com/grpc/grpc/commit/245941e0da74afa3e5446105ca3baad2f3bd8a70 | |
| 8 | 8 | - https://github.com/grpc/grpc/compare/v1.66.0...v1.67.0#diff-b468864be3a47863ed0cb9dcf59ce107929f46e5789fff9a5cab33043eeb5518 | |
| 9 | - | - https://github.com/grpc/grpc/issues/38184 | |
| 9 | + | - https://github.com/grpc/grpc/issues/38184 | |
| 10 | + | - https://github.com/grpc/grpc/issues/39509 | |
carbontwelve revised this gist 1 month ago. Go to revision
1 file changed, 9 insertions
README.md(file created)
| @@ -0,0 +1,9 @@ | |||
| 1 | + | While using gRPC at work we started to notice PHP throwing the following error when attempting to communicate via the gRPC extension: *Maximum call stack size of 10436608 bytes (zend.max_allowed_stack_size - zend.reserved_stack_size) reached. Infinite recursion?* | |
| 2 | + | ||
| 3 | + | My initial investigation uncovered [issue 39509 raised against `grpc/grpc` on Github](https://github.com/grpc/grpc/issues/39509) which confirmed the same problem I was seeing was more widespread and related to something internal to the gRPC extension that was introduced in v1.67.0. | |
| 4 | + | ||
| 5 | + | For the time being I have downgraded us to v1.66.0 of gRPC. | |
| 6 | + | ||
| 7 | + | - https://github.com/grpc/grpc/commit/245941e0da74afa3e5446105ca3baad2f3bd8a70 | |
| 8 | + | - https://github.com/grpc/grpc/compare/v1.66.0...v1.67.0#diff-b468864be3a47863ed0cb9dcf59ce107929f46e5789fff9a5cab33043eeb5518 | |
| 9 | + | - https://github.com/grpc/grpc/issues/38184 | |
Newer
Older