lyft / lyft/fake_sqs

Support for DelaySeconds?

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Ruby
Stars
16
Forks
5
PR merge metrics
No merged PRs in 30d

Description

I cannot find if fake_sqs strictly supports (or not) DelaySeconds?

https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-delay-queues.html

We are seeing messages consumed immediately when a DelaySeconds is provided.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing fake_sqs's message-delay handling with the AWS SQS DelaySeconds documentation linked in the issue. Reproduce the case where a message with DelaySeconds is consumed immediately, then trace the relevant message creation and consumption entry points. Done means delayed messages are not available for consumption until their delay expires.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, ruby
Domain
backend, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.