Closed Bug 73920 Opened 24 years ago Closed 17 years ago

"null" appears in many NNTP log messages

Categories

(MailNews Core :: Networking: NNTP, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: bugzilla, Unassigned)

References

Details

Attachments

(2 files)

I'm not sure if it's important or not but anyways: there seems to be a lot of NNTP log comments that contain "null". Like: 0[346138]: m_messageID = (null) 0[346138]: group = (null) 0[346138]: commandSpecificData = (null) 0[346138]: Receiving: (null)
QA Contact: esther → stephend
I don't think this is a bug?
*** This bug has been marked as a duplicate of 57659 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
*** Bug 57659 has been marked as a duplicate of this bug. ***
Henrik, when you're ready, go ahead and verify. thanks.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
So, re-opening this bug. Sorry for the mess.
As I said some 7 months earlier, I don't think this is a bug. :) We are showing the actual value, which happens to be null in this case. If this causes you no harm, it's a feature and no bug. Marking as worksforme. Gemal, please verify / comment.
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → WORKSFORME
Stephen: What was the Outlook Express log to show? The reason why I logged this bug, was just I didn't understand why some log comments was showing "null". "null" normally means something is detected wrong, etc..
Null need not mean that something is wrong, it's just a 'techie' word for "nothing" or "empty".
Gemal, can you give us a testcase in which 'null' as a value appears? IE, does it happen on public servers like news.mozilla.org? The log from Outlook Express was just meant to show (since I can't figure out how to log what 4.x does) that 'null' isn't a common value for news (in this simple posting and reading testcase that I came up with).
Leaving open, until I hear from Seth on the expected behavior. It may turn out that Outlook Express doesn't log null values.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
The "null" value not being present in the OE log, is just because we log different thing. I just wanna be sure that stuff like: 0[3441b0]: (31e5138) m_messageID = (null) 0[3441b0]: (31e5138) group = (null) 0[3441b0]: (31e5138) commandSpecificData = (null) doesn't mean that Mozilla is either doing something wrong or detecting some server response wrong. We have a lot of NNTP bugs and these null's could perhaps be a cause. Just want to be 110% sure...
Product: MailNews → Core
sorry for the spam. making bugzilla reflect reality as I'm not working on these bugs. filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
Status: REOPENED → NEW
A trip though the NNTP parser code reveals that not only are the specified null values not problematic, they are necessary to trigger the newsrc information. Are there any other null values not generated by ParseURL or LoadURL?
QA Contact: stephend → networking.news
RESO INVALID. This is not a problem.
Status: NEW → RESOLVED
Closed: 24 years ago17 years ago
Resolution: --- → INVALID
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: