You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@netbeans.apache.org by "Greenberg, Gary" <gg...@visa.com.INVALID> on 2022/12/05 22:28:10 UTC

What happened with Netbeans bug reporting?

It used to be a feature that allows to submit exceptions along with some other info to Netbeans development team with a
click of a button.
Now you can only open notification and view the exception stack trace and that's it. Exceptions do occur regularly and I
mostly ignore them. I did raise this question sometime ago and was told that now I need to open JIRA ticket manually to
submit any NB problem and supply code samples in Apache GIT.
IMHO it is bad idea and not acceptable for many Netbeans users because

  1.  It does take more time, which is hard to allocate in busy development schedule.
  2.  Many companies (like mine) for security reasons do not allow to use offsite GIT and JIRA
Therefore, Netbeans team diminishing their ability to fix bugs and other problems.

For example, yesterday I was debugging an application and wanted to see changes in the database. I did have SQL window open.
As I switched to this SQL tab, exception occurred and all windows in Netbeans were garbled.
I saved the stack trace and had to restart NB as it was not responsive.
Here the stack trace:

java.lang.NullPointerException
    at org.netbeans.modules.db.dataview.util.FileBackedClob.getSubString(FileBackedClob.java:166)
    at org.netbeans.modules.db.dataview.util.LobHelper.clobToString(LobHelper.java:142)
    at org.netbeans.modules.db.dataview.table.ClobCellRenderer.getTableCellRendererComponent(ResultSetCellRenderer.java:217)
    at org.netbeans.modules.db.dataview.table.ResultSetCellRenderer.getTableCellRendererComponent(ResultSetCellRenderer.java:98)
    at java.desktop/javax.swing.JTable.prepareRenderer(JTable.java:5741)
    at org.netbeans.modules.db.dataview.table.JXTableDecorator.prepareRenderer(JXTableDecorator.java:119)
    at org.netbeans.modules.db.dataview.output.DataViewTableUI.prepareRenderer(DataViewTableUI.java:126)
    at java.desktop/javax.swing.plaf.basic.BasicTableUI.paintCell(BasicTableUI.java:2190)
    at java.desktop/javax.swing.plaf.basic.BasicTableUI.paintCells(BasicTableUI.java:2092)
    at java.desktop/javax.swing.plaf.basic.BasicTableUI.paint(BasicTableUI.java:1888)
    at com.formdev.flatlaf.ui.FlatTableUI.paint(FlatTableUI.java:396)
    at java.desktop/javax.swing.plaf.ComponentUI.update(ComponentUI.java:161)
    at java.desktop/javax.swing.JComponent.paintComponent(JComponent.java:797)
    at java.desktop/javax.swing.JComponent.paint(JComponent.java:1074)
    at org.netbeans.modules.db.dataview.table.JXTableDecorator.paint(JXTableDecorator.java:65)
    at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
    at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
    at java.desktop/javax.swing.JViewport.paint(JViewport.java:737)
    at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
    at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
    at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
    at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
    at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
    at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
    at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
    at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
    at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
    at java.desktop/javax.swing.JSplitPane.paintChildren(JSplitPane.java:1024)
    at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
    at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
    at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
    at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
    at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
    at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
    at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
    at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
    at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
    at org.netbeans.swing.tabcontrol.TabbedContainer.paint(TabbedContainer.java:969)
    at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
    at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
    at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
    at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
    at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
    at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
    at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
    at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
    at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
    at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
    at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
    at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
    at java.desktop/javax.swing.JLayeredPane.paint(JLayeredPane.java:586)
    at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
    at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
    at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
    at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
    at org.netbeans.core.windows.view.ui.MainWindow$1.paint(MainWindow.java:166)
    at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
    at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
    at java.desktop/javax.swing.JLayeredPane.paint(JLayeredPane.java:586)
    at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
    at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
    at java.desktop/javax.swing.JComponent.paintToOffscreen(JComponent.java:5255)
    at java.desktop/javax.swing.RepaintManager$PaintManager.paintDoubleBufferedImpl(RepaintManager.java:1643)
    at java.desktop/javax.swing.RepaintManager$PaintManager.paintDoubleBuffered(RepaintManager.java:1618)
    at java.desktop/javax.swing.RepaintManager$PaintManager.paint(RepaintManager.java:1556)
    at java.desktop/javax.swing.RepaintManager.paint(RepaintManager.java:1323)
    at java.desktop/javax.swing.JComponent._paintImmediately(JComponent.java:5203)
    at java.desktop/javax.swing.JComponent.paintImmediately(JComponent.java:5013)
    at java.desktop/javax.swing.RepaintManager$4.run(RepaintManager.java:865)
    at java.desktop/javax.swing.RepaintManager$4.run(RepaintManager.java:848)
    at java.base/java.security.AccessController.doPrivileged(AccessController.java:391)
    at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
    at java.desktop/javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:848)
    at java.desktop/javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:823)
    at java.desktop/javax.swing.RepaintManager.prePaintDirtyRegions(RepaintManager.java:772)
    at java.desktop/javax.swing.RepaintManager$ProcessingRunnable.run(RepaintManager.java:1884)
    at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:316)
    at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:770)
    at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
    at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
    at java.base/java.security.AccessController.doPrivileged(AccessController.java:391)
    at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
    at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:740)
    at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)
[catch] at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
    at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
    at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
    at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
    at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
    at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)

And here is my NB info

Product Version: Apache NetBeans IDE 14

Java: 14.0.2; Java HotSpot(TM) 64-Bit Server VM 14.0.2+12-46

Runtime: Java(TM) SE Runtime Environment 14.0.2+12-46

System: Windows 10 version 10.0 running on amd64; Cp1252; en_US (nb)

Gary Greenberg
Staff Software Engineer

Re: What happened with Netbeans bug reporting?

Posted by Scott Palmer <sw...@gmail.com>.
I personally would prefer a setting somewhere that lets NB automatically gather exception info. Opt-in only to be privacy-friendly. An automated system that collects exceptions and counts how many are reported for each unique stack trace could help direct developers to things that should be addressed.
I don’t think they should go automatically into the bug database.  They should be visible to developers to triage.
If the exception has been dealt with in a newer version of NB (this info would be available when the exceptions automatically submitted), the UI could indicate that to the user.

Scott

> On Dec 5, 2022, at 5:28 PM, Greenberg, Gary <gg...@visa.com.INVALID> wrote:
> 
> It used to be a feature that allows to submit exceptions along with some other info to Netbeans development team with a
> click of a button.
> Now you can only open notification and view the exception stack trace and that’s it. Exceptions do occur regularly and I
> mostly ignore them. I did raise this question sometime ago and was told that now I need to open JIRA ticket manually to
> submit any NB problem and supply code samples in Apache GIT.
> IMHO it is bad idea and not acceptable for many Netbeans users because
> It does take more time, which is hard to allocate in busy development schedule.
> Many companies (like mine) for security reasons do not allow to use offsite GIT and JIRA
> Therefore, Netbeans team diminishing their ability to fix bugs and other problems.
>  
> For example, yesterday I was debugging an application and wanted to see changes in the database. I did have SQL window open.
> As I switched to this SQL tab, exception occurred and all windows in Netbeans were garbled.
> I saved the stack trace and had to restart NB as it was not responsive.
> Here the stack trace:
> java.lang.NullPointerException
>     at org.netbeans.modules.db.dataview.util.FileBackedClob.getSubString(FileBackedClob.java:166)
>     at org.netbeans.modules.db.dataview.util.LobHelper.clobToString(LobHelper.java:142)
>     at org.netbeans.modules.db.dataview.table.ClobCellRenderer.getTableCellRendererComponent(ResultSetCellRenderer.java:217)
>     at org.netbeans.modules.db.dataview.table.ResultSetCellRenderer.getTableCellRendererComponent(ResultSetCellRenderer.java:98)
>     at java.desktop/javax.swing.JTable.prepareRenderer(JTable.java:5741)
>     at org.netbeans.modules.db.dataview.table.JXTableDecorator.prepareRenderer(JXTableDecorator.java:119)
>     at org.netbeans.modules.db.dataview.output.DataViewTableUI.prepareRenderer(DataViewTableUI.java:126)
>     at java.desktop/javax.swing.plaf.basic.BasicTableUI.paintCell(BasicTableUI.java:2190)
>     at java.desktop/javax.swing.plaf.basic.BasicTableUI.paintCells(BasicTableUI.java:2092)
>     at java.desktop/javax.swing.plaf.basic.BasicTableUI.paint(BasicTableUI.java:1888)
>     at com.formdev.flatlaf.ui.FlatTableUI.paint(FlatTableUI.java:396)
>     at java.desktop/javax.swing.plaf.ComponentUI.update(ComponentUI.java:161)
>     at java.desktop/javax.swing.JComponent.paintComponent(JComponent.java:797)
>     at java.desktop/javax.swing.JComponent.paint(JComponent.java:1074)
>     at org.netbeans.modules.db.dataview.table.JXTableDecorator.paint(JXTableDecorator.java:65)
>     at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
>     at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
>     at java.desktop/javax.swing.JViewport.paint(JViewport.java:737)
>     at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
>     at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
>     at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
>     at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
>     at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
>     at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
>     at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
>     at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
>     at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
>     at java.desktop/javax.swing.JSplitPane.paintChildren(JSplitPane.java:1024)
>     at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
>     at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
>     at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
>     at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
>     at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
>     at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
>     at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
>     at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
>     at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
>     at org.netbeans.swing.tabcontrol.TabbedContainer.paint(TabbedContainer.java:969)
>     at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
>     at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
>     at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
>     at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
>     at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
>     at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
>     at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
>     at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
>     at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
>     at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
>     at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
>     at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
>     at java.desktop/javax.swing.JLayeredPane.paint(JLayeredPane.java:586)
>     at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
>     at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
>     at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
>     at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
>     at org.netbeans.core.windows.view.ui.MainWindow$1.paint(MainWindow.java:166)
>     at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
>     at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
>     at java.desktop/javax.swing.JLayeredPane.paint(JLayeredPane.java:586)
>     at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907)
>     at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083)
>     at java.desktop/javax.swing.JComponent.paintToOffscreen(JComponent.java:5255)
>     at java.desktop/javax.swing.RepaintManager$PaintManager.paintDoubleBufferedImpl(RepaintManager.java:1643)
>     at java.desktop/javax.swing.RepaintManager$PaintManager.paintDoubleBuffered(RepaintManager.java:1618)
>     at java.desktop/javax.swing.RepaintManager$PaintManager.paint(RepaintManager.java:1556)
>     at java.desktop/javax.swing.RepaintManager.paint(RepaintManager.java:1323)
>     at java.desktop/javax.swing.JComponent._paintImmediately(JComponent.java:5203)
>     at java.desktop/javax.swing.JComponent.paintImmediately(JComponent.java:5013)
>     at java.desktop/javax.swing.RepaintManager$4.run(RepaintManager.java:865)
>     at java.desktop/javax.swing.RepaintManager$4.run(RepaintManager.java:848)
>     at java.base/java.security.AccessController.doPrivileged(AccessController.java:391)
>     at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
>     at java.desktop/javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:848)
>     at java.desktop/javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:823)
>     at java.desktop/javax.swing.RepaintManager.prePaintDirtyRegions(RepaintManager.java:772)
>     at java.desktop/javax.swing.RepaintManager$ProcessingRunnable.run(RepaintManager.java:1884)
>     at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:316)
>     at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:770)
>     at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
>     at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
>     at java.base/java.security.AccessController.doPrivileged(AccessController.java:391)
>     at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
>     at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:740)
>     at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)
> [catch] at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
>     at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
>     at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
>     at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
>     at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
>     at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
> 
> And here is my NB info
> 
> Product Version: Apache NetBeans IDE 14 
> Java: 14.0.2; Java HotSpot(TM) 64-Bit Server VM 14.0.2+12-46
> Runtime: Java(TM) SE Runtime Environment 14.0.2+12-46
> System: Windows 10 version 10.0 running on amd64; Cp1252; en_US (nb)
>  
> Gary Greenberg
> Staff Software Engineer

Re: What happened with Netbeans bug reporting?

Posted by Ernie Rael <er...@raelity.com>.
On 22/12/07 7:05 AM, Neil C Smith wrote:
> On Mon, 5 Dec 2022 at 22:28, Greenberg, Gary <gg...@visa.com.invalid> wrote:
>> It used to be a feature that allows to submit exceptions along with some other info to Netbeans development team with a
>> click of a button.
>> Now you can only open notification and view the exception stack trace and that’s it. Exceptions do occur regularly and I
>> mostly ignore them. I did raise this question sometime ago and was told that now I need to open JIRA ticket manually to
>> submit any NB problem and supply code samples in Apache GIT.
> The infrastructure for accepting issues in that way no longer exists.
> It never existed at Apache.
>
> NetBeans issues should be reported in the GitHub issue queue.  There
> is no JIRA access for users.  You'll need a GitHub account to report -
> https://github.com/apache/netbeans/issues
>
> See also https://netbeans.apache.org/participate/report-issue.html
>
>
>> IMHO it is bad idea and not acceptable for many Netbeans users because
>>
>> It does take more time, which is hard to allocate in busy development schedule.
> You need to balance that with the time needed for the volunteer
> NetBeans community, many of whom also have a busy development
> schedule, to assess any reported issue.  Yes, you may now need to
> spend more time in order to provide all of the required information to
> submit an issue.  It's better than incomplete issue reports
> languishing completely ignored.  IMHO that is an even worse and
> unacceptable situation for everyone.

IIRC, the automated submission of exceptions accumulated same/similar 
exceptions into a single issue. That allowed frequently occurring 
exceptions to bubble to the top. It was more than just a bunch of 
scattered reports.

-ernie
>
> Best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: users-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@netbeans.apache.org
For additional commands, e-mail: users-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: What happened with Netbeans bug reporting?

Posted by Neil C Smith <ne...@apache.org>.
On Wed, 7 Dec 2022 at 16:31, Sean Carrick <se...@pekinsoft.com> wrote:
> It's really too bad that NetBeans Project went with GitHub, instead of GitLab...GitLab has a feature called "Service Desk" that provides a unique email address to which bugs, RFEs, etc., can be email by anonymous users, without them needing a GitLab account. In that instance, NB would only have needed to change the private code of the old bug reporter to redirect to the Service Desk email address...Just an FYI for the future, maybe.

NetBeans went with Apache!  And GitHub happens to be a major sponsor
of Apache, and there's a lot of additional resources and linkage back
and forth.

Could we support anonymous bugs and RFEs?  Quite probably.  Whether
there would be any desire to is another matter.  Personally I think we
have enough on our plates trying to handle issues and RFEs from
seriously engaged non-anonymous users.  Our previous JIRA instance was
full of likely unread, semi-anonymous, exception reporter style
issues, and it was utterly pointless.

Best wishes,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@netbeans.apache.org
For additional commands, e-mail: users-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: What happened with Netbeans bug reporting?

Posted by Michael Bien <mb...@gmail.com>.
the most important part of an issue report is a minimal reproducer or 
steps how to reproduce the issue. Since the main user base of an IDE are 
devs, it is often possible to get good quality submissions in some cases.

It is really difficult to automate this. Telemetry can do only so much 
and privacy/trust is also a concern there (you don't want your IDE to 
upload your source code if there is a parsing error or take screen 
shots, right?).

With the traditional submission process a user can decide what 
information to provide and review logs/snippets etc before submission - 
so the whole problem is completely avoided.

Since the user base of an IDE are devs, it is also likely that they have 
a github account already. So this shouldn't be a big barrier if you 
really want to submit a bug report.

And as Neil already alluded to: open source projects rarely have a lack 
of issue submissions. There is no need to artificially inflate the issue 
count with automated uploads [1].

Some open source projects go even a step further and automatically close 
stale/inactive issues after a certain time period. Since inactive issues 
are probably not interesting enough to be fixed by the community - no 
need to keep them in the system forever.

best regards,
michael

[1] https://martinfowler.com/bliki/Datensparsamkeit.html


On 07.12.22 17:31, Sean Carrick wrote:
> It's really too bad that NetBeans Project went with GitHub, instead of 
> GitLab...GitLab has a feature called "Service Desk" that provides a 
> unique email address to which bugs, RFEs, etc., can be email by 
> anonymous users, without them needing a GitLab account. In that 
> instance, NB would only have needed to change the private code of the 
> old bug reporter to redirect to the Service Desk email address...Just 
> an FYI for the future, maybe.
>
> Sincerely,
>
> Sean Carrick
> Owner - PekinSOFT Systems
> sean@pekinsoft.com
> (309) 989-0672
>
>
> On Wed, Dec 7, 2022 at 9:05 AM Neil C Smith <ne...@apache.org> wrote:
>
>     On Mon, 5 Dec 2022 at 22:28, Greenberg, Gary
>     <gg...@visa.com.invalid> wrote:
>     > It used to be a feature that allows to submit exceptions along
>     with some other info to Netbeans development team with a
>     > click of a button.
>     > Now you can only open notification and view the exception stack
>     trace and that’s it. Exceptions do occur regularly and I
>     > mostly ignore them. I did raise this question sometime ago and
>     was told that now I need to open JIRA ticket manually to
>     > submit any NB problem and supply code samples in Apache GIT.
>
>     The infrastructure for accepting issues in that way no longer exists.
>     It never existed at Apache.
>
>     NetBeans issues should be reported in the GitHub issue queue. There
>     is no JIRA access for users.  You'll need a GitHub account to report -
>     https://github.com/apache/netbeans/issues
>
>     See also https://netbeans.apache.org/participate/report-issue.html
>
>
>     > IMHO it is bad idea and not acceptable for many Netbeans users
>     because
>     >
>     > It does take more time, which is hard to allocate in busy
>     development schedule.
>
>     You need to balance that with the time needed for the volunteer
>     NetBeans community, many of whom also have a busy development
>     schedule, to assess any reported issue.  Yes, you may now need to
>     spend more time in order to provide all of the required information to
>     submit an issue.  It's better than incomplete issue reports
>     languishing completely ignored.  IMHO that is an even worse and
>     unacceptable situation for everyone.
>
>     Best wishes,
>
>     Neil
>
>     ---------------------------------------------------------------------
>     To unsubscribe, e-mail: users-unsubscribe@netbeans.apache.org
>     For additional commands, e-mail: users-help@netbeans.apache.org
>
>     For further information about the NetBeans mailing lists, visit:
>     https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>

Re: What happened with Netbeans bug reporting?

Posted by Sean Carrick <se...@pekinsoft.com>.
It's really too bad that NetBeans Project went with GitHub, instead of
GitLab...GitLab has a feature called "Service Desk" that provides a unique
email address to which bugs, RFEs, etc., can be email by anonymous users,
without them needing a GitLab account. In that instance, NB would only have
needed to change the private code of the old bug reporter to redirect to
the Service Desk email address...Just an FYI for the future, maybe.

Sincerely,

Sean Carrick
Owner - PekinSOFT Systems
sean@pekinsoft.com
(309) 989-0672


On Wed, Dec 7, 2022 at 9:05 AM Neil C Smith <ne...@apache.org> wrote:

> On Mon, 5 Dec 2022 at 22:28, Greenberg, Gary <gg...@visa.com.invalid>
> wrote:
> > It used to be a feature that allows to submit exceptions along with some
> other info to Netbeans development team with a
> > click of a button.
> > Now you can only open notification and view the exception stack trace
> and that’s it. Exceptions do occur regularly and I
> > mostly ignore them. I did raise this question sometime ago and was told
> that now I need to open JIRA ticket manually to
> > submit any NB problem and supply code samples in Apache GIT.
>
> The infrastructure for accepting issues in that way no longer exists.
> It never existed at Apache.
>
> NetBeans issues should be reported in the GitHub issue queue.  There
> is no JIRA access for users.  You'll need a GitHub account to report -
> https://github.com/apache/netbeans/issues
>
> See also https://netbeans.apache.org/participate/report-issue.html
>
>
> > IMHO it is bad idea and not acceptable for many Netbeans users because
> >
> > It does take more time, which is hard to allocate in busy development
> schedule.
>
> You need to balance that with the time needed for the volunteer
> NetBeans community, many of whom also have a busy development
> schedule, to assess any reported issue.  Yes, you may now need to
> spend more time in order to provide all of the required information to
> submit an issue.  It's better than incomplete issue reports
> languishing completely ignored.  IMHO that is an even worse and
> unacceptable situation for everyone.
>
> Best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: users-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>

Re: What happened with Netbeans bug reporting?

Posted by Neil C Smith <ne...@apache.org>.
On Mon, 5 Dec 2022 at 22:28, Greenberg, Gary <gg...@visa.com.invalid> wrote:
> It used to be a feature that allows to submit exceptions along with some other info to Netbeans development team with a
> click of a button.
> Now you can only open notification and view the exception stack trace and that’s it. Exceptions do occur regularly and I
> mostly ignore them. I did raise this question sometime ago and was told that now I need to open JIRA ticket manually to
> submit any NB problem and supply code samples in Apache GIT.

The infrastructure for accepting issues in that way no longer exists.
It never existed at Apache.

NetBeans issues should be reported in the GitHub issue queue.  There
is no JIRA access for users.  You'll need a GitHub account to report -
https://github.com/apache/netbeans/issues

See also https://netbeans.apache.org/participate/report-issue.html


> IMHO it is bad idea and not acceptable for many Netbeans users because
>
> It does take more time, which is hard to allocate in busy development schedule.

You need to balance that with the time needed for the volunteer
NetBeans community, many of whom also have a busy development
schedule, to assess any reported issue.  Yes, you may now need to
spend more time in order to provide all of the required information to
submit an issue.  It's better than incomplete issue reports
languishing completely ignored.  IMHO that is an even worse and
unacceptable situation for everyone.

Best wishes,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@netbeans.apache.org
For additional commands, e-mail: users-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists