Skip to content
← General

I suggest you ...

General

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Bug: Revision type change is stored on server but not updated on clients

User A changes revision type of an item from binary to text. User B runs update and refresh of items list, but item remains binary. Pressing CTRL+D shows a dialog that quotes "Error: Differences between items of diffente types cannot be calculated". That implies that the change of User A was sent to the server and applied to the item, but the information is not propagated to the other users.

1 vote
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Marco shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • AdminCodice Software (CEO / Founder, plasticscm) commented  ·   ·  Report

    Hi Marco,

    Yes, you're right, the revision type information is cached on each workspace.

    It means that the client first looks into the workspace tree, so it won't get the new filetype info until the file is updated with a new revision (or if the file is locally deleted and re-downloaded).

    It is certainly inconvenient in many scenarios.

    We need to make a change on this mechanism. Probably storing the file type is not so useful after all, and we can take advantage of the filetypes.conf mechanism and expand it as the single source of truth through the rest of the system.

    Thanks