Bug 198651 - [ftp][regression] RSE loses selection and expand state when trying to expand a broken symbolic link folder on FTP
Summary: [ftp][regression] RSE loses selection and expand state when trying to expand ...
Status: RESOLVED DUPLICATE of bug 187739
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0.1   Edit
Assignee: Martin Oberhuber CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords:
Depends on: 187739 196662
Blocks:
  Show dependency tree
 
Reported: 2007-08-02 07:24 EDT by Martin Oberhuber CLA
Modified: 2008-09-16 16:49 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2007-08-02 07:24:55 EDT 
When FTP encounters a symbolic link, it cannot know whether the link is a file or directory, or it may be broken. It uses a heuristics to characterize the link as file (if . contained) or folder (if no . contained).

Connect to remote FTP server.
With a shell on that server, create a broken symbolic link, e.g.
   ln -s brokenDoesNotExist brokenLink
Browse down to the parent folder of the broken link, and try to expand the 
broken link.

RSE loses selection and expand state, and queries the parent folder.

Expected behavior: It should instead show an ErrorObject below the broken symlink folder, indicating the error message from the remote.

Supposedly, similar behavior is to be expected when a remote folder can not be expanded due to missing permissions.

This is most probably a regression due to the fix for bug #196662.
Comment 1 David McKnight CLA 2007-09-06 12:24:38 EDT 
Martin, given the implications of bug #196662 and the requirements to improve that solution, I think we may have to defer this to the future.  What are your thoughts?
Comment 2 Martin Oberhuber CLA 2007-09-06 12:45:16 EDT 
Given that this particular issue is specific to FTP (because it cannot categorize broken symbolic links), I think we can decrease priority.

Perhaps Javier can come up with an idea how to handle this properly.
Comment 3 Martin Oberhuber CLA 2007-10-01 07:57:12 EDT 
Bulk update target milestone 2.0.1 -> 3.0
Comment 4 Martin Oberhuber CLA 2008-09-16 16:49:46 EDT 
In 3.0.1, this works as expected (child item reading "Operation failed. File system input or output error"). Most likely due to the fix for bug 187739, or perhaps due to the fix for bug 191275.

*** This bug has been marked as a duplicate of bug 187739 ***