Hi folks,
started getting this on the provider sid...
# pact-jsa
Arnon Ram
07/13/2023, 1:05 PMHi folks,
started getting this on the provider side, any ideas?
Nothing was changed on consumer or provider sides
Copy code
Pact::UnexpectedIndex Copy code
* Actual array is too long and should not contain a Hash at $.identity_locations[1]t
Timothy Jones
07/13/2023, 1:08 PM“Hash” is the pact Rust core’s way of saying that the array contained an object
Timothy Jones
07/13/2023, 1:08 PM(that’s probably a defect in the Rust core, as I don’t think people are used to talking about json objects as “json hashes”)
Timothy Jones
07/13/2023, 1:09 PMThis message says that the actual array contained two items
Timothy Jones
07/13/2023, 1:09 PMbut it was expected to contain one
Timothy Jones
07/13/2023, 1:09 PMWithout more details, it’s hard to tell what has changed.
a
Arnon Ram
07/13/2023, 1:11 PMstrange, because my expected is like so
I only check types of id and name, and don’t check anything else
Copy code
.willRespondWith({
status: 200,
headers: {
'Content-Type': 'application/json; charset=utf-8',
},
body: {
identity_locations: eachLike({
id: '123',
name: 'xxx',
}),
},
});Arnon Ram
07/13/2023, 1:14 PMi can see the actual. It did not change.
t
Timothy Jones
07/13/2023, 1:15 PMWhat do you mean by it did not change?
a
Arnon Ram
07/13/2023, 1:16 PMthe provider response did not change. It’s as expected with nothing extra
t
Timothy Jones
07/13/2023, 1:17 PMDid not change from what?
Timothy Jones
07/13/2023, 1:17 PMPerhaps open an issue - we’ll need the logs and the full test in order to understand what is happening
a
Arnon Ram
07/13/2023, 1:18 PMahh missed you message that “but it was expected to contain one”
but i have the eachLike, which handles arrays
t
Timothy Jones
07/13/2023, 1:18 PMThe error message is saying that it wasn’t expected to contain two.
Timothy Jones
07/13/2023, 1:18 PMI suspect that the contract that is being verified isn’t from the code that you’re sharing.
Timothy Jones
07/13/2023, 1:19 PMWhich is why we need the full log
a
Arnon Ram
07/13/2023, 1:19 PMsorry, cannot provide full log
but it is from correct test
and i have 5 similar failures 😕
t
Timothy Jones
07/13/2023, 1:21 PMI would run the verifier with debug logging on. I guess that the contract that you’re verifying isn’t from that test, but also I can only guess without more information.
Timothy Jones
07/13/2023, 1:23 PMThe error message is saying that it wasn’t expected to contain two.This is the key point. Either your provider is returning two when it is supposed to return one, or the expectation in the contract is expecting one, when it is supposed to be expecting one or more.
☝️ 1
Timothy Jones
07/13/2023, 1:23 PMOr, there’s a bug, although I think that’s unlikely as this matcher is used widely.
m
Matt (pactflow.io / pact-js / pact-go)
07/13/2023, 1:37 PM
BTW I think that's a Ruby type so my guess is this an older version. The issue template will sort that out
t
Timothy Jones
07/13/2023, 1:40 PMoh right yeah. I think the rust core still calls them non-objects. Dictionary, maybe?
Timothy Jones
07/13/2023, 1:41 PMMap! Looks like I complained about this already: https://github.com/pact-foundation/pact-reference/issues/222
Timothy Jones
07/13/2023, 1:41 PMit should be object. That’s what the O in json is for.
👌 2
2 Views