SOS 5.0.1 Get again

[Jared Sullivan]

Get on folder (recursive) doesn't flag files as READ-ONLY. However everything works if a GET is performed on file list.

NOTE to repo bug you have to GET from 2 folders up of your file list. i.e. A Get Latest on the folder "project" recursvly [\project\source\*.* ] will fail to flag all files in \source as read-only.

Natarually files didn't exist when task was performed.

Can this be fixed in 5.0.2?

Thanks
Jared Sullivan

[jclausius]

Jared,

Just to clarify... The files exist on disk in these sub folders as they were retrieved with a "GET" by SOS, but the read-only file attribute was turned off at some point. So when the secondary GET is performed, although no files were retrieved, the read-only flag attribute remains unset?

Is that correct?

[Jared Sullivan]

Jeff...The files don't exist on disk, when a GET is done through SOS on a folder for files in sub folder(2 deep), the files are created by SOS *without* READ ONLY flag.

Bug synopsis = "GET on GrandParent folder where local copies of files in child folder are not present leads to creation of files with no read only flag set"

Thanks
Jared Sullivan

[jclausius]

Jared, I'll have someone dig into this. Thanks for the report.

[jclausius]

Jared,

I could not repro this problem with a pre-release 5.0.2 client. The only thing I did see in my testing was if a GET was performed on missing files, and they were checked out, the files *did not* have the RO flag set. However, if the GET was performed on missing files, and they were NOT checked out, the RO attribute was set.

The key is if the files were checked out or not checked out.

[jclausius]

Jared,

QA went back and tried the problem with SOS 5.0.1 Build 242, and it DOES exist there. So this problem has been addressed in the soon to be released 5.0.2 client.

[jclausius]

Jared,

The read-only issue for missing files has been addressed in SOS 5.0.2. Look for the maintenance release to be out today (March 31, 2010).