Requeue Message on deleted message does nothing, used to requeue

[abatishchev]

Storage Explorer Version: 1.14.0
Build Number: 20200624.3
Platform/OS: Windows 10 x64
Architecture: ia32
Regression From: Yes, it was working in 1.13.0

Bug Description

Clicking Requeue Message on a queue message that was already consumed and deleted from the queue does nothing. In previous version it used to requeue its "cached" (currently displayed) version from the memory.

Steps to Reproduce

1. Enqueue a message
2. Refresh to see it in the list
3. Consume the message programmatically
4. Do not refresh! Otherwise it'll be gone
5. Press right click ->Requeue Message

Expected Experience

The message is requeued to the queue

Actual Experience

Nothing happens. Pressing Refresh clears up the list.

Additional Context

Worked as expected in the previous version.

[CurtMiller66]

I have seen the same issue. Frustrating regression. I really got used to it working.

[MRayermannMSFT]

Thanks for reporting this. We'll look into fixing this for our hotfix of 1.14

[MRayermannMSFT]

@CurtMiller66 I talked with Alex separately. Turns out he was working against the storage emulator. Are you working with the emulator as well?

[CurtMiller66]

Requeue issue is against the emulator. I use it for development/testing. Curt From: Matthew Rayermann <notifications@github.com> Sent: Monday, July 6, 2020 1:50 PM To: microsoft/AzureStorageExplorer <AzureStorageExplorer@noreply.github.com> Cc: Curt Miller <CMiller@Airnote.Com>; Mention <mention@noreply.github.com> Subject: Re: [microsoft/AzureStorageExplorer] Requeue Message on deleted message does nothing, used to requeue (#3173) @CurtMiller66<https://github.com/CurtMiller66> I talked with Alex separately. Turns out he was working against the storage emulator. Are you working with the emulator as well? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#3173 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACXTEWADKDMX32P4NNYTI7LR2I2H3ANCNFSM4OOCPKTA>.

[MRayermannMSFT]

@CurtMiller66, ah ok. That's a known issue for version 1.14.0. The .NET emulator has issues when we try to requeue a messafe if the message's time to live is greater than 7 days, and in 1.14.0, we changed the default time to live for new messages to be infinite (none/no time to live).

So for now you can either:

• when adding new messages, change time to live to not be infinite (none/no time to live)
• switch to using Azurite
• downgrade to Storage Explorer 1.13.x

And then in 1.14.1, which should be going out next week, we will be reverting to having the default time to live be 7 days. That way if you're using the .NET emulator, we don't put in you in a position where it'll be easy to run into issues.

Let me know if you have any questions.

[MRayermannMSFT]

Fix was merged into the hotfix branch.