[tor-commits] [stem/master] Move NEWDESC sample events to alphabetic position

[atagar@xxxxxxxxxxxxxx]

commit 38190ab9cbedf9844022fe02f4385f1b129c5f52
Author: Sean Robinson <seankrobinson@xxxxxxxxx>
Date:   Fri Dec 14 16:15:53 2012 -0700

    Move NEWDESC sample events to alphabetic position
    
    Signed-off-by: Sean Robinson <seankrobinson@xxxxxxxxx>
---
 test/unit/response/events.py |   14 +++++++-------
 1 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/test/unit/response/events.py b/test/unit/response/events.py
index a632125..7fb39c6 100644
--- a/test/unit/response/events.py
+++ b/test/unit/response/events.py
@@ -181,6 +181,13 @@ s Fast Guard Running Stable Valid
 650 OK
 """
 
+# NEWDESC events. I've never actually seen multiple descriptors in an event,
+# but the spec allows for it.
+
+NEWDESC_SINGLE = "650 NEWDESC $B3FA3110CC6F42443F039220C134CBD2FC4F0493=Sakura"
+NEWDESC_MULTIPLE = "650 NEWDESC $BE938957B2CA5F804B3AFC2C1EE6673170CDBBF8=Moonshine \
+$B4BE08B22D4D2923EDC3970FD1B93D0448C6D8FF~Unnamed"
+
 # NS event from tor v0.2.1.30.
 
 NS_EVENT = """650+NS
@@ -288,13 +295,6 @@ STREAM_DNS_REQUEST = "650 STREAM 1113 NEW 0 www.google.com:0 \
 SOURCE_ADDR=127.0.0.1:15297 \
 PURPOSE=DNS_REQUEST"
 
-# NEWDESC events. I've never actually seen multiple descriptors in an event,
-# but the spec allows for it.
-
-NEWDESC_SINGLE = "650 NEWDESC $B3FA3110CC6F42443F039220C134CBD2FC4F0493=Sakura"
-NEWDESC_MULTIPLE = "650 NEWDESC $BE938957B2CA5F804B3AFC2C1EE6673170CDBBF8=Moonshine \
-$B4BE08B22D4D2923EDC3970FD1B93D0448C6D8FF~Unnamed"
-
 def _get_event(content):
   controller_event = mocking.get_message(content)
   stem.response.convert("EVENT", controller_event, arrived_at = 25)



_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits