@Jamie Weatherby has left the channel

@Corey Maynard has left the channel

Hello ruby people! If anyone is up for a hacktoberfest contribution, the mock service needs a rack update, and it would be greatly appreciated https://github.com/pact-foundation/pact-mock_service/issues/145

Has anyone been able to get the protobuf + grpc plugin to work with Ruby? I’m having trouble setting it up

@Ruth has left the channel

@Cody Jenkins has left the channel

Hi there... Anyone know an issue when using Pact with Rails 7.1.2 ? I tried to upgrade a Rails app from 7.0.8 to Rails 7.1.2 and Pact start creating issues related with RSpec, even when I am using Minitest The error:

Error:
OperationResultTest::#target_type#test_0001_should be set to configured value after initialize for new record:
RSpec::Mocks::OutsideOfExampleError: The use of doubles or partial doubles from rspec-mocks outside of the per-test lifecycle is not supported.

I am not using Rspec. And looking into Gemfile.lock, I see that Pact is the the introducing rspec. So I decided to disable pact, and my tests are green. Any idea?

@Lukasz has left the channel

Has anyone run into issues having both

service_provider

and

message_provider

in the same

pact_helper.rb

file? The solution I'm about to try is just changing the name of the message provider to

super_secret_name_for_slack_message

, and I expect that to work. It would be ideal though, if we didn't need to have two different names for the provider service depending on which type of Pact we're expecting.

Pact.service_provider "super_secret_name_for_slack" do
  honours_pacts_from_pact_broker do
    pact_broker_base_url pact_base_url, {token: token}
    consumer_version_selectors [version_selector]
  end

  app_version provider_version
  app_version_tags [provider_branch]
  app_version_branch provider_branch
  publish_verification_results publish_flag
end

Pact.message_provider "super_secret_name_for_slack" do
  honours_pacts_from_pact_broker do
    pact_broker_base_url pact_base_url, {token: token}
    consumer_version_selectors [version_selector]
  end

  app_version provider_version
  app_version_tags [provider_branch]
  publish_verification_results publish_flag

  builder do |message_description|
    DatabaseCleaner.clean
    CONFIG[message_description].call
  end
end

Hello! Would it be possible to have a release of the pact-ruby gem with the latest changes? Specially the one regarding the x509 certificates handling. Thanks in advance 🙌

Hey there! I'm having a problem with Pact ruby and provider verification. I've got a service that requires a date passed in the request body that is within next 30 days and can't find a good way to make it dynamic. Static JSON pactfile will obviously mean I would have to update the Pact every month which is not great. Since pact ruby flavour doesn't yet support v3 Pact spec, there's no generators or similar to help out here. Scouring through the code I've noticed https://github.com/pact-foundation/pact-ruby/commit/4ae0b5844aaaacf961af495df6a5d1a97c61f309 some

request_customizer

got added a good while back and in principle should let me achieve what I want to - i.e. dynamically modify the request body before running interaction. However I'm unable to see how I can tap into this/pass customizer as an option when running

bundle exec pact verify

- it's not a CLI recognised option. Any good ideas here?

Trying to set up a quick POC locally. I have a pact json file in my rails app and have followed the guide. 1. Should I be running the rake command against

test

or

development

?

bundle exec rake pact:verify                                                                                                                                                              
rake aborted!
KeyError: key not found: "RAILS_ENV"

2. The API request in the consumer pact is a GET request to get foo/123. How do I ensure this id and associated data will exist in the database? (either test or dev). Surely I don't create this data but if I need do how is this done? I was under the impression that Provider simply pulls down the contract and runs it against an instance of the app. Since this will run on CI then I assume it will run against

test

and out sqlite3 db?

Hello, I have an integration that uses

pact-ruby

on the provider and

pact-js

on the consumer. When I run the provider verification, I see

WARN

logs for >

WARN: Ignoring unsupported combine AND for path

On the consumer side, we're using matchers from the V2 version, not V3, since V3 matchers aren't yet supported by

pact-ruby

. Still seeing these logs, though. Is there any way to suppress these logs on provider verifications other than by increasing the log level to

ERROR

? Thanks.

Hi, I'm interested in using pact-ruby for a project I'm running, however, it looks like for my use case I would require some V3 features. I'm particularly interested in state provider params and I'm wondering if there's a minimum feature set required to contribute at least partial support for V3 Any guidance on implementation also appreciated. Thanks!

@Logi Ragnarsson has left the channel

hey there, some vulnerabilities are flagging up on our end in the pact ruby standalone, appears to be in

rack

v2.2.8, any chance for a version bump and release?

@Pere Villega has left the channel

@Evan Rademacher has left the channel

Hi! My company uses pact-ruby and I'm interested in contributing to the project. I noticed the above message though about just integrating the rust core with ruby, so I'm not sure if it makes sense to do this. What would be the best approach for contributing to getting v3/v4 features? Thanks!

@Michael Strasser has left the channel

@Tomer has left the channel

@Taha Shakibania has left the channel

@Jason Sunde has left the channel

@georgia andrews has left the channel

@PK has left the channel

Hello, team! I'm trying to verify that a pact between our go client and ruby backend returns an integer value rather than a float. Is it possible to configure the pact-ruby side to verify this given pact-ruby only supports v2 of the pact specification?

I have a rails application that uses cookies for session management. In the consumer pact we don't really care about sending the cookie, and on the provider side we use that to specify an account to authorize with. I'm pretty lost with how this should work - in the provider state should I somehow login as a user so I can pass authorization / authentication checks, or how do you all manage an authenticated endpoint?

@Paolo Laurenti has left the channel

@Jocelyn Lecomte has left the channel

@Diego Betancur has left the channel