Mikhail f. Shiryaev

Hello. Sorry for such a disappearance. But I've finally reproduced the issue https://github.com/Felixoid/geesefs-reprepro I have s3-debug logs with three following lines, but not sure how safe it is to share...

It feels to me, like the FS reports success before the big files are uploaded. Could `--fsync-on-close` save us in this case?

[Added](https://github.com/Felixoid/geesefs-reprepro/commit/70af2695592fa65151c559c99c677c2898cfa996) `--fsync-on-close` didn't help with conflicting ETag ``` 2024/08/28 11:04:59.724218 s3.WARNING Conflict detected (inode 296): server-side ETag or size of reproduce/deb/dists/stable/Release ("6089c83c9868d9ae622987eac4d365a2", 1584) differs from local ("e960a07962379de04df349011a1a6070", 1584). File is...

It is worth saying the next. To reproduce the issue, I've launched the [run.sh](https://github.com/Felixoid/geesefs-reprepro/blob/70af2695592fa65151c559c99c677c2898cfa996/run.sh) many times. So, it's very inconsistent. I am waiting for the feedback regarding the S3 debug...

Thanks a lot, it's fixed by a given commit. To see if the issue is addressed, I've built a special binary from https://github.com/yandex-cloud/geesefs/tree/v0.41.2: ```diff diff --git a/internal/handles.go b/internal/handles.go index 62748a3..72867b3...

The issue with sccache server will probably be addressed in https://github.com/ClickHouse/ClickHouse/pull/83600

Dear @AXGKl, I've bisected repo, and the commit implementing this behavior is cd4839d3d1374670cf78390d27784171a5acf122 

Both reports are pending because of the crashed server, @Algunenano is right.

> I am not able to replicate this It's valid only for a maximized window on a HIDPI screen 3840x2160. With 0.5 and even 0.8-sized windows it's much better. I...

> OS Arch Linux > gpu card `04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Lucienne (rev c1)` > screen resolution, scaling 3840x2160, 125% > X11/Wayland Wayland, ~will check...