Tyler Ferrara

Greetings @mostafabarmshory 👋 I'm working on #64 which also involves expanding the project's CI pipeline to include all the same C++ versions as this issue. Since @k06a suggests this project...

# Environment Selection In respect to AppVeyor, this project should support the following: ### Platforms - x86 - x64 - ARM Additionally, [all operating systems defined here](https://www.appveyor.com/docs/build-environment/#build-worker-images) should also be...

@k06a After lots of testing I'm able to run all three platforms. However, Windows has been shown to take several minutes to finish compiling. My question is: How many tests...

Adding an `appveyor.yml` configuration file seems strait-forward and well documented for setting up a [build pipeline](https://www.appveyor.com/docs/build-configuration/#build-pipeline). According to your [travis.yml config](https://github.com/k06a/boolinq/blob/0df37ed90570a148c9d2395f5066313fd59247c9/.travis.yml#L70), this project only targets linux based `x86_64` architectures. Do...

> Interesting question, I believe it should work for x86, x86_64, ARM and ARM64 We can put this to the test 👍

## Update Adding AppVeyor support to a [fork of this project](https://github.com/tylerferrara/boolinq/pull/1). This includes GitHub integrations to run builds and tests for every PR.  Once the build configuration supports your...

@listx appears to be correct! [Here](https://github.com/kubernetes-sigs/k8s-container-image-promoter/blob/0d994e8a53682a831224af62b34065ad88442d9a/legacy/dockerregistry/inventory.go#L1591-L1677) we see two functions that make HTTP requests to GCR. I don't believe this would be monitored by the Container Registry API. This would...

Deployment of this PR: #383 should help us gain insight into the auditor's network usage.

According the the logs, the auditor is periodically restarting.  It doesn't appear to show any error or failing behavior which makes a strong case that Cloud Run is throttling...

We have successfully captured an instance where the Auditor has exceeded quota! This was during the audit of `mock/kube-scheduler`: