https://pact.io logo
Join Slack
Powered by
# maintainers
  • m
    Good luck at API Days Paris @Yousaf Nabi (pactflow.io) (hope you have notifications off if you’re in the demo 😉 )
  • m
    I’d like to table the following for the agenda tonight: 1. Discuss collection of OSS metrics (again) 2. AI - how might we use this more in OSS land to help accelerate bug fixes, features. Do we have access?
  • m
    sorry for the late notice - I need a night off from Zoom tonight, so will give this one a pass!
    j
    • 2
    • 2
  • t
    @Matt (pactflow.io / pact-js / pact-go) @Joshua Ellis please take a look on this https://github.com/pact-foundation/roadmap/pull/113#issuecomment-3779513819
    👀 2
  • m
    Hey folks, I’ll pass on tonight’s call - had a few big days and need to catch up on things tonight.
  • y
    No worries dude, if anyone does turn up, just drop me a ping here and I will pop in. Outside of that, if you want to reach out directly anytime, just holla
    thankyou 1
  • m
    Likely to miss tonight sorry team. Just getting the kids down and forgot about TZ shift
  • m
    Scrap that, wife will deal with them. But might be a few mins late
    smooth parrot 2
  • r
    Wow, look what Google did: https://github.com/google/magika
    👍 1
    m
    • 2
    • 6
  • r
    The CI builds in the pact-reference are extremely slow (sometimes over an hour). This is mainly queue time waiting for MacOS agents. It currently runs both intel and arm MacOS agents, which I think is a waste as the OS is not going to behave differently on the different architectures. I'm going to remove the intel build, and reduce the matrix a bit.
    y
    • 2
    • 2
  • r
    Coming back to the Pact Plugin proposals. There has been no work on this since 2024, because busy. I have got Mr Claude to revise the proposals and we have broken them down into a number of smaller ones and also fixed a lot of things that were just confusing or no longer relevant. Docos are here: https://github.com/pact-foundation/pact-plugins/blob/main/docs/proposals/README.md
    👀 2
    ❤️ 1
    m
    t
    • 3
    • 9
  • r
    cool doge flip 1
    👍 1
    smooth parrot 1
  • m
    This (and related work) would be good to discuss at this Wednesday’s maintainer catch up ^^
    💯 1
  • r
    I have been going around in circles thinking about how to support simpler Pact plugins, especially when we want to have plugins that can provide new matchers and/or generators. I have come back to using scripting languages as a good candidate for that. I did a spike a few years ago with a Lua content type plugin supporting JWT and that seemed to work ok but only with Rust. A brief investigation for JVM support, and I think it is doable for both Lua and Python. Javascript is a bit more of a problem, firstly they have dropped the Nashorn engine from the JVM in JDK 15, but it is a separate project now so we could still use it. Also, it will be supporting pure JavaScript not Node, and will require something like Webpack to bundle the plugin code.
    👀 1
    m
    • 2
    • 8
  • r
    Have a brief investigation (using Claude) on supporting Python for plugins. Proposal written up in github.com/pact-foundation/pact-plugins/blob/…/010_Support_Python_script_plugins.md
    👀 1
    j
    a
    • 3
    • 21
  • m
    Sorry folks, I'm a decline for tonight's call. Had to duck out to pickup some furniture for kids and need to get dinner before my next meeting
    hug blob but its okay because theyre vaccinated 1
    y
    • 2
    • 1
  • y
    With you in 5 @Joshua Ellis
  • r
    I have updated the Pact plugin callback (007) and Host-provided core matching (009) proposals with a concrete architecture. 009 now just becomes configuration and wiring in in the Pact framework implementations. These allow a plugin to use the capabilities from either another plugin or from the host Pact framework github.com/pact-foundation/pact-plugins/blob/…/007_Driver_plugin_callback_model.md github.com/pact-foundation/pact-plugins/blob/…/009_Host_provided_core_matching_and…
    👀 2
  • m
    g'day, again... months have passed and I still didn't do what I offered to do. Now that the PactSwift drifted past breaking changes in 
    libpact_ffi
    more than a couple of people are willing to contribute. But, I still don't have much time on my hands. So, I promised to move PactSwift and related repos to 
    pact-foundation
    org... I think it's time we start doing that. I'll need help/access to the repos I need to push shallow clone up. Why? Because the history is waaaaaay too big to drag around. We could just transfer ownershipt, but I don't think you want 4GB of history because... `bin`s
    👋 1
    r
    m
    • 3
    • 24
  • m
    Hey folks apologies again but I'm likely to miss tonight (meeting clash). I think Josh is also unwell and should rest
    j
    j
    • 3
    • 2
  • r
    ooohweee 2
  • r
    I have updated the design for the Plugin V2 field level matchers/generators (006) as well as created a example plugin that shows the proposed design for matching/generating credit card numbers. It is a good example because it can check the first 4 digits are correct for the brand as well as the final check digit is valid, which you can't do with a regex. This is the final missing piece for the plugin overhaul. Updated design doc: github.com/pact-foundation/pact-plugins/blob/…/006_Field_level_matchers_and… Example plugin: github.com/pact-foundation/pact-plugins/…/creditcard
    👍 1
    m
    • 2
    • 4
  • r
    I have released Pact-Rust consumer lib (1.4.10) and the verifier cli (1.3.5) with support for Lua plugins and field level matching rules and generators. Pact-JVM 4.7.4 also has support, but it requires the latest plugin driver to work. The example plugin and project works. Here is an example of a provider returning an invalid credit card number
    • 1
    • 1
  • y
    blob wave Won’t be able to make it today to our pact community meeting, and Matt is on PTO. Have a good day/evening all
    j
    • 2
    • 3
  • m
    Hey folks, Unfortunately I’ll have to miss tomorrow (a few conflicts).
    👍 1
    j
    y
    • 3
    • 8
  • m
    FYI I’ll be raising a new invoice in OC soon. Question - do we want to keep paying this? There’s only a handful of secrets in there, and it’s quite expensive. I wonder if moving them to our AWS account secret manager would be a much cheaper and fiscally responsible option. Side note: I still pay that bill, so I should probably claim that too…..
    r
    • 2
    • 7
  • m
    P.S. one more (AWS invoices for past 12 months): opencollective.com/pact-foundation/expenses/346769
  • r
    I have run through a prototype design and build with Claude scoped to answer the questions in the Pact MkII RFC, findings comment here github.com/pact-foundation/roadmap/pull/146#…
    👀 1
    • 1
    • 1
  • m
    Argh, sorry folks - I forgot I had a clash tonight!
  • m
    I know Yousaf’s at API Days so not sure you made it?
    y
    • 2
    • 1