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

Closed (moved)
(moved)
Open
Created Feb 19, 2020 by Nick Mathewson@nickm🍬

Do we actually need the orconn_ext_or_id_map?

So apparently we have this structure, orconn_ext_or_id_map, where we map from ext_orport identifiers to the corresponding orconn objects ... but nothing in our code (outside of the unit tests) actually looks anything up in this map.

I can't remember -- is this a feature that we were planning to do something with if transports needed it in the future? Or is this just dead code?

Found while working on #33368 (moved).

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