James Munson
James Munson
### Host operating system: output of `uname -a` Linux 5.10.58 ### node_exporter version: output of `node_exporter --version` node_exporter, version 1.2.2 (branch: HEAD, revision: 26645363b486e12be40af7ce4fc91e731a33104e) build user: root@b9cb4aa2eb17 build date: 20210806-13:44:18...
To be clear all documentation states that the input string should be "warn" and not "warning", but since this is typically used when accepting user configuration, it would be nice...
**Describe the bug** When the volume of API calls gets high we start seeing requests fail with ```WARNING:urllib3.connectionpool:Connection pool is full, discarding connection: {hostname of jira}``` **To Reproduce** I have...
I'm trying to write some code that will store files on S3, but not overwrite them if they already exist. To do this I'm calling HEAD first to see if...
This is decent sized refactor of all logging code. The "file" backend could still use more work, as it doesn't retain the calling spec. We still respect the configuration options...
### What version of shadowsocks-libev are you using? Debian package shadowsocks-libev 3.3.5+ds-4 ### What operating system are you using? Debian 11 (bullseye) ### What did you do? Run one instance...
It would be nice if this were replaced by reading a password from the environment (which then could be provided via `docker secrets`), and then if a password is not...
I noticed that if fan control is open it constantly reserves 100MB of dedicated GPU memory, even when the window is minimized. The only way to free up the memory...