This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Created attachment 140341 [details] The ZIP of NBMs I am trying to upload (compatible with both 7.3 and 7.4) I tried to upload binaries to http://plugins.netbeans.org/plugin/43938/ both as an “Edit” to the 7.3 version, and as a new binary for 7.4. Both attempts failed: I got some unspecified error in the web UI.
31923 2013-09-21 17:18:44 Stapler/Hudson/Jenkins Support jglick Binary uploaded successfully - /space/pluginportal-v2/public/data/nbms/nb-stapler.zip 31922 2013-09-21 17:18:44 Stapler/Hudson/Jenkins Support jglick Uploading new binary for version 7.4 31921 2013-09-21 17:17:16 Stapler/Hudson/Jenkins Support jglick Binary uploaded successfully - /space/pluginportal-v2/public/data/nbms/nb-stapler.zip 31920 2013-09-21 17:17:16 Stapler/Hudson/Jenkins Support jglick Uploading new binary for version 7.3 I don't see any problem in the log. Honzo, can you please take a look at this? Jesse, a screenshot would maybe help.
> I don't see any problem in the log. And yet the plugin page does not show any new binaries. > a screenshot would maybe help All that is shown in the browser after uploading is ---%<--- An error occurred Application error ---%<--- Also when I go back to http://plugins.netbeans.org/my-plugins I see ERROR: SQLSTATE[HY000]: General error: 1366 Incorrect integer value: '(0)' for column 'signed' at row 1 in a red box at the top of the screen the first time I visit this URL after the failed upload. When I reload the page, it goes away.
I guess the problem was that the NBMs were unsigned. When I regenerate them with signatures and upload again it works. But this is a pretty lousy way to report that error! (BTW requiring plugin authors to sign NBMs is a PIA. Plugin Portal should repack unsigned NBMs with its own signature instead.)
Downgrading since the problem is one of error reporting, not affecting valid usage.
This is strange, because in the past it generated a nice red warning message. Honzo, is it somehow related to the MySQL upgrade?
fixed now