BreakPoint

cancel
Showing results for 
Search instead for 
Did you mean: 

Bug thread discussion

Call it serendipity, call it what you will... on my way to lunch today, I was thinking about "Formalizing Issue Tracking" as a new Idea for the Exchange. Despite tepid response here, I think I want to add a new Idea. Thanks, Ben, for bumping this post, it's a good history lesson for the topic.

0 Kudos
Message 28 of 44
(11,102 Views)

@JackDunaway wrote:

[...] ... on my way to lunch today, I was thinking about [...] a new Idea for the Exchange.


Ah ha! So that's your secret. Smiley Very Happy Smiley Tongue

Richard






0 Kudos
Message 29 of 44
(11,093 Views)

Dbaechtel,

 

Please read the rules that are posted in the first message of the thread.

 

This thread is not to report bugs.  Create a new message thread in the appropriate board (usually LabVIEW) where you bring up that there is a possibility of a bug.  Give it a little bit of time for someone to reply and say they agree with you that you have a bug.  (Many times people claim a bug when it is really user error.)

 

At that time, then a message can be posted in this board with a short description of the bug and link to the actual thread where the bug is discussed.

 

I am going to ask the moderator to have your 3 messages moved to the LabVIEW board.

Message 20 of 44
(11,390 Views)

 


@Ravens Fan wrote:

Dbaechtel,

 

Please read the rules that are posted in the first message of the thread.

 

This thread is not to report bugs. 


I think Ravens Fan meant to say here that these threads are to report bugs (as later indicated in his post), not speculations on behavior (which may or may not be a bug), or complaints about the way LabVIEW works.

 

0 Kudos
Message 21 of 44
(11,308 Views)

Sometimes it is difficult to tell the difference between bad (unwanted) behavior and a BUG.

 

I think that NI should be less defensive and take great value in all of the feedback they are given.

 

0 Kudos
Message 22 of 44
(11,283 Views)

 


@smercurio_fc wrote:

 


@Ravens Fan wrote:

Dbaechtel,

 

Please read the rules that are posted in the first message of the thread.

 

This thread is not to report bugs. 


I think Ravens Fan meant to say here that these threads are to report bugs (as later indicated in his post), not speculations on behavior (which may or may not be a bug), or complaints about the way LabVIEW works.

 


Yes, I get the point (if it was about me). But unless otherwise proven, how can one say if something is a bug or not? And if something is a proven bug, why the discussion on it would continue at all? 

And I agree, in this thread there shouldn't be any discussion about the bugs, just indication of the thread.

 

Vaibhav
0 Kudos
Message 23 of 44
(11,214 Views)

 


@dbaechtel wrote:

Sometimes it is difficult to tell the difference between bad (unwanted) behavior and a BUG.


That's why there's the regular boards to discuss this, and not these threads.

 

 


I think that NI should be less defensive and take great value in all of the feedback they are given.


Where did you get the impression that NI is being defensive? And since when did we start working for NI? These bug threads were NOT started by NI, but by regular forum users. We are volunteers, and we're perfectly happy with pointing out bugs. It fixes issues and improves the software. As noted in the rules for this thread, these threads are not intended to discuss bugs. Please abide by the rules.

 

 

Message 24 of 44
(11,211 Views)

 


@Vaibhav wrote:

@smercurio_fc wrote:

@Ravens Fan wrote:

Dbaechtel,

 

Please read the rules that are posted in the first message of the thread.

 

This thread is not to report bugs. 


I think Ravens Fan meant to say here that these threads are to report bugs (as later indicated in his post), not speculations on behavior (which may or may not be a bug), or complaints about the way LabVIEW works.

 


Yes, I get the point (if it was about me).


It was not about you. Ravens Fan was talking about dbaechtel's three posts. And I agree with Ravens Fan, regardless of whether the items mentioned are bugs or not.

 

Message 25 of 44
(11,210 Views)

Thanks Smercurio.

 

Dbaechtel,

 

I'm not commenting on whether what you posted are bugs or not.  Or whether you are complaining or not.  I'm just saying please follow the rules of the thread that are posted at the beginning of every monthly thread.

 

This thread is a compilation of links to threads where bugs have been discovered and discussed.  This makes it easy for us users to browse this thread to see what problems have recently been discovered to determine whether they might affect us or not.  It gives a place where NI can look to be sure that they have created a CAR# so they can investigate any problems that people have discovered and general consensus is that it is a bug.  NI does browse the forums and are looking for potential bug complaints, but a repository thread like this should guarantee the threads don't fall through the cracks.

 

Why should only links to bug threads be listed here with a quick description rather than actually reporting the bug here?  First, not everything that someone thinks is a bug actually is.  It may be user error and thus a bug in their program rather than a bug in LabVIEW.  It may be undesirable behavior, but well documented.  If everything that someone might complain about that wasn't actually a bug was listed here, this thread would be filled with a lot of noise.

 

Second, in finding a bug, usually you need several people discussing it to figure out if it is a bug.  If you have a problem in 2009, but someone can test it in LV 8.6 and confirms it behaved properly there.  It is probably a bug.  It can confirm that an issue as existed for several versions undiscovered, now the extent of the bug has been determined.  Perhaps it is an installation issue on one person's machine that no one else seems to have a problem with.  Perhaps there is a workaround someone discovered that you can use so that it isn't a showstopper for your work.  That's a good thing to list in a thread that discusses a bug.  Every month there are a few to a dozen or so bugs that get listed in the monthly bug thread.  If this was the only place they were discussed, then the different conversations related to the different bugs would step all over each other in this thread and no one would be able to follow anything.  Again, a bunch of noise as the list of a dozen bugs becomes a thread with 200 messages when their are about 10-15 messages related to the conversation of each bug.

 

So please, when you think you have a bug, create a new thread in the appropriate forum.  Let it get discussed there.  Once there is a consensus that it is a bug, (and many times by then an NI person has stepped it, agreed, and gives a CAR# that documents it in their database), you or someone else can step into this thread and post a simple message with a quick description of the bug and a link to the real thread where the message is discussed.  These threads have been setup this way for years, work well, and we are just asking you to continue to follow the same rules.

Message 26 of 44
(11,198 Views)

You all are certainly having alot of discussion about not having any discussions in this thread.

 

Let's not worry so much about the rules and having discussions about not having discussions and get on with the work of identifying and FIXING Bugs in LV.

 

 

0 Kudos
Message 30 of 44
(11,089 Views)