Hello!

When using OAuth2 with authorization flow we usually need to test some APIs with different users. There is no quick way to clear the authorization session besides the "Clear OAuth 2 session" in the preferences dialog.

I would suggest to bring or replicate the Clear OAuth 2 session button to the Advanced Options in the auth tab. This would allow changing authenticated users faster

🐛 Bug Report

In v2, repeated fields are now only allowed once per global scope:

https://github.com/grpc-ecosystem/grpc-gateway/blob/4a35071321dc8a3fc19e8042ed54110fd1a42835/runtime/fieldmask.go#L77-L82

There is a single comment in the protobuf spec that mentions

When using type google.protobuf.Timestamp, BloomRPC maps this to an object, e.g.:

"create_time": {
  "seconds": "1562723637",
  "nanos": 928852400
}

However, the Google API Design Guide specifies that the string representation should be RFC 3339 format, e.g. "2014-07-30T10:43:17Z"

This JSON mapp

我需要

可我在hyperf中不知道该如何使用write

In our codebase, we push RequestContext and immediately run some code with try-with-resources.
For example:

try (SafeCloseable ignored = ctx.push()) {
    logger.trace(decorate(msg));
}

If RequestContext provides run(Runnable) or call(Callable) we can reduce boilerplate code and simplify it.

ctx.run(() -> logger.trace(decorate(msg));

This is inspired by g

We have a fancy logo from the new tokio website, we should go through the code base and update it in every spot we use the old one.

https://github.com/tokio-rs/website/blob/master/public/img/icons/tonic.svg

Is your feature request related to a problem? Please describe.
Gloo Edge users want an easy-to-implement solution for CSRF protection of their applications.

Describe the solution you'd like
Add support for upstream CSRF filter in Gloo Edge.
https://www.envoyproxy.io/docs/envoy/latest/api-v2/config/filter/http/csrf/v2/csrf.proto
https://www.envoyproxy.io/docs/envoy/latest/start/sandb

Issue Description

是否有计划用actions 完全取代 TravisCI
感觉actions 速度上比 TravisCI更好点 ，另外也是github原生的。

Type: feature request

Describe what feature

Feature Request

There are many config generation options in talosctl cluster create which make no sense with --input-dir as they're going to be ignored.

Description

Fail with error message is any gen options are used with --input-dir. This might confuse users as arguments are silently ignored.

At present we can run the load generator for a set amount of time or a certain number of requests.
I would like to a mode --reconnetRequests=1000 where fortio client will reconnect after 1000 requests.

Use case: We are testing SDS cert rotation using an https fortio client (std client).
For cert rotation to be exercised fortio should reconnect periodically to fetch the new cert.
In