Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #29364

Closed (moved)
(moved)
Open
Created Feb 07, 2019 by David Fifield@dcf

Tone down [WARN] log messages resulting from meek-client output

Since #28179 (moved), tor logs any output from managed proxies' stderr at the WARN level. So meek-client's log messages like

2019/02/07 08:12:22 listening on 127.0.0.1:39071

that formerly went into a black hole, now get logged by tor as

2/7/19, 08:12:22.657 [WARN] Managed proxy at './TorBrowser/Tor/PluggableTransports/meek-client' reported: 2019/02/07 08:12:22 listening on 127.0.0.1:39071

The only real problem here is one of user interface. Being logged at WARN level causes the ⚠️ to pop up in Tor Launcher, when this is not something that requires user attention at all.

May affect other transports.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking