📚 Documentation

usegotemplates.md contains examples that have go templates (ie things surrounded in double-curly-brackets), but the website's usegotemplates.html has those important sections stripped out.

Perhaps the pipeline

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

virtual host options

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

Description

We should use ManagedVolume in the DiskSpaceRecoveryITTest to avoid having dangling volumes in case the JVM crashes. While these are tmpfs mounts and not persisted if the host restart, if the JVM crashes they are still dangling and may eat up the memory of the host. This is however only really a problem with repeated crashes on a local machine, and not really an issue in CI wher