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
  • #25471

Closed (moved)
(moved)
Open
Created Mar 13, 2018 by David Fifield@dcf

"log to pt_state directory" option for snowflake-client

From #25449 (moved):

[comment:3:ticket:25449 dcf]:

My removal of default logging in 12922a232b was arguably rash: while obviously eventually we would have to stop logging by default, requiring a -log option with a path prevents writing to a log file that's inside the pt_state directory, which, in sandbox situations, may be the only place the transport plugin is allowed to write. obfs4proxy just has a boolean option -enableLogging that doesn't take a path, unconditionally writing to pt_state/obfs4proxy.log. Perhaps something like that would be better, even if it's less convenient for development.

[comment:4:ticket:25449 arlolra]:

Maybe just add another flag, -logToStateDir or the like

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