Hi community

This message is to clarify and make transparent the current situation of Public APIs, in addition to demonstrating the frustration of us maintainers. So read this if you find it interesting, please.

Well, I keep the Public APIs project together with other 3 developers (@pawelborkar, @marekdano and @yannbertrand) for a long time.

1 year ago, the Public APIs project was dead, w

expected result:
example.com?param=abc -> will become example.com
example.com/?param=abc -> will stay example.com/

actual result:
example.com?param=abc -> become example.com
example.com/?param=abc -> stays example.com/?param=abc

Issue

The response header does not reflect the correct version for HTTP2 requests. Even though, wiremock replies in h2 but the version in the response header shows "HTTP/1.1 200". This is caused by the hardcoded value in the toString() method of Response.java class

    @Override
    public String toString() {
        StringBuilder sb = new StringBuilder();
        **sb.append("HTTP

What happened?

As parsing time.Duration works only with time periods (i.e 1m, 24h, 23h59m etc.) you cannot specify period in days/months/years as we suggests in help/docs of our commands:
https://github.com/kumahq/kuma/blob/8708885a8ef244f0806aa7d5dae08c7dde64a7bb/app/kumactl/cmd/generate/generate_zoneingress_token.go#L29
we can fix it by changing flag description/help, but I think we

1. Make sure the include_sent_via_pipedream_flag prop is included in every send message action (not currently included in the "reply-to-a-message-thread" action).
2. Add a "Send as mrkdwn" optional prop to all Slack send message actions that use the `chat.postM

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When I schedule new pods I see equally the same behaviour each time - pod fails to start and does 'restarts', kubectl reports minimum 2 restarts before pod is marked as 'running'. in events I see next:

Events:
  Type     Reason     Age                    From               Message
  -

Right now the tutorial is coherently designed, tested, and even documented. However, it doesn't build up in a way that's very beginner friendly. It establishes glom's value and then immediately uses it at an intermediate level.

I'd like it if it was a bit more drawn out to use basic features first and then add a multi-line Coalesce as the

Describe your problem(s)

In the "Complexity Analysis" tab in GraphQL try-out page in devportal, we can see only the complexity Values of each field. If we want to know the complexity value or the depth value, we have to calculate ourself manually. Instead, it would be a nice to have feature to have the possibility to display the calculated complexity/depth values on a button click. So before

Hi, I'd like to implement the flow where verification is triggered via webhook. One can configure various options (ncluding authorization token) for WithPactBrokerSource, however for WithUriSource there's no such possibility. How can I pass auth token when using uri source?

The fastapi example (and perhaps the others) are a little misleading to newbies.

The following lines would suggest that there is pact mock on the provider side, when in reality this is the address of the locally running FastAPI provider:

PACT_MOCK_HOST = 'loca