dosubot[bot] commented on issue #7187:
URL: https://github.com/apache/opendal/issues/7187#issuecomment-3881912271

   <!-- Greeting -->
   Hi @matthambrecht! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping 
the opendal team.
   
   <!-- Answer -->
   The recent PR for the fs service lister now ensures that file size 
(content-length) is always included in the metadata for listed entries, so you 
should see correct sizes without extra stat calls going forward 
[details](https://github.com/apache/opendal/pull/7072). However, based on the 
available information, it's not clear if access times (like last modification 
time) are also included in the lister metadata. If you still see undefined 
access times, you may need to extend the lister to fetch and populate these 
fields from the filesystem metadata (using, for example, the modified time from 
std::fs::Metadata or tokio::fs::Metadata) when building each entry. If you want 
to submit a PR, focus on ensuring that the lister extracts and sets the last 
modification time in the Metadata for each entry, similar to how content-length 
is now handled.
   
   
   <!-- Dosu Comment Footer -->
   *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
   
   ---
   <sup>How did I do? 
[Good](https://app.dosu.dev/response-feedback/3671eb83-b8f5-4634-b19b-a1d46a5395dc?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/3671eb83-b8f5-4634-b19b-a1d46a5395dc?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/3671eb83-b8f5-4634-b19b-a1d46a5395dc?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/3671eb83-b8f5-4634-b19b-a1d46a5395dc?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/3671eb83-b8f5-4634-b19b-a1d46a5395dc?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/3671eb83-b8f5-4634-b19b-a1d46a5395dc?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/3671eb83-b8f5-4634-b19b-a1d46a5395dc?feedback_type=other)</sup>
   
   [![Chat with 
Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/997a2c5a-0c54-497b-989d-44651635dd36/ask?utm_source=github)&nbsp;[![Open
 in 
Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=The%20recent%20PR%20for%20the%20fs%20service%20lister%20now%20ensures%20that%20file%20size%20%28content-length%29%20is%20always%20included%20in%20the%20metadata%20for%20listed%20entries%2C%20so%20you%20should%20see%20correct%20sizes%20without%20extra%20stat%20calls%20going%20forward%C2%A0%5Bdetails%5D%28https%3A//github.com/apache/opendal/pull/7072%29.%20However%2C%20based%20on%20the%20available%20information%2C%20it%27s%20not%20clear%20if%20access%20times%20%28like%20last%20modification%20time%29%20are%20also%20included%20in%20the%20lister%20metadata.%20If%20you%20still%20see%20undefined%20access%20times%2C%20you%20may%20need%20to%20extend%20the%20lister%20to%20fetch%20and%20populate%20these%20fields%20from%20the%20filesystem%20metadata%20%28using
 
%2C%20for%20example%2C%20the%20modified%20time%20from%20std%3A%3Afs%3A%3AMetadata%20or%20tokio%3A%3Afs%3A%3AMetadata%29%20when%20building%20each%20entry.%20If%20you%20want%20to%20submit%20a%20PR%2C%20focus%20on%20ensuring%20that%20the%20lister%20extracts%20and%20sets%20the%20last%20modification%20time%20in%20the%20Metadata%20for%20each%20entry%2C%20similar%20to%20how%20content-length%20is%20now%20handled.)&nbsp;[![Join
 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share
 on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/opendal/issues/7187)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to