cloud: Deploy a dead-letter topic for submission queues
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
The Google Cloud Pub/Sub system supports assigning a "dead-letter" topic to a subscription, which receives all messages that failed delivery despite trying it for some time. This could be useful for collecting messages which failed delivery for one reason or another, and helping the CI systems as well as KCIDB developers debug submission issues.
At the moment we drop any messages which fail JSON schema validation, perhaps we should be putting them into such "dead-letter" topic ourselves as well, immediately, instead of NACK'ing them and letting Pub/Sub retry them uselessly.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the submission-queue Pub/Sub handling and the JSON schema validation path; determine how a dead-letter topic would be configured and used, with completion defined by failed validation messages being collected for debugging instead of retried uselessly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, python
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100