I

start

the main mock server. After that, I

create

a new mock server from a pact file. The debug output of the main server shows this:

13:29:03 [DEBUG] (18) pact_mock_server_cli::server: Starting mock server with id 49c8834c-661f-4b65-94ce-03d9384bb330
13:29:03 [DEBUG] (18) pact_mock_server::mock_server: Started mock server on 0.0.0.0:51714
13:29:03 [DEBUG] (18) pact_mock_server_cli::server: mock server started on port 51714
13:29:03 [DEBUG] (18) pact_mock_server_cli::server: Result of starting mock server: Ok(true)
13:29:03 [DEBUG] (4) pact_mock_server_cli::server: Result of thread: Ok(true)

When I run

./pact_mock_server_cli list

after that, the

list

call hangs. This is the only debug info shown on the main server:

13:29:30 [DEBUG] (11) hyper::proto::h1::io: parsed 3 headers
13:29:30 [DEBUG] (11) hyper::proto::h1::conn: incoming body is empty
13:29:30 [DEBUG] (11) pact_mock_server_cli::server: main_resource -> resource_exists
13:29:30 [DEBUG] (11) pact_mock_server_cli::server: main_resource -> render_response

Am I doing something wrong? Any known issues with this?

I don’t know - in most use cases, you don’t need to interact directly with the mock server like this. What are you trying to do?

@Timothy Jones see the other thread on what I’m trying to do.

Interesting!

The

list

command was already to debug the fact that my created mock server wasn’t responding at all.

Yeah, I thought that might be the case.

Thanks for the suggestion, but I’m going to stop investigating this way for now. I already have to debug our customer problem. Not going to debug the pact tooling on top of that. No offence.

That’s very reasonable.

If I read this correctly you are using the pact tooling, in your tool for your customer. I think it is completely reasonable that you raise debug steps for us to follow up. We don't expect you to debug it, but if you are asking for help here, and we are openly providing it, it would be kind to share a repro back

This is a small handwritten pact file, which I want to return the

body

when a

GET

is done on the given `path`:

{
  "provider": {
    "name": "PulumiService"
  },
  "consumer": {
    "name": "PulumiCLI"
  },
  "interactions": [
    {
      "description": "History request",
      "request": {
        "method": "GET",
        "path": "/api/stacks/redacted_customer_name/redacted_project_name/dev/updates?output-type=service&pageSize=1&page=28",
        "headers": {
          "Content-Type": "application/json"
        },
        "body": {},
        "matchingRules": {}
      },
      "response": {
        "status": 200,
        "headers": {
          "Content-Type": "application/json; charset=UTF-8"
        },
        "body": {
          "updates": [
            {
              "info": {
                "kind": "import",
                "startTime": 1669315256,
                "message": "",
                "environment": {},
                "config": {},
                "result": "succeeded",
                "endTime": 1669315256,
                "version": 139,
                "resourceChanges": {
                  "create": 0,
                  "delete": 0,
                  "same": 58,
                  "update": 0
                }
              },
              "updateID": "3b1f14e2-bc4e-4b5a-8875-2a56c5fd0217",
              "version": 139,
              "latestVersion": 139,
              "requestedBy": {
                "name": "",
                "githubLogin": "redacted-user",
                "avatarUrl": "<https://avatars.githubusercontent.com>"
              }
            }
          ],
          "itemsPerPage": 10,
          "total": 139
        },
        "matchingRules": {}
      }
    }
  ],
  "metadata": {
    "pact-specification": {
      "version": "3.0.0"
    },
    "pact-jvm": {
      "version": "3.5.6"
    }
  }
}

Awesome, thanks. It being hand-written is a good bit of info - I don’t know if much validation is done, as it expects the Pacts to be generated by Pact.

@Yousaf Nabi (pactflow.io) fair point. I’m only under time pressure to follow up on this Pact based setup. Need to find another way to get to the bottom of my customer issue first.

Although at a glance it looks ok

No rush @Ringo 💛 in your own time, we are here all the time 😅 Hope you get a happy customer in the end

FYI: I’m mocking our Pulumi Service REST API here: https://www.pulumi.com/docs/reference/service-rest-api/

Oh very cool, your companies name came up recently in conversation, I can't remember with whom, as something to checkout. I'm definitely interested in helping you get to the bottom of it eventually and learning a bit more about Pulumi on my journey. Your docs look fabulous

I know. Matt contacted me recently.

Ah I see you are using Pact-JVM. AFAIK, the pact-jvm doesn't use the Rust reference implementation and has its own core. (or this pact was created with pact-jvm)?

I don’t think your Pact file is the problem - I experience the same issue with a different pact file written by Pact-JS

@Timothy Jones sorry I was silent until now, but I had a few customer calls. Will see if I can get it working. Thanks for your help already! 🙏