btw which RAILS_ENV do you use when running

bundle exec rails pact:verify

? Locally I'm using

development

but on CI not sure which one to use

Hullo, why I am getting error

/usr/lib/ruby/3.0.0/net/http.rb:987:in `initialize': Failed to open TCP connection to <http://xyz.pactflow.io:443|xyz.pactflow.io:443> (getaddrinfo: Try again) (SocketError)

when trying to publish pact via docker CLI? Command:

docker run --rm -w ${PWD} -v ${PWD}:${PWD} --network bridge -e PACT_DO_NOT_TRACK -e PACT_BROKER_BASE_URL \
-e PACT_BROKER_TOKEN pactfoundation/pact-cli:latest pact-broker publish "${PWD}/pactFiles/" --consumer-app-version=1234 --tag=branchName --branch=branchName

@Tõnis Ojandu has left the channel

👋🏽 - is there any significant difference with the following two commands in the docker image `pactfoundation/pact-cli:latest`: • publish • pact-broker publish

@Joris van Eijden has left the channel

@Amit Wertheimer has left the channel

Hellooo! Has anyone used an older version of the pact gem, im using version 1.32.0 and im having some troubles passing in the include_wip_pacts_since, enable_pending, and consumer_version_selectors options. I see this attached error that options method is not found. Even when I passed in any of those options without the options method it would tell me "consumer_version_selectors missing method, undefined method. Am i passing these options in wrong? Because these ones are working fine: • pact_broker_base_url • verbose • publish_verification_results

@Lotem Dagan has left the channel

Hello there! Please, let me ask if there are any plans to update the Faraday gem version for the pact-provider-verifier gem shortly. I am asking this because I can see that the dependency for that gem is specified to be ‘= 0.9.0’, ‘<= 2.0’> and I have a dependency in my repository that needs to use at least 2.5. Thanks a lot for you help!

@Dale has left the channel

@Beth (pactflow.io/Pact Broker/pact-ruby) we are experimenting with pact testing messages. We use kafka, and we want to be able to test the following: 1. MyConsumer sends a message to TopicA 2. MyProvider does some stuff and sends a message to TopicB It looks like that the pact-message-ruby have some testing capabilities to assert on the message MyProvider sends to TopicB that it has to be certain structure and type. However, we don't see any expectations on the message MyConsumer sends to TopicA that trigs the response from MyProvider. Is my understanding correct?

blobwave Are you using pact-ruby? Would you like to collab on work to introduce the pact ffi (rust core) into pact-ruby and the other Pact gems? I’ve already published a couple of gems with the pact_ffi shared lib being loaded into the namespace with ruby’s

ffi

gem. https://github.com/YOU54F/pact-ruby-ffi I’ve learned Ruby by example from our codebases and happy to pair,

Hello there, I have a consumer generated by https://github.com/surpher/PactSwift. So all specifications are from V3. We are a provider on pact-ruby. So do you know how can I remove the warning like this:

WARN: Ignoring unsupported combine AND for path

Thanks a lot 🙏

Hi, do you think that this change proposed is something that we can integrate into pact-ruby to make it support v3?

@Stan Amsellem has left the channel

@Justyna Sliwinska has left the channel

@Teea Alarto has left the channel

@Eytan Hanig has left the channel

@Tigran Davtyan has left the channel

@Georg Duemlein has left the channel

Hi Pact team, quick query re: ruby version of pact ruby standalone. Saw it got bumped to ruby 3.2.2 a few months back, which is fantastic news! My question is, is the pact team gonna track security vulns related to the ruby version and update accordingly? Just need to understand what the maintenance looks like going forward, as our security team will need that info prior to installing the standalone on our end. Thanks a lot!

@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