Azure / Azure/Azurite

Queues do not correctly handle visibility timeout

Open
#2,343 1 comment 0 reactions 1 assignee Claimed by @blueww View on GitHub
featureparity queue-storage
Dominant language
TypeScript
Stars
2.3k
Forks
393
Avg merge
1d 20h
Merged PRs (30d)
36

Description

### Which service(blob, file, queue, table) does this issue concern?

queue

### Which version of the Azurite was used?

3.29

### Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)

npm

### What's the Node.js version?

16.20

### What problem was encountered?

visibility_timeout is ignored, ie, if a message was leased from the queue for longer than visibility timeout, it does not reappear, and can still be updated by the client.

I confirmed with the team, that this feature is currently lacking.

Note that validation of visibility timeout had some issues [in the past](https://github.com/Azure/Azurite/issues/2083) which were [fixed](https://github.com/Azure/Azurite/pull/2087), but it seems that the functionality is not implemented.

### Steps to reproduce the issue?

### Have you found a mitigation/solution?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.