How can I make a Microsoft Azure setup reproducible?
The same project needs to behave consistently on developer machines, in CI and after deployment. Which versions, dependencies and configuration should be recorded?
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
The same project needs to behave consistently on developer machines, in CI and after deployment. Which versions, dependencies and configuration should be recorded?
Context Portainer Edge Agents maintain a persistent WebSocket connection to the Portainer Server with exponential backoff retries (default 5s, configurable via EDGE_AGENT_RETRY_INTERVAL ). When the Server dispatches a stack deployment and the acknowledgment is lost due to a network partition, the Server re-sends the command on reconnect. Problem The Edge Age
Performance Degradation in Deep Pagination When utilizing setFirstResult() and setMaxResults() in Hibernate ORM, the generated SQL typically relies on LIMIT and OFFSET clauses. While efficient for initial pages, this approach causes linear performance degradation as the offset increases because the database must scan and discard all preceding rows before ret
Extension Interoperability and Product Identification VSCodium distributes a telemetry-free version of the VS Code source, utilizing the Open VSX Registry as the primary extension gallery. This is achieved by modifying the product.json configuration to redirect gallery endpoints away from the Microsoft Marketplace. A technical challenge arises when extension
http.Agent maintains a per-origin pool of keep-alive sockets. maxSockets caps concurrent sockets per origin and maxFreeSockets caps idle sockets retained, which together bound connection reuse under load. The global agent is shared across modules by default, so concurrent requests from different callers compete for the same limits. Keep-alive sockets remain
The goal is to guarantee that a schema change applied via YugabyteDB's online DDL can be safely reverted if the migration has only progressed on a subset of tablets, without risking data loss or inconsistency. Currently, once a background migration starts altering tablets, there is no built‑in mechanism to roll back those tablets to the previous schema; cert
Scalingo utilizes a container-based model where the application state is ephemeral, ensuring that any data written to the local filesystem is lost upon restart or redeployment. This behavior is critical for maintaining statelessness across scaled containers. While the runtime environment is strictly ephemeral, there is a distinction in how the filesystem beh
Goal: achieve identical identifier case‑sensitivity behavior for tables between a typical Windows development server and a Linux production server so that application queries succeed in both environments. Constraint: the lower_case_table_names variable can only be set at server startup; changing it after InnoDB tablespaces have been initialized requires a lo
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?