Synchronize view - individual files not showing?

Another team member committed some changes to our
repository.  In 
Synchronize view, for one of the changesets, I see the
folders 
containing files he changed, but not the actual files
themselves.  They 
appear in one of the bottom-right panes, but of course there
there's no 
context menu or ability to use Quick Diff.

Could this be related to committing a folder vs. committing
individual 
files, or the use of svn commit --recursive?  Would they
appear 
differently to Subclipse?

Jay

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribesubclipse.tigris.org
For additional commands, e-mail: users-helpsubclipse.tigris.org

On 9/4/07, Jay Levitt <lists-subclipseshopwatch.org> wrote:
> Another team member committed some changes to our
repository.  In
> Synchronize view, for one of the changesets, I see the
folders
> containing files he changed, but not the actual files
themselves.  They
> appear in one of the bottom-right panes, but of course
there there's no
> context menu or ability to use Quick Diff.
>
> Could this be related to committing a folder vs.
committing individual
> files, or the use of svn commit --recursive?  Would
they appear
> differently to Subclipse?

The change set view will only show an item once.  I'd expect
the files
to show up under their most recent change.

There is no distinction made about a type of commit.

BTW, everyone can arrange Eclipse to look however they want,
so screen
locations do not mean anything to anyone.  You would need to
give view
names.

-- 
Thanks

Mark Phippard
http://markphip.blogspo
t.com/

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribesubclipse.tigris.org
For additional commands, e-mail: users-helpsubclipse.tigris.org

Mark Phippard wrote:
> On 9/4/07, Jay Levitt <lists-subclipseshopwatch.org> wrote:
>> Another team member committed some changes to our
repository.  In
>> Synchronize view, for one of the changesets, I see
the folders
>> containing files he changed, but not the actual
files themselves.  They
>> appear in one of the bottom-right panes, but of
course there there's no
>> context menu or ability to use Quick Diff.
>>
>> Could this be related to committing a folder vs.
committing individual
>> files, or the use of svn commit --recursive?  Would
they appear
>> differently to Subclipse?
> 
> The change set view will only show an item once.  I'd
expect the files
> to show up under their most recent change.

Hmm, OK, I'll see if that's what's happening.

> There is no distinction made about a type of commit.

Good to know.

> BTW, everyone can arrange Eclipse to look however they
want, so screen
> locations do not mean anything to anyone.  You would
need to give view
> names.

Yeah, you caught me weasel-wording my way out of the fact
that I killed 
my fail case by updating, so I could no longer tell you
where I saw the 
filenames appearing... turns out they were in the
bottom-left pane of 
the History view.

Jay

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribesubclipse.tigris.org
For additional commands, e-mail: users-helpsubclipse.tigris.org

Mark Phippard wrote:
> On 9/4/07, Jay Levitt <lists-subclipseshopwatch.org> wrote:
>> Another team member committed some changes to our
repository.  In
>> Synchronize view, for one of the changesets, I see
the folders
>> containing files he changed, but not the actual
files themselves.  They
>> appear in one of the bottom-right panes, but of
course there there's no
>> context menu or ability to use Quick Diff.
> 
> The change set view will only show an item once.  I'd
expect the files
> to show up under their most recent change.

OK, I just saw this happen again.  I had checked in a change
to 
spec/models/user_spec.rb, did a synchronize, and saw my own
changeset as 
incoming (naturally).  However, instead of showing a
compressed folder 
of "spec/models" with a filename of
"user_spec.rb", Synchronize shows me 
two compressed folders - one "spec", the other
"spec/models", both 
apparently empty.  Checking the history of spec/models does
correctly 
show the user_spec.rb file in the bottom half of the history
pane.

Mark, I'll send you a screen shot off-list so as not to
pollute the list 
w/binaries.

Jay

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribesubclipse.tigris.org
For additional commands, e-mail: users-helpsubclipse.tigris.org

On 9/7/07, Jay Levitt <lists-subclipseshopwatch.org> wrote:
> Mark Phippard wrote:
> > On 9/4/07, Jay Levitt <lists-subclipseshopwatch.org> wrote:
> >> Another team member committed some changes to
our repository.  In
> >> Synchronize view, for one of the changesets, I
see the folders
> >> containing files he changed, but not the
actual files themselves.  They
> >> appear in one of the bottom-right panes, but
of course there there's no
> >> context menu or ability to use Quick Diff.
> >
> > The change set view will only show an item once. 
I'd expect the files
> > to show up under their most recent change.
>
> OK, I just saw this happen again.  I had checked in a
change to
> spec/models/user_spec.rb, did a synchronize, and saw my
own changeset as
> incoming (naturally).  However, instead of showing a
compressed folder
> of "spec/models" with a filename of
"user_spec.rb", Synchronize shows me
> two compressed folders - one "spec", the
other "spec/models", both
> apparently empty.  Checking the history of spec/models
does correctly
> show the user_spec.rb file in the bottom half of the
history pane.
>
> Mark, I'll send you a screen shot off-list so as not to
pollute the list
> w/binaries.

That is a feature.  It is described here:

http://markphip.blogspot.com/200
6/12/subclipse-synchronize-feature-show-out.html

There is a preference that controls it which you can turn
off.  In our
next major release we are going to make it off by default as
most
people do not need it in the first place, and most people
also do not
understand it.

-- 
Thanks

Mark Phippard
http://markphip.blogspo
t.com/

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribesubclipse.tigris.org
For additional commands, e-mail: users-helpsubclipse.tigris.org

Mark Phippard wrote:
> On 9/7/07, Jay Levitt <lists-subclipseshopwatch.org> wrote:
>> Mark Phippard wrote:
>>> On 9/4/07, Jay Levitt <lists-subclipseshopwatch.org> wrote:
>>>> Another team member committed some changes
to our repository.  In
>>>> Synchronize view, for one of the
changesets, I see the folders
>>>> containing files he changed, but not the
actual files themselves.  They
>>>> appear in one of the bottom-right panes,
but of course there there's no
>>>> context menu or ability to use Quick Diff.
>>> The change set view will only show an item
once.  I'd expect the files
>>> to show up under their most recent change.
>> OK, I just saw this happen again.  I had checked in
a change to
>> spec/models/user_spec.rb, did a synchronize, and
saw my own changeset as
>> incoming (naturally).  However, instead of showing
a compressed folder
>> of "spec/models" with a filename of
"user_spec.rb", Synchronize shows me
>> two compressed folders - one "spec", the
other "spec/models", both
>> apparently empty.  Checking the history of
spec/models does correctly
>> show the user_spec.rb file in the bottom half of
the history pane.
>>
>> Mark, I'll send you a screen shot off-list so as
not to pollute the list
>> w/binaries.
> 
> That is a feature.  It is described here:
> 
> http://markphip.blogspot.com/200
6/12/subclipse-synchronize-feature-show-out.html

I do understand "show outdated folders", and I can
see how this might be 
related - but it's (at least slightly) a separate issue,
because this 
occurs whether I have that enabled or disabled.

However:

1. With "show outdated folders" enabled, I'd
expect Presentation: 
Compressed Folders to compress spec and spec/models into
just 
spec/models.  Minor nit.  But more importantly:

2. With "show updated folders" disabled, I
shouldn't see anything at 
all!  But I still see those two incoming folders.

And more importantly yet:

3. I see this happening in places where I am NOT the
committer, so these 
are not merely out-of-date folders - they're true changesets
that aren't 
being shown.

F'rinstance:

In my WC, the top-level "mediajoint" folder is at
revision 6062, as are 
the app/ and app/controllers/ folders.  login_controller.rb
is at 6060 
and not locally modified.

Changeset 6068 in the repository modifies 
app/controllers/login_controller.rb.  But in the Synchronize
view, with 
changesets enabled, incoming only, I see

+ mediajoint
   <= app/controllers

There is no twisty on app/controllers, and no indications of
what files 
have changed.  If I right-click on app/controllers and
"show history", I 
can see login_controller.rb in the bottom left portion of
the history pane.

Screen shot again sent under separate cover - with
preferences open to 
prove I'm not seeing things 

Again, I'm happy to just file this as a bug, but I suspect
that you 
wouldn't be able to fix it unless I gather more information
to help you 
reproduce it.  I just don't know what that information is. 
This doesn't 
happen 100% of the time, and I haven't seen any patterns
that would 
guide me toward creating a failcase.  But if there's debug
logging or 
anything else that would help, I'm happy to do that.

Jay

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribesubclipse.tigris.org
For additional commands, e-mail: users-helpsubclipse.tigris.org

On 9/7/07, Jay Levitt <lists-subclipseshopwatch.org> wrote:
> > That is a feature.  It is described here:
> >
> > http://markphip.blogspot.com/200
6/12/subclipse-synchronize-feature-show-out.html
>
> I do understand "show outdated folders", and
I can see how this might be
> related - but it's (at least slightly) a separate
issue, because this
> occurs whether I have that enabled or disabled.

I am still convinced it is only because of this feature. 
One thing
about this feature is that it does not toggle on/off very
easily.  The
issue is that the feature effects the information that gets
into our
cache, and once info is in the cache it will stick there. 
In your
case, if you turned the feature off, and then updated
everything it
would likely stay off.

> However:
>
> 1. With "show outdated folders" enabled, I'd
expect Presentation:
> Compressed Folders to compress spec and spec/models
into just
> spec/models.  Minor nit.  But more importantly:

The presentation modes come from the Synch view itself. 
They are each
folders, so they will each be their own node.  They do not
compress
because the Show Out of Date Folders features has told
Eclipse that
each of those is an Incoming change (the blue arrow).


> 2. With "show updated folders" disabled, I
shouldn't see anything at
> all!  But I still see those two incoming folders.

That is because of what I mentioned above.  The feature does
not shut
off immediately.

> And more importantly yet:
>
> 3. I see this happening in places where I am NOT the
committer, so these
> are not merely out-of-date folders - they're true
changesets that aren't
> being shown.
>
> F'rinstance:
>
> In my WC, the top-level "mediajoint" folder
is at revision 6062, as are
> the app/ and app/controllers/ folders. 
login_controller.rb is at 6060
> and not locally modified.
>
> Changeset 6068 in the repository modifies
> app/controllers/login_controller.rb.  But in the
Synchronize view, with
> changesets enabled, incoming only, I see
>
> + mediajoint
>    <= app/controllers
>
> There is no twisty on app/controllers, and no
indications of what files
> have changed.  If I right-click on app/controllers and
"show history", I
> can see login_controller.rb in the bottom left portion
of the history pane.
>
> Screen shot again sent under separate cover - with
preferences open to
> prove I'm not seeing things 
>
> Again, I'm happy to just file this as a bug, but I
suspect that you
> wouldn't be able to fix it unless I gather more
information to help you
> reproduce it.  I just don't know what that information
is.  This doesn't
> happen 100% of the time, and I haven't seen any
patterns that would
> guide me toward creating a failcase.  But if there's
debug logging or
> anything else that would help, I'm happy to do that.

I'd just suggest operating for a while with this feature
turned off.

-- 
Thanks

Mark Phippard
http://markphip.blogspo
t.com/

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribesubclipse.tigris.org
For additional commands, e-mail: users-helpsubclipse.tigris.org

Mark Phippard wrote:
> On 9/7/07, Jay Levitt <lists-subclipseshopwatch.org> wrote:
>>> That is a feature.  It is described here:
>>>
>>> http://markphip.blogspot.com/200
6/12/subclipse-synchronize-feature-show-out.html
>> I do understand "show outdated folders",
and I can see how this might be
>> related - but it's (at least slightly) a separate
issue, because this
>> occurs whether I have that enabled or disabled.
> 
> I am still convinced it is only because of this
feature.  One thing
> about this feature is that it does not toggle on/off
very easily.  The
> issue is that the feature effects the information that
gets into our
> cache, and once info is in the cache it will stick
there.  In your
> case, if you turned the feature off, and then updated
everything it
> would likely stay off.

I don't mean to be difficult, but I don't see how cached
out-of-date 
folders could result in the changed files being -missing-
from the 
changeset.  I could see how otherwise-unchanged folders
would still show 
up, but under those folders (or maybe under an
identical-looking but 
genuine folder node) I'd expect to see the changed files
that really do 
need updating.  That's the bug I'm concerned about.

Is there a way for me to blow away the cache?  If not, could
you point 
me toward some interesting points in Subclipse I could step
through to 
debug?  I have some time this weekend.

Jay

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribesubclipse.tigris.org
For additional commands, e-mail: users-helpsubclipse.tigris.org

On 9/7/07, Jay Levitt <lists-subclipseshopwatch.org> wrote:
> Mark Phippard wrote:
> > On 9/7/07, Jay Levitt <lists-subclipseshopwatch.org> wrote:
> >>> That is a feature.  It is described here:
> >>>
> >>> http://markphip.blogspot.com/200
6/12/subclipse-synchronize-feature-show-out.html
> >> I do understand "show outdated
folders", and I can see how this might be
> >> related - but it's (at least slightly) a
separate issue, because this
> >> occurs whether I have that enabled or
disabled.
> >
> > I am still convinced it is only because of this
feature.  One thing
> > about this feature is that it does not toggle
on/off very easily.  The
> > issue is that the feature effects the information
that gets into our
> > cache, and once info is in the cache it will stick
there.  In your
> > case, if you turned the feature off, and then
updated everything it
> > would likely stay off.
>
> I don't mean to be difficult, but I don't see how
cached out-of-date
> folders could result in the changed files being
-missing- from the
> changeset.  I could see how otherwise-unchanged folders
would still show
> up, but under those folders (or maybe under an
identical-looking but
> genuine folder node) I'd expect to see the changed
files that really do
> need updating.  That's the bug I'm concerned about.
>
> Is there a way for me to blow away the cache?  If not,
could you point
> me toward some interesting points in Subclipse I could
step through to
> debug?  I have some time this weekend.

I'd love to have you or anyone try to make Subclipse
better.
Unfortunately, the Synch view is probably not the place to
start.  One
of the reasons I am talking around this issue is that even
if you file
a bug, I am not going to look at it.  I can never make heads
or tails
of how that view works because the Eclipse API is just so
complicated
and involves so much cache.  We have had some other
committers that
come back for short periods that seem to grok this better
and have
made most of the improvements over the years.

I am going based on my own observations using the view and
what I see
in similar situations.  I have not had situations where
files go
missing, other than the known problem where toggling the
view mode
seems to resolve it.

As for the cache issue, I was more answering the other
points you had
made which I think are explained by the cache.  The missing
files I do
not have an explanation for.  I just have not experienced
that myself.

-- 
Thanks

Mark Phippard
http://markphip.blogspo
t.com/

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribesubclipse.tigris.org
For additional commands, e-mail: users-helpsubclipse.tigris.org

Mark Phippard wrote:
> I'd love to have you or anyone try to make Subclipse
better.
> Unfortunately, the Synch view is probably not the place
to start.  One
> of the reasons I am talking around this issue is that
even if you file
> a bug, I am not going to look at it.  I can never make
heads or tails
> of how that view works because the Eclipse API is just
so complicated
> and involves so much cache.  We have had some other
committers that
> come back for short periods that seem to grok this
better and have
> made most of the improvements over the years.

Wow, OK - I had no idea it was that bad.  Of course, you
realize that 
this forces me to rise to the challenge and try to debug it
this 
weekend, despite not knowing Java, let alone Eclipse.  If
you do not 
hear any new Subclipse complaints from me by Monday, form a
search party 
and tell my future wife that I love her - whoever she is.

Jay

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribesubclipse.tigris.org
For additional commands, e-mail: users-helpsubclipse.tigris.org

On 9/7/07, Jay Levitt <lists-subclipseshopwatch.org> wrote:
> Mark Phippard wrote:
> > I'd love to have you or anyone try to make
Subclipse better.
> > Unfortunately, the Synch view is probably not the
place to start.  One
> > of the reasons I am talking around this issue is
that even if you file
> > a bug, I am not going to look at it.  I can never
make heads or tails
> > of how that view works because the Eclipse API is
just so complicated
> > and involves so much cache.  We have had some
other committers that
> > come back for short periods that seem to grok this
better and have
> > made most of the improvements over the years.
>
> Wow, OK - I had no idea it was that bad.  Of course,
you realize that
> this forces me to rise to the challenge and try to
debug it this
> weekend, despite not knowing Java, let alone Eclipse. 
If you do not
> hear any new Subclipse complaints from me by Monday,
form a search party
> and tell my future wife that I love her - whoever she
is.

Well, the view is working pretty good in general these days
and I am
able to make small incursions into it to fix certain things
and have.
Something like this would be deep in the dark recesses.

-- 
Thanks

Mark Phippard
http://markphip.blogspo
t.com/

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribesubclipse.tigris.org
For additional commands, e-mail: users-helpsubclipse.tigris.org

Eric Berry wrote:
> Mark,
>    Please correct me if I'm wrong, I'm a basic user of
the products, but 
> doesn't Subversion version the folders as well. So if
you commit your 
> files from the synch view, then go to incoming changes,
you technically 
> should see the folders, because each of their revisions
need to be 
> updated. Whenever I commit my files, I always have to
go to the incoming 
> changes to update the revisions on the folders, and I
don't see the 
> files I just committed.

Right - that is the "show outdated folders"
preference, which is turned 
on by default in 1.2.3, but will be turned off by default in
future 
releases because it causes so much confusion.

You won't see the files you just committed in synch view,
because the 
commit updates the local revision number of that file when
it commits, 
so it's up-to-date with the repository and doesn't need
updating.  (I 
didn't realize it did that, so that confused me in the first
example 
with my own files.)  However, commit can't similarly update
the local 
revision number of the parent folders, since they might
contain other 
changes in the repository that you need to update.

> This might explain the issue where Jay isn't seeing his
own committed 
> files and only seeing the folders, but wouldn't help in
the case where 
> another colleague had made commits.

Right, that second case is really the only mystery.

> Jay, are you perchance doing updates outside of the
synch view?

I may occasionally commit a single file direct from the
RadRails 
perspective, but all my updates are done from Synch view
w/changesets on.

Jay


------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribesubclipse.tigris.org
For additional commands, e-mail: users-helpsubclipse.tigris.org

On 9/7/07, Eric Berry <elberrygmail.com> wrote:
> Mark,
>    Please correct me if I'm wrong, I'm a basic user of
the products, but
> doesn't Subversion version the folders as well. So if
you commit your files
> from the synch view, then go to incoming changes, you
technically should see
> the folders, because each of their revisions need to be
updated. Whenever I
> commit my files, I always have to go to the incoming
changes to update the
> revisions on the folders, and I don't see the files I
just committed.
>
> This might explain the issue where Jay isn't seeing his
own committed files
> and only seeing the folders, but wouldn't help in the
case where another
> colleague had made commits.
>
> Jay, are you perchance doing updates outside of the
synch view?

That is the Show Out of Date folders feature.  You should
read the
blog post that was linked earlier.

It sounds like Jay gets that.  I do think this explains some
of what
he was confused about.  But it also sounds like there is
something
else going on.

-- 
Thanks

Mark Phippard
http://markphip.blogspo
t.com/

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribesubclipse.tigris.org
For additional commands, e-mail: users-helpsubclipse.tigris.org

On 9/7/07, Jay Levitt <lists-subclipseshopwatch.org> wrote:
> > Jay, are you perchance doing updates outside of
the synch view?
>
> I may occasionally commit a single file direct from the
RadRails
> perspective, but all my updates are done from Synch
view w/changesets on.

For the record, this should not matter.  The Synch view does
not know
that you executed an option from it, or elsewhere.  It
entirely
operates on change listeners and indirect updates to the
view.

-- 
Thanks

Mark Phippard
http://markphip.blogspo
t.com/

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribesubclipse.tigris.org
For additional commands, e-mail: users-helpsubclipse.tigris.org