Azurestorageexplorer: Garbled message text in 1.14.0

[evictor]

Storage Explorer Version: 1.14.0 -- just after upgrade, so probably newly introduced bug
Build Number: 20200624.3
Platform/OS: macOS Catalina 10.15.5
Architecture: x64
Regression From: Yes, prior release

Bug Description

Message text appears as seen in screenshot in the table, whereas it appears correctly in the "View Message" popup.

In the popup (parts obscured for privacy):

[MRayermannMSFT]

@evictor is there a chance you could share the full message with us? Or maybe a different one which is also affected by this issue?

[evictor]

Sorry, I should have mentioned this is with an Azure queue.

Here is a simple example of adding a message "Test 123" with UTF-8 encoding:

And then the garbled result as it appears in the table:

Note the odd expiration time also with year 9999.

Note also that the message body display is correct in the View Message popup:

[MRayermannMSFT]

@evictor OK, got it, we'll fix it the encoding issue. As for the "weird date", that's what the server returns for expiration date of a queue message that was added with a time to live of "none".

[evictor]

Got it—thank you for the great product

On Wed, Jul 1, 2020 at 11:43 AM Matthew Rayermann [e-mail]
wrote:

@evictor https://github.com/evictor OK, got it, we'll fix it the
encoding issue. As for the "weird date", that's what the server returns for
expiration date of a queue message that was added with a time to live of
"none".

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/AzureStorageExplorer/issues/3154#issuecomment-652585394,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMLRPCVSYCPWG75G7DWIZTRZN7WPANCNFSM4OLPCQQA
.

--

• Zeke

[michaeldrouin]

What's happening is the queue message when you open it shows fine, but in the queue list it's trying to decode UTF-8 to Base-64. you can see this by taking what is in your queue message in UTF-8 format and decoding it _from_ Base-64 (not encoding it _to_ Base-64).

[MRayermannMSFT]

We've checked in a fix for this for our hotfix, 1.14.1.