FileProperties from list_directories_and_files with timestamps differs from get_file_properties on files

[DisplayL]

• Package Name: azure-storage-file-share
• Package Version: 12.21.0
• Operating System: Ubuntu 20.04.4 LTS
• Python Version: 3.8.10

Describe the bug
list_directories_and_files including timestamps for a given file renders different data from getting the respective file client get_file_properties

To Reproduce

1. list_directories_and_files for a file
2. get_file_properties on that file
3. for example, change_time has tzinfo utc in listing but not on get_file_properties

Expected behavior
Expected the same FileProperties object

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @jalauzon-msft @vincenttran-msft.

[github-actions]

Hi @DisplayL, I'm an AI Support assistant here to help with your issue. While the Azure SDK team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

• The differences in the FileProperties returned by list operations versus get operations can be attributed to the SDK’s current deserialization behavior for those responses. One method returns timestamps with UTC tzinfo while the other does not.
• Similar differences in model property behaviors have been observed in other areas of the SDK. For example, changes related to newly added or updated properties (e.g. “version” or “service_endpoint”) have been documented in the Data Factory changelogs (link) and the Confidential Ledger samples (link). Although those issues are in different client libraries, they highlight how property parsing differences can emerge in new or updated versions.
• If you need a consistent time format, consider applying an explicit conversion to the output of get_file_properties to add UTC tzinfo so that it matches the result from list_directories_and_files.
• These observations can help determine whether the difference is expected behavior or if further investigation is needed within the SDK’s current implementation.

The Azure SDK team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!