nielash

It is also reproducible on the `TestChunkerMailru:` integration tests: https://pub.rclone.org/integration-tests/2024-04-15-010011/chunker-backend.chunker-TestChunkerMailru-5.txt https://pub.rclone.org/integration-tests/2024-04-15-010011/chunker-cmd.bisync-TestChunkerMailru-5.txt

> 1. Do we need to invent our own time format when we can just link to [the Go docs](https://pkg.go.dev/time#pkg-constants)? I did something just like this recently (actually twice!) Maybe...

I think your solution is fine, but just to clarify one thing: > Since we will be using this time in the name of the file, where `/` and `:`...

I too would love to see this, as it is probably the most reliable protocol on macOS. I think that the library rclone uses for the `smb` backend is only...

Hmm, where are you seeing that? According to [this source](https://github.com/macos-fuse-t/fuse-t/releases/tag/1.0.35), [go-smb2](https://github.com/macos-fuse-t/go-smb2) is just the smb server library used in [fuse-t](https://github.com/macos-fuse-t/fuse-t).

Right, but that is [fuse-t](https://github.com/macos-fuse-t/fuse-t). I am talking about [go-smb2](https://github.com/macos-fuse-t/go-smb2), a different repo from the same author. (Rclone already supports fuse-t in `rclone mount`.)

Yep, looking at it now.

Ok I think I figured it out. Branch with fixes: https://github.com/nielash/rclone/commits/fix-int-tests/ Three different issues, involving different remotes. (Btw, all 3 tests are new ones I added -- not regressions.) ###...

> I don't think the Feature flag is useful except in the tests, so I'd probably go with 1. What do you think? I agree. I also have one other...

> We could potentially do the same here, without needing the backend to self-report its features Here's an example of how this could be done here: https://github.com/nielash/rclone/commit/da487ba695d85af4751f799702f9b8e4fcf50bdc