Successful Installation of poliastro but the tests failed

I've successfully installed poliastro on my MacBook Pro running Mac OS X ver. 10.10.3. Now the python environment is Anaconda for Python 2.7.  When run the test, python -c "import poliastro; poliastro.test()", I get errors which point to stumpff.py. A copy of my installation log and test output is given below.
Please advise.
users-MacBook-Pro:poliastro user$ python setup.py install
running install
running bdist_egg
running egg_info
creating poliastro.egg-info
writing poliastro.egg-info/PKG-INFO
writing top-level names to poliastro.egg-info/top_level.txt
writing dependency_links to poliastro.egg-info/dependency_links.txt
writing poliastro.egg-info/PKG-INFO
writing top-level names to poliastro.egg-info/top_level.txt
writing dependency_links to poliastro.egg-info/dependency_links.txt
writing manifest file 'poliastro.egg-info/SOURCES.txt'
reading manifest file 'poliastro.egg-info/SOURCES.txt'
writing manifest file 'poliastro.egg-info/SOURCES.txt'
installing library code to build/bdist.macosx-10.5-x86_64/egg
running install_lib
running build_py
creating build
creating build/lib
creating build/lib/poliastro
copying poliastro/__init__.py -> build/lib/poliastro
copying poliastro/bodies.py -> build/lib/poliastro
copying poliastro/examples.py -> build/lib/poliastro
copying poliastro/iod.py -> build/lib/poliastro
copying poliastro/maneuver.py -> build/lib/poliastro
copying poliastro/plotting.py -> build/lib/poliastro
copying poliastro/stumpff.py -> build/lib/poliastro
copying poliastro/util.py -> build/lib/poliastro
creating build/lib/poliastro/twobody
copying poliastro/twobody/__init__.py -> build/lib/poliastro/twobody
copying poliastro/twobody/conversion.py -> build/lib/poliastro/twobody
copying poliastro/twobody/propagation.py -> build/lib/poliastro/twobody
copying poliastro/twobody/state.py -> build/lib/poliastro/twobody
creating build/lib/poliastro/tests
copying poliastro/tests/__init__.py -> build/lib/poliastro/tests
copying poliastro/tests/test_bodies.py -> build/lib/poliastro/tests
copying poliastro/tests/test_examples.py -> build/lib/poliastro/tests
copying poliastro/tests/test_iod.py -> build/lib/poliastro/tests
copying poliastro/tests/test_maneuver.py -> build/lib/poliastro/tests
copying poliastro/tests/test_plotting.py -> build/lib/poliastro/tests
copying poliastro/tests/test_twobody.py -> build/lib/poliastro/tests
copying poliastro/tests/test_util.py -> build/lib/poliastro/tests
creating build/bdist.macosx-10.5-x86_64
creating build/bdist.macosx-10.5-x86_64/egg
creating build/bdist.macosx-10.5-x86_64/egg/poliastro
copying build/lib/poliastro/__init__.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro
copying build/lib/poliastro/bodies.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro
copying build/lib/poliastro/examples.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro
copying build/lib/poliastro/iod.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro
copying build/lib/poliastro/maneuver.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro
copying build/lib/poliastro/plotting.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro
copying build/lib/poliastro/stumpff.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro
creating build/bdist.macosx-10.5-x86_64/egg/poliastro/tests
copying build/lib/poliastro/tests/__init__.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/tests
copying build/lib/poliastro/tests/test_bodies.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/tests
copying build/lib/poliastro/tests/test_examples.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/tests
copying build/lib/poliastro/tests/test_iod.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/tests
copying build/lib/poliastro/tests/test_maneuver.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/tests
copying build/lib/poliastro/tests/test_plotting.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/tests
copying build/lib/poliastro/tests/test_twobody.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/tests
copying build/lib/poliastro/tests/test_util.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/tests
creating build/bdist.macosx-10.5-x86_64/egg/poliastro/twobody
copying build/lib/poliastro/twobody/__init__.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/twobody
copying build/lib/poliastro/twobody/conversion.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/twobody
copying build/lib/poliastro/twobody/propagation.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/twobody
copying build/lib/poliastro/twobody/state.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/twobody
copying build/lib/poliastro/util.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/__init__.py to __init__.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/bodies.py to bodies.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/examples.py to examples.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/iod.py to iod.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/maneuver.py to maneuver.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/plotting.py to plotting.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/stumpff.py to stumpff.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/tests/__init__.py to __init__.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/tests/test_bodies.py to test_bodies.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/tests/test_examples.py to test_examples.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/tests/test_iod.py to test_iod.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/tests/test_maneuver.py to test_maneuver.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/tests/test_plotting.py to test_plotting.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/tests/test_twobody.py to test_twobody.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/tests/test_util.py to test_util.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/twobody/__init__.py to __init__.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/twobody/conversion.py to conversion.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/twobody/propagation.py to propagation.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/twobody/state.py to state.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/util.py to util.pyc
creating build/bdist.macosx-10.5-x86_64/egg/EGG-INFO
copying poliastro.egg-info/PKG-INFO -> build/bdist.macosx-10.5-x86_64/egg/EGG-INFO
copying poliastro.egg-info/SOURCES.txt -> build/bdist.macosx-10.5-x86_64/egg/EGG-INFO
copying poliastro.egg-info/dependency_links.txt -> build/bdist.macosx-10.5-x86_64/egg/EGG-INFO
copying poliastro.egg-info/top_level.txt -> build/bdist.macosx-10.5-x86_64/egg/EGG-INFO
zip_safe flag not set; analyzing archive contents...
poliastro.__init__: module references __file__
creating dist
creating 'dist/poliastro-0.3.0_dev-py2.7.egg' and adding 'build/bdist.macosx-10.5-x86_64/egg' to it
removing 'build/bdist.macosx-10.5-x86_64/egg' (and everything under it)
Processing poliastro-0.3.0_dev-py2.7.egg
creating /Users/user/anaconda/lib/python2.7/site-packages/poliastro-0.3.0_dev-py2.7.egg
Extracting poliastro-0.3.0_dev-py2.7.egg to /Users/user/anaconda/lib/python2.7/site-packages
Adding poliastro 0.3.0-dev to easy-install.pth file
error: [Errno 13] Permission denied: '/Users/user/anaconda/lib/python2.7/site-packages/easy-install.pth'
users-MacBook-Pro:poliastro user$ sudo python setup.py install
Password:
running install
running bdist_egg
running egg_info
writing poliastro.egg-info/PKG-INFO
writing top-level names to poliastro.egg-info/top_level.txt
writing dependency_links to poliastro.egg-info/dependency_links.txt
writing poliastro.egg-info/PKG-INFO
writing top-level names to poliastro.egg-info/top_level.txt
writing dependency_links to poliastro.egg-info/dependency_links.txt
reading manifest file 'poliastro.egg-info/SOURCES.txt'
writing manifest file 'poliastro.egg-info/SOURCES.txt'
installing library code to build/bdist.macosx-10.5-x86_64/egg
running install_lib
running build_py
creating build/bdist.macosx-10.5-x86_64/egg
creating build/bdist.macosx-10.5-x86_64/egg/poliastro
copying build/lib/poliastro/__init__.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro
copying build/lib/poliastro/bodies.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro
copying build/lib/poliastro/examples.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro
copying build/lib/poliastro/iod.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro
copying build/lib/poliastro/maneuver.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro
copying build/lib/poliastro/plotting.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro
copying build/lib/poliastro/stumpff.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro
creating build/bdist.macosx-10.5-x86_64/egg/poliastro/tests
copying build/lib/poliastro/tests/__init__.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/tests
copying build/lib/poliastro/tests/test_bodies.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/tests
copying build/lib/poliastro/tests/test_examples.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/tests
copying build/lib/poliastro/tests/test_iod.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/tests
copying build/lib/poliastro/tests/test_maneuver.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/tests
copying build/lib/poliastro/tests/test_plotting.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/tests
copying build/lib/poliastro/tests/test_twobody.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/tests
copying build/lib/poliastro/tests/test_util.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/tests
creating build/bdist.macosx-10.5-x86_64/egg/poliastro/twobody
copying build/lib/poliastro/twobody/__init__.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/twobody
copying build/lib/poliastro/twobody/conversion.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/twobody
copying build/lib/poliastro/twobody/propagation.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/twobody
copying build/lib/poliastro/twobody/state.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro/twobody
copying build/lib/poliastro/util.py -> build/bdist.macosx-10.5-x86_64/egg/poliastro
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/__init__.py to __init__.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/bodies.py to bodies.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/examples.py to examples.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/iod.py to iod.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/maneuver.py to maneuver.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/plotting.py to plotting.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/stumpff.py to stumpff.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/tests/__init__.py to __init__.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/tests/test_bodies.py to test_bodies.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/tests/test_examples.py to test_examples.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/tests/test_iod.py to test_iod.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/tests/test_maneuver.py to test_maneuver.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/tests/test_plotting.py to test_plotting.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/tests/test_twobody.py to test_twobody.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/tests/test_util.py to test_util.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/twobody/__init__.py to __init__.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/twobody/conversion.py to conversion.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/twobody/propagation.py to propagation.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/twobody/state.py to state.pyc
byte-compiling build/bdist.macosx-10.5-x86_64/egg/poliastro/util.py to util.pyc
creating build/bdist.macosx-10.5-x86_64/egg/EGG-INFO
copying poliastro.egg-info/PKG-INFO -> build/bdist.macosx-10.5-x86_64/egg/EGG-INFO
copying poliastro.egg-info/SOURCES.txt -> build/bdist.macosx-10.5-x86_64/egg/EGG-INFO
copying poliastro.egg-info/dependency_links.txt -> build/bdist.macosx-10.5-x86_64/egg/EGG-INFO
copying poliastro.egg-info/top_level.txt -> build/bdist.macosx-10.5-x86_64/egg/EGG-INFO
zip_safe flag not set; analyzing archive contents...
poliastro.__init__: module references __file__
creating 'dist/poliastro-0.3.0_dev-py2.7.egg' and adding 'build/bdist.macosx-10.5-x86_64/egg' to it
removing 'build/bdist.macosx-10.5-x86_64/egg' (and everything under it)
Processing poliastro-0.3.0_dev-py2.7.egg
removing '/Users/user/anaconda/lib/python2.7/site-packages/poliastro-0.3.0_dev-py2.7.egg' (and everything under it)
creating /Users/user/anaconda/lib/python2.7/site-packages/poliastro-0.3.0_dev-py2.7.egg
Extracting poliastro-0.3.0_dev-py2.7.egg to /Users/user/anaconda/lib/python2.7/site-packages
Adding poliastro 0.3.0-dev to easy-install.pth file

Installed /Users/user/anaconda/lib/python2.7/site-packages/poliastro-0.3.0_dev-py2.7.egg
Processing dependencies for poliastro==0.3.0-dev
Finished processing dependencies for poliastro==0.3.0-dev
users-MacBook-Pro:poliastro user$ python -c "import poliastro; poliastro.test()"
=================================================================== test session starts ===================================================================
platform darwin -- Python 2.7.9 -- py-1.4.26 -- pytest-2.6.4
collected 7 items / 5 errors

poliastro/tests/test_bodies.py ....
poliastro/tests/test_util.py ...

========================================================================= ERRORS ==========================================================================
____________________________________________________ ERROR collecting poliastro/tests/test_examples.py ____________________________________________________
poliastro/tests/test_examples.py:4: in <module>
    from poliastro import examples
poliastro/examples.py:10: in <module>
    from poliastro.twobody import State
poliastro/twobody/__init__.py:3: in <module>
    from poliastro.twobody.state import State
poliastro/twobody/state.py:16: in <module>
    from poliastro.twobody.propagation import kepler
poliastro/twobody/propagation.py:10: in <module>
    from poliastro.stumpff import c2, c3
poliastro/stumpff.py:10: in <module>
    @numba.jit('f8(f8)', nopython=True)
../anaconda/lib/python2.7/site-packages/numba/decorators.py:171: in wrapper
    disp.compile(sig)
../anaconda/lib/python2.7/site-packages/numba/dispatcher.py:277: in compile
    flags=flags, locals=self.locals)
../anaconda/lib/python2.7/site-packages/numba/compiler.py:547: in compile_extra
    return pipeline.compile_extra(func)
../anaconda/lib/python2.7/site-packages/numba/compiler.py:293: in compile_extra
    return self.compile_bytecode(bc, func_attr=self.func_attr)
../anaconda/lib/python2.7/site-packages/numba/compiler.py:301: in compile_bytecode
    return self._compile_bytecode()
../anaconda/lib/python2.7/site-packages/numba/compiler.py:534: in _compile_bytecode
    return pm.run(self.status)
../anaconda/lib/python2.7/site-packages/numba/compiler.py:191: in run
    raise patched_exception
E   TypingError: Failed at nopython (nopython frontend)
E   Untyped global name 'gamma'
E   File "poliastro/stumpff.py", line 19
______________________________________________________ ERROR collecting poliastro/tests/test_iod.py _______________________________________________________
poliastro/tests/test_iod.py:8: in <module>
    from poliastro.iod import lambert
poliastro/iod.py:9: in <module>
    from poliastro.stumpff import c2, c3
poliastro/stumpff.py:10: in <module>
    @numba.jit('f8(f8)', nopython=True)
../anaconda/lib/python2.7/site-packages/numba/decorators.py:171: in wrapper
    disp.compile(sig)
../anaconda/lib/python2.7/site-packages/numba/dispatcher.py:277: in compile
    flags=flags, locals=self.locals)
../anaconda/lib/python2.7/site-packages/numba/compiler.py:547: in compile_extra
    return pipeline.compile_extra(func)
../anaconda/lib/python2.7/site-packages/numba/compiler.py:293: in compile_extra
    return self.compile_bytecode(bc, func_attr=self.func_attr)
../anaconda/lib/python2.7/site-packages/numba/compiler.py:301: in compile_bytecode
    return self._compile_bytecode()
../anaconda/lib/python2.7/site-packages/numba/compiler.py:534: in _compile_bytecode
    return pm.run(self.status)
../anaconda/lib/python2.7/site-packages/numba/compiler.py:191: in run
    raise patched_exception
E   TypingError: Failed at nopython (nopython frontend)
E   Untyped global name 'gamma'
E   File "poliastro/stumpff.py", line 19
____________________________________________________ ERROR collecting poliastro/tests/test_maneuver.py ____________________________________________________
poliastro/tests/test_maneuver.py:11: in <module>
    from poliastro.twobody import State
poliastro/twobody/__init__.py:3: in <module>
    from poliastro.twobody.state import State
poliastro/twobody/state.py:16: in <module>
    from poliastro.twobody.propagation import kepler
poliastro/twobody/propagation.py:10: in <module>
    from poliastro.stumpff import c2, c3
poliastro/stumpff.py:10: in <module>
    @numba.jit('f8(f8)', nopython=True)
../anaconda/lib/python2.7/site-packages/numba/decorators.py:171: in wrapper
    disp.compile(sig)
../anaconda/lib/python2.7/site-packages/numba/dispatcher.py:277: in compile
    flags=flags, locals=self.locals)
../anaconda/lib/python2.7/site-packages/numba/compiler.py:547: in compile_extra
    return pipeline.compile_extra(func)
../anaconda/lib/python2.7/site-packages/numba/compiler.py:293: in compile_extra
    return self.compile_bytecode(bc, func_attr=self.func_attr)
../anaconda/lib/python2.7/site-packages/numba/compiler.py:301: in compile_bytecode
    return self._compile_bytecode()
../anaconda/lib/python2.7/site-packages/numba/compiler.py:534: in _compile_bytecode
    return pm.run(self.status)
../anaconda/lib/python2.7/site-packages/numba/compiler.py:191: in run
    raise patched_exception
E   TypingError: Failed at nopython (nopython frontend)
E   Untyped global name 'gamma'
E   File "poliastro/stumpff.py", line 19
____________________________________________________ ERROR collecting poliastro/tests/test_plotting.py ____________________________________________________
poliastro/tests/test_plotting.py:9: in <module>
    from poliastro import plotting
poliastro/plotting.py:13: in <module>
    from poliastro.twobody.conversion import rv_pqw
poliastro/twobody/__init__.py:3: in <module>
    from poliastro.twobody.state import State
poliastro/twobody/state.py:16: in <module>
    from poliastro.twobody.propagation import kepler
poliastro/twobody/propagation.py:10: in <module>
    from poliastro.stumpff import c2, c3
poliastro/stumpff.py:10: in <module>
    @numba.jit('f8(f8)', nopython=True)
../anaconda/lib/python2.7/site-packages/numba/decorators.py:171: in wrapper
    disp.compile(sig)
../anaconda/lib/python2.7/site-packages/numba/dispatcher.py:277: in compile
    flags=flags, locals=self.locals)
../anaconda/lib/python2.7/site-packages/numba/compiler.py:547: in compile_extra
    return pipeline.compile_extra(func)
../anaconda/lib/python2.7/site-packages/numba/compiler.py:293: in compile_extra
    return self.compile_bytecode(bc, func_attr=self.func_attr)
../anaconda/lib/python2.7/site-packages/numba/compiler.py:301: in compile_bytecode
    return self._compile_bytecode()
../anaconda/lib/python2.7/site-packages/numba/compiler.py:534: in _compile_bytecode
    return pm.run(self.status)
../anaconda/lib/python2.7/site-packages/numba/compiler.py:191: in run
    raise patched_exception
E   TypingError: Failed at nopython (nopython frontend)
E   Untyped global name 'gamma'
E   File "poliastro/stumpff.py", line 19
____________________________________________________ ERROR collecting poliastro/tests/test_twobody.py _____________________________________________________
poliastro/tests/test_twobody.py:10: in <module>
    from poliastro.twobody import State
poliastro/twobody/__init__.py:3: in <module>
    from poliastro.twobody.state import State
poliastro/twobody/state.py:16: in <module>
    from poliastro.twobody.propagation import kepler
poliastro/twobody/propagation.py:10: in <module>
    from poliastro.stumpff import c2, c3
poliastro/stumpff.py:10: in <module>
    @numba.jit('f8(f8)', nopython=True)
../anaconda/lib/python2.7/site-packages/numba/decorators.py:171: in wrapper
    disp.compile(sig)
../anaconda/lib/python2.7/site-packages/numba/dispatcher.py:277: in compile
    flags=flags, locals=self.locals)
../anaconda/lib/python2.7/site-packages/numba/compiler.py:547: in compile_extra
    return pipeline.compile_extra(func)
../anaconda/lib/python2.7/site-packages/numba/compiler.py:293: in compile_extra
    return self.compile_bytecode(bc, func_attr=self.func_attr)
../anaconda/lib/python2.7/site-packages/numba/compiler.py:301: in compile_bytecode
    return self._compile_bytecode()
../anaconda/lib/python2.7/site-packages/numba/compiler.py:534: in _compile_bytecode
    return pm.run(self.status)
../anaconda/lib/python2.7/site-packages/numba/compiler.py:191: in run
    raise patched_exception
E   TypingError: Failed at nopython (nopython frontend)
E   Untyped global name 'gamma'
E   File "poliastro/stumpff.py", line 19
=========================================================== 7 passed, 5 error in 26.22 seconds ============================================================
users-MacBook-Pro:poliastro user$

I uninstalled the version of poliastro I installed using Git and reinstalled using pip. The bottom line is 6 tests failed and 27 passed. What am I doing wrong? The output from the uninstall, the reinstall and the test are below.
Please advise.
users-MacBook-Pro:~ user$ sudo pip uninstall poliastro
Password:
The directory '/Users/user/Library/Logs/pip' or its parent directory is not owned by the current user and the debug log has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
The directory '/Users/user/Library/Caches/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
The directory '/Users/user/Library/Caches/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
Uninstalling poliastro-0.3.0.dev0:
/Users/user/anaconda/lib/python2.7/site-packages/poliastro-0.3.0_dev-py2.7.egg
Proceed (y/n)? y
Successfully uninstalled poliastro-0.3.0.dev0
users-MacBook-Pro:~ user$ pip install poliastro
Collecting poliastro
Downloading poliastro-0.2.0.tar.gz (84kB)
100% |████████████████████████████████| 86kB 1.3MB/s
Installing collected packages: poliastro
Running setup.py install for poliastro
Successfully installed poliastro-0.2.0
users-MacBook-Pro:~ user$ python -c "import poliastro; poliastro.test()"
==================================================================== test session starts ====================================================================
platform darwin -- Python 2.7.9 -- py-1.4.26 -- pytest-2.6.4
collected 32 items
anaconda/lib/python2.7/site-packages/poliastro/tests/test_bodies.py ....
anaconda/lib/python2.7/site-packages/poliastro/tests/test_maneuver.py ..F.FF
anaconda/lib/python2.7/site-packages/poliastro/tests/test_plotting.py ..
anaconda/lib/python2.7/site-packages/poliastro/tests/test_twobody.py .........F..F....
anaconda/lib/python2.7/site-packages/poliastro/tests/test_util.py .F.
========================================================================= FAILURES ==========================================================================
_________________________________________________________________ test_maneuver_total_time __________________________________________________________________
def test_maneuver_total_time():
    dt1 = 10.0 * u.s
    dt2 = 100.0 * u.s
    _v = np.zeros(3) * u.km / u.s  # Unused velocity
    expected_total_time = 110.0 * u.s
    man = Maneuver((dt1, _v), (dt2, _v))

  assert_almost_equal(man.get_total_time(), expected_total_time)

anaconda/lib/python2.7/site-packages/poliastro/tests/test_maneuver.py:42:

anaconda/lib/python2.7/site-packages/numpy/testing/utils.py:474: in assert_almost_equal
return assert_array_almost_equal(actual, desired, decimal, err_msg)
anaconda/lib/python2.7/site-packages/numpy/testing/utils.py:842: in assert_array_almost_equal
precision=decimal)
anaconda/lib/python2.7/site-packages/numpy/testing/utils.py:646: in assert_array_compare
val = comparison(x, y)
anaconda/lib/python2.7/site-packages/numpy/testing/utils.py:838: in compare
return around(z, decimal) <= 10.0**(-decimal)

self = <Quantity 0.0 s>, obj = array(False, dtype=bool), context = (<ufunc 'less_equal'>, (<Quantity 0.0 s>, 1e-07), 0)
def __array_prepare__(self, obj, context=None):
    # This method gets called by Numpy whenever a ufunc is called on the
    # array. The object passed in ``obj`` is an empty version of the
    # output array which we can e.g. change to an array sub-class, add
    # attributes to, etc. After this is called, then the ufunc is called
    # and the values in this empty array are set.

    # If no context is set, just return the input
    if context is None:
        return obj

    # Find out which ufunc is being used
    function = context[0]

    from .quantity_helper import UNSUPPORTED_UFUNCS, UFUNC_HELPERS

    # Check whether we even support this ufunc
    if function in UNSUPPORTED_UFUNCS:
        raise TypeError("Cannot use function '{0}' with quantities"
                        .format(function.__name__))

    # Now find out what arguments were passed to the ufunc, usually, this
    # will include at least the present object, and another, which could
    # be a Quantity, or a Numpy array, etc. when using two-argument ufuncs.
    args = context[1][:function.nin]
    units = [getattr(arg, 'unit', None) for arg in args]

    # If the ufunc is supported, then we call a helper function (defined
    # in quantity_helper.py) which returns the scale by which the inputs
    # should be multiplied before being passed to the ufunc, as well as
    # the unit the output from the ufunc will have.
    if function in UFUNC_HELPERS:
        converters, result_unit = UFUNC_HELPERS[function](function, *units)
    else:
        raise TypeError("Unknown ufunc {0}.  Please raise issue on "
                        "https://github.com/astropy/astropy"
                        .format(function.__name__))

    if any(converter is False for converter in converters):
        # for two-argument ufuncs with a quantity and a non-quantity,
        # the quantity normally needs to be dimensionless, *except*
        # if the non-quantity can have arbitrary unit, i.e., when it
        # is all zero, infinity or NaN.  In that case, the non-quantity
        # can just have the unit of the quantity
        # (this allows, e.g., `q > 0.` independent of unit)
        maybe_arbitrary_arg = args[converters.index(False)]
        try:
            if _can_have_arbitrary_unit(maybe_arbitrary_arg):
                converters = [None, None]
            else:
                raise UnitsError("Can only apply '{0}' function to "
                                 "dimensionless quantities when other "
                                 "argument is not a quantity (unless the "
                                 "latter is all zero/infinity/nan)"

                               .format(function.__name__))

E                                    UnitsError: Can only apply 'less_equal' function to dimensionless quantities when other argument is not a quantity (unless the latter is all zero/infinity/nan)
anaconda/lib/python2.7/site-packages/astropy/units/quantity.py:317: UnitsError
___________________________________________________________________ test_hohmann_maneuver ___________________________________________________________________
def test_hohmann_maneuver():
    # Data from Vallado, example 6.1
    alt_i = 191.34411 * u.km
    alt_f = 35781.34857 * u.km
    ss_i = State.circular(Earth, alt_i)
    expected_dv = 3.935224 * u.km / u.s
    expected_t_trans = 5.256713 * u.h
    man = Maneuver.hohmann(ss_i, Earth.R + alt_f)
    assert_almost_equal(ss_i.apply_maneuver(man).ecc, 0)
    assert_almost_equal(man.get_total_cost().to(u.km / u.s), expected_dv,

                      decimal=5)

anaconda/lib/python2.7/site-packages/poliastro/tests/test_maneuver.py:61:

anaconda/lib/python2.7/site-packages/numpy/testing/utils.py:474: in assert_almost_equal
return assert_array_almost_equal(actual, desired, decimal, err_msg)
anaconda/lib/python2.7/site-packages/numpy/testing/utils.py:842: in assert_array_almost_equal
precision=decimal)
anaconda/lib/python2.7/site-packages/numpy/testing/utils.py:646: in assert_array_compare
val = comparison(x, y)
anaconda/lib/python2.7/site-packages/numpy/testing/utils.py:838: in compare
return around(z, decimal) <= 10.0**(-decimal)

self = <Quantity 0.0 km / s>, obj = array(False, dtype=bool), context = (<ufunc 'less_equal'>, (<Quantity 0.0 km / s>, 1e-05), 0)
def __array_prepare__(self, obj, context=None):
    # This method gets called by Numpy whenever a ufunc is called on the
    # array. The object passed in ``obj`` is an empty version of the
    # output array which we can e.g. change to an array sub-class, add
    # attributes to, etc. After this is called, then the ufunc is called
    # and the values in this empty array are set.

    # If no context is set, just return the input
    if context is None:
        return obj

    # Find out which ufunc is being used
    function = context[0]

    from .quantity_helper import UNSUPPORTED_UFUNCS, UFUNC_HELPERS

    # Check whether we even support this ufunc
    if function in UNSUPPORTED_UFUNCS:
        raise TypeError("Cannot use function '{0}' with quantities"
                        .format(function.__name__))

    # Now find out what arguments were passed to the ufunc, usually, this
    # will include at least the present object, and another, which could
    # be a Quantity, or a Numpy array, etc. when using two-argument ufuncs.
    args = context[1][:function.nin]
    units = [getattr(arg, 'unit', None) for arg in args]

    # If the ufunc is supported, then we call a helper function (defined
    # in quantity_helper.py) which returns the scale by which the inputs
    # should be multiplied before being passed to the ufunc, as well as
    # the unit the output from the ufunc will have.
    if function in UFUNC_HELPERS:
        converters, result_unit = UFUNC_HELPERS[function](function, *units)
    else:
        raise TypeError("Unknown ufunc {0}.  Please raise issue on "
                        "https://github.com/astropy/astropy"
                        .format(function.__name__))

    if any(converter is False for converter in converters):
        # for two-argument ufuncs with a quantity and a non-quantity,
        # the quantity normally needs to be dimensionless, *except*
        # if the non-quantity can have arbitrary unit, i.e., when it
        # is all zero, infinity or NaN.  In that case, the non-quantity
        # can just have the unit of the quantity
        # (this allows, e.g., `q > 0.` independent of unit)
        maybe_arbitrary_arg = args[converters.index(False)]
        try:
            if _can_have_arbitrary_unit(maybe_arbitrary_arg):
                converters = [None, None]
            else:
                raise UnitsError("Can only apply '{0}' function to "
                                 "dimensionless quantities when other "
                                 "argument is not a quantity (unless the "
                                 "latter is all zero/infinity/nan)"

                               .format(function.__name__))

E                                    UnitsError: Can only apply 'less_equal' function to dimensionless quantities when other argument is not a quantity (unless the latter is all zero/infinity/nan)
anaconda/lib/python2.7/site-packages/astropy/units/quantity.py:317: UnitsError
_________________________________________________________________ test_bielliptic_maneuver __________________________________________________________________
def test_bielliptic_maneuver():
    # Data from Vallado, example 6.2
    alt_i = 191.34411 * u.km
    alt_b = 503873.0 * u.km
    alt_f = 376310.0 * u.km
    ss_i = State.circular(Earth, alt_i)
    expected_dv = 3.904057 * u.km / u.s
    expected_t_trans = 593.919803 * u.h
    man = Maneuver.bielliptic(ss_i, Earth.R + alt_b, Earth.R + alt_f)
    assert_almost_equal(ss_i.apply_maneuver(man).ecc, 0)
    assert_almost_equal(man.get_total_cost().to(u.km / u.s), expected_dv,

                      decimal=5)

anaconda/lib/python2.7/site-packages/poliastro/tests/test_maneuver.py:77:

anaconda/lib/python2.7/site-packages/numpy/testing/utils.py:474: in assert_almost_equal
return assert_array_almost_equal(actual, desired, decimal, err_msg)
anaconda/lib/python2.7/site-packages/numpy/testing/utils.py:842: in assert_array_almost_equal
precision=decimal)
anaconda/lib/python2.7/site-packages/numpy/testing/utils.py:646: in assert_array_compare
val = comparison(x, y)
anaconda/lib/python2.7/site-packages/numpy/testing/utils.py:838: in compare
return around(z, decimal) <= 10.0**(-decimal)

self = <Quantity 0.0 km / s>, obj = array(False, dtype=bool), context = (<ufunc 'less_equal'>, (<Quantity 0.0 km / s>, 1e-05), 0)
def __array_prepare__(self, obj, context=None):
    # This method gets called by Numpy whenever a ufunc is called on the
    # array. The object passed in ``obj`` is an empty version of the
    # output array which we can e.g. change to an array sub-class, add
    # attributes to, etc. After this is called, then the ufunc is called
    # and the values in this empty array are set.

    # If no context is set, just return the input
    if context is None:
        return obj

    # Find out which ufunc is being used
    function = context[0]

    from .quantity_helper import UNSUPPORTED_UFUNCS, UFUNC_HELPERS

    # Check whether we even support this ufunc
    if function in UNSUPPORTED_UFUNCS:
        raise TypeError("Cannot use function '{0}' with quantities"
                        .format(function.__name__))

    # Now find out what arguments were passed to the ufunc, usually, this
    # will include at least the present object, and another, which could
    # be a Quantity, or a Numpy array, etc. when using two-argument ufuncs.
    args = context[1][:function.nin]
    units = [getattr(arg, 'unit', None) for arg in args]

    # If the ufunc is supported, then we call a helper function (defined
    # in quantity_helper.py) which returns the scale by which the inputs
    # should be multiplied before being passed to the ufunc, as well as
    # the unit the output from the ufunc will have.
    if function in UFUNC_HELPERS:
        converters, result_unit = UFUNC_HELPERS[function](function, *units)
    else:
        raise TypeError("Unknown ufunc {0}.  Please raise issue on "
                        "https://github.com/astropy/astropy"
                        .format(function.__name__))

    if any(converter is False for converter in converters):
        # for two-argument ufuncs with a quantity and a non-quantity,
        # the quantity normally needs to be dimensionless, *except*
        # if the non-quantity can have arbitrary unit, i.e., when it
        # is all zero, infinity or NaN.  In that case, the non-quantity
        # can just have the unit of the quantity
        # (this allows, e.g., `q > 0.` independent of unit)
        maybe_arbitrary_arg = args[converters.index(False)]
        try:
            if _can_have_arbitrary_unit(maybe_arbitrary_arg):
                converters = [None, None]
            else:
                raise UnitsError("Can only apply '{0}' function to "
                                 "dimensionless quantities when other "
                                 "argument is not a quantity (unless the "
                                 "latter is all zero/infinity/nan)"

                               .format(function.__name__))

E                                    UnitsError: Can only apply 'less_equal' function to dimensionless quantities when other argument is not a quantity (unless the latter is all zero/infinity/nan)
anaconda/lib/python2.7/site-packages/astropy/units/quantity.py:317: UnitsError
__________________________________________________________________ test_perigee_and_apogee __________________________________________________________________
def test_perigee_and_apogee():
    expected_r_a = 500 * u.km
    expected_r_p = 300 * u.km
    a = (expected_r_a + expected_r_p) / 2
    ecc = expected_r_a / a - 1
    _a = 1.0 * u.deg  # Unused angle
    ss = State.from_elements(Earth, a, ecc, _a, _a, _a, _a)

  assert_almost_equal(ss.r_a, expected_r_a)

anaconda/lib/python2.7/site-packages/poliastro/tests/test_twobody.py:107:

anaconda/lib/python2.7/site-packages/numpy/testing/utils.py:474: in assert_almost_equal
return assert_array_almost_equal(actual, desired, decimal, err_msg)
anaconda/lib/python2.7/site-packages/numpy/testing/utils.py:842: in assert_array_almost_equal
precision=decimal)
anaconda/lib/python2.7/site-packages/numpy/testing/utils.py:646: in assert_array_compare
val = comparison(x, y)
anaconda/lib/python2.7/site-packages/numpy/testing/utils.py:838: in compare
return around(z, decimal) <= 10.0**(-decimal)

self = <Quantity 0.0 km>, obj = array(False, dtype=bool), context = (<ufunc 'less_equal'>, (<Quantity 0.0 km>, 1e-07), 0)
def __array_prepare__(self, obj, context=None):
    # This method gets called by Numpy whenever a ufunc is called on the
    # array. The object passed in ``obj`` is an empty version of the
    # output array which we can e.g. change to an array sub-class, add
    # attributes to, etc. After this is called, then the ufunc is called
    # and the values in this empty array are set.

    # If no context is set, just return the input
    if context is None:
        return obj

    # Find out which ufunc is being used
    function = context[0]

    from .quantity_helper import UNSUPPORTED_UFUNCS, UFUNC_HELPERS

    # Check whether we even support this ufunc
    if function in UNSUPPORTED_UFUNCS:
        raise TypeError("Cannot use function '{0}' with quantities"
                        .format(function.__name__))

    # Now find out what arguments were passed to the ufunc, usually, this
    # will include at least the present object, and another, which could
    # be a Quantity, or a Numpy array, etc. when using two-argument ufuncs.
    args = context[1][:function.nin]
    units = [getattr(arg, 'unit', None) for arg in args]

    # If the ufunc is supported, then we call a helper function (defined
    # in quantity_helper.py) which returns the scale by which the inputs
    # should be multiplied before being passed to the ufunc, as well as
    # the unit the output from the ufunc will have.
    if function in UFUNC_HELPERS:
        converters, result_unit = UFUNC_HELPERS[function](function, *units)
    else:
        raise TypeError("Unknown ufunc {0}.  Please raise issue on "
                        "https://github.com/astropy/astropy"
                        .format(function.__name__))

    if any(converter is False for converter in converters):
        # for two-argument ufuncs with a quantity and a non-quantity,
        # the quantity normally needs to be dimensionless, *except*
        # if the non-quantity can have arbitrary unit, i.e., when it
        # is all zero, infinity or NaN.  In that case, the non-quantity
        # can just have the unit of the quantity
        # (this allows, e.g., `q > 0.` independent of unit)
        maybe_arbitrary_arg = args[converters.index(False)]
        try:
            if _can_have_arbitrary_unit(maybe_arbitrary_arg):
                converters = [None, None]
            else:
                raise UnitsError("Can only apply '{0}' function to "
                                 "dimensionless quantities when other "
                                 "argument is not a quantity (unless the "
                                 "latter is all zero/infinity/nan)"

                               .format(function.__name__))

E                                    UnitsError: Can only apply 'less_equal' function to dimensionless quantities when other argument is not a quantity (unless the latter is all zero/infinity/nan)
anaconda/lib/python2.7/site-packages/astropy/units/quantity.py:317: UnitsError
_______________________________________________________ test_apply_zero_maneuver_returns_equal_state ________________________________________________________
def test_apply_zero_maneuver_returns_equal_state():
    _d = 1.0 * u.AU  # Unused distance
    _ = 0.5 * u.one  # Unused dimensionless value
    _a = 1.0 * u.deg  # Unused angle
    ss = State.from_elements(Sun, _d, _, _a, _a, _a, _a)
    dt = 0 * u.s
    dv = [0, 0, 0] * u.km / u.s
    ss_new = ss.apply_maneuver([(dt, dv)])

  assert_almost_equal(ss_new.r.to(u.km), ss.r.to(u.km))

anaconda/lib/python2.7/site-packages/poliastro/tests/test_twobody.py:152:

anaconda/lib/python2.7/site-packages/numpy/testing/utils.py:474: in assert_almost_equal
return assert_array_almost_equal(actual, desired, decimal, err_msg)
anaconda/lib/python2.7/site-packages/numpy/testing/utils.py:842: in assert_array_almost_equal
precision=decimal)
anaconda/lib/python2.7/site-packages/numpy/testing/utils.py:646: in assert_array_compare
val = comparison(x, y)
anaconda/lib/python2.7/site-packages/numpy/testing/utils.py:838: in compare
return around(z, decimal) <= 10.0**(-decimal)

self = <Quantity [ 0., 0., 0.] km>, obj = array([False, False, False], dtype=bool), context = (<ufunc 'less_equal'>, (<Quantity [ 0., 0., 0.] km>, 1e-07), 0)
def __array_prepare__(self, obj, context=None):
    # This method gets called by Numpy whenever a ufunc is called on the
    # array. The object passed in ``obj`` is an empty version of the
    # output array which we can e.g. change to an array sub-class, add
    # attributes to, etc. After this is called, then the ufunc is called
    # and the values in this empty array are set.

    # If no context is set, just return the input
    if context is None:
        return obj

    # Find out which ufunc is being used
    function = context[0]

    from .quantity_helper import UNSUPPORTED_UFUNCS, UFUNC_HELPERS

    # Check whether we even support this ufunc
    if function in UNSUPPORTED_UFUNCS:
        raise TypeError("Cannot use function '{0}' with quantities"
                        .format(function.__name__))

    # Now find out what arguments were passed to the ufunc, usually, this
    # will include at least the present object, and another, which could
    # be a Quantity, or a Numpy array, etc. when using two-argument ufuncs.
    args = context[1][:function.nin]
    units = [getattr(arg, 'unit', None) for arg in args]

    # If the ufunc is supported, then we call a helper function (defined
    # in quantity_helper.py) which returns the scale by which the inputs
    # should be multiplied before being passed to the ufunc, as well as
    # the unit the output from the ufunc will have.
    if function in UFUNC_HELPERS:
        converters, result_unit = UFUNC_HELPERS[function](function, *units)
    else:
        raise TypeError("Unknown ufunc {0}.  Please raise issue on "
                        "https://github.com/astropy/astropy"
                        .format(function.__name__))

    if any(converter is False for converter in converters):
        # for two-argument ufuncs with a quantity and a non-quantity,
        # the quantity normally needs to be dimensionless, *except*
        # if the non-quantity can have arbitrary unit, i.e., when it
        # is all zero, infinity or NaN.  In that case, the non-quantity
        # can just have the unit of the quantity
        # (this allows, e.g., `q > 0.` independent of unit)
        maybe_arbitrary_arg = args[converters.index(False)]
        try:
            if _can_have_arbitrary_unit(maybe_arbitrary_arg):
                converters = [None, None]
            else:
                raise UnitsError("Can only apply '{0}' function to "
                                 "dimensionless quantities when other "
                                 "argument is not a quantity (unless the "
                                 "latter is all zero/infinity/nan)"

                               .format(function.__name__))

E                                    UnitsError: Can only apply 'less_equal' function to dimensionless quantities when other argument is not a quantity (unless the latter is all zero/infinity/nan)
anaconda/lib/python2.7/site-packages/astropy/units/quantity.py:317: UnitsError
_______________________________________________________________ test_rotate_vector_with_units _______________________________________________________________
def test_rotate_vector_with_units():
    vector = [1, 0, 0] * u.m
    angle = 90 * u.deg
    axis = 'y'
    expected_vector = [0, 0, -1] * u.m
    result = util.rotate(vector, angle, axis)

  assert_array_almost_equal(result, expected_vector)

anaconda/lib/python2.7/site-packages/poliastro/tests/test_util.py:25:

anaconda/lib/python2.7/site-packages/numpy/testing/utils.py:842: in assert_array_almost_equal
precision=decimal)
anaconda/lib/python2.7/site-packages/numpy/testing/utils.py:646: in assert_array_compare
val = comparison(x, y)
anaconda/lib/python2.7/site-packages/numpy/testing/utils.py:838: in compare
return around(z, decimal) <= 10.0**(-decimal)

self = <Quantity [ 0., 0., 0.] m>, obj = array([False, False, False], dtype=bool), context = (<ufunc 'less_equal'>, (<Quantity [ 0., 0., 0.] m>, 1e-06), 0)
def __array_prepare__(self, obj, context=None):
    # This method gets called by Numpy whenever a ufunc is called on the
    # array. The object passed in ``obj`` is an empty version of the
    # output array which we can e.g. change to an array sub-class, add
    # attributes to, etc. After this is called, then the ufunc is called
    # and the values in this empty array are set.

    # If no context is set, just return the input
    if context is None:
        return obj

    # Find out which ufunc is being used
    function = context[0]

    from .quantity_helper import UNSUPPORTED_UFUNCS, UFUNC_HELPERS

    # Check whether we even support this ufunc
    if function in UNSUPPORTED_UFUNCS:
        raise TypeError("Cannot use function '{0}' with quantities"
                        .format(function.__name__))

    # Now find out what arguments were passed to the ufunc, usually, this
    # will include at least the present object, and another, which could
    # be a Quantity, or a Numpy array, etc. when using two-argument ufuncs.
    args = context[1][:function.nin]
    units = [getattr(arg, 'unit', None) for arg in args]

    # If the ufunc is supported, then we call a helper function (defined
    # in quantity_helper.py) which returns the scale by which the inputs
    # should be multiplied before being passed to the ufunc, as well as
    # the unit the output from the ufunc will have.
    if function in UFUNC_HELPERS:
        converters, result_unit = UFUNC_HELPERS[function](function, *units)
    else:
        raise TypeError("Unknown ufunc {0}.  Please raise issue on "
                        "https://github.com/astropy/astropy"
                        .format(function.__name__))

    if any(converter is False for converter in converters):
        # for two-argument ufuncs with a quantity and a non-quantity,
        # the quantity normally needs to be dimensionless, *except*
        # if the non-quantity can have arbitrary unit, i.e., when it
        # is all zero, infinity or NaN.  In that case, the non-quantity
        # can just have the unit of the quantity
        # (this allows, e.g., `q > 0.` independent of unit)
        maybe_arbitrary_arg = args[converters.index(False)]
        try:
            if _can_have_arbitrary_unit(maybe_arbitrary_arg):
                converters = [None, None]
            else:
                raise UnitsError("Can only apply '{0}' function to "
                                 "dimensionless quantities when other "
                                 "argument is not a quantity (unless the "
                                 "latter is all zero/infinity/nan)"

                               .format(function.__name__))

E                                    UnitsError: Can only apply 'less_equal' function to dimensionless quantities when other argument is not a quantity (unless the latter is all zero/infinity/nan)
anaconda/lib/python2.7/site-packages/astropy/units/quantity.py:317: UnitsError
============================================================ 6 failed, 26 passed in 8.54 seconds ============================================================
users-MacBook-Pro:~ user$

Hello @OrbitalMechanic, did you close the issue because you managed to make the test pass? If so, do you know what was the problem?

If it was closed it was purely by accident. I haven't discovered the
reason for the failures. Please reopen the issue.
Sam Dupree.
On 04/23/2015 00:39:45, Juan Luis Cano Rodríguez wrote:

Hello @OrbitalMechanic https://github.com/OrbitalMechanic, did you
close the issue because you managed to make the test pass? If so, do
you know what was the problem?
—
Reply to this email directly or view it on GitHub
https://github.com/Pybonacci/poliastro/issues/35#issuecomment-95430000.

Thanks @OrbitalMechanic, I changed the formatting of your last comment to properly see the result (you can use triple backticks ``` for that). Can you tell me how did you download poliastro and which astropy version do you have?
If I understood correctly, you manage your Python packages through Anaconda and the root environment is installed in a location which needs super admin privileges, am I right? Perhaps you can try to create a conda environment to make testing easier:
$ conda create -n poliastro27 python=2.7 numpy astropy matplotlib numba
$ source activate poliastro27
$ cd poliastro
$ python setup.py install

Initially I used GitHub to clone a version of the source to my system
and installed it per the following commands:
$ git clone https://github.com/Pybonacci/poliastro.git
$ cd poliastro/
$ python setup.py install
Not happy with the results I got from running the tests, I uninstalled
poliastro using the command "pip uninstall poliastro" and when realizing
that the preferred method of installing poliastro was to use pip, I
reinstalled poliastro using the command "pip install poliastro".
After looking at the installation procedures under "Getting Started" is
there a difference in just using "pip install poliastro" as opposed to
using "pip install numpy astropy matplotlib poliastro" as cite on the
webpage, even though I have numpy, astropy and matplotlib already installed?
On 04/24/2015 04:57:12, Juan Luis Cano Rodríguez wrote:

Thanks @OrbitalMechanic https://github.com/OrbitalMechanic, I
changed the formatting of your last comment to properly see the result
(you can use triple backticks ``` for that). Can you tell me how did
you download poliastro and which astropy version do you have?
If I understood correctly, you manage your Python packages through
Anaconda and the root environment is installed in a location which
needs super admin privileges, am I right? Perhaps you can try to
create a conda environment to make testing easier:
|$ conda create -n poliastro27 python=2.7 numpy astropy matplotlib numba
$ source activate poliastro27
$ cd poliastro
$ python setup.py install
|
—
Reply to this email directly or view it on GitHub
https://github.com/Pybonacci/poliastro/issues/35#issuecomment-95857911.

While there is no difference between installing poliastro with all the
requirements explicitely or not when using pip, this will install the
stable version available in PyPI which is 2.0 and has some differences with
the one from GitHub.
The first time you had many tests failing probably because of an old numba
version. It only works with the latest one, which is 0.18.2 if I recall
correctly.
The second time the tests failed because of a change in recent versions of
astropy that I had not tested with poliastro 2.0. I will therefore release
a 2.0.1 installable with pip without these problems.
Thanks for the bug report!
On Apr 24, 2015 3:29 PM, "OrbitalMechanic"<EMAIL_ADDRESS>wrote:

Initially I used GitHub to clone a version of the source to my system
and installed it per the following commands:
$ git clone https://github.com/Pybonacci/poliastro.git
$ cd poliastro/
$ python setup.py install
Not happy with the results I got from running the tests, I uninstalled
poliastro using the command "pip uninstall poliastro" and when realizing
that the preferred method of installing poliastro was to use pip, I
reinstalled poliastro using the command "pip install poliastro".
After looking at the installation procedures under "Getting Started" is
there a difference in just using "pip install poliastro" as opposed to
using "pip install numpy astropy matplotlib poliastro" as cite on the
webpage, even though I have numpy, astropy and matplotlib already
installed?
On 04/24/2015 04:57:12, Juan Luis Cano Rodríguez wrote:

Thanks @OrbitalMechanic https://github.com/OrbitalMechanic, I
changed the formatting of your last comment to properly see the result
(you can use triple backticks ``` for that). Can you tell me how did
you download poliastro and which astropy version do you have?
If I understood correctly, you manage your Python packages through
Anaconda and the root environment is installed in a location which
needs super admin privileges, am I right? Perhaps you can try to
create a conda environment to make testing easier:
|$ conda create -n poliastro27 python=2.7 numpy astropy matplotlib numba
$ source activate poliastro27
$ cd poliastro
$ python setup.py install
|
--
Reply to this email directly or view it on GitHub
<https://github.com/Pybonacci/poliastro/issues/35#issuecomment-95857911
.

--
Reply to this email directly or view it on GitHub
https://github.com/Pybonacci/poliastro/issues/35#issuecomment-95932304.

Please let me know when the 2.0.1 becomes available, and thanks for your
help. :-)
On 04/24/2015 13:02:01, Juan Luis Cano Rodríguez wrote:

While there is no difference between installing poliastro with all the
requirements explicitely or not when using pip, this will install the
stable version available in PyPI which is 2.0 and has some differences
with
the one from GitHub.
The first time you had many tests failing probably because of an old numba
version. It only works with the latest one, which is 0.18.2 if I recall
correctly.
The second time the tests failed because of a change in recent versions of
astropy that I had not tested with poliastro 2.0. I will therefore release
a 2.0.1 installable with pip without these problems.
Thanks for the bug report!
On Apr 24, 2015 3:29 PM, "OrbitalMechanic"<EMAIL_ADDRESS>wrote:

Initially I used GitHub to clone a version of the source to my system
and installed it per the following commands:
$ git clone https://github.com/Pybonacci/poliastro.git
$ cd poliastro/
$ python setup.py install
Not happy with the results I got from running the tests, I uninstalled
poliastro using the command "pip uninstall poliastro" and when realizing
that the preferred method of installing poliastro was to use pip, I
reinstalled poliastro using the command "pip install poliastro".
After looking at the installation procedures under "Getting Started" is
there a difference in just using "pip install poliastro" as opposed to
using "pip install numpy astropy matplotlib poliastro" as cite on the
webpage, even though I have numpy, astropy and matplotlib already
installed?
On 04/24/2015 04:57:12, Juan Luis Cano Rodríguez wrote:

Thanks @OrbitalMechanic https://github.com/OrbitalMechanic, I
changed the formatting of your last comment to properly see the result
(you can use triple backticks ``` for that). Can you tell me how did
you download poliastro and which astropy version do you have?
If I understood correctly, you manage your Python packages through
Anaconda and the root environment is installed in a location which
needs super admin privileges, am I right? Perhaps you can try to
create a conda environment to make testing easier:
|$ conda create -n poliastro27 python=2.7 numpy astropy matplotlib
numba
$ source activate poliastro27
$ cd poliastro
$ python setup.py install
|
--
Reply to this email directly or view it on GitHub

<https://github.com/Pybonacci/poliastro/issues/35#issuecomment-95857911

.

--
Reply to this email directly or view it on GitHub

https://github.com/Pybonacci/poliastro/issues/35#issuecomment-95932304.

—
Reply to this email directly or view it on GitHub
https://github.com/Pybonacci/poliastro/issues/35#issuecomment-95992930.

I just released poliastro 0.2.1 (not 2.0.1, sorry :sweat_smile:) to fix this bug. You can already pip install it, I added your name in the release notes.
http://pybonacci.github.io/poliastro/changelog.html#new-in-poliastro-0-2-1
As soon as you try poliastro 0.2.1 and check that all test pass I will fix this issue.

I was able to install poliastro ver. 0.2.1 successfully. All tests ran
successfully - see below.
Thanks for your help. I really appreciated it.
Sam Dupree.
users-MacBook-Pro:~ user$ sudo pip install poliastro
Password:
Collecting poliastro
Downloading poliastro-0.2.1.tar.gz (86kB)
100% |████████████████████████████████| 90kB 1.2MB/s
Installing collected packages: poliastro
Running setup.py install for poliastro
Successfully installed poliastro-0.2.1
users-MacBook-Pro:~ user$ python -c "import poliastro; poliastro.test()"
========================================================== test session
starts ===========================================================
platform darwin -- Python 2.7.9 -- py-1.4.26 -- pytest-2.6.4
collected 30 items
anaconda/lib/python2.7/site-packages/poliastro/tests/test_bodies.py ....
anaconda/lib/python2.7/site-packages/poliastro/tests/test_maneuver.py ......
anaconda/lib/python2.7/site-packages/poliastro/tests/test_twobody.py
.................
anaconda/lib/python2.7/site-packages/poliastro/tests/test_util.py ...
======================================================= 30 passed in
3.95 seconds ========================================================
users-MacBook-Pro:~ user$
On 04/26/2015 04:19:39, Juan Luis Cano Rodríguez wrote:

I just released poliastro 0.2.1 (not 2.0.1, sorry :sweat_smile:) to
fix this bug. You can already |pip install| it, I added your name in
the release notes.
http://pybonacci.github.io/poliastro/changelog.html#new-in-poliastro-0-2-1
As soon as you try poliastro 0.2.1 and check that all test pass I will
fix this issue.
—
Reply to this email directly or view it on GitHub
https://github.com/Pybonacci/poliastro/issues/35#issuecomment-96342448.

--
mail-signature
<IYA-2009.jpg>
<mmb_emblem-2.gif>   Samuel H. Dupree<EMAIL_ADDRESS>10501 Rising Ridge Road
Apartment 201 http://users.speakeasy.net/~sdupree/
Fredericksburg, VA 22407, USA
 HOME:<PHONE_NUMBER>            WORK:<PHONE_NUMBER>     FAX:<PHONE_NUMBER>

/          "The Greatest Show on Earth" is not on Earth. It's in Space!/

Perfect, thanks! Don't hesitate to send me your criticism or ideas about the package. Before May 10th I will release version 0.3, with substantial improvements :)
Closing!

This is  from poliastro 0.4 run on ubuntu 15.10
No plots are genertaed with poliastro.
Matplotlib examples work well
from poliastro.plotting import OrbitPlotter
op = OrbitPlotter()
#ss_a, ss_f = ss_i.apply_maneuver(hoh, intermediate=True)
op.plot(ss, label="Initial orbit")
The output
[<matplotlib.lines.Line2D at 0x7f808c286278>,
<matplotlib.lines.Line2D at 0x7f808c1b3438>]
no plots
ss = State.from_vectors(Earth, r, v)
ss.epoch
ss.epoch.iso
from poliastro.plotting import plot
plot(ss)
output
/home/loga/anaconda3/lib/python3.5/site-packages/matplotlib/axes/_axes.py:519: UserWarning: No labelled objects found. Use label='...' kwarg on individual plots.
warnings.warn("No labelled objects found. "
OUT[9][<matplotlib.lines.Line2D at 0x7f808c17ecc0>,
<matplotlib.lines.Line2D at 0x7f808c1859e8>]

Hello @ashalogu23, I guess you are missing a pyplot.show() call at the end. Try the Jupyter notebook for nicer interactive plots. The last warning was fixed as part of https://github.com/poliastro/poliastro/issues/103. Please open a new issue if the problem persists.


⚠ NGINX has degraded performance

In ed78ec0, NGINX (https://web.sshcdn.com) experienced degraded performance:

HTTP code: 200
Response time: 6800 ms

Resolved: NGINX performance has improved in 002bc8f.


Use I/O safety in sys::mman

Approved, but with a question: how do we want to handle the changelog for these changes, which do modify API signatures?

Since all of these changes are related, I think we should roll them up into one big CHANGELOG entry at the top of the file.  The awesomest option would be if we could convince Cargo to print suggestions for how to fix users' code, at least for the common cases.  But I don't know how.

The awesomest option would be if we could convince Cargo to print suggestions for how to fix users' code, at least for the common cases. But I don't know how.

I'll do some digging to see if there are attributes we can use.
bors r+


Updated gradle dependencies

To fix #66 the following changes were made:

Upgrade androidx.appcompat:appcompat from version 1.5.1 to 1.6.1
Upgrade com.google.android.material:material from version 1.7.0 to 1.8.0
Upgrade androidx.test.ext:junit from version 1.1.3 to 1.1.5
Upgrade androidx.test:core-ktx from version  1.4.0 to 1.5.0
Upgrade androidx.test.espresso:espresso-core from version 3.4.0 to 3.5.1

Result
All tests in LemonadeTests pass

Thanks. I also got stuck there

test_picking_lemon_proceeds_to_squeeze_state
Still my this test case is failing


UofT-DSI | Introduction to Building Software (Shell and Git) Week 1 - Assignment 1 (Shell)

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
I made changes to question #3
What did you learn from the changes you have made?
Somehow, the autograder didn't like my code "cd dir2 && touch file1.txt file2.txt file3.txt file4.txt file5.txt", and crossed them as incorrect...
My new code is "touch dir2/file1.txt dir2/file2.txt dir2/file3.txt dir2/file4.txt dir2/file5.txt" and autograder recognizes it!
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
My initial approach was "cd dir2 && touch file1.txt file2.txt file3.txt file4.txt file5.txt" - which works in my Git Bash Terminal, but autograder doesn't like it...
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
I struggled with how to submit the assignments (assignment 1 for shell, and assignment 2 for git) correctly. It was very confusing.
During the Saturday workshop, Pedram Asli kindly helped clarify my questions and correct steps to submit the assignments.
How were these changes tested?
For this assignment 1, I forked the UofT-DSI repository, created a new branch, worked on this assignment, and submitted it.
I submitted these Pull Requests and able to see Autograder, and see this template to fill it!
A reference to a related issue in your repository (if applicable)
N/A
Checklist

[X] I can confirm that my changes are working as intended

Thank you Emma Teng for having confirmed on Slack that my work is good, I will close the Pull Request now.


UiAutomator sample: UiDevice.pressHome and startActivity timeouts

After code call UiDevice.pressHome(), it can not startActivity for 5 seconds (it gets delayed) unless activity was started from user interaction. So test startup is always slow. That's why you have 5 seconds LAUNCH_TIMEOUT  :lollipop:
I did not found easy way to workaround it (there are hacky options). Please point out what can be done or at least document it's behavior.
Related code
https://github.com/googlesamples/android-testing/blob/master/uiautomator/BasicSample/app/src/androidTest/java/com/example/android/testing/uiautomator/BasicSample/ChangeTextBehaviorTest.java#L62
Related readings
https://code.google.com/p/android/issues/detail?id=4536
http://stackoverflow.com/questions/5600084/starting-an-activity-from-a-service-after-home-button-pressed-without-the-5-seco
And I've made scaffolding test of stock dialer where I skip UiDevice.pressHome() https://github.com/logcat/uiautomator-template

Can you please file a bug for the support library under: https://code.google.com/p/android/issues/entry?template=Test Support Library bug

This is not a bug of support library. Go create bug for support library, and let support lib team close it.  It's a joke to wait 5 seconds each time. You promote it as "the sample" in "google sample repo", brilliant :+1:

There is just no good way of synchronizing this. You can adjust the timeout to your needs in your test. The other thing that you could do is to use ActivityLifeCycleCallback's to track your target Activity in your test. But this sounds like something that could be solved at at the library level. That's why we suggested you to file a bug under the TESTING support library, so we can assign it the right person on the UIautomator team to see and look what they can improve there or offer other solutions.

If you use UiDevice.pressHome() and smaller timeouts, tests will fail. You can listen to ActivityLifeCycleCallback after you've pressed UiDevice.pressHome(), guess how long would it take? I bet for 5000ms.


Need vaccination data from publish date 2021-03-25 until 2021-03-20

Need vaccination data from publish date 2021-03-25 until 2021-03-20

Wont fix


Added profile pic url to UserBaseMinimumSerializer

Proposed Changes

Added read_profile_picture_url to UserBaseMinimumSerializer

Makes the image url available to treating_physician_object (allowing for user avatar to show up for existing choices in UserAutoComplete on frontend).

Associated Issue

8967 in FE.

Merge Checklist

[ ] Tests added/fixed
[ ] Update docs in /docs
[ ] Linting Complete
[ ] Any other necessary step

Only PR's with test cases included and passing lint and test pipelines will be reviewed
@ohcnetwork/care-backend-maintainers @ohcnetwork/care-backend-admins

I'll get the test fixed 👍


Loadig the token icon flashes the defult one first

Reported by simo on 23 Apr 2015 18:30 UTC
The default icon should be shown only if there isn't a custom icon, so the default icon doesn't flash even if briefly when the token is shown. A blank background should be set on default token object creation and icons loaded only after.

Closing as outdated.


Command to stage hunk under the cursor

Stage hunk would stage the block of uninterrupted lines under the cursor which changed.

@joaomoreno, the screenshot you posted show a command to stage selected ranges, not the hunk under the carey. what you showed us equivalent to line or selection staging.

How about this one?

@joaomoreno that looks more like it! I understand that menu is available in the normal editor if you click on the diff decorations in the gutter?
Are there currently commands to do the following?

navigate between these change hunks
open the diff decoration menu
stage the change

Off topic: which color theme is that in the screenshot?

The commands are Move to Next Change and Move to Previous Change
Hmm maybe not this one
We don't have one for this

Feel free to create independent issues for those missing commands.

I use the Ayu Mirage theme for quite some time now. Absolutely my favourite in the store.

This commands only seem to work on the normal editor, not in scm view right?

Somehow my colors look way more saturated:

Yeah, only works in the regular editor, unfortunately.
They do... which OS are you on? I'm on macOS. There might be an OS level setting which lets you reduce overall saturation.

I'm on macOS 10.12.6 Sierra.
I thought you were on Ubuntu judging by this contextual menu.

Strange thing is that your screenshots and the official screenshots look correct. Wonder if this is something electron/webkit related.
https://camo.githubusercontent.com/cd48eaf1d2bc4329db6d5ad7003bda5af7db81a6/68747470733a2f2f692e696d6775722e636f6d2f4b59584a6242752e706e67

The commands are Move to Next Change and Move to Previous Change

https://github.com/Microsoft/vscode/issues/48964

We don't have one for this

https://github.com/Microsoft/vscode/issues/48965


add basic parser logic

I fixed the code according to the comments.

Added error handling using a decorator and returning None. If critical data, such as title or link, is not found, the listing is skipped, and information about the skip is logged.


Feature: issue template to run sims through GH Actions

User submits an issue using the sims issue template.  Sims GH Action runs the configured simulations and uploads graphs to accessible cloud storage.

Work outline:

[ ] setup workflow to read "sim request" issue for sim settings and run it
[ ] settings should allow fee and A values and ranges
[ ] plots (output) should be saved to a branch with sim metadata
[ ] issue should be updated with a comment linking to output branch, show parsed settings, and status of run

Nomics data could be problematic since request retry logic isn't robust yet.

Nomics data could be problematic since request retry logic isn't robust yet.

Nomics is no longer in business.


Passwords may cached in memory

The script creates a client file which causes the following warning on my Android phone:
WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
As the warning suggests, adding 'auth-nocache' to the config helps me getting rid of the warning.
Do others get the same warning as well? And if so, should 'auth-nocache' be added to every config by the script?

Yea i get that warning it's fine

Weird: https://github.com/angristan/openvpn-install/pull/92

Also, can someone confirm they also have the warning?

Not an issue on our end. The config properly includes the option, the Android app simply doesn't parse it from the config. This is documented here: https://github.com/schwabe/ics-openvpn/issues/935
To fix the issue, the user must click on edit config, go to the advanced tab, edit custom options, and add auth-nocache.


[hotfix][docs] fix the broken reference

What is the purpose of the change
jus a simple fix on a broken reference.
Brief change log
fix the broken reference in these docs.
Verifying this change
run a local build and check the broken reference fixed.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

@flinkbot run azure

Hi @MartijnVisser, Sure, I have updated the commit message.

Hi @MartijnVisser, I have created these two PR. Thanks for the quick response. =)


translateY and offsets

Hi based on your theme.js within the src directory i think for example:
'fade-down': {
            '0%': {
                opacity: '0',
                transform: 'translateY(-2rem)',
            },
            '100%': {
                opacity: '1',
                transform: 'translateY(0)',
            },
        },

would not respect the original translateY value i guess like:

you could add a utility class (offset.js)
module.exports = function ({ addUtilities, matchUtilities, theme }) {
const animateUtilities = matchUtilities(
    {
        'animate-y': (value) => {
            const spacingValue = theme('spacing')[value];
            const className = `animate-y-${value}`;

            return {
                [`--an-translate-y-${value}`]: spacingValue,
            };
        },
    },
    {
        values: Object.keys(theme('spacing')),
    }
)
}

then change theme.js to :
'fade-up': {
            '0%': {
                opacity: '0',
                transform: 'translateY(var(--an-translate-y))',
            },
            '100%': {
                opacity: '1',
                transform: 'translateY(var(--tw-translate-y))',
            },
        },

now the div slides from your new offset position class like (animate-y-40) to the orinal y value:

Great work! I just wish there was a built-in way to use arbitrary values for more properties including offset positions.

@merijnponzo Sorry for the late reply. But indeed a good suggestion! We'll have a look what's possible.

With v1.1.0 this plugin now supports animation-composition utilities. With these we have a bit more control over intial values and offsets.


[DOCS] Standardize blog images sizes

Change Logs
Changed the image size to a standard size of 1200 * 600 for most images for better rendering of blogs landing page.
Impact
Describe any public API or user-facing feature change or any performance impact.
Risk level: none | low | medium | high
Choose one. If medium or high, explain what verification was done to mitigate the risks.
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

I definitely agree. But a question or a thought is should it be okay to decouple that and fix individual images in a second PR. I want to do the bulk change quickly and go from there. But open to ideas. What do you think?

I definitely agree. But a question or a thought is should it be okay to decouple that and fix individual images in a second PR. I want to do the bulk change quickly and go from there. But open to ideas. What do you think?

Given this is affecting how the website is visualized, let's have the changes to make images look better in one PR.

Done. @yihua  redrawing the entire image might be a bigger effort. I changed the images so their ratio does not change and are closer to 1200 * 600 either in width or height. Please take a look and flag any image that comes out odd.

Done. @yihua redrawing the entire image might be a bigger effort. I changed the images so their ratio does not change and are closer to 1200 * 600 either in width or height. Please take a look and flag any image that comes out odd.

Sg.  I'll take a look.  No need to redraw the images in this PR.

@bhasudha If needed, the images can be adjusted in a follow-up PR.


support presto as an adapter

Feature
Feature description
dbt should work with Presto. Someone familiar with Presto should fill out this survey and paste the results in here.
Who will this benefit?
Presto users, users that want to query cross-database.

New adapter questionnaire, via the New Adapter Information Sheet
Questions

What options are there for connecting to the warehouse? Eg: ODBC, a python module, etc

Use PyHive, a DB-API compatible module for connecting to Hive and Presto.

Is there a consensus around which of the options in #1 is the most featureful/best supported/most mature/etc option?

Yeah - use PyHive.

Does the warehouse support namespaces/schemas/datasets (or similar)?
Yes, schemas

Can schemas/namespaces be created using SQL? Eg: create schema my_schema

CREATE SCHEMA [ IF NOT EXISTS ] schema_name

via https://prestodb.io/docs/current/sql/create-schema.html

Does the warehouse support logical databases?
Yes, these are called "catalogs".

A Presto catalog contains schemas and references a data source via a connector. For example, you can configure a JMX catalog to provide access to JMX information via the JMX connector. When you run a SQL statement in Presto, you are running it against one or more catalogs. Other examples of catalogs include the Hive catalog to connect to a Hive data source.

Catalogs are defined in properties files stored in the Presto configuration directory.

via https://prestodb.io/docs/current/overview/concepts.html

Does the warehouse support standard-ish SQL? Are there any noteworthy caveats?
Yes, Presto was designed with ANSI SQL compliance in mind.

Are transactions supported?
I think so? Presto has START TRANSACTION, COMMIT, and ROLLBACK statements. The START TRANSACTION statement takes an isolation level, and I believe that the SERIALIZABLE isolation level will mimic Redshift's implementation of transactions. Unsure if there's a different/better option for modeling workloads, but worth investigating.

Can tables be created with create table schema.table as (...)?
Yes: https://prestodb.io/docs/current/sql/create-table-as.html

Can views be created with create view schema.view as (...)?
Yes: https://prestodb.io/docs/current/sql/create-view.html

Can tables/views be renamed with alter table {table_name} rename to {new_name}?
Yes: https://prestodb.io/docs/current/sql/alter-table.html

Does the warehouse support insert statements? Any caveats?
Yes: https://prestodb.io/docs/current/sql/insert.html

Does the warehouse support delete statements? Any caveats?
Yes: https://teradata.github.io/presto/docs/141t/sql/delete.html

Caveat:

Only Hive Connector currently supports DELETE and it works for the queries where one or more partitions are deleted entirely.

Does the warehouse support update statements? Any caveats?
don't think so. Replicate with a delete + insert?

Does the warehouse support merge statements? Any caveats?
Nope

Does the warehouse support drop table/drop view statements? Any caveats?
Yes: https://prestodb.io/docs/current/sql/drop-table.html

Does the warehouse support truncate statements? Any caveats?
Yes: https://prestodb.io/docs/current/sql/drop-view.html

Does the warehouse support temporary tables? Any caveats?
Doesn't look like it

Can queries be cancelled?

runtime.kill_query(query_id, message)

via https://prestodb.io/docs/current/connector/system.html

Are views bound to the relations they select from? Ie. do drop table statements require a ...cascade argument?
No

Does the warehouse support querying for existing relations (ie. their existence and type)? Is this via an API call or a SELECT statement? Eg: select * from information_schema.tables.

Possibly. Is the output of show tables structured? https://prestodb.io/docs/current/sql/show-tables.html

Does the warehouse support querying for the the columns in a relation? Is this via an API call or a SELECT statement? Eg: select * from information_schema.columns

Possibly. Is the output of show columns structured? https://prestodb.io/docs/current/sql/show-columns.html

Can columns be added and removed using DDL? Eg: alter table add column <name> <type>?
Yes: https://prestodb.io/docs/current/sql/alter-table.html

Does the warehouse support non-standard performance configurations? Ie. clustering, partitioning, sort/dist keys, etc. What are they, and how are they used? Can they be supplied in create table as statements?

Don't think so! This is surprising, but I can't find any good info on the topic.

Which column types does the warehouse support? Are text types varchars (with sizes) or unsized string columns? Are numeric types (with fixed precision) supported? Is there a different type for timestamps with timezones? Any caveats?
Types: https://prestodb.io/docs/current/language/types.html

Does the warehouse support column-level constraints (eg. unique, not null, foreign key, primary key)? Are they enforced? Can they be defined in create table as statements?
Nope


Email functionality added

#103 issue resolved

any update?

Conflicts up

closing it down due to no resolutions in the conflicts

It showed me no conflicts.


get_region_and_token.sh: curl default --connect-timeout is wrong

Modern curl version don't support subsecond --connect-timeout. The default is set to 0.05, which causes a curl warning.
The default therefore needs to be raised to 1 second.

Modern curl version don't support subsecond --connect-timeout

From the man page of the latest curl version:
--connect-timeout <seconds>
Maximum time in seconds that you allow curl's connection to take.
This only limits the connection phase, so if curl connects within the
given period it will continue - if not it will exit. Since version 7.32.0,
this option accepts decimal values.
If this option is used several times, the last one will be used.

The default is set to 0.05, which causes a curl warning.

The warning shouldn't appear . If it does, there is some issue with bash or curl on your system. This is how normal output looks:
Testing regions that respond faster than 0.05 seconds:
Got latency 0.045503s for region: DE Frankfurt
Got latency 0.048684s for region: Isle of Man (geo)
Got latency 0.048116s for region: Liechtenstein (geo)
Got latency 0.030201s for region: Moldova
Got latency 0.049863s for region: Netherlands

The default therefore needs to be raised to 1 second.

All regions in the world will probably respond within 350 milliseconds and most regions from the same continent should respond within 50 milliseconds. Having the limit set to 1000 milliseconds defeats the purpose of seeing only the regions that provide the best performance. If you set it to 1000, you will always see all regions and it will also make the script take a lot of time as it will have to wait a lot for all the regions from other continents.

Please make sure you compile curl with c-ares support as this 1 year old Gentoo bug points out: https://bugs.gentoo.org/699632
Solving the bug would also help other Gentoo users, but this is a Gentoo/curl bug, not a bug with this repository.
All other distros do not have this issue.


Option for opening defintion in peek view with Ctrl+click

When we use Ctrl + mouse click to jump to definition, vscode would open the definition in a new window, which is inconvenient for me.
It would be better if we can choose where to open definition, like in Visual Studio. VS settings here

Nice suggestion.
@jrieken If you agree with this, I'll create a setting so one can choose the 'ctrl+click behavior':

Go to definition (default)
Peek definition

Normally, ctrl+click runs editor.action.revealDefinition and cmd+ctrl+click opens editor.action.revealDefinitionAside. With this setting enabled, they both run editor.action.PeekDefinition. I don't think that's expected. Possibly change https://github.com/microsoft/vscode/pull/89884/files#diff-e65fe89b0a38c52267c34d0a2b04a9feR339 to
new DefinitionAction({ openToSide, openInPeek: openInPeek && !openToSide, ....

?

@JacksonKearl you can reopen verification-found issues

@JacksonKearl Uhm, I'll take a look on that. Thanks for your feedback!

@JacksonKearl Please file a bug and don't reopen feature requests

I created https://github.com/microsoft/vscode/issues/91665


Add dotenv and polyfills globally

Well after a lot of search and tests, i can't make dotenv works, or polyfills like whatwg-fetch in my environment.
Hmm, i'm complete noob with this kind of tools, i've been using things like create-react-app so, yep, this is new for me.
I tried to use the order of compiling, and entryFiles to bootstrap this kind of things but nothing works, and can't figure some solution in the docs or google... here is my actual configuration:
exports.files = {
  javascripts: {
    joinTo: {
      'dependencies.js': /^(?!app\/)/,
      'bundle.js': /^app\//
    },
    entryPoints: {
      'app/confs.js': 'bundle.js'
    }
  },
  stylesheets: {
    joinTo: 'app.css'
  },
};

exports.plugins = {
  babel: { presets: ['latest', 'react'] }
};

confs.js
require('dotenv').config();
require('whatwg-fetch');

Any recomendation? Hint? The idea is just to get the dotenv capabilities in all of my files, and add support for fetch with the polifyll.

Hey @nanotime, we appreciate the issue.
joinTo and entryPoints can't be used together. I am sorry that docs wasn't enough clear on this.
We recommend using entryPoints:
entryPoints: {
  'app/shims.js': 'shims.js',
  'app/init.js': 'app.js',
}

@shvaikalesh ok, i'll try that.
 Here is a note from docs:

Only the things you require will be included into an entryPoint bundle.
This means non-app/non-npm dependencie won't be included. Also means only statically analyzable requires will work.


Ensure Next.js parses client-side query post-hydration

In the meantime, using the above ideas here is what I came up with:
import { withRouter } from 'next/router';

export const withPageRouter = Component => {
  return withRouter(({ router, ...props }) => {
    router.query = [
      ...new URLSearchParams((router.asPath || '').split(/\?/)[1]).entries()
    ].reduce((q, [k, v]) => Object.assign(q, { [k]: v }), {});

    return <Component {...props} router={router} />;
  });
};

Originally posted by @cansin in https://github.com/zeit/next.js/issues/4804#issuecomment-541420735

We should make sure (add a test) that client-side query strings are correctly merged into statically exported pages post-hydration (for a normal and dynamically routed page).

@Timer FYI, here is the latest version of the above code that fixes an issue re: getInitialProps and follow the pattern applied at https://github.com/zeit/next.js/blob/canary/packages/next/client/with-router.tsx :
import { withRouter } from 'next/router';
import React from 'react';

export const withPageRouter = ComposedComponent => {
  const WithPageRouteWrapper = withRouter(({ router, ...props }) => {
    router.query = [
      ...new URLSearchParams((router.asPath || '').split(/\?/)[1]).entries()
    ].reduce((q, [k, v]) => Object.assign(q, { [k]: v }), {});

    return <ComposedComponent {...props} router={router} />;
  });

  WithPageRouteWrapper.getInitialProps = ComposedComponent.getInitialProps;
  WithPageRouteWrapper.origGetInitialProps =
    WithPageRouteWrapper.origGetInitialProps;
  if (process.env.NODE_ENV !== 'production') {
    const name =
      ComposedComponent.displayName || ComposedComponent.name || 'Unknown';
    WithPageRouteWrapper.displayName = `withPageRouter(${name})`;
  }

  return WithPageRouteWrapper;
};

Kudos to @Rameshv for pointing it out.

Regarding #9524

@stephenjang not sure why you're linking to the SSG RFC 🤔

@stephenjang not sure why you're linking to the SSG RFC 🤔

Oh I'm sorry. I was tested on dynamic-import with withRouter and getStaticProps examples for  SSG. That's misreporting issue.

This issue has been automatically closed because it wasn't verified against next@canary. If you think it was closed by accident, please leave a comment. If you are running into a similar issue, please open a new issue with a reproduction. Thank you.


Upgrade to Knative 0.9

This upgrades to using:

Knative serving and eventing 0.9
API version v1beta1 for serving and messaging.knative.dev/v1alpha1 (instead of eventing.knative.dev)
Duck type API for accessing Addressable resources (i.e. We can now target InMemoryChannel resources, not only the deprecated Channel).

Currently the list of possible channel types is encoded in a trait property, but I plan to allow users to specify channel type in the URI as well.
Unfortunately this may break compatibility with 0.8.0 because Subscription has changed package between 0.8 and 0.9 :(
Tests in progress for 0.8 compat.

Added a knative08compat package that make it work with knative 0.8 (which is current stable version) and also with knative 0.9.
Please check, removing wip.
I can create an issue to remove that package in M3, but I prefer to keep it in M2.
No chances to make it work also with knative 0.7.

May need to update the OLM manifest for 1.0.0-M2 as well.

Right. Done!


Use a single block of RAM

Rather than having split instruction and data RAM (like Caliptra Core has).
This matches what our eventual hardware will eventually be.
The main challenge is that we don't necessarily know how much data RAM we're going to need yet, nor do we know the final amount of total RAM we're going to have.
Here, we tweak the build so that the RAM offsets are computed more dynamically.
For now, we allocate the last 64 KB of RAM as data RAM, but we still try to be flexible about its location.
We also move some of the constants specifying it into one place, and turned optimization to the space-saving setting (opt-level set to s).
The example app seems to have a little trouble: I had to adjust the stack size so that it would load after this change, which makes me suspect we have a bug somewhere, either in the app RAM offset calculations, or in the way we run integration tests.
Next I'll work on enabling PMP, which I think will help us identify these bugs more easily.

Thanks!


5.2

Waiting for review from @radvani13

@radvani13  Instead of just an LGTM you should press the review buttons and approve. That unlocks the merge.

it looks like Radhika did indeed approve the PR, she just isn't a code owner.


Skeleton of parsing left to be done

Coverage decreased (-13.004%) to 72.956% when pulling abdd23919664d0fb62dda9ef1485fab7ca225a20 on little-cleanups into bb27f6cb57df2854ba3d7e8853eb0e8bf87c586c on master.


Missing support for determining if authenticated user is organization owner

Some operations involving teams within organizations require the authenticated user to be an organization owner.  As far as I can tell, there is no way to get this information in the current implementation.  The following stackoverflow answer illustrates the the information I am trying to retrieve: http://stackoverflow.com/a/28190753

Can you turn around the link?
You have the link in the text, and the text(nothing) in the link.

Thanks for notifying me, it should work now.

Implemented toward 1.81


fuzz test with single bool input is 50x slower vs two non fuzz with functions

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (471e4ac 2024-10-03T00:27:20.819613000Z)
What command(s) is the bug in?
forge test
Operating System
macOS (Apple Silicon)
Describe the bug
function testWithBoolInput(bool x) public {...}
takes 50x testing time vs running the following two combined:
function testWithTrueInput() public {bool x=true;...}
function testWithFalseInput() public {bool x=false;...}
maybe because the fuzzer runs over uints and converts to bool.
the fuzzer should specialize for bool input and deliver only 2 values.

@1m1-github thanks for reporting! The fuzzing test is done according to fuzz.runs config (which defaults to 256), therefore function testWithBoolInput(bool x) public {...} is actually called 256 times compared to only 2 calls when calling testWithTrueInput() + testWithFalseInput combined, see https://book.getfoundry.sh/reference/config/testing?fuzz#runs
Please reopen the issue if you see other perf improvements that could be done in the area. Thank you!

my point is that a bool input variable should run at most twice no matter what fuzz.runs says

@grandizzy my point is that a bool input variable should run at most twice no matter what fuzz.runs says

yeah, but that's better suitable for a unit test.
For fuzz tests IMO this is still valuable as the test itself could generate random values by using cheatcodes, e.g.
    function test_fuzzWithBoolInput(bool callAFirst) public {
        uint256 x = vm.randomUint();
        if (callAFirst) {
            target.a(x);
            target.b(x);
        } else {
            target.b(x);
            target.a(x);
        }
    }


runtime: GC pause time 20% increase in 1.8beta1 compared to 1.7.3

On my 64bits Windows 10 machine, the following benchmark https://gitlab.com/gasche/gc-latency-experiment/blob/master/main.go (with msgCount increased to 100M) display a worst time of 15.50ms in 1.8beta1 and 13.00ms in 1.7.3.

/cc @aclements

I suspect time.Now() isn't a great way to measure, especially on Windows.

There might be a performance regression here, but nothing in this benchmark indicates that it's specifically a GC pause time regression (in fact, it's highly unlikely that it is). In addition to Brad's suggestion, looking at the execution trace may be enlightening.

@aclements I looked into this test program yesterday (from a blog post via golang-nuts), and it looks like there's GC involvement. After the GC completes, allocation needs to assist with sweep—and when the heap is growing in the first 1/5th of that program, sweep assists won't find any garbage. Single allocations are delayed until the entire heap is swept.
I didn't do any comparison with go1.7.3, so can't speak to a regression.
I filed #18155 with details on what I found.

1.7.3:
...
gc 527 @57.745s 6%: 0+6.0+5.9 ms clock, 0+0/12/36+47 ms cpu, 381->381->195 MB, 391 MB goal, 8 P
gc 528 @57.854s 6%: 0+8.0+5.9 ms clock, 0+0/8.0/50+47 ms cpu, 381->381->195 MB, 391 MB goal, 8 P
gc 529 @57.966s 6%: 0+6.5+5.0 ms clock, 0+0/12/36+40 ms cpu, 381->381->195 MB, 391 MB goal, 8 P
gc 530 @58.074s 6%: 0+7.9+5.5 ms clock, 0+0/15/46+44 ms cpu, 381->381->195 MB, 391 MB goal, 8 P
gc 531 @58.187s 6%: 0+5.9+6.0 ms clock, 0+0/5.9/41+48 ms cpu, 381->381->195 MB, 391 MB goal, 8 P
1.8beta1
...
gc 525 @56.566s 1%: 0+9.0+0 ms clock, 0+9.0/9.9/3.9+0 ms cpu, 385->385->195 MB, 395 MB goal, 8 P
gc 526 @56.674s 1%: 0+9.0+0 ms clock, 0+9.0/0/9.0+0 ms cpu, 381->381->195 MB, 390 MB goal, 8 P
gc 527 @56.780s 1%: 0+9.0+1.0 ms clock, 0+9.0/10/5.0+8.0 ms cpu, 381->382->196 MB, 390 MB goal, 8 P
gc 528 @56.887s 1%: 0+9.0+0 ms clock, 0+9.0/1.9/12+0 ms cpu, 383->383->195 MB, 393 MB goal, 8 P
gc 529 @56.993s 1%: 0+7.9+0 ms clock, 0+7.9/7.9/0+0 ms cpu, 381->381->195 MB, 390 MB goal, 8 P
If I'm reading the trace correctly, GC is doing much better in 1.8beta1 than in 1.7.3. So the difference must be somewhere else.

stop-the-world (STW) sweep termination seems to be tacking more CPU time 0+9.0 compared to 0+0

Thanks for the gctrace. It's showing that your STW sweep termination and STW mark termination times in 1.8beta1 are less than a microsecond in both wall-clock and CPU time (except in gc 527). The "9.0" in "0+9.0" belongs to concurrent mark, not sweep term.
I think @rhysh is on to something, though. If you grab an execution trace with 1.8 and post it here, I can probably confirm his findings.

I've updated the previous post with the full traces as attachments (both 1.7.3 and 1.8beta1). I’ve also looked at what the resolution might be for time.Now on Windows. It’s complicated but I’m reasonably confident it’s around 1 micro-second on my machine. So measurement differences of 2.5ms could not be rounding errors.

After reading Rhys's post I was able to convince myself if half the spans
contain no free objects then a single allocation may end up scanning half
the heap's allocation bits. This is complicated by the fact that the
allocation fast path has be optimized for exactly the opposite situation,
where there are lots of free objects in each span.
One possible way to resolve this is to scan the spans in a pseudo random
order so that if half the object's are free finding a span with one should
not take too many tries, Certainly not half the spans. Perhaps the random
choice is only done by assists that are trying to allocate.
On Fri, Dec 2, 2016 at 12:26 PM, Austin Clements<EMAIL_ADDRESS>wrote:

Thanks for the gctrace. It's showing that your STW sweep termination and
STW mark termination times in 1.8beta1 are less than a microsecond in both
wall-clock and CPU time (except in gc 527). The "9.0" in "0+9.0" belongs to
concurrent mark, not sweep term.
I think @rhysh https://github.com/rhysh is on to something, though. If
you grab an execution trace with 1.8 and post it here, I can probably
confirm his findings.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/18161#issuecomment-264510926, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA7Wn9MtzZbWYyVGKwBU6T38N0zICEpjks5rEFTIgaJpZM4LCmtu
.

@frje, can you try applying https://golang.org/cl/34291 and see if that helps?

@aclements It looks like my original conclusion was probably wrong : 1.8beta1 does not get longer pauses than 1.7.3 it’s just that the benchmark is inherently imprecise and results are quite volatiles. I’ve now ran the benchmark multiple times with billions of calls.
What I get is this:
1.7.3
16-22.5ms
1.8Beta1
15-16ms
34291
19-20ms
As far as I’m concerned, this issue should be closed.

Closing, thanks for the update.


Implement underline,strikethrough styling for Label and MarkupLabel

ref #3903
Added two init boolean arguments 'underline' and 'strikethrough' in kivy.uix.label.Label and two options of same name in kivy.core.text.LabelBase
Uses the SDL routine TTF_SetFontStyle()
Added tags to MarkupLabel for the same.

@dessant please review this.

Looks good @udiboy1209, great job. I'll test it today.
New api endpoints need a versionadded tag and a bit of docstrings, you could use this as a template for those two props: https://github.com/udiboy1209/kivy/blob/styling/kivy/uix/label.py#L619.
The version will be 2.0.0.

We need to support all providers not just sadly so support for this needs to be added to text_pygame, text_pil,...

@akshayaurora @dessant should I mention that it only works with SDL2 in the docstring? the issue did not mention support for pygame,pil... only SDL2

@udiboy1209 yes, it should be mentioned, like this: https://github.com/kivy/kivy/blob/4e429deb8864e3450cb71cd670cd00d1516d2799/kivy/core/window/init.py#L837.

Why is the version 2.0.0? We're at 1.9.2.

@matham, we may need to update the repo version too.

The code works flawlessly, great work. :+1:

Awesome, thanks a lot for your contribution. :wink:

@dessant you guys check every little detail, even in the docstrings :stuck_out_tongue: ! Happy to contribute! :smile:


amam/ remove all reference to japan + update help centre answer

Description

remove japan from footer

Type of change

[x] Bug fix
[ ] New feature
[ ] Refactor code
[ ] Update translation text
[ ] Breaking change
[ ] Dependency update
[ ] This change requires a documentation update
[ ] Release

📝Changed routes:

/help-centre/trading

(view full size)

Commit 79fea7a88dfaf6e15d7fb591406e39d84efc370a (https://deriv-com-git-fork-mustofa-binary-amam-updatejapan.binary.sx).


Not jumping while using watch.

Jumping to the correct place can be skipped if the theme is very short  <10 sec as the "websocket tick" normally happens every 7-10 sec. Should we just skip ever short themes or calculate the tick then jump?

Possible solutions:
add a the "task" to a queue that check over and over if its the correct time and it it is add it to the process pool.