Opened 12 years ago

Closed 12 years ago

#5910 closed (wontfix)

Signals are unnamed making logging non-informative

Reported by: smurf@… Owned by: nobody
Component: Core (Other) Version: master
Severity: Keywords:
Cc: smurf@… Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


When debugging, I frequently need to log signals. However, they're just opaque objects: figuring out *which* signal is logged is frequently very very annoying.

Therefore I propose this simple patch.

Attachments (1)

signals.patch (1.4 KB) - added by smurf@… 12 years ago.

Download all attachments as: .zip

Change History (4)

Changed 12 years ago by smurf@…

Attachment: signals.patch added

comment:1 Changed 12 years ago by anonymous

Cc: smurf@… added

comment:2 Changed 12 years ago by Simon G <dev@…>

Summary: [patch] Signals are unnamedSignals are unnamed making logging non-informative
Triage Stage: UnreviewedReady for checkin

comment:3 Changed 12 years ago by Jeremy Dunck

Resolution: wontfix
Status: newclosed

Quoting Malcolm on #4521, of which this is a dupe, "We're going to end up taking some variation on #4561 and that includes this functionality. So let's punt this exact patch and push the other one to completion."

Note: See TracTickets for help on using tickets.
Back to Top