Does anyone know why pact ffi library 0.5.9 hang o...
# maintainers
t
Does anyone know why pact ffi library 0.5.9 hang on Windows, while 0.5.8 work fine? It hang without any log or error message, so I don't have any to share github.com/pact-foundation/pact-php/pull/829
blob wave 1
y
I can't see any reason via the changelog. Is it a particular interaction type or mode? Just released 0.5.10 Happy to take a look on a windows machine
hmm 0.5.10 made more failures 😂 github.com/pact-foundation/pact-php/pull/830 got a green ci run against pact-ruby-ffi (which tests alot less of the ffi surface) github.com/pact-foundation/pact-ruby-ffi/pull/25
r
0.5.9 added a log callback mechanism, which I guess was never tested on Windows
Stick to 0.5.8, the later versions don't have anything you really need
@Tien Vo did you resolve your issue? I see this PR addresses an issue when using the logging calback from C/C++ github.com/pact-foundation/pact-reference/pull/559
t
@rholshausen I resolved my issue. but it's not related to logging calback. It's a pipe deadlock between Pact FFI 0.5.9 and PHPUnit process-isolation on Windows Before 0.5.9: • Parent process read
stdout
• Child process call
pactffi_init_with_log_level
-> write
stdout
After 0.5.9: • Parent process read
stdout
• Child process call
pactffi_init_with_log_level
-> write
stderr
I follow suggestion from github.com/YOU54F/pact-php/pull/3, and replaced
pactffi_init_with_log_level
with
pactffi_logger_init
+
pactffi_logger_attach_sink
to
stdout
+
pactffi_logger_apply
r
Ok, great.