You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Filtering the log data using "subsystem CONTAINS "me.chucker""
Timestamp Thread Type Activity PID TTL
2022-11-18 00:19:08.588877+0100 0x147f90 Info 0x0 8955 0 MyApp: [me.chucker.MyApp:] info
2022-11-18 00:19:08.588932+0100 0x147f90 Fault 0x290b3b 8955 0 MyApp: [me.chucker.MyApp:] critical
2022-11-18 00:19:08.588954+0100 0x147f90 Error 0x0 8955 0 MyApp: [me.chucker.MyApp:] error
2022-11-18 00:19:08.588967+0100 0x147f90 Default 0x0 8955 0 MyApp: [me.chucker.MyApp:] notice
2022-11-18 00:19:08.588978+0100 0x147f90 Info 0x0 8955 0 MyApp: [me.chucker.MyApp:] warning
Which is to say… it works as expected for types info and above, but not for debug, even though I explicitly ask log stream to show debug messages. Same if I go to the Console app and do Action → Include Debug Messages.
I know the --debug flag works because ignoring my current app, this:
(Maybe I'm missing a step where I need to tell
swift-log
not to swallow them?)Given the following code:
And a Terminal call to
log stream
:I get:
Which is to say… it works as expected for types info and above, but not for debug, even though I explicitly ask
log stream
to showdebug
messages. Same if I go to the Console app and do Action → Include Debug Messages.I know the
--debug
flag works because ignoring my current app, this:…will return nothing, whereas this:
…will return a veritable firehose (but nothing from my app).
The text was updated successfully, but these errors were encountered: