aws-sdk-go

ch. That's an effort most devs won't take on. I'd also guess that many developers, up-to this point if not indefinitely because education is hard, interpreted that `go` directive to mean more-of "the version of go this was built with"; not necessarily "the version of go minimally required". There are really major libraries (kubernetes/client-go [1]) which assert a minimum go version of 1.20; the latest version (see, for comparison, the aws-sdk, which specifies a more reasonable go1.11 [2]). I haven't, you know, fully audited these libraries, but 1.20 wasn't exactly a major release with huge language and library changes; do they really need 1.20? If devs haven't traditionally operated in this world where keeping this value super-current results in actually significant downstream costs in network bandwidth (go1.20 is 100mb!) and CI runtime, do we have confidence that the community will adapt? There's millions of Go packages out there. Or, will a future version of Go patch a security update, not backport it more than one version or so, and libraries have to specify the newest `go` directive version, because manifest security scanning and policy and whatever? Like, yeah, I get the rosy worldview of "your minimum version encodes required language and library features", but its not obvious to me that this is how this field is, or even will be, used. Just a LOT of tertiary costs to this change which I hope the team has thought through. [1] https://github.com/kubernetes/client-go/blob/master/go.mod#L... [2] https://github.com/aws/aws-sdk-go/blob/main/go.mod

com/aws/aws-sdk-go/issues/2130 1: see the ListObject page under "encoding-type"

a series of brittle aliases to disptach the proper version? ~ which terraform terraform () { binary=terraform if [[ $1 == "v"\* ]] && [[ $1 != "validate" ]] then version=$1 shift binary="$binary-$version" [ -f ~/bin/$binary ] || bail 1 "missing binary $binary" || return 1 else binary=/usr/bin/$binary fi dispatch --name terraform --scope --slice compilers.slice -c 35 -mh 2048M -mm 2048M -s 1M --binary $binary "$@" } (dispatch just runs things with memory and cpu limits) ~ which dispatch dispatch () { if [[ $USER == "root" ]] then command "$binary" "$@" return $? fi declare args=(--user --same-dir -p IOAccounting=yes -p MemoryAccounting=yes -p TasksAccounting=yes) while (($#)) do case "$1" in (-c) args+="-p" args+="CPUWeight=$2" shift 2 ;; (-mm) args+="-p" args+="MemoryMax=$2" shift 2 ;; (-mh) args+="-p" args+="MemoryHigh=$2" shift 2 ;; (-s) args+="-p" args+="MemorySwapMax=$2" shift 2 ;; (--scope) args+=--scope shift ;; (--slice) args+="--slice=$2" shift 2 ;; (--name) name=$1 shift 2 ;; (-P) args+=-P shift ;; (--binary) [ -z "$name" ] || name=$2 binary="$2" shift ;; (*) break ;; esac done systemd-run $args "$@" 2> >(>&2 grep -vE 'Running.*as unit:') } and of course, then you'd need a shitty little script to call your alias when other tools decide they want to call terraform ~ cat ~/bin/terraform #!/usr/bin/env zsh source ~/.zshrc >/dev/null 2>/dev/null || exit 1 terraform $@ Because that would be silly and dumb, and I totally don't do that for everything. Don't even get me started on virtualenvs.

n of memory ready to be reclaimed. Even a major library like the official AWS SDK's S3 client had this wrong as recently as 2017 (solution was to use sync.pool to avoid throwing away buffers): https://github.com/aws/aws-sdk-go/pull/1784 Python should perform much better from a memory perspective in these situations: its weakness would be the deserialized size that objects blow up to in memory, but its use would be bounded. Java would also handle this pretty effortlessly, though with a high enough rate of garbage production might hit a few short GC pauses that last far less time than a process restart. Really wish go were better about this. Imagine that a simple Go cronjob that uploads a backup to s3 at under a 160MB/sec could risk you OOM killing your server if you don't set cgroup memory caps on all your go processes.

e Storage Service service client for testing your code. With the exact same name, to boot. Please consider providing and returning interfaces. Even if your struct is the only type implementing it.