(pid=41679)   File "python/ray/_raylet.pyx", line 300, in ray._raylet.RayletClient.push_error
(pid=41679)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41679) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Connection closed unexpectedly.
(pid=41697) Traceback (most recent call last):
(pid=41697)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 98, in <module>
(pid=41697)     ray.worker.global_worker.main_loop()
(pid=41697)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1087, in main_loop
(pid=41697)     task = self._get_next_task_from_raylet()
(pid=41697)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1070, in _get_next_task_from_raylet
(pid=41697)     task = self.raylet_client.get_task()
(pid=41697)   File "python/ray/_raylet.pyx", line 247, in ray._raylet.RayletClient.get_task
(pid=41697)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41697) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Raylet connection closed.
(pid=41697)
(pid=41697) During handling of the above exception, another exception occurred:
(pid=41697)
(pid=41697) Traceback (most recent call last):
(pid=41697)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 105, in <module>
(pid=41697)     job_id=None)
(pid=41697)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/utils.py", line 68, in push_error_to_driver
(pid=41697)     worker.raylet_client.push_error(job_id, error_type, message, time.time())
(pid=41697)   File "python/ray/_raylet.pyx", line 300, in ray._raylet.RayletClient.push_error
(pid=41697)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41697) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Connection closed unexpectedly.
(pid=41720) Traceback (most recent call last):
(pid=41720)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 98, in <module>
(pid=41720)     ray.worker.global_worker.main_loop()
(pid=41720)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1087, in main_loop
(pid=41720)     task = self._get_next_task_from_raylet()
(pid=41720)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1070, in _get_next_task_from_raylet
(pid=41720)     task = self.raylet_client.get_task()
(pid=41720)   File "python/ray/_raylet.pyx", line 247, in ray._raylet.RayletClient.get_task
(pid=41720)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41720) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Raylet connection closed.
(pid=41720)
(pid=41720) During handling of the above exception, another exception occurred:
(pid=41720)
(pid=41720) Traceback (most recent call last):
(pid=41720)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 105, in <module>
(pid=41720)     job_id=None)
(pid=41720)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/utils.py", line 68, in push_error_to_driver
(pid=41720)     worker.raylet_client.push_error(job_id, error_type, message, time.time())
(pid=41720)   File "python/ray/_raylet.pyx", line 300, in ray._raylet.RayletClient.push_error
(pid=41720)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41720) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Connection closed unexpectedly.
(pid=41677) Traceback (most recent call last):
(pid=41677)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 98, in <module>
(pid=41677)     ray.worker.global_worker.main_loop()
(pid=41677)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1087, in main_loop
(pid=41677)     task = self._get_next_task_from_raylet()
(pid=41677)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1070, in _get_next_task_from_raylet
(pid=41677)     task = self.raylet_client.get_task()
(pid=41677)   File "python/ray/_raylet.pyx", line 247, in ray._raylet.RayletClient.get_task
(pid=41677)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41677) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Raylet connection closed.
(pid=41677)
(pid=41677) During handling of the above exception, another exception occurred:
(pid=41677)
(pid=41677) Traceback (most recent call last):
(pid=41677)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 105, in <module>
(pid=41677)     job_id=None)
(pid=41677)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/utils.py", line 68, in push_error_to_driver
(pid=41677)     worker.raylet_client.push_error(job_id, error_type, message, time.time())
(pid=41677)   File "python/ray/_raylet.pyx", line 300, in ray._raylet.RayletClient.push_error
(pid=41677)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41677) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Connection closed unexpectedly.
(pid=41724) Traceback (most recent call last):
(pid=41724)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 98, in <module>
(pid=41724)     ray.worker.global_worker.main_loop()
(pid=41724)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1087, in main_loop
(pid=41724)     task = self._get_next_task_from_raylet()
(pid=41724)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1070, in _get_next_task_from_raylet
(pid=41724)     task = self.raylet_client.get_task()
(pid=41724)   File "python/ray/_raylet.pyx", line 247, in ray._raylet.RayletClient.get_task
(pid=41724)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41724) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Raylet connection closed.
(pid=41724)
(pid=41724) During handling of the above exception, another exception occurred:
(pid=41724)
(pid=41724) Traceback (most recent call last):
(pid=41724)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 105, in <module>
(pid=41724)     job_id=None)
(pid=41724)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/utils.py", line 68, in push_error_to_driver
(pid=41724)     worker.raylet_client.push_error(job_id, error_type, message, time.time())
(pid=41724)   File "python/ray/_raylet.pyx", line 300, in ray._raylet.RayletClient.push_error
(pid=41724)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41724) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Connection closed unexpectedly.
(pid=41716) Traceback (most recent call last):
(pid=41716)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 98, in <module>
(pid=41716)     ray.worker.global_worker.main_loop()
(pid=41716)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1087, in main_loop
(pid=41716)     task = self._get_next_task_from_raylet()
(pid=41716)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1070, in _get_next_task_from_raylet
(pid=41716)     task = self.raylet_client.get_task()
(pid=41716)   File "python/ray/_raylet.pyx", line 247, in ray._raylet.RayletClient.get_task
(pid=41716)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41716) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Raylet connection closed.
(pid=41716)
(pid=41716) During handling of the above exception, another exception occurred:
(pid=41716)
(pid=41716) Traceback (most recent call last):
(pid=41716)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 105, in <module>
(pid=41716)     job_id=None)
(pid=41716)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/utils.py", line 68, in push_error_to_driver
(pid=41716)     worker.raylet_client.push_error(job_id, error_type, message, time.time())
(pid=41716)   File "python/ray/_raylet.pyx", line 300, in ray._raylet.RayletClient.push_error
(pid=41716)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41716) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Connection closed unexpectedly.
(pid=41649) Traceback (most recent call last):
(pid=41649)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 98, in <module>
(pid=41649)     ray.worker.global_worker.main_loop()
(pid=41649)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1087, in main_loop
(pid=41649)     task = self._get_next_task_from_raylet()
(pid=41649)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1070, in _get_next_task_from_raylet
(pid=41649)     task = self.raylet_client.get_task()
(pid=41649)   File "python/ray/_raylet.pyx", line 247, in ray._raylet.RayletClient.get_task
(pid=41649)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41649) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Raylet connection closed.
(pid=41649)
(pid=41649) During handling of the above exception, another exception occurred:
(pid=41649)
(pid=41649) Traceback (most recent call last):
(pid=41649)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 105, in <module>
(pid=41649)     job_id=None)
(pid=41649)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/utils.py", line 68, in push_error_to_driver
(pid=41649)     worker.raylet_client.push_error(job_id, error_type, message, time.time())
(pid=41649)   File "python/ray/_raylet.pyx", line 300, in ray._raylet.RayletClient.push_error
(pid=41649)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41649) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Connection closed unexpectedly.
(pid=41676) Traceback (most recent call last):
(pid=41676)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 98, in <module>
(pid=41676)     ray.worker.global_worker.main_loop()
(pid=41676)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1087, in main_loop
(pid=41676)     task = self._get_next_task_from_raylet()
(pid=41676)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1070, in _get_next_task_from_raylet
(pid=41676)     task = self.raylet_client.get_task()
(pid=41676)   File "python/ray/_raylet.pyx", line 247, in ray._raylet.RayletClient.get_task
(pid=41676)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41676) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Raylet connection closed.
(pid=41676)
(pid=41676) During handling of the above exception, another exception occurred:
(pid=41676)
(pid=41676) Traceback (most recent call last):
(pid=41676)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 105, in <module>
(pid=41676)     job_id=None)
(pid=41676)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/utils.py", line 68, in push_error_to_driver
(pid=41676)     worker.raylet_client.push_error(job_id, error_type, message, time.time())
(pid=41676)   File "python/ray/_raylet.pyx", line 300, in ray._raylet.RayletClient.push_error
(pid=41676)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41676) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Connection closed unexpectedly.
(pid=41715) Traceback (most recent call last):
(pid=41715)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 98, in <module>
(pid=41715)     ray.worker.global_worker.main_loop()
(pid=41715)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1087, in main_loop
(pid=41715)     task = self._get_next_task_from_raylet()
(pid=41715)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1070, in _get_next_task_from_raylet
(pid=41715)     task = self.raylet_client.get_task()
(pid=41715)   File "python/ray/_raylet.pyx", line 247, in ray._raylet.RayletClient.get_task
(pid=41715)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41715) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Raylet connection closed.
(pid=41715)
(pid=41715) During handling of the above exception, another exception occurred:
(pid=41715)
(pid=41715) Traceback (most recent call last):
(pid=41715)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 105, in <module>
(pid=41715)     job_id=None)
(pid=41715)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/utils.py", line 68, in push_error_to_driver
(pid=41715)     worker.raylet_client.push_error(job_id, error_type, message, time.time())
(pid=41715)   File "python/ray/_raylet.pyx", line 300, in ray._raylet.RayletClient.push_error
(pid=41715)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41715) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Connection closed unexpectedly.
(pid=41725) Traceback (most recent call last):
(pid=41725)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 98, in <module>
(pid=41725)     ray.worker.global_worker.main_loop()
(pid=41725)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1087, in main_loop
(pid=41725)     task = self._get_next_task_from_raylet()
(pid=41725)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1070, in _get_next_task_from_raylet
(pid=41725)     task = self.raylet_client.get_task()
(pid=41725)   File "python/ray/_raylet.pyx", line 247, in ray._raylet.RayletClient.get_task
(pid=41725)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41725) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Raylet connection closed.
(pid=41725)
(pid=41725) During handling of the above exception, another exception occurred:
(pid=41725)
(pid=41725) Traceback (most recent call last):
(pid=41725)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 105, in <module>
(pid=41725)     job_id=None)
(pid=41725)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/utils.py", line 68, in push_error_to_driver
(pid=41725)     worker.raylet_client.push_error(job_id, error_type, message, time.time())
(pid=41725)   File "python/ray/_raylet.pyx", line 300, in ray._raylet.RayletClient.push_error
(pid=41725)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41725) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Connection closed unexpectedly.
(pid=41693) Traceback (most recent call last):
(pid=41693)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 98, in <module>
(pid=41693)     ray.worker.global_worker.main_loop()
(pid=41693)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1087, in main_loop
(pid=41693)     task = self._get_next_task_from_raylet()
(pid=41693)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1070, in _get_next_task_from_raylet
(pid=41693)     task = self.raylet_client.get_task()
(pid=41693)   File "python/ray/_raylet.pyx", line 247, in ray._raylet.RayletClient.get_task
(pid=41693)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41693) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Raylet connection closed.
(pid=41693)
(pid=41693) During handling of the above exception, another exception occurred:
(pid=41693)
(pid=41693) Traceback (most recent call last):
(pid=41693)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 105, in <module>
(pid=41693)     job_id=None)
(pid=41693)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/utils.py", line 68, in push_error_to_driver
(pid=41693)     worker.raylet_client.push_error(job_id, error_type, message, time.time())
(pid=41693)   File "python/ray/_raylet.pyx", line 300, in ray._raylet.RayletClient.push_error
(pid=41693)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41693) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Connection closed unexpectedly.
(pid=41729) Traceback (most recent call last):
(pid=41729)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 98, in <module>
(pid=41729)     ray.worker.global_worker.main_loop()
(pid=41729)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1087, in main_loop
(pid=41729)     task = self._get_next_task_from_raylet()
(pid=41729)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1070, in _get_next_task_from_raylet
(pid=41729)     task = self.raylet_client.get_task()
(pid=41729)   File "python/ray/_raylet.pyx", line 247, in ray._raylet.RayletClient.get_task
(pid=41729)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41729) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Raylet connection closed.
(pid=41729)
(pid=41729) During handling of the above exception, another exception occurred:
(pid=41729)
(pid=41729) Traceback (most recent call last):
(pid=41729)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 105, in <module>
(pid=41729)     job_id=None)
(pid=41729)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/utils.py", line 68, in push_error_to_driver
(pid=41729)     worker.raylet_client.push_error(job_id, error_type, message, time.time())
(pid=41729)   File "python/ray/_raylet.pyx", line 300, in ray._raylet.RayletClient.push_error
(pid=41729)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41729) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Connection closed unexpectedly.
(pid=41701) Traceback (most recent call last):
(pid=41701)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 98, in <module>
(pid=41701)     ray.worker.global_worker.main_loop()
(pid=41701)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1087, in main_loop
(pid=41701)     task = self._get_next_task_from_raylet()
(pid=41701)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1070, in _get_next_task_from_raylet
(pid=41701)     task = self.raylet_client.get_task()
(pid=41701)   File "python/ray/_raylet.pyx", line 247, in ray._raylet.RayletClient.get_task
(pid=41701)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41701) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Raylet connection closed.
(pid=41701)
(pid=41701) During handling of the above exception, another exception occurred:
(pid=41701)
(pid=41701) Traceback (most recent call last):
(pid=41701)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 105, in <module>
(pid=41701)     job_id=None)
(pid=41701)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/utils.py", line 68, in push_error_to_driver
(pid=41701)     worker.raylet_client.push_error(job_id, error_type, message, time.time())
(pid=41701)   File "python/ray/_raylet.pyx", line 300, in ray._raylet.RayletClient.push_error
(pid=41701)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41701) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Connection closed unexpectedly.
(pid=41669) Traceback (most recent call last):
(pid=41669)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 98, in <module>
(pid=41669)     ray.worker.global_worker.main_loop()
(pid=41669)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1087, in main_loop
(pid=41669)     task = self._get_next_task_from_raylet()
(pid=41669)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1070, in _get_next_task_from_raylet
(pid=41669)     task = self.raylet_client.get_task()
(pid=41669)   File "python/ray/_raylet.pyx", line 247, in ray._raylet.RayletClient.get_task
(pid=41669)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41669) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Raylet connection closed.
(pid=41669)
(pid=41669) During handling of the above exception, another exception occurred:
(pid=41669)
(pid=41669) Traceback (most recent call last):
(pid=41669)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 105, in <module>
(pid=41669)     job_id=None)
(pid=41669)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/utils.py", line 68, in push_error_to_driver
(pid=41669)     worker.raylet_client.push_error(job_id, error_type, message, time.time())
(pid=41669)   File "python/ray/_raylet.pyx", line 300, in ray._raylet.RayletClient.push_error
(pid=41669)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41669) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Connection closed unexpectedly.
(pid=41718) Traceback (most recent call last):
(pid=41718)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 98, in <module>
(pid=41718)     ray.worker.global_worker.main_loop()
(pid=41718)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1087, in main_loop
(pid=41718)     task = self._get_next_task_from_raylet()
(pid=41718)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1070, in _get_next_task_from_raylet
(pid=41718)     task = self.raylet_client.get_task()
(pid=41718)   File "python/ray/_raylet.pyx", line 247, in ray._raylet.RayletClient.get_task
(pid=41718)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41718) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Raylet connection closed.
(pid=41718)
(pid=41718) During handling of the above exception, another exception occurred:
(pid=41718)
(pid=41718) Traceback (most recent call last):
(pid=41718)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 105, in <module>
(pid=41718)     job_id=None)
(pid=41718)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/utils.py", line 68, in push_error_to_driver
(pid=41718)     worker.raylet_client.push_error(job_id, error_type, message, time.time())
(pid=41718)   File "python/ray/_raylet.pyx", line 300, in ray._raylet.RayletClient.push_error
(pid=41718)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41718) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Connection closed unexpectedly.
(pid=41732) Traceback (most recent call last):
(pid=41732)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 98, in <module>
(pid=41732)     ray.worker.global_worker.main_loop()
(pid=41732)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1087, in main_loop
(pid=41732)     task = self._get_next_task_from_raylet()
(pid=41732)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1070, in _get_next_task_from_raylet
(pid=41732)     task = self.raylet_client.get_task()
(pid=41732)   File "python/ray/_raylet.pyx", line 247, in ray._raylet.RayletClient.get_task
(pid=41732)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41732) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Raylet connection closed.
(pid=41732)
(pid=41732) During handling of the above exception, another exception occurred:
(pid=41732)
(pid=41732) Traceback (most recent call last):
(pid=41732)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 105, in <module>
(pid=41732)     job_id=None)
(pid=41732)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/utils.py", line 68, in push_error_to_driver
(pid=41732)     worker.raylet_client.push_error(job_id, error_type, message, time.time())
(pid=41732)   File "python/ray/_raylet.pyx", line 300, in ray._raylet.RayletClient.push_error
(pid=41732)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41732) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Connection closed unexpectedly.
(pid=41692) Traceback (most recent call last):
(pid=41692)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 98, in <module>
(pid=41692)     ray.worker.global_worker.main_loop()
(pid=41692)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1087, in main_loop
(pid=41692)     task = self._get_next_task_from_raylet()
(pid=41692)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1070, in _get_next_task_from_raylet
(pid=41692)     task = self.raylet_client.get_task()
(pid=41692)   File "python/ray/_raylet.pyx", line 247, in ray._raylet.RayletClient.get_task
(pid=41692)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41692) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Raylet connection closed.
(pid=41692)
(pid=41692) During handling of the above exception, another exception occurred:
(pid=41692)
(pid=41692) Traceback (most recent call last):
(pid=41692)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 105, in <module>
(pid=41692)     job_id=None)
(pid=41692)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/utils.py", line 68, in push_error_to_driver
(pid=41692)     worker.raylet_client.push_error(job_id, error_type, message, time.time())
(pid=41692)   File "python/ray/_raylet.pyx", line 300, in ray._raylet.RayletClient.push_error
(pid=41692)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41692) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Connection closed unexpectedly.
(pid=41730) Traceback (most recent call last):
(pid=41730)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 98, in <module>
(pid=41730)     ray.worker.global_worker.main_loop()
(pid=41730)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1087, in main_loop
(pid=41730)     task = self._get_next_task_from_raylet()
(pid=41730)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1070, in _get_next_task_from_raylet
(pid=41730)     task = self.raylet_client.get_task()
(pid=41730)   File "python/ray/_raylet.pyx", line 247, in ray._raylet.RayletClient.get_task
(pid=41730)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41730) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Raylet connection closed.
(pid=41730)
(pid=41730) During handling of the above exception, another exception occurred:
(pid=41730)
(pid=41730) Traceback (most recent call last):
(pid=41730)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 105, in <module>
(pid=41730)     job_id=None)
(pid=41730)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/utils.py", line 68, in push_error_to_driver
(pid=41730)     worker.raylet_client.push_error(job_id, error_type, message, time.time())
(pid=41730)   File "python/ray/_raylet.pyx", line 300, in ray._raylet.RayletClient.push_error
(pid=41730)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41730) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Connection closed unexpectedly.
(pid=41702) WARNING: Logging before InitGoogleLogging() is written to STDERR
(pid=41702) E1118 16:58:53.084489 41928 raylet_client.cc:343] IOError: [RayletClient] Connection closed unexpectedly. [RayletClient] Failed to push profile events.
(pid=41702) Traceback (most recent call last):
(pid=41702)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 98, in <module>
(pid=41702)     ray.worker.global_worker.main_loop()
(pid=41702)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1087, in main_loop
(pid=41702)     task = self._get_next_task_from_raylet()
(pid=41702)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py", line 1070, in _get_next_task_from_raylet
(pid=41702)     task = self.raylet_client.get_task()
(pid=41702)   File "python/ray/_raylet.pyx", line 247, in ray._raylet.RayletClient.get_task
(pid=41702)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41702) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Connection closed unexpectedly.
(pid=41702)
(pid=41702) During handling of the above exception, another exception occurred:
(pid=41702)
(pid=41702) Traceback (most recent call last):
(pid=41702)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/workers/default_worker.py", line 105, in <module>
(pid=41702)     job_id=None)
(pid=41702)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/utils.py", line 68, in push_error_to_driver
(pid=41702)     worker.raylet_client.push_error(job_id, error_type, message, time.time())
(pid=41702)   File "python/ray/_raylet.pyx", line 300, in ray._raylet.RayletClient.push_error
(pid=41702)   File "python/ray/_raylet.pyx", line 61, in ray._raylet.check_status
(pid=41702) ray.exceptions.RayletError: The Raylet died with this message: [RayletClient] Connection closed unexpectedly.
(pid=41698) Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7f7b822df730>
(pid=41698) Traceback (most recent call last):
(pid=41698)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/weakref.py", line 117, in remove
(pid=41698) TypeError: 'NoneType' object is not callable
(pid=41690) Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7fb85b9df730>
(pid=41690) Traceback (most recent call last):
(pid=41690)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/weakref.py", line 117, in remove
(pid=41690) TypeError: 'NoneType' object is not callable
(pid=41673) Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7fb013f27730>
(pid=41673) Traceback (most recent call last):
(pid=41673)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/weakref.py", line 117, in remove
(pid=41673) TypeError: 'NoneType' object is not callable
(pid=41728) Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7fd2601d7730>
(pid=41728) Traceback (most recent call last):
(pid=41728)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/weakref.py", line 117, in remove
(pid=41728) TypeError: 'NoneType' object is not callable
(pid=41671) Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7fa6dfb63730>
(pid=41671) Traceback (most recent call last):
(pid=41671)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/weakref.py", line 117, in remove
(pid=41671) TypeError: 'NoneType' object is not callable
(pid=41714) Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7fca19ea3730>
(pid=41714) Traceback (most recent call last):
(pid=41714)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/weakref.py", line 117, in remove
(pid=41714) TypeError: 'NoneType' object is not callable
(pid=41646) Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7f6ad1156730>
(pid=41646) Traceback (most recent call last):
(pid=41646)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/weakref.py", line 117, in remove
(pid=41646) TypeError: 'NoneType' object is not callable
(pid=41687) Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7fb9f8f14730>
(pid=41687) Traceback (most recent call last):
(pid=41687)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/weakref.py", line 117, in remove
(pid=41687) TypeError: 'NoneType' object is not callable
(pid=41663) Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7fd6ea2df730>
(pid=41663) Traceback (most recent call last):
(pid=41663)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/weakref.py", line 117, in remove
(pid=41663) TypeError: 'NoneType' object is not callable
(pid=41713) Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7fb8028b6730>
(pid=41713) Traceback (most recent call last):
(pid=41713)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/weakref.py", line 117, in remove
(pid=41713) TypeError: 'NoneType' object is not callable
---------------------------------------------------------------------------
ArrowIOError                              Traceback (most recent call last)
<ipython-input-10-8198f8a7bbcb> in <module>
----> 1 scaled_feats = StandardScaler().fit_transform(mat.values)

~/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/modin/pandas/base.py in __getattribute__(self, item)
   3431         ]
   3432         if item not in default_behaviors:
-> 3433             method = object.__getattribute__(self, item)
   3434             is_callable = callable(method)
   3435             # We default to pandas on empty DataFrames. This avoids a large amount of

~/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/modin/pandas/base.py in values(self)
   3401             The numpy representation of this object.
   3402         """
-> 3403         return self.to_numpy()
   3404
   3405     @property

~/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/modin/pandas/base.py in to_numpy(self, dtype, copy)
   2999             A numpy array.
   3000         """
-> 3001         arr = self._query_compiler.to_numpy()
   3002         if dtype is not None:
   3003             return np.asarray(arr, dtype)

~/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/modin/backends/pandas/query_compiler.py in to_numpy(self)
    146             NumPy Array of the QueryCompiler.
    147         """
--> 148         arr = self._modin_frame.to_numpy()
    149         ErrorMessage.catch_bugs_and_request_email(
    150             len(arr) != len(self.index) or len(arr[0]) != len(self.columns)

~/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/modin/engines/base/frame/data.py in to_numpy(self)
   1201             Numpy array.
   1202         """
-> 1203         return self._frame_mgr_cls.to_numpy(self._partitions)
   1204
   1205     def transpose(self):

~/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/modin/engines/ray/generic/frame/partition_manager.py in to_numpy(cls, partitions)
     21             [
     22                 obj.apply(lambda df: df.to_numpy()).oid
---> 23                 for row in partitions
     24                 for obj in row
     25             ]

~/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/modin/engines/ray/generic/frame/partition_manager.py in <listcomp>(.0)
     22                 obj.apply(lambda df: df.to_numpy()).oid
     23                 for row in partitions
---> 24                 for obj in row
     25             ]
     26         )

~/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/modin/engines/ray/pandas_on_ray/frame/partition.py in apply(self, func, **kwargs)
     50         oid = self.oid
     51         call_queue = self.call_queue + [(func, kwargs)]
---> 52         result, length, width = deploy_ray_func.remote(call_queue, oid)
     53         return PandasOnRayFramePartition(result, length, width)
     54

~/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/remote_function.py in _remote_proxy(*args, **kwargs)
     76         @wraps(function)
     77         def _remote_proxy(*args, **kwargs):
---> 78             return self._remote(args=args, kwargs=kwargs)
     79
     80         self.remote = _remote_proxy

~/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/remote_function.py in _remote(self, args, kwargs, num_return_vals, num_cpus, num_gpus, resources)
    153             invocation = self._decorator(invocation)
    154
--> 155         return invocation(args, kwargs)

~/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/remote_function.py in invocation(args, kwargs)
    143                     args,
    144                     num_return_vals=num_return_vals,
--> 145                     resources=resources)
    146
    147             if len(object_ids) == 1:

~/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py in submit_task(self, function_descriptor, args, actor_id, actor_handle_id, actor_counter, actor_creation_id, actor_creation_dummy_object_id, previous_actor_task_dummy_object_id, max_actor_reconstructions, new_actor_handles, num_return_vals, resources, placement_resources, job_id)
    678                     args_for_raylet.append(arg)
    679                 else:
--> 680                     args_for_raylet.append(put(arg))
    681
    682             if new_actor_handles is None:

~/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py in put(value)
   2275                 worker.task_context.put_index,
   2276             )
-> 2277             worker.put_object(object_id, value)
   2278         worker.task_context.put_index += 1
   2279         return object_id

~/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py in put_object(self, object_id, value)
    396                 range(ray_constants.DEFAULT_PUT_OBJECT_RETRIES)):
    397             try:
--> 398                 self._try_store_and_register(object_id, value)
    399                 break
    400             except pyarrow.plasma.PlasmaStoreFull as plasma_exc:

~/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py in _try_store_and_register(self, object_id, value)
    416         """
    417         try:
--> 418             self.store_and_register(object_id, value)
    419         except pyarrow.plasma.PlasmaObjectExists:
    420             # The object already exists in the object store, so there is no

~/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/worker.py in store_and_register(self, object_id, value, depth)
    325                         memcopy_threads=self.memcopy_threads,
    326                         serialization_context=self.get_serialization_context(
--> 327                             self.current_job_id))
    328                 break
    329             except pyarrow.SerializationCallbackError as e:

~/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/utils.py in _wrapper(*args, **kwargs)
    517                 def _wrapper(*args, **kwargs):
    518                     with self.lock:
--> 519                         return orig_attr(*args, **kwargs)
    520
    521                 self._wrapper_cache[attr] = _wrapper

~/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/pyarrow_files/pyarrow/_plasma.pyx in pyarrow._plasma.PlasmaClient.put()

~/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/pyarrow_files/pyarrow/_plasma.pyx in pyarrow._plasma.PlasmaClient.create()

~/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/pyarrow_files/pyarrow/_plasma.pyx in pyarrow._plasma.plasma_check_status()

~/Store/Cardiomics/python_dir/python_project/lib/python3.5/site-packages/ray/pyarrow_files/pyarrow/error.pxi in pyarrow.lib.check_status()

ArrowIOError: Encountered unexpected EOF

(pid=41697) Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7fb2d94ea730>
(pid=41697) Traceback (most recent call last):
(pid=41697)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/weakref.py", line 117, in remove
(pid=41697) TypeError: 'NoneType' object is not callable
(pid=41697) Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7fb2d94ea730>
(pid=41697) Traceback (most recent call last):
(pid=41697)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/weakref.py", line 117, in remove
(pid=41697) TypeError: 'NoneType' object is not callable
(pid=41720) Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7f17b1829730>
(pid=41720) Traceback (most recent call last):
(pid=41720)   File "/BiO/Access/yahoyoungho/Store/Cardiomics/python_dir/python_project/lib/python3.5/weakref.py", line 117, in remove
(pid=41720) TypeError: 'NoneType' object is not callable

similar error for mat_np = mat.to_numpy()

Hi @yahoyoungho, thanks for posting!
This looks like an issue related to Ray. I have created an issue in the Ray repo (https://github.com/ray-project/ray/issues/6198) to track this. Thanks again for reporting!


Sieve of Eratosthenes method for computing prime numbers in C

ISSUE: #137
Added code for implementing Sieve of Eratosthenes in C.
Updated README.md.
PLEASE PLEASE PLEASE READ AND CHECK THE BOXES BELOW

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked the issues to see if your request isn't assigned to someone else?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] If your submission is to improve an existing code, have you created an issue to specify that?
[x] Don't tag anyone unless specifically requested to do so
[x] Don't create any subfolders unless specifically requested to do so.

New Code Submissions:

[x] Does your code work locally?
[x] Have you cleaned your code for better readability? (no extra unnecessary lines, etc.)
[x] Have you updated the README.md file to add the link to your code?

I went for a naive solution, though we need to iterate the loop only through odd numbers because 2 is the one and only even prime number. Is this what you were looking for? @ricardoprins

close :)
but what about the max value? do we really need to evaluate all the way through n? what if we were to run that code for  n=10^7?
btw, you can edit it later to add multiple possible solutions! it will certainly be useful for those who are aiming to learn more about efficiency in algorithms


[BEAM-1886] Remove TextIO override in Flink runner

This is a duplicate of #2537. The tests work locally but not on Jenkins, I'm trying to figure out why that might be.

Run Flink ValidatesRunner

Coverage remained the same at 70.136% when pulling ecb2b4ce0b94392f4698fa411ee0263c9101e97e on aljoscha:finish-pr-2537-remove-flink-source into 104f9823563c4a2cd2ef9495e9a16b3a219dd49b on apache:master.

Coverage increased (+0.01%) to 70.146% when pulling ecb2b4ce0b94392f4698fa411ee0263c9101e97e on aljoscha:finish-pr-2537-remove-flink-source into 104f9823563c4a2cd2ef9495e9a16b3a219dd49b on apache:master.


Bump edge to 0.14

release notes?

release notes?

Added as part of this PR: https://github.com/netfoundry/ziti-cmd/pull/89


Bug: terraform plan fails not able to read storage account queue because no private dns entry created

Steps to reproduce
I was using the project defaults to not create private link/a-record for storage account queue.   This caused the below error on the terraform plan.  I then turned on the private links/a-record for storage account queue and the /28 network ran out of ip. addresses for the storage subnet.   I changed it to /27 to fix that.
Error Message
Error: retrieving queue properties for Storage Account (Subscription: "xxxxxx"
│ Resource Group Name: "xxxx"
│ Storage Account Name: "xxxxx"): queues.Client#GetServiceProperties: Failure sending request: StatusCode=0 -- Original Error: context deadline exceeded
│
│   with module.data_landing_zone.module.datalake_workspace.azurerm_storage_account.datalake,
│   on ../../modules/analytics/datalake/datalake.tf line 1, in resource "azurerm_storage_account" "datalake":
│    1: resource "azurerm_storage_account" "datalake" {

Screenshots
No response

Thanks @opme . I will review this tomorrow or on the weekend.

Hi @opme, The above error suggests that you or your runner was not able to connect to the private storage account. This is is not related to limited IP space. I have the Data Landing Zone created in my subscription and there is exactly one IP left in that subnet:

Can you please check once more?


local test network file

Is missing the network ID of the X chain
I got this error with the command "ash avalanche subnet list"
Error loading network: Config error: failed to deserialize configuration from 'terraform/multipass/local-test-network.yml': missing field id

Hi @pedro-sys,
What version of Ash CLI are you running? (ash -V). You are probably running an older version.
Please upgrade to v0.2.2 and let us know if you still have an issue.
Here's what the command looks like on my side:
ash -c terraform/multipass/local-test-network.yml avalanche subnet list --network local

Found 5 Subnet(s) on network 'local':
-------------------------------------------------------
- 29uVeLPJB1eQJkzRemU8g8wZDw5uJRqpab5U2mX9euieVwiEbL:
  Type: Permissioned
  Control keys: ["P-local18jma8ppw3nhx5r4ap8clazz0dps7rv5u00z96u"]
  Threshold:    1
  Blockchains list (1):
  - AshLocalEVM:
    ID:      RfX8YRUHePxFENBZFwaNt1tP6CR6RQ4hJJ5AqYv49LRoSKniK
    VM ID:   srEXiWaHuhNyGwPUi444Tu47ZEDwxTWrbQiuD7FmgSAQ6X7Dy
    VM type: SubnetEVM
------------------------------------------
-<PHONE_NUMBER>1111111111111111111111LpoYY:
  Type: PrimaryNetwork
  Blockchains list (3):
  - P-Chain:
    ID:<PHONE_NUMBER>1111111111111111111111LpoYY
    VM ID:<PHONE_NUMBER>1111111111111111111111LpoYY
    VM type: PlatformVM
    RPC URL: http://<IP_ADDRESS>:9650/ext/bc/P
  - C-Chain:
    ID:      2CA6j5zYzasynPsFeNoqWkmTCt3VScMvXUZHbfDJ8k3oGzAPtU
    VM ID:   mgj786NP7uDwBCcq6YwThhaN8FLyybkCa4zBWTQbNgmK6k9A6
    VM type: SubnetEVM
  - X-Chain:
    ID:      2eNy1mUFdmaxXNj1eQHUe7Np4gju9sJsEtWQ4MX3ToiNKuADed
    VM ID:   jvYyfQTxGMJLuGWa55kdP2p2zSUYsQ5Raupu4TW34ZAUBAbtq
    VM type: AvalancheVM
    RPC URL: http://<IP_ADDRESS>:9650/ext/bc/X

ash_cli 0.2.0
Ok I'll try

Hi @pedro-sys, I just released v0.2.3 both on GitHub and on https://crates.io. You should be able to install it whatever your preferred method!

Just installed v0.2.3 :)
works fine !!


Update workspace versions when running bolt add on an existing dependency in the project root

We updated the bolt add command in the last version to re-run yarn add when run from the project root to allow installing new versions of an existing dependency without needing to run bolt upgrade which behaves differently (it recursively upgrades transitive deps).
As part of this work, we forgot to also update the versions of the dependency being added in each workspace in the repo. Resulting in version mismatch errors on subsequent runs of bolt until workspace versions were manually updated.

Released in 0.24.3


Added support for Swifts UUID type

I was cleaning up my code and had a nasty work around for getting uuid types, so i added support for those.

nice. i'll be reviewing this tomorrow

@Hiiragisan09 thanks! this will be available in the next release 1.1.0; until then - develop can be pointed to 🎉


[bug] Autoware on Melodic fails to build: lidar_apollo_cnn_seg_detect.

Bug
Error while compiling #2032
error: ‘iota’ is not a member of ‘std’

Specifications

Ubuntu version: 18.04
ROS version: Melodic
Autoware branch: feature/melodic

@amc-nu can you check the compiler? http://www.cplusplus.com/forum/beginner/230449/

gcc-7 7.3.0


Adding content

This is an iteration of the website with the Getting Started, Why Neuroshapes, INCF/Neuroshapes SIG, Adoption realized.
Yet to be added are the Specifications and Get Involved Sections

Closed because of git user error, intended changes are replicated in #239


Add seqkit to coidb dependencies; issue in clustering

Hi, a couple of snags I hit. I'm running on a cluster using slurm job manager, so the run occurs in a near-default system environment, running with a conda environment containing only coidb.
Initially, remove_non_standard fails because seqkit is not installed. An easy fix to install seqkit into the environment, just a note that it's a dependency missing from the coidb conda install.
I then hit a more confusing issue, that cluster hangs for a long period, in this case for about 12 hours, before crashing. The end of the STDERR log looks like this:
[Tue Jun 21 12:48:50 2022]
rule cluster:
    input: bold_filtered.fasta
    output: bold_clustered.fasta
    log: logs/bold/cluster.log
    jobid: 3
    reason: Missing output files: bold_clustered.fasta; Input files updated by another job: bold_filtered.fasta
    threads: 10
    resources: tmpdir=/tmp, runtime=600

WorkflowError:
Failed to open source file <home>/miniconda3/envs/coidb/lib/python3.10/site-packages/coidb/envs/cluster.yml
FileNotFoundError: [Errno 2] No such file or directory: '<home>/miniconda3/envs/coidb/lib/python3.10/site-packages/coidb/envs/cluster.yml'
Removing output files of failed job cluster since they might be corrupted:
bold_clustered.fasta
Shutting down, this might take some time.
Exiting because a job execution failed. Look above for error message
Complete log: .snakemake/log/2022-06-21T120759.823981.snakemake.log
/var/spool/slurm/slurmd/job85596/slurm_script: line 13: 674824 Bus error               (core dumped) coidb -j 20

As you can see, it started this rule about 40 minutes after starting the run. The run failed at 00:17 this morning.
The logs/bold/cluster.log file looks like this:
Reading bold_filtered.fasta and clustering with vsearch...
Records read: 6540815
BOLD IDs clustered: 517543
Sequence clusters: 678981

Let me know if you need any more info!

Hi @tjcreedy and thanks for submitting this issue!
I've updated the bioconda recipe so that seqkit is now a required dependency which should take care of the first problem.
The second issue is strange because to me it looks like clustering completed but the workflow complained about a missing file (envs/cluster.yml). This is an old reference that I've forgot to delete. The line of code has now been removed from the package and hopefully the issue is fixed in the new version of coidb. I'm updating the bioconda recipe now but if you don't want to wait for the next version to be uploaded to anaconda you can download the latest release from the Releases page and install directly from there.
Let me know how it goes!

Hi, I've run again and it works! I get all the bold_* files I expected. Thank you.
One minor point - I note you've updated the README.md, but I found the original version with the instructions very handy - has this moved somewhere else?

@tjcreedy The original instructions have now been placed in the repo Wiki.


Major Possible Update: Support For Times.

We're using Django-Recurrence in a production server, and we largely deal with events. We would like to see a DateTime field instead of a DateField alone so it becomes hugely easier to tackle trickier issues like timezone conversion, and event management. Please feel free to give an explanation as to why this wasn't the design initially thought of.
Larger issue: We're using the recurrence field along with a TimeField in our project but the problem is that the TimeField in Django is not TimeZoneAware which causes weird and sometimes bizarre errors. We've tried our best to fix the issue but I think it's high time django-recurrence supported DateTime instead of just a Date.

@aekanshd , the RecurrenceField is actually a TextField not a DateField as far as I understand.
According to dateutil, each rule could have a dtstart which is an aware datetime. In this package, this dtstart can be set generally for the ruleset, but not per rule.  I don't know why the author made this choice.
I'm also using a TimeField alongside the RecurrenceField, but this means that I would need to duplicate this in order to have more than one specified time in a ruleset, with bothers me. I have a need to create a recurrence ruleset that would happen every weekday at 9am and 3pm.
I can accomplish this with 1 vanila dateuitl ruleset, but not with 1 django-recurrence ruleset, since I can only associate one time (either 9am or 3pm). I would need 2 django-recurrence rulesets with one time each and would need to get the earliest of the 2 occurrences every time which would alternate between the 9am and 3pm rules. I would prefer to take advantage of dateutil's algorithm only...
I'm considering abandoning this package because of this. I have created a vuejs frontend for my endusers with  https://github.com/jakubroztocil/rrule js library which is inspired by dateutil.

@aekanshd some other thoughts about this :
I looked at the dateutil library directly to check the datetime support. As the RFC 5545 specifies every rule has its own DTSTART property which gives the time as we want. There is one drawback though. In dateutil every component of the ruleset, including and excluding rules and dates, must be of the same type.
So if you have an including rule which specifies a certain time, if you want to exclude a specific day, you need to enter that day with the same specific time. Otherwise, you get an error. I have also chimed in a discussion there regarding this issue.
@dominicrodger seems to have "solved" this issue in this package imposing the fact that only one time is allowed. One dtstart is passed independently from all the rules and if you look at the code, when this package converts its ruleset to dateutil's ruleset, it passes the same dtstart to all rules and dates (including and excluding ones).
As my understanding, this package offers a great admin widget (I did not test the regular non-admin widget) and an abstraction of times making us work with date only for the rules and inserting the same time information for all rules/dates.
@dominicrodger , can you chime in and shed some light on it ?

Hi @duduklein - I don't have a lot of light to shed here unfortunately - your assertion that this library deals with dates only is correct - where I've used it I just add a separate field for time on the model, I've never needed anything more complicated than that.
I don't actually use this library now - so my support here is mostly just merging fixes where I am comfortable with them, and pushing releases to PyPI. If someone else wants to take over ownership, I'd be more than happy to hand it over.


[CH] Support json_tuple function

What changes were proposed in this pull request?
Support json_tuple funtion for spark in clickhouse backend， the related pr: https://github.com/Kyligence/ClickHouse/pull/361
How was this patch tested?
test by manual

please add some ut for this function, btw, it may need to support this function in ch backend?

please add some ut for this function, btw, it may need to support this function in ch backend?

ok, I will add some ut. and I have support this function in ch backend in pr : https://github.com/ClickHouse/ClickHouse/pull/47343
but I think this also can archive by JsonExtract function, i will open the pr to see whether it can be accpeted by clickhouse

please add some ut for this function, btw, it may need to support this function in ch backend?

ut added done. @zzcclp

Can one of the admins verify this patch?

cc @zzcclp @liuneng1994


Remote-FTP 1.1.3 Error

Atom keeps warning me to rebuild the remote ftp:
binding@unknown – Cannot find module '/Users/sakai/.atom/packages/Remote-FTP/node_modules/fsevents/lib/binding'

Thanks for report.
Duplicate of #839


Invalid None values in anytone CSV

When a channel doesn't specify certain "required" fields, the CSV file is written out with the string representation of None instead of Off. I think the CPS would ignore this value and have no harm, but need to confirm.

The CPS does ignore this value

I'd still like to fix it for posterity though

The CPS does ignore this value

I'd still like to fix it for posterity though


Mistake function argument in sample script(readme.md)

just a little help if there is someone had confuse like me,
please check get_base64_hashed function argument .
this is correct one.
get_base64_hashed('user_passw0rd', salt, iter, hashlib.sha256)
not this one
b = get_base64_hashed('user_tried_password', iter, salt, hashlib.sha256)

Thanks for the notice. That's my typo in the document. Doc updated. Codes are fine.


[PF-2333] Fix test failures caused by IAM delay

GCP has been slow to propagate IAM permissions for the past ~week and a number of CLI tests have been failing as a result. This adds polling to the appropriate places to verify that a user has permission in a project.

GHA for this repo are broken, I think https://github.com/broadinstitute/terraform-ap-deployments/pull/869 will fix

Tests are failing in GHA but passing fairly consistently locally - I'd like to merge this and try running it in Verily's environment to confirm if the issue is in GHA setup here.


Upgrade to C# 6

Would you be open to upgrading the code to C# 6?
If not today, then at a later date?

I will re-open this when C# 6 becomes mainstream.


Automatically pick up sign in "user code" for Linux

Currently the linux implementation for Live Share requires that a user enter a user code after sign in is complete in the browser.

Ideally, like Mac and Windows, the Linux version of VS Live Share should automatically sign you into VS Code after you've completed the sign via the web browser rather than requiring the user code be copied and pasted.

This is resolved as of 0.3.317


setting sps->direct_8x8_inference_flag doesn't take level into account

According to Rec. ITU-T H.264 (10/2016) A3.3.2 A-4, direct_8x8_inference_flag should be 1 when level beyond or equal 3, but all set to 0 now.

thank you for the input! Rec. ITU-T H.264 (10/2016) A3.3.2 A-4, is only for Main .... Profile, should we add a profile check in PR#3404 ? thank you

more discussion at #3404


Conditional type evaluation is stopping at the first possible branch

TypeScript Version:  2.8.0-rc

Search Terms: conditional types
Code
export type RequestResponse<T> =
	T extends IGetRolesRequest ? IGetRolesResponse :
	T extends IGetSettingsRequest ? IGetSettingsResponse :
	T extends ISetSettingsRequest ? ISetSettingsResponse :
	T extends IHasPermsRequest ? IHasPermsResponse :
	object;

Expected behavior:
When given the appropriate request interface, the matching response interface should be the expected type.
For example: RequestResponse<IGetSettingsRequest> should return IGetSettingsResponse
Actual behavior:
Every interface given to RequestResponse is having the expected response type as IGetRolesResponse
Further evidenced here:

What do your interfaces look like?

Oh shoot, now that you mention it, most of them contain the same structure or at least one shared field, with the name only really existing for grokking purposes. I see now why this is not working. Thanks for the inadvertent hint.

Wish we could do like
type Foo<T> = T is Bar ? Baz : Bar;

for absolute type conditions, rather than structural comparisons

I was able to come up with a solution that still allows me to use conditional types to map my request interfaces to their associated response interface. By creating a base interface
export interface IRequest<T>
{
    identifier?: T;
}

I am able to then have each request interface contain a unique identifier, differentiating them structurally from the other interfaces, even if they technically contain all the same fields.
export interface IGetSettingsRequest extends IRequest<'IGetSettingsRequest'> { ... }

It's working great. 👌


Document how to use nextConfig with the plugin

Closes #418.
Add some documentation on how to combine next-translate with custom webpack config for example.

@allcontributors please add @tperamaki for documentation


UITextDisplayer is mishandling lineAlign

Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
3.4.5
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from main?
Yes
Are you using the demo app or your own custom app?
Custom app
If custom app, can you reproduce the issue using our demo app?
Have not tried
What browser and OS are you using?
Electron, on Windows
The UITextDisplayer is using lineAlign improperly.  This is causing subtitles with lineAlign == "end" to be drawn at the top of the screen.
Here's the relevant code:

It looks to me like the code for HORIZONTAL_TOP_TO_BOTTOM and VERTICAL_LEFT_TO_RIGHT is swapped.   If the text is horizonal. lineAlign should affect left & right; if it's vertical is should affect top & bottom.  This code has it the other way around.

I notice you deleted the part of the form that asks for content.  Can you provide us with a subtitle sample that demonstrates the problem?  That would both help us understand the issue and create a regression test to make sure we don't make this mistake twice.

I was testing with "Doctor Strange" and "The Mandalorian" S1E1 on Disney+ using Hearo.  Testing using Hearo will be a little tricky: subtitles are broken in the current release, and the next release will include a hack that fixes the problem.  But I could create a test build that shows the problem if that's useful.

I've attached an m3u8 plus one of the VTT segments.  Let me know if you need anything else.
composite_cs_NORMAL_1b145a3c-88fb-4fd6-ba4b-e6218e77b6be_daf3602b-9036-47f9-9ff9-88b1f81adbde.m3u8.txt
seg_00000.vtt.txt
.

The settings that the WebVTT file has is: line:95%,end

I was wrong about what's causing the problem here.  Please ignore my reference to the specific spot in the code.
In the Mandalorian, all the titles appear at the top, but some are supposed to be at the top and some at the bottom.  The relevant cue data is:
//text at top
line: 14.81
lineAlign: "start"

//text at bottom
line: 85.19
lineAlign: "end"

In the first one, the top of the text box should be at 14.81%.  In the second, the bottom of the text box should be at 85.19%.
I'm don't know what's wrong in the code that's causing the problem, but it should be fairly easy to duplicate.

FYI, here's my hack to fix the text.  I change lineAlign to "start", convert the line value to line counts (instead of percent) and adjust by the number of lines in the text.
          if ((cue.lineAlign === "end") && (typeof cue.line === "number") && (cue.line > 50) && (cue.lineInterpretation === 1)) {
            cue.lineAlign = "start"
            let newlineCount = 0;
            for (let i = 0; i < cue.payload.length; i++) if (cue.payload[i] === "\n") newlineCount++;
            cue.line = -(100 - cue.line) / 5 - (newlineCount - 1)
            cue.lineInterpretation = 0
          }

Can you test if the main branch still has the problem? Thanks!

@avelad Can you provide some guidance on building my app with the main branch code?
I pulled the latest code, built with python build/all.py and then copied the dist folder over to my project's node_modules/shaka-player folder.  Is there something else I should do?  I'm not seeing any subtitles at all now.
I've been building with 4.3.7.  Are there changes I need to make for the latest code to work?


Use environment variables for configuration

This fixes #304 - environment variables can be used in the Caddyfile with the {$VAR_NAME} syntax.

Cool. I think we don't want to do this in the parser, though. The Replacer type is particularly good at this... it just that the replacement happens later.
Using the Replacer also gives each directive discretion over whether it wants to allow replacements on an argument. This may or may not be what the user would expect. The current PR forces the env var replacements right away for all tokens in the Caddyfile, but the Replacer would give the directives some control. I kind of like the idea of the latter.

As I read Replacer it is for replacing strings in transit during a request. I can't find anywhere that use Replacer for anything else - what am I missing?

Yeah, so far the Replacer is just used during requests. That's why I'm still not sure if it belongs in the Replacer, but I will have to think it over to make sure this really belongs in the parser.

fwiw I was looking for a place where the whole Caddyfile is present in one string as I initially wanted to do the replacement there. I see it as a short cut to get dynaic values into the configuration with no choice to the middleware/directives (I really have to re-state that I litterally just started using Caddy a week ago).

@mbanzon Hi, hope you're making progress.

@abiosoft still on a pause with this - want to see the deep thoughts of @mholt about where this environment use should be put in the code. So far the changes in this branch/PR works in my setup.

Yeah, my bad. It does feel weird to put that logic in the parser, but it also doesn't seem quite right to put it in the Replacer... will mull it over some more, look around the code for the best place.

When would the directives require control over the environment replacement?

If regex is the concern for it not to reside in the parser, it can be done without regex.

Okay, this doesn't belong in Replacer. Those are executed at request time and no need to slow down the request handling with such static values as env variables.
This is looking fine -- but it will need tests. Can you write some? :smiley:

Sure - I will look into it ;-)

Tests added - @mholt

I've made the changes we discussed. Regex is no longer used and it now supports the Windows {%ENV_VAR%} notation as well.

Thanks! Like a champ.


fix: inherit environment variables

Permit environment variables in data sources when running via
gramps command.

Use case: some api's need an api key, and during development I may want the api keys defined as environment variables that get wiped out when running "yarn live-data" on a datasource.

This resolves issues I'm having with my nvm node install as well. 👍


respect vispy max texture limits

Description
This PR contains parts of #737 that prevent vispy segmentation faults when the array sent over is too large by downsampling the array an emitting a warning that downsampling is happening. For 2D rendering it will read the max texture limit from your GPU, i havn't figured out how to read the value for 3D so have hard coded it to 2048, the value on my machine.
To test you can use
img = np.random.random((20_000, 20_000))
napari.view_image(img, is_pyramid=False)

note we need is_pyramid=False otherwise we will try and autogenerate a pyramid (something that maybe fixed in a future PR but is out of scope for this one)
Type of change

[x] Bug-fix (non-breaking change which fixes an issue)

How has this been tested?

[x] This PR adds two tests in test_vispy_big_images.py (one 2D one 3D) both of which currently fail on master

Final checklist:

[x] My PR is the minimum possible work for the desired functionality
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works

I will merge this after the tests pass. I think in the future we could consider doing better downsampling, so using a mean instead of just a stride, and we can also consider whether this limiting is done inside out vispy view code or any DataSource like object that @jni or @d-v-b might be considering adding.
For now though this will prevent seg faults with a warning which is an improvement


conda activate conda-environment not working on windows

Environment data

VS Code version: 1.39.2
Extension version (available under the Extensions sidebar): XXX
OS and version: Windows 10 Enterprise 1809
Python version (& distribution if applicable, e.g. Anaconda): conda 4.7.12
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda 4.7.12
Relevant/affected Python packages and their versions: None
Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): XXX

Expected behaviour
In bash shell:
conda activate PIMSmyApp
-> activates environment PIMSmyApp
This does not work even after running (as advised in the error message)
 conda init bash
Actual behaviour
conda activate base
generates the following error message:
CommandNotFoundError: Your shell has not been properly configured to use 'conda activate'.
If using 'conda activate' from a batch script, change your
invocation to 'CALL conda.bat activate'.

To initialize your shell, run

    $ conda init <SHELL_NAME>

Currently supported shells are:
  - bash
  - cmd.exe
  - fish
  - tcsh
  - xonsh
  - zsh
  - powershell

See 'conda init --help' for more information and options.

IMPORTANT: You may need to close and restart your shell after running 'conda init'.

Steps to reproduce:

conda activate base

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
XXX

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)
XXX

Thanks for letting us know about this, @mfittere.  I'll take a look at this today.

It isn't clear from your description how this relates to the Python extension of VS Code.  We'd like to try reproducing the problem, but will need more information:

how are you triggering this problem is VS Code?
what is in your workspace settings.json file?
are you only seeing this problem in the VS Code terminal window?

Hello,
thank you for following this up. I think I might have chosen the wrong channel as it might be a problem with the git bash shell.

I am triggering this problem by trying to activate any environment, most simply with the base environment:
conda activate base

This is the content of my settings.json file:
{   "python.pythonPath": "C:\\Users\\fitterma\\AppData\\Local\\Continuum\\anaconda3",   "telemetry.enableCrashReporter": false,   "telemetry.enableTelemetry": false,   "terminal.integrated.shell.windows": "C:\\Users\\fitterma\\AppData\\Local\\Programs\\Git\\bin\\bash.exe" }

This problem occurs in the git bash shell and also in VS Code choosing the bash shell. I only noticed it right now. Are you aware of any fix for this?

Many thanks!

@mfittere, I'm not sure how git bash interacts with conda.  You are best off either posting something to stack overflow or checking the conda documentation/support.


element: 1.7.25 -> 1.7.26

Motivation for this change
https://github.com/vector-im/element-web/blob/v1.7.26/CHANGELOG.md
https://github.com/vector-im/element-desktop/blob/v1.7.26/CHANGELOG.md
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS

[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Ported to stable as 10cde818493537790bdbab867a0ead77ca5ace2c.


[BUG] Discovery timed out with mdns error "Browse failure"  while paring device in iOS 16.6 beta3

Reproduction steps
We are using Matter Support Framework to pair the device into our own fabric.
Everything is ok in iOS 16.5.
But in iOS 16.6beta3, we are encountering the issue:  Mdns: Browse failure.
In the logs, we can see that the device has joined the system fabric:
2023-06-19 14:02:01.493073+0800 Runner[653:53799] did scan wifi
2023-06-19 14:02:02.968257+0800 Runner[653:53799] validate device credential
2023-06-19 14:02:20.010459+0800 Runner[653:53799] didJoinInSystemFabric: {
deviceId = "1B96EE31-6A0D-4720-B922-EA6010E8A457";
manualCode = "MT:S6AA0C0R15BRCW4L600";
}
but when we call the method:
[self.chipController pairDevice:self.commissioningData.deviceId onboardingPayload:manualCode error:&error]
the error occured.
We have post a feedback with feedback id FB12342761 in FeedbackAssistant.
Bug prevalence
Always
GitHub hash of the SDK that was being used
iOS 16.6 beta3 MatterSupportFramework
Platform
darwin
Platform Version(s)
16.6 beta3
Anything else?
No response

@zzz2016 Thank you for reporting this, and the pointer to the feedback id.  This is an issue in the 16.3 betas in Home and is being worked on.  Not an issue in the Matter SDK, per se, though https://github.com/project-chip/connectedhomeip/pull/27282 was related.


Devon m bias plot

This branch implements a (somewhat) basic methylation bias plotting program and also enables PileOMeth to use inclusion/trimming bounds. I ended up just using the same syntax that's used in bison for this, since it'll cover all use cases that at least I can think of. Changes to that are certainly welcome, of course.
I should note that in the process of doing this, I found that the read pair overlap detection provided by HTSlib has some issues. It will miss any pair that overlaps but where read 2 (or 1 for that matter) has been heavily trimmed such that the fragment insert size is more than twice the shorter read's length. With BS-seq (and RRBS in particular), this isn't exactly an uncommon occurrence. I'll actually start a new branch to work on that, since I'd like to start using PileOMeth more and this problem is a deal-breaker for me.
BTW, it'd make sense to merge some of the code between "PileOMeth" and "PileOMethMbias" and then put them both in a single executable (so "PileOMeth mbias" and "PileOMeth extract" or something like that).

If you keep this up, PileOMeth is going to become extremely useful.

That's the goal :) Anyway, let me know if you have any issues with this or the other pull request I just created. If not I'll merge them.

I just gave it a quick read, but looks good. I like the SVG idea.

Yeah, I was trying to come up with a convenient visualization method and then I remembered Pierre Lindenbaum posting some example visualizations in SVG on twitter. It turns out that it's a pretty convenient way to do things (well, more convenient than adding a non-standard library dependence).


Start and end point

Hi,
is there an easy way to set the start position of an track to a specific duration (e.g. start the track at 8s from beginning)? Same problem with the end of a track.
I hope you will have a solution for this problem.

Hey, sorry I never got back to you.  That feature isn't in TinySound at the moment.  I could imagine adding such a feature to the Sound interface, with the play function taking a start and stop position.  Were you thinking about this feature more along the lines of with the Music interface though, to allow for looping?  In any case, I hope you were able to find a workaround.


motors do not work on newest (2015-05-01) image

I tried to use python-ev3 on newest (2015-05-01) version of evdev. Sensors, sound, lcd and leds do work but motors fail to work. When I try to instantiate MediumMotor or LargeMotor I get NoSuchMotorError. Forcing port does not help. I am aware of issue #28

I checked the path in /sys/class:
ls /sys/class/tacho-motor/
motor0  motor1  motor2

I started debugging motors by hand as described here and they work perfectly. I'm starting to debug/refactor the library.

CC: @sharived (ref: ev3dev/ev3dev#323).

I just put in a pull request for the changes I made to get the motors working.

@sharived @dlech
Thanks a lot. A new release is published.


Add users public key to authorized_keys

https://github.com/Shippable/pm/issues/10359

this is done, closing


Adding detect_flow and detect_flows functions

Added the following two functions to allow users easily create optical flow and optionally save the data (as images and as .pt data files respectively).

detect_flow: detects optical-flow for a single image-pair
detect_flows: detects optical-flow for a series of image-pairs

The detect_flow() function makes sure of managing memory (grabage collection + emptying cuda cache), while evaluating and saving optical flow  information on a pair of images. When I tried running the RAFT demo to create a series of optical-flow images, I found the colab notebook running out of memory. These functions take care of the memory aspect and make it easier for the user to apply optical flow on image-pairs.

Gif Source: LinkedIn Post

@datumbox I am not sure if I should add this code where I did. I am not sure if this should go under torchvision.utils. I have not added any tests yet. Once it is determined where this code should be added to, I will work on adding the tests as well.
Also, I will post a correction/update to the RAFT demo with these functions.
current path: torchvision/models/optical_flow/detector.py

@sugatoray First of all thanks for the contribution.
It's not clear if this should be handled in the references of TorchVision or if this should be a separate utility added on your own repo. That's because we try to keep references as simple as possible and avoid multiple entry points. I will let @NicolasHug who has led the effort of supporting optical flow to provide input about whether specific optimisations of this PR are worth adopting on the current scripts.
A couple of notes that will help you maximise the chances of getting your contributions merged: If a PR touches more than 20 lines of code, it's usually recommended to first open an issue and discuss the changes. Discussing the reported issue with the rest of the community can help us decide if the reported is indeed an problem and how it should be addressed. For more info on the contribution process please check this

@datumbox Thank you. I will keep the "20 lines" in mind for future. Out of the two functions, detect_flow helps detect a single flow-pair. If this function is available, that would work as a helpful utility for people to use it directly, alike other functions in torchvision.utils.
Also, for the demo notebook, I could push a separate PR, to include similar changes, but without the specific function in question (detect_flow).

Thanks a lot for the PR @sugatoray . As @datumbox already noted, this kind of util is usually not included in the models/ namespace; it's more likely to fit in the utils/. But here, it seems that this function is somewhat redundant with our RAFT example.

When I tried running the RAFT demo to create a series of optical-flow images, I found the colab notebook running out of memory

Could you please provide us with some details here? If the example runs out of memory, perhaps there's an issue that we can fix directly there :)

@NicolasHug Yes, it ran out of memory.

@datumbox So, will it be okay if I move the functions detect_flow and detect_flows under utils/?

@NicolasHug The memory limit was struck when I tried running the last section to create multiple frames in a loop. Also the for loop had some obvious typos.

Thanks for the details @sugatoray . We'll be happy to review a PR that fixes these issues in the example. As noted there, this snippet that we commented out is only a starting point, not a full fledge solution.

@NicolasHug I will send a PR with the fixes to the snippet section.

@sugatoray Shall we close this PR? I understand we are going ahead with a different approach, right?

@datumbox Would it be possible to leave this PR to remain open for the time being, while I work on the other PR and submit it?
But, I was wondering if these functions could be added to utils. Please let me know your thoughts on that. Also, please let me know if you believe some changes to the functions could be a better option.
Thank you.

@sugatoray Happy to leave the PR open if you prefer. Please consider closing it once you are happy with the other PR to keep things tidy.
From @NicolasHug response, I understand that this is not something we probably want on the utils of references (this is something that people can't import from TorchVision anyway because references are not part of the binary). Nicolas, is my understanding wrong?

I'm not sure yet whether this would make sense as a util in the references either. It will depend on what are the needed changes to the snippet from the example, and why the changes are needed. It's important to keep in mind that the snippet is really a starting point, it doesn't pretend to be anything else, and there might be blind spots. The typos mentioned by @sugatoray are definitely worth fixing though.

@datumbox and @NicolasHug Let me send the PR to introduce minimal changes to the RAFT example. Once it is working and the example is updated, perhaps you can take a more objective call on whether the functions in this PR are appropriate for torchvision.utils or not.

utils: torchvision/utils.py

Does that sound reasonable to you?

Sounds good but this is definitely something we can't put on torchvision.utils. This area is not meant for model inference utilities. Let's get clarity over what the changes are and decide if there is any need to modify the examples.


Could not sync

Could not find artifact pro.husk:mysql:pom:1.2 in papermc-repo (https://papermc.io/repo/repository/maven-public/)

Have you got my repo listed in your pom?

I have this.

papermc-repo
https://papermc.io/repo/repository/maven-public/

husk
http://maven.husk.pro/repository/internal/

<dependencies>
    <dependency>
        <groupId>org.bukkit</groupId>
        <artifactId>bukkit</artifactId>
        <version>1.14.4-R0.1-SNAPSHOT</version>
        <scope>provided</scope>
    </dependency>
    <dependency>
        <groupId>mysql</groupId>
        <artifactId>mysql-connector-java</artifactId>
        <version>8.0.18</version>
    </dependency>
    <dependency>
        <groupId>pro.husk</groupId>
        <artifactId>mysql</artifactId>
        <version>1.2</version>
    </dependency>
</dependencies>

Awesome, thanks. I've had a look, and the issue should now be fixed :)
Can you please try compile again?

It's still the same. It look like that your dependency looks for repository only in https://papermc.io/repo/repository/maven-public/ and not in  http://maven.husk.pro/repository/internal/

Issue was resolved.
If anyone reads this with the same issue, try using the -U flag in your build or clear your .m2 cache
Thanks


The json-c is not needed anymore

@steffengy Can you please review?

Thanks

Hi, Do the doc shouldn't be updated: http://docs.zephir-lang.com/en/latest/install.html

https://github.com/phalcon/zephir-docs/pull/39


Document has been updated with grammar correction

This document has been updated with the following grammar correction:
"lets assume" should be "let's assume"

Thanks @AzureMentor for taking the time to submit this PR! Good catch. Your commit will be merged and this article update is in flight. After the updated article is published, GitHub will list you as an article contributor.
Thanks again for this feedback, your suggestions help improve our documentation.
#sign-off


PyPI does not honor package name from author in some cases

Describe the bug
PyPI's UI does not honor the package name I specify in my pyproject.toml file.  This leads to confusion and incorrect (or at least unintentional) installation instructions on the PyPI front page of the project.
Take for example flufl.i18n.  I clearly call the project that in its pyproject.toml file.  That's the name I want to advertise the package as, and this intentional -- and legal -- so PyPI should honor that, even if the packaging tools normalize the upload file name.  But this doesn't happen, as this screenshot illustrates.

The URL is also normalized: https://pypi.org/project/flufl-i18n/.
Expected behavior
I would expect PyPI at least to display flufl.i18n 5.0.1 on the project page, and provide a pip install command as pip install flufl.i18n.  If it doesn't do this, it directly conflicts with my intentional choices and my own documentation.
I think the URL should also be non-normalized, but I'm a little less concerned about that.
To Reproduce
Create a project with a dot in its name.  Use a modern packaging tool that support pyproject.toml (flufl,i18n uses PDM).  Upload that package to PyPI.
My Platform
n/a
Additional context
This may be related to the meta issue #12316 but I didn't see this specific issue discussed there (I could have missed it).  It's also related to this discuss.python.org thread.  It's probably also related to the root cause for a downstream bug report in GNU Mailman.

PyPI respects the Name field in the project metadata of the artifact it was provided. In this case, it was flufl-i18n.
This was set by the build backend you were using, which consumed it from pyproject.toml before producing your distributions. If the value in your pyproject.toml and the value in your distributions metadata don't agree, that's a bug in your build backend, not with PyPI, as PyPI is not aware of pyproject.toml at all.

(And to be clear, if the Name value was flufl.i18n, PyPI would respect that, both in the web UI and URL. See https://pypi.org/project/jaraco.develop/7.22.1/ for a recent example)

Note that PyPI will rename the project to whatever the most recently uploaded artifact's Name field is. So this will be remediated upon your next release with a backend that doesn't normalize the name.

Thanks @di - that's what I suspected.  In this case I'm using PDM and pdm-backend.  I bet build backends are stuck between a rock and a hard place here, as evidenced by the discuss.python.org meta thread.  I want to at least capture the issue so we can begin to unwind and fix the ecosystem.

@warsaw I agree with your intent, but I don't think there's anything actionable for PyPI to do here.
Given that PEP 621 says this about the name field:

Tools SHOULD normalize this name, as specified by PEP 503, as soon as it is read for internal consistency.

I think if you disagree with this behavior in build backeds, you probably need to take it up as an ecosystem-wide issue instead (which you kind of already have in your discourse thread).

The PEP that I hope to post this weekend clarifies that section of PEP 621, because I think that segment goes against what most people expected.

@dstufft 💯
Thank you!

@warsaw Given that a future PEP would likely resolve this, and that PyPI would likely not need to make changes as a result of that PEP, is it OK with you if we close this?

Yep, and thanks @di!

@di I'm reopening this issue because I think there may still be a problem on the PyPI side.  pdm-backend has been fixed to no longer normalize the package name metadata, but PyPI is still displaying the normalized name and pip install instructions.
Let's look at flufl.enum 6.0.1.
.whl METADATA excerpt:
Metadata-Version: 2.1
Name: flufl.enum
Version: 6.0.1
Summary: A Python enumeration package
Keywords: enum

sdist PKG-INFO excerpt:
Metadata-Version: 2.1
Name: flufl.enum
Version: 6.0.1
Summary: A Python enumeration package
Keywords: enum

Both metadata files are non-normalized, as we all now expect and want.
However, look at the PyPI page.

It is still displaying the normalized name and instructions.  I've verified the metadata by actually downloading the .whl and .tar.gz so I know that PyPI has the right information.  But it's still displaying the wrong data.

What is doing the upload? Because PyPI also doesn't read the METADATA file itself, whatever is doing the upload does that and sends it alongside the file as data.

Okay, thanks!

What is doing the upload? Because PyPI also doesn't read the METADATA file itself, whatever is doing the upload does that and sends it alongside the file as data.

TIL!  I'm using pdm publish, so I think that's probably a bug in the PDM front-end.  Maybe I can try flit.


Friendly overloads should translate out PCWSTR to out string

In process of doing this, keep @kennykerr's advice in mind:

If there's no attribute that says how to free the PWSTR then you let the API free it and you simply copy the string. IXmlReader is an example of this. If there's an attribute that indicates how to free the memory then you use that allocator. ISpellingError is an example of this.

Careful or you'll regress PathParseIconLocation and end up with mutable C# strings again.

Interesting cases:

GetFullPathNameW declares an [Out] PWSTR* which is actually a pointer into the original input buffer, so no memory freeing should be done.


IIS Express tests: orphaned iis process fails to shutdown

The last 10 builds of ServerTests on Win8 have failed because the previous test run failed to shutdown. The iisexpress.exe process does not die and locks the folder. The process can only be killed with admin rights.  This leads to the following error:

http://aspnetci/viewType.html?buildTypeId=XPlat_Windows_Win8_Universe

Test that is most suspect:
ServerComparison.FunctionalTests.ResponseCompressionTests.ResponseCompression_Windows_NoCompression(serverType: IISExpress, runtimeFlavor: Clr, architecture: x64, applicationBaseUrl)
This ran for 2 hours before TC killed it. All subsequent builds failed.

The process can only be killed with admin rights

This seems very concerning... our tests don't run as Admin do they?

Yes, concerning. The build runs under our normal build agent user, but I was unable to kill iisexpress.exe without elevating Process Explorer to run as admin.

I'm seeing this on another box (aspnetci-a-100), with a different test. So it seems unrelated to the test, but it is a relatively consistent problem. What I don't get is how iisexpress is somehow elevating.

Same issue occurs in IIS Integration.
stderr: warning: failed to remove .r/IISIntegration/test/FunctionalTests/bin/Release/net46

@anurse do you have time to investigate this one as well?

At this point we're not going to get any more information unless we start running procmon while running the tests. Nobody knows why the process ended up with an Admin token.

We've added a call to taskkill /f /im iisexpress.exe in CI settings at the end of our test runs to mitigate this.

Should we close this for now? We can always reopen if it reoccurs.

Depends. Do we still need to add something to integration testing to ensure iisexpress.exe is killed?

We already have as much code as I can find to do that. The thing we may still want to investigate is why the tests was hanging. iisexpress was left running because a test was hanging and TeamCity killed it, which orphaned iisexpress

Let's close as done for now. If iisexpress is left running because a test hangs, TC will fail the build with a timeout failure. The main work we needed here was to prevent those kinds of failures from breaking the agent on future builds.


Add ElementFinder's methods to prototype

Instead of adding methods to each instance you can add them only once to prototype. That will reduce memory usage and will speed up ElementFinder creation. I'm talking about this part:
  var self = this;
  WEB_ELEMENT_FUNCTIONS.forEach(function(fnName) {
    self[fnName] = function() {
      var args = arguments;
      var actionFn = function(webElem) {
        return webElem[fnName].apply(webElem, args);
      };
      return self.applyAction_(actionFn);
    };
  });

Similar code inside ElementFinder class

Given the latency involved in WebDriver commands, the speedup from the creation of an ElementFinder object wouldn't be noticeable, especially since it isn't a really hot path in the code. I don't think we should optimize this unless it's actually proven to cause issues.
Thanks for your attention to detail though! And if someone wanted to actually go ahead and make a clean, passing PR with these changes, I probably wouldn't turn it down.

@juliemr  You are right but anyway that's what is heavily used inside tests. For example for 1000 elementFinders it's almost 8 times works faster

+1
I am working on one project, which requires log all actions made in browser. I am planning decorate ElementArrayFinder.click() to export my custom log. However it failed because click() is defined at element object but not prototype level.
PR #2575


[bug] The install_server.md has error.

Ⅰ. Issue Description
When I first deployed the server according to the  instrction #Procedure - When Deploying with Docker#.
I found it must be  compiled the source code before  #2.build-supernode# .
https://github.com/dragonflyoss/Dragonfly/edit/master/docs/user_guide/install_server.md
Ⅱ. Describe what happened
first step :
git clone https://github.com/dragonflyoss/Dragonfly.git

then:
 cd Dragonfly
now:
$ make build-supernode
Begin to build supernode.
./hack/build-supernode.sh
Begin to build supernode in the local environment.
/ hack/build-supernode.sh: Line 19: mvn: No command found

// ./hack/build-supernode.sh:行19: mvn: 未找到命令

Cp: Cannot get the file status of "/app/dragonfly/Dragonfly/hack/. / src/supernode/target/supernode.jar" (stat): No file or directory

// cp: 无法获取"/app/dragonfly/Dragonfly/hack/../src/supernode/target/supernode.jar" 的文件状态(stat): 没有那个文件或目录

BUILD: supernode in /app/dragonfly/Dragonfly/bin/supernode.jar

Ⅲ. Describe what you expected to happen
BUILD success.
Ⅳ. How to reproduce it (as minimally and precisely as possible)
The description document needs to be supplemented with this content:
2.Enter the project directory.
cd Dragonfly/src/supernode
2.Compile the source code.
mvn clean -U install -DskipTests=true

then
4.Build the Docker image.
build-supernode

Ⅴ. Anything else we need to know?
no
Ⅵ.

The doc has been updated and you can check it here  https://d7y.io/zh-cn/docs/userguide/install_server.html. So close it now.