Opened 8 years ago

Closed 8 years ago

#9898 closed Bug Report - General (fixed)

Calling appendChild() messages

Reported by: Ian Dall <ian@…> Owned by:
Priority: minor Milestone: 0.25
Component: MythTV - General Version: Unspecified
Severity: low Keywords:
Cc: Ticket locked: no

Description

Version: v0.25pre-2563-ga41e965

When starting up a backend I get a bunch of error messages to the console:

    Calling appendChild() on a null node does nothing.

Nothing appears in the log file (indeed these messages seem to come out before the log file is even opened). As far as I can tell, nothing bad happens despite the ominous tone.

Two odd things:

  1. I only see this on two out of three backends (a master and one slave).
  2. A grep of the entire tree only finds the string appendChild inside some javascript. So maybe this comes from a javascript library. We don't run server side javascript. Do we?

Change History (3)

comment:1 Changed 8 years ago by robertm

Ian,

Aside from being an indication of imperfect code, there appears to be no actual consequence here. It's really, really hard to devote developer time to tracking down real bugs, let alone ones which aren't necessarily bugs at all. I am very, very tempted to close this as invalid since you yourself admit you're not seeing any sort of actual problem.

I'll leave it open for now, and maybe even investigate it myself, but please think carefully in the future about opening tickets on items where you can't articulate an actual impact to the operation of MythTV (at least, not without submitting patches). We're stretched awfully thin as it is.

Also, please see the ticket howto ref: priorities and severities. These are for developer use only.

comment:2 Changed 8 years ago by Ian Dall <ian@…>

Yes, fair enough. I understand if it is not worth fixing. The argument for reporting (and my thinking in doing so) is that:

  1. it is (relatively) new
  2. someone familiar with that bit of code might recognise it as significant and
  3. if not, and it is declared harmless, then there is a record of that, which could stop other people wasting time on it.

Is there a "Won't Fix" tag? Which sounds like it would be appropriate in these circumstances.

comment:3 Changed 8 years ago by Github

Milestone: unknown0.25
Resolution: fixed
Status: newclosed

libmythupnp: Squash a runtime Qt warning.

Fixes #9898

Branch: master Changeset: 27ef93fe30b7e35202fa58ed620742e897c5c74e

Note: See TracTickets for help on using tickets.