ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
FusionAuth provides tenant-level controls for public API access and API keys with assignable permissions. The goal is to keep administrative endpoints non-public while allowing specific public-facing flows such as registration and password reset to remain available when intended. The current design includes a Disable Public API Access toggle per tenant and A
Dropwizard's DataSourceFactory uses HikariCP by default, and the documented behavior when the pool is exhausted is that callers wait up to connectionTimeout before a SQLTransientConnectionException is thrown. With connectionTimeout set to zero, waiting threads block indefinitely, which risks starving the Jetty worker pool under sustained load. The unresolved
WebSocket connection behavior in collection runs Hoppscotch supports executing multiple WebSocket requests as part of a collection run. Each request can target the same endpoint, yet the documentation does not clarify whether the client reuses an existing WebSocket connection or opens a new one for each request in the sequence. Browser developer tools show a
Browser Control Surface Exposure When initializing a browser instance via puppeteer.launch , the library allows the configuration of Chromium launch arguments. A critical security consideration involves the remote debugging port, which provides an unauthenticated interface for browser control. While Puppeteer manages the browser process, the binding of this
When deploying CouchDB 3.x, the httpd/bind_address setting defaults to 127.0.0.1, which permits local tools such as Futon/_utils to function but blocks external client connections. The goal is to decide on a production‑ready binding strategy that allows remote access while maintaining security and compatibility with existing upgrade paths. Operators must wei
Hyper-V relies on underlying Windows domain credentials for severalion access, live migration, and remote management. When a user's domain password expires, the behavior of existing and new connection sessions appears inconsistent depending on the authentication protocol utilized during the initial handshake. If a Kerberos ticket is already cached, it may re
Goal We want to maintain Alertmanager silence definitions across k3os upgrades so that noise‑reducing alerts remain effective after a new release is applied. Constraints The silences live in the k3s-alertmanager ConfigMap in kube-system , which is regenerated during an upgrade. There is no built‑in persistence for these custom rules, and the default Alertman
When utilizing FireDAC's multi-threaded architecture to fetch data in the background, the goal is to maintain a responsive interface. However, pushing high-frequency updates from a background TFDQuery thread to the main UI thread via TThread.Synchronize often results in message queue saturation. In high-concurrency scenarios, the overhead of frequent synchro
Nim's integer overflow handling in release builds relies on wrapping arithmetic by default, which maps directly to machine-word operations and avoids runtime checks for performance. The --check:overflow flag and compiler configuration can enable overflow checks, but their interaction with user-defined integer subtypes, optimization pragmas, and external C li
dropwizard
hoppscotch
puppeteer
couchdb
delphi
nim