One more I'd add - http://statistics.netbeans.org/analytics/detail.do?id=225493 (The {{ exception)

Quite possibly the same root cause as some of the others below (editor state gets confused).

This happens maybe 4 times a week, but when it does you have to close out and restart or lines start to disappear from your file without the possibility of undo.

Dawn

On 02/01/2018 21:07, Jan Lahoda wrote:
I've accidentally responded only to Gili outside the list, apologizes. Forwarding the conversation.

Jan

---------- Forwarded message ----------
From: *cowwoc* <[email protected] <mailto:[email protected]>>
Date: Sun, Dec 31, 2017 at 10:38 PM
Subject: Re: Question about issue tracker
To: Jan Lahoda <[email protected] <mailto:[email protected]>>


Yes. Go ahead.

Gili


On 2017-12-31 10:04 AM, Jan Lahoda wrote:
Hi Gili,

Thanks for the pointer. I'll look at what I can. I accidentally sent the e-mail just to you instead of the mailing list - is it OK to forward your e-mail back to the mailing lists?

Thanks,
    Jan


On Sun, Dec 31, 2017 at 2:02 PM, cowwoc <[email protected] <mailto:[email protected]>> wrote:

    Hi Jan,

    Here are some concrete examples:

    https://netbeans.org/bugzilla/show_bug.cgi?id=270632
    <https://netbeans.org/bugzilla/show_bug.cgi?id=270632> <-- makes
    IDE slow to the point of being unusable
    https://netbeans.org/bugzilla/show_bug.cgi?id=252602
    <https://netbeans.org/bugzilla/show_bug.cgi?id=252602> <-- not as
    bad, but still extremely annoying if you are using Find Usages
    frequently
    https://netbeans.org/bugzilla/show_bug.cgi?id=270272
    <https://netbeans.org/bugzilla/show_bug.cgi?id=270272> <--
    impossible to debug lambdas
    https://netbeans.org/bugzilla/show_bug.cgi?id=250595
    <https://netbeans.org/bugzilla/show_bug.cgi?id=250595> <-- error
    that depends on your project state, but once you get into this
    bad state it is extremely annoying (parsing errors get thrown
    very frequently)
    https://netbeans.org/bugzilla/show_bug.cgi?id=255791
    <https://netbeans.org/bugzilla/show_bug.cgi?id=255791> <--
    parsing issue similar to previous one
    https://netbeans.org/bugzilla/show_bug.cgi?id=271633
    <https://netbeans.org/bugzilla/show_bug.cgi?id=271633> <-- cannot
    code-complete methods in enums. I've recently seen a similar
    problem for non-enum anonymous classes. End result: I keep on
    having to type method prototypes by hand.

    Some of these issues have been around for years. There are
    stack-traces, profiler dumps, and sometimes even full-out repro
    steps but there has been no follow-up from the committers' end.
    Communication is very important to prevent bug reports from
    becoming stale, so if you are unable to reproduce the issue the
    sooner you tell me the better so we can collect more logs.

    Anyway, fixing some/most of these bugs would go a long way
    towards improving my working experience with Netbeans. For the
    past couple of years I have felt that we should dedicate an
    entire release towards bug fixing (no new features) to make
    Netbeans more reliable and performant. It's still a good IDE but
    compared to Intellij there is no comparison (this was not always
    the case). I want to keep on using Netbeans, so I hope we can
    streamline this process.

    PS: It is absolutely vital that the Exception Reporter
    infrastructure be moved over to the new bug tracker. I can't
    imagine having to report all these issues by hand... The vast
    majority of bugs I run into on a daily basis are
    NullPointerExceptions, parsing errors, and such. In these cases,
    the Exception Reporter does a better job than I would collecting
    all the relevant files (and keystoke history) to help you
    reproduce the problem.

    PS2: If you want to save users even more time, try detecting if a
    bug is known before asking us to enter a description. Very often
    I see a report is fully fleshed out and all I need to log my vote
    ("I'm impacted by this bug"). Asking me to enter a description
    each time is annoying and discourages me from reporting bugs in
    the first place.

    Thanks,
    Gili


    On 2017-12-31 3:04 AM, Jan Lahoda wrote:
    Hi Gili,

    On Sun, Dec 31, 2017 at 7:28 AM, cowwoc <[email protected]
    <mailto:[email protected]>> wrote:

        Hi,

        Are there any plans to open up (migrate) the issue tracker
        for the broader apache community to tackle existing/old
        Netbeans bugs?

        I ask because I feel like the bandwidth for fixing Java
        Editor bugs is like sucking a milkshake through a straw:
        major bugs are being reported at an expoentially-growing
        rate and they are being fixed at a rate of 1-2 a week. The
        nightly builds are frankly barely usable anymore. I am
        specifically concerned about Maven + Java projects where I
        routinely get NullPointerExceptions and "slow action" errors
        (actions taking 13-20 seconds to complete on a seemingly
        random basis).


    Do you have links to the bugs reported about the problems you
    see? (Using the Apache tracker for new bugs would be strongly
    preferred.) Or are there some pull requests?

    Thanks,
        Jan


        This component needs more love. And soon. Can you please
        prioritize accordingly?

        Thank you,
        Gili

        (For context, I've been using Netbeans since 1999 so when I
        say things are unstable I've got a long track-record to
        judge by)


        ---------------------------------------------------------------------
        To unsubscribe, e-mail:
        [email protected]
        <mailto:[email protected]>
        For additional commands, e-mail:
        [email protected]
        <mailto:[email protected]>

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







--

Rgds.
*Dawn Raison*
Lemur Software Ltd.

E:[email protected]      W:http://www.lemur.co.uk
M: 07956 609 618        T: 01428 729 431
Reg: 3097160, England & Wales
Heldan House, Tower Close, Liphook, Hampshire. GU30 7AS

This email and any attached files are for the exclusive use of the addressee and may contain privileged and/or confidential information. If you receive this email in error you should not disclose the contents to any other person nor take copies but should delete it immediately. Lemur Software Ltd makes no warranty as to the accuracy or completeness of this email and accepts no liability for its contents or use. Any opinions expressed in this email are those of the author and do not necessarily reflect the opinions of Lemur Software Ltd.

Reply via email to