jade
### Describe the issue Regression in #1905 cc @jamesdbrock @Nebucatnetzer With a lock file entry like: ```toml [[package]] name = "colorama" version = "0.4.6" description = "Cross-platform colored terminal text."...
Currently (tested on 2.0) the default hooks in Amazonka will log credentials like `x-amz-security-token`: ``` [Client Request] { host = redacted.s3.us-east-1.amazonaws.com:443 secure = True method = PUT target = Nothing...
I am filing this issue in light of some oopsies we did in production, because it's not very obvious when a value is a CTE versus a subquery and that...
Hi! I have some hpack includes which aren't working due to, erm, *probably*, what we refer to as "yaml footguns" at work: ```yaml # /!\ /!\ /!\ /!\ /!\ /!\...
Uses amazonka-s3, which auto discovers credentials. Did some manual testing: ``` glean --tier test --db-root ~/glean backup myrepo/0 s3:mybucket/jade-test glean --tier test --db-root ~/glean2 restore s3:mybucket/jade-test/myrepo.0 ``` Configuration ~/.config/glean/server/test, though...
This is required for Nix builds. I also switched pwd to be resolved from PATH because /bin/pwd is not a thing on NixOS.
It would be nice if dependencies were cached for OSS CI so that it would merely have to wait for glean itself to build. The goal here is CI down...
In general `GLOG_v=3` works, but the shell code overrides user input about the log level (!!): https://github.com/facebookincubator/Glean/blob/0a424535b09a7b30fd0e8b01da1a5ff1c4de9bbd/glean/shell/Glean/Shell.hs#L1423-L1425 However, either way, it's not really documented anywhere that this logging situation is...