Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #25046

Closed
Open
Opened Jan 27, 2018 by Tom Ritter@tom

reveal_count incorrect in stem

I am stem master, commit b2c8810dc94b0e2e62c0e482158de3d33504a709 Sat Jan 20 17:53:41 2018 -0800

» python
Python 2.7.10 (default, Jul 15 2017, 17:16:57)
[GCC 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.31)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import stem.descriptor.remote
>>>
>>> downloader = stem.descriptor.remote.DescriptorDownloader(
...     timeout = 60,
...     fall_back_to_authority = False,
...     document_handler = stem.descriptor.DocumentHandler.DOCUMENT,
... )
>>> query = downloader.query('/tor/status-vote/current/consensus', default_params = False)
>>> d = query.run()
>>> d
[<stem.descriptor.networkstatus.NetworkStatusDocumentV3 object at 0x10aa8ea10>]
>>> c = d[0]
>>> c.shared_randomness_current_reveal_count
>>> c.shared_randomness_previous_reveal_count
>>> c.shared_randomness_current_value
u'vLbCqI2m02UXzOUYtSMPWxC/QUSXSw0mrOBNyBCGtcE='
>>> c.shared_randomness_previous_value
u'2xFM9tuS7c84CfE2OIURwJjh/XYop/tQoQD70DBBJNA='

Previously these values... had values. But now it appears they're not being populated? The documentation is a little fuzzy, but can you confirm they are intentionally not being populated anymore, even though they appear in the consensus?

shared-rand-previous-value 9 2xFM9tuS7c84CfE2OIURwJjh/XYop/tQoQD70DBBJNA=
shared-rand-current-value 9 vLbCqI2m02UXzOUYtSMPWxC/QUSXSw0mrOBNyBCGtcE=
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#25046