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

Closed (moved)
(moved)
Open
Created May 10, 2017 by Karsten Loesing@karsten

Decide whether to sanitize padding-counts lines

I found this message in CollecTor's logs today:

2017-05-10 06:09:07,711 WARN o.t.c.b.SanitizedBridgesWriter:1212 Unrecognized line 'padding-counts 2017-05-10 01:48:43 (86400 s) bin-size=10000 write-drop=10000 write-pad=10000 write-total=10000 read-drop=10000 read-pad=10000 read-total=70000 enabled-read-pad=0 enabled-read-total=0 enabled-write-pad=0 enabled-write-total=0 max-chanpad-timers=0'. Skipping.

We need to decide whether it's okay to keep these lines in sanitized bridge descriptors, and if not, how to sanitize them. I believe it's okay to keep them, but I'd like to get confirmation on that.

Note that we should make this decision soon, because we're currently not sanitizing descriptors containing these lines. That means those bridges cannot be found in Atlas and won't be included in any statistics.

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