Infinite recursion while DLTK index project with symlink

[spam38]

I just discovered a minor issue with DLTK indexing when a project contains a symbolic that refers to a parent directory (ie: siteroot/foo/bar points to siteroot/) that causes infinite recursion. Because of the symlink, the indexer will scan siteroot/*, then siteroot/foo/bar/*, then siteroot/foo/bar/foo/bar/*, etc. Removing the symbolic link will prevent this, but it probably shouldn't happen in the first place. (The find command and grep -r will work just fine in these conditions)

[spam38]

oh, and this is with Zend Studio 7.2.1 on Mac OS X 10.6.4

[iconic2020]

bump ....

any fix or tips for this issue?

[kentatzend]

We have entered a bug for it but ... Just out of curiosity why do you do this?

[iconic2020]

I'm not sure of spam38's need, but I have the same problem due to some complexities related to and apache config & subdomain workaround -- using a symbolic link to the current folder solved the apache problem but has blown up Zend Studio

[kentatzend]

got it ....

[raymondjplante]

I've also notice if you have symbolic links in your directory tree and you try searching it throws an error and the search dies.

[crazymerlin]

This sounds like bad practice. Why would you have a symlink in your project? Can you not just exclude it from the build?
I take it this is a project you already had in place before using ZSt?

This certainly doesn't sound like a bug, more like a feature request.

[raymondjplante]

Yes, pre exisiting symbolic links, but regardless they're core to unix file system constructs and especily as the majority of Php sites are on linux systems, one would think studio could handle gracefully symbolic links. In java ( i am assuming the search functionality is java) its trivial to check whether you have a real directory or symbolic link before traversing--crashing the search with a big red exception error is probably bad practice UX when building (or re skinning) an IDE.

[monkeygod82]

This problem still exists in Zend Studio 9.0.3.

Now to find out how to dump the indexes so I can rebuild them.