files to be downloaded with filename with unsupported characters should show error early?

[moscicki]

There appears to be a regression in 2.2.4 and 2.3.1 #5076

Could you please confirm?

[guruz]

@moscicki Current version is 2.3.3rc1 :-) Re-try that first..

[yolanda93]

We have tried with the current version (2.3.3rc1) and the problem remains

[michaelstingl]

@moscicki @yolanda93 Could you send the exact "steps to reproduce" to better cover it in qa?

[SamuAlfageme]

@michaelstingl no need, I could reproduce by simply including a colon on any filename via webUI and forcing/waiting for sync.

@ogoffart @guruz wonder if the new encoding/decoding logic (#5875) could have some impact here. Probably that is making the error to go unnoticed.

UPDATE: 2.3.2 is also affected. Some bisect support here? cc/ @ckamm as he did some error-refactorings there that could trigger this.

[guruz]

I'm creating a file called : on the web interface with oC 9.1.6.2 and sync down in Windows 10.x with 2.3.3rc2

I can then clearly see it in Not Synced tab as File names containing the character ':' are not supported on this file system.

@moscicki @yolanda93 Can you give me more detailed reproduction steps?
Are you sure you waited for the next sync to happen and then checked the Not Synced tab?
It would be good to run the client with log file and paste a link to log file here.

Now the big question is of course how was @SamuAlfageme able to reproduce!?
Is it because you all have different oC versions?
But I thought for downloading those checks are client side..

[SamuAlfageme]

@guruz

But I thought for downloading those checks are client side..

Indeed; you're right, I'm seeing the entries appear on "Not Synced" after a few seconds, I think the other day I assumed not seeing the file-count in the tab meant there was nothing there (I'm used to it on 2.4 by now):

2.3.X	2.4.0

@moscicki @yolanda93 do you guys have any more insights on how to reproduce it?

[guruz]

@moscicki @yolanda93 ping ^^

[yolanda93]

The same as @guruz, sorry. Now, I double checked waiting a few seconds and it appears in Not Synced tab.

[guruz]

@yolanda93 great!

@ogoffart @mrow4a Just a thought we could have those kind of error jobs (generated by a sync job, not in discovery) be ordered very early so that they are visible earlier in the UI?
I don't know how this is influenced by renames/moves

[mrow4a]

Hmm, I think we can do that, any priority for that?

[ogoffart]

Recent version reads the invalidFilenameRegex from the capabilities.