SQS send_messages method response different from AWS resource about alpine-sqs HOT 5 OPEN

Hi @babaMar,

Thanks for your interest in this project and submitting an issue.

This project is nothing more than a packaging of Softwaremill's elasticmq server. Unless I'm misunderstanding your issue, I believe this is something that can be better addressed by @adamw.

Cheers,
Ronald

from alpine-sqs.

Hi @roribio,

yeah I realized that, when I run ElasticMQ locally it actually returns the correct response tho, that's why I opened this issue.

from alpine-sqs.

I see 🤔 Could you provide more info to help debug this issue? For example, which version of ElasticMQ are you running locally? Which version of alpine-sqs are you running?

Any details that you can provide will help.

Thanks!

from alpine-sqs.

For both containers I use to pull images, so versions that come with softwaremill/elasticmq and roribio16/alpine-sqs

from alpine-sqs.

This is caused by SQS insights in the container receiving the messages and causing the visibility timeout to begin. Your code is trying to receive messages from the queue which are inflight. I worked around this issue by turning off SQS insights (the web UI).

from alpine-sqs.