Unable to install kubeflow-fairing from most recent pip version

/kind bug
pip install -U pip
pip install kubeflow-fairing

                 OR

pip install --use-feature=2020-resolver kubeflow-fairing

Get errors or loops when try to install some deps like botocore ans s3-sotrage
Environment:

Fairing version: 1.0.2:

OS: Colab

@diegodgs I could install the kubeflow-fairing successful liking your above steps(pasted the details here):
python3 -m pip install -U pip --user
Collecting pip
  Using cached https://files.pythonhosted.org/packages/ab/11/2dc62c5263d9eb322f2f028f7b56cd9d096bb8988fcf82d65fa2e4057afe/pip-20.3.1-py2.py3-none-any.whl
Installing collected packages: pip
  Found existing installation: pip 19.3.1
    Uninstalling pip-19.3.1:
      Successfully uninstalled pip-19.3.1
  WARNING: The scripts pip, pip3 and pip3.7 are installed in '/Users/llhu/Library/Python/3.7/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
Successfully installed pip-20.3.1

Found existing installation: kubeflow-fairing 1.0.2
Uninstalling kubeflow-fairing-1.0.2:
  Would remove:
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/containerregistry/*
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/*
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow_fairing-1.0.2.dist-info/*
  Would not remove (might be manually added):
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/fairing/config.py.bak
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/fairing/preprocessors/istio.yaml
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/pytorchjob/__init__.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/pytorchjob/api/__init__.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/pytorchjob/api/py_torch_job_client.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/pytorchjob/api/py_torch_job_watch.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/pytorchjob/api_client.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/pytorchjob/configuration.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/pytorchjob/constants/__init__.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/pytorchjob/constants/constants.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/pytorchjob/models/__init__.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/pytorchjob/models/v1_job_condition.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/pytorchjob/models/v1_job_status.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/pytorchjob/models/v1_py_torch_job.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/pytorchjob/models/v1_py_torch_job_list.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/pytorchjob/models/v1_py_torch_job_spec.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/pytorchjob/models/v1_replica_spec.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/pytorchjob/models/v1_replica_status.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/pytorchjob/models/v1_time.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/pytorchjob/rest.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/pytorchjob/utils/__init__.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/pytorchjob/utils/utils.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/tfjob/__init__.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/tfjob/api/__init__.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/tfjob/api/tf_job_client.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/tfjob/api/tf_job_watch.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/tfjob/api_client.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/tfjob/configuration.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/tfjob/constants/__init__.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/tfjob/constants/constants.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/tfjob/models/__init__.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/tfjob/models/v1_job_condition.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/tfjob/models/v1_job_status.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/tfjob/models/v1_replica_spec.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/tfjob/models/v1_replica_status.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/tfjob/models/v1_tf_job.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/tfjob/models/v1_tf_job_list.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/tfjob/models/v1_tf_job_spec.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/tfjob/models/v1_time.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/tfjob/rest.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/tfjob/utils/__init__.py
    /Users/llhu/Library/Python/3.7/lib/python/site-packages/kubeflow/tfjob/utils/utils.py
Proceed (y/n)? y
  Successfully uninstalled kubeflow-fairing-1.0.2
llhu@huleis-mbp hulei % python3 -m pip install kubeflow-fairing --user
Collecting kubeflow-fairing
  Using cached kubeflow_fairing-1.0.2-py3-none-any.whl (162 kB)
Requirement already satisfied: notebook>=5.6.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (6.0.2)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: google-cloud-logging>=1.13.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.14.0)
Requirement already satisfied: urllib3==1.24.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.24.2)
Requirement already satisfied: numpy>=1.17.3 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.17.4)
Requirement already satisfied: oauth2client>=4.0.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (4.1.3)
Requirement already satisfied: google-auth>=1.6.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.23.0)
Requirement already satisfied: azure-storage-file>=2.1.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.1.0)
Requirement already satisfied: kfserving>=<IP_ADDRESS> in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (0.4.1)
Requirement already satisfied: setuptools>=34.0.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (42.0.2)
Requirement already satisfied: boto3>=1.9.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.10.27)
Requirement already satisfied: python-dateutil<=2.8.0,>=2.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.8.0)
Requirement already satisfied: httplib2>=0.12.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (0.14.0)
Requirement already satisfied: kubernetes==10.0.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (10.0.1)
Requirement already satisfied: nbconvert>=5.6.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (5.6.1)
Requirement already satisfied: kubeflow-pytorchjob>=0.1.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (0.1.2)
Requirement already satisfied: ibm-cos-sdk>=2.6.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.8.0)
Requirement already satisfied: docker>=3.4.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (4.1.0)
Requirement already satisfied: azure-mgmt-storage>=9.0.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (16.0.0)
Requirement already satisfied: cloudpickle<=1.4.1,>=0.8 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.2.2)
Requirement already satisfied: kubeflow-tfjob>=0.1.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (0.1.2)
Requirement already satisfied: google-cloud-storage>=1.13.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.32.0)
Requirement already satisfied: retrying>=1.3.3 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.3.3)
Requirement already satisfied: future>=0.17.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (0.18.2)
Requirement already satisfied: requests<2.23,>=2.21.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.22.0)
Requirement already satisfied: google-api-python-client>=1.7.8 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.7.11)
Requirement already satisfied: tornado>=6.0.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (6.1)
Requirement already satisfied: grpcio>=1.27.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.33.2)
Requirement already satisfied: azure-common~=1.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from azure-mgmt-storage>=9.0.0->kubeflow-fairing) (1.1.23)
Requirement already satisfied: msrest>=0.5.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from azure-mgmt-storage>=9.0.0->kubeflow-fairing) (0.6.10)
Requirement already satisfied: azure-mgmt-core<2.0.0,>=1.2.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from azure-mgmt-storage>=9.0.0->kubeflow-fairing) (1.2.1)
Requirement already satisfied: azure-core<2.0.0,>=1.8.2a in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from azure-mgmt-core<2.0.0,>=1.2.0->azure-mgmt-storage>=9.0.0->kubeflow-fairing) (1.8.2)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: requests<2.23,>=2.21.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.22.0)
Requirement already satisfied: azure-storage-common~=2.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from azure-storage-file>=2.1.0->kubeflow-fairing) (2.1.0)
Requirement already satisfied: azure-common~=1.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from azure-mgmt-storage>=9.0.0->kubeflow-fairing) (1.1.23)
Requirement already satisfied: requests<2.23,>=2.21.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.22.0)
Requirement already satisfied: python-dateutil<=2.8.0,>=2.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.8.0)
Requirement already satisfied: cryptography in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from azure-storage-common~=2.1->azure-storage-file>=2.1.0->kubeflow-fairing) (2.8)
Requirement already satisfied: azure-common~=1.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from azure-mgmt-storage>=9.0.0->kubeflow-fairing) (1.1.23)
Requirement already satisfied: jmespath<1.0.0,>=0.7.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from boto3>=1.9.0->kubeflow-fairing) (0.9.4)
Requirement already satisfied: s3transfer<0.3.0,>=0.2.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from boto3>=1.9.0->kubeflow-fairing) (0.2.1)
Requirement already satisfied: botocore<1.14.0,>=1.13.27 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from boto3>=1.9.0->kubeflow-fairing) (1.13.27)
Requirement already satisfied: jmespath<1.0.0,>=0.7.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from boto3>=1.9.0->kubeflow-fairing) (0.9.4)
Requirement already satisfied: python-dateutil<=2.8.0,>=2.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.8.0)
Requirement already satisfied: urllib3==1.24.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.24.2)
Requirement already satisfied: docutils<0.16,>=0.10 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from botocore<1.14.0,>=1.13.27->boto3>=1.9.0->kubeflow-fairing) (0.15.2)
Requirement already satisfied: cffi!=1.11.3,>=1.8 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from cryptography->azure-storage-common~=2.1->azure-storage-file>=2.1.0->kubeflow-fairing) (1.13.2)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: pycparser in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from cffi!=1.11.3,>=1.8->cryptography->azure-storage-common~=2.1->azure-storage-file>=2.1.0->kubeflow-fairing) (2.19)
Requirement already satisfied: websocket-client>=0.32.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from docker>=3.4.1->kubeflow-fairing) (0.56.0)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: requests<2.23,>=2.21.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.22.0)
Requirement already satisfied: google-auth-httplib2>=0.0.3 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from google-api-python-client>=1.7.8->kubeflow-fairing) (0.0.3)
Requirement already satisfied: httplib2>=0.12.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (0.14.0)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: uritemplate<4dev,>=3.0.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from google-api-python-client>=1.7.8->kubeflow-fairing) (3.0.0)
Requirement already satisfied: google-auth>=1.6.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.23.0)
Requirement already satisfied: setuptools>=34.0.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (42.0.2)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: rsa<5,>=3.1.4 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from google-auth>=1.6.2->kubeflow-fairing) (4.0)
Requirement already satisfied: cachetools<5.0,>=2.0.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from google-auth>=1.6.2->kubeflow-fairing) (3.1.1)
Requirement already satisfied: pyasn1-modules>=0.2.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from google-auth>=1.6.2->kubeflow-fairing) (0.2.7)
Requirement already satisfied: google-auth>=1.6.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.23.0)
Requirement already satisfied: httplib2>=0.12.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (0.14.0)
Requirement already satisfied: google-api-core[grpc]<2.0.0dev,>=1.14.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from google-cloud-logging>=1.13.0->kubeflow-fairing) (1.23.0)
Requirement already satisfied: google-cloud-core<2.0dev,>=1.0.3 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from google-cloud-logging>=1.13.0->kubeflow-fairing) (1.4.3)
Requirement already satisfied: google-auth>=1.6.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.23.0)
Requirement already satisfied: requests<2.23,>=2.21.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.22.0)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: protobuf>=3.12.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from google-api-core[grpc]<2.0.0dev,>=1.14.0->google-cloud-logging>=1.13.0->kubeflow-fairing) (3.13.0)
Requirement already satisfied: pytz in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from google-api-core[grpc]<2.0.0dev,>=1.14.0->google-cloud-logging>=1.13.0->kubeflow-fairing) (2019.3)
Requirement already satisfied: googleapis-common-protos<2.0dev,>=1.6.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from google-api-core[grpc]<2.0.0dev,>=1.14.0->google-cloud-logging>=1.13.0->kubeflow-fairing) (1.6.0)
Requirement already satisfied: setuptools>=34.0.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (42.0.2)
Requirement already satisfied: grpcio>=1.27.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.33.2)
Requirement already satisfied: google-auth>=1.6.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.23.0)
Requirement already satisfied: requests<2.23,>=2.21.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.22.0)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: protobuf>=3.12.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from google-api-core[grpc]<2.0.0dev,>=1.14.0->google-cloud-logging>=1.13.0->kubeflow-fairing) (3.13.0)
Requirement already satisfied: pytz in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from google-api-core[grpc]<2.0.0dev,>=1.14.0->google-cloud-logging>=1.13.0->kubeflow-fairing) (2019.3)
Requirement already satisfied: googleapis-common-protos<2.0dev,>=1.6.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from google-api-core[grpc]<2.0.0dev,>=1.14.0->google-cloud-logging>=1.13.0->kubeflow-fairing) (1.6.0)
Requirement already satisfied: setuptools>=34.0.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (42.0.2)
Requirement already satisfied: requests<2.23,>=2.21.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.22.0)
Requirement already satisfied: google-resumable-media<2.0dev,>=1.0.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from google-cloud-storage>=1.13.2->kubeflow-fairing) (1.1.0)
Requirement already satisfied: google-cloud-core<2.0dev,>=1.0.3 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from google-cloud-logging>=1.13.0->kubeflow-fairing) (1.4.3)
Requirement already satisfied: google-auth>=1.6.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.23.0)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: google-crc32c<2.0dev,>=1.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from google-resumable-media<2.0dev,>=1.0.0->google-cloud-storage>=1.13.2->kubeflow-fairing) (1.0.0)
Requirement already satisfied: cffi!=1.11.3,>=1.8 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from cryptography->azure-storage-common~=2.1->azure-storage-file>=2.1.0->kubeflow-fairing) (1.13.2)
Requirement already satisfied: protobuf>=3.12.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from google-api-core[grpc]<2.0.0dev,>=1.14.0->google-cloud-logging>=1.13.0->kubeflow-fairing) (3.13.0)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: jmespath<1.0.0,>=0.7.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from boto3>=1.9.0->kubeflow-fairing) (0.9.4)
Requirement already satisfied: ibm-cos-sdk-core==2.8.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from ibm-cos-sdk>=2.6.0->kubeflow-fairing) (2.8.0)
Requirement already satisfied: ibm-cos-sdk-s3transfer==2.8.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from ibm-cos-sdk>=2.6.0->kubeflow-fairing) (2.8.0)
Requirement already satisfied: jmespath<1.0.0,>=0.7.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from boto3>=1.9.0->kubeflow-fairing) (0.9.4)
Requirement already satisfied: requests<2.23,>=2.21.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.22.0)
Requirement already satisfied: python-dateutil<=2.8.0,>=2.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.8.0)
Requirement already satisfied: docutils<0.16,>=0.10 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from botocore<1.14.0,>=1.13.27->boto3>=1.9.0->kubeflow-fairing) (0.15.2)
Requirement already satisfied: ibm-cos-sdk-core==2.8.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from ibm-cos-sdk>=2.6.0->kubeflow-fairing) (2.8.0)
Requirement already satisfied: tornado>=6.0.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (6.1)
Requirement already satisfied: minio>=4.0.9 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kfserving>=<IP_ADDRESS>->kubeflow-fairing) (5.0.5)
Requirement already satisfied: setuptools>=34.0.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (42.0.2)
Requirement already satisfied: kubernetes==10.0.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (10.0.1)
Requirement already satisfied: numpy>=1.17.3 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.17.4)
Requirement already satisfied: adal>=1.2.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kfserving>=<IP_ADDRESS>->kubeflow-fairing) (1.2.2)
Requirement already satisfied: azure-storage-blob<=2.1.0,>=1.3.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kfserving>=<IP_ADDRESS>->kubeflow-fairing) (2.1.0)
Requirement already satisfied: certifi>=14.05.14 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kfserving>=<IP_ADDRESS>->kubeflow-fairing) (2019.9.11)
Requirement already satisfied: python-dateutil<=2.8.0,>=2.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.8.0)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: table-logger>=0.3.5 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kfserving>=<IP_ADDRESS>->kubeflow-fairing) (0.3.6)
Requirement already satisfied: google-cloud-storage>=1.13.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.32.0)
Requirement already satisfied: urllib3==1.24.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.24.2)
Requirement already satisfied: cryptography in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from azure-storage-common~=2.1->azure-storage-file>=2.1.0->kubeflow-fairing) (2.8)
Requirement already satisfied: python-dateutil<=2.8.0,>=2.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.8.0)
Requirement already satisfied: PyJWT>=1.0.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from adal>=1.2.2->kfserving>=<IP_ADDRESS>->kubeflow-fairing) (1.7.1)
Requirement already satisfied: requests<2.23,>=2.21.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.22.0)
Collecting argparse>=1.4.0
  Using cached argparse-1.4.0-py2.py3-none-any.whl (23 kB)
Requirement already satisfied: azure-storage-common~=2.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from azure-storage-file>=2.1.0->kubeflow-fairing) (2.1.0)
Requirement already satisfied: azure-common~=1.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from azure-mgmt-storage>=9.0.0->kubeflow-fairing) (1.1.23)
Requirement already satisfied: setuptools>=34.0.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (42.0.2)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: certifi>=14.05.14 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kfserving>=<IP_ADDRESS>->kubeflow-fairing) (2019.9.11)
Requirement already satisfied: python-dateutil<=2.8.0,>=2.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.8.0)
Requirement already satisfied: table-logger>=0.3.5 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kfserving>=<IP_ADDRESS>->kubeflow-fairing) (0.3.6)
Requirement already satisfied: kubernetes==10.0.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (10.0.1)
Requirement already satisfied: urllib3==1.24.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.24.2)
Requirement already satisfied: setuptools>=34.0.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (42.0.2)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: certifi>=14.05.14 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kfserving>=<IP_ADDRESS>->kubeflow-fairing) (2019.9.11)
Requirement already satisfied: python-dateutil<=2.8.0,>=2.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.8.0)
Requirement already satisfied: table-logger>=0.3.5 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kfserving>=<IP_ADDRESS>->kubeflow-fairing) (0.3.6)
Requirement already satisfied: kubernetes==10.0.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (10.0.1)
Requirement already satisfied: urllib3==1.24.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.24.2)
Requirement already satisfied: pyyaml>=3.12 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubernetes==10.0.1->kubeflow-fairing) (5.1.2)
Requirement already satisfied: requests-oauthlib in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubernetes==10.0.1->kubeflow-fairing) (1.3.0)
Requirement already satisfied: setuptools>=34.0.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (42.0.2)
Requirement already satisfied: websocket-client>=0.32.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from docker>=3.4.1->kubeflow-fairing) (0.56.0)
Requirement already satisfied: requests<2.23,>=2.21.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.22.0)
Requirement already satisfied: urllib3==1.24.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.24.2)
Requirement already satisfied: certifi>=14.05.14 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kfserving>=<IP_ADDRESS>->kubeflow-fairing) (2019.9.11)
Requirement already satisfied: python-dateutil<=2.8.0,>=2.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.8.0)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: google-auth>=1.6.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.23.0)
Requirement already satisfied: python-dateutil<=2.8.0,>=2.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.8.0)
Requirement already satisfied: urllib3==1.24.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.24.2)
Requirement already satisfied: certifi>=14.05.14 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kfserving>=<IP_ADDRESS>->kubeflow-fairing) (2019.9.11)
Requirement already satisfied: pytz in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from google-api-core[grpc]<2.0.0dev,>=1.14.0->google-cloud-logging>=1.13.0->kubeflow-fairing) (2019.3)
Requirement already satisfied: requests-oauthlib in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubernetes==10.0.1->kubeflow-fairing) (1.3.0)
Requirement already satisfied: requests<2.23,>=2.21.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.22.0)
Requirement already satisfied: certifi>=14.05.14 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kfserving>=<IP_ADDRESS>->kubeflow-fairing) (2019.9.11)
Requirement already satisfied: isodate>=0.6.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from msrest>=0.5.0->azure-mgmt-storage>=9.0.0->kubeflow-fairing) (0.6.0)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: jinja2>=2.4 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbconvert>=5.6.1->kubeflow-fairing) (2.10.3)
Requirement already satisfied: jupyter-core in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbconvert>=5.6.1->kubeflow-fairing) (4.6.1)
Requirement already satisfied: pandocfilters>=1.4.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbconvert>=5.6.1->kubeflow-fairing) (1.4.2)
Requirement already satisfied: entrypoints>=0.2.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbconvert>=5.6.1->kubeflow-fairing) (0.3)
Requirement already satisfied: testpath in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbconvert>=5.6.1->kubeflow-fairing) (0.4.4)
Requirement already satisfied: bleach in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbconvert>=5.6.1->kubeflow-fairing) (3.1.0)
Requirement already satisfied: defusedxml in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbconvert>=5.6.1->kubeflow-fairing) (0.6.0)
Requirement already satisfied: traitlets>=4.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbconvert>=5.6.1->kubeflow-fairing) (4.3.3)
Requirement already satisfied: pygments in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbconvert>=5.6.1->kubeflow-fairing) (2.5.2)
Requirement already satisfied: mistune<2,>=0.8.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbconvert>=5.6.1->kubeflow-fairing) (0.8.4)
Requirement already satisfied: nbformat>=4.4 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbconvert>=5.6.1->kubeflow-fairing) (4.4.0)
Requirement already satisfied: webencodings in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from bleach->nbconvert>=5.6.1->kubeflow-fairing) (0.5.1)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: MarkupSafe>=0.23 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from jinja2>=2.4->nbconvert>=5.6.1->kubeflow-fairing) (1.1.1)
Requirement already satisfied: traitlets>=4.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbconvert>=5.6.1->kubeflow-fairing) (4.3.3)
Requirement already satisfied: jsonschema!=2.5.0,>=2.4 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbformat>=4.4->nbconvert>=5.6.1->kubeflow-fairing) (3.2.0)
Requirement already satisfied: ipython-genutils in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbformat>=4.4->nbconvert>=5.6.1->kubeflow-fairing) (0.2.0)
Requirement already satisfied: jupyter-core in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbconvert>=5.6.1->kubeflow-fairing) (4.6.1)
Requirement already satisfied: traitlets>=4.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbconvert>=5.6.1->kubeflow-fairing) (4.3.3)
Requirement already satisfied: pyrsistent>=0.14.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from jsonschema!=2.5.0,>=2.4->nbformat>=4.4->nbconvert>=5.6.1->kubeflow-fairing) (0.15.6)
Requirement already satisfied: attrs>=17.4.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from jsonschema!=2.5.0,>=2.4->nbformat>=4.4->nbconvert>=5.6.1->kubeflow-fairing) (19.3.0)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: setuptools>=34.0.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (42.0.2)
Requirement already satisfied: importlib-metadata in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from jsonschema!=2.5.0,>=2.4->nbformat>=4.4->nbconvert>=5.6.1->kubeflow-fairing) (1.3.0)
Requirement already satisfied: zipp>=0.5 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from importlib-metadata->jsonschema!=2.5.0,>=2.4->nbformat>=4.4->nbconvert>=5.6.1->kubeflow-fairing) (0.6.0)
Requirement already satisfied: nbformat>=4.4 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbconvert>=5.6.1->kubeflow-fairing) (4.4.0)
Requirement already satisfied: jupyter-core in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbconvert>=5.6.1->kubeflow-fairing) (4.6.1)
Requirement already satisfied: jinja2>=2.4 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbconvert>=5.6.1->kubeflow-fairing) (2.10.3)
Requirement already satisfied: ipykernel in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from notebook>=5.6.0->kubeflow-fairing) (5.1.3)
Requirement already satisfied: terminado>=0.8.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from notebook>=5.6.0->kubeflow-fairing) (0.8.3)
Requirement already satisfied: prometheus-client in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from notebook>=5.6.0->kubeflow-fairing) (0.7.1)
Requirement already satisfied: tornado>=6.0.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (6.1)
Requirement already satisfied: nbconvert>=5.6.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (5.6.1)
Requirement already satisfied: jupyter-client>=5.3.4 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from notebook>=5.6.0->kubeflow-fairing) (5.3.4)
Requirement already satisfied: Send2Trash in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from notebook>=5.6.0->kubeflow-fairing) (1.5.0)
Requirement already satisfied: pyzmq>=17 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from notebook>=5.6.0->kubeflow-fairing) (18.1.1)
Requirement already satisfied: ipython-genutils in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbformat>=4.4->nbconvert>=5.6.1->kubeflow-fairing) (0.2.0)
Requirement already satisfied: traitlets>=4.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbconvert>=5.6.1->kubeflow-fairing) (4.3.3)
Requirement already satisfied: traitlets>=4.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbconvert>=5.6.1->kubeflow-fairing) (4.3.3)
Requirement already satisfied: jupyter-client>=5.3.4 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from notebook>=5.6.0->kubeflow-fairing) (5.3.4)
Requirement already satisfied: appnope in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from ipykernel->notebook>=5.6.0->kubeflow-fairing) (0.1.0)
Requirement already satisfied: tornado>=6.0.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (6.1)
Requirement already satisfied: ipython>=5.0.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from ipykernel->notebook>=5.6.0->kubeflow-fairing) (7.10.1)
Requirement already satisfied: prompt-toolkit!=3.0.0,!=3.0.1,<3.1.0,>=2.0.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from ipython>=5.0.0->ipykernel->notebook>=5.6.0->kubeflow-fairing) (2.0.10)
Requirement already satisfied: pexpect in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from ipython>=5.0.0->ipykernel->notebook>=5.6.0->kubeflow-fairing) (4.7.0)
Requirement already satisfied: backcall in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from ipython>=5.0.0->ipykernel->notebook>=5.6.0->kubeflow-fairing) (0.1.0)
Requirement already satisfied: setuptools>=34.0.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (42.0.2)
Requirement already satisfied: decorator in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from ipython>=5.0.0->ipykernel->notebook>=5.6.0->kubeflow-fairing) (4.4.1)
Requirement already satisfied: jedi>=0.10 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from ipython>=5.0.0->ipykernel->notebook>=5.6.0->kubeflow-fairing) (0.15.1)
Requirement already satisfied: traitlets>=4.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbconvert>=5.6.1->kubeflow-fairing) (4.3.3)
Requirement already satisfied: pygments in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbconvert>=5.6.1->kubeflow-fairing) (2.5.2)
Requirement already satisfied: appnope in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from ipykernel->notebook>=5.6.0->kubeflow-fairing) (0.1.0)
Requirement already satisfied: pickleshare in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from ipython>=5.0.0->ipykernel->notebook>=5.6.0->kubeflow-fairing) (0.7.5)
Requirement already satisfied: parso>=0.5.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from jedi>=0.10->ipython>=5.0.0->ipykernel->notebook>=5.6.0->kubeflow-fairing) (0.5.1)
Requirement already satisfied: jupyter-core in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbconvert>=5.6.1->kubeflow-fairing) (4.6.1)
Requirement already satisfied: tornado>=6.0.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (6.1)
Requirement already satisfied: pyzmq>=17 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from notebook>=5.6.0->kubeflow-fairing) (18.1.1)
Requirement already satisfied: python-dateutil<=2.8.0,>=2.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.8.0)
Requirement already satisfied: traitlets>=4.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbconvert>=5.6.1->kubeflow-fairing) (4.3.3)
Requirement already satisfied: pyasn1-modules>=0.2.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from google-auth>=1.6.2->kubeflow-fairing) (0.2.7)
Requirement already satisfied: rsa<5,>=3.1.4 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from google-auth>=1.6.2->kubeflow-fairing) (4.0)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: pyasn1>=0.1.7 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from oauth2client>=4.0.0->kubeflow-fairing) (0.4.8)
Requirement already satisfied: httplib2>=0.12.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (0.14.0)
Requirement already satisfied: ptyprocess>=0.5 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from pexpect->ipython>=5.0.0->ipykernel->notebook>=5.6.0->kubeflow-fairing) (0.6.0)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: wcwidth in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from prompt-toolkit!=3.0.0,!=3.0.1,<3.1.0,>=2.0.0->ipython>=5.0.0->ipykernel->notebook>=5.6.0->kubeflow-fairing) (0.1.7)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: setuptools>=34.0.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (42.0.2)
Requirement already satisfied: pyasn1>=0.1.7 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from oauth2client>=4.0.0->kubeflow-fairing) (0.4.8)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: idna<2.9,>=2.5 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from requests<2.23,>=2.21.0->kubeflow-fairing) (2.8)
Requirement already satisfied: chardet<3.1.0,>=3.0.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from requests<2.23,>=2.21.0->kubeflow-fairing) (3.0.4)
Requirement already satisfied: urllib3==1.24.2 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.24.2)
Requirement already satisfied: certifi>=14.05.14 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kfserving>=<IP_ADDRESS>->kubeflow-fairing) (2019.9.11)
Requirement already satisfied: oauthlib>=3.0.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from requests-oauthlib->kubernetes==10.0.1->kubeflow-fairing) (3.1.0)
Requirement already satisfied: requests<2.23,>=2.21.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (2.22.0)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: pyasn1>=0.1.7 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from oauth2client>=4.0.0->kubeflow-fairing) (0.4.8)
Requirement already satisfied: botocore<1.14.0,>=1.13.27 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from boto3>=1.9.0->kubeflow-fairing) (1.13.27)
Requirement already satisfied: numpy>=1.17.3 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.17.4)
Requirement already satisfied: tornado>=6.0.1 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (6.1)
Requirement already satisfied: ptyprocess>=0.5 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from pexpect->ipython>=5.0.0->ipykernel->notebook>=5.6.0->kubeflow-fairing) (0.6.0)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: ipython-genutils in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from nbformat>=4.4->nbconvert>=5.6.1->kubeflow-fairing) (0.2.0)
Requirement already satisfied: decorator in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from ipython>=5.0.0->ipykernel->notebook>=5.6.0->kubeflow-fairing) (4.4.1)
Requirement already satisfied: six>=1.11.0 in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from kubeflow-fairing) (1.15.0)
Requirement already satisfied: more-itertools in /Users/llhu/Library/Python/3.7/lib/python/site-packages (from zipp>=0.5->importlib-metadata->jsonschema!=2.5.0,>=2.4->nbformat>=4.4->nbconvert>=5.6.1->kubeflow-fairing) (8.0.2)
Installing collected packages: argparse, kubeflow-fairing
Successfully installed argparse-1.4.0 kubeflow-fairing-1.0.2

Testing:
 % python3
Python 3.7.3 (default, Nov 15 2019, 04:04:52)
[Clang 11.0.0 (clang-1<IP_ADDRESS>)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import kubeflow.fairing
>>> kubeflow.fairing.__version__
'1.0.2'
>>>

Yes @xauthulei , I will close this issue. It seens like a pip that was fixed with 9011


[WIP] Count MD steps run in EngineMover

Resolves #292.
In principle, I think the 2-line fix in here does the job. However, I'll add some testing for it later.

Correction ... current stuff does a limited implementation of the goal. The idea proposed in #292 is better than what I've implemented so far here. But this is a necessary start.

Can we move this to an issue. Only if we abandon this PR anyway and will create a new one later.

Can we move this to an issue. Only if we abandon this PR anyway and will create a new one later.

The PR is still pretty close to up-to-date. No reason to abandon it.
(Already mentioned this in person, but adding for the record)

Closing this as outdated and unlikely to be cleaned up for merge (more likely to be completely rewritten). The linked issue is suggests a better implementation than what was started here.


swiftbar: 1.4.3 -> 2.0.0

Description of changes
Diff: https://github.com/swiftbar/Swiftbar/compare/refs/tags/v1.4.3..v2.0.0
Release notes: https://github.com/swiftbar/SwiftBar/releases/tag/v2.0.0
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4204

@SuperSandro2000 Removed hydraPlatforms = [ ]; 👍🏻


feat: Add option to postgres instrumentation to disable db.statement

We leave it on by default, but allow users to disable the inclusion of the attribute entirely if they so wish.
cc #736

It is unclear to me why the 2.7 tests are failing ... there are a few failures for non-pg related things. 🤔


UnicodeDecodeError

Just installed aws-shell on osx 10.10.5 using Python 2.7.10. I get this error upon openings aws-shell. It does not crash the shell or seem to affect any normal functionality. I installed using sudo pip install aws-shell --upgrade --ignore-installed six.
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 810, in __bootstrap_inner
    self.run()
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 763, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/awsshell/makeindex.py", line 84, in write_doc_index
    do_write_doc_index(db, help_command, close_db_on_finish=should_close)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/awsshell/makeindex.py", line 89, in do_write_doc_index
    _index_docs(db, help_command)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/awsshell/makeindex.py", line 107, in _index_docs
    _index_docs(db, sub_help_command)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/awsshell/makeindex.py", line 104, in _index_docs
    text_docs = render_docs_for_cmd(sub_help_command)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/awsshell/makeindex.py", line 113, in render_docs_for_cmd
    help_command(None, None)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/awscli/help.py", line 264, in __call__
    self.renderer.render(self.doc.getvalue())
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/botocore/docs/bcdoc/restdoc.py", line 78, in getvalue
    return ''.join(self._writes).encode('utf-8')
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 49: ordinal not in range(128)

Same happened to me.
OS: 10.11.4
Python: 2.7.11
pip: 8.1.1
Installed via:
pip install aws-shell --upgrade --ignore-installed six

We're seeing the same thing on EMR.
(looker-emr)[ec2-user]$ aws-shell
Creating doc index in the background. It will be a few minutes before all documentation is available.
aws> Exception in thread Thread-1:
Traceback (most recent call last):
File "/usr/lib64/python2.7/threading.py", line 813, in __bootstrap_inner
self.run()
File "/usr/lib64/python2.7/threading.py", line 766, in run
self.__target(*self.__args, **self.__kwargs)
File "/home/ec2-user/.envs/looker-emr/local/lib/python2.7/dist-packages/awsshell/makeindex.py", line 84, in write_doc_index
do_write_doc_index(db, help_command, close_db_on_finish=should_close)
File "/home/ec2-user/.envs/looker-emr/local/lib/python2.7/dist-packages/awsshell/makeindex.py", line 89, in do_write_doc_index
_index_docs(db, help_command)
File "/home/ec2-user/.envs/looker-emr/local/lib/python2.7/dist-packages/awsshell/makeindex.py", line 107, in _index_docs
_index_docs(db, sub_help_command)
File "/home/ec2-user/.envs/looker-emr/local/lib/python2.7/dist-packages/awsshell/makeindex.py", line 104, in _index_docs
text_docs = render_docs_for_cmd(sub_help_command)
File "/home/ec2-user/.envs/looker-emr/local/lib/python2.7/dist-packages/awsshell/makeindex.py", line 113, in render_docs_for_cmd
help_command(None, None)
File "/home/ec2-user/.envs/looker-emr/local/lib/python2.7/dist-packages/awscli/help.py", line 264, in call
self.renderer.render(self.doc.getvalue())
File "/home/ec2-user/.envs/looker-emr/local/lib/python2.7/dist-packages/botocore/docs/bcdoc/restdoc.py", line 78, in getvalue
return ''.join(self._writes).encode('utf-8')
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 49: ordinal not in range(128)
aws>

What version of the AWS CLI do you have (aws --version)?  I suspect this may be related to a recent release that pulled in some documentation with non ascii chars .
If that's the case, this should be fixed with the next release of the AWS CLI (https://github.com/aws/aws-cli/pull/1882).

aws-cli/1.10.17 Python/2.7.11 Darwin/15.4.0 botocore/1.4.8

The error was caused on: aws-cli/1.10.17 Python/2.7.10 Darwin/14.5.0 botocore/1.4.8
The new version of aws-cli is not on brew yet, nor is it on pip. Pip says there is a new version "10.10.1", but when I pip install --upgrade awscli and run aws --version I get 10.10.17. The same error is still present.

aws-cli/1.10.17 Python/2.7.10 Linux/4.1.10-17.31.amzn1.x86_64 botocore/1.4.8

aws-cli/1.10.17 Python/2.7.6 Linux/3.13.0-74-generic botocore/1.4.8

Same issue
aws-cli/1.10.17 Python/2.7.11 Darwin/15.4.0 botocore/1.4.8

Ok, we'll get a new CLI release out that should fix this issue.  I'll also update the doc generator to be more robust when cases like this happen.
I'll update this issue once a CLI release is out.

Same issue
aws-cli/1.10.17 Python/2.7.11 Darwin/15.2.0 botocore/1.4.8

Just a FYI, I upgraded today and it looks good so far!

All good here too :+1:

Works for me too :+1:

Fixed

Fixed


Update more instances of elastic search to get build to pass

Signed-off-by: Harsha Vamsi Kalluri<EMAIL_ADDRESS>Thank you for submitting a pull request!
Please make sure you have signed our Contributor License Agreement (CLA).
We are not asking you to assign copyright to us, but to give us the right to distribute your code without restriction. We ask this of all contributors in order to assure our users of the origin and continuing existence of the code.
You only need to sign the CLA once.

[X] I have signed the Contributor License Agreement (CLA)

@nknize Updated more instances of ES. I removed some tests around multiIndexType since we don't support them anymore.


nginx: do not run anything as root

Instead tell systemd to run the service as the requested user/group with
the capability to listen on reserved ports (< 1024).
Motivation for this change
Defense in depth: less root processes running on the system.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

The nextcloud test is still broken for now, looking at why. But interested in early comments about whether this is desirable or not, and whether this is the proper way to achieve the goal :)

@Mic92 agreed, I'll work on some documentation for the change. I expect some configs have been relying on the fact that the process was starting as root -- but I don't know yet how common that is or how hard to fix that is though (and I guess we won't really know until this is pushed to users...). Note that for the ACME case, if you use the useACME = true; option of nginx vhosts, the permissions should already be nginx:nginx and not root:root.

I think served files should be mostly ok because they have to be already readable by nginx:nginx. There might be some users that have configuration included via nginx include directive that are not user-readable.

Drafted a changelog entry. English is not my first language, so suggestions are welcome :-)

If delete the "nginx -t" service will work normally?

@Mic92 as mentioned in the comment thread, there never was a setuid binary.

Ok. Then can you rename the setcap wrapper to something else but nginx? It would be only usable to the nginx user anyway.

@Mic92 this variant normal?

I'm dropping this change, it seems to be going nowhere. If someone is motivated to follow through with the comments, feel free to pick it up. So far it's been less painful to rebase this change regularly in my local nixpkgs fork than to figure out how to upstream this...


v2.0.0 gives error when running ember deploy

Error: The Broccoli Plugin: [Fingerprint] failed with:
Error: ENOENT: no such file or directory, open '/repo/tmp/uglify_writer-input_base_path-ZtW0omFx.tmp/assets/dag-map.js.map'
    at Object.fs.openSync (fs.js:653:18)
    at Object.fs.readFileSync (fs.js:554:33)
    at UglifyWriter.processFile (/repo/node_modules/broccoli-uglify-sourcemap/index.js:101:41)
    at /repo/node_modules/broccoli-uglify-sourcemap/index.js:65:16
    at Array.forEach (<anonymous>)
    at /repo/node_modules/broccoli-uglify-sourcemap/index.js:55:25
    at Array.forEach (<anonymous>)
    at UglifyWriter.build (/repo/node_modules/broccoli-uglify-sourcemap/index.js:54:19)
    at /repo/node_modules/broccoli-plugin/read_compat.js:93:34
    at tryCatch (/repo/node_modules/rsvp/dist/rsvp.js:525:12)
    at invokeCallback (/repo/node_modules/rsvp/dist/rsvp.js:538:13)
    at publish (/repo/node_modules/rsvp/dist/rsvp.js:508:7)
    at flush (/repo/node_modules/rsvp/dist/rsvp.js:2415:5)
    at _combinedTickCallback (internal/process/next_tick.js:131:7)
    at process._tickCallback (internal/process/next_tick.js:180:9)

I suspect this is because of the upgrade to source-map-url: ^0.4.0

I think this is pretty much the same issue as https://github.com/ember-cli/ember-cli-uglify/issues/29

I added a comment there I think it's not solved for every case yet: https://github.com/ember-cli/ember-cli-uglify/issues/29#issuecomment-336085319

@urbany - #29 was not a bug in ember-cli-uglify (but was instead a bug in the actual source files that Ember generated). So far there is no evidence that an actual bug exists in this repo...

Thank you for the quick reply Robert!
I'm not sure how all the pieces fit together, but shouldn't the broccoli-uglify-sourcemap remove the //# sourceMappingURL=popper.js.map when joining all the vendor files into the vendor.js?since the popper.js.map is already in the cendor.map there is no need to have the //# sourceMappingURL=popper.js.map comment right?

Workaround for this was to disable sourcemaps in production builds
ember-cli-build.js
// ...
const EmberApp = require('ember-cli/lib/broccoli/ember-app');

// ...
module.exports = function(defaults) {
  let app = new EmberApp(defaults, {
    sourcemaps: {
      enabled: EmberApp.env() !== 'production',
    },
   // ...


Revit plugin needs to use Design Automation bridge from Nuget

It's using a local copy, which is not correct, needs to use the Nuget package

fixed in #22


A question about training different datasets without initialization

How to make the model continuously train on two datasets. Specifically, how to continue training on the second data without initialization after training on the first one.
Thanks

for bayesian generative models, there is a var named is_initial_local to control the initialization of local params, and u can set this var as False when u want to retrain the model on the second dataset, thx
def train(self, data:np.ndarray, num_epochs: int=1, is_train: bool = True, is_initial_local: bool=True):


White Screen on first load

The first time the camera loads, I get a white screen, when i press a button or go to another page and go back, it works fine.
sometimes its half the screen, sometimes full screen white.

oops, wrong plugin. was meant for qrscanner.


Optimizer should save the binary when a pass succeeds without changes

Added a test for this too.
Fixes https://github.com/KhronosGroup/SPIRV-Tools/issues/611

Rebased

Fixed order of using decls, as noted in review for #613.
Keeping approval.


Too many rows

input 5 4, 5 cols, 4 row, plus the corresponding 3x3 section is between [2, 0] top left and [4, 2] bottom right = 19 ( i might be horribly wrong ofc )

Actually, the number of rows is OK, but the number of columns is not.

there goes my HW in the trash, thanks for clarifying


Mapping for Section 2 to Section 7

Description
The CDA text section can contain section 2 to section 7, and they have not been mapped yet (see the DMS)
Component
NHS111 adapter
Version
0.1.0
Step to Reproduce

Put the valid a CDA in the payload
add section2 to one of the section (put this as the last element of the section)

                               <component typeCode="COMP" contextConductionInd="true">
                                         <templateId root="2.16.840.1.1138<IP_ADDRESS>.<IP_ADDRESS>"
                                                            extension="COCD_TP146246GB01#component1"/>

                                                <templateId root="2.16.840.1.1138<IP_ADDRESS>.<IP_ADDRESS>"
                                                            extension="COCD_TP146246GB01#Section2"/>
                                                <id root="BBC110DB-288F-4B32-8DE1-362646A65AAF"/>
                                                <title>SUBSUB</title>
                                                <text>
                                                    <content>SUBSUB</content>
                                                </text>

                                        </component>

OR if you want add section2 and section 3 to one of the sections, add below to one of the section 1.

                               <component typeCode="COMP" contextConductionInd="true">
                                         <templateId root="2.16.840.1.1138<IP_ADDRESS>.<IP_ADDRESS>"
                                                            extension="COCD_TP146246GB01#component1"/>

                                                <templateId root="2.16.840.1.1138<IP_ADDRESS>.<IP_ADDRESS>"
                                                            extension="COCD_TP146246GB01#Section2"/>
                                                <id root="BBC110DB-288F-4B32-8DE1-362646A65AAF"/>
                                                <title>SUBSUB2</title>
                                                <text>
                                                    <content>SUBSUB2</content>
                                                </text>
                                                <component typeCode="COMP" contextConductionInd="true">
                                                          <templateId root="2.16.840.1.1138<IP_ADDRESS>.<IP_ADDRESS>"
                                                                   extension="COCD_TP146246GB01#component2"/>

                                                               <templateId root="2.16.840.1.1138<IP_ADDRESS>.<IP_ADDRESS>"
                                                                               extension="COCD_TP146246GB01#Section3"/>
                                                               <id root="DDD110DB-288F-4B32-8DE1-362646A65DDD"/>
                                                                <title>SUBSUB3</title>
                                                               <text>
                                                                <content>SUBSUB3 </content>
                                                                </text>

                                                 </component>

                                        </component>

Test Data
Any data
Preconditions
None
Environment
local environment
Severity
High, impact on integration
Priority
Not urgent
Expected Behavior
Section 2 - Section 7 is mapped and the content of it is in the output.
Also, the parent-child relationship link between them is preserved.
The example only shows samples with Section 2 and Section 3.

We can't verify if this is a valid case for the 111 PEM adapter. We will raise with NHS to verify.

Existing suppliers tend to only use a single section, but population of the other sections is a valid use case that the adapter should cope with.  The additional sections should just be added to the Composition

@Kusnaditjung will add this to the next release

@Kusnaditjung closing as discussed. This is now fixed.


Relay/TRT Integration (whole graph only)

This PR includes support for a version of Relay/TRT integration which only works when the entire model can be converted to TRT. It is enabled with the EnableTrt pass. If any op in the model cannot be converted to TRT, EnableTrt will return the original module unmodified.
How to use:
mod = relay.transform.EnableTrt()(mod)
with relay.build_config(opt_level=2, disabled_pass={"SimplifyInference"}):
  graph, lib, params = relay.build(mod, "cuda", params=params)

The NNVM/TRT integration is still present.

@zhiics Could you please review?

@yongwww @reminisce @ziyu-guo Could you please review?

@zhiics Could you take a quick look at my changes to use the external codegen/runtime?

@comaniac @anijain2305 Could you please review? Thanks!


I can not open a .pck file.

Open & read .pck files.

We try to keep VS Code lean and we think the functionality you're asking for is great for a VS Code extension. Maybe you can already find one that suits you in the VS Code Marketplace. Just in case, in a few simple steps you can get started writing your own extension. See also our issue reporting guidelines.
Happy Coding!


Confusing help box for setting precursor mass tolerance

Right now the suggestion for entering a precursor mass tolerance is:

Examples:
name dot 5 ppm 0,1.003,2.006
name interval [-4;-3],[-0.5;0.5],[101;102]

This is a bit confusing on first attempt; I had to ask for help.
Here are a few suggestions --

Change "dot" to "tolerance"
Make a "Format:" section above or below the examples that specifies that each field should have a space between them, and what each of the fields for the two types of commands represent. Maybe briefly mention how the comma-separated lists are handled.

Some additional problems: commas between numbers are bad, because sometimes they are used within numbers, e.g. 1,000 for a thousand. Need a better system that is as flexible as the current one, simply documenting it is not sufficient.

Is this current tooltip clear?
A custom mass difference acceptor may be specified in multiple ways:

To accept a custom (other than the interval corresponding to the precursor tolerance) interval around zero daltons, specify a custom name, followed by "ppmAroundZero" or "daltonsAroundZero", followed by the numeric value corresponding to the interval width. Examples:

CustomPpmInterval ppmAroundZero 5
CustomDaltonInterval daltonsAroundZero 2.1

To accept a variety of pre-specified mass differences, use a custom name, followed by "dot", followed by a custom bin width, followed by comma separated acceptable mass differences. Examples:

CustomMissedIsotopePeaks dot 5 ppm 0,1.0029,2.0052
CustomOxidationAllowed dot 0.1 da 0,16

To accept mass differences in pre-specified dalton intervals, use a custom name, followed by "interval", followed by comma separated mass intervals in brackets. Example:

CustomPositiveIntervalAcceptror interval [0,200]


WIP: Add IPv6 support to wireguard typha bootstrapping

Description
WIP: Add IPv6 support to wireguard typha bootstrapping
Test changes are still pending.

Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[x] Release note

Release Note

Add IPv6 support to wireguard typha bootstrapping

Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one docs-* label.

docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.

Other optional labels:

cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

Closing this in favor doing all the work in https://github.com/projectcalico/calico/pull/6178 (split under different commits).


Bump Terraform provider version to v3.117.0

Description of your changes
This PR bumps Terraform provider version to v3.117.0
I have:

[x] Read and followed Crossplane's contribution process.
[x] Run make reviewable to ensure this PR is ready for review.
[ ] ~Added backport release-x.y labels to auto-backport this PR if necessary.~

How has this code been tested
Will update

/test-examples="examples/storage/v1beta1/account.yaml"

/test-examples="examples/network/v1beta1/subnet.yaml"

/test-examples="examples/network/v1beta2/subnet.yaml"

/test-examples="examples/containerservice/v1beta1/kubernetescluster.yaml"


Add Browser middleware

Inspired by Guzzle middlewares I added a middleware system to the Browser component.
I took the already existing \React\Http\Io\MiddlewareRunner as an example for this.
Example usage:
class MyCustomMiddleware implements \React\Http\Browser\MiddlewareInterface
{
  public function __invoke(RequestInterface $request, callable $next)
  {
    return $next($request->withHeader('X-Foo', 'Bar')); // I know this is also possible another way, but just as a demo
  }
}

$client = (new Browser())->withMiddleware(new MyCustomMiddleware());
$client->get('https://example.com/api/v1/demo');

My concrete use case right now is that I want to keep track of the last request for advanced logging. I do this by storing request information in a custom middleware.
Please let me know what you think and if I should apply some changes to my code in order for this to get merged :)

Done this some years ago over at https://github.com/orgs/php-api-clients/repositories?q=middleware-&type=all&language=&sort= and would love to see this land directly in here instead of building on top of it. Things like gzip and other compressions could also benefit from this. Other things that come to mind are metrics about requests per route/method/whatever, tracing, or authentication. Maybe even #445 could benefit from this before it lands directly in this package.
This, IMHO would be a great feature candidate for our next major: v3.

Hi @WyriHaximus,
happy to hear that this feature can be useful for others as well.
But the next new major version would be v2, not v3, wouldn't it?

Hi @WyriHaximus, happy to hear that this feature can be useful for others as well.

Well, I'm not the only one to convince, talked about this with @clue and @SimonFrings in the past and we had other features to include back then.

But the next new major version would be v2, not v3, wouldn't it?

We went with v3 instead of v2 for aesthetic reasons and to keep it in line with other packages already having a v2. With v3 we're pulling everything on the same minimum version again.

@R4c00n Thanks for opening this PR, this is definitely a cool feature and something I want to see being part of this component! 👍

I also don't know what the error in the PHP5.3 builds wants to tell me.

It seems like it has some problem with the invoke() of your interface, but I think we don't even need a new interface for this and ultimately will resolve the problem with PHP 5.3.

But the next new major version would be v2, not v3, wouldn't it?

As @WyriHaximus said, we decided to go for v3 instead of v2 to keep our versioning consistent across all our projects (especially because of promise v3), you can read all about our decision here: https://github.com/orgs/reactphp/discussions/472#discussioncomment-3680968
Also a little heads up, once all tests are green and this is ready to merge, make sure to combine your commits into one. Nothing to worry about now, I think it makes most sense to do this, once everything is in and functional ;)

It seems like this ticket is open for quite a while now and haven't received any updates since. To avoid issues and pull request laying around for too long, I'll close this for now.
We're currently working towards a v1.10.0 of our HTTP component and once this is released, we can start with the feature implementations for HTTP v3 as discussed in #517. As @WyriHaximus said above, this could be a good v3 candidate so we can reopen/revisit this once we're sure this will be part of the v3 release. If this doesn't involve any BC breaks, it's also possible to add this in a following v3.1, v3.2, etc.  👍


feat: Tutorial Module 1: LLMs and Prompt Engineering

Intro to LLMs: a large amount of data (almost the entire internet), attention-based architecture, transformers, needs a lot of computing, requires millions of $, and not everyone can train them.
One way to interact with LLMs is prompts
Common LLM parameters: temperature, top-k, etc.
Prompting Techniques: Zero-shot, few-shot, and maybe another technique like chain-of-thought or ReAct with OLMo

Intro to LLMs: a large amount of data (almost the entire internet), attention-based architecture, transformers, needs a lot of computing, requires millions of $, and not everyone can train them.

One way to interact with LLMs is prompts

Common LLM parameters: temperature, top-k, etc.

Prompting Techniques: Zero-shot, few-shot, and maybe another technique like chain-of-thought or ReAct with OLMo

According to our original plan, #39 comes after this module, but I think #39 can overlap with LLM parameters / prompting techniques section in this module.

https://github.com/uw-ssec/tutorials/blob/main/SciPy2024/module1/llms-and-prompt-engineering-with-olmo.ipynb


Provide option to configure the "KwokConfiguration" for "kwok in cluster".

What would you like to be added?
We added a config map containing "https://kwok.sigs.k8s.io/docs/user/stages-configuration/" and mounted the volume on the kwok deployment file generated by Kustomization, with --config option, however this is not working.
So would be great if this is supported.
Why is this needed?
feature parity with kwokctl.

Of course, I have plans to support crd for this.
#264


Failed to parse incoming request: runtime error: index out of range [0] with length 0

Hi there, I have a WS-2902A and have it working according to the instructions. On my server I'm receiving the error message "Failed to parse incoming request: runtime error: index out of range [0] with length 0".
My /metrics currently look like:
battery{name="Yorkshire Estates",sensor="outdoor"} 0
temperature{name="Yorkshire Estates",sensor="dewpoint"} 35.80457327367417
temperature{name="Yorkshire Estates",sensor="feelsLike"} 45
temperature{name="Yorkshire Estates",sensor="indoor"} 72
temperature{name="Yorkshire Estates",sensor="outdoor"} 45
It stops there. Could you help me diagnose the bad data causing the metrics to stop part way through?

Hi @crouthamela! Could you obtain the data your weather station is sending to the server? Here's how I would do that:

Install netcat via sudo apt install netcat-openbsd (assuming you are running on debian-based linux)
Stop ambientweatherexporter
Run netcat listening on the port ambientweatherexporter was listening on: nc -l 1234
If you still have a prometheus or other metrics scraper running, you may see its requests, ctrl-c to close the connection, restart nc to listen again
You should end up with output something like this:

GET /data/report/stationtype=AMBWeatherV4.3.2&PASSKEY=XX:XX:XX:XX:XX:XX&dateutc=2024-02-10+03:34:26&tempinf=65.8&battin=1&humidityin=61&baromrelin=29.959&baromabsin=29.519&tempf=49.8&battout=1&humidity=68&winddir=87&winddir_avg10m=87&windspeedmph=0.2&windspdmph_avg10m=0.7&windgustmph=1.1&maxdailygust=8.1&hourlyrainin=0.000&eventrainin=0.000&dailyrainin=0.000&weeklyrainin=0.000&monthlyrainin=0.000&yearlyrainin=6.480&solarradiation=0.00&uv=0&temp2f=68.2&humidity2=51&temp3f=67.1&humidity3=54&temp4f=59.7&humidity4=57&temp5f=70.2&humidity5=55&batt2=1&batt3=1&batt4=1&batt5=1&batt_co2=1 HTTP/1.1
Host: <IP_ADDRESS>
Connection: close
User-Agent: ESP8266

I should be able to debug the issue with that output. 😃

Thanks! Here is the output:
GET /data/report/stationtype=AMBWeatherV4.3.4&PASSKEY=80:7D:3A:49:6E:AB&dateutc=2024-02-10+03:44:32&tempinf=71.4&humidityin=33&baromrelin=29.761&baromabsin=29.610&tempf=44.8&humidity=71&winddir=76&windspeedmph=0.7&windgustmph=1.1&maxdailygust=9.2&hourlyrainin=0.000&eventrainin=0.000&dailyrainin=0.000&weeklyrainin=0.000&monthlyrainin=0.189&totalrainin=236.220&solarradiation=0.00&uv=0&batt_co2=1 HTTP/1.1
Host: <IP_ADDRESS>
Connection: close
User-Agent: ESP8266

Found the issue! The code was expecting "battout", "battin", and "yearlyrainin" as parameters in the url. I've fixed that issue and made it more robust to any missing previously expected params in the url. I just released v1.5.0, please check it out and let me know if it works!

That fixed it for me, thanks! I checked the data in /metrics vs the netcat output and I'm missing a few datapoints. Would you be willing to implement these few?
tempf=44.8             (outdoor temp)
humidity=71            (outdoor humidity)
windgustmph=1.1
maxdailygust=9.2
hourlyrainin=0.000
PS - Haven't seen Trogdor in a long time!

Oops, I inverted some error checks. You should get these fields as well from v1.5.1:

temperature{sensor="outdoor"}
wind_speed_mph{type="sustained"}
humidity{sensor="outdoor"}
dewpoint
temperature{sensor="dewpoint"}
temperature{sensor="feelsLike"}

Looking good now, thanks!

Awesome! Hope it meets your needs.
And the Trogdor comes in the night!


Add webhook to validate service override endpoint type

Can also be called from the openstack-operator webhook on the OctaviaSpecCore, like for other operators in [1].
Depends-On: https://github.com/openstack-k8s-operators/lib-common/pull/505
[1] https://github.com/openstack-k8s-operators/openstack-operator/blob/d2703d3a321c979dacaca95b5d4a634bf116e0db/apis/core/v1beta1/openstackcontrolplane_webhook.go#L181

/hold until after freeze

/test octavia-operator-build-deploy-kuttl


Resource requirements in CWL not respected when restarting

I'm using LSF as a batch system, and I have resource requirements defined in CWL as shown below:
requirements:
  InlineJavascriptRequirement: {}
  ResourceRequirement:
    ramMin: 20
    coresMin: 2

cwltoil correctly requested 20 GB of memory initially,
RESOURCE REQUIREMENT DETAILS:
 Combined: select[type == any] order[iounits] rusage[mem=20.00:iounits=1.00] sp
                     an[hosts=1] affinity[thread(1)*1]
 Effective: select[type == any] order[iounits] rusage[mem=20.00,iounits=1.00] s
                     pan[hosts=1] affinity[thread(1)*1]

but if I restart the job, cwltoil only requests 2 GB of memory.
 RESOURCE REQUIREMENT DETAILS:
 Combined: select[type == any] order[iounits] rusage[mem=2.00:iounits=1.00] spa
                     n[hosts=1] affinity[thread(1)*1]
 Effective: select[type == any] order[iounits] rusage[mem=2.00,iounits=1.00] sp
                     an[hosts=1] affinity[thread(1)*1]

@hisplan that's bizarre.. Did this happen when you manually restarted an entire pipeline run or when a single job/step was retried automatically?

We have a workflow that runs a couple of tools sequentially. One tool in the middle of the chain failed due to temp directory permission issue, so we fixed it and reran cwltoil with --restart, and the job failed again, but this time due to lack of memory (only 2 GB requested)
I also tried a very simple job that only has one tool associated with it - the same error received.

@hisplan From the CWL v1.0 spec: http://www.commonwl.org/v1.0/CommandLineTool.html#ResourceRequirement

ramMin Minimum reserved RAM in mebibytes (2**20)

ramMin is always in mebibytes (known as megabytes by some) -- cwltoil does correctly translate this, but different LSF clusters vary in their units and Toil has yet to adapt to that, see https://github.com/BD2KGenomics/toil/issues/1691

I think I'm running into similar issues using toil-cwl-runner on an LSF cluster. I've tried on a simple example, where I've tweaked the memory requirements in CWL after the command line tool failed. It seems, however, that toil doesn't pick up on that. Is this an expected behavior or a bug?
It is important for us that we could restart a complex workflow with different resource requirements without having to restart from scratch.
I've tried the following using a recent commit on master (https://github.com/DataBiosphere/toil/commit/f5c737902ff7b93c2d806f981c316a85a80cfcb3).
I attempted to run a dummy CommandLineTool which uses roughly $(inputs.bytes) of RAM (see also https://stackoverflow.com/questions/20200982/how-to-generate-a-memory-shortage-using-bash-script):
cwlVersion: v1.0
class: CommandLineTool
requirements:
  - class: ShellCommandRequirement
  - class: ResourceRequirement
    ramMin: 1000
    ramMax: 1000

arguments:
  - shellQuote: false
    valueFrom: |
     yes | tr '\\n' 'x' | head -c $(inputs.bytes) | grep no > file.out
inputs:
  bytes:
    type: long
outputs:
 myfile:
   type: File
   outputBinding:
     glob: "file.out"

bytes parameter was set to<PHONE_NUMBER> so using overall a bit more than 2G.
Running it with toil-cwl-runner --logDebug --logFile toil.log --retryCount=0 --batchSystem=lsf --disableCaching --jobStore myjobstore uses_memory.cwl arguments.yml crashes as expected since LSF kills the job once it used up the 1000M it allocated:
Issued job 'PATH_DELETED/uses_memory.cwl' L/9/jobGtHAkU with job batch system ID: 0 and cores: 1, disk: 2.0 G, and memory: 1000.0 M

Changing ramMin and ramMax to 3000 in uses_memory.cwl and rerunning it with toil-cwl-runner --logDebug --logFile toil.log --retryCount=0 --batchSystem=lsf --disableCaching --jobStore myjobstore --restart uses_memory.cwl arguments.yml still leads to a crash and yields the following:
INFO:toil.leader:Issued job 'PATH_DELETED/uses_memory.cwl' L/9/jobGtHAkU with job batch system ID: 0 and cores: 1, disk: 2.0 G, and memory: 2.0 G

So interestingly toil seems to fall back to default settings after a restart.
I've tried a similar experiment where I ran toil locally (i.e. without --batchSystem=lsf) and manually killed the grep command and then restarted the job again with different memory requirements. Here, the new memory requirements were also ignored but the previous settings of 1000M were taken, not the default ones (the behavior might be different not because of local vs LSF but perhaps due to when/how the worker was killed).


Use tsconfig.json for TS transformation when running browser tests

Description
With this change browser tests will use configuration files (package.json, jest.config.js) from local directory rather than using the ones provided in the image. That makes sure that changes to configs immediately take effect.
Additionally this change sets up ts-jest to use tsconfig.json provided in the tests. Until now tsconfig.json hasn't been used at all.
Related to #2955

Oops, I enabled auto-merge and it got merged automatically.

@kmcnellis please take a look as Brett suggested and I'll address comments in a follow up PR


[store] mobile support

Hello, I've run into a panic with tauri-plugin-store.
This happens on the Android emulator, but not on Linux desktop. I'm using the Tauri 2.0 beta so I can have mobile support.
I have this setup function:
pub fn setup_app(app: &mut App) -> Result<(), Box<dyn Error>> {
    let store = StoreBuilder::new("app_data.bin").build(app.handle().clone());
    let app_data: AppData = Mutex::new(AppDataInner::new(store)?);
    app.manage(app_data);

    Ok(())
}

And when running in the Android emulator, it crashes now with
 Tauri plugin: pluginId: path, command: getDataDir
2024-02-23 16:10:36.357 23941-23965 RustStdoutStderr        com.tauri.sage                I  thread '<unnamed>' panicked at /home/rigidity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tauri-2.0.0-beta.4/src/app.rs:965:11:
2024-02-23 16:10:36.357 23941-23965 RustStdoutStderr        com.tauri.sage                I  Failed to setup app: error encountered during setup hook: data store error: No such file or directory (os error 2)
2024-02-23 16:10:36.357 23941-23965 RustStdoutStderr        com.tauri.sage                I  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
2024-02-23 16:10:36.358 23941-23965 RustStdoutStderr        com.tauri.sage                I  attempt to unwind out of `rust` with err: Any { .. }

For what it's worth, there were some other file not found errors and warnings as well, not just this. Not sure if that part is normal or not.

The error occurs on load() and if I check if the file exists and don't call load if it doesn't, it seems to work as expected.

The issue is not mobile support, it's using it purely from the Rust side isn't as ergonomic and doesn't handle saving or loading by default if you manually create the store without having the plugin manage it. And when loading you should check if the file exists first.

i really thought the plugin doesn't support mobile because the file systems works so different on mobile. But i guess we can update the readme table about that then 😅
Also, load() is not supposed to panic if the file doesn't exist, but just return an error. Are you unwrapping the load result or does it really panic internally? Your code only shows the StoreBuilder which doesn't interact with the file system at all as you noticed already.

i really thought the plugin doesn't support mobile because the file systems works so different on mobile. But i guess we can update the readme table about that then 😅
Also, load() is not supposed to panic if the file doesn't exist, but just return an error. Are you unwrapping the load result or does it really panic internally? Your code only shows the StoreBuilder which doesn't interact with the file system at all as you noticed already.

Yes, I was unwrapping it. Handling it properly fixes the issue also.
It does seem to work on mobile for me as long as the file is within the app directory.

It does seem to work on mobile for me as long as the file is within the app directory.

Can you check if #1011 makes this a bit easier?


WIP Fix session replication autoconfigure

TODO

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@mmoayyed Thanks. Should I backport this fix to v6.2.x?

No, I should be able to easily cherry-pick so it'd be less work for you. That said, any particular breaking changes in behavior that should be noted for 6.2?

Thanks.
In most cases, I think people don't know about the autoConfigureCookiePath option. So either they need /cas/ or they set the path on their own. In both cases, it should work after the fix, either as the /cas/ path will be computed (via the autoconfiguration) or as their defined path will be used (no autoconfiguration).
The only problematic use case I can think of is someone disabling the autoConfigureCookiePath option and relying on the default /cas/ path. After the fix, the path will be "" and this could lead to issues. But this seems unlikely.
Raise a warning if the autoConfigureCookiePath property has been explicitly set to false.

I concur; that seems like a very unlikely scenario, but I'll try to make a note of it in the release notes. Thanks!


Is it production ready? Distribution and hosting options.

Is Ocelot is production ready?
If so, are you guys using docker containers to distribute your .net core solutions with Ocelot?
Are you using Azure, AWS, Linux VM or something else?

p.s
Just thinking to go with .net core for my next project and currently in research mode thinking about the architecture, distribution and hosting options, etc.

@kuncevic

I can't say if it is production ready yet. I would like to use it where I work but we need something from NET Standard 2.0 which has not been released yet. When this is released I'm hoping where I work would be interested in trying Ocleot out.

I am using docker but haven't put up an image yet.

You can use anything to host your containers, Azure, AWS, VMs etc are all fine.

I would like to try it out at some point soon. Form the description it is sounds like it is handles the IdentityServer tokens which is making a lot of sense as I am already using IdentityServer.
What exactly it is missing from NET Standard 2.0? Can you give a bit more light on that?

@kuncevic I have applied it to the product environment, in the process of using ocelot to improve the functional characteristics

@kuncevic at my work we would need a custom middleware injected into Ocelot that uses something from .NET Standard 2.0. I cant really say what it is as work related and not sure if Im allowed!


Windows 10

Hi,
I was just wondering if this is easy to use on wondows 10 or should I use Ubuntu?

I'm using Windows, but it should work on Ubuntu.

I'm having issues using it after I build it in Visual Studio. It just shuts down. Tried looking at a previous thread regarding something similar, but couldn't solve the issue.
Any pointers/hints? We're using your software along with a HackRF One in a bachelors assignment, trying to spoof a DJI drone. But as you may understand, getting nowhere without the program working.

How did you run the software? You have to run it on a command prompt window to specify options.

I'm having no trouble to build the software with VS2017 and run it on Windows 10:
https://drive.google.com/open?id=1lZPTYtHcYtvITYiZwDhNymXUCMFiYv4G
You have to open the command prompt first and type in the command to run the software.

Thank you, of course it was user error from my side.
We are pretty green to this, would you be able to give us some advice on setting up for right ephemerides and maybe some other things so this could be a little more plug 'n play?
Much appreciated

Please try the prebuilt executable in the release page:
https://github.com/osqzss/gps-sdr-sim/releases
Open a command prompt windows from the start menu, move to the release folder, and type in the following command line:
> gps-sdr-sim -e brdc3540.14n

Ok, so far it seems to work. My next issue is really to transfer it to the hackrf.
"> hackrf_transfer -t gpssim.bin -f<PHONE_NUMBER> -s 2600000 -a 1 -x 0"
This command isn't recognized as an internal or external command.
Sorry for disturbing you with this, but I'm really trying to figure this out.

You first have to build the HackRF host tools.
https://github.com/mossmann/hackrf/tree/master/host

Okey. At this time, we can't seem to install the HackRF host tools, mostly because of lack of competence I guess, but we're not able to get the installation to work properly.
Do you have any suggestions/advice for what we can do from here, since we may not be able to test the gps-sim in our bachelor? Any help is much appreciated.

Try PothosSDR. It contains the prebuilt HackRF host tools (and many others) for Windows.
https://github.com/pothosware/PothosSDR/wiki/Tutorial#download-and-install
You can find the hackrf_transfer executable and all the necessary dependencies in the PothosSDR/bin folder.

Thank you, it seems to be working fine now. May be questions that occur later though.

I have found recent brdc file from NASA. But it doesn't seem to change the location of anything, not our drone or phones or gps-watches. What things are we missing to determine a new position to broadcast from the SDR?

Hi,
We seem to have a found out why the drone won't change position. It doesn't seem like the HackRF is transmitting anything, despite the TX led glowing. Any ideas?

hello sir , I am new to visual studio can you please explain me how to build GPS sdr sim in windows.

Start Visual Studio.
Create an empty project for a console application.
On the Solution Explorer at right, add "gpssim.c" and "getopt.c" to the Souce Files folder.
Select "Release" in Solution Configurations drop-down list.
Build the solution.

Can we also generate that GPS signal using cmd prompt??


[FLINK-11191][table] Check for ambiguous columns in MATCH_RECOGNIZE

What is the purpose of the change
Added a validation that checks if no ambiguous columns are defined in MATCH_RECOGNIZE clause. Without the check there is a cryptic message thrown from code generation stack.
Verifying this change

org.apache.flink.table.match.MatchRecognizeValidationTest#testValidatingAmbiguousColumns

Does this pull request potentially affect one of the following parts:

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

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Hi @dianfu, yes once it is solved in calcite we can remove those checks here.

OK. Thanks for the confirmation. Make sense to me.


Windows installer automatically restarts computer WITHOUT PROMPTING THE USER.

Describe the bug

After doing a fresh install of Chatterino on windows, the installer automatically reboots the computer WITHOUT prompting the user.
To Reproduce

Use the official Windows installer from the Chatterino website, complete steps, and you will get rebooted.
Expected behavior

I'd expect the software to prompt first
Chatterino version

Chatterino 2.1.5 (commit c6e1a1de2)

Cannot confirm, tried on Windows 10 machine and fresh VM

Must not be reproducible, closing ticket

Does it happen again if you reinstall, or have you perhaps missed a prompt by accident?

I have this same problem. With a fresh Windows 10 install, the last step of the Chatterino install will reboot the system without warning.

I tried to replicate the problem with a re-install on my PC as well as with a fresh install into a virtual machine. Neither of the produced the restart. For some reason, it only happens in a truly fresh install on physical hardware.
The next time I reset my PC (in a matter of weeks or months), I will try to take a video of exactly what happens.

Hi. I actually needed to re-install Windows this morning and had the opportunity to re-install Chatterino on a fresh, physical system. I made a video of the process and uploaded it to YouTube: https://www.youtube.com/watch?v=zqieort5BKk
The automatic restart occurs in the video at 2m 15s.
The automatic restart occurs a split-second after the final installation screen shows up. My guess is there is a bug that triggers the restart here without waiting for the user to click "Finish."
After re-watching the video, I did notice that my mouse cursor just happened to be over the "Finish" button, but I can assure you my hands were not on my mouse or keyboard at the time as I was adjusting my grip on the iPad I was using to record.

Same thing happened to forsen on stream, his PC was restarted without prompt

Installer will now prompt

Only screen I got was this:


Use a more strict type for variant of cards

As discussed in a previous PR.
Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)

Another alternative would have been to support a (very) small set of extremely specialised props.
<Grid container>
  <Grid item>
    <InfoCard fullHeight>...

(or even gridItem instead of fullHeight if it really needs to be a special thing)
But now I'm getting carried away :) Some other day!

I think it would be neat if the size in the layout wasn't something that the card controls itself, but comes from the outside grid.
But I think adding typings here already makes it a lot harder to introduce new variants 😆 so we are on the right track.


Command Access to Buy/Sell?

Love your plugin it's great!
We have a request, we'd really like for players to be able to access the global player shops by player/Items through commands. No need to teleport to player/shops to buy/sell.
f.e. commands like:   (added the " cs " for CarrotShop - custom command)
/csbuy clay   (would list in chat; name of seller, amount in stock and price)
/cssell clay  (would list in chat; name of buyer, amount buyer wants and price)
1. Player clicks on the seller/buyer name to buy/sell from.
2. Asks buyer/seller for the amount to buy/sell.
3. Buyer/seller inputs amount in chat and Profit!

/cslist <player>  (would list all items player is selling/buying, amount in stock and price)
Then same process as above to buy/sell.

Would this be something you'd be interested in adding? Makes server management and player interaction simpler, faster and more enjoyable. We'd love to see this added to our servers soon.
Thank you for your great work.

Shouldn't it be specific item instead of Random crap, to avoid gimmicks and frauds?

I mean the text on the sign can be whatever the user want and you can sell say "redstone pack" that contains multiple items (redstone, piston...)

I understand.
You could add, in brackets, the content of what's being sold, regardless of what the "sign" says?
So if  could says f.e:
2 Diamonds  $100 {5 diamonds}
1 Redstone pack $100 {1 redstone, 2 Pistons}
¯_(ツ)_/¯      if possible of course.

Issue #53 would be similar to this request.
To use commands in game to display and interact.


Approach for Cross Validation and Seeding

Thanks for this wonderful framework.
It would be really helpful if you can help me with an approach for K-fold cross validation.
With the help of classes RandomTileDataset and TileDataset, I'm able to sample tiles from tiffle files but, how can I validate by performing k-fold cross validation over the entire training data picking some validation tiles in the first round of training and then picking the other tiles in the subsequent round of training without leakage of data between multiple validation folds.
train_ds = RandomTileDataset(files, ...)
valid_ds = TileDataset(files, ...)

Also, please let me know if RandomTileDataset and TileDataset picks tiles without leakage between two datasets. That is, are both the splits exclusive of each other? Is there a chance of some of the validation tiles picked by TileDataset to be present in the random tiles picked by RandomTileDataset
On a related note, please help me with the required seeds that should be set for the entire pipeline with steps such as dataset/data loader preparation, training, inference, etc.
Thanks in advance.

Hi @sreevishnu-damodaran ,
Thanks for bringing up this issue. In your example, there would possibly be data leakage between the RandomTileDataset and TileDataset. The RandomTileDataset samples 1*sample_mult random tiles from each image during one epoch. The TileDataset performs standard tiling (+overlap via the padding parameter) on the images and can be limited to val_length randomly sampled validation tiles (using a fixed 'val_seed').
At the current stage, the default way of doing cross validation is simply by splitting files into train and validation sets (as implemented in the EnsemleLearner class using sklearn).
This approach ensures no data leakage and between images and gives a good estimate on the generalization of the model. However, if only a few images are available for training (as this is the case in the HuBMAP-20 competition), the performance of the single models trained on fewer data points may be degraded compared to models that have seen parts (tiles) of all images.
We are planning to add a more detailed documentation of this package soon, until then, you can find the whole training and inference pipeline implemented in the EnsembleLearner class.
If you have any suggestions on how to implement a solution for this issue, let me know :)

Thanks a lot @matjesg
That helps. I was doing the same file based split for cross-validation.
Sure. I'll let you know if I get any ideas. As of know, I have just started a few experiments with the HuBMAP-20 competition and deepflash2 is a huge help.


Included drush-launcher has dependency which causes warnings with PHP 8.2

See https://github.com/drush-ops/drush-launcher/issues/102
The project has not been updated since Feb 2022 and cannot see much answer on the issues either. I wonder if drush-launcher is active anymore...
Originally posted by @back-2-95 in https://github.com/wodby/drupal-php/issues/95#issuecomment-1377231343

Fixed in #98