Hi everyone, do you know how to fix this error: pa...
# pactflows
Sergio Riveros
08/14/2023, 10:10 PMHi everyone, do you know how to fix this error: pact-core@13.15.0: {supportedPlatformsMessage}
We detected your platform as:
- darwin-arm64
We looked for a supported build in this location /Users/Documents/Repos/service/prebuilds/darwin-arm64
Tip: check there is a prebuild for darwin-arm64
check the prebuild exists at the path: /Users/Documents/Repos/service/prebuilds/darwin-arm64
Wrong Path?: set the load path with PACT_PREBUILD_LOCATION ensuring that $PACT_PREBUILD_LOCATION/prebuilds/darwin-arm64 exists
- Note: You dont need to include the prebuilds/darwin-arm64 part of the path, just the parent directory
- Let us know: We can add more supported path lookups easily, chat to us on slack or raise an issue on github
[165753.137] ERROR (22295): pact@11.0.2: The pact mock service doesn’t appear to be running
- Please check the logs above to ensure that there are no pact service startup failures
- Please check that pact lifecycle methods are called in the correct order (setup() needs to be called before this method)
- Please check that your test code waits for the promises returned from lifecycle methods to complete before calling the next one
- To learn more about what is happening during your pact run, try setting logLevel: ‘DEBUG’
Thanks!
m
Matt (pactflow.io / pact-js / pact-go)
08/14/2023, 10:19 PM
Hi Sergio, looks like a #C9VBGLUM9 for the future.
✅ 1
Matt (pactflow.io / pact-js / pact-go)
08/14/2023, 10:20 PM
Have you checked the tips above?
s
Sergio Riveros
08/14/2023, 10:23 PMMy guess is that pact is looking in wrong path
Sergio Riveros
08/14/2023, 10:24 PMit should be looking at the node module levels no? but is looking at the repo level
m
Matt (pactflow.io / pact-js / pact-go)
08/14/2023, 10:26 PM
yes, you’re right
Matt (pactflow.io / pact-js / pact-go)
08/14/2023, 10:26 PM
can you provide a little more info about your setup - is there a repro you can provide?
Matt (pactflow.io / pact-js / pact-go)
08/14/2023, 10:27 PM
Have you also tried updating to the latest (pact-core)?
s
Sergio Riveros
08/14/2023, 10:28 PMUpdating and trying again
Sergio Riveros
08/14/2023, 10:32 PMit solves the first issue but still getting: [173000.489] INFO (27853): 0.4.7: pact native library successfully found, and the correct version
[173001.276] ERROR (27853): pact@12.1.0: The pact mock service doesn’t appear to be running
- Please check the logs above to ensure that there are no pact service startup failures
- Please check that pact lifecycle methods are called in the correct order (setup() needs to be called before this method)
- Please check that your test code waits for the promises returned from lifecycle methods to complete before calling the next one
- To learn more about what is happening during your pact run, try setting logLevel: ‘DEBUG’
Sergio Riveros
08/14/2023, 10:33 PMUnfortunately I cant share code here, but I can send directly to you if that works let me know
m
Matt (pactflow.io / pact-js / pact-go)
08/14/2023, 11:18 PM
sure, you can, ideally a minimal example with no work IP in it would be fine though
Matt (pactflow.io / pact-js / pact-go)
08/14/2023, 11:18 PM
(sorry in a meeting)
s
Sergio Riveros
08/14/2023, 11:44 PMNo worries I will reply to you directly