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

Closed (moved)
(moved)
Open
Created Aug 28, 2019 by teor@teor

sr: Check why some sr_disk_state fields need to be cleared

Split off #31240 (moved):

teor: When we add fields, how will we make sure we remember to clear them all?

nickm: We don't need to do so in general, the manager will take care of it for us. This is only necessary for derived fields, and fields for which the unit tests are expecting an unusual behavior, IIRC.

nickm: (I can dig deeper here; I forget the exact reason why this function is clearing these, but I think it is because of legacy cruft.)

teor: Yeah let's double-check what's going on here.

https://github.com/nmathewson/tor/pull/3#discussion_r317548828

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