I made up a guide to setup Firebase services into a real-world scenario with cutting-edge technologies. I think you could get some insights on DX of your services and how they are used out in the wild (or add it to this examples repository).
Tech used: Quasar (Vue), TypeScript, Jest (unit testing), Firebase Firestore, Cloud Functions, RxFire.

Inside the guide there are some helpers and code ma

Thanks to @miekg and code they added here: https://github.com/coredns/coredns/blob/master/test/metric_naming_test.go

Is your feature request related to a problem? Please describe.
Provide help in CLI for sub-commands

Describe the solution you'd like
Sub-commands help should describe the sub-command's functionality and options available for the sub-command

Describe alternatives you've considered
N/A

Additional context
See: golang-migrate/migrate#370

According to the postgresql documentation on https://www.postgresql.org/docs/current/static/continuous-archiving.html section 25.3.3.1 you can pass 2 extra parameters to pg_start_backup().

I'm particularly interested in the second parameter which does a fast checkpoint.

Is this a feature which can be added as a command-line parameter to wal-e backup-push eg `wal-e backup-push --fast-chec

Is there some documentation or user guide for this project?
I've just spent half an hour figuring out how to mount with goofys inside a docker container -- it's not a big deal, of course, but I'd like to write it down, so that others can figure it out faster.

When s3proxy trace logging is enabled, the jclouds logging should be enabled as well. It's most certainly going to be required to understand whether there is an issue in the actual response from the provider vs s3proxy translation of the response.

Is it mandatory to put windowing in unbounded pcollection from pubsub if i'm not using any aggregation steps i.e groupbyKey?

A note in following link is as follows.
https://cloud.google.com/dataflow/docs/guides/specifying-exec-params

**If your pipeline uses unbounded data sources and sinks, it is necessary to pick a Windowing strategy for your unbounded PCollections before you use any aggre

In the following lines, we check if the visibility has been specified, and if it hasn't we default to private. https://github.com/Superbalist/flysystem-google-cloud-storage/blob/master/src/GoogleStorageAdapter.php#L143-L149

Is there any reason we need to default to anything at all? If we specify nothing, the default object ACL of the bucket should be applied (by default private, visible to owne

Hi,
after connecting to ssh repository using Kopia UI ,if the connection is lost, Kopia UI will not reattempt to reconnect to the ssh server again.
logs says after every scheduled backup:

06:31:16.332 [kopia/server] error refreshing repository: error refreshing content index: failed to send packet: EOF
06:31:19.000 [kopia/server] starting upload of LLED2@lled2-pc:F:\_bin\_bin\_backup\ko

TL;DR: All the google-cloud-cpp-* GitHub repos will be combined into this repo as a single "monorepo" in Q2-2020. We apologize for any confusion this may cause our customers, but we think this will be much simpler for our customers going forward. This should not result in any build breaks for our customers, but in order for customers to pick up the newest monorepo versions of our lib

As the sole active maintainer, I'm looking for co-maintainers for the project to push features faster.
Please ping me if you're interested.

It'd be awesome if you have already contributed to the project and interested. Otherwise, there would be a brief probation period after starting contributing to the project.

I installed the helm chart 1.5.1 into a GKE cluster:
helm install -f values.yaml --name cicd stable/sonatype-nexus

When the ingress is ready, I always get "default backend - 404" when visiting my nexus service IP/host.

$ kubectl describe ingress/cicd-nexus-sonatype-nexus
Name:             cicd-nexus-sonatype-nexus
Namespace:        default
Address:          35.190.xxx.xxx
Defaul

I think the README should mention that there is no guarantee that postStart hook finishes before container's entrypoint is called so the container might try to access the storage before the mounting finishes.

The safe way would be to mount it in container's command, e.g.:

command: ["/bin

Currently, the installation instructions for CRMInt contain this line:

bash <(curl -Ls https://raw.githubusercontent.com/google/crmint/master/scripts/install.sh) master

It looks like you are doing active development on master... It seems to me you should either make a separate dev branch and only merge to `maste

Currently, if you check for ACLs of a new bucket you get:

gcs_get_bucket_acl('{bucket_name}')

Error: API returned: Not Found

Perhaps, it should guide the user to create ACLs first using gcs_create_bucket_acl().