# timeout Published articles for timeout. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How to operate shared platforms safely at agent scale DevFeed: [How to operate shared platforms safely at agent scale]() Original publisher: [Read original article]() Author: Candace Shamieh; T Zhang; Gabriele Baldoni Published: 2026-09-15T00:00:00Z Content type: article Language: en Sources: [Datadog | The Monitor blog]() Topics: [Platform Engineering](), [Loop Engineering](), [AI Agent](), [sdlc](), [Latency](), [Low Latency](), [Concurrency](), [Software]() Tags: [agent](), [agent-observability](), [agentic-workflows](), [agents](), [ai](), [ai-agent](), [ci](), [concurrency](), [latency](), [low-latency](), [operational](), [performance](), [platform-engineering](), [platforms](), [queue](), [recovery](), [timeout]() ### AI overview This Datadog article explains how platform teams can operate shared platforms safely as AI agent workloads scale across teams. It discusses modeling demand across agent trajectories, planning capacity across dependencies such as CI queues and sandbox pools, handling contention and recovery behavior, and preserving control across system boundaries. ### Source excerpt Learn how Datadog models agent demand, allocates capacity under contention, and preserves control as AI agent workloads scale across shared platforms. ## 【kube-apiserver】Admission 链概览：内置插件顺序与 webhook 边界 DevFeed: [【kube-apiserver】Admission 链概览：内置插件顺序与 webhook 边界]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-28T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [Kubernetes]() Tags: [admission](), [api](), [apiserver](), [authz](), [controllers](), [distributed](), [kubernetes](), [mutating](), [namespace-lifecycle](), [openapi](), [resourcequota](), [timeout](), [v1-30-3](), [validating](), [webhook]() ### AI overview This tutorial explains the Kubernetes v1.30.3 admission chain in kube-apiserver. It places Admission between authorization and storage, describes the Mutating-then-Validating order, and covers built-in plugins, webhooks, timeout behavior, and fail-open versus fail-closed considerations. ### Source excerpt 钉 Kubernetes v1.30.3 Admission 链的阶段位置、Mutating 与 Validating 两阶段顺序、内置插件注册路径与典型示例、webhook 边界与 timeout 语义，以及 fail-open vs fail-closed 的工程争议。 ## 【kube-apiserver】Watch 路径（服务端）：长连接、410 Gone 与 timeout DevFeed: [【kube-apiserver】Watch 路径（服务端）：长连接、410 Gone 与 timeout]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-28T00:00:00Z Content type: article Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [Kubernetes](), [HTTP](), [kubectl]() Tags: [410-gone](), [apiserver](), [bookmark](), [cacher](), [distributed](), [etcd](), [etcd3](), [informer](), [kubernetes](), [resourceversion](), [rest](), [timeout](), [v1-30-3](), [watch]() ### AI overview This article explains the Kubernetes v1.30.3 apiserver Watch path, from the REST handler through cacher and etcd3 watchers. It distinguishes 410 Gone caused by cacher ring-buffer eviction from errors propagated from etcd compaction, and covers resourceVersion semantics, timeouts, bookmarks, connection lifecycle, and the boundary with client-go Informer. ### Source excerpt 钉 Kubernetes v1.30.3 服务端 Watch 路径：从 REST handler 到 cacher/etcd3 watcher 的建立过程、resourceVersion=0 与具体 RV 的语义差异、410 Gone 与 etcd ErrCompacted 的映射、bookmark 推送与连接生命周期，以及与 client-go Informer 的边界。 ## 【kube-apiserver】Mutating / Validating Webhook：timeout、failurePolicy 与可用性门 DevFeed: [【kube-apiserver】Mutating / Validating Webhook：timeout、failurePolicy 与可用性门]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-28T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [Kubernetes](), [configuration](), [dry-run](), [TLS (Transport Layer Security)](), [API]() Tags: [admission](), [api](), [apiserver](), [cel](), [configuration](), [distributed](), [kubernetes](), [kyverno](), [mutating](), [timeout](), [tls](), [v1-30-3](), [validating](), [webhook]() ### AI overview A tutorial on configuring and troubleshooting Kubernetes v1.30.3 mutating and validating admission webhooks. It explains configuration fields, timeout and failurePolicy behavior, production availability requirements, reinvocation and idempotency, CEL ValidatingAdmissionPolicy boundaries, and an evidence-based troubleshooting approach. It emphasizes that slow webhooks add latency to the admission path rather than indicating etcd lag. ### Source excerpt 钉 K8s v1.30.3 的 MutatingWebhookConfiguration / ValidatingWebhookConfiguration v1：timeoutSeconds、failurePolicy、sideEffects、reinvocationPolicy 字段语义；webhook 慢如何表现为写路径延迟而非 etcd lag；生产可用性门选取；CEL ValidatingAdmissionPolicy 作为内置替代路径；排障证据包。 ## 【kube-apiserver】APF 与 max-in-flight：公平排队、504 与 etcd lag 分列 DevFeed: [【kube-apiserver】APF 与 max-in-flight：公平排队、504 与 etcd lag 分列]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-28T00:00:00Z Content type: article Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [Kubernetes](), [API](), [SRE](), [Linux]() Tags: [apf](), [api](), [apiserver](), [distributed](), [etcd](), [fairness](), [fairqueuing](), [flowcontrol](), [k8s](), [kubernetes](), [lag](), [max-in-flight](), [priority](), [timeout](), [v1-30-3]() ### AI overview This article explains how Kubernetes v1.30.3 protects kube-apiserver from overload through API Priority and Fairness (APF) and the older max-in-flight limits. It distinguishes 429 responses, APF queue timeouts that can produce 504 responses before storage is reached, etcd latency, and admission webhook delays, and describes APF's FlowSchema, PriorityLevelConfiguration, fair queuing, and shuffle sharding mechanisms. ### Source excerpt 钉 K8s v1.30.3 的 API Priority and Fairness（APF）：FlowSchema 匹配、PriorityLevelConfiguration 公平排队（SFVR）、与旧 max-in-flight flag 的共存关系；429/timeout/504 在 APF 排队、etcd_request_duration_seconds、Admission Webhook 三轴的分列；pkg/util/flowcontrol 路径；APF 与简单 max-in-flight 的运维复杂度争论。 ## Investigating Redis Client Failures After a Node Loss at hh.ru DevFeed: [Investigating Redis Client Failures After a Node Loss at hh.ru]() Original publisher: [Read original article]() Author: nicholasgribanov (hh.ru) Published: 2026-08-26T05:30:49Z Content type: article Language: ru Sources: [HeadHunter RU]() Topics: [Redis]() Tags: [consul](), [downtime](), [java](), [jedis](), [redis](), [sre](), [tag-1d4e49052118](), [tag-68e701e78517](), [tag-b0a411324cb6](), [tag-b92bf5906bbd](), [tag-dfac9042ce7b](), [timeout]() ### AI overview A Platform team at hh.ru investigates incidents in its internal Redis client, including a 57-minute outage after a Redis node was lost. The team used controlled-load testing, Jedis updates, timeout and pool experiments, new metrics, and logs to trace the failures to a code issue and improve client stability. ### Source excerpt Пару лет назад мы устроили настоящее расследование серии инцидентов в поисках скрытого дефекта нашего Redis-клиента. Команда воспроизводила сбои под контролируемой нагрузкой, проверяла одну гипотезу за другой, обновляла Jedis, экспериментировала с таймаутами и размерами пулов -- но ничего не помогало. А помогли новые метрики и логи, настойчивость команды, ночные эксперименты и готовность разбирать поведение системы до последнего соединения. Получилась история с неожиданными поворотами, ложными следами и одной лишней строчкой кода в роли главного подозреваемого -- а её итогом стал Redis-клиент, который оказался устойчивее, чем был до начала расследования. Меня зовут Коля Грибанов, я тимлид команды "Платформа" в hh.ru. В статье расскажу, почему потеря одной ноды Redis вызывала шторм из десятков тысяч соединений, и как мы шаг за шагом искали причину инцидентов. Читать далее ## ADD COLUMN is not always free, and the lock queue is what takes you down DevFeed: [ADD COLUMN is not always free, and the lock queue is what takes you down]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-08-26T00:00:00Z Content type: article Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [PostgreSQL](), [incident](), [Query (disambiguation)](), [migration](), [MySQL]() Tags: [ddl](), [incident](), [locking](), [migration](), [migrations](), [mysql](), [postgresql](), [query](), [queues](), [schema-design](), [timeout]() ### AI overview Adding a nullable column can cause an outage even when the schema change itself is nearly instantaneous. In PostgreSQL, ALTER TABLE may wait for a long-running query, and subsequent queries can queue behind the waiting lock request. Setting a short lock_timeout and retrying can prevent the migration from taking down the table. ### Source excerpt Modern PostgreSQL adds a column with a default as a metadata change, so the table is never rewritten and the migration itself is instant. The outage comes from lock acquisition instead: ALTER TABLE needs an ACCESS EXCLUSIVE lock, and while it waits behind one long-running query, every subsequent query queues behind the waiting ALTER because the lock queue is ordered. Setting lock_timeout to a couple of seconds and retrying converts that from an outage into a no-op. ## Networking Concepts Every DevOps Engineer Needs to Know DevFeed: [Networking Concepts Every DevOps Engineer Needs to Know]() Original publisher: [Read original article]() Author: Pramodh Kumar M Published: 2026-08-14T17:14:08Z Content type: tutorial Language: en Sources: [Kubernetes - KodeKloud Blog | DevOps, Cloud, Kubernetes, AI Tutorials & More]() Topics: [networking](), [DevOps](), [browser](), [Kubernetes]() Tags: [browser](), [cidr-and-subnets](), [cloud](), [conntrack](), [devops](), [dns](), [ephemeral-ports](), [kubernetes](), [kubernetes-networking](), [linux](), [mtu-mismatch](), [nat-and-snat](), [network](), [network-troubleshooting-commands](), [networking](), [networking-concepts-for-devops](), [osi-model-for-devops](), [platform-engineering](), [proxy](), [routing](), [tcp](), [tcp-handshake](), [timeout](), [tls-handshake](), [vpn]() ### AI overview A tutorial follows a request from a browser to a container to explain networking concepts relevant to DevOps engineers. It maps symptoms such as connection refusal, timeouts, resets, and packet-size-related hangs to network layers and discusses diagnosis across VPN gateways, Kubernetes, and other infrastructure. ### Source excerpt Follow one request from a browser to a container and back. Every networking concept you actually need shows up on that path, in order, and so does every place it breaks. ## Your SQS consumer can hang forever by default DevFeed: [Your SQS consumer can hang forever by default]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-07-28T00:00:00Z Content type: article Language: en Sources: [Encore Updates]() Topics: [Amazon Simple Queue Service (SQS)](), [SDK](), [Rust](), [Amazon Web Services]() Tags: [aws](), [health-check](), [queue](), [retry](), [rust](), [sdk](), [sqs](), [tcp](), [timeout]() ### AI overview The article explains that the AWS Rust SDK has no request timeout by default. A failed or silently dropped connection can leave an SQS receive waiting indefinitely, stopping a sequential consumer loop while the process and health check still appear healthy. It describes fixing the issue with a per-attempt timeout. ### Source excerpt The AWS Rust SDK ships no request timeout by default, so one SQS receive on a dead connection can hang a whole consumer with nothing in the logs. ## Timers, Timeouts, and the Art of Waiting in Temporal DevFeed: [Timers, Timeouts, and the Art of Waiting in Temporal]() Original publisher: [Read original article]() Author: Joshua Smith Published: 2026-06-30T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [SDKs](), [Code](), [Processes]() Tags: [concurrent](), [crashes](), [deployment](), [developers](), [how-to](), [scaling](), [sdks](), [temporal-concepts](), [timeout](), [waiting]() ### AI overview This tutorial explains that Temporal timers provide durable business-logic waiting, while Activity and Workflow timeouts detect failures. It describes how timers survive Worker or process failures and can support large numbers of concurrent waits. ### Source excerpt Timers and timeouts look similar in Temporal but solve different problems. Learn how each one works and how to choose the right tool for durable waiting. ## 3 Resilience Patterns That Keep a Backend Service Up When Its Dependencies Aren't DevFeed: [3 Resilience Patterns That Keep a Backend Service Up When Its Dependencies Aren't]() Original publisher: [Read original article]() Author: The T-Shaped Dev Published: 2026-06-27T10:19:01Z Content type: tutorial Language: en Sources: [The T-Shaped Dev]() Topics: [Resilience](), [Back end](), [API]() Tags: [backend](), [circuit](), [dependencies](), [patterns](), [resilience](), [retry](), [timeout]() ### AI overview A tutorial on using timeouts, retries with backoff, and circuit breakers to limit cascading failures in backend services when dependencies become slow or unreliable. It explains how unbounded waiting can exhaust server resources and describes how to layer these resilience patterns. ### Source excerpt Timeout, retry with backoff, and circuit breaker -- what each one actually does, and the order to stack them. ## Sentry's new AI grouping model reduces duplicate issues and incorrect merges DevFeed: [Sentry's new AI grouping model reduces duplicate issues and incorrect merges]() Original publisher: [Read original article]() Author: Kush Dubey; Yuval Mandelboum Published: 2026-06-12T09:00:00Z Content type: article Language: en Sources: [Sentry Blog]() Topics: [Artificial Intelligence](), [Machine learning](), [Embeddings](), [Algorithm](), [GPU]() Tags: [ai](), [algorithm](), [connection-pool](), [embeddings](), [gpu](), [issue](), [ml](), [model](), [production](), [server](), [timeout]() ### AI overview Sentry describes an upgraded AI model for grouping errors into issues. The model prevents 20% more duplicate issues and halves incorrect merges, separating errors with distinct root causes that the previous model combined. ### Source excerpt Sentry's new AI grouping model prevents 20% more duplicate issues while cutting incorrect merges in half. Here's how we trained and deployed it. ## Bad Retries Can Break Good Systems DevFeed: [Bad Retries Can Break Good Systems]() Original publisher: [Read original article]() Author: Raul Junco Published: 2026-05-09T11:45:53Z Content type: tutorial Language: en Sources: [System Design Classroom]() Topics: [systems](), [Back end](), [distributed-systems](), [incident](), [Latency]() Tags: [backend](), [circuit](), [gateway](), [incident](), [latency](), [retry](), [timeout]() ### AI overview A practical guide to handling transient faults in backend and distributed systems. It explains that uncontrolled retries can increase pressure on slow or overloaded dependencies and recommends backoff, jitter, retry budgets, idempotency, and circuit breakers to reduce user-facing incidents. ### Source excerpt A practical guide to using backoff, jitter, retry budgets, idempotency, and circuit breakers in backend systems. ## Top Resiliency Patterns for Developers DevFeed: [Top Resiliency Patterns for Developers]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-04-21T06:08:56Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [resiliency](), [distributed-systems](), [circuit](), [Availability](), [Latency](), [Scalability](), [Architecture & Design]() Tags: [availability](), [circuit](), [distributed-systems](), [latency](), [monitoring](), [resiliency](), [scalability](), [timeout]() ### AI overview A quick guide to resiliency patterns for distributed systems. It introduces downstream and upstream patterns, then explains timeouts, circuit breakers, and retries with exponential backoff as ways to limit cascading failures and help downstream services recover. ### Source excerpt Quick Guide ## How to Reduce Payment Declines and Recover More Revenue DevFeed: [How to Reduce Payment Declines and Recover More Revenue]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-13T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service](), [Transactions]() Tags: [churn](), [customer](), [fraud](), [how-to](), [implement](), [payments](), [recovery](), [reduce](), [retry](), [revenue](), [saas](), [strategy](), [subscription](), [timeout](), [velocity]() ### AI overview This guide explains how payment declines affect subscription businesses, including their contribution to involuntary churn. It distinguishes soft declines from hard declines and outlines strategies such as smart retry logic to recover recurring revenue. ### Source excerpt Payment declines silently drain SaaS revenue. Learn 12 proven strategies to reduce false declines, retry failed payments, and recover lost recurring revenue. ## Instrumenting AI Agents: Why the Apology Metric Is a First Class Reliability Signal DevFeed: [Instrumenting AI Agents: Why the Apology Metric Is a First Class Reliability Signal]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-03-21T00:00:00Z Content type: article Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [Artificial Intelligence](), [AI Agent](), [reliability](), [agent observability](), [context]() Tags: [ai](), [ai-agents](), [api](), [backend](), [context](), [dependency](), [distributed-systems](), [inference](), [json](), [kv-cache](), [latency](), [llm](), [llmops](), [metric](), [observability](), [orchestration](), [rag](), [reliability](), [reliability-engineering](), [signal](), [timeout]() ### AI overview This article argues that AI agents can return HTTP 200 responses while still failing business tasks. It proposes tracking apology responses as a reliability signal to expose context starvation caused by stalled dependencies, timeouts, stale synchronization, dropped data, or payload truncation in retrieval and orchestration pipelines. ### Source excerpt An AI agent that returns "I apologize, but I cannot find that order" ships an HTTP 200. Infrastructure dashboards call that healthy; the business calls it a failure. Tracking apology phrases as a first-class SLO surfaces context starvation, a stalled dependency, a timeout guard tripping, or silent payload truncation, none of which HTTP status codes and CPU graphs can see. ## Bigger Slugs and Greater Build Timeout Flexibility DevFeed: [Bigger Slugs and Greater Build Timeout Flexibility]() Original publisher: [Read original article]() Author: Jesse Brown Published: 2026-03-19T22:28:36Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [Deployment](), [container]() Tags: [buildpacks](), [deployment](), [developer](), [dynos](), [heroku](), [news](), [platform-updates](), [timeout]() ### AI overview Heroku increased the default maximum compressed app slug size from 500MB to 1GB and raised build compile timeouts. The update supports applications with large dependencies, while larger slugs may increase dyno boot times. ### Source excerpt Modern applications, especially those leveraging AI and data-heavy libraries, need more room to breathe. To support these evolving stacks and reduce developer friction, we've increased the default maximum compressed slug size from 500MB to 1GB. Understanding app slugs and deployment App slugs are the container build artifacts produced by Heroku Buildpacks and run in dynos. [...] The post Bigger Slugs and Greater Build Timeout Flexibility appeared first on Heroku. ## On Metastable Failures and Interactions Between Systems DevFeed: [On Metastable Failures and Interactions Between Systems]() Original publisher: [Read original article]() Author: Aleksey Charapko Published: 2025-12-24T21:26:49Z Content type: opinion Language: en Sources: [Aleksey Charapko]() Topics: [systems](), [retry](), [clients](), [servers](), [Latency]() Tags: [clients](), [fault-tolerance](), [latency](), [load](), [metastabiilty](), [other-thoughts](), [performance](), [retry](), [server](), [signal](), [state](), [systems](), [timeout]() ### AI overview The article explains metastable failures as self-sustaining performance failures caused by positive feedback loops. It uses retry storms to show how overload, latency, timeouts, and client retries can reinforce one another, and examines how ambiguous timeout signals make recovery more difficult. ### Source excerpt I've written about metastable failures before. The topic has been picked up by a few different teams since the, all analyzing metastable failures more, while I apparently has been slacking off... Anyway, Metastable failures are self-sustaining performance failures that arise in systems due to a positive feedback loop triggered by an initial problem. This positive [...] ## How Interrupting Your Users Can Create Accessibility Concerns DevFeed: [How Interrupting Your Users Can Create Accessibility Concerns]() Original publisher: [Read original article]() Author: Chris Published: 2025-12-22T12:30:00Z Content type: article Language: en Sources: [Blog-Main]() Topics: [Web Accessibility (a11y)](), [Web Content Accessibility Guidelines](), [digital accessibility](), [Website](), [Users](), [notifications]() Tags: [accessibility](), [accessibility-guidelines](), [accessibility-ux](), [automatic](), [digital-accessibility](), [display](), [people-with-disabilities](), [send](), [stop](), [time](), [timeout](), [web-accessibility](), [web-content-accessibility-guidelines](), [web-developers](), [websites]() ### AI overview The article explains how dynamic website behavior, including unexpected notifications, automatic refreshes, and other interruptions, can create accessibility barriers for screen reader users and people with attention disorders. It discusses WCAG Success Criterion 2.2.4, which says interruptions can be postponed or suppressed except in emergencies, while noting that this Level AAA criterion is not generally required for conformance goals. ### Source excerpt If you're building a dynamic website, there are plenty of valid reasons to interrupt your users. You might need to tell someone if their session is about to timeout, for example, or you might want your content to refresh periodically in order to show more up-to-date information. ## Kotlin Multiplatform test interceptors with Burst DevFeed: [Kotlin Multiplatform test interceptors with Burst]() Original publisher: [Read original article]() Author: Jesse Wilson Published: 2025-09-04T00:00:00Z Content type: tutorial Language: en Sources: [Cash App Code Blog]() Topics: [Kotlin Multiplatform](), [Testing](), [Kotlin](), [test]() Tags: [http](), [junit](), [kotlin](), [kotlin-android](), [kotlin-multiplatform](), [multiplatform](), [okhttp](), [snapshot](), [test](), [testing](), [tests](), [timeout]() ### AI overview This article introduces Burst 2.8's Kotlin Multiplatform test interceptors, an alternative to JUnit rules for reusing behavior across tests on Kotlin platforms. It also describes interception of suspending tests. ### Source excerpt Interceptors are like JUnit rules, but for every Kotlin platform ## Keycloak 26.2.2 released DevFeed: [Keycloak 26.2.2 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2025-04-30T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Authentication](), [ci](), [migration]() Tags: [bugs](), [changes](), [ci](), [cve](), [fips](), [idm](), [kerberos](), [keycloak](), [keycloak-release](), [ldap](), [migration](), [openid-connect](), [release](), [saml](), [sso](), [tests](), [timeout](), [verification]() ### AI overview Keycloak 26.2.2 was released on April 30, 2025. The release includes a configurable distribution startup timeout, CI FIPS crypto tests, and fixes for a two-factor authentication bypass and hostname verification issues. ### Source excerpt To download the release go to Keycloak downloads. Upgrading Before upgrading refer to the migration guide for a complete list of changes. All resolved issues Enhancements #39142 Make distribution startup timeout configurable testsuite Bugs #39125 [Keycloak CI] - FIPS UT - Run crypto tests ci #39349 CVE-2025-3910 Two factor authentication bypass #39350 CVE-2025-3501 Keycloak hostname verification ## What to do about SQLITE\_BUSY errors despite setting a timeout DevFeed: [What to do about SQLITE\_BUSY errors despite setting a timeout]() Original publisher: [Read original article]() Published: 2025-02-16T20:00:00Z Content type: tutorial Language: en Sources: [Bert Hubert's writings]() Topics: [SQLite](), [Concurrency](), [PostgreSQL]() Tags: [errors](), [postgresql](), [programming](), [rsync](), [sqlite](), [timeout]() ### AI overview This article explains why SQLite can return SQLITE_BUSY despite a configured timeout. It recommends avoiding read-to-write transaction upgrades and using BEGIN IMMEDIATE, or starting the transaction with a write, while describing the concurrency behavior involved. ### Source excerpt So I'm a huge SQLite fanboy and I use it for almost everything these days. Recently, the project added sqlite3_rsync which allows you to swiftly replicate your database to other servers (or to the same server if you want), and this really was the cherry on top for me. Last week however, I ran into one of my projects unexpectedly getting SQLITE_BUSY errors. And then someone urged me to run 'a real database' (PostgreSQL), and that hurt. ## Use Github with SSH on port 443 DevFeed: [Use Github with SSH on port 443]() Original publisher: [Read original article]() Author: Tom Published: 2023-12-26T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [GitHub](), [OpenSSH](), [Firewall]() Tags: [blocking](), [bypass-firewall-github](), [firewall](), [github](), [github-repository-access](), [github-ssh-port-443](), [how-to](), [https](), [linux](), [port](), [repository](), [ssh](), [ssh-configuration-github](), [ssh-github-access](), [timeout](), [wifi]() ### AI overview This tutorial explains how to use GitHub over SSH on port 443 when standard SSH access is blocked or times out, such as on hotel or public Wi-Fi networks. It describes configuring the connection to simulate HTTPS traffic so repositories can still be cloned, pulled, and pushed over SSH. ### Source excerpt Learn how to use GitHub with SSH on port 443 to bypass firewall restrictions and ensure seamless repository access. ## Working with the new Idempotency Keys RFC DevFeed: [Working with the new Idempotency Keys RFC]() Original publisher: [Read original article]() Author: HTTP Toolkit; Phil Sturgeon Published: 2023-12-12T15:00:00Z Content type: tutorial Language: en Sources: [HTTP Toolkit]() Topics: [HTTP](), [Internet Engineering Task Force (IETF)](), [client](), [Server](), [stripe]() Tags: [apis](), [http](), [ietf](), [payment](), [request](), [server](), [standards](), [stripe](), [timeout]() ### AI overview This article explains how idempotency keys make retries safe for HTTP API operations, especially POST and PATCH requests that modify server state. It discusses an IETF draft RFC and the risks of duplicate actions such as payments when clients time out. ### Source excerpt Idempotency is when doing an operation multiple times is guaranteed to have the same effect as doing it just once. When working with APIs this is exceptionally helpful on slow or unreliable internet connections, or when dealing with particularly sensitive actions such as payments, because it makes retrying operations safe and reliable. This is why most payment gateways like Stripe and Adyen support 'idempotency keys' as a key feature of their APIs. Recently, the IETF have gone further, and created a draft RFC standard for this useful common pattern, as part of the 'Building Blocks for HTTP APIs' working group. This is technically still a draft and the details could change, but it's fairly mature now and increasingly widely used, so it's a good time to take a closer look, and start using & implementing it for yourself. Idempotency in HTTP APIs Many HTTP methods are defined as idempotent in all cases. In theory, any GET, HEAD, PUT, DELETE, OPTIONS, or TRACE operation can be executed multiple times without any unintended side effects (though for badly behaved APIs your mileage may vary). The idea is that an HTTP request like DELETE /users/123 clearly wants to delete that user, and if that accidentally happens twice then that's just fine. User 123 ends up deleted just the same. It's a lot more complicated for POST and PATCH requests, which do not provide that same level of confidence out of the box. These are designed to allow non-idempotent operations, like adding a new user, sending a payment, or appending to existing data. Those are important use cases too - sometimes you really do want to send the same thing twice, and have it happen twice - but this can cause problems when things go wrong. When sending POST and PATCH requests to modify server state, if you want to support retries then both the client and server need to explicitly handle this - which is exactly what idempotency keys are designed to allow you to do. How can non-idempotency go wrong? Without idempoten [Next page]()