Controller method to get our own descriptor

I'm wondering why this pythin snippet

def main():
  ControlPort = 9051
  ProcessName = 'tor'

  with Controller.from_port(port = ControlPort) as controller:
    controller.authenticate()
    #print " Tor version %s" % controller.get_version()
    try:
      desc = controller.get_microdescriptor()
      print " flags : %s" % desc.flags()
      print " measured bandwidth : %i" % desc.measured()
    except Exception as exc:
      print exc
      #pass

gives

Tor was unable to provide the descriptor for 'F1BE15429B3CE696D6807F4D4A58B1BFEC45C822'

Does this means that stems asks tor and tor doesn't know itself ?

changed milestone to %Tor: unspecified

added component::core tor/tor easy lorax milestone::Tor: unspecified points::1 priority::medium severity::normal sponsor::S-can status::new tor-control tor-relay type::enhancement version::tor 0.2.7 labels

Yup. The trouble is that tor only provides methods for 'give me the descriptor I've downloaded about relay x'. It doesn't offer a method to get the descriptor we published.

As such if we haven't received a descriptor about ourselves then this query fails. This is most often an issue for newly started relays since they won't be part of a consensus for up to an hour.

Imho it would be nice if tor provided controller methods for...

• give me my self-published server descriptor
• give me my self-published extra-info descriptor
• give me my self-published microdescriptor

This won't be possible for router status entries (the get_network_status() method), but for all the rest tor should be capable of telling us the descriptor we ourselves are publishing.

Sending this over to Nick for his thoughts.

Trac:
Summary: does tor knows itself ? to Controller method to get our own descriptor
Component: Stem to Tor
Type: task to enhancement

This is most often an issue... for up to an hour. FWIW, this tor-relay is up and running since 8 days (0.2.6.2-alpha)

I'd be fine to have all of those new methods provided.

notes: "give me my self-published microdescriptor" doesn't work -- microdescs aren't selfpublished.

We need to decide whether these items mean "give us the most recently published descriptor," "give me the descriptor we would publish, if we were to publish one right now," or what.

Trac:
Keywords: N/A deleted, lorax easy tor-relay added
Milestone: N/A to Tor: 0.2.???

"give me my self-published microdescriptor" doesn't work -- microdescs aren't selfpublished

Gotcha. Wasn't sure on that one.

We need to decide whether these items mean "give us the most recently published descriptor," "give me the descriptor we would publish, if we were to publish one right now," or what.

Good question. If we could have both via something like...

GETINFO desc/ours/current
GETINFO desc/ours/published

GETINFO extra-info/ours/current
GETINFO extra-info/ours/published

... that seems preferable.

These may be worth looking at for 0.2.7.

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.2.7.x-final

Trac:
Status: new to assigned
Owner: atagar to N/A

Marking more tickets as triaged-in for 0.2.7

Trac:
Keywords: lorax easy tor-relay deleted, lorax, tor-relay, easy, 027-triaged-1-in added

Trac:
Priority: minor to normal
Version: N/A to Tor: 0.2.7
Keywords: N/A deleted, SponsorS added
Points: N/A to small

Trac:
Milestone: Tor: 0.2.7.x-final to Tor: 0.2.8.x-final

Trac:
Keywords: N/A deleted, 028-triaged added

Bulk-replace SponsorS keyword with SponsorS sponsor field in Tor component.

Trac:
Sponsor: N/A to SponsorS
Keywords: SponsorS deleted, N/A added

These seem like features, or like other stuff unlikely to be possible this month. Bumping them to 0.2.9

Trac:
Milestone: Tor: 0.2.8.x-final to Tor: 0.2.9.x-final

Trac:
Severity: N/A to Normal
Sponsor: SponsorS to SponsorS-can
Reviewer: N/A to N/A

Trac:
Keywords: N/A deleted, tor-controller-extension added

Trac:
Points: small to 1

Put all unowned "assigned" tickets back into "new".

Trac:
Status: assigned to new

Trac:
Keywords: N/A deleted, isaremoved added
Milestone: Tor: 0.2.9.x-final to Tor: 0.2.???

Milestone renamed

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.3.???

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

Trac:
Milestone: Tor: 0.3.??? to Tor: unspecified
Keywords: N/A deleted, tor-03-unspecified-201612 added

Remove an old triaging keyword.

Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A added

Trac:
Keywords: N/A deleted, 027-triaged-in added

Trac:
Keywords: 027-triaged-in deleted, N/A added

Trac:
Keywords: 027-triaged-1-in deleted, N/A added

Trac:
Keywords: 028-triaged deleted, N/A added

Trac:
Keywords: isaremoved deleted, N/A added

Unify tor-controller-extension keyword to "tor-control".

Trac:
Keywords: tor-controller-extension deleted, tor-control added

changed time estimate to 8h

moved to tpo/core/tor#14164 (closed)