Community
Participate
Working Groups
Created attachment 83688 [details] log showing exceptions In my dev. env., my CVS decorators have stopped working (where it shows exact revision, "outgoing changes" etc. From the exceptions being written to the log, I think this is related to RSE. I do have RSE installed, have used it some, but at the time of these exceptions, there is no RSE view/perspective open.
Created attachment 83689 [details] configuration of current dev. env.
The stacktrace seems to come from the RSE EFS provider. It looks like in your workspace, there are some remote resources (folders) linked in through the RSE EFS provider. Can you describe your workspace a little? Do you have a project that is shared through CVS with some EFS-hooked remote resources? Could it be that your RSE-shared remote resources are unavailable because the connection is not connected? It's important for us to get to a point at which the problem is sufficiently clear such that we can reproduce it locally.
> Can you describe your workspace a little? only about 10 projects. Which happen to "map" to org.eclipse/www folders, for developing web content. > Do you have a project that is shared through CVS with some EFS-hooked remote resources? Maybe indirectly. Since my RSE "points to" build.eclipse.org, in theory, if you follow the symbolic links, the "root tree" eventually goes to //cvsroot/org.eclipse/www I did have a few filters defined, but not to there. They were to a symbolic link through $HOME/downloads/webtools.... > Could it be that your RSE-shared remote resources are unavailable because the connection is not connected? I think always connected.
Kevin you've been working with EFS a lot, have you ever seen this or can you reproduce it?
I have never seen this and haven't been able to reproduce it, but I don't use EFS and CVS in the same workspace much. I have seen weird errors occur when my ssh connection times out. I've seen the Eclipse Debug Breakpoints view have an error stacktrace as it couldn't retrieve some of the files I had breakpoints in.
SSH timeouts should no longer occur now that we have keepalives.
