Central_Bug_Checklist[1]

UNC - Bug Checklist DESCRIPTION Notes Code Test 1 Empty folders are not replicated. 2 Check count does not go up for Real-Time events. 3 Progress bar appears to be stuck at the end of an event. FIXED FIXED FIXED 23-May 23-May 23-May 23-May 4 Empty preserved paths created in the Revisions folder for each file/folder add, update, delete and file rename. This ACCEPTED FUNCTIONALITY may result in a folder structure in the Revisions folder that no longer exists on the source. Revisions will be scattered amongst different folder versions. 6 The Deletions folder stores deletions with their preserved paths (Ex: Deleting Test.txt located in C:\ …\Source\1\2\3 will be stored in the Deletions folder as: C:\…\Deletions\1\2\3\Test.txt). This occous in TCP Pull, UNC, FTP (both Push and Pull) but not for TCP Push. (in TCP Push is stored as C:\....\Deletions\Test.txt). 7 Non ASCII file updates using the Byte-Replicator corrupt the Target file. 8 ON A PULL - Non ASCII file updates using the Byte-Replicator corrupt the Target file. 9 Getting "PSListener failed to respond to connection on …" messages on updates with ByteReplicator on. Works fine in TCP mode. 10 11 12 13 14 15 16 17 18 19 FIXED 26-May TCP - Bug Checklist DESCRIPTION Notes Code Test 1 Files smaller then 500 KB but larger then 0 KB cause the Listener to throw "PSListener failed to accept data …" messages. 2 Empty folders are not sinked. 3 Check count does not go up for Real-Time events. 4 3rd level file deletions are stored in the deletions folder within their folder and with trunkated name - varies between last 3, 7, and 6 characters. 6 Deletions folder stores files in their preserved paths. 7 When Revisioning is off - empty folders are created in the Revisions folder on folder renames, moves, and file deletes. 8 For file deletes - empty preserved path is created on the local Deletions folder. 9 File rename and moves are treated as adds. ?????????? Therefore no revisions are created. (This may be the accepted behavior for TCP) 10 Does not retry if the Target is open when the source is updated. 11 Empty Folders created in the Revisions folder for each added, updated, renamed, or delete of a file/folder. 12 Non ASCII file updates using the Byte-Replicator corrupt the Target file. FIXED FIXED FIXED FIXED FIXED FIXED FIXED FIXED FIXED ACCEPTED FUNCTIONALITY FIXED 22-May 22-May 22-May 22-May 22-May 22-May 22-May 23-May 23-May 23-May 26-May 23-May 24-May 24-May 24-May FIXED 13 Folder renames treated as ADD and DELETE 14 Deleting Files and Folders located in a folder depth of 4 or deeper - deletions will be stored in a preserved path (with FIXED trunkated folder name) in the Deletions folder. 15 Deleting Files and Folders that are located in a folder depth of 4 or deeper will cause empty preserved paths to be created in the LOCAL Deletions folder. 16 ON A PULL - Files smaller then 500 KB but larger then 0 KB cause the Listener to throw "PSListener failed to accept data …" messages. Zero size .brtmp files are left on the target. 17 ON A PULL - Non ASCII file updates using the Byte-Replicator corrupt the Target file. 18 19 FIXED FIXED FTP - Bug Checklist DESCRIPTION Notes Code Test 1 If you drop in any folder (with or without content) PS will not add it to the target. A subsequest scan will do it. 2 A newly created folder (aka: New Folder) does not get added to the target in real-time. 3 File updates/renames treated as adds. Running a scan fixes the issue. 4 Deletions - throw messages "Could not delete folder…". Files remain on target and not copied into the deletions folder. 6 Empty folders (with preserved paths) are created in the revisioning folder when adding/deleting/updating files/folders. 7 Allows for Additional Target Path Selections - uses only path specified in the target field - additional target paths (UNC or FTP) are validated for connection but are ignored for all events. 8 Exclusions - if Target is composite1b Excluding any subfolder results in no files and folders to be checked and added even during a scan. Target iomnas Works well. 9 On an update, if the Target file is open, PS leaves a .PSTMP file on the target and does not retry or give any messages. 10 If file retries are exceeded a scan will not run if "Run a scan on reconnect" is selected. (same issue with UNC target) 11 Folder rename and moves will result in having an empty preserved path to the renamed or moved folder on the target.(Deletions are on but the Move option is not enabled) 12 File deletes cause empty preserved path folders to be created in the Revisions folder. (Deletions are enabled but Move and revisioning are disabled). 13 If the Target file is open and cannot be updated, PS creates a revision in the Revisions folder for every retry until it can sucessfully update the target. This is not the case in UNC and TCP modes. 14 The Deletions folder stores deletions with their preserved paths (Ex: Deleting Test.txt located in C:\ …\Source\1\2\3 will be stored in the Deletions folder as: C:\…\Deletions\1\2\3\Test.txt). This occous in TCP Pull and FTP (both Push and Pull) but not for TCP Push. (in TCP Push is stored as C:\....\Deletions\Test.txt). FIXED FIXED FIXED FIXED ACCEPTED FUNCTIONALITY ADDRESSED IN NEW INTERFACE FIXED FIXED ACCEPTED FUNCTIONALITY FIXED FIXED FIXED 23-May 23-May 23-May 23-May 23-May 23-May 23-May 23-May 23-May 23-May 25-May 15 File and Folder Deletes throw "Could not delete file : …" messages when the Move option is not enabled for deletions. FIXED 16 0 Size Revisions created for updated files and 0 Size Revisions created for every new file that is added. Deletions are corectly stored in the Revisions folder if the Move option is not enabled ( but 11KB Word files [empty] are stores as 0KB Back files) 17 Each subsequent scan updates the Target files on a LINUX machine even if they are significantly newer then the source. If the Target is a Windows machine each scan will update the Target files only if the modified date time stamp on the target is less then or equal to that of the source (on a Push - target files with the same time stamp as the source will be updated) 18 During Scans [NO Real-Time] - Folder deletions are incomplete - empty folders/subfolders are left on the target if the source folder has more then one subfolder when it is deleted. 19 During Scans [NO Real-Time] - Folder deletions are not logged. Instead logs the deletion of the first file in the folder only. 20 Deletions folder does not store all files and subfolders of a deleted folder. Appears to store out up to the first file it finds. 21 Getting "Could not delete file: … " messages for folder deletions in Real-Time mode. 22 PS runs very sluggishly and uses all CPU at times. Occurs with both Windows and Linux targets. (MTM 05-30-06) 23 When using "Delete unmatched target files older than x days" option - PeerSync throws a "Could not write target file … (the process cannot access the file because it is being used by another process)" message before the file is sucessfully deleted. 24 Revisoning does not work - (when specifying revisions to go into the target folder - files will end up in the deletions folder instead) - see Deletions & Revisions Tab for detailed description of revisions issues. 25 Pull a file from FTP...currently date/time are not applied after transfer....When applying date/time if the now time is in the same minute apply one minute less to the target so the file will be checked again to revalidate an update within the same minute. (this is not working when using temp files and/or Revisioning) 26 Exclude files to an FTP source/target will exclude folders with that string but it is not logged and the excluded count is not incremented 27 Pulling from a Unix FTP - will have GMTModified date time stamp on the target files (+4 hours) 28 DUPLICATED (MTM) 25-May 30-May Global Issues - Bug Checklist DESCRIPTION Notes Code Test 1 2 3 4 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 FTP Testing PUSH Real-Time Windows UNIX Windows Scan UNIX Windows PULL Profiler - Bug Checklist DESCRIPTION Notes Code Test 1 Not all of the Options dialogs are the same (ie. Current Command-Line Arguments dialog has the PeerSync icon). This is probably caused by the fact that that particular dialog is resizable. (MTM 05-30-06) 2 "Places" background color (left part of the Open and Save dialog boxes) is not consistent with the rest of the form. (MTM 05-30-06) 3 When an invalid entry is entered into the source or the target field, should Profiler wait to display a warning until after the text field loses focus? (MTM 05-30-06) FIXED (MAS 06-01-06) ACCEPTED FUNCTIONALITY FIXED (MAS 06-12-06) 4 When opening a profile with a job that utilizes TCP, the TCP information is correctly stored out but the mode is not FIXED (MAS 05-31-06) changed to TCP. (MTM 05-30-06) 5 The length of the "General Settings" frame on the "TCP Configuration" tab is not the same as the length of the "Listener Configuration" frame on the "Listener Configuration" tab. (MTM 05-30-06) 6 When typing "TCP:\\" into the path when FTP is selected and you go to change to Normal mode, "TCP" becomes the path. 7 Status bar skin needs to be updated after an option shown in the status bar (such as to reload the current profile) is clicked on. 8 View Menu > Folders > Show Selected dosen't relocate the source folder 9 FIXED (MAS 05-31-06) FIXED (MAS 06-12-06) Deletions & Revisions Testing - Bug Checklist DESCRIPTION Category Importance Notes Test 1 When running as a service (all default options), PeerSync tries to open Profiler under the System account. This happens several times before the open Profiler connects to the service. 2 <<$SrcList.txt$>> variables for source and target are not working. They are being successfully loaded in as jobs but are never given a job name and are never scanned. 3 If PeerLock is terminated abruptly PeerSync checks for and deletes the lock files but the file needs to be updated twice. 4 When renaming to an excluded file or folder, PeerSync ignores the rename. 5 When Relaunching a Profile through Profiler (option shows up at the bottom of the form after saving a profile that is running), PeerSync's excluded file count is not cleared out. (Profiler issue and not PeerSync???) 6 When PeerSync is running, ":" and "\" in the current job name goes back and forth between "_" and the true character. 7 When excluding a .zip file while using file compression, PeerSync will say its adding files to the target everytime a scan is run regardless of whether or not the source was changed. The same thing happens when a file and its corresponding zip file both exist in the source directory. 8 Still seeing "none" in the File name field in PeerSync when a profile is first starting up 9 If deletion folder does not exist, deletions are moved to a path in the install folder. Now they are just deleted, not moved. 10 On a local job, revisioning to an alternate folder clears out the target folder after the initial sync. 11 12 13 14 PeerSync > Services PeerSync > General PeerSync > General PeerSync > Exceptions PeerSync > General PeerSync > General High High Fixed & Validated Fixed & Validated Still not Fixed Desired Functionality Fixed & Validated PeerSync > Compression PeerSync > General PeerSync > Deletions PeerSync > Revisions High Fixed & Validated Validated