Pulling still skipping even with `--force`

[Hans5958]

It seems that the client still skipping pulling newer files, even though the --force or -f was given. I'm not sure if this also happens when pushing, Any ideas?

This is tested on v1.6.4, both on Windows and Linux (GitHub Actions).

$ tx pull --all --force
# Getting info about resources

project.resource1 - Done
project.resource2 - Done
...
project.resource27 - Done
project.resource28 - Done
[##############################] (28 / 28)

# Pulling files

project.resource1 [ab] - Local file is newer than remote, skipping
project.resource1 [af] - Local file is newer than remote, skipping
project.resource1 [am] - Local file is newer than remote, skipping
project.resource1 [ar] - Doneting download job
project.resource1 [az] - Local file is newer than remote, skipping
project.resource1 [be] - Local file is newer than remote, skipping
project.resource1 [bg] - Local file is newer than remote, skipping
project.resource1 [ca] - Doneting download job
project.resource1 [ckb] - Local file is newer than remote, skipping
project.resource1 [cs] - Local file is newer than remote, skipping
project.resource1 [cy] - Local file is newer than remote, skipping
project.resource1 [da] - Local file is newer than remote, skipping
project.resource1 [de] - Doneting download job
project.resource1 [el] - Local file is newer than remote, skipping
project.resource1 [es] - Doneting download job
project.resource1 [et] - Local file is newer than remote, skipping
project.resource1 [eu] - Local file is newer than remote, skipping
project.resource1 [fa] - Local file is newer than remote, skipping
project.resource1 [fi] - Doneting download job
project.resource1 [fr] - Doneting download job
...

[zerocrates]

Do you have a minimum_perc set? It seems that skips with the same message about "Local file is newer than remote" even though it's actually the percentage causing the file to be skipped.

[Hans5958]

I do infact have minimum_perc set on 1%. If that's the case, the log should be changed.

[codegaze]

@Hans5958 thanks for bringing this up, and @zerocrates for the clarification, you are spot on. 🙏
This is caused indeed due to wrong message logic. We will tackle it in a future release.

[codegaze]

@Hans5958 The latest version v1.6.5 has a fix for the message.

I will close this one, but feel free to open it again if something still seems off. :)