ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
When a transient database failure occurs after NHibernate has flushed an insert but before the transaction commits, the session is left in an inconsistent state and must be discarded. Reopening a session and retrying the same unit of work risks inserting a duplicate row if the original insert actually persisted. This risk depends heavily on the identifier ge
Context AngularJS $http provides no built-in retry mechanism, so applications that retry failed POST, PUT, or PATCH requests must implement custom logic. Because these methods are not inherently idempotent, a client-side timeout or 5xx response does not guarantee the server aborted the original write. A subsequent retry can therefore create duplicate records
Goal We need to load‑test an API that performs non‑idempotent POSTs while still allowing transient failure retries. Constraint Retries must not cause duplicate side‑effects; the API only guarantees idempotence when an idempotency key header is present. Unresolved Decision Should we rely on Gatling’s retry DSL combined with manual idempotency‑key handling, or
In a Jamstack build, write operations are typically delegated to serverless functions or third-party APIs rather than the static host itself. When a browser times out waiting for a response, the endpoint may have already committed the write, so a naive retry can duplicate the effect unless the receiving service enforces idempotency. Idempotency keys are a do
When integrating external automation with the Bitbucket Server/Data Center REST API, network timeouts during POST requests create uncertainty regarding whether a resource was successfully created on the server before the connection dropped. Because standard write endpoints for entities like pull requests or repositories do not natively support idempotency ke
Context FoundationDB's optimistic concurrency control returns retryable errors ( transaction_too_old , not_committed ) when read-write conflicts occur. The on_error callback automatically re-executes the entire transaction function, which re-applies any writes unless the application implements idempotency at the key level. Constraint Current patterns require
gleam.http.Client retry configuration The goal is to configure automatic retries for HTTP requests without risking duplicate side‑effects when the request method is not idempotent (e.g., POST, PUT with non‑idempotent payload). Currently the Retry type attached to a gleam.http.Client request only inspects HTTP status codes and network errors; it does not eval
Context Terraform providers implement retry logic for throttling errors such as AWS Throttling or GCP rateLimitExceeded using the Plugin SDK's resource.Retry helpers. When a CREATE or UPDATE call succeeds on the remote side but the HTTP response is lost due to timeout or network partition, the provider may re-issue the same request. Problem If the target res
Goal Determine whether a Crystal application can retry a side-effecting operation without creating duplicate writes using only the standard library and language concurrency features. Constraints and uncertainty Crystal 1.x does not include a built-in atomic retry, circuit breaker, or distributed transaction coordinator. The Cells actor model isolates state w
jamstack
bitbucket
terraform
crystal
nhibernate