Dead letter queue

[bboynton97]

closes ENG-565

Failed requests are retried.
After 3 failures, they are stored in-memory with a queue.
When a request succeeds, the queue attempts to retry.

[bboynton97]

Add persistent storage and show users logs when a request fails

[codecov]

Codecov Report

Attention: Patch coverage is 73.68421% with 20 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
agentops/http_client.py	77.61%	12 Missing and 3 partials ⚠️
agentops/helpers.py	44.44%	3 Missing and 2 partials ⚠️

Flag	Coverage Δ
unittests	46.16% <73.68%> (+1.76%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
agentops/helpers.py	64.00% <44.44%> (-1.94%)	⬇️
agentops/http_client.py	71.51% <77.61%> (+27.71%)	⬆️

[bboynton97]

ready for review again @siyangqiu

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
13866639	Triggered	Generic High Entropy Secret	1a7cba1	tests/core_manual_tests/http_client/dead_letter_queue.py	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}