bug: Missing file size and access times for services-fs lister

[matthambrecht]

Describe the bug

Currently if you use the fs service's lister and attempt to view the metadata it only returns type defaults so sizes are always 0 and access times are always undefined.

Steps to Reproduce

use opendal::{self, Operator};
use futures_util::TryStreamExt;

#[tokio::main]
async fn main() {
    let operator = Operator::from_uri("fs:///tmp/test_dir").unwrap();
    let lister = operator.lister("/").await.unwrap();
    let entries = lister.try_collect::<Vec<_>>().await.unwrap(); 

   for entry in entries {
        let metadata = entry.metadata();
        println!("Metadata: {:#?}", metadata)
    }
}

Expected Behavior

Should serve the file's size and time of last access.

Additional Context

No response

Are you willing to submit a PR to fix this bug?

• Yes, I would like to submit a PR.

[dosubot]

Hi @matthambrecht! I'm Dosu and I’m helping the opendal team.

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. 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.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}