https://pact.io logo
Join Slack
Powered by
Hello again, I'm working on verifying a pact I gen...
# pact-js
a
Hello again, I'm working on verifying a pact I generated. I set the log level to 
debug
and am seeing a lot of this error: 
[tracing-subscriber] Unable to write an event to the Writer for this Subscriber! Error: Resource temporarily unavailable (os error 35)
as well as 
Caught panic with error: failed printing to stderr: Resource temporarily unavailable (os error 35)
It seems like the test is getting about halfway through the matchers before randomly stopping. Unsure if theres a setting I need to change so any advice here would be appreciated.
thread '<unnamed>' panicked at 'failed printing to stderr: Resource temporarily unavailable (os error 35)', library/std/src/io/stdio.rs:1019:9
m
A panic whilst printing to stderr, haven't seen that one before. Could be a red herring. Feel free to share the logs here and we can a peek
a
The issue is that there's not much to show from the logs, its just going through the matcher but occasionally it will show something like this
Copy code
[tracing-subscriber] Unable to write an event to the Writer for this Subscriber! Error: Resource temporarily unavailable (os error 35)

[tracing-subscriber] Unable to write an event to the Writer for this Subscriber! Error: Resource temporarily unavailable (os error 35)

[tracing-subscriber] Unable to write an event to the Writer for this Subscriber! Error: Resource temporarily unavailable (os error 35)

[tracing-subscriber] Unable to write an event to the Writer for this Subscriber! Error: Resource temporarily unavailable (os error 35)

[tracing-subscriber] Unable to write an event to the Writer for this Subscriber! Error: Resource temporarily unavailable (os error 35)

[tracing-subscriber] Unable to write an event to the Writer for this Subscriber! Error: Resource temporarily unavailable (os error 35)

[tracing-subscriber] Unable to write an event to the Writer for this Subscriber! Error: Resource temporarily unavailable (os error 35)

[tracing-subscriber] Unable to write an event to the Writer for this Subscriber! Error: Resource temporarily unavailable (os error 35)

2023-09-20T19:07:44.686013Z DEBUG ThreadId(02) verify_interaction{interaction="a request for all processing accounts for a business"}: pact_matching::json: compare: Comparing path $.processingAccounts[2].parent.serviceType
If theres something specific I should look for in the logs that would help, I can't really copy the whole thing since its hundreds of lines
Copy code
Caught panic with error: failed printing to stderr: Resource temporarily unavailable (os error 35)
[12:07:44.693] DEBUG (38324): pact-core@14.0.4: shutting down verifier with handle 0
2023-09-20T19:07:44.694175Z DEBUG ThreadId(01) pact_ffi::verifier: pact_ffi::verifier::pactffi_verifier_shutdown FFI function invoked
[12:07:44.694] DEBUG (38324): pact-core@14.0.4: response from verifier: null, 1
[12:07:44.694] ERROR (38324): pact-core@14.0.4: Verification unsuccessful
m
So it looks like it does complete. Any chance you could put together a repro for this we could use to debug the issue? Is this locally on your machine, or CI and what is the OS etc.? You can then raise it here: https://github.com/pact-foundation/pact-js/issues and we can investigate
Open in Slack
PreviousNext
Powered by