Vuze Forums

Full Version: Bug in plugin - AutoPilot v0.5.1
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Have had this problem with the AutoPilot plugin for a while now but thought someone else would report and fix... but since that didn't happen, here's my post. Other than this plugin, everything is fine.


Java 1.8.0_66 (64 bit)
Oracle Corporation
SWT v4508, win32
Windows 10 v10.0, amd64
V5.7.0.0/4 az3

For the last few months now, the plugin AutoPilot ( has had problems rendering its global configuration UI. Note: previously configured rules continue to be applied for new torrents, and existing torrents can be manually configured (Right-click, Other, Change auto-stop settings for this torrent). The global rules, however, can not be accessed. There is no line if you click on "Tools - Plugins".  No log message is created when viewing that menu list.

If you go to "Tools - Options - Plugins" there is a menu item for AutoPilot, however selecting it does nothing (it continues to display the previous config panel), but the following is logged:

12:25:38.764 3 stderr DEBUG::Tue Dec 22 12:25:38 EST 2015::org.gudy.azureus2.ui.swt.mainwindow.SWTThread::createInstance::61:
12:25:38.765 3 stderr An unhandled error occurred in the GUI, further errors may be reported.
12:25:38.765 3 stderr Initializer::<init>::160, NativeConstructorAccessorImpl::newInstance0::-2, NativeConstructorAccessorImpl::newInstance::62, DelegatingConstructorAccessorImpl::newInstance::45, Constructor::newInstance::422, Main::<init>::111, Main::main::334, NativeMethodAccessorImpl::invoke0::-2, NativeMethodAccessorImpl::invoke::62, DelegatingMethodAccessorImpl::invoke::43, Method::invoke::497, MainExecutor$1::run::34, Thread::run::745
12:25:38.765 3 stderr java.lang.NoSuchMethodError: org.gudy.azureus2.ui.swt.config.BooleanParameter.isSelected()Z
12:25:38.766 3 stderr at com.tdelta.azureus.plugins.autopilot.UI.AutoPilotConfig.configSectionCreate(
12:25:38.766 3 stderr at org.gudy.azureus2.ui.swt.views.ConfigView.ensureSectionBuilt(
12:25:38.766 3 stderr at org.gudy.azureus2.ui.swt.views.ConfigView.showSection(
12:25:38.766 3 stderr at org.gudy.azureus2.ui.swt.views.ConfigView.access$200(
12:25:38.767 3 stderr at org.gudy.azureus2.ui.swt.views.ConfigView$7.widgetSelected(
12:25:38.767 3 stderr at org.eclipse.swt.widgets.TypedListener.handleEvent(
12:25:38.767 3 stderr at org.eclipse.swt.widgets.EventTable.sendEvent(
12:25:38.767 3 stderr at org.eclipse.swt.widgets.Display.sendEvent(
12:25:38.767 3 stderr at org.eclipse.swt.widgets.Widget.sendEvent(
12:25:38.767 3 stderr at org.eclipse.swt.widgets.Display.runDeferredEvents(
12:25:38.768 3 stderr at org.eclipse.swt.widgets.Display.readAndDispatch(
12:25:38.768 3 stderr at org.gudy.azureus2.ui.swt.mainwindow.SWTThread.<init>;(
12:25:38.768 3 stderr at org.gudy.azureus2.ui.swt.mainwindow.SWTThread.createInstance(
12:25:38.768 3 stderr at com.aelitis.azureus.ui.swt.Initializer.<init>;(
12:25:38.768 3 stderr at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
12:25:38.769 3 stderr at sun.reflect.NativeConstructorAccessorImpl.newInstance(
12:25:38.769 3 stderr at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
12:25:38.769 3 stderr at java.lang.reflect.Constructor.newInstance(
12:25:38.769 3 stderr at org.gudy.azureus2.ui.swt.Main.<init>;(
12:25:38.769 3 stderr at org.gudy.azureus2.ui.swt.Main.main(
12:25:38.770 3 stderr at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
12:25:38.770 3 stderr at sun.reflect.NativeMethodAccessorImpl.invoke(
12:25:38.770 3 stderr at sun.reflect.DelegatingMethodAccessorImpl.invoke(
12:25:38.770 3 stderr at java.lang.reflect.Method.invoke(
12:25:38.770 3 stderr at com.aelitis.azureus.launcher.MainExecutor$
12:25:38.771 3 stderr at

Anyone know what might be going on and how to fix it?
Well, it appears that yesterday someone pushed out an update for this plugin, and I am now able to confirm that v0.5.2 of AutoPilot does, indeed, return full functionality.

Surprised the developer (Carl?) didn't post to say he had looked into the issue, but I'm glad enough that it has been fixed!

Thanks - Issue closed.

Sorry, missed the original bug report and only just got around to looking into it - happy 2016 :)