Desktop: Desktop 3.0.0 - Conflict details not shown

[khorton]

Expected behaviour

If there are conflicts, show the conflict details when the user clicks on "Click for details"

Actual behaviour

Client shows yellow exclamation point. Unresolved conflicts text is shown. User clicks on "Click for details", but nothing happens. There is no obvious way to see a list of conflicts.

Steps to reproduce

1. Create conflict
2. Sync
3. Conflict state is shown
4. Click on "Click for details"

Client configuration

Client version: Mac 3.0.0

Operating system: macOS 10.15.6

OS language: English

Qt version used by client package (Linux only, see also Settings dialog):

Client package (From Nextcloud or distro) (Linux only):

Installation path of client: /Applications/nextcloud.app

Server configuration

Nextcloud version: 18.0.7

Storage backend (external storage):

Logs

Please use Gist (https://gist.github.com/) or a similar code paster for longer
logs.

1. Client logfile: Output of nextcloud --logwindow or nextcloud --logfile log.txt
   (On Windows using cmd.exe, you might need to first cd into the Nextcloud directory)
   (See also https://docs.nextcloud.com/desktop/2.3/troubleshooting.html#log-files)
   No log is shown if F12 is pressed

2. Web server error log:

3. Server logfile: nextcloud log (data/nextcloud.log):

[toshichi]

Same on Windows 10

[despens]

Same on Linux — there is sometimes a mismatch in between the 3.0 client's display of activities and what happens when you click on them. For instance, items with the :information_source: (info icon) can contain a description that's too long to fully read, even no file name visible, clicking on it seems to open some random folder on the local disk.

[artfulrobot]

Ah yeah, this is a nightmare, can't see which file has the conflicts at all!

If I squint at the new window I can see a filename with a ! but I need a filepath - I have a lot of files!

And clicking on the file just brings up a web link to /files which is no use to anyone.

Is there anywhere we can get this from? Is there a text log file or something?

[er-vin]

You could use the logwindow for this for instance. We're working on a fix for 3.0.2 though regarding the new window.

[artfulrobot]

@er-vin thanks I couldn't find that in v3's maze like UI! I've gone to 2.6.5, clicked it and it took me right to the file. Bingo!

[RufioHugo]

Same problem here - approx 1/3 of all data with conflict! Ver. 3.0.1 (just updated)
btw: Not a single file had a conflict the second before the update - I've ran a sync for scurity reasons beforehand!

& jftr: Trying to solve the conflict by hand ended up in deleted files ... on both sides (and problems undelting them from tray ;-

[er-vin]

Same problem here - approx 1/3 of all data with conflict! Ver. 3.0.1 (just updated)
btw: Not a single file had a conflict the second before the update - I've ran a sync for scurity reasons beforehand!

& jftr: Trying to solve the conflict by hand ended up in deleted files ... on both sides (and problems undelting them from tray ;-

This is a different issue altogether though. There are other tickets regarding invalid conflicts, here this is about showing the details of the conflicts and how to get them solved. Please move conversation regarding invalid conflicts in the relevant tickets.

[er-vin]

Closing this one, this should be addressed with #2396.

[memen45]

Same problem here - approx 1/3 of all data with conflict! Ver. 3.0.1 (just updated)
btw: Not a single file had a conflict the second before the update - I've ran a sync for scurity reasons beforehand!
& jftr: Trying to solve the conflict by hand ended up in deleted files ... on both sides (and problems undelting them from tray ;-

This is a different issue altogether though. There are other tickets regarding invalid conflicts, here this is about showing the details of the conflicts and how to get them solved. Please move conversation regarding invalid conflicts in the relevant tickets.

I cannot find the other tickets you mention. I have the same problems as above with version 3.0.1:

• conflict created, while actually there should be no conflicts as it was fully synced before updating from 2.6.x
• conflict details not visible

So the question is, how do I undo or solve all these (unknown) conflicts? It seems like the client has overwritten a lot of local files with the (older) remote versions, without asking and without offering a way to solve it, or even see which files are affected. Also: why is this version 3.0.1 pushed to users and not marked as beta if it contains this kind of critical bugs?

[er-vin]

So the question is, how do I undo or solve all these (unknown) conflicts? It seems like the client has overwritten a lot of local files with the (older) remote versions, without asking and without offering a way to solve it, or even see which files are affected.

Right now this is indeed a problem, one way to do it is to fire up with logs and look at those. Another way is to temporarily downgrade. In any case 3.0.2 will come with the tooltip patch allowing to read the client message in full.

Also: why is this version 3.0.1 pushed to users and not marked as beta if it contains this kind of critical bugs?

Because we had weeks of dailies, beta and rc containing that code. That QA was done. And none of those safety nets reported that before.

Besides most of the "unwanted conflicts" situations predate the 3.0 codebase, you could have them on 2.6. Actually, I've been looking at one today which it turns out wasn't the client fault but server induced in some specific setups. Flexibility comes with complexity.