Keith Smiley
Keith Smiley
Building with: ``` USE_BAZEL_VERSION=last_green bazelisk build android_app --java_runtime_version=remotejdk_11 ``` reproduces https://github.com/bazelbuild/rules_java/issues/64 Removing the `--java_runtime_version` argument does not reproduce it
Produces copy-able formatting
The only reason this repo uses toolchains is to avoid downloading multiple versions of buildifier that you'll never use on your platform. It looks like if you use some indirection...
We started seeing this crash with our buildkite agents on Linux: ``` SIGQUIT: quit PC=0x468c21 m=0 sigcode=0 goroutine 0 [idle]: runtime.futex(0x1b35a28, 0x80, 0x0, 0x0, 0x0, 0x7fffe24203e8, 0x43a7b3, 0xc000280148, 0x7fffe2420408, 0x40ae9f,...
The MachO version of LLD is being used in production at this point, but the detection incorrectly detected the linker name on macOS. Since the detection was using `string.find("lld")` it...
I just wanted to provide some numbers for our iOS project when using sandboxfs. If this isn't useful for you, feel free to close it. Note: I ran `clean --expunge`...
Looks like there are some new warnings in IB that we're violating
When launching brisk you see this log: ``` TIC Read Status [2:0x0]: 1:57 ``` More details [here](https://stackoverflow.com/a/46431730/902968) for now this looks unfixable
When someone types their 6 character 2 factor auth code, we could autosubmit this
The token received from one authentication is good for some time frame defined by the response JSON. We could store this so we don't have to re-ask for a few...