镜像编译报错

按照文档给的方法，做镜像时报错， 日志如下：
Build NeurSafe FL all images.
------------Build nsfl-base:latest----------------
Sending build context to Docker daemon  3.994MB
Step 1/6 : FROM python:3.7.8
---> d70fc156eb55
Step 2/6 : COPY deploy/scripts/install_bazel.sh /tmp/install_bazel.sh
---> Using cache
---> 3b8509353a39
Step 3/6 : RUN bash /tmp/install_bazel.sh &&     rm -f /tmp/install_bazel.sh
---> Running in 2140051bb7df
Bazel installer
Bazel is bundled with software licensed under the GPLv2 with Classpath exception.
You can find the sources next to the installer on our release page:
https://github.com/bazelbuild/bazel/releases

Build information

Commit
Uncompressing.......

Bazel is now installed!
Make sure you have "/usr/local/bin" in your path. You can also activate bash
completion by adding the following line to your ~/.bashrc:
source /usr/local/lib/bazel/bin/bazel-complete.bash
See http://bazel.build/docs/getting-started.html to start a new project!
/
Removing intermediate container 2140051bb7df
---> b90e69acac42
Step 4/6 : COPY requirements.txt /tmp/neursafe_fl/requirements.txt
---> 86480b6e4ba4
Step 5/6 : SHELL ["/bin/bash", "-c"]
---> Running in 66b34cb54ea6
Removing intermediate container 66b34cb54ea6
---> 270f8645bcce
Step 6/6 : RUN python3.7 -m pip install -r /tmp/neursafe_fl/requirements.txt &&         rm -rf ~/.cache/pip /tmp/neursafe_fl
---> Running in 261cab5ae3d4
Collecting click==7.1.2
Downloading click-7.1.2-py2.py3-none-any.whl (82 kB)
Collecting urllib3==1.26.4
Downloading urllib3-1.26.4-py2.py3-none-any.whl (153 kB)
Collecting absl-py==0.11.0
Downloading absl_py-0.11.0-py3-none-any.whl (127 kB)
Collecting boto3==1.17.67
Downloading boto3-1.17.67-py2.py3-none-any.whl (131 kB)
Collecting cryptography==3.3.1
Downloading cryptography-3.3.1-cp36-abi3-manylinux2010_x86_64.whl (2.6 MB)
Collecting lmdb==1.0.0
Downloading lmdb-1.0.0-cp37-cp37m-manylinux1_x86_64.whl (280 kB)
Collecting grpclib==0.4.1
Downloading grpclib-0.4.1.tar.gz (57 kB)
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Preparing wheel metadata: started
Preparing wheel metadata: finished with status 'done'
Collecting protobuf==3.14.0
Downloading protobuf-3.14.0-cp37-cp37m-manylinux1_x86_64.whl (1.0 MB)
Collecting tensorflow==2.4.0
Downloading tensorflow-2.4.0-cp37-cp37m-manylinux2010_x86_64.whl (394.7 MB)
Collecting cgroupspy==0.1.6
Downloading cgroupspy-0.1.6.tar.gz (14 kB)
Collecting watchdog==0.10.3
Downloading watchdog-0.10.3.tar.gz (94 kB)
Collecting torch==1.7.1
Downloading torch-1.7.1-cp37-cp37m-manylinux1_x86_64.whl (776.8 MB)
Collecting torchvision==0.8.2
Downloading torchvision-0.8.2-cp37-cp37m-manylinux1_x86_64.whl (12.8 MB)
Collecting nvidia-ml-py==11.450.51
Downloading nvidia-ml-py-11.450.51.tar.gz (23 kB)
Collecting diffiehellman==0.13.3
Downloading diffiehellman-0.13.3.tar.gz (5.3 kB)
Collecting secret-sharing==0.2.7
Downloading secret-sharing-0.2.7.tar.gz (6.3 kB)
Collecting kubernetes==12.0.1
Downloading kubernetes-12.0.1-py2.py3-none-any.whl (1.7 MB)
Collecting psutil==5.8.0
Downloading psutil-5.8.0-cp37-cp37m-manylinux2010_x86_64.whl (296 kB)
Collecting tornado==6.1
Downloading tornado-6.1-cp37-cp37m-manylinux2010_x86_64.whl (428 kB)
Collecting pymongo==3.11.3
Downloading pymongo-3.11.3-cp37-cp37m-manylinux2014_x86_64.whl (512 kB)
Collecting psycopg2==2.7.7
Downloading psycopg2-2.7.7-cp37-cp37m-manylinux1_x86_64.whl (2.7 MB)
Collecting pycryptodome==3.10.1
Downloading pycryptodome-3.10.1-cp35-abi3-manylinux2010_x86_64.whl (1.9 MB)
Collecting pyOpenSSL==20.0.1
Downloading pyOpenSSL-20.0.1-py2.py3-none-any.whl (54 kB)
Collecting six
Downloading six-1.16.0-py2.py3-none-any.whl (11 kB)
Collecting jmespath<1.0.0,>=0.7.1
Downloading jmespath-0.10.0-py2.py3-none-any.whl (24 kB)
Collecting s3transfer<0.5.0,>=0.4.0
Downloading s3transfer-0.4.2-py2.py3-none-any.whl (79 kB)
Collecting botocore<1.21.0,>=1.20.67
Downloading botocore-1.20.112-py2.py3-none-any.whl (7.7 MB)
Collecting cffi>=1.12
Downloading cffi-1.15.0-cp37-cp37m-manylinux_2_12_x86_64.manylinux2010_x86_64.whl (427 kB)
Collecting h2<5,>=3.1.0
Downloading h2-4.1.0-py3-none-any.whl (57 kB)
Collecting multidict
Downloading multidict-6.0.2-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (94 kB)
Collecting astunparse~=1.6.3
Downloading astunparse-1.6.3-py2.py3-none-any.whl (12 kB)
Collecting termcolor~=1.1.0
Downloading termcolor-1.1.0.tar.gz (3.9 kB)
Collecting keras-preprocessing~=1.1.2
Downloading Keras_Preprocessing-1.1.2-py2.py3-none-any.whl (42 kB)
Collecting numpy~=1.19.2
Downloading numpy-1.19.5-cp37-cp37m-manylinux2010_x86_64.whl (14.8 MB)
Collecting wheel~=0.35
Using cached wheel-0.37.1-py2.py3-none-any.whl (35 kB)
Collecting gast==0.3.3
Downloading gast-0.3.3-py2.py3-none-any.whl (9.7 kB)
Collecting flatbuffers~=1.12.0
Downloading flatbuffers-1.12-py2.py3-none-any.whl (15 kB)
Collecting tensorflow-estimator<2.5.0,>=2.4.0rc0
Downloading tensorflow_estimator-2.4.0-py2.py3-none-any.whl (462 kB)
Collecting google-pasta~=0.2
Downloading google_pasta-0.2.0-py3-none-any.whl (57 kB)
Collecting tensorboard~=2.4
Downloading tensorboard-2.9.1-py3-none-any.whl (5.8 MB)
Collecting typing-extensions~=3.7.4
Downloading typing_extensions-<IP_ADDRESS>-py3-none-any.whl (22 kB)
Collecting opt-einsum~=3.3.0
Downloading opt_einsum-3.3.0-py3-none-any.whl (65 kB)
Collecting grpcio~=1.32.0
Downloading grpcio-1.32.0-cp37-cp37m-manylinux2014_x86_64.whl (3.8 MB)
Collecting h5py~=2.10.0
Downloading h5py-2.10.0-cp37-cp37m-manylinux1_x86_64.whl (2.9 MB)
Collecting wrapt~=1.12.1
Downloading wrapt-1.12.1.tar.gz (27 kB)
Collecting pathtools>=0.1.1
Downloading pathtools-0.1.2.tar.gz (11 kB)
Collecting pillow>=4.1.1
Downloading Pillow-9.1.1-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (3.1 MB)
Collecting utilitybelt
Downloading utilitybelt-0.2.6.tar.gz (3.9 kB)
Collecting certifi>=14.05.14
Downloading certifi-2<IP_ADDRESS>-py3-none-any.whl (155 kB)
Collecting websocket-client!=0.40.0,!=0.41.,!=0.42.,>=0.32.0
Downloading websocket_client-1.3.2-py3-none-any.whl (54 kB)
Requirement already satisfied: setuptools>=21.0.0 in /usr/local/lib/python3.7/site-packages (from kubernetes==12.0.1->-r /tmp/neursafe_fl/requirements.txt (line 18)) (49.3.1)
Collecting python-dateutil>=2.5.3
Downloading python_dateutil-2.8.2-py2.py3-none-any.whl (247 kB)
Collecting google-auth>=1.0.1
Downloading google_auth-2.7.0-py2.py3-none-any.whl (160 kB)
Collecting requests
Downloading requests-2.27.1-py2.py3-none-any.whl (63 kB)
Collecting pyyaml>=3.12
Downloading PyYAML-6.0-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_12_x86_64.manylinux2010_x86_64.whl (596 kB)
Collecting requests-oauthlib
Downloading requests_oauthlib-1.3.1-py2.py3-none-any.whl (23 kB)
Collecting pycparser
Downloading pycparser-2.21-py2.py3-none-any.whl (118 kB)
Collecting hpack<5,>=4.0
Downloading hpack-4.0.0-py3-none-any.whl (32 kB)
Collecting hyperframe<7,>=6.0
Downloading hyperframe-6.0.1-py3-none-any.whl (12 kB)
Collecting tensorboard-data-server<0.7.0,>=0.6.0
Downloading tensorboard_data_server-0.6.1-py3-none-manylinux2010_x86_64.whl (4.9 MB)
Collecting google-auth-oauthlib<0.5,>=0.4.1
Downloading google_auth_oauthlib-0.4.6-py2.py3-none-any.whl (18 kB)
Collecting markdown>=2.6.8
Downloading Markdown-3.3.7-py3-none-any.whl (97 kB)
Collecting werkzeug>=1.0.1
Downloading Werkzeug-2.1.2-py3-none-any.whl (224 kB)
Collecting tensorboard-plugin-wit>=1.6.0
Downloading tensorboard_plugin_wit-1.8.1-py3-none-any.whl (781 kB)
Collecting pyasn1-modules>=0.2.1
Downloading pyasn1_modules-0.2.8-py2.py3-none-any.whl (155 kB)
Collecting rsa<5,>=3.1.4; python_version >= "3.6"
Downloading rsa-4.8-py3-none-any.whl (39 kB)
Collecting cachetools<6.0,>=2.0.0
Downloading cachetools-5.2.0-py3-none-any.whl (9.3 kB)
Collecting charset-normalizer~=2.0.0; python_version >= "3"
Downloading charset_normalizer-2.0.12-py3-none-any.whl (39 kB)
Collecting idna<4,>=2.5; python_version >= "3"
Downloading idna-3.3-py3-none-any.whl (61 kB)
Collecting oauthlib>=3.0.0
Downloading oauthlib-3.2.0-py3-none-any.whl (151 kB)
Collecting importlib-metadata>=4.4; python_version < "3.10"
Downloading importlib_metadata-4.11.4-py3-none-any.whl (18 kB)
Collecting pyasn1<0.5.0,>=0.4.6
Downloading pyasn1-0.4.8-py2.py3-none-any.whl (77 kB)
Collecting zipp>=0.5
Downloading zipp-3.8.0-py3-none-any.whl (5.4 kB)
Building wheels for collected packages: grpclib, cgroupspy, watchdog, nvidia-ml-py, diffiehellman, secret-sharing, termcolor, wrapt, pathtools, utilitybelt
Building wheel for grpclib (PEP 517): started
Building wheel for grpclib (PEP 517): finished with status 'done'
Created wheel for grpclib: filename=grpclib-0.4.1-py3-none-any.whl size=69834 sha256=8f1fa9c232c90da7d272f23f591fa3e1365471871814382d8f167565553b2621
Stored in directory: /root/.cache/pip/wheels/24/dc/d4/6f5f1421c630f0d59a00e3f6061ebd78389ec8da08913baa4a
Building wheel for cgroupspy (setup.py): started
Building wheel for cgroupspy (setup.py): finished with status 'done'
Created wheel for cgroupspy: filename=cgroupspy-0.1.6-py3-none-any.whl size=17887 sha256=8d4c650b127f20eec1c39429ca0ca2c7bfc4aa1ffa8918d890edd12abd8013d1
Stored in directory: /root/.cache/pip/wheels/6b/8e/89/f93dc69d26c2bba667b1615ffd0bb0f91b977ec59cf9e19fa8
Building wheel for watchdog (setup.py): started
Building wheel for watchdog (setup.py): finished with status 'done'
Created wheel for watchdog: filename=watchdog-0.10.3-py3-none-any.whl size=73871 sha256=4ecbbb793d124910ce65fb3f2573d1ee9f26ad8745771ee9b20806eec85d785e
Stored in directory: /root/.cache/pip/wheels/27/21/35/9d1e531f9de5335147dbef07e9cc99d312525ba128a93d1225
Building wheel for nvidia-ml-py (setup.py): started
Building wheel for nvidia-ml-py (setup.py): finished with status 'done'
Created wheel for nvidia-ml-py: filename=nvidia_ml_py-11.450.51-py3-none-any.whl size=24232 sha256=c00c3bfa8f3b3921274203d2574c8bb0ff4a45ba179cd98ff5229e4f607bc336
Stored in directory: /root/.cache/pip/wheels/b3/69/f5/6e7f8d6e3a0dbbe4db51449bf1e243a7486f43b4f344b38b8d
Building wheel for diffiehellman (setup.py): started
Building wheel for diffiehellman (setup.py): finished with status 'done'
Created wheel for diffiehellman: filename=diffiehellman-0.13.3-py3-none-any.whl size=7364 sha256=0aa386ff6559f7e259975900b38df36ec49c9ae22bf418b53bcf8215445220da
Stored in directory: /root/.cache/pip/wheels/d4/99/da/b971b9b0fb6fe78fbf1f5e1b1c4780ff68b22ade247138d7b0
Building wheel for secret-sharing (setup.py): started
Building wheel for secret-sharing (setup.py): finished with status 'done'
Created wheel for secret-sharing: filename=secret_sharing-0.2.7-py3-none-any.whl size=5745 sha256=09f43b224d7244bf7cbe66b4089e63da0aaed29d7589e640cf0ae9cae5b98bd8
Stored in directory: /root/.cache/pip/wheels/08/9e/b5/738fd7420cff4bdd74e72c2b8d9262c4be579e5022ec733475
Building wheel for termcolor (setup.py): started
Building wheel for termcolor (setup.py): finished with status 'done'
Created wheel for termcolor: filename=termcolor-1.1.0-py3-none-any.whl size=4830 sha256=6da1764c176884dbe83ed47eb210b728fded4b4edb94ba3de330bada9d740612
Stored in directory: /root/.cache/pip/wheels/3f/e3/ec/8a8336ff196023622fbcb36de0c5a5c218cbb24111d1d4c7f2
Building wheel for wrapt (setup.py): started
Building wheel for wrapt (setup.py): finished with status 'done'
Created wheel for wrapt: filename=wrapt-1.12.1-cp37-cp37m-linux_x86_64.whl size=76417 sha256=51707a7779760e891a351d2fc597a903b9037b5f3ba700281c55c877f5b272c6
Stored in directory: /root/.cache/pip/wheels/62/76/4c/aa25851149f3f6d9785f6c869387ad82b3fd37582fa8147ac6
Building wheel for pathtools (setup.py): started
Building wheel for pathtools (setup.py): finished with status 'done'
Created wheel for pathtools: filename=pathtools-0.1.2-py3-none-any.whl size=8784 sha256=29c6fab5b554144a0e52d994d99fbf042f95d7339ef8ed7034a6efb69ce8b1a0
Stored in directory: /root/.cache/pip/wheels/3e/31/09/fa59cef12cdcfecc627b3d24273699f390e71828921b2cbba2
Building wheel for utilitybelt (setup.py): started
Building wheel for utilitybelt (setup.py): finished with status 'done'
Created wheel for utilitybelt: filename=utilitybelt-0.2.6-py3-none-any.whl size=5581 sha256=7000a8f09d4112435c67f8ccc323d018cbf06551c35b23712b39084bb0eb1ee4
Stored in directory: /root/.cache/pip/wheels/fe/4e/71/1930807859723c55b0ee510e636a745dea2abea10ebf97c06f
Successfully built grpclib cgroupspy watchdog nvidia-ml-py diffiehellman secret-sharing termcolor wrapt pathtools utilitybelt
Installing collected packages: click, urllib3, six, absl-py, jmespath, python-dateutil, botocore, s3transfer, boto3, pycparser, cffi, cryptography, lmdb, hpack, hyperframe, h2, multidict, grpclib, protobuf, wheel, astunparse, termcolor, numpy, keras-preprocessing, gast, flatbuffers, tensorflow-estimator, google-pasta, tensorboard-data-server, pyasn1, pyasn1-modules, rsa, cachetools, google-auth, oauthlib, charset-normalizer, idna, certifi, requests, requests-oauthlib, google-auth-oauthlib, zipp, typing-extensions, importlib-metadata, markdown, werkzeug, tensorboard-plugin-wit, grpcio, tensorboard, opt-einsum, h5py, wrapt, tensorflow, cgroupspy, pathtools, watchdog, torch, pillow, torchvision, nvidia-ml-py, diffiehellman, utilitybelt, secret-sharing, websocket-client, pyyaml, kubernetes, psutil, tornado, pymongo, psycopg2, pycryptodome, pyOpenSSL
Attempting uninstall: wheel
Found existing installation: wheel 0.34.2
Uninstalling wheel-0.34.2:
Successfully uninstalled wheel-0.34.2
ERROR: After October 2020 you may experience errors when installing or updating packages. This is because pip will change the way that it resolves dependency conflicts.
We recommend you use --use-feature=2020-resolver to test your packages with the new resolver before it becomes the default.
tensorflow 2.4.0 requires six~=1.15.0, but you'll have six 1.16.0 which is incompatible.
Successfully installed absl-py-0.11.0 astunparse-1.6.3 boto3-1.17.67 botocore-1.20.112 cachetools-5.2.0 certifi-2<IP_ADDRESS> cffi-1.15.0 cgroupspy-0.1.6 charset-normalizer-2.0.12 click-7.1.2 cryptography-3.3.1 diffiehellman-0.13.3 flatbuffers-1.12 gast-0.3.3 google-auth-2.7.0 google-auth-oauthlib-0.4.6 google-pasta-0.2.0 grpcio-1.32.0 grpclib-0.4.1 h2-4.1.0 h5py-2.10.0 hpack-4.0.0 hyperframe-6.0.1 idna-3.3 importlib-metadata-4.11.4 jmespath-0.10.0 keras-preprocessing-1.1.2 kubernetes-12.0.1 lmdb-1.0.0 markdown-3.3.7 multidict-6.0.2 numpy-1.19.5 nvidia-ml-py-11.450.51 oauthlib-3.2.0 opt-einsum-3.3.0 pathtools-0.1.2 pillow-9.1.1 protobuf-3.14.0 psutil-5.8.0 psycopg2-2.7.7 pyOpenSSL-20.0.1 pyasn1-0.4.8 pyasn1-modules-0.2.8 pycparser-2.21 pycryptodome-3.10.1 pymongo-3.11.3 python-dateutil-2.8.2 pyyaml-6.0 requests-2.27.1 requests-oauthlib-1.3.1 rsa-4.8 s3transfer-0.4.2 secret-sharing-0.2.7 six-1.16.0 tensorboard-2.9.1 tensorboard-data-server-0.6.1 tensorboard-plugin-wit-1.8.1 tensorflow-2.4.0 tensorflow-estimator-2.4.0 termcolor-1.1.0 torch-1.7.1 torchvision-0.8.2 tornado-6.1 typing-extensions-<IP_ADDRESS> urllib3-1.26.4 utilitybelt-0.2.6 watchdog-0.10.3 websocket-client-1.3.2 werkzeug-2.1.2 wheel-0.37.1 wrapt-1.12.1 zipp-3.8.0
WARNING: You are using pip version 20.2.2; however, version 22.1.2 is available.
You should consider upgrading via the '/usr/local/bin/python3.7 -m pip install --upgrade pip' command.
Removing intermediate container 261cab5ae3d4
---> bc88ac4d0af4
Successfully built bc88ac4d0af4
Successfully tagged nsfl-base:latest
--------Build or push nsfl-base:latest Successfully-------
------------Build <IP_ADDRESS>:5000/nsfl-cli:latest----------------
Sending build context to Docker daemon  3.994MB
Step 1/6 : FROM nsfl-base:latest
---> bc88ac4d0af4
Step 2/6 : ARG FL_PROJECT_PATH=/tmp/neursafe_fl
---> Running in 2b7411ca9e93
Removing intermediate container 2b7411ca9e93
---> c8dc26ee4e5a
Step 3/6 : COPY . ${FL_PROJECT_PATH}
---> a82deb605bf0
Step 4/6 : RUN . ${FL_PROJECT_PATH}/deploy/scripts/const.properties &&     cd ${FL_PROJECT_PATH} &&     bazel build $cli_bazel_obj &&     cd -
---> Running in c01814c42655
Extracting Bazel installation...
Starting local Bazel server and connecting to it...
Loading:
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
INFO: Repository rules_python instantiated at:
no stack (--record_rule_instantiation_callstack not enabled)
Repository rule git_repository defined at:
/root/.cache/bazel/_bazel_root/86292729879514e3c2b25f87138800ba/external/bazel_tools/tools/build_defs/repo/git.bzl:195:33: in
ERROR: An error occurred during the fetch of repository 'rules_python':
Traceback (most recent call last):
File "/root/.cache/bazel/_bazel_root/86292729879514e3c2b25f87138800ba/external/bazel_tools/tools/build_defs/repo/git.bzl", line 177, column 30, in _git_repository_implementation
update = _clone_or_update(ctx)
File "/root/.cache/bazel/_bazel_root/86292729879514e3c2b25f87138800ba/external/bazel_tools/tools/build_defs/repo/git.bzl", line 36, column 20, in clone_or_update
git = git_repo(ctx, directory)
File "/root/.cache/bazel/_bazel_root/86292729879514e3c2b25f87138800ba/external/bazel_tools/tools/build_defs/repo/git_worker.bzl", line 91, column 12, in git_repo
_update(ctx, git_repo)
File "/root/.cache/bazel/_bazel_root/86292729879514e3c2b25f87138800ba/external/bazel_tools/tools/build_defs/repo/git_worker.bzl", line 103, column 10, in _update
fetch(ctx, git_repo)
File "/root/.cache/bazel/_bazel_root/86292729879514e3c2b25f87138800ba/external/bazel_tools/tools/build_defs/repo/git_worker.bzl", line 129, column 27, in fetch
_git_maybe_shallow(
File "/root/.cache/bazel/_bazel_root/86292729879514e3c2b25f87138800ba/external/bazel_tools/tools/build_defs/repo/git_worker.bzl", line 171, column 15, in _git_maybe_shallow
_error(ctx.name, start + args_list, st.stderr)
File "/root/.cache/bazel/_bazel_root/86292729879514e3c2b25f87138800ba/external/bazel_tools/tools/build_defs/repo/git_worker.bzl", line 182, column 9, in _error
fail("error running '%s' while working with @%s:\n%s" % (command_text, name, stderr))
Error in fail: error running 'git fetch origin refs/heads/:refs/remotes/origin/ refs/tags/:refs/tags/' while working with @rules_python:
Timed out
ERROR: no such package '@rules_python//python': error running 'git fetch origin refs/heads/:refs/remotes/origin/ refs/tags/:refs/tags/' while working with @rules_python:
Timed out
INFO: Elapsed time: 608.932s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)
FAILED: Build did NOT complete successfully (0 packages loaded)

网络问题，重试一遍之后可以了

problem solved

problem solved


Update needed for 4b_reflex tutorial

Hello, I just encountered an issue running the tutorial "4b_reflex".
When I run the jupyter notebook, it gives the error:  ERROR: myoLegDemo-v0 not found in env registry and mjb mentioned in the tutorial is not matching with the mjb file in myosuite/myosuite/simhive/myo_sim/leg/.
Although I replaced those with the environments and mjb files available in the repo, it doesn't work. Any advice on how to fix this? Thank you very much.

Hi Soe Lin, thank you for your interest in the reflex model. Yes, this is indeed an error in the tutorial. I will fix it and inform you once it is done.

@elladyr  -- Any update on this issue? If resolved, lets add a summary with a commit ID

The fixes have been made, and I am waiting for an independent test before merging the fix.

Thank you very much, Chun Kwang! I have tested the program and it is working now. Just one quick question. It keeps falling after three steps as in the video below. What changes should I make to make it walk longer?
https://github.com/MyoHub/myosuite/assets/51859787/49c5c281-351b-420e-a053-ff65d4551efc

Hi SoeLin, Could you tell which branch did you pull it from? Also, could you include the params file you are using?

Hi Soe Lin, could you pull from the repository again and run it? The latest updates have been merged into the main branch

Thanks, Chun Kwang! The program is working now.


[workerserver] magic bag updates

Updating the default magic bag to not include

snapshot.Checkouter
runner.OutputCreator

These are set differently in Twitter Source, and magic bag doesn't support overriding what's already in there.
tested via
go run ./binaries/setup-cloud-scoot/main.go --strategy local.local
go run ./binaries/scootapi/main.go run_smoke_test

Current coverage is 63.99% (diff: 100%)

Merging #142 into master will increase coverage by 0.26%

@@             master       #142   diff @@
==========================================
  Files            61         61
  Lines          2622       2622
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1671       1678     +7
+ Misses          833        826     -7
  Partials        118        118

Powered by Codecov. Last update 2493db7...cbaf94c

I don't see anything that restricts us from overriding magic bag defaults... it looks like you can just call bag.Put(fn)? And if this doesn't work for some reason it seems like we'd want to make it work. Can you describe what's failing exactly?

Oh you are right, just tried it with tmp dir defined in both places it does appear to override.  I thought @dbentley had mentioned that you couldn't put things with the same type in the bag or it would cause problems.  I can update this, will still need a bit of a refactor to make runner.OutputCreateor and snapshot.Checkouter their own functions that can be overridden


Extract retrier to seperate package

New package created
https://github.com/Exanlv/reactphp-retrier


Review the impact of enabling OpenSSL's assembly optimization

Goals:

[ ] Benchmark RSA decryption to verify the claimed speedup of 2-4x (OpenSSL mailing list; ping Bilal with the results)
[ ] Try to find out if the regular-asm target breaks any platform (aarch64?)
[ ] Possibly disable it in this fork, as it only supports a very limited set of platforms (my own)

Is there any reason to even turn this off? I don't think it'll be very useful, so let's just not until there's a real problem to solve here.


PhpLdapAdmin : connect to openldap with LDAPS and custom certificates

Hi,
I'm trying to set up PhpLdapAdmin to connect to the openldap server through its ldaps port. I use custom certificates on openldap (certificates signed by my CA). Since it seems PLA cannot be configured to use ldaps port in values.yaml, I had to modify the following :
PhpLdapAdmin values.yaml :
---
env:
  PHPLDAPADMIN_HTTPS: "false"
  PHPLDAPADMIN_TRUST_PROXY_SSL: "true"
  PHPLDAPADMIN_LDAP_CLIENT_TLS_CA_CRT_FILENAME: ca.crt
  PHPLDAPADMIN_LDAP_CLIENT_TLS_CRT_FILENAME: tls.crt
  PHPLDAPADMIN_LDAP_CLIENT_TLS_KEY_FILENAME: tls.key
  PHPLDAPADMIN_LDAP_CLIENT_TLS_REQCERT: "never"
replicaCount: 1
image:
  repository: osixia/phpldapadmin
  tag: 0.9.0
  pullPolicy: IfNotPresent
  pullSecrets: []
initContainers:
  - name: copy-ro-certs
    image: busybox
    command: ['sh', '-c', 'cp /tmp-certs/* /container/service/ldap-client/assets/certs/;']
    volumeMounts:
      - name: ldap-certs
        mountPath: /tmp-certs
      - name: pla-certs
        mountPath: /container/service/ldap-client/assets/certs
volumeMounts:
  - mountPath: /container/service/ldap-client/assets/certs
    name: pla-certs
volumes:
  - name: ldap-certs
    secret:
      secretName: openldap-tls-secrets
  - name: pla-certs
    emptyDir: {}
service:
  type: ClusterIP
  port: 80
  annotations: {}
ingress:
  enabled: false
  annotations: {}
  path: /
  tls: []
readinessProbe:
  httpGet:
    path: /
    port: http
livenessProbe:
   httpGet:
     path: /
     port: http
resources: {}
nodeSelector: {}
tolerations: []
affinity: {}

The idea here is to copy the ca certificates to trust the ldaps certificate. openldap-tls-secrets is composed of ca.crt, tls.key and tls.crt.
configmap.yaml :
apiVersion: v1
kind: ConfigMap
metadata:
  name: {{ template "phpldapadmin.fullname" . }}
  labels:
    app: {{ template "phpldapadmin.name" . }}
    chart: {{ template "phpldapadmin.chart" . }}
    release: {{ .Release.Name }}
    heritage: {{ .Release.Service }}
{{- if .Values.extraLabels }}
{{ toYaml .Values.extraLabels | indent 4 }}
{{- end }}
data:
{{ toYaml .Values.env | indent 2 }}
  PHPLDAPADMIN_LDAP_HOSTS: "#PYTHON2BASH:[{ '{{ template "global.server" . }}'  : [{'server': [{'tls': True},{'port':{{ .Values.global.sslLdapPort }}}]},{'login': [{'bind_id': '{{ template "global.bindDN" . }}'  }]}]}]"

Here I changed the port to use sslLdapPort.
On PLA, when trying to connect with the admin user, I get :

On the openldap pods, I get the error :
6697df2d.05320dbb 0x7fddc33326c0 conn=2167 fd=22 ACCEPT from IP=<IP_ADDRESS>:44910 (IP=<IP_ADDRESS>:1636)
6697df2d.05341d73 0x7fddc2b316c0 TLS: can't accept: error:0A00010B:SSL routines::wrong version number.
6697df2d.0535aec1 0x7fddc2b316c0 conn=2167 fd=22 closed (TLS negotiation failure)

The LDAPS port is working, I can ldapsearch locally from the pods as well as outside the cluster using the openldap service ( while trusting my custom certificates). Seems to me it is a trust issue. Am I missing something ?

Looks like an ssl version mismatch.
This is currently not supported , I ran across issues when I created the chart regarding ldaps and PLA .
Feel free to investigate and propose a PR 🙂

Ok Thank you !


tests: nested BaseModel-inherited structures are not supported

I miss an additional CHANGELOG that you could fill in by hand to indicate the changes you made, otherwise it will be difficult to further understand the difference between versions.

It is also better to add to the documentation examples of what types for models can be used and in README it would not hurt to have information about freeze versions of dataclassess_avroschema.


[1.10] Bump navstar

High-level description
Navstar compilation broken
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS_OSS-2145 Navstar compilation broken

Related tickets (optional)
Other tickets related to this change:
Checklist for all PRs

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[ ] Read the DC/OS contributing guidelines
[ ] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
https://github.com/dcos/navstar/pull/97
Instructions and review process
What is the review process and when will my changes land?
All PRs require 2 approvals using GitHub's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label [Ready For Review]


Partially overlapping union discriminators are not assignable from a union of discriminating values

Bug Report
🔎 Search Terms
tagged, discriminated, union, partially, overlapping, infinite, types, not, assignable
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about Type system behavior and Classes

I tried versions from v3.3.3 to v4.3.5, as those were available in the Playground at this time.
Note that between v3.3.3 and v3.5.1 something changed that affects type C from my example below. In v3.3.3 the assignment to const c: C is an error, from v3.5.1 its okay.
⏯ Playground Link
Playground link with relevant code
💻 Code
// Original Problem:
type A = { aprop: 'a' | RegExp } | { aprop: 'b' | RegExp };
declare const aprop: 'a' | 'b';
const a: A = { aprop }; // error

// Distillation:
type B = { bprop: 1 | string } | { bprop: 2 | string }
declare const bprop: 1 | 2;
const b: B = { bprop } // same error

// error appears only for "infinite" types, this works fine
type C = { cprop: 1 | 3 } | { cprop: 2 | 3 }
declare const cprop: 1 | 2;
const c: C = { cprop } // C['cprop'] == 1 | 2 | 3

// more detailed example
type Infinite = string;
type D = { dprop: 1 | Infinite } | { dprop: 2 | Infinite }
type Dprop = D['dprop']; // 1 | 2 | string -> "merging" seems to work correctly
declare const dprop: 1 | 2;
const d1: D = { dprop: 1 } // OK
const d2: D = { dprop: 2 } // OK
const d3: D = { dprop } // error

🙁 Actual behavior
The assignments to const a: A, const b: B, and const d3: D raise an error.
🙂 Expected behavior
As demonstrated in the assignments to const d1: D and const d2: D, my partially discriminating property dprop can be either of the two discriminating values. So It should be possible to assign to dprop a value that is either of them, as in the assignment to const d3: D.

between v3.3.3 and v3.5.1 something changed

The change was "smarter union type checking", implemented in #30779 and released in TS3.5.

In general if you have some type { a: U1, b: U2, c: U3, d, U4 }, you can't tell if that's going to be assignable to some target type without doing a computation involving size(U1) * size(U2) * size(U3) * ... different expansions of the type to enumerate all possible inhabitants. So we're always going to sometimes reject some of these assignments because the special-casing to allow the trivial cases has some limits.
That said, I don't see why this should matter when a non-literal type appears in the target.

This is the expected behavior. It is far too expensive to compute this kind of overlapping assignability for all cases, so we only currently do this work when a union has overlapping discriminant properties. A property is a discriminant property when its type consists of only unit types (e.g., 1 or "foo"). In the three failing cases above, the property in question consists of a unit type unioned with a non-unit type (string, RegExp, etc.), which means the property is not considered a discriminant and thus does not qualify for this assignability rule.
In the case of C, both types in the union contain discriminant properties as they consist only of unit types or unions of unit types (1 | 3 and 2 | 3).


Regression: choosing lowest-bandwidth codec leads to always picking audio-only variant for HLS

This was introduced by 434f1bf (CL that fixed #841). The fact that we started grouping variants by codecs and choosing the group with the smallest average bandwidth led to the player always choosing audio-only variants for HLS content that has at least one.
We can't switch from audio-only variants to audio+video, so we end up being stuck with audio-only.
A manifest to repro: https://nexxplayplus6.streaming.mediaservices.windows.net/32de1b7d-822c-43b2-b3a5-1cd97f0e9ae7/242391_src.ism/manifest(format=m3u8-aapl)
(Discovered by investigating #860).

Given #824, where we can't switch to audio-only variants anyway, we should probably solve both problems at one by filtering out audio-only variants in cases where there are audio+video variants available.

The fix for this has been cherry-picked and will be released in v2.1.5.


azure-npm randomly corrupts ip-tables. Results in connection failures between pods

What happened:
We have 3 AKS clusters, 3 nodes each. Mix of B16 and D16 nodes.
We use NetworkPolicies to restrict traffic between pods. We define pretty strict rules (per-pod & namespace).
azure-npm randomly causes the pod connections to fail, as it seems the IP table rules are getting corrupted.
Sometimes, when I inspect the clusters in the morning, I have multiple pods failing due to azure-npm corrupting the iptables, without having changed or touched anything overnight.
For example, we use argocd to manage our deployments. argocd-server will randomly fail to contact the argocd-repo-server.
Killing the azure-npm pods solves the problem. But this is not a viable solution.
I sometimes see this error in azure-npm
2021/04/23 07:06:04 [1] Error: There was an error running command: [ipset -X -exist azure-npm-784554818] Stderr: [exit status 1, ipset v7.5: Set cannot be destroyed: it is in use by a kernel component[]

What you expected to happen:
azure-npm to correctly define IP-table rules. We would expect AKS to have a bug-free CNI, as this is such a critical component of the infrastructure!
I tried upgrading azure-npm to 1.3.0, but it seems that AKS automatically manages this, and will downgrade to 1.1.8
How to reproduce it:
Very hard to say. It sometimes happens when the labels on the pods/namespaces change. But also happen randomly. Help in debugging this would be greatly appreciated.
Orchestrator and Version (e.g. Kubernetes, Docker):
AKS 1.20.2
azure-npm mcr.microsoft.com/containernetworking/azure-npm:v1.1.8`
Operating System (Linux/Windows):
Linux
Kernel (e.g. uanme -a for Linux or $(Get-ItemProperty -Path "C:\windows\system32\hal.dll").VersionInfo.FileVersion for Windows):
5.4.0-1043-azure #45~18.04.1-Ubuntu SMP Sat Mar 20 16:16:05 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Anything else we need to know?:
[Miscellaneous information that will assist in solving the issue.]

https://github.com/Azure/AKS/issues/1810

@ludydoo
We are in the process of rolling out 1.3.0 (currently rolled out in EastUS2Euap and CentralUSEuap). It will reach all production by ~05/07.
We've made significant improvements for reliability and handing scale/perf with NPM some of the details are below and beefed up our investments in this space to make it first class, this has come a long way
Improvements:

NPM will now maintain a cache of resources it has operated on resulting in reduced churn for duplicate events.
Re-sync period for shared informer reduced from 24hrs to 15 mins. This helps reduce the possibility of NPM missing resource events (Add, update or Delete)
NPM logs will now be only available through kubectl logs (stdout). NPM will NOT create log files in /var/log/azure-npm.log. This improves CPU usage by reducing Disk I/O operations

Bugs fixed

https://github.com/Azure/azure-container-networking/issues/854 (Periodic reconciliation of AZURE-NPM base chains every 5 mins.)
NPM does not exclude host network Pods from the network policies resulting in blocking of traffic and disruption in system functions such as collection of kubectl logs.
NPM now supports NameSpace label updates
Changing rule evaluation behavior to (INGRESS and EGRESS)
Before this change, NPM would have allowed traffic if there is a single “ACCEPT” rule in either ingress or egress direction. With this change, NPM evaluates both ingress and egress rules to take a decision on the packet.

Original behavior logic:
(Ingress rule 1 OR ingress rule 2 OR ingress rule 3 OR egress rule 1 OR Egress rule 2)
Current Behavior:
(Ingress rule 1 OR ingress rule 2 OR ingress rule 3) AND (egress rule 1 OR Egress rule 2)
We've also added Prometheus and azure monitor support for latency , iptables and ipset rules monitoring as well:
https://docs.microsoft.com/en-us/azure/virtual-network/kubernetes-network-policies#monitor-and-visualize-network-configurations-with-azure-npm
Release Notes:
https://github.com/Azure/azure-container-networking/releases
Can you share more about your setup details like Region, Subscription, AKS cluster details and Network policies to help you assist better?

@ludydoo
I would also like to add we are also compliant with Ginkgo E2E conformance test-suite which is maintained by sig-network.
We are currently in the process of also integrating with their cyclonus test framework (https://kubernetes.io/blog/2021/04/20/defining-networkpolicy-conformance-cni-providers/#cyclonus).

Hi @neaggarwMS
Thanks for the answer.
Our setup is as follows:
3 x AKS 1.20.2 clusters, westeurope region
When do you estimate GA of 1.3.0 for Westeurope region ? Also, is there a way we can fastrack this?
We have multiple networkpolicies.
I'll give a few examples:
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: argo-server
  namespace: argo
spec:
  podSelector:
    matchLabels:
      app: argo-server
  policyTypes:
  - Ingress
  - Egress
  ingress:
    # Allow ingress from VPN-IngressGateway
    - ports:
        - port: web
          protocol: TCP
      from:
        - namespaceSelector:
            matchLabels:
              name: istio-system
          podSelector:
            matchExpressions:
              - key: istio
                operator: In
                values:
                  - vpn-ingressgateway
    # Allow ingress from Prometheus (metrics)
    - ports:
        - port: http-envoy-prom
          protocol: TCP
        - port: 15020
          protocol: TCP
      from:
        - namespaceSelector:
            matchLabels:
              name: monitoring
          podSelector:
            matchExpressions:
              - key: prometheus
                operator: In
                values:
                  - prometheus
  egress:
    - ports:
        - port: 15012
          protocol: TCP
      to:
        - namespaceSelector:
            matchLabels:
              name: istio-system
          podSelector:
            matchExpressions:
              - key: istio
                operator: In
                values: [ pilot ]
    - ports:
        - protocol: UDP
          port: 53
      to:
        - namespaceSelector:
            matchLabels:
              name: kube-system

kind: NetworkPolicy
apiVersion: networking.k8s.io/v1
metadata:
  name: minio
  namespace: argo
spec:
  podSelector:
    matchLabels:
      app: minio
  ingress:
    - ports:
        - port: 9000
          protocol: TCP
      from:
        # Allow Argo Server Ingress
        - podSelector:
            matchExpressions:
              - key: app
                operator: In
                values: [ argo-server ]
          namespaceSelector:
            matchLabels:
              name: argo
        # Allow Ingress from Argo Workflows
        - podSelector:
            matchExpressions:
              - key: workflows.argoproj.io/workflow
                operator: Exists
          namespaceSelector:
            matchExpressions:
              - key: name
                operator: In
                values: [ argo ]
    - ports:
        - port: 15020
          protocol: TCP
      from:
        # Allow Prometheus Metrics Scraping
        - podSelector:
            matchExpressions:
              - key: prometheus
                operator: In
                values: [ "prometheus" ]
          namespaceSelector:
            matchLabels:
              name: monitoring

kind: NetworkPolicy
apiVersion: networking.k8s.io/v1
metadata:
  name: workflow-controller
spec:
  podSelector:
    matchLabels:
      app: workflow-controller
  policyTypes:
  - Egress
  - Ingress
  ingress:
    # Allow Prometheus Metrics Scraping
    - ports:
        - port: 15020
          protocol: TCP
        - port: 9090
          protocol: TCP
      from:
        - podSelector:
            matchExpressions:
              - key: prometheus
                operator: In
                values: [ "prometheus" ]
          namespaceSelector:
            matchLabels:
              name: monitoring
  egress:
    - ports:
        - port: 15012
          protocol: TCP
      to:
        - namespaceSelector:
            matchLabels:
              name: istio-system
          podSelector:
            matchExpressions:
              - key: istio
                operator: In
                values: [ pilot ]
    - ports:
        - protocol: UDP
          port: 53
      to:
        - namespaceSelector:
            matchLabels:
              name: kube-system
    - ports:
        - protocol: TCP
          port: 8081
      to:
        - namespaceSelector:
            matchLabels:
              name: argo
          podSelector:
            matchExpressions:
              - key: app
                operator: In
                values: [ repo-server ]

apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: argo-server-egress-to-kubernetes-api
  namespace: argo
spec:
  podSelector:
    matchLabels:
      app: argo-server
  policyTypes:
  - Egress
  egress:
    - to:
        - ipBlock:
            cidr: <redacted_master_api_ip>/32
      ports:
        - protocol: TCP
          port: 443

apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: argo-workflow-controller-egress-to-kubernetes-api
  namespace: argo
spec:
  podSelector:
    matchLabels:
      app: workflow-controller
  policyTypes:
  - Egress
  egress:
    - to:
        - ipBlock:
            cidr: <redacted_master_api_ip>/32
      ports:
        - protocol: TCP
          port: 443

apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: minio-ingress-from-argo-workflow
  namespace: argo
spec:
  podSelector:
    matchLabels:
      app: minio
  policyTypes:
  - Ingress
  ingress:
    - ports:
        - protocol: TCP
          port: 9000
      from:
        - podSelector:
            matchExpressions:
              - key: "workflows.argoproj.io/workflow"
                operator: Exists
          namespaceSelector:
            matchExpressions:
              - key: name
                operator: In
                values: [ cicd ]

apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: argo-server-egress-to-kubernetes-api
  namespace: argo
spec:
  podSelector:
    matchLabels:
      app: argo-server
  policyTypes:
  - Egress
  egress:
    - to:
        - ipBlock:
            cidr: <redacted_master_api_ip>/32
      ports:
        - protocol: TCP
          port: 443

kind: NetworkPolicy
apiVersion: networking.k8s.io/v1
metadata:
  name: external-dns
  namespace: external-dns
spec:
  podSelector:
    matchExpressions:
      - key: app
        operator: In
        values:
          - external-dns
          - external-dns-private
  policyTypes:
  - Ingress
  - Egress
  ingress:
    - ports:
        - port: 15020
          protocol: TCP
      from:
        - podSelector:
            matchExpressions:
              - key: prometheus
                operator: In
                values: [ prometheus ]
          namespaceSelector:
            matchLabels:
              name: monitoring
  egress:
    - ports:
        - port: 15012
          protocol: TCP
      to:
        - namespaceSelector:
            matchLabels:
              name: istio-system
          podSelector:
            matchExpressions:
              - key: istio
                operator: In
                values: [ pilot ]
    - ports:
        - protocol: UDP
          port: 53
      to:
        - namespaceSelector:
            matchLabels:
              name: kube-system
    - ports:
        - port: 443
          protocol: TCP
      to:
        - namespaceSelector:
            matchLabels:
              name: istio-system
          podSelector:
            matchExpressions:
              - key: istio
                operator: In
                values: [ egressgateway-sni-proxy ]

@ludydoo  Thank you for sharing the extensive list of NetworkPolicies. v1.3.1 is now being rolled out as we speak. Through safe deployment processes, we release the version to only a subset of regions on a given day. WestEurope should get this release by EOD Monday 3rd May. Once the cluster upgrades, please test if these issues are still persistent, if yes, you can either ping us here or create a support ticket with Azure Support. As Neha mentioned, with 1.3.1, we have added some reliability improvements which should remove flakiness with iptable rules and ipset lists.

@vakalapa
I think we faced this same issue today, after 1 year in production with AKS & CNI & Network policies, pods were not able to connect each other. Kubernetes 1.17.9, North Europe.
Removing network policies and rebooting azure-npm & coreDNS pods resolved, but is this ramdom issue still on-going is this version and region?

@tiholm, can you describe one of the Azure NPM pod and share its version? Also can you share the cluster details (Region, Subscription, Resource Group Name and Cluster Name)?

@neaggarwMS  I have opened an support issue with id<PHONE_NUMBER>002654 and discuss the private things there.

Sounds good, thanks @tiholm. We will look into that and get back on the case. We can close this github issue.

I believe we were experiencing this issue also in two clusters. One of the namespaces using egress network policies could not connect to services anymore. We could only "fix" it by removing all network policies.
There was a restart of the azure-npm pods around the time the errors first happened in both clusters.
Support request ID |<PHONE_NUMBER>01058

@BenjaminHerbert  a new release of NPM v1.3.2 is deployed and the restart of NPM might be because of that. With this version, we are changing the behavior to be inline with upstreams rules evaluation. You can find details below:
https://github.com/Azure/azure-container-networking/wiki/TSG:-NPM--v1.3.0-breaking-changes
If the egress is allowing the traffic and traffic gets dropped, there is a high probability that ingress of the destination is not allowing this traffic. Can you please evaluate all ingress rules being applied on the destination pod.

@BenjaminHerbert  thank you for the debugging session, as discussed, you are hitting this  #870 known issue.

@ludydoo Are you still facing issue ? If so can you raise a support case and request to be escalated to<EMAIL_ADDRESS>We can help resolve. until that i will be closing this issue.

It seems that the issue is not present anymore


Improvements for ORT Run details page

From 23.5.2024 front-end alignment meeting:

[x]  move downloadable results to the top of page (before JSONs)
[ ] download logs from a run - currently blocked by issue #168
[ ] implement streaming logs instead of / in addition to downloadable ones
[x] thinking forward, the JSONs are there mainly for debugging purposes currently, so a nicer way of showing job configs and results is needed

* thinking forward, the JSONs are there mainly for debugging purposes currently, so a nicer way of showing job configs and results is needed

I think the UI for that should look similar to the one used when starting a new run.

The item

implement streaming logs instead of / in addition to downloadable ones

is neither ticked nor tracked as a separate issue... @Etsija please take care that it does not fall through the cracks.


LotV base datapack

I did a straight copy from the last HotS datapack and basically just modified linked code until it stopped crashing. Not sure if I did this right or wrong, but I would hope that it at least is not a regression.
Also have another commit with the fix from
https://github.com/GraylinKim/sc2reader/issues/185#issuecomment-104150265

Other than the above this looks good. I spent a few minutes looking through your website and noticed that you have the new units in the build orders already. How is that working right now (since they aren't part of the LotV data yet)?

Added the comment.
As far as how LotV units work, I think it is because spawningtool doesn't rely on the event.unit to get the name since that varies as the unit changes and retains the final version, and I want the current name. As such, I go straight for the event.unit_type_name first if possible.
https://github.com/StoicLoofah/spawningtool/blob/32-lotv/spawningtool/parser.py#L194-L203
Maybe it's not the most proper way for the library to work, but it seems to function flexibly for new unit types.


Gevent, SentryAsgiMiddleware and ContextVars are not working together

It seems to me that #630 re-opened, when using most up to date gevent with current sentry-sdk. The culprit seems to be that the sdk calls _is_contextvars_broken in utils.py which itself uses gevent's is_object_patched function to determine if contextvars was indeed patched.
If I understand the gevent sources correctly they indeed do no longer patch contextvars on python versions >= 3.7 (https://github.com/gevent/gevent/blob/83c9e2ae5b0834b8f84233760aabe82c3ba065b4/src/gevent/monkey.py#L604)
Environment
How do you use Sentry?
Sentry SaaS (sentry.io), but error happens (already) on local installation
Which SDK and version?
python 3.9.0
sentry-sdk 1.0.0
gevent 21.1.2
Steps to Reproduce

Set up gunicorn with gevent workers, use SentryAsgiMiddleware
Try to start gunicorn with gevent (monkey patching activated)
Error about missing contextvar support is thrown

Expected Result
Sentry should work just fine as stated in https://docs.sentry.io/platforms/python/troubleshooting/ for gevent since version 20.5
Actual Result
Gunicorn workers die with the message

RuntimeError: The ASGI middleware for Sentry requires Python 3.7+ or the aiocontextvars package.
With asyncio/ASGI applications, the Sentry SDK requires a functional
installation of contextvars to avoid leaking scope/context data across
requests.

Please refer to https://docs.sentry.io/platforms/python/contextvars/ for more information.

I've got the same issue.

I implemented a potential fix for this in https://github.com/getsentry/sentry-python/pull/1157 :rocket:

This was fixed (at least for me) in Sentry Python SDK version 1.3.1 released today. :tada:


too many arguments for function-like macro invocation 'GetCurrentTime'

This is a pretty straightforward issue. The steps to reproduce are:

Open visual studio IDE with  "C++/WinRT" extension installed.
Create a new CPP project "Visual C++ -> Windows Universal -> Windows Runtime Component(C++/WinRT)
Add a macro definition "WINAPI_PARTITION_DESKTOP" to the preprocessor macro definition list in the project settings
Build and resolve the normal build issue related to runtime class implementation.
Rebuild the project so that only 1 warning remains and this warning is the topic of the issue.

It could be two things. Either the macro definition is not allowed or it is an issue in the C++/WinRT and may or may not be fixed.
I am attaching a sample project that can reproduce the issue. The attachment also contains a screenshot of the issue.
UniversalRuntimeComponent.zip

GetCurrentTime is a known collision between a Windows.h macro definition and a WinRT member. One solution is to #undef GetCurrentTime in your pch.h.


docs: Add EBS CSI driver httpPutResponseHopLimit note

Fixes #7200
Description

Adding a note for customers that use EBS CSI driver with default MDSv2 configuration

How was this change tested?

N/A

Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 83.073%

Totals

Change from base Build<PHONE_NUMBER>2:
0.0%

Covered Lines:
5595

Relevant Lines:
6735

💛  - Coveralls


Add more Management Console modules to run

Description of the new feature / enhancement
Please add Management Console modules (.msc) and control panel applets to run command recognition. Thanks.
Scenario when this would be used?
When opening any of these applets
Supporting information
No response

Bunch are. Which are you trying to access. /needinfo

Hi. The ones I tried are diskmgmt.msc (console) and power, network, sound (control panel). Thanks much
Allan
Allan Grossman
Office:<PHONE_NUMBER>
Cell:<PHONE_NUMBER>
@.*** @.***>
From: Clint Rutkas @.>
Sent: Wednesday, October 5, 2022 9:39 PM
To: microsoft/PowerToys @.>
Cc: ADG11 @.>; Author @.>
Subject: Re: [microsoft/PowerToys] Run Command (Issue #21041)
Bunch are. Which are you trying to access. /needinfo
—
Reply to this email directly, view it on GitHub https://github.com/microsoft/PowerToys/issues/21041#issuecomment-1269193231 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AIHTBWSKLY5XI7OK5B63Y5DWBYUSTANCNFSM6AAAAAAQ5QR3IY .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/AIHTBWTC5YIHCFDU6DZNADLWBYUSTA5CNFSM6AAAAAAQ5QR3I2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSLUZNA6.gif Message ID: @.*** @.***> >

@htcfreek Heiko , i thought you added a bunch.  Is there a list of MIA ones?

@crutkas
I did not start yet. But I guess you mean the other issue #20423

@crutkas
For clarification: The Program plugin which handles the "Run commands", supports only msc files and only if they have a shortcut in start menu. Because both are DLLs and special XML files, we can't add them to Program plugin.
I suggest to add both manually to the settings plugin as they are used to manage / configure the computer.

This was implemented in release 0.68. Thank you for the enhancement request!


Adding depracation warnings to Dataflow artifacts.

LGTM, I would update the pom's description as well

I updated pom.xml descriptions and the readme.


Create a Project in SAP Web IDE and Push into GitHub

Tutorial URL: https://developers.sap.com/tutorials/webide-github-import-project.html
Please specify the step you are referring to step 10 - push your local changes to GitHub
Hi gurus,
I create a project (from template) and now I am trying to push changes to GitHub. By doing so, I receive the following error: "push request failed undefined".

BR,
Pietro

Hi gurus,
Some extra piece of information:
"8:43:55 AM (git) Project ReplenishCockpit: Push request failed undefined
8:43:55 AM (git) https://github.com/sunstar-devteam/replenishment-cockpit.git: git-receive-pack not permitted
8:43:55 AM (git) Project ReplenishCockpit: Push request failed"
BR,
Pietro

The root-cause was missing permission to write. I close this thread.


Use matching extension manager version in integration tests

Currently integration tests always use the latest extension manager version. This is a problem for these reasons:

This will break existing tests for extensions when a new, incompatible version of the extension manager is published.
You want to test an extension against a specific previous release of extension manager.

Instead of using version latest the tests should use the EM version they where built against. We can implement this by using the current project version as default instead of latest in method ExtensionTestConfig.getExtensionManagerVersion().

[x] Verify consistent versions in .project-keeper.yml and pom.xml (properties/revision)
[x] Use current version for installing EM

We can implement this by using another default value in method ExtensionTestConfig.getExtensionManagerVersion() instead of latest.

Some findings.


[BUG] Unable to detect Shell version in macOS 10.15.7

General description of bug:

What happened: Fastfetch fails to detect shell version on macOS 10.15.7 in both iTerm and Terminal. Neofetch correctly detects it as zsh 5.7.1.
What should happen: Shell version should be displayed.
Fastfetch version used: Tested with 2.24, 2.25 and 2.29
Did it work in an older version: No idea, 2.24 was the first version I have used/tried.
Where did you get the binary: Compiled myself but also tried binary from GitHub release with the same results.

Often helpful information:
Screenshot:

If fastfetch crashed or froze
fastfetch_2024-11-10-crash.txt

Please test if the newest dev build fix your problem. You may download it here: https://github.com/fastfetch-cli/fastfetch/actions/runs/11776108502

Yep, that works!
One minor thing, tried with compiling myself with ./run.sh and then it displays Shell as "sh" at the end of the compile, but running fastfetch from the build directory shows Shell correct as "zsh 5.7.1"
Bit off topic but downloading the file from the link above, the zip file actually contained a zip and an tar.gz inside, is it supposed to be that way? Seems a bit redundant to have two packed files (that both contain the same things) inside a packed file.

the zip file actually contained a zip and an tar.gz inside

It's expected. They will be put in release assets


Feature Request: Two actions are possible by Switch Bot

Problem
In beta version of Switchbot there are 2 actions for one Bot
Solution
can you implement this option?
Alternatives
No response
Additional context
No response

Any possibility?

While not exactly what you are requesting, the beta (v2.4.0) allows you to do this by allowing you to send non-predefined amounts of push requests to your device. I will think about this, but there is another feature/way I'm thinking about that would accomplish this.


Update github event processor to 1.0.0-dev.20230422.1

This update removes the need for a sparse-checkout which was necessary to get the event-processor.config and CODEOWNERS files. Instead, those are pulled down from the raw.githubusercontent.com for the repository.

There's nothing that'll run that check enforcer can key off of. I'm going to override.


Streamlit app - waiting on user input in the background

When run is finishing, the app hangs as it waits for the user reply:

At the moment it prints the output in the end(you should type exit), a possible feature is to print the conversation in Streamlit Ui instead of the terminal, would you like to contribute? :-)

Yes, why not!

I added PR with this improvement https://github.com/yanivvak/dream-team/pull/9

closing now


Transition out implicit features for optional dependencies

Problem
Today cargo will implicitly create a feature for optional dependencies unless the dependency is referenced in a feature as dep:<dep_name>.
Downsides

People overlook using dep: and unintentionally create features

Exposing implementation details in their public API
Confusing users on which features to activate (#9459)

Remove the need for people to special case this (e.g. #10543)
Avoid mistakes with explicitly creating the feature (#10125)

Proposed Solution
We should stop implicitly creating features in a new Edition
Optional dependencies without a dep: reference can be either

A hard error
Allowed assuming people will then want to use it via the future #[cfg(accessible)]

The downside is users might assume a feature would exist (at first) and things not work as expected
We could start with an error and move away from it

Create private features (#10882, see also #1596)

cargo add foo --optional can implicitly create a feature with the dependency's name, if a dep:foo doesn't already exist (#11010).
Notes
No response

See also #9088

The main hurdle for transitioning is that #12130 was just barely merged though there is the workaround of "dep:foo", "foo?/feat" which would be the standard way of doing it with #10556.

@epage Do you want to keep this issue open?

If this were about a specific use case then I might want to keep it open but since its effectively "lets make an RFC", lets close it out.


All logs incorrectly write to console.error

Prerequisites

[x] Did you check the FAQ?
[x] Did you search open and closed issues to see if your issue has already been reported?

Description
All logs run through console.error blocking CI processes that fail when error is written to.
Steps to Reproduce

typings install github:aurelia/templating
There is a WARNing message about the typing being able to change.
The warning is processed through console.error making it write to stderr

Expected behavior: It should write to console.warn or console.log
Actual behavior: It wrote to console.error
Versions
1.3.1

Why? stderr is the correct place to write these warnings. Anywhere else would mean breaking programmatic usage. CI should use the exit code.

These are warnings not errors, which exit code should it be looking for for non-errors? https://nodejs.org/api/process.html#process_exit_codes

Yes, they and warnings or errors. Any non-standard output is written there. A non-error is always a 0 exit code. Anything other than 0 should be considered an error.

I agree with @PWKad I'm trying to build this using the VSTS build agent using a powershell step. While the process succeeds and returns a 0 exit code the step and build fails because:
##[error]Process completed with exit code 0 and had 1 error(s) written to the error stream.
I don't want to pipe out all output somewhere else as I'd be concerned that this would allow errors to slip through.
If there's a console.warn then this should be where warnings are written.

@blakeembrey Would you accept a PR to add a log filter flag such as --log warn so only errors are emitted when changing the level?

@sturobo console.warn writes to stderr. I would accept a PR changing what's emitted, just not where.

Sound like a code smell for this purpose.
An alternative solution is to consume typings-core directly and handle the events yourself.

@unional not sure why, every other CLI has a warning level on install command to set for the same purposes it seems.

@blakeembrey I said that backwards, you are correct it should be --loglevel error or --loglevel err so only errors are emitted not warnings or info.

Sorry, let me elaborate.
What I mean is that it seems like you would like to add the --log feature so that when you use it, you can simply hide the warning message.  You need that because you intercept stderr and use it to determine if there are errors instead of checking the exit code.
That's the code smell I talk about.

@unional I'm almost finished with a small PR one second it may make more sense.

@unional (and of course @blakeembrey ) feedback welcome on PR #700 in re: this issue.


Data engineer

Hi @Shakeyys , would you be kind enough to let us know what the issue is?
Kindly add description and details, if in case there is an issue with the page.


run non standart images like a static binary

I am assuming, I meant to use a minimal static binary as runner and binfmt_misc to make squash files executable


Feature/enhance specs

@ndushay - work in progress to revise rspecs, using this example to develop pull request practice from a feature branch into develop (leaving master for releases).  Not sure how this will work with the git flow, which is now enabled in my workspace.  If you do the pull request and it merges into origin/develop, it might conflict with the assumptions of git flow that I'm using in my workspace.  Let's see what happens.

Coverage increased (+15.25%) to 94.58% when pulling eb60660b2b792c3f2fbdf58c53319355a79f8c7a on feature/enhance_specs into 66b9faad1482329557c0aa7a965e6097b3304b63 on develop.

Lets discuss the implications of git-flow on Monday.  If no one else is using it and it makes big assumptions about how git branches have to be done, then that's going to make it hard to work on projects in a team environment. [Noted in google doc]

I'll review this after lunch.  I'm not clear on how git flow is affecting things;  I will not click the "merge" button and leave that to you.  You'll have to figure out how we can have a conversation about your pull requests, with eventual merges to master, using your tools of choice.

We can go over remaining questions f2f -- I can prolly help you w before blocks and clashes.  I think the respond_to  tests should go away, which would be one way of addressing that, too ...   but this is starting to feel like a lot of typing.

Yes, so what's the purpose of this pull request process?

If that was a rhetorical question, then feel free to ignore all of the below :)
The rationales behind the process includes:

Review by others improves the resulting code
It facilitates knowledge transfer between engineers, improving skills and building a culture of teamwork
It ensures that at least two people have seen and understand the code, reducing bugs (many eyes) and improving sustainability (higher bus factor)
It does not replace pairing / team communication and collaboration, instead it facilitates it as it provides a focus for that discussion

I'm sure @bess or @cbeer could provide a better explanation if that's insufficient!

Well, yes, it was kind-of-a rehetorical to save some typing, but now that you mention it....
I'm not entirely clear yet whether Naomi and I may just have minor differences of opinion about how to do something that can be done various ways (and that's OK), or whether we are trying to come to some kind of best-practice that we could expect DLSS to arrive at consensus on or develop a convention around on how things must be done?  (This may not be the best example of a pull request to consider, as I am working through a minor learning curve with rspec 3 idoms.  However, the general issue arises when, say, Joe posts something to dlss-developers about a certain way that he professes things should be done or not done.)  So, let's discuss in our next standup and Naomi and I will work out the details for this code.

Coverage increased (+14.55%) to 93.87% when pulling ad5287c44696d9f17244ef2a8decbd71102487f2 on feature/enhance_specs into 66b9faad1482329557c0aa7a965e6097b3304b63 on develop.

Coverage increased (+14.55%) to 93.87% when pulling ad5287c44696d9f17244ef2a8decbd71102487f2 on feature/enhance_specs into 66b9faad1482329557c0aa7a965e6097b3304b63 on develop.

Coverage increased (+14.55%) to 93.87% when pulling ad5287c44696d9f17244ef2a8decbd71102487f2 on feature/enhance_specs into 66b9faad1482329557c0aa7a965e6097b3304b63 on develop.

Coverage increased (+14.68%) to 94.01% when pulling 358108e4134dbc397f4dcd18c31fe61c91e1f001 on feature/enhance_specs into 66b9faad1482329557c0aa7a965e6097b3304b63 on develop.

Coverage increased (+14.9%) to 94.22% when pulling deadcdc01edd69e414f805b690cdc79ecdffd024 on feature/enhance_specs into 66b9faad1482329557c0aa7a965e6097b3304b63 on develop.

Coverage increased (+14.9%) to 94.22% when pulling deadcdc01edd69e414f805b690cdc79ecdffd024 on feature/enhance_specs into 66b9faad1482329557c0aa7a965e6097b3304b63 on develop.

Coverage increased (+14.99%) to 94.31% when pulling c003387321dcd6b357dc1905157badbcfdc3592b on feature/enhance_specs into 66b9faad1482329557c0aa7a965e6097b3304b63 on develop.

Coverage increased (+15.15%) to 94.48% when pulling 16c8c2ca61cdc8a32d855debf57d385b843c6672 on feature/enhance_specs into 66b9faad1482329557c0aa7a965e6097b3304b63 on develop.

Coverage increased (+15.15%) to 94.48% when pulling 16c8c2ca61cdc8a32d855debf57d385b843c6672 on feature/enhance_specs into 66b9faad1482329557c0aa7a965e6097b3304b63 on develop.

So this looks pretty good.  Seems like you're getting the hang of rspec - yay!
It looks like you check for how the client handles errors from triannon server in the context of delete_annotation but not in the context of any of the other methods?   Or maybe you can just show that each verb method calls the error handling methods?
Note that none of us writes perfect tests, nor perfect code -- if you or someone else were giving my test code this much scrutiny, I'm sure there would be many things I could improve.    I'm only being this detailed because you initially expressed some unfamiliarity with rspec.
In general, pull request review across projects probably shouldn't get so picky-uny.

:)

connected to #1

Coverage decreased (-34.32%) to 45.0% when pulling 3e3b30c55e1b917fe6d5d67be441c8043085213b on feature/enhance_specs into 66b9faad1482329557c0aa7a965e6097b3304b63 on develop.

Coverage decreased (-34.32%) to 45.0% when pulling 3e3b30c55e1b917fe6d5d67be441c8043085213b on feature/enhance_specs into 66b9faad1482329557c0aa7a965e6097b3304b63 on develop.

Coverage decreased (-34.32%) to 45.0% when pulling 3e3b30c55e1b917fe6d5d67be441c8043085213b on feature/enhance_specs into 66b9faad1482329557c0aa7a965e6097b3304b63 on develop.

Coverage increased (+16.49%) to 95.81% when pulling 0c9cbfe3e1ce8ad68e5a020a850988203d8a13f5 on feature/enhance_specs into 66b9faad1482329557c0aa7a965e6097b3304b63 on develop.

Working on reviewing details for this pull request and reviewing information on how to use git-flow with github pull requests, e.g. http://datasift.github.io/gitflow/

Coverage increased (+16.63%) to 95.96% when pulling 1efd5981bb52de1f988761b29df6956249b26b9f on feature/enhance_specs into 66b9faad1482329557c0aa7a965e6097b3304b63 on develop.

Coverage increased (+16.63%) to 95.96% when pulling 1efd5981bb52de1f988761b29df6956249b26b9f on feature/enhance_specs into 66b9faad1482329557c0aa7a965e6097b3304b63 on develop.

@ndushay - shall we merge this?  Maybe this one is getting out of hand and could be broken into smaller items now?

ja, sure - I wasn't sure if you were still working on it.  You can hit the green button this time if you like, or tell me you're ready?

I'll let you hit the big green button to merge this ...

travis is having troubles - the latest commits failed in the 'push' but passed in the 'pr', i.e. https://travis-ci.org/sul-dlss/triannon-client/builds/60465059 (I have no idea exactly why there is a distinction between the 'push' and the 'pr' in travis).

Merging this PR now, as it has served it's purpose to facilitate working with proper rspec idioms and rspec mocks to enhance the client specs.  Additional features will be added to new feature branches (e.g. additional code and specs for the /search path).

Coverage increased (+16.76%) to 96.08% when pulling ad684fa4bf1a046b9baae54ac752b20debe062a1 on feature/enhance_specs into 66b9faad1482329557c0aa7a965e6097b3304b63 on develop.


nginx: fix formating the config file

Motivation for this change
Fix this PR #56280
cc @etu
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

[ ] 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"
[x] 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)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg test nginx

Thanks!

Also format your commit message according to the Contribution Guidelines, also linked to from the PR template in the future


Small error in AssetDatabaseTab when using with Unity 2021.3

Hi @DonnYep
In AssetDatabaseTab.cs line 330, I think we have small error here:

Please check
Thank you!

@codingwatching Thank you for your feedback, this error I have fixed and uploaded.


Implement Access support

Minimal support:

Unix chmod and chown

For SourceFile, should probably be able to set Access on the symlink

Keep the desire for parallelism in mind
https://github.com/crate-ci/stager/issues/6


Popup-Window

Add images and modified index.html, main.js and styles.css

How do I do that ...You initially approved the project.
On Thu, Jul 27, 2023 at 3:55 PM Temitope Ogunleye @.***>
wrote:

@evansnyamekye https://github.com/evansnyamekye you still have changes
to make. please revert your merge
—
Reply to this email directly, view it on GitHub
https://github.com/evansnyamekye/Post-index/pull/8#issuecomment-1653899533,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AORFTGMQI7LDMYC6L4GWXXDXSKFN7ANCNFSM6AAAAAA2ZQ2INM
.
You are receiving this because you were mentioned.Message ID:
@.***>


More Order Samples!

Hey!
I just discovered your repo and YouTube video series. Excellent work! I'm looking to use your application to build my strategy using Interactive Brokers.
What I am a bit confused about, is how to create "custom" types of orders. The IB API docs are confusing and don't really highlight what I'm after. (I typed out a request form on their website and hit "Send" where I was then greeted with a "Something went wrong, please try again later" error message eye roll). I'm thinking this might be better served here anyway as I'm hoping we might discover some new order types to add to your examples/samples to help others!
To keep things simple, I'll pseudocode what the order I'm looking to create should look like:
**Buy Stop-Limit Order for 100 shares of AAPL WITH Trailing Stop Loss.**
Stop price (to trigger the buy Limit order) - $25.00
Limit price (once Buy Stop price is triggered) - $30.00
Trailing Stop Loss (once Buy Stop price is triggered) - $20.00
Trailing Stop Amount (to increment every X) - $1.00

I assume one could make some kind of bracket order, just leaving the Take Profit stuff blank as it's not needed in this case? Some potential issues I see with this above order might be:

Is it even possible to trigger a Buy Limit order with Trailing SL order like this?
If it is, if the order only gets a partial fill before exceeding the limit price (say only 56 shares get filled), can the Trailing SL be fitted to sell the entire position, regardless of the share size?

Looking at the sample for limit orders included in this repo's docs, and this webpage, I would envision it should look something like:
[
    // STOP-LIMIT BUY ORDER, ENTER A POSITION.
    {
        "conid": 251962528, # <- or whatever AAPL's conid is
        "secType": "362673777:STK",
        "cOID": "limit-buy-order-1",
        "orderType": "STP LMT",
        "lmtPrice": 30.00,
        "auxPrice": 25.00
        "side": "BUY",
        "quantity": 100,
        "tif": "DAY"
    },
    // TRAILING STOP, EXIT A POSITION.
    {
        "conid": 251962528,
        "secType": "362673777:STK",
        "cOID": "market-sell-order-1",
        "orderType": "TRAIL",
        "trailStopPrice": 20.00,
        "trailingPercent": 0.01, # <- 1%? Is there a way to make this $1.00 as described above?
        "side": "BUY",
        "quantity": 100,  # <- is there a way to make this 100% of position?
        "tif": "DAY"
    }
]

I noticed there might be something to do with defining the transmit attribute too, which is not included above (as I have no clue what I'm doing yet XD)

I just added some more examples of order types in the samples folders. Hopefully, they help you out. :)
As for your order, I think that would work. Your best bet is to try it with the paper account and see if the behavior is what you expect.

Wicked! I think I can work with the added samples! Thanks a lot!


[Doc] 2.10* docs provide incorrect command for namespace set-backlog-quota

Search before asking

[X] I searched in the issues and found nothing similar.

What issue do you find in Pulsar docs?
This reference requests the following command:

pulsar-admin namespaces set-backlog-quota my-tenant/my-ns \
--limitTime 3600 \
--policy producer_request_hold \
--type message_age

That command does not work, and results in this error:
The following option is required: [-l | --limit]
What is your suggestion?

The command should work.
Command examples should be provided that only adjust size-based thresholds.
Command examples should be provided that only adjust time-based thresholds.
Command examples should be provided that adjust both time- and size-based thresholds.

Any reference?
https://pulsar.apache.org/docs/2.10.x/pulsar-admin/#set-backlog-quota
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

cc @labuladong @nodece

Perhaps also place a --limit 2G above?

@tisonkun that would make the command valid, but ideally examples would exist for all three limit cases: just size, just time, and both.

but ideally examples would exist for all three limit cases: just size, just time, and both.

I agree. I think this is a bug in the admin interface, I'll create a pr to fix it.


httpx: 1.6.0 -> 1.6.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/projectdiscovery/httpx/releases.
meta.description for httpx is: Fast and multi-purpose HTTP toolkit
meta.homepage for httpx is: https://github.com/projectdiscovery/httpx
meta.changelog for httpx is: https://github.com/projectdiscovery/httpx/releases/tag/v1.6.1
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.6.1 with grep in /nix/store/z8fizfiq00yp5ihwv5pz7aq8p2ya82wq-httpx-1.6.1
found 1.6.1 in filename of file in /nix/store/z8fizfiq00yp5ihwv5pz7aq8p2ya82wq-httpx-1.6.1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

httpx

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/z8fizfiq00yp5ihwv5pz7aq8p2ya82wq-httpx-1.6.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A httpx https://github.com/r-ryantm/nixpkgs/archive/42077426dadc785db85b2053978ecc33044bd68e.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/42077426dadc785db85b2053978ecc33044bd68e#httpx

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/z8fizfiq00yp5ihwv5pz7aq8p2ya82wq-httpx-1.6.1
ls -la /nix/store/z8fizfiq00yp5ihwv5pz7aq8p2ya82wq-httpx-1.6.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

httpx

Maintainer pings
cc @fabaff for testing.

Result of nixpkgs-review pr 313027 run on x86_64-linux 1

1 package built:

httpx


Add misc/timeit and misc/set* to README (and remove a debug print from test suite)

Sorry -- forgot to update README on my original PR.

thanks!
mike
On Mon, Jan 11, 2021 at 12:13 PM Josef Pospíšil<EMAIL_ADDRESS>wrote:

@pepe approved this pull request.
LGTM
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/janet-lang/spork/pull/13#pullrequestreview-565569188,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAM7HKRG6SFDNOCXZHBKN6TSZMWVLANCNFSM4V5ZOU3Q
.

thanks!
mike
On Mon, Jan 11, 2021 at 12:13 PM Josef Pospíšil<EMAIL_ADDRESS>wrote:

@pepe approved this pull request.
LGTM
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/janet-lang/spork/pull/13#pullrequestreview-565569188,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAM7HKRG6SFDNOCXZHBKN6TSZMWVLANCNFSM4V5ZOU3Q
.


[FLINK-15791][kubernetes] Use explicit I/O Executor for asynchronous operations in Fabric8FlinkKubeClient

What is the purpose of the change
We should not use the ForkJoinPool#commonPool() in order to run asynchronous operations in the Fabric8FlinkKubeClient as it is done here. Since we don't know which other component is using this pool, it can be quite dangerous to use it as there might be congestion.
Instead, I propose to provide an explicit I/O Executor which is used for running asynchronous operations.
This PR is based on #10970.
Brief change log

Use explicit I/O Executor for asynchronous operations in Fabric8FlinkKubeClient

Verifying this change

All the tests should work well
Manually starting a Flink cluster on K8s

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

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

Documentation

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

Hi @tillrohrmann. Thanks for your comments.
I have added an internal class Fabric8FlinkKubeClient#ExecutorWrapper. Its responsibility is to get the executor to run asynchronous operations on. It could create a dedicated thread pool or reuse an existing one.
However, i am not sure it is really what you mean to. Please take a look at your convenience.

This PR needs to rebase on the new decorator #11233 after it is merged.

@tillrohrmann @TisonKun
Thanks a lot for your suggestion. Since the #11233(Refactor the Kubernetes decorator design) has remove the action watcher. I will close this PR and moving the explicit I/O Executor to FLINK-15790(Make FlinkKubeClient and its implementations asynchronous).


Example of usage of fd2html within a page (or within a hfun)

With prerender=true and julia-repl it looks like the character escaping is going bananas as kindly pointed out by @shashi

Note that this is not julia-repl code block though, it's actually ```julia inside a docstring, that I included into Franklin by doing Markdown.html(docstring). So I'm not sure if julia-repl is affected.

ohhhhhhh that explains it. So Markdown.html is a bit dumb; you could try using Franklin.fd2html(markdown_string) instead as it's more careful with how it treats code blocks.
I need to try this as well to see what's going on.

Amazing just what I was looking for! Can I use franklin macros inside my docstrings then??? :heart_eyes:

hmm ok so yes but this is a bit unchartered territory so you might encounter issues (hopefully not too many). Basically the key is that fd2html itself has its own scope by default, this might interfere with the scope of whatever page you're on. You can disable that by doing fd2html(string, internal=true), this then uses the current scope and so will have access to everything that's available on that page.
Btw if you do not do internal=true calling fd2html within a page can be dangerous because it can wipe out the current scope. This is part of a broader issue that I need to look into of making sure that scopes are preserved but it requires some thinking.

Alright! Thanks for explaining that!! Yeah doesn't sound like fun. I'm okay with forcing codeblocks in docstrings to be 100% self contained.

Ok no sorry in your case the safe path is to use the internal flag if you intend to use fd2html within your page process.

I found this function is not very practical though . This seems to make serve() hangs forever and stop responding to ctrl c. Also changing doc string some times requires restart Julia to see the changes.

^ no fd2html is instantaneous (<50ms), but you have to be a bit careful with where the code  is executed... this is why these features are not advertised widely at this point. You can always open an issue with reproducing code for discussion.

I understand that. But when there is sophisticated plotting Code in the docstring, the process seems never finish.
There is another drawback which is to get output you need to put \output in docstring. That is perhaps not desirable.
I would recommend to leave example code in the docstring unevaluated if you use Franklin. Otherwise it is perhaps better to use Documenter.jl.

Yeah I mean Franklin was not designed to be a competitor to Documenter. It can actually do stuff (as per the SymbolicUtils folks) but it's not magic.
That being said, you could make this hfun_docstring as sophisticated as you want and essentially reproduce the whole of Documenter (hell you could even call Documenter functions from within Franklin), all this is possible but it will require a fair bit of effort as it's not something Franklin is explicitly supporting at this point.


Newtonsoft.Json 12.0.0 from dotnet-script always imported even when 13.0.1 package installed

This simple script:
#r "nuget: Newtonsoft.Json, 13.0.1"

Console.WriteLine(typeof(Newtonsoft.Json.JsonConvert).Assembly);
Console.WriteLine(typeof(Newtonsoft.Json.JsonConvert).Assembly.Location);

Prints:
Newtonsoft.Json, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed
C:\Users\georgiosd\.dotnet\tools\.store\dotnet-script\1.3.1\dotnet-script\1.3.1\tools\net6.0\any\Newtonsoft.Json.dll

😱

This is "expected". The few of own dependencies of dotnet-script are loaded into the same default assembly load context as the script. Since they are first, they win over the script ones.
You can suppress this behavior by adding the flag --isolated-load-context when running the script.

@filipw perhaps it would be prudent to issue a warning for this if there is a version mismatch, for the uninitiated souls?

how can i set option --isolated-load-context in vscode launch.json?

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": ".NET Script Debug",
      "type": "coreclr",
      "request": "launch",
      "program": "${env:HOME}/.dotnet/tools/dotnet-script",
      "args": [
        "${file}",
        "--isolated-load-context"
      ],
      "windows": {
        "program": "${env:USERPROFILE}/.dotnet/tools/dotnet-script.exe",
      },
      "cwd": "${workspaceFolder}",
      "stopAtEntry": false,
    }
  ]
}


performance degradation (time) of insert / upsert in batch operation

My Environment

ArangoDB Version:        3.6.5
Storage Engine:             RocksDB
Deployment Mode:       Cluster
Deployment Strategy:   Kubernetes
Configuration:

apiVersion: "database.arangodb.com/v1alpha"
kind: "ArangoDeployment"
metadata:
  name: "cluster"
spec:
  externalAccess:
    type: NodePort
  auth:
    jwtSecretName: None
  tls:
    caSecretName: None
  mode: Cluster
  image: arangodb/arangodb:3.6.5
  dbservers:
    count: 3
    args: ["--rocksdb.write-buffer-size=1024MB", "--rocksdb.max-write-buffer-number=6"]
    overrideDetectedTotalMemory: true
  coordinators:
    count: 3
    overrideDetectedTotalMemory: true

Infrastructure:               Azure
Total RAM in your machine:        16GB for each node (3 worker nodes)
Disks in use:        SSD 8GB PVC for each pod
Used Package:             Docker - official Docker library | other

Component, Query & Data
Affected feature:
AQL INSERT/UPSERT IN BATCH OPERATION (STRESS)
Replication Factor & Number of Shards (Cluster only):
3 & 3
Steps to reproduce
// bomb-arangodb jar
...
queries.forEach(query -> {
    arangoDatabase.query(query, String.class);
});
arangoDB.shutdown();
...

apiVersion: apps/v1
kind: Deployment
metadata:
  name: bomb-arangodb-write-deployment
  labels:
    app: bomb-arangodb-write-deployment
spec:
  replicas: 20
  selector:
    matchLabels:
      app: bomb-arangodb-write
  template:
    metadata:
      labels:
        app: bomb-arangodb-write
    spec:
      containers:
        - name: bomb-arangodb-write-container
          image: <<ACR_NAME>> .azurecr.io/bomb-arangodb:0.0.3
          imagePullPolicy: Always
          ports:
            - containerPort: 8080
          command: ["/bin/bash"]
          args: ["-c", "java -cp bomb-arangodb.jar com.effe.WriteApp 25000 cluster-ea.arango.svc.cluster.local"]

Problem:
I start 20 pods (as posted in the deployment above, then 25000 writes per head = tot: 500000) that write ["insert" or "upsert"] (both tested) and as time passes I see a degradation of the times of every single write (moreover, sometimes some dbserver or coordinator node falls). I don't really know how to fix this. I also increased the size of the write buffer assuming a possible problem but nothing always the same story.
times go from 20 milliseconds to 300 400 dopo circa 100k-200k writes - up to 1000 milliseconds when it reaches 400k writes and so on
Please, point me in the right way. thank you
Expected result:

No time degradation
No fall of the nodes

So assuming the compaction kicks in the performance may decrease until the level0 is free again. Did you provide the code of your stress test? Are you using indexes? These may increase insert times when doing updates
Have you ever tried increasing the level0 values:
--rocksdb.level0-slowdown-trigger 30 --rocksdb.level0-stop-trigger 50
Perhaps increasing the target size would also help: --rocksdb.target-file-size-base 256MiB
https://www.arangodb.com/docs/stable/data-modeling-operational-factors.html

Perhaps you could provide us at witht the code of your stress test

@effesessa Did you have a chance to try out graetzer's suggestions?

Looks like the suggested configuration changed solved #12190, therefore I'm also closing this issue.


Error installationId may not be changed in this operation on 2.2.22 when update installation object

Describe your issue in as much detail as possible.
After updating to Parse-Server 2.2.22, my previously working code on 2.2.21 that just to update the user pointer on an installation object is not working anymore. Got following error:
error: Error generating response. ParseError {
  code: 136,
  message: 'installationId may not be changed in this operation' } code=136, message=installationId may not be changed in this operation
error: Failed running cloud function addUserToInstallation for user FA9IMj9eDx with:
  Input: {"installationId":"4bb1e0ac-1224-4d99-ae7b-619778834e5f","userId":"FA9IMj9eDx"}

  Error: {"code":141,"message":{"code":136,"message":"installationId may not be changed in this operation"}} functionName=addUserToInstallation, code=141, code=136, message=installationId may not be changed in this operation, installationId=4bb1e0ac-1224-4d99-ae7b-619778834e5f, userId=FA9IMj9eDx, user=FA9IMj9eDx

Steps to reproduce
Please include a detailed list of steps that reproduce the issue. Include curl commands when applicable.

 ParseError {
  code: 141,
  message:
   ParseError {
     code: 136,
     message: 'installationId may not be changed in this operation' } } code=141, code=136, message=installationId may not be changed in this operation

Environment Setup

Server

parse-server version (Be specific! Don't say 'latest'.) : [2.2.22]
Operating System:     [ubuntu/trusty64]
Hardware:             [FILL THIS OUT]
Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): [vagrant 1.8.5]

Database

MongoDB version: [MongoDB 3.2.8]
Storage engine:  [mmapv1 ]
Hardware:        [1GB Disk]
Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc): [compose.io]

Logs/Trace
You can turn on additional logging by configuring VERBOSE=1 in your environment.
[Not Necessary]

Thanks for reporting the issue, I'll do my best to provide a fix ASAP.

Same case here.

Ditto

+1

@flovilmart Thank your for the pr.
Do you have any ETA to 2.2.23?
In my use case, I use to save the User pointer in this object to send push notification. (same case of @yingliangzhang)
Now, none of my recent installations is receiving push because of this,

In the meantime you should downgrade to the latest stable version for you

@flovilmart I've already done. ;)


Updated UserGuide.adoc for Undo/Redo commands

Pull Request Test Coverage Report for Build 183

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 82.707%

Totals

Change from base Build 182:
0.0%

Covered Lines:
2353

Relevant Lines:
2845

💛  - Coveralls


improve 'name' data property

At the moment names of events, series, organizations and people are all lumped together under the aeon:'name' data property. This needs to be cleaned up.
We need to have a way of describing that

an event or event series

must have an official name, which may be in multiple languages
often has an acronym
can have one or more alternative names
sometimes can have a former name (e.g. when two series merged into one)

names of organizations an people should not be defined in AEON. But we need to reuse them in order to properly describe the contributors (organizer, maintainer, speaker etc). Just having a PID would fall short of the fact that there are contributors who do not yet have a PID

What there is at the moment is iao:identifier and iao:written name. We cannot use the latter in AEON to refer to the official name of an event or series, as its definition as a iao:textual entity entails being "a part of a manifestation (FRBR sense)". What we need however is the name of an event or series that is written down in databases. In other words we need the thing that signifies the event/series "proper name" (is_a iao:identifier). Therefore it seems better to define the thing we use to refer to the official name of an event or series as a symbol, similar to iao:'centrally registered identifier symbol'.

The current design decision is to have the class aeon:'planned process name' as a subclass of iao:identifier similar to pno:'personal name' with the restriction that it is equivalent to identifier and (denotes only 'planned process').
This way we are able to have instances of academic event or series names with which we can express the fact that events and series are sometimes called differently on different plattforms.
The data property aeon:'planned process acronym', defined as a subproperty of iao:'has representation' restricted to the domain of planned processes and the range of xsd:string, can be used to provide the acronym of an academic event or series. As can be seen from the example individuals for the VIVO 2020 conference and its series, preferred and alternative names can be provided using skos:prefLabel and skos:altLabel. For translated event or series names it seems best to use skos:altLabel with the respective language tag.


Stop forcing Linux 4.4 on qemux86-64

The mentioned issue doesn't seem to exist anymore

Precision: I ran oe-selftest -r updaterand only had failures on the rpi tests (should probably check those anyway).

I ran oe-selftest -r updaterand only had failures on the rpi tests

What were the errors? It's possible that the test is not robust, but it's also possible that the linux-4.4 issue was because of rpi in the first place.

I'll relaunch a test but since the change is in sota_qemux86-64.bbclass, it shouldn't have an influence.
Here is the commit that introduces the version freeze: https://github.com/advancedtelematic/meta-updater/commit/a42822fe5d4351a64c4a589756f7b72c81b8f2ef

Everything passed this time

Glad to hear it. Have you tested with an rpi? It worked for me as well with qemu, but I'd like to make sure that someone has tested booting an rpi with this.

@patrickvacek you really think it's necessary, even though the only change is in sota_qemux86-64.bbclass? We're compiling 4.9.xx kernels from meta-raspberrypi, just like before.