high-availability

These are all functions/structs for configuring the same thing:

https://github.com/thanos-io/thanos/blob/5bda2d48b9ef0bf138af6132641eb20102223edb/pkg/objstore/azure/helpers.go#L121
https://github.com/thanos-io/thanos/blob/46ac4d590e783368fc4ec7676f29ff97cd0bd630/pkg/objstore/cos/cos.go#L95
https://github.com/thanos-io/thanos/blob/bf963237e0b95402aeea4093dce465abde055675/pkg/objstore/s3/s3.go#

What language are you using?

C++

What operating system (Linux, Ubuntu, …) and version?

Linux

What runtime / compiler are you using (e.g. jdk version or version of gcc)

4.8.5

Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
tars的发布流程：tarsweb上传安装包 -> tarsAdminRegistry开始发布 -> tarspatch 从/usr/local/app/p

We want to have consistent and structured logs to improve the ability to filter and analyse longhorn-manager logs.
Currently the controller uses the global logrus package logger, the task here would be to switch the log calls to the instance logger that was implemented in longhorn/longhorn-manager#661

While doing this also improve the log messages, where possible.
For an example of a successf

Currently we have a mix of:

• Out of memory error.
• Out of memory error
• out of memory error
• out of memory
• out of memory.
• out of memory [some context]

All these should be adjusted to use the same wording for consistency and it should also make the executable a little bit smaller 😄

https://github.com/google/starlark-go/blob/master/doc/spec.md

It should satisfy our reproducibility needs (like jsonnet) and could be easier to write agola config files.

Like in #137 we should provide build context information.

Is there any helm chart to deploy promxy on k8?

Hi, hackers, I'm a database(postgresql variant) developer and we're considering to port pg_auto_failover for our database. The group_id is defined to be a keyword for a long time, which conflicts with the parameter in some functions. We can't change the keyword in our database.
Besides we maintain a new variant of pg_auto_failover, is it possible to change the parameter name group_id to anoth