ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Harbor Scanner Cache Refresh on Updated Vulnerability Database When the underlying vulnerability scanner (e.g., Trivy) updates its CVE database, Harbor may continue to serve scan results from its internal cache, leading to stale or incomplete vulnerability information. The goal is to understand how to trigger a cache refresh or override the cached data so th
When integrating with Trello’s REST API, developers rely on the documented rate‑limit headers (X‑RateLimit‑Limit, X‑RateLimit‑Remaining) to throttle calls and avoid HTTP 429 errors. However, many endpoints omit these headers, and intermittent 429 responses have been observed even when the reported remaining quota appears sufficient. This suggests that Trello
The goal is to confirm whether a password change for a local Portainer user, performed through the API endpoint /api/users/{id}/password, becomes effective for subsequent authentication requests without restarting the Portainer container, or whether the change only takes effect after a container restart. Current observations show that the UI appears to apply
When an Okta upgrade is in progress, API calls to upgrade‑related endpoints can fail with a 503 Service Unavailable response. The failure typically occurs when the upgrade package is large or the service is temporarily overloaded. The 503 response includes a Retry‑After header, but Okta’s API does not automatically retry the request. Clients must implement e
Goal Guarantee that a PATCH request applied via an idempotency key is performed only once, even when the client retries or sends concurrent identical requests. Constraints & Uncertainty PATCH is a partial update; the server may apply the patch multiple times if not guarded. Some APIs store the full request body and response for idempotency, others do not
Goal Retrieve a large collection of Pods from a k3s cluster and paginate the results by issuing successive GET requests with a limit and continue query parameter. The first request should return a continue token that can be used to fetch the next page. Constraints & Uncertainty When the dataset grows quickly, the resourceVersion embedded in the first pag
We need to migrate a small application’s test artifacts from an existing qTest instance to a new deployment while keeping the system online. The goal is to preserve continuity for both test execution and defect tracking in Jira. The primary constraint is the lack of a single‑transaction migration path. qTest’s REST API supports incremental pulls via the modi
When bounding a query and paginating a large dataset in Shopware 6, the goal is to control the number of results returned per page to avoid performance issues. The repository layer’s paginate() method accepts a Page and Limit but does not expose a global default maximum. Developers must enforce limits manually. The Admin API applies a hard‑coded 1000‑item ca
When using ngrok’s inspection API to page through request logs, clients typically combine a fixed limit with an increasing offset to retrieve successive batches. Ngrok automatically removes older inspection entries after a configurable retention period, which can change the total number of stored requests while a pagination walk is in progress. This raises u
harbor
trello
okta
k3s
kubernetes
qtest
jira
doctrine
ngrok