Bzr eclipse doesn't work with latest Eclipse and latest Bzr

Bug #280888 reported by Russel Winder
50
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Bazaar Plugin for Eclipse
Invalid
Undecided
Unassigned
bzr-xmloutput
Fix Released
High
Guillermo Gonzalez

Bug Description

This may be something stupid I am doing but...

I have just had to reinstall Eclipse 3.4 Ganymede on Ubuntu Hardy, I installed from the tarball I had and then immediately updated to get the Ganymede updates. I then installed all the plugins including the Bazaar one. My Bazaar installation is bzr.dev with xmloutput 0.6.1.

Whenever I try to open a project that is a Bazaar branch I get:

Error while executing xmlstatus
    <?xml version="1.0" encoding="UTF-8"?><error><class>AttributeError</class><dict></dict><message>'module' object has no attribute '_raise_if_nonexistent'</message></error>
    <?xml version="1.0" encoding="UTF-8"?><error><class>AttributeError</class><dict></dict><message>'module' object has no attribute '_raise_if_nonexistent'</message></error>

and there is a great deal of activity that slows things down massively for every operation in Eclipse.

Basically the project in unusable with the plugin installed.

Revision history for this message
Guillermo Gonzalez (verterok) wrote :

Hi Russel,

If you are using bzr-eclipse-1.1.0 you need bzr-xmloutput-0.8 (I added a one-time popup window as a warning when the plugin need an update of it dependencies)

Regards,

Revision history for this message
Russel Winder (russel) wrote :

OK, but as noted above I got no nice popup just the message above on the console.

I used to use xmloutput branched from:

bzr+ssh://<email address hidden>/%7Eguillo.gonzo/bzr-xmloutput/xmlrpc

as that was the place that used to be documented as the place to get the cutting edge version. However it seems this is a dead branch stuck at 0.6.1. I guess the problem here is that changes were made to which is the development branch and notice was not issued?

I will try lp:bzr-xmloutput and see if that helps.

OK that gives me 0.8.0.

Eclipse now does seem to go into its problem state but I don't have any Team menu for the Bazaar project. I guess this is a different bug, in need of a different entry -- after further investigation to make sure I give the right data!

Revision history for this message
Guillermo Gonzalez (verterok) wrote :

Russel,
I'll delete that branch, to avoid this problem.
The dialog 'll popup only ofter the first installation of the plugin (and on each update that requires new dependencies) after the requested restart of eclipse. (I don't remember excatly, but I think this is tied to the workspace in use, so if you create new workspace the dialog should appear)

I recommend to uninstall all bzr-eclipse versions and install the lastest.

About the missing Team menu, I don't fully understand, but at least it should provide the disconnect action.

Cheers,

Revision history for this message
Russel Winder (russel) wrote :

OK, that sounds good.

Currently I have installed bzr-eclipse 1.1.0 newly installed from http://verterok.com.ar/bzr-eclipse/update-site.

If I use the context menu over a closed project when I select the Team entry I see a two item submenu with a selectable "Apply patch..." and a greyed out "Share project...".

When I open a project using Bazaar, I get the "Bazaar refreshing" in the bottom right corner for a while and everything seems fine. The project context menu Team entry has all the expected Bazaar entries, they are all greyed out except "Disconnect". The file context menu Team entry has a different set of Bazaar entries all greyed out except the bottom one which is "Show local history".

So it seems that unloading and reloading the Bazaar plugin has cleared up whatever mess I had. However, I am wondering why all the menu entries are greyed out.

Also I have correctly got a question make annotation on the bottom right of a file that is not known to Bazaar, but I do not have a Bazaar annotation on the icons of the files that are actually in need of having changes committed -- shouldn't there be a black asterisk on these?

So significant progress :-) but... :-(

Thanks for helping out on this so promptly, it is much appreciated.

Revision history for this message
Guillermo Gonzalez (verterok) wrote : Re: [Bug 280888] Re: Bzr eclipse doesn't work with latest Eclipse and latest Bzr

Hi Russel,

On Sat, Oct 11, 2008 at 2:59 AM, Russel Winder
<email address hidden> wrote:
> OK, that sounds good.
>
> Currently I have installed bzr-eclipse 1.1.0 newly installed from
> http://verterok.com.ar/bzr-eclipse/update-site.
>
> If I use the context menu over a closed project when I select the Team
> entry I see a two item submenu with a selectable "Apply patch..." and a
> greyed out "Share project...".
>
> When I open a project using Bazaar, I get the "Bazaar refreshing" in the
> bottom right corner for a while and everything seems fine. The project
> context menu Team entry has all the expected Bazaar entries, they are
> all greyed out except "Disconnect". The file context menu Team entry
> has a different set of Bazaar entries all greyed out except the bottom
> one which is "Show local history".
>
> So it seems that unloading and reloading the Bazaar plugin has cleared
> up whatever mess I had. However, I am wondering why all the menu
> entries are greyed out.
>
> Also I have correctly got a question make annotation on the bottom right
> of a file that is not known to Bazaar, but I do not have a Bazaar
> annotation on the icons of the files that are actually in need of having
> changes committed -- shouldn't there be a black asterisk on these?

that looks quite strange, and yes you should have a black asterisk on
modified files.
Maybe you can take a look in the log files: $HOME/.bzr.log and
<WORKSPACE>/.metadata/.log (or the error log view, in case you have
the Eclipse SDK).
In case there is an exception, please send or attach it and I'll try
to figure out what's going on.

>
> So significant progress :-) but... :-(
>
> Thanks for helping out on this so promptly, it is much appreciated.
>
No problem,

Regards,

--Guillermo
> --
> Bzr eclipse doesn't work with latest Eclipse and latest Bzr
> https://bugs.launchpad.net/bugs/280888
> You received this bug notification because you are a member of bzr-
> eclipse developers, which is subscribed to Bazaar Plugin for Eclipse.
>
> Status in Bazaar Plugin for Eclipse: New
>
> Bug description:
> This may be something stupid I am doing but...
>
> I have just had to reinstall Eclipse 3.4 Ganymede on Ubuntu Hardy, I installed from the tarball I had and then immediately updated to get the Ganymede updates. I then installed all the plugins including the Bazaar one. My Bazaar installation is bzr.dev with xmloutput 0.6.1.
>
> Whenever I try to open a project that is a Bazaar branch I get:
>
> Error while executing xmlstatus
> <?xml version="1.0" encoding="UTF-8"?><error><class>AttributeError</class><dict></dict><message>'module' object has no attribute '_raise_if_nonexistent'</message></error>
> <?xml version="1.0" encoding="UTF-8"?><error><class>AttributeError</class><dict></dict><message>'module' object has no attribute '_raise_if_nonexistent'</message></error>
>
> and there is a great deal of activity that slows things down massively for every operation in Eclipse.
>
> Basically the project in unusable with the plugin installed.
>

Revision history for this message
Russel Winder (russel) wrote :

I am still getting messages in the Console:

    Error while executing xmlstatus
    'module' object has no attribute '_raise_if_nonexistent'

which is a bit annoying. From the .bzr.log I am seeing:

1143.129 run_bzr_xml arguments: (['/home/users/russel/bin/bzr', 'xmlstatus', '/home/users/russel/Repositories/Bazaar/Masters/ADS'], '/home/users/russel/Repositories/Bazaar/Masters/ADS')
1143.129 bzr arguments: [u'xmlstatus', u'/home/users/russel/Repositories/Bazaar/Masters/ADS']
1143.139 encoding stdout as osutils.get_user_encoding() 'UTF-8'
1143.151 opening working tree '/home/users/russel/Repositories/Bazaar/Masters/ADS'
1143.173 Traceback (most recent call last):
  File "/home/users/russel/.bazaar/plugins/xmloutput/xml_errors.py", line 61, in xml_error_handling
    return func(*args, **kwargs)
  File "/home/users/russel/.bazaar/plugins/xmloutput/__init__.py", line 123, in run
    to_file=to_file, versioned=versioned)
  File "/home/users/russel/.bazaar/plugins/xmloutput/statusxml.py", line 143, in show_tree_status_xml
    diff._raise_if_nonexistent(specific_files, old, new)
AttributeError: 'module' object has no attribute '_raise_if_nonexistent'

Running form the command line, I get:

|> /home/users/russel/bin/bzr xmlstatus /home/users/russel/Repositories/Bazaar/Masters/ADS
<?xml version="1.0" encoding="UTF-8"?><error><class>AttributeError</class><dict></dict><message>'module' object has no attribute '_raise_if_nonexistent'</message></error>214 balin:~/Repositories/Bazaar/Masters/ADS
|>

Revision history for this message
Guillermo Gonzalez (verterok) wrote :

Hi Russel,

On Sun, Oct 12, 2008 at 8:08 AM, Russel Winder
<email address hidden> wrote:
> I am still getting messages in the Console:
>
> Error while executing xmlstatus
> 'module' object has no attribute '_raise_if_nonexistent'
>
> which is a bit annoying. From the .bzr.log I am seeing:
>
> 1143.129 run_bzr_xml arguments: (['/home/users/russel/bin/bzr', 'xmlstatus', '/home/users/russel/Repositories/Bazaar/Masters/ADS'], '/home/users/russel/Repositories/Bazaar/Masters/ADS')
> 1143.129 bzr arguments: [u'xmlstatus', u'/home/users/russel/Repositories/Bazaar/Masters/ADS']
> 1143.139 encoding stdout as osutils.get_user_encoding() 'UTF-8'
> 1143.151 opening working tree '/home/users/russel/Repositories/Bazaar/Masters/ADS'
> 1143.173 Traceback (most recent call last):
> File "/home/users/russel/.bazaar/plugins/xmloutput/xml_errors.py", line 61, in xml_error_handling
> return func(*args, **kwargs)
> File "/home/users/russel/.bazaar/plugins/xmloutput/__init__.py", line 123, in run
> to_file=to_file, versioned=versioned)
> File "/home/users/russel/.bazaar/plugins/xmloutput/statusxml.py", line 143, in show_tree_status_xml
> diff._raise_if_nonexistent(specific_files, old, new)
> AttributeError: 'module' object has no attribute '_raise_if_nonexistent'
>

This error is related to an incompatible version of bzr and
bzr-xmloutput, it seems that in bzr.dev diff._raise_if_non_existent
was removed recently

I'll try to push a fix during the weekend.

Cheers,

>
> --
> Bzr eclipse doesn't work with latest Eclipse and latest Bzr
> https://bugs.launchpad.net/bugs/280888
> You received this bug notification because you are a member of bzr-
> eclipse developers, which is subscribed to Bazaar Plugin for Eclipse.
>
> Status in Bazaar Plugin for Eclipse: New
>
> Bug description:
> This may be something stupid I am doing but...
>
> I have just had to reinstall Eclipse 3.4 Ganymede on Ubuntu Hardy, I installed from the tarball I had and then immediately updated to get the Ganymede updates. I then installed all the plugins including the Bazaar one. My Bazaar installation is bzr.dev with xmloutput 0.6.1.
>
> Whenever I try to open a project that is a Bazaar branch I get:
>
> Error while executing xmlstatus
> <?xml version="1.0" encoding="UTF-8"?><error><class>AttributeError</class><dict></dict><message>'module' object has no attribute '_raise_if_nonexistent'</message></error>
> <?xml version="1.0" encoding="UTF-8"?><error><class>AttributeError</class><dict></dict><message>'module' object has no attribute '_raise_if_nonexistent'</message></error>
>
> and there is a great deal of activity that slows things down massively for every operation in Eclipse.
>
> Basically the project in unusable with the plugin installed.
>

Revision history for this message
Guillermo Gonzalez (verterok) wrote :

The problem was that bzr-xmloutput is using bzr internal API, and it changed in revno 3756 (3224.5.19).

Changed in bzr-eclipse:
status: New → Invalid
Revision history for this message
Guillermo Gonzalez (verterok) wrote :

I'm working on a fix. that shortly 'll land in trunk.

Changed in bzr-xmloutput:
assignee: nobody → guillo.gonzo
importance: Undecided → High
status: New → In Progress
Changed in bzr-xmloutput:
status: In Progress → Fix Committed
Revision history for this message
s4lv0 (s4lv00) wrote :
Revision history for this message
Evan Willms (ewillms) wrote :

I had the same disabled items problem and .bzr.log error ( AttributeError: 'module' object has no attribute '_raise_if_nonexistent' ) under Windows with a fresh install of Eclipse 3.4, bzr 1.8rc1,xmloutput 0.8.0, and bzr-eclipse 1.1.0.

Getting the latest head version of xmloutput from launchpad ( 0.9.0dev0 ) and manually installing the plugin (which needs SimpleXMLRPCServer.py, I just overwrote the NCIS installed 0.8.0 files) has gotten things working.

Revision history for this message
Guillermo Gonzalez (verterok) wrote :

Thanks for the sharing this.

I'm sure this 'ld help other users until a new version of xmloutput is realeased.

Regardsm

Revision history for this message
bianchi (uspbianchi) wrote :

Hi,

Guillermo, do you have any idea when this fix will be available? Until there, how can I get the latest version (0.9)?

Thanks a lot,

Thiago

Revision history for this message
Guillermo Gonzalez (verterok) wrote :

Hi,

If you are using Windows with the standalone bzr.exe, you can do like Evan Willms commented above, just: bzr branch lp:bzr-xmloutput and copy the contents in the previous installed xmloutput.
In other cases (windows with python based installers and *nix) just:
 bzr branch lp:bzr-xmloutput $HOME/.bazaar/plugins/xmloutput

Remember to remove previously installed xmloutput if you are using the later approach.

I'll be doing a release ASAP.

Cheers,

Revision history for this message
bianchi (uspbianchi) wrote :

Thanks a lot,

Like Evan said it's working now with the development version.

Thanks a lot,

Thiago

Changed in bzr-xmloutput:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.