[atlas] CLI

On Wed, May 30, 2018 at 11:13:11AM +0430,
 Milad Afshari <afshar.milad89 at gmail.com> wrote 
 a message of 97 lines which said:

> Exception in thread Thread-1 (most likely raised during interpreter shutdown):
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
>   File "/usr/lib/python2.7/dist-packages/socketIO_client/heartbeats.py", line 27, in run
>   File "/usr/lib/python2.7/dist-packages/socketIO_client/__init__.py", line 192, in _ping
>   File "/usr/lib/python2.7/dist-packages/socketIO_client/transports.py", line 159, in send_packet
> <type 'exceptions.TypeError'>: 'NoneType' object is not callable
> Unhandled exception in thread started by 
> sys.excepthook is missing
> lost sys.stderr

It seems a bug in the tool, to me, may be triggered by some MiTM TLS
interceptor. In the case it is specific to the streaming interface,
you may try a tool which does not use this interface (weaknesses can
be strengths :-)
<https://labs.ripe.net/Members/stephane_bortzmeyer/creating-ripe-atlas-one-off-measurements-with-blaeu>:

% blaeu-reach --probes 33717 9.9.9.9
1 probes reported
Test #13596250 done at 2018-05-30T06:46:37Z
Tests: 3 successful tests (100.0 %), 0 errors (0.0 %), 0 timeouts (0.0 %), average RTT: 130 ms

Or with your measurement (which indeed worked):

% blaeu-reach --measurement-ID 13595420 --probes 33717 9.9.9.9 
Warning: --probes ignored since we use probes from a previous measurement
Test #13595420 done at 2018-05-30T06:29:04Z
Tests: 3 successful tests (100.0 %), 0 errors (0.0 %), 0 timeouts (0.0 %), average RTT: 130 ms

If you have time to test, tell me if it works better.