Bug 274748 - Collecting resources and send notification operations fails
Summary: Collecting resources and send notification operations fails
Status: RESOLVED DUPLICATE of bug 274010
Alias: None
Product: Subversive
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Linux
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Igor Burilo CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-03 07:07 EDT by David Norman CLA
Modified: 2009-05-05 03:59 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Norman CLA 2009-05-03 07:07:45 EDT
Build ID: M20090211-1700

Steps To Reproduce:
1. Right click on a project
2. Choose Team -> Commit
3. Error message appears

or... just save a file under SVN control

More information:
This is the error message I get when trying to commit a file:

SVN: '0x00400039: Collecting Resources' operation finished with error: org.eclipse.team.svn.core.connector.SVNChangeStatus.<init>(Ljava/lang/String;Ljava/lang/String;IJJJLjava/lang/String;IIIIZZLjava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;JZLjava/lang/String;Ljava/lang/String;Ljava/lang/String;JLorg/eclipse/team/svn/core/connector/SVNLock;JJILjava/lang/String;)V
org.eclipse.team.svn.core.connector.SVNChangeStatus.<init>(Ljava/lang/String;Ljava/lang/String;IJJJLjava/lang/String;IIIIZZLjava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;JZLjava/lang/String;Ljava/lang/String;Ljava/lang/String;JLorg/eclipse/team/svn/core/connector/SVNLock;JJILjava/lang/String;)V

Then if I try to save a file under SVN control, I get a Send notifications operation failed:

SVN: '0x00000025: Send Notifications' operation finished with error: org.eclipse.team.svn.core.connector.SVNChangeStatus.<init>(Ljava/lang/String;Ljava/lang/String;IJJJLjava/lang/String;IIIIZZLjava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;JZLjava/lang/String;Ljava/lang/String;Ljava/lang/String;JLorg/eclipse/team/svn/core/connector/SVNLock;JJILjava/lang/String;)V
org.eclipse.team.svn.core.connector.SVNChangeStatus.<init>(Ljava/lang/String;Ljava/lang/String;IJJJLjava/lang/String;IIIIZZLjava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;JZLjava/lang/String;Ljava/lang/String;Ljava/lang/String;JLorg/eclipse/team/svn/core/connector/SVNLock;JJILjava/lang/String;)V

With the send notifications window, I get an additional window that says:

'Updating Change Sets for org.eclipse.team.svn.core.synchronize.UpdateSubscriber' has encountered a problem
An internal error occurred during: "Updating Change Sets for org.eclipse.team.svn.core.synchronize.UpdateSubscriber".

I didn't have any of these problems when I was running 0.7.7,I20090224-1900. The errors happen in both 0.7.8.I20090428-1500 and 0.7.7.I20090422-1500.

The result is that Subversive is completely unusable and that saving files is extremely annoying because I get two error boxes per save. I'm not able to use the automated report sender button because apparently I don't have a proper reporting plugin installed, so send is grayed out.
Comment 1 David Norman CLA 2009-05-03 08:56:43 EDT
I got extreme and did a complete reinstall of Eclipse, PDT 2, and Subversive. When that still didn't fix the errors, I decided maybe it had something to do with the way my existing projects were checked out, so I checked out a new project from SVN. It seemed to be working fine doing that until the very end:

Checkout operation for 'svn+ssh://xxx@svn.example.com/var/svn/repo/trunk' failed.
org.eclipse.team.svn.core.connector.SVNChangeStatus.<init>(Ljava/lang/String;Ljava/lang/String;IJJJLjava/lang/String;IIIIZZLjava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;JZLjava/lang/String;Ljava/lang/String;Ljava/lang/String;JLorg/eclipse/team/svn/core/connector/SVNLock;JJILjava/lang/String;)V

...and I get the same errors I pasted before with the new checkout.
Comment 2 Igor Burilo CLA 2009-05-05 03:59:06 EDT

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