ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #erlang
An Erlang service using Mnesia must schedule a backup with minimal node downtime. The team needs to decide whether to take an offline snapshot using mnesia:backup/2 with the force option or an online snapshot using mnesia:backup/2 with safe_fallback , then restore it with mnesia:restore/2 and confirm the recovered tables match the pre-backup state. Assuming
Accidental public API exposure due to export_all In Erlang modules, the -export/1 clause defines the public API. Using -export_all can inadvertently expose internal helper functions, especially when combined with OTP behaviours that rely on exported callbacks. This can lead to unintended remote calls or misuse. The community has documented that omitting func
Timeout semantics of process.call I'm designing a Gleam service on the BEAM target that makes blocking requests to worker processes using process.call from gleam/erlang/process with a timeout in milliseconds. My understanding from the module documentation is that when the timeout elapses, the caller gets a timeout outcome instead of blocking forever — but th
Build Profile Configuration Gleam 1.0+ utilizes dev and prod build profiles within the gleam.toml configuration. The dev profile is designed to preserve debug information and disable specific optimizations to facilitate local development and debugging. Production Optimization Constraints When switching to the prod profile, the compiler enables BEAM optimizat
The goal is to guarantee that a name registered via global:register_name/2 can be reused immediately after the owning node fails. In a local single‑node environment the registry is recreated on restart, hiding the issue. In a production cluster the global registry is replicated across nodes, and the OTP documentation states that stale entries are eventually
Goal Build a Docker‑based CI pipeline that can run an Erlang release on multiple OTP releases (23 and 24) while keeping module resolution deterministic. Constraints & Uncertainty OTP 24 introduced the overlay mechanism, allowing partial patching without a full system restart. However, the code:which/1 resolution order changed between OTP 23 and 24 when e
OTP Logger per‑module filtering Since OTP 21, Logger supports custom filter modules that can be attached per handler. The handler’s filter is set to the module’s return value for each log message, allowing fine‑grained suppression of noise. Dynamic update concern When a filter module is edited and recompiled, the usual approach is to call logger:reload_handl
Precision Goal The goal is to understand how Erlang systems should recover from a failed hot code upgrade when some processes remain indefinitely on the old module version. Erlang's hot code loading mechanism keeps both old and new versions active, with processes transitioning only upon fully qualified function calls. This creates a recovery challenge when p
Integration Boundary: Gleam Language and Erlang OTP Gleam provides a native, typed actor framework via the gleam/otp library, which abstracts BEAM concurrency. Simultaneously, the language allows direct interoperability with Erlang's gen_server and other OTP behaviors through the @external attribute. While the gleam/otp implementation offers compile-time saf
gleam