Recently, I was analyzing some initialization code in Go with a teammate. The value being initialized was meant to be used in concurrent Go, so initialization had some requirement of atomicity. The code essentially boiled down to:
func (t *T) Start() {
if atomic.LoadInt32(&t.State) == Started {
return // Early Exit …Throughout the Go monorepo we use context.WithValue() to "stash" a global
value on a root context. For example
ctx = logger.WithLogger(ctx, log)
// ... later ...
log := logger.GetLogger(ctx)
The implementations for stashing a logger.Log are in the same general form
as most context wrapping helpers:
type loggerKey …For most applications that use a database, user-facing queries must
complete in a reasonable amount of time. In order to ensure a maximum
query time, PostgreSQL supports a statement_timeout which will cause a
query to be cancelled if it exceeds the timeout:
$ psql
monsters_inc=> SHOW statement_timeout;
statement_timeout …
To understand why it's helpful to import external keys into Vault, it's important to understand
TL;DR: Using the
cafield to specify custom CAs (certificate authorities) in Node.js is a footgun. It replaces (rather than appends to) the root trust store which can lead to unintended consequences. I've seen this behavior cause outages in production when a third party server does a routine …