Hi there! I am trying to use the Hosted API Stubs,...
# pactflowm
Marcus Couto
10/21/2024, 2:49 PMHi there! I am trying to use the Hosted API Stubs, but for one of my interactions, I keep receiving an error like this:
Internal Server Error. An error has occurred. The details have been logged with the reference dMQaVEMjZzm
Matt (pactflow.io / pact-js / pact-go)
10/22/2024, 2:26 AM
That’s an internal error code, but we can look it up
Matt (pactflow.io / pact-js / pact-go)
10/22/2024, 2:29 AM
Any chance you could please log a support ticket (howtosupport)? I can’t tell from the log, but it might be something we need to investigate.
Note that we only support pact files with up to V2 (V3 sort-of works, but the matching rules don’t). It could be relating to that also.
s
Slackbot
10/22/2024, 2:29 AMPlease create a ticket here with the issue details so that we can properly track the resolution and the PactFlow product support team will continue to work through it with you: https://support.smartbear.com/pactflow/message
m
Marcus Couto
10/22/2024, 2:04 PMOh, this is a V4 pact file. I didn’t know it was not supported. The local pact-broker works like a charm.
Marcus Couto
10/22/2024, 6:22 PMI’ve opened a support ticket: 00677189
m
Matt (pactflow.io / pact-js / pact-go)
10/22/2024, 10:22 PM
Oh, this is a V4 pact file. I didn’t know it was not supported. The local pact-broker works like a charm.V4 pacts are supported in PactFlow in the same way that the pact broker supports them, except PactFlow also renders them in the UI. What we don’t support is those files in the stub server (see https://docs.pactflow.io/docs/stubs).
Matt (pactflow.io / pact-js / pact-go)
10/22/2024, 10:22 PM
I’ve opened a support ticket: 00677189thanks. If you attached the Pact or URL to that we should be able to reproduce the issue.
m
Marcus Couto
10/22/2024, 10:37 PMWhat we don’t support is those files in the stub serverThat will be a problem, then. The teams will use Spec V4 to write the pact tests to get the advantage of this version (like using the same name participant name for Sync and Async requests), but they won’t be able to use the API Stubs. Is there any plan to add support to V4? I added my PactFlow Url instance to the case, thank you!
m
Matt (pactflow.io / pact-js / pact-go)
10/22/2024, 11:08 PM
Is there any plan to add support to V4?there is. Tentatively Q1 next year. The primary reason is that the stub server in PactFlow is powered by the Ruby Pact Broker, and uses the Ruby libraries which currently only support up to version 2 (sort of) of the spec. We’ve created (spiked) a solution where we embed the core engine into PactFlow and it works pretty well. We may be able to do it this year, but it needs a bit of testing before we can release it
m
Marcus Couto
10/23/2024, 2:01 PMOk, thank you for the explanation 😉
m
Matt (pactflow.io / pact-js / pact-go)
10/30/2024, 10:19 PM
FYI reviewed the ticket, it’s due to the V4 pact file. Keep an eye on our roadmap for updates on the stub server upgrade
m
Marcus Couto
10/31/2024, 2:11 PMThanks, Matt. What bogs me is that I don’t see the problem using the local Pact broker. Isn’t PactFlow based on it?
m
Matt (pactflow.io / pact-js / pact-go)
11/03/2024, 2:14 AM
yes
Matt (pactflow.io / pact-js / pact-go)
11/03/2024, 2:15 AM
The problem is with the stub server. The local pact broker doesn’t have stubs at all, only PactFlow has hosted stubs
Matt (pactflow.io / pact-js / pact-go)
11/03/2024, 2:15 AM
Maybe you mean something else?
m
Marcus Couto
11/04/2024, 3:32 PMWhat I meant is that I can use the Local API Stubs with Spec V4 without any problems, but it fails when using the same Pact files in PactFlow.
m
Matt (pactflow.io / pact-js / pact-go)
11/06/2024, 5:30 AM
OK, they are two different things entirely. Yes eventually we would support that in PactFlow (hosted stubs with V4) support but it’s not currently. You can continue to use the local stub server in the meantime of course
Oh, this is a V4 pact file. I didn’t know it was not supported. The local pact-broker works like a charm.this is what confused me.