Neale Swinnerton

In short, clj-aws-s3 doesn't support the v4 authentication scheme, because we're on quite an old version of the AWS SDK. s3 regions created after 30 Jan 2014 use this v4...

@weavejester the point is that for almost all cases the AWS best practice is to supply _no_ creds at all and let the AWS SDK determine what creds to use...

Yes this could be implemented. A wrapper around [getObject(GetObjectRequest)](http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/AmazonS3Client.html#getObject%28com.amazonaws.services.s3.model.GetObjectRequest%29) following the existing patterns in s3.clj would be good as a PR...

The `cooling` queue is an [unbounded](https://github.com/xtdb/xtdb/blob/065f41945daed67c6742a5c480864eaa24f6e48d/core/src/xtdb/cache/second_chance.clj#L182) `LinkedBlockingQueue`, but items are [placed on the queue](https://github.com/xtdb/xtdb/blob/065f41945daed67c6742a5c480864eaa24f6e48d/core/src/xtdb/cache/second_chance.clj#L109) with `.offer` which at least implies there is an expectation in the design that the queue...

Hi, > - Setting http_proxy globally (it's our standard config), per-user and > on the command line > > Looking here: https://github.com/technomancy/leiningen/blob/95bdc72f805d59494ec58e7a63012fe15971d038/leiningen-core/src/leiningen/core/classpath.clj#L99 & https://github.com/technomancy/leiningen/blob/95bdc72f805d59494ec58e7a63012fe15971d038/leiningen-core/src/leiningen/core/utils.clj#L18 It looks like the environment variable...

There has been a change in glib in how a NULL `GMainContext` is [documented](https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3234) in various functions The following patch, prevents the service client crashing, but connections don't get established,...

it is possible to downgrade glib2, connect the VPN, then upgrade glib2 back to the original version to allow other apps to run correctly. Obviously this is only practical if...

https://gist.github.com/Eleonore9/f747540d919f6f1a8fde