Local files overwrite updated server-side files without conflict prompts after upgrading Iris from 2025.1.1 to 2025.1.2.

[yunhaibao]

After exporting files to the local system in iris2025.1.1, if the server is upgraded to 2025.1.2 and the files on the server are modified by others, and then I also make modifications locally, no conflict prompt will be given during compilation. Instead, the local files will be directly overwritten onto the server.

The data version I mentioned is just an example. This issue will occur as long as the versions are different.

[isc-bsaviano]

Hi @yunhaibao, this is going to be hard to debug unless you have objectscript.overwriteServerChanges set by mistake. When saving a document on the server, it checks the timestamp sent by the client against the timestamp on the server. If the timestamps match, it allows the save. The client's copy of the timestamp is set whenever the document is exported from the server, or a previous save succeeded. There are no changes between 2025.1.1 and 2025.1.2 that affected this code, and the code in this extension hasn't changed recently.

I think you workflow could be improved though. Client-side editing works best when the IRIS server isn't shared. It relies on the local files being the "source of truth". When the server changes independently, you risk blowing each other's changes away. I recommend you have a dedicated IRIS server for your own development. Then you can turn on objectscript.overwriteServerChanges and the server will always match your local "source of truth".

[isc-bsaviano]

Closing because I don't think this is a bug in the extension. Please re-open if you've collected more evidence.