ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #erlang
Mnesia transaction retry duplicates writes on deadlock or timeout Goal: confirm whether Mnesia re-executes write operations when a transaction restarts after a deadlock or timeout, and whether any built-in API prevents duplicate writes across those retries. Mnesia automatically restarts a transaction on contention, but documentation indicates that side effec
When using the erlang_time module to convert UTC timestamps to local time, a specific challenge arises during the 'fold' period of a Daylight Saving Time transition. In these instances, the same local time occurs twice as the clock shifts back. The current behavior of erlang_time:from_local/1 relies on the host system's IANA time zone database but appears to
When targeting the Erlang VM (BEAM), Gleam leverages immutable data structures and exhaustive pattern matching to ensure runtime stability. For low-traffic workloads, the primary goal is to minimize the baseline memory footprint of the compiled bytecode to reduce infrastructure costs. While Gleam's compilation to Erlang bytecode is efficient, the actual memo
EPMD and Erlang distribution bind address after OTP version change Goal: confirm whether EPMD and Erlang distribution sockets bind to all IPv4 and IPv6 interfaces or to loopback only when inet_dist_use_interface is not set at node startup. The affected feature is distributed Erlang node discovery through EPMD on TCP port 4369 and distribution ports from inet
poolboy checkout returns `{error, timeout}` when pool exhausted Goal: determine the intended semantics of poolboy’s checkout timeout in the context of an exhausted pool, and how to handle this in production code. Constraints: poolboy 1.5+ no longer emits a distinct `{error, exhausted}`; instead checkout blocks until the supplied timeout expires and then retu
The primary goal is to keep the memory footprint of a low‑traffic Erlang node minimal so that hosting costs can be reduced. Erlang’s lightweight processes normally require roughly 1.5 KB of heap, but the default runtime allocator (erts_alloc) can over‑allocate for short‑lived processes, inflating the resident set size on nodes that handle only a handful of c
Designing a portable Erlang/OTP TLS client that validates server certificates without relying on the host OS trust store raises a documented trade-off between two ssl options. The ssl module supports certificate validation via the verify option. A static PEM bundle can be supplied with cacertfile for portability across deployments. The certstore option enabl
An Erlang application works as a single development node but fails to form a distributed cluster in production. The distribution handshake depends on a cookie value configured with -setcookie or erlang:set_cookie, and all production nodes appear to use the same string. The unresolved behavior is whether runtime version differences, OS security policies, or n
Erlang Module Export vs. Private Functions: Avoiding Accidental Public Access Goal: Keep helper predicates hidden while still enabling quick prototyping with the -export_all compiler flag. Constraints Erlang has no explicit private attribute; non‑exported functions rely on convention. The -export_all option overrides any explicit export list, making accident
gleam