text:
Code Inspection: npm audit on scatter

graphql-code-generator:>=0

(error) Insecure Default Configuration No fix is currently available. Consider using an alternative module until a fix is made available.

graphql-code-generator:0.16.1:

@atomist/automation-client>graphql-code-generator

handlebars:<=4.0.13 || >=4.1.0 <4.1.2

(error) Prototype Pollution For handlebars 4.1.x upgrade to 4.1.2 or later.
For handlebars 4.0.x upgrade to 4.0.14 or later.

handlebars:4.0.12:

typedoc>handlebars

js-yaml:<3.13.0

(warn) Denial of Service Upgrade to version 3.13.0.

js-yaml:3.12.0:

@atomist/automation-client>graphql-code-generator>graphql-config>js-yaml
@atomist/sdm-core>@kubernetes/client-node>js-yaml
@atomist/uhura>@kubernetes/client-node>js-yaml
tslint>js-yaml

js-yaml:3.12.1:

@atomist/automation-client>graphql-code-generator>js-yaml

js-yaml:<3.13.1

(error) Code Injection Upgrade to version 3.13.1.

js-yaml:3.12.0:

@atomist/automation-client>graphql-code-generator>graphql-config>js-yaml
@atomist/sdm-core>@kubernetes/client-node>js-yaml
@atomist/uhura>@kubernetes/client-node>js-yaml
tslint>js-yaml

js-yaml:3.12.1:

@atomist/automation-client>graphql-code-generator>js-yaml

marked:>=0.3.14 <0.6.2

(warn) Regular Expression Denial of Service Upgrade to version 0.6.2 or later.

marked:0.4.0:

typedoc>marked

static-eval:<=2.0.1

(warn) Sandbox Breakout / Arbitrary Code Execution Upgrade to version 2.0.2 or later.

static-eval:2.0.0:

@atomist/sdm-core>@kubernetes/client-node>jsonpath>static-eval
@atomist/uhura>@kubernetes/client-node>jsonpath>static-eval

[atomist:code-inspection:scatter=@atomist/atomist-sdm]

Issue closed because branch scatter was deleted.

Issue closed because branch scatter was deleted.

authors: cdupuis dansmithy

repo: atomist-blogs/org-visualizer


text:
Lost of atoti extension

Steps to reproduce
Not sure what triggered but occasionally I lose the extension and had no choice but to refresh the page for the extension to come back.

Environment

atoti: 0.5.1
Operating System: win32

Hi Hui Fang,

Do you have any errors in the browser console?
What's your output for jupyter labextension list?
Can you please list the packages installed in your virtual env?

Hi Hui Fang,

Do you have any errors in the browser console?
What's your output for jupyter labextension list?
Can you please list the packages installed in your virtual env?

Hi Thibault,
I didn't manage to check the first point. Will note them when it reoccurs.

jupyter labextension list:

JupyterLab v3.0.0
C:\Apps\miniconda3\envs\atoti_51\share\jupyter\labextensions
        atoti-jupyterlab v0.5.1 enabled ok
        @jupyter-widgets/jupyterlab-manager v3.0.0 enabled ok (python, jupyterlab_widgets)

Virtual env package list:

(atoti_51) C:\Users\Yeo Hui Fang>conda list
# packages in environment at C:\Apps\miniconda3\envs\atoti_51:
#
# Name                    Version                   Build  Channel
abseil-cpp                20200923.2           h0e60522_1    conda-forge
anyio                     2.0.2            py39hcbf5309_4    conda-forge
argon2-cffi               20.1.0           py39hb82d6ee_2    conda-forge
arrow-cpp                 2.0.0           py39h59ff000_16_cpu    conda-forge
async_generator           1.10                       py_0    conda-forge
atoti                     0.5.1                   7f32d5e    https://conda.atoti.io
atoti-aws                 0.5.1                   7f32d5e    https://conda.atoti.io
atoti-jupyterlab          0.5.1                   7f32d5e    https://conda.atoti.io
attrs                     20.3.0             pyhd3deb0d_0    conda-forge
aws-c-cal                 0.4.5                hd67dfff_4    conda-forge
aws-c-common              0.4.65               h8ffe710_0    conda-forge
aws-c-event-stream        0.2.6                hc969853_1    conda-forge
aws-c-io                  0.8.0                h9f364c9_0    conda-forge
aws-checksums             0.1.10               h9f364c9_2    conda-forge
aws-sdk-cpp               1.8.122              h0223788_0    conda-forge
babel                     2.9.0              pyhd3deb0d_0    conda-forge
backcall                  0.2.0              pyh9f0ad1d_0    conda-forge
backports                 1.0                        py_2    conda-forge
backports.functools_lru_cache 1.6.1                      py_0    conda-forge
bleach                    3.2.1              pyh9f0ad1d_0    conda-forge
brotli                    1.0.9                h0e60522_4    conda-forge
brotlipy                  0.7.0           py39hb82d6ee_1001    conda-forge
bzip2                     1.0.8                h8ffe710_4    conda-forge
c-ares                    1.17.1               h8ffe710_0    conda-forge
ca-certificates           2020.12.5            h5b45459_0    conda-forge
certifi                   2020.12.5        py39hcbf5309_1    conda-forge
cffi                      1.14.4           py39h0878f49_1    conda-forge
chardet                   4.0.0            py39hcbf5309_1    conda-forge
colorama                  0.4.4              pyh9f0ad1d_0    conda-forge
confuse                   1.4.0                    pypi_0    pypi
cryptography              3.3.1            py39h0878f49_1    conda-forge
cycler                    0.10.0                   pypi_0    pypi
decorator                 4.4.2                      py_0    conda-forge
defusedxml                0.6.0                      py_0    conda-forge
entrypoints               0.3             pyhd8ed1ab_1003    conda-forge
gflags                    2.2.2             ha925a31_1004    conda-forge
glog                      0.4.0                h0174b99_3    conda-forge
graphviz                  2.38.0            h6538335_1011    conda-forge
grpc-cpp                  1.34.1               hd7e1925_0    conda-forge
htmlmin                   0.1.12                   pypi_0    pypi
idna                      2.10               pyh9f0ad1d_0    conda-forge
imagehash                 4.2.0                    pypi_0    pypi
imbalanced-learn          0.7.0                    pypi_0    pypi
imblearn                  0.0                      pypi_0    pypi
importlib-metadata        3.4.0            py39hcbf5309_0    conda-forge
importlib_metadata        3.4.0                hd8ed1ab_0    conda-forge
intel-openmp              2020.3             h57928b3_311    conda-forge
ipykernel                 5.4.2            py39he1a07ef_0    conda-forge
ipython                   7.19.0           py39h832f523_0    conda-forge
ipython_genutils          0.2.0                      py_1    conda-forge
ipywidgets                7.6.3                    pypi_0    pypi
jdk4py                    11.0.9.0                 py39_0    https://conda.atoti.io
jedi                      0.18.0           py39hcbf5309_2    conda-forge
jinja2                    2.11.2             pyh9f0ad1d_0    conda-forge
joblib                    1.0.0                    pypi_0    pypi
json5                     0.9.5              pyh9f0ad1d_0    conda-forge
jsonschema                3.2.0                      py_2    conda-forge
jupyter_client            6.1.11             pyhd8ed1ab_1    conda-forge
jupyter_core              4.7.0            py39hcbf5309_0    conda-forge
jupyter_server            1.2.1            py39hcbf5309_0    conda-forge
jupyterlab                3.0.0              pyh5fc60ef_0    conda-forge/label/jupyterlab_rc
jupyterlab-widgets        1.0.0                    pypi_0    pypi
jupyterlab_pygments       0.1.2              pyh9f0ad1d_0    conda-forge
jupyterlab_server         2.0.0              pyh70d38ba_0    conda-forge/label/jupyterlab_server_rc
kiwisolver                1.3.1                    pypi_0    pypi
krb5                      1.17.2               hbae68bd_0    conda-forge
libblas                   3.9.0                     7_mkl    conda-forge
libcblas                  3.9.0                     7_mkl    conda-forge
libcurl                   7.71.1               h4b64cdc_8    conda-forge
liblapack                 3.9.0                     7_mkl    conda-forge
libprotobuf               3.14.0               h7755175_0    conda-forge
libsodium                 1.0.18               h8d14728_1    conda-forge
libssh2                   1.9.0                hb06d900_5    conda-forge
libthrift                 0.13.0               hdfef310_6    conda-forge
libutf8proc               2.6.1                hcb41399_0    conda-forge
llvmlite                  0.35.0                   pypi_0    pypi
lz4-c                     1.9.3                h8ffe710_0    conda-forge
m2w64-gcc-libgfortran     5.3.0                         6    conda-forge
m2w64-gcc-libs            5.3.0                         7    conda-forge
m2w64-gcc-libs-core       5.3.0                         7    conda-forge
m2w64-gmp                 6.1.0                         2    conda-forge
m2w64-libwinpthread-git   5.0.0.4634.697f757               2    conda-forge
markupsafe                1.1.1            py39hb82d6ee_3    conda-forge
matplotlib                3.3.3                    pypi_0    pypi
missingno                 0.4.2                    pypi_0    pypi
mistune                   0.8.4           py39hb82d6ee_1003    conda-forge
mkl                       2020.4             hb70f87d_311    conda-forge
msys2-conda-epoch         20160418                      1    conda-forge
nbclassic                 0.2.6              pyhd8ed1ab_0    conda-forge
nbclient                  0.5.1                      py_0    conda-forge
nbconvert                 6.0.7            py39hcbf5309_3    conda-forge
nbformat                  5.0.8                      py_0    conda-forge
nest-asyncio              1.4.3              pyhd8ed1ab_0    conda-forge
networkx                  2.5                      pypi_0    pypi
notebook                  6.2.0            py39hcbf5309_0    conda-forge
numba                     0.53.0dev0      np1.16py3.9h5685391_gddc6d35c2_465    numba/label/dev
numpy                     1.19.5           py39h6635163_1    conda-forge
openssl                   1.1.1i               h8ffe710_0    conda-forge
packaging                 20.8               pyhd3deb0d_0    conda-forge
pandas                    1.2.0            py39h2e25243_0    conda-forge
pandas-profiling          2.10.0                   pypi_0    pypi
pandoc                    2.11.3.2             h8ffe710_0    conda-forge
pandocfilters             1.4.2                      py_1    conda-forge
parquet-cpp               1.5.1                         2    conda-forge
parso                     0.8.1              pyhd8ed1ab_0    conda-forge
phik                      0.11.0                   pypi_0    pypi
pickleshare               0.7.5                   py_1003    conda-forge
pillow                    8.1.0                    pypi_0    pypi
pip                       20.3.3             pyhd8ed1ab_0    conda-forge
prometheus_client         0.9.0              pyhd3deb0d_0    conda-forge
prompt-toolkit            3.0.10             pyha770c72_0    conda-forge
pyarrow                   2.0.0           py39hf9247be_16_cpu    conda-forge
pycparser                 2.20               pyh9f0ad1d_2    conda-forge
pygments                  2.7.3              pyhd8ed1ab_0    conda-forge
pyopenssl                 20.0.1             pyhd8ed1ab_0    conda-forge
pyparsing                 2.4.7              pyh9f0ad1d_0    conda-forge
pyrsistent                0.17.3           py39hb82d6ee_2    conda-forge
pysocks                   1.7.1            py39hcbf5309_3    conda-forge
python                    3.9.1           h7840368_3_cpython    conda-forge
python-dateutil           2.8.1                      py_0    conda-forge
python_abi                3.9                      1_cp39    conda-forge
pytz                      2020.5             pyhd8ed1ab_0    conda-forge
pywavelets                1.1.1                    pypi_0    pypi
pywin32                   228              py39hb82d6ee_1    conda-forge
pywinpty                  0.5.7            py39hde42818_1    conda-forge
pyyaml                    5.3.1            py39hb82d6ee_2    conda-forge
pyzmq                     20.0.0           py39h6e08c89_1    conda-forge
re2                       2020.11.01           h0e60522_0    conda-forge
requests                  2.25.1             pyhd3deb0d_0    conda-forge
scikit-learn              0.24.0                   pypi_0    pypi
scipy                     1.6.0                    pypi_0    pypi
seaborn                   0.11.1                   pypi_0    pypi
send2trash                1.5.0                      py_0    conda-forge
setuptools                49.6.0           py39hcbf5309_3    conda-forge
six                       1.15.0             pyh9f0ad1d_0    conda-forge
sklearn                   0.0                      pypi_0    pypi
snappy                    1.1.8                ha925a31_3    conda-forge
sniffio                   1.2.0            py39hcbf5309_1    conda-forge
sqlite                    3.34.0               h8ffe710_0    conda-forge
tangled-up-in-unicode     0.0.6                    pypi_0    pypi
terminado                 0.9.2            py39hcbf5309_0    conda-forge
testpath                  0.4.4                      py_0    conda-forge
threadpoolctl             2.1.0                    pypi_0    pypi
tk                        8.6.10               h8ffe710_1    conda-forge
tornado                   6.1              py39hb82d6ee_1    conda-forge
tqdm                      4.56.0                   pypi_0    pypi
traitlets                 5.0.5                      py_0    conda-forge
typeguard                 2.9.1                      py_0    conda-forge
typing_extensions         3.7.4.3                    py_0    conda-forge
tzdata                    2020f                he74cb21_0    conda-forge
urllib3                   1.26.2             pyhd8ed1ab_0    conda-forge
vc                        14.2                 hb210afc_2    conda-forge
visions                   0.6.0                    pypi_0    pypi
vs2015_runtime            14.28.29325          h5e1d092_0    conda-forge
wcwidth                   0.2.5              pyh9f0ad1d_2    conda-forge
webencodings              0.5.1                      py_1    conda-forge
wheel                     0.36.2             pyhd3deb0d_0    conda-forge
widgetsnbextension        3.5.1                    pypi_0    pypi
win_inet_pton             1.1.0            py39hcbf5309_2    conda-forge
wincertstore              0.2             py39hcbf5309_1006    conda-forge
winpty                    0.4.3                         4    conda-forge
xz                        5.2.5                h62dcd97_1    conda-forge
yaml                      0.2.5                he774522_0    conda-forge
zeromq                    4.3.3                h0e60522_3    conda-forge
zipp                      3.4.0                      py_0    conda-forge
zlib                      1.2.11            h62dcd97_1010    conda-forge
zstd                      1.4.8                h4e2f164_1    conda-forge

Hi Thibault,
I didn't manage to check the first point. Will note them when it reoccurs.

jupyter labextension list:

JupyterLab v3.0.0
C:\Apps\miniconda3\envs\atoti_51\share\jupyter\labextensions
        atoti-jupyterlab v0.5.1 enabled ok
        @jupyter-widgets/jupyterlab-manager v3.0.0 enabled ok (python, jupyterlab_widgets)

Virtual env package list:

(atoti_51) C:\Users\Yeo Hui Fang>conda list
# packages in environment at C:\Apps\miniconda3\envs\atoti_51:
#
# Name                    Version                   Build  Channel
abseil-cpp                20200923.2           h0e60522_1    conda-forge
anyio                     2.0.2            py39hcbf5309_4    conda-forge
argon2-cffi               20.1.0           py39hb82d6ee_2    conda-forge
arrow-cpp                 2.0.0           py39h59ff000_16_cpu    conda-forge
async_generator           1.10                       py_0    conda-forge
atoti                     0.5.1                   7f32d5e    https://conda.atoti.io
atoti-aws                 0.5.1                   7f32d5e    https://conda.atoti.io
atoti-jupyterlab          0.5.1                   7f32d5e    https://conda.atoti.io
attrs                     20.3.0             pyhd3deb0d_0    conda-forge
aws-c-cal                 0.4.5                hd67dfff_4    conda-forge
aws-c-common              0.4.65               h8ffe710_0    conda-forge
aws-c-event-stream        0.2.6                hc969853_1    conda-forge
aws-c-io                  0.8.0                h9f364c9_0    conda-forge
aws-checksums             0.1.10               h9f364c9_2    conda-forge
aws-sdk-cpp               1.8.122              h0223788_0    conda-forge
babel                     2.9.0              pyhd3deb0d_0    conda-forge
backcall                  0.2.0              pyh9f0ad1d_0    conda-forge
backports                 1.0                        py_2    conda-forge
backports.functools_lru_cache 1.6.1                      py_0    conda-forge
bleach                    3.2.1              pyh9f0ad1d_0    conda-forge
brotli                    1.0.9                h0e60522_4    conda-forge
brotlipy                  0.7.0           py39hb82d6ee_1001    conda-forge
bzip2                     1.0.8                h8ffe710_4    conda-forge
c-ares                    1.17.1               h8ffe710_0    conda-forge
ca-certificates           2020.12.5            h5b45459_0    conda-forge
certifi                   2020.12.5        py39hcbf5309_1    conda-forge
cffi                      1.14.4           py39h0878f49_1    conda-forge
chardet                   4.0.0            py39hcbf5309_1    conda-forge
colorama                  0.4.4              pyh9f0ad1d_0    conda-forge
confuse                   1.4.0                    pypi_0    pypi
cryptography              3.3.1            py39h0878f49_1    conda-forge
cycler                    0.10.0                   pypi_0    pypi
decorator                 4.4.2                      py_0    conda-forge
defusedxml                0.6.0                      py_0    conda-forge
entrypoints               0.3             pyhd8ed1ab_1003    conda-forge
gflags                    2.2.2             ha925a31_1004    conda-forge
glog                      0.4.0                h0174b99_3    conda-forge
graphviz                  2.38.0            h6538335_1011    conda-forge
grpc-cpp                  1.34.1               hd7e1925_0    conda-forge
htmlmin                   0.1.12                   pypi_0    pypi
idna                      2.10               pyh9f0ad1d_0    conda-forge
imagehash                 4.2.0                    pypi_0    pypi
imbalanced-learn          0.7.0                    pypi_0    pypi
imblearn                  0.0                      pypi_0    pypi
importlib-metadata        3.4.0            py39hcbf5309_0    conda-forge
importlib_metadata        3.4.0                hd8ed1ab_0    conda-forge
intel-openmp              2020.3             h57928b3_311    conda-forge
ipykernel                 5.4.2            py39he1a07ef_0    conda-forge
ipython                   7.19.0           py39h832f523_0    conda-forge
ipython_genutils          0.2.0                      py_1    conda-forge
ipywidgets                7.6.3                    pypi_0    pypi
jdk4py                    11.0.9.0                 py39_0    https://conda.atoti.io
jedi                      0.18.0           py39hcbf5309_2    conda-forge
jinja2                    2.11.2             pyh9f0ad1d_0    conda-forge
joblib                    1.0.0                    pypi_0    pypi
json5                     0.9.5              pyh9f0ad1d_0    conda-forge
jsonschema                3.2.0                      py_2    conda-forge
jupyter_client            6.1.11             pyhd8ed1ab_1    conda-forge
jupyter_core              4.7.0            py39hcbf5309_0    conda-forge
jupyter_server            1.2.1            py39hcbf5309_0    conda-forge
jupyterlab                3.0.0              pyh5fc60ef_0    conda-forge/label/jupyterlab_rc
jupyterlab-widgets        1.0.0                    pypi_0    pypi
jupyterlab_pygments       0.1.2              pyh9f0ad1d_0    conda-forge
jupyterlab_server         2.0.0              pyh70d38ba_0    conda-forge/label/jupyterlab_server_rc
kiwisolver                1.3.1                    pypi_0    pypi
krb5                      1.17.2               hbae68bd_0    conda-forge
libblas                   3.9.0                     7_mkl    conda-forge
libcblas                  3.9.0                     7_mkl    conda-forge
libcurl                   7.71.1               h4b64cdc_8    conda-forge
liblapack                 3.9.0                     7_mkl    conda-forge
libprotobuf               3.14.0               h7755175_0    conda-forge
libsodium                 1.0.18               h8d14728_1    conda-forge
libssh2                   1.9.0                hb06d900_5    conda-forge
libthrift                 0.13.0               hdfef310_6    conda-forge
libutf8proc               2.6.1                hcb41399_0    conda-forge
llvmlite                  0.35.0                   pypi_0    pypi
lz4-c                     1.9.3                h8ffe710_0    conda-forge
m2w64-gcc-libgfortran     5.3.0                         6    conda-forge
m2w64-gcc-libs            5.3.0                         7    conda-forge
m2w64-gcc-libs-core       5.3.0                         7    conda-forge
m2w64-gmp                 6.1.0                         2    conda-forge
m2w64-libwinpthread-git   5.0.0.4634.697f757               2    conda-forge
markupsafe                1.1.1            py39hb82d6ee_3    conda-forge
matplotlib                3.3.3                    pypi_0    pypi
missingno                 0.4.2                    pypi_0    pypi
mistune                   0.8.4           py39hb82d6ee_1003    conda-forge
mkl                       2020.4             hb70f87d_311    conda-forge
msys2-conda-epoch         20160418                      1    conda-forge
nbclassic                 0.2.6              pyhd8ed1ab_0    conda-forge
nbclient                  0.5.1                      py_0    conda-forge
nbconvert                 6.0.7            py39hcbf5309_3    conda-forge
nbformat                  5.0.8                      py_0    conda-forge
nest-asyncio              1.4.3              pyhd8ed1ab_0    conda-forge
networkx                  2.5                      pypi_0    pypi
notebook                  6.2.0            py39hcbf5309_0    conda-forge
numba                     0.53.0dev0      np1.16py3.9h5685391_gddc6d35c2_465    numba/label/dev
numpy                     1.19.5           py39h6635163_1    conda-forge
openssl                   1.1.1i               h8ffe710_0    conda-forge
packaging                 20.8               pyhd3deb0d_0    conda-forge
pandas                    1.2.0            py39h2e25243_0    conda-forge
pandas-profiling          2.10.0                   pypi_0    pypi
pandoc                    2.11.3.2             h8ffe710_0    conda-forge
pandocfilters             1.4.2                      py_1    conda-forge
parquet-cpp               1.5.1                         2    conda-forge
parso                     0.8.1              pyhd8ed1ab_0    conda-forge
phik                      0.11.0                   pypi_0    pypi
pickleshare               0.7.5                   py_1003    conda-forge
pillow                    8.1.0                    pypi_0    pypi
pip                       20.3.3             pyhd8ed1ab_0    conda-forge
prometheus_client         0.9.0              pyhd3deb0d_0    conda-forge
prompt-toolkit            3.0.10             pyha770c72_0    conda-forge
pyarrow                   2.0.0           py39hf9247be_16_cpu    conda-forge
pycparser                 2.20               pyh9f0ad1d_2    conda-forge
pygments                  2.7.3              pyhd8ed1ab_0    conda-forge
pyopenssl                 20.0.1             pyhd8ed1ab_0    conda-forge
pyparsing                 2.4.7              pyh9f0ad1d_0    conda-forge
pyrsistent                0.17.3           py39hb82d6ee_2    conda-forge
pysocks                   1.7.1            py39hcbf5309_3    conda-forge
python                    3.9.1           h7840368_3_cpython    conda-forge
python-dateutil           2.8.1                      py_0    conda-forge
python_abi                3.9                      1_cp39    conda-forge
pytz                      2020.5             pyhd8ed1ab_0    conda-forge
pywavelets                1.1.1                    pypi_0    pypi
pywin32                   228              py39hb82d6ee_1    conda-forge
pywinpty                  0.5.7            py39hde42818_1    conda-forge
pyyaml                    5.3.1            py39hb82d6ee_2    conda-forge
pyzmq                     20.0.0           py39h6e08c89_1    conda-forge
re2                       2020.11.01           h0e60522_0    conda-forge
requests                  2.25.1             pyhd3deb0d_0    conda-forge
scikit-learn              0.24.0                   pypi_0    pypi
scipy                     1.6.0                    pypi_0    pypi
seaborn                   0.11.1                   pypi_0    pypi
send2trash                1.5.0                      py_0    conda-forge
setuptools                49.6.0           py39hcbf5309_3    conda-forge
six                       1.15.0             pyh9f0ad1d_0    conda-forge
sklearn                   0.0                      pypi_0    pypi
snappy                    1.1.8                ha925a31_3    conda-forge
sniffio                   1.2.0            py39hcbf5309_1    conda-forge
sqlite                    3.34.0               h8ffe710_0    conda-forge
tangled-up-in-unicode     0.0.6                    pypi_0    pypi
terminado                 0.9.2            py39hcbf5309_0    conda-forge
testpath                  0.4.4                      py_0    conda-forge
threadpoolctl             2.1.0                    pypi_0    pypi
tk                        8.6.10               h8ffe710_1    conda-forge
tornado                   6.1              py39hb82d6ee_1    conda-forge
tqdm                      4.56.0                   pypi_0    pypi
traitlets                 5.0.5                      py_0    conda-forge
typeguard                 2.9.1                      py_0    conda-forge
typing_extensions         3.7.4.3                    py_0    conda-forge
tzdata                    2020f                he74cb21_0    conda-forge
urllib3                   1.26.2             pyhd8ed1ab_0    conda-forge
vc                        14.2                 hb210afc_2    conda-forge
visions                   0.6.0                    pypi_0    pypi
vs2015_runtime            14.28.29325          h5e1d092_0    conda-forge
wcwidth                   0.2.5              pyh9f0ad1d_2    conda-forge
webencodings              0.5.1                      py_1    conda-forge
wheel                     0.36.2             pyhd3deb0d_0    conda-forge
widgetsnbextension        3.5.1                    pypi_0    pypi
win_inet_pton             1.1.0            py39hcbf5309_2    conda-forge
wincertstore              0.2             py39hcbf5309_1006    conda-forge
winpty                    0.4.3                         4    conda-forge
xz                        5.2.5                h62dcd97_1    conda-forge
yaml                      0.2.5                he774522_0    conda-forge
zeromq                    4.3.3                h0e60522_3    conda-forge
zipp                      3.4.0                      py_0    conda-forge
zlib                      1.2.11            h62dcd97_1010    conda-forge
zstd                      1.4.8                h4e2f164_1    conda-forge

Hi @tibdex,
the console threw a lot of messages:

Hi @tibdex,
the console threw a lot of messages:

It looks like you're facing MDX issues. Did you write the MDX by hand or was it entirely generated from the UI?

It looks like you're facing MDX issues. Did you write the MDX by hand or was it entirely generated from the UI?

Hi @tibdex,
I managed to replicate one scenario where it will be gone. I accidentally selected a chart that is not suitable for my data for instance.

As to your questions, I can't be sure as I need to manipulate the cell meta properties to add in the filters I want.

Hi @tibdex,
I managed to replicate one scenario where it will be gone. I accidentally selected a chart that is not suitable for my data for instance.

As to your questions, I can't be sure as I need to manipulate the cell meta properties to add in the filters I want.

The crash occurring when switching to an incompatible widget type will be fixed in the next release.

The crash occurring when switching to an incompatible widget type will be fixed in the next release.

source: gharchive/issue

authors: HuifangYeo tibdex

repo: atoti/atoti

license_type: permissive

license_source: github-api


text:
Code revisions and added packages subcommand

- What I did

Revised some of the code for maintainability as we prepare to add more samples and templates
Added packages command

add subcommand - abstraction of pub add
list subcommand - lists @platform packages

- How I did it

Local changes

- How to verify it

Pull and try the packages command

- Description for the changelog
Code revisions and added packages subcommand

@XavierChanth approved on the basis that this passes in terms of 'nothing obviously crazy', but without a test suite it's really hard for me to have faith in whether the changes work as intended (and even harder to anticipate side effects).

@XavierChanth approved on the basis that this passes in terms of 'nothing obviously crazy', but without a test suite it's really hard for me to have faith in whether the changes work as intended (and even harder to anticipate side effects).

Agreed, this is something that I would like to setup before the next release.

source: gharchive/pull-request

authors: XavierChanth cpswan


text:
at_server's implementation of OutboundMessageListener is lagging at_lookup's

Describe the bug

at_server has its own implementation of OutboundMessageListener. This contains old code which doesn't include the fixes that have been made in AtLookup which properly handle slow network connections where the full server response might not be received before timeout. While this is unlikely to happen when the communicating secondaries are running in the same GCP region, it is a lot more likely to happen when secondaries are running in places we can't predict.

Expected behaviour

at_secondary_server/lib/src/connection/outbound/outbound_message_listener.dart should be compared with old versions of the same class in at_lookup
Assuming same semantics, at_secondary_server's implementation should be removed and we use at_lookup's improved implementation instead
We should also refactor e2e_test_utils.dart in at_server/at_end2end_test to use the improved code

Moving to backlog but changing to High priority so we don't forget about it


text:
Release binaries for Linux don't specify operating system

Describe the bug
It's kind of obvious that the binaries that aren't OSX must be Linux, but that should be explicit.

Made a note in this release but will change the filenames to be more obvious as they get automated..

authors: cconstab cpswan

repo: atsign-foundation/sshnoports


text:
Harp errors out when "process" button is hit.

I got the latest HARP VST3 plugin downloaded and installed with Reaper.   I tried two different Gradio endpoints. I got the same error message with both endpoints. These endpoints were:
hugggof/pitch_shifter
descript/vampnet
HERE IS AN IMAGE OF THE REPORTED ERROR

HERE IS THE LOG RETURNED BY HARP AFTER VAMPNET ERRORED OUT
vamp_net_HARP.log
HERE IS THE LOG FOR THE PITCH SHIFTER
pitch_shifter_HARP.log

Note: I couldn't select any audio in the waveform so I just hit "process".  Is that the reason? If so, there should be a much more graceful exit. Something like a message saying "Select audio from the waveform before processing"

There's no selection in harp, so there is likely another issue happening here.

maybe related to #59

authors: bryan-pardo hugofloresgarcia

repo: audacitorch/HARP


text:
Очень медленно загружается сайт

Сегодня, особенно во второй половине дня, сайт через раз отдаёт Gateway Timeout, наиболее часто на странице графика. Браузер и устройство принципиального значения не имеют.

Это точно не баг. Я заметил это сейчас вечером примерно около 23:00 по МСК. Днем не загружал сайт, не знаю. После 18:00, сайт работал, я во всяком случае не наблюдал тормозов, а к 23:00 уже заметил. Это что-то у провайдера и это с сетью, канал. Так как во время зависания нельзя было подключиться по ssh к серверу. Сами сервера работают нормально, перегруза нет, тут проблема похоже в каналах связи у провайдера. Буду наблюдать. Не знаю, что можно сделать сейчас в этом случае.

Возможно укроп атакует какие-то соседние центры и нагрузка съела канал.

Возможно укроп атакует какие-то соседние центры и нагрузка съела канал.

Возможно, посмотрим, я как заметил то, по всем машинам проверил нагрузку, ее нет. Наблюдаю.

Написал в тех поддержку, интересно, что скажут.

По времени примерно такой расклад — где-то с 15-16 часов начались перебои, выражаемые в замедлении загрузки страниц, притом любых, не связанных с поиском в базе, но происходило это не постоянно, а обрывочно, через раз или через два. Так продолжалось по-видимому всё время до 22-23 часов, а после этого перебои стали более долгими и постоянными. Смена браузеров, устройств и провайдеров ничего не изменила, то есть это где-то вокруг серверов нашего домена, а не на пользовательской стороне.

Вчера общался с тех. поддержкой. сказали, что на их ЦОД атак нет, подсказали как проверить маршруты, сделал трассировку маршрутов, отправил в тп в общем наблюдались потери на маршруте между серверами в МСК СПБ. В общем помогли разобраться, молодцы.

По предоставленной вами статистики есть потери на 5 хопе при запросах до сервера.
При запросах с сервера потерь нет
Рекомендуется проверить корректность работы с другой интернет сети или же используя впн.

Я на неделе завершу переезд . Сейчас ситуация такая, что сервер принимающий запросы (балансировщик nginx) и распределяющий их по сервисам, и парсеры в СПБ, а БД и Мантикора и сайт в МСК, и между ними ходит трафик. Я не хотел делать полный перенос до праздников, так как если будут проблемы после переезда, чтобы не иметь их в праздники. Теперь завершу работы спокойно. Сейчас, вроде, проблем не наблюдается. Работаем.

Сейчас всё летает.

authors: audetv iprst

repo: audetv/fct-search


text:
Cached VCS branch is used if user doesn't redownload template

Cookiecutter version: 1.6.0
Template project url: Various (tested with pybee/Python-macOS-template)
Python version: Various (tested on Python 3.6)
Operating System: Any (tested on macOS High Sierra)

Description:
If:

You are using a cookiecutter template from a VCS repository; and
The repository uses branches; and
You have previously used the template; and
You choose to re-use the existing version, rather than re-downloading

Cookiecutter ignores the branch you have requested, and re-uses the previously checked out branch.
What I've run:
Briefcase has repositories storing templates that it uses to generate project deployment wrappers. These templates vary for each Python version, and branches are used to store each version; so a given template might have a "2.7" branch, and a "3.4" branch, and a "3.5" branch, and so on.
On first use, we request the Python 2.7 template (using defaults for all template values):
$cookiecutter https://github.com/pybee/Python-macOS-template.git --checkout 2.7
...
$ tail -n 1 macOS/App\ Name.app/Contents/MacOS/App\ Name
python/bin/python -m appname

The last line of the file indicates the Python2 template has been used.
On second use, we request the Python 3.6 template. Since we've used the template before, we're prompted to re-download it. We say yes:
# clean up after the last template first...
$ rm -rf macOS
$ cookiecutter https://github.com/pybee/Python-macOS-template.git --checkout 3.6
You've downloaded /Users/rkm/.cookiecutters/Python-macOS-template before. Is it okay to delete and re-download it? [yes]: yes
...
$ tail -n 1 macOS/App\ Name.app/Contents/MacOS/App\ Name
python/bin/python3 -m appname

This time, we can see from the last line that the Python 3.6 template has been used.
Now, lets switch back to the 2.7 template - but without recloning:
# Clean up...
$ rm -rf macOS/
$ cookiecutter https://github.com/pybee/Python-macOS-template.git --checkout 2.7
You've downloaded /Users/rkm/.cookiecutters/Python-macOS-template before. Is it okay to delete and re-download it? [yes]: no
Do you want to re-use the existing version? [yes]: yes
...
$ tail -n 1 macOS/App\ Name.app/Contents/MacOS/App\ Name
python/bin/python3 -m appname

Even though we specified the 2.7 branch, the 3.6 template branch has been used, because it was the last version that was checked out.
This scenario also successfully clones if you specify a branch that doesn't exist:
$ cookiecutter https://github.com/pybee/Python-macOS-template.git --checkout 2.8

This raises an error if it's a fresh checkout, or if you specify yes to redownload; but if answer no and reuse the existing checkout, it succeeds without error.
The problem appears to occur because the logic in cookiecutter/vcs.py that checks out a requested branch is only executed if the repository is completely re-cloned. In the case where you don't re-clone, the checkout is used as-is, without changing branches.
This is particularly problematic during sprint, travel, or other bandwidth-limited situations. In those situations, it may not be possible to obtain a fresh checkout, but you may still want to use a different branch for your cookiecutter.
It's also a problem if the first request to clone requests a branch that doesn't exist. In that case, Cookiecutter will clone the repository, but be unable to switch to the branch (because it doesn't exist). This raises an error, but the repository remains in the .cookiecutters cache (checked out to an apparently random branch). If, on a subsequent use, you answer no to redownload (after all, you've already downloaded the repository!), you'll get the "random" branch, rather than the one you requested.
This problem was discovered (pybee/briefcase#108) because someone tried to create a Python 3.6 project with Briefcase before a Python 3.6 template had been published. In the absence of a Python 3.6 branch, Cookiecutter cloned the Python 2.7 branch, and used that for the project. This highlighted the need for improved error handling in Briefcase; but even if Briefcase had handled the errors correctly, it would be possible to end up with the wrong template by not redownloading the template after using the template on a different Python version.
Workarounds:

Always specify that the template should be re-downloaded; or
Manually switch branches in the .cookiecutters cache directory.

Thank you for this detailed bug description @freakboy3742! 🙇

repo: audreyr/cookiecutter

license_source: bigquery


text:
resize technique breaks zoom/crop with opentok.js v2.4.0

since the 2.4.0 update, the layout container's resizing of elements improperly impacts the crop/zoom behavior of publishers/subscribers. examples using the demo page in this repo:
1 publisher (doesn't capture full frame and black bar on right):

2 publishers (black bars on bottom):

3 publishers (black bars on bottom - all different):

middle publisher made big (really weird cropping):

sorry about the killer stare face :smile:

This looks like it's not an issue anymore from my testing. I think this was actually a bug in opentok 2.4 which we fixed.

authors: aoberoi aullman

repo: aullman/opentok-layout-js

license: MIT


text:
Add try_stream equivalent

Proposed API:
fn try_stream<F, Ok, Error, Fut>(func: F) -> impl TryStream<Ok = Ok, Error = Error>
where
    F: FnOnce(TryYielder<Ok, Error>) -> Fut,
    Fut: TryFuture<Ok = Ok, Error = Error>;

impl<Ok, Error> TryYielder<Ok, Error> {
    async fn yield_item(&mut self, item: Result<Ok, Error>);
    async fn yield_ok(&mut self, item: Ok);
    async fn yield_error(&mut self, item: Error);
}

Makes it easier to construct fallible streams. I just need to figure out how to not duplicate too much of the internals because I really don't want to keep track of two very similar APIs.

(found this while trying to dog-food the crate in Kitsune)

repo: aumetra/asynk-strim


text:
Set up automatic builds

Can we please run make test and fail the build if the tests fail? Can someone work with me in Discord to get permissions needed to set this up such that we have an automatic build for the project?

Also please update the readme in #5

Should this be set up in CI? Perhaps using Github actions or something?

Highly recommend @goreleaser

Can we enable GHA?  Then should have a docker build based golang builder ;)

I second goreleaser.

We can use GHA and goreleaser. How do we set it up?

I am unavailable until later this weekend (although if no one gets to it I'd be happy to contribute)
But for anyone else, here is a quick link https://goreleaser.com/ci/actions/

I can open a PR for it tonight or later today. I recently set this up at work for an internal tool.
We can add macos binary signing in a separate PR afterwards.

authors: Daegalus devanbenz jasonmcintosh jolheiser krisnova

repo: aurae-runtime/ae


text:
Support for Webpack from Aurelia CLI

The getting started page is not very user-friendly.

We don't go through the painful details of how you should configure your aurelia-cli, webpack or fusebox. The plugin will work with all of them based on the basic configurations that you should know when using each.

To test it out, I created a new project with Aurelia CLI, which now uses webpack by default.
Then I ran yarn add aurelia-toolbelt, and added aurelia.use.plugin(PLATFORM.moduleName('aurelia-toolbelt')); as suggested. Then I ran aurelia run and immediately got errors, such as:

ERROR in ./node_modules/aurelia-toolbelt/dist/commonjs/components/jquery/block-ui/aut-block-ui.js
Module not found: Error: Can't resolve './SharedOptions' in '~/test/node_modules/aurelia-toolbelt/dist/commonjs/components/jquery/block-ui'

ERROR in ./node_modules/aurelia-toolbelt/dist/commonjs/components/jquery/metis-menu/aut-metis-menu.html
Module not found: Error: Can't resolve 'metismenu/dist/metismenu.css' in '~/test/node_modules/aurelia-toolbelt/dist/commonjs/components/jquery/metis-menu'

Dear @khuongduybui,

The getting started page is not very user-friendly.

We have plans to make a complete overhaul. So it will look more like the bootstrap page.

To test it out, I created a new project with Aurelia CLI,

Your error is due to the fact that some of the jquery plugins are not easy to configure, neither in webpack nor in other formats, so we have created startup projects here that you could take a look, you need to make some changes in webpack.js to set the wheel in motion.
This is the starter kit for webpack 4.
if you still have any problems please let me know.

BTW, you should run this yarn add aurelia-toolbelt@0.9.2-alpha, and I've added another starter kit for just webpack and no asp.net core, find it here.
I ran au run --watch

@khuongduybui
You should use au run --watch because of this and this

I figured out the 2 errors; they are due to mis-case typos.
First one is here: from './SharedOptions' should be from './sharedOptions'.
Second one is here: "metismenu/dist/metismenu.css" should be "metismenu/dist/metisMenu.css" (see metismenu).

authors: HamedFathi khuongduybui shahabganji

repo: aurelia-toolbelt/aurelia-toolbelt


text:
TypeScript's emitDecoratorMetadata produces client-only globals

I'm submitting a bug report

Library Version:
1.5.0

Please tell us about your environment:

Operating System:
Linux F26

Node Version:
8.9.4

NPM Version:
5.6.0

JSPM OR Webpack AND Version
webpack 3.11.0

Browser:
all

Language:
TypeScript 2.7.2

Current behavior:
I am using the emitDecoratorMetadata compiler option in my TypeScript application to leverage the @autoinject decorator where appropriate. The emitDecoratorMetadata option is currently producing browser-only globals. In the custom element below I have explicitly avoided using autoinject and instead manually injected DOM.Element - however it is still producing some decorator metadata which references the Element type:
Source
@inject(DOM.Element)
@customAttribute('zoom')
export class Zoom {
    element: Element;

    constructor(element: Element) {
        this.element = element;
    }

Transpiled
e = i([o.inject(o.DOM.Element), o.customAttribute('zoom'), r('design:paramtypes', [Element])], e);

I have also tried typing the element field as follows:
@inject(DOM.Element)
@customAttribute('zoom')
export class Zoom {
    element: DOM.Element;

    constructor(element: DOM.Element) {
        this.element = element;
    }

However this produces the following TypeScript error:
TS2503: Cannot find namespace 'DOM'.

Expected/desired behavior:

What is the expected behavior?

There should be some mechanism for using DOM.Element as an actual property type in TypeScript, as then the emitted decorator metadata would align with the DOM.Element type in PAL and not the Element type from the browser.

Will this work: constructor(element: typeof DOM.Element) ?

@EisenbergEffect I tried that, and it then stopped me using any methods that actually exist on the Element type:
ERROR in [at-loader] ./src/components/example.ts:27:22
    TS2339: Property 'classList' does not exist on type '{ new (): Element; prototype: Element; }'.

ERROR in [at-loader] ./src/components/example.ts:33:22
    TS2339: Property 'addEventListener' does not exist on type '{ new (): Element; prototype: Element; }'.

ERROR in [at-loader] ./src/components/example.ts:37:22
    TS2339: Property 'removeEventListener' does not exist on type '{ new (): Element; prototype: Element; }'.

I suppose you could cast it before assigning in the constructor. Not idea, but a little better.

That'll do for now. Thanks @EisenbergEffect.

authors: EisenbergEffect michaelbull

repo: aurelia/pal

license: mit


text:
Fix buildQueryString params types

fix buildQueryString parameters types
add typing on private methods
various var chore

This PR is a bit hard to follow. It looks like the spacing changed a lot. Can you possible ensure that you are using the same 2 spaces rule as us? Also, if you can void including the dist folder in your commit, that would also help. Finally, if possible, when you have multiple commits, would you mind squashing them?
I'm going to close them for now. If you can resubmit as above, that would greatly help.

Sorry, I am a beginner on github PR.
I review my commit with your advices and resubmit another PR.

authors: EisenbergEffect npelletm

repo: aurelia/path


text:
add back support for I2C sensors

Depends on #simplify_api branch/PR in OXRS_Sensor library
https://github.com/austinscreations/OXRS-AC-I2CSensors-ESP-LIB/pull/22

Tested and working on a LilyGO + PWM shield + SHT40 temp/humidity sensor breakout.


text:
Introduce a config file

Scope

Right now the burner-wallet is configured in App.js. Variables are overwritten based on the location of the browser.
LeapDAO has proposed a config.js file in their burner fork that could easily be used to make the project more configurable: https://github.com/leapdao/burner-wallet/pull/134
@dmihal also proposed a nice way to handle configuration: https://github.com/austintgriffith/burner-wallet/pull/194/commits/4ff5d2f4b9d4ad37ed970eb2aa5784fa066e880a
Note that in @dmihal's spec, there might be hints on how this config.js file should look like: https://docs.google.com/document/d/1GtS_NxhxSt9XVTphp4fWRvjeQjIVT8WbYsqpKAlWbfE/edit If you think we should implement according to this spec, feel free to ping @dmihal for advice.

Deliverables

Somehow combine or decide between one of the two two approaches outlined above and introduce a config.js file to the repo

Gains for the project

Easier whitelabeling and configuration

Roles
bounty gardener: @TimDaub / 10%
bounty worker: name / 75%
bounty reviewer: name / 15%

I would totally love some configuration options, allowing to configure network node, symbols, token names and turning some features on/off based on a particular need of a particular pop-up economy.
Alternatively, a documentation on how to do this would be great. Not only changing constants in App.js, but turning on/off some particular features (some pop-up economies will not have a prediction market, some don't need Wyre or exchanges).

authors: TimDaub jooray

repo: austintgriffith/burner-wallet


text:
🛑 repl.co is down

In b9e94ba, repl.co (https://hello-repl.auteen.repl.co) was down:

HTTP code: 404
Response time: 425 ms

Resolved: repl.co is back up in c367802 after 1 hour, 11 minutes.

repo: auteen/autoreplit


text:
fix: clippy

Proposal

Fix clippy issues

Codecov Report

Merging #40 (a41a66f) into main (94449b3) will not change coverage.
The diff coverage is 50.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main      #40   +/-   ##
=======================================
  Coverage   76.25%   76.25%
=======================================
  Files          49       49
  Lines        1259     1259
=======================================
  Hits          960      960
  Misses        299      299

Impacted Files
Coverage Δ

src/presentation/cronjob/mod.rs
0.00% <0.00%> (ø)

...tation/cronjob/commands/retry_charging_invoices.rs
88.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

authors: AndrewHanasiro codecov-commenter

repo: auth-plus/auth-plus-billing


text:
Babel Polyfill Error on 1.3.0

Whenever I try to run the 1.3.0 I receive the following error:
Uncaught Error: only one instance of babel-polyfill is allowed
I'm using babel for ES6 and I don't plan on reconfiguring my entire site to make auth0 analytics work. Luckily when I use 1.2.1 the issue doesn't persist so I'll be using that until it doesn't block regular site babel usage.

Hey @cpres! Sorry for the delay. I'll investigate what's happening and keep you updated.

I used 1.3.1 and still have the same issue!

Hi @johnnabil. What version of babel-polyfill are you using?

@francocorreasosa I have an old vue-project with manually configured webpack v3 and I import babel-poylfill in main.js file where Vue app is created. Still got issue Uncaught Error: only one instance of babel-polyfill is allowed. Version 1.3.1 of analytics is used from https://cdn.auth0.com/js/analytics/1.3.1/analytics.min.js.
babel-polyfill in packaje json is ^6.26.0. Could You help with it?

authors: NShulzhenko cpres francocorreasosa johnnabil


text:
[1/2] DXCDT-129: Set up go-vcr for tests

Description
In this PR we are adding https://github.com/dnaeon/go-vcr so it can record our request/responses and re-use them for subsequent tests in order to speed up testing.

References

Testing

[x] This change adds test coverage for new/changed/fixed functionality

Checklist

[x] I have read and agreed to the terms within the Auth0 Code of Conduct.
[x] I have read the Auth0 General Contribution Guidelines.
[x] I have reviewed my own code beforehand.
[x] I have added documentation for new/changed functionality in this PR.
[x] All active GitHub checks for tests, formatting, and security are passing.
[x] The correct base branch is being used, if not main.

Codecov Report

Merging #67 (53101e6) into main (7ab091a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #67   +/-   ##
=======================================
  Coverage   94.59%   94.59%
=======================================
  Files          33       33
  Lines        5550     5550
=======================================
  Hits         5250     5250
  Misses        240      240
  Partials       60       60

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7ab091a...53101e6. Read the comment docs.

Note: Tests are failing cuz we reached the global limit on revoking the signing keys. Will try again later.

authors: codecov-commenter sergiughf


text:
Normalize use of shortcode and widget

Lets see how to improve the use of shortcode and login page, handle better the options and provide parity in configurations

Old but still relevant.
Includes #407

authors: glena joshcanhelp


text:
New design for Authlib v0.13

Track of server metadata urls:

[ ] https://accounts.google.com/.well-known/openid-configuration

See "next" branch

repo: authlib/loginpass


text:
[Feature Request] gRPC Support

Hi,
zerocode supports REST endpoints, it would be great if we can add gRPC support as its becoming prominent technology in the industry.

Hi,
zerocode supports REST endpoints, it would be great if we can add gRPC support as its becoming prominent technology in the industry.

Hello @Amar-C, Yes, happy to support.
Can you provide an usecase(example scenario) with example of request/response you want it to be?
Then will try to implement and put the solution in place.

authors: Amar-C authorjapps

repo: authorjapps/zerocode


text:
User not refreshed if storage is emptied

Hello,
I'm trying to use this library in my project.
When the user logs out from a tab I would like to log him out of all tabs.
For this I thought  I could configure userManager to use localStorage but even if I remove the user from one tab the user that was loaded in the context of other tabs is not refreshed. Is there an event I should be listening too or if not would it be possible to tell the provider to call the userManager.getUser() function at a certain interval to refresh the user in the context?
Thanks!

userManager.removeUser() or userManager.signoutRedirect/Popup/Silent should make it work

I have the same problem. I set the userStore to use local storage in order to have the session shared amongst multiple tabs:
oidcConfig.userStore = new WebStorageStateStore({
    store: window.localStorage
});

...and in my sign out handler I have:
const onClick = () => {
    auth.removeUser();
    Router.push('/signin');
};

...which works fine for the tab where the Signout was clicked... but switching to the second tab, I see that the AuthContext still thinks isAuthenticated == true and that a user exists - despite the entry now missing in local storage.
I played with signoutRedirect() - but I don't in fact want to log out at the authorization provider - just the open tabs of my app.
I've found snippets in the Issues here about using events, but haven't had any luck trying those out as yet.

Has anyone figured out how to get this to work correctly?  I am running to the same issue.  I do notice that after the session's token has expired, the remaining tabs (presumably because they can't refresh the token) will transitioned to a state where auth.error is set.

I believe I've figured out how this can be done.   The first step is to include monitorSession={true} to the AuthProvider, ie:
 <AuthProvider {...otherConfig} monitorSession={true}>
   ...
</AuthProvider>

The second is to add a called back to the addUserSignedOut event, ie:
const auth = useAuth()

React.useEffect(() => {
        return auth.events.addUserSignedOut(() => {
            auth.signoutSilent();
        });
    }, [auth.events]);

And there you have it.  All other tabs will be signed out.

I believe I've figured out how this can be done. The first step is to include monitorSession={true} to the AuthProvider, ie:
 <AuthProvider {...otherConfig} monitorSession={true}>
   ...
</AuthProvider>

The second is to add a called back to the addUserSignedOut event, ie:
const auth = useAuth()

React.useEffect(() => {
        return auth.events.addUserSignedOut(() => {
            auth.signoutSilent();
        });
    }, [auth.events]);

And there you have it. All other tabs will be signed out.

This works if you want to sing out from the provider but does not work if you only want to remove the user from the browsers storage.

This issue (question) staled some time ago, closing it for now.

authors: AlexThurston EloHg kramer99 pamapa

repo: authts/react-oidc-context


text:
🛑 Do Práce na Kole § dopracenakole.cz is down

In 77302b5, Do Práce na Kole § dopracenakole.cz (https://dopracenakole.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Do Práce na Kole § dopracenakole.cz is back up in 060b779.

repo: auto-mat/automat-statuspage


text:
🛑 Automat eshop § obchod.auto-mat.cz is down

In 12a39c1, Automat eshop § obchod.auto-mat.cz (https://obchod.auto-mat.cz/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Automat eshop § obchod.auto-mat.cz is back up in 3fb7391.


text:
console log when we exceed 1000ms for a load

Any objection? I usually avoid checking in console.warns() but at least at the moment I want to emphasize finding and fixing these slow documents.

I can absolutely see the value in this. Is it worth making it optional?

yea, it should probably be tied to a debug setting. i'll update the patch.

I'm going to drop this PR -- I still think it's a good idea and we can revive it later but it's not an active problem and I think building on the perfLogger model would be a better plan.

authors: acurrieclark pvh

repo: automerge/automerge-repo


text:
Plugin fails to analyze Dagger usages

Build scan link

Reproducer kapt-dagger.zip
Plugin version

0.78.0
Gradle version

7.0 and 7.2
Describe the bug

When Dagger is used with kapt the plugin will print Could not reflectively access processor class dagger.internal.codegen.ComponentProcessor and will then go ahead to suggest
Plugin advice:
- kotlin-kapt: this project has the kotlin-kapt (org.jetbrains.kotlin.kapt) plugin applied, but no annotation processors (or no used annotation processors), which is redundant.

To Reproduce
Steps to reproduce the behavior:

Add Dagger as a kapt dependency

Expected behavior

Plugin does not fail to access the Dagger processor and does not suggest to remove kapt.
Additional context

I wonder if the behavior should generally be different if the access to a processor class fails. Maybe a different message for the plugin advice? In bigger builds it's easy to miss the "Could not reflectively access ..." message. I can open a feature request for that if you think it makes sense.

Thanks for the reproducer. I actually just noticed this myself the other day but didn't have time to investigate. This makes it so much easier.
Regarding "Could not reflectively access...", what do you think would be a better solution? I'm open to improving this use-case. Warnings-as-errors? Something else?

I was thinking that the plugin advice would say something like "Could not determine whether kapt is used because processor ... could not be accessed" instead of recommending the removal of kapt. That way even if you miss the log beforehand it's clear from the actual output. Currently you'd probably try removing kapt and then realize it was actually needed when things  don't build anymore. It could still use the plugin advice severity

That might be feasible. Would you mind filing a separate feature request for that?

This is pretty interesting. The dagger AP has a pretty complex initialization compared to other APs I've looked at. It even uses Dagger itself (sigh). Here's the top of the stacktrace from the failing init() call:
> Task :settings:findDeclaredProcsDebug
Trying to initialize annotation processor with type dagger.internal.codegen.ComponentProcessor
Could not initialize dagger.internal.codegen.ComponentProcessor. May not be able to get supported annotation types.
java.lang.NoSuchMethodError: 'java.lang.Object dagger.internal.Preconditions.checkNotNullFromProvides(java.lang.Object)'
        at dagger.internal.codegen.ProcessingEnvironmentModule_DaggerElementsFactory.daggerElements(ProcessingEnvironmentModule_DaggerElementsFactory.java:39)
        at dagger.internal.codegen.ProcessingEnvironmentModule_DaggerElementsFactory.get(ProcessingEnvironmentModule_DaggerElementsFactory.java:30)
        at dagger.internal.codegen.ProcessingEnvironmentModule_DaggerElementsFactory.get(ProcessingEnvironmentModule_DaggerElementsFactory.java:11)
        at dagger.internal.DoubleCheck.get(DoubleCheck.java:47)
        at dagger.internal.codegen.validation.InjectBindingRegistryImpl_Factory.get(InjectBindingRegistryImpl_Factory.java:54)
        at dagger.internal.codegen.validation.InjectBindingRegistryImpl_Factory.get(InjectBindingRegistryImpl_Factory.java:14)
        at dagger.internal.DoubleCheck.get(DoubleCheck.java:47)
        at dagger.internal.codegen.DaggerComponentProcessor_ProcessorComponent.injectComponentProcessor(DaggerComponentProcessor_ProcessorComponent.java:741)
        at dagger.internal.codegen.DaggerComponentProcessor_ProcessorComponent.inject(DaggerComponentProcessor_ProcessorComponent.java:736)
        at dagger.internal.codegen.ComponentProcessor.processingSteps(ComponentProcessor.java:127)
        at dagger.shaded.androidx.room.compiler.processing.javac.JavacBasicAnnotationProcessor.steps(JavacBasicAnnotationProcessor.kt:41)
        at dagger.shaded.auto.common.BasicAnnotationProcessor.init(BasicAnnotationProcessor.java:121)
        at com.autonomousapps.tasks.FindDeclaredProcsTask.tryInit(FindDeclaredProcsTask.kt:166)

So, at the very least, it's choking on the NoSuchMethodError because it can't find dagger.internal.Preconditions.checkNotNullFromProvides. This makes sense, because I'm loading the AP class dynamically at runtime, in a classloader that doesn't also have this other required class. I dug through the decompiled bytecode a bit (for some reason, IDEA can't download the source jars?), and in this case, it is required to call init() in order to then call getSupportedAnnotationTypes().
So there are a couple of options:

Punt and create a list of known annotation types that dagger supports. Meh.
Treat dagger a bit specially, which may be warranted given its prominence, and try to appease it by creating a custom classloader and loading more stuff at runtime.
Something else??

@gabrielittner you can workaround this right now by updating your build.gradle:
buildscript {
  repositories {
    mavenCentral()
  }
  dependencies {
    classpath("com.google.dagger:dagger:2.38.1")
    classpath("com.squareup:javapoet:1.13.0")
  }
}

The annotation processor analysis is failing because it can't initialize the dagger AP due to classes from these dependencies missing from the build classpath. I will be working on resolving this transparently.

Thanks for the workaround, that's helpful 👍
I've opened the extra feature request for our message discussion.

Resolved, will be in the next release.

authors: autonomousapps gabrielittner


text:
Interrogate consumer proguard files for rules.

Resolves https://github.com/autonomousapps/dependency-analysis-android-gradle-plugin/issues/227.
TODO:

Add a test
Rename ProguardClasses to something not dumb
Resolve TODOs.

and as a follow-up:

Consider finding a way to make the "metadata" more discoverable. For instance, it would be nice to know why a dependency was not marked unused. We could say "this dependency provides consumer proguard rules and so, out of an abundance of caution, we are saying keep it." Another complementary option would be to provide some kind of DSL configuration.

Build failed https://gradle.com/s/omx63tw6vj2rk

Example failed test: https://scans.gradle.com/s/omx63tw6vj2rk/tests/:functionalTest/com.autonomousapps.android.AnnotationProcessorSpec/dagger is used with annotationProcessor on method (Gradle 6.5.1 AGP 4.1.0-beta01)?anchor=e30&focused-exception-line=0-5#1
This is not unexpected. A consequence of whitelisting all android libs that supply proguard rules is now a lot of things get filtered out, even if they're truly unused. I don't like it so I need to consider how to finesse the analysis. Maybe look for usages of reflection?

My idea with looking for reflective use has grown more complex. The actual reflection is done in the CameraX class, which is provided by the androidx.camera:core dependency, which is a transitive dependency of androidx.camera:camera-camera2. So I'd have to look in not only the direct dependencies, but the transitive dependencies, and correlate them back up the graph.


text:
influence of diffrent normalization

Hi there,
I want to ask your advice regarding the normalization layers. I am implementing a network similar to yours, but I found if I use batch norm layer, during testing time model.eval() will give much worse results. Did you encounter this before? Thank you for your reply!

I did several experiments about BN layers for OccNet. With BN layers, the training will be much stable and the final reconstruction results will be more 'average' and generally well. Without BN layers you cannot easily train the network(the loss fluctuated) and final results are statistically worse.

I did several experiments about BN layers for OccNet. With BN layers, the training will be much stable and the final reconstruction results will be more 'average' and generally well. Without BN layers you cannot easily train the network(the loss fluctuated) and final results are statistically worse.

Hi AlexsaseXie, did you call model.eval() before doing inference ? I get very bad results if I call model.eval()

authors: AlexsaseXie hua-wu-que


text:
Update default major versions for Teleport recipes

This PR updates the major version used to download Teleport products to the current latest of each. (I wasn't able to find a version 17 package for tsh.)

Looks like they stopped shipping a separate release of TSH:

Starting with version 17, Teleport no longer provides a separate tsh.pkg macOS
package.

Instead, teleport.pkg and all macOS tarballs include signed and notarized
tsh.app and tctl.app.

Which is too bad, I liked the TSH package because it was 80% smaller if it was the only tool you needed.

authors: homebysix kevinmcox

repo: autopkg/kevinmcox-recipes


text:
🛑 Broker is down

In 5af3c67, Broker (https://broker.autovance.com/health) was down:

HTTP code: 503
Response time: 206 ms

Resolved: Broker is back up in 5d554f3.

repo: autovance/uptime


text:
refactor(ndt_scan_matcher): rework parameters

Description
Implement the ROS Node configuration layout described in https://github.com/orgs/autowarefoundation/discussions/3371.

Remove the default value from the source code in order to ensure all parameter values are passed from the parameter files.

already completed.

Create the yaml configs in this package and the autoware_launch repository.

already completed.

Create the schema.

This PR.

Update Parameters chapter in the readme file.

This PR.

Tests performed
Lsim works.
passed check-jsonschema.

Effects on system behavior

Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

I will open this pr after merging https://github.com/autowarefoundation/autoware.universe/pull/6208 and https://github.com/autowarefoundation/autoware.universe/pull/6231

@YamatoAndo
It works fine when I check schema locally in my pc.
~/autoware/src/universe/autoware.universe/localization$ find -wholename '*/schema/*.schema.json' -printf '%p: ' -execdir bash -c 'check-jsonschema --schemafile "$1" ../config/"${1:2:-12}"*.param.yaml' bash '{}' +
./pose_instability_detector/schema/pose_instability_detector.schema.json: ok -- validation done
./twist2accel/schema/twist2accel.schema.json: ok -- validation done
./gyro_odometer/schema/gyro_odometer.schema.json: ok -- validation done
./yabloc/yabloc_common/schema/ll2_decomposer.schema.json: ./yabloc/yabloc_common/schema/ground_server.schema.json: ok -- validation done
./yabloc/yabloc_image_processing/schema/graph_segment.schema.json: ./yabloc/yabloc_image_processing/schema/segment_filter.schema.json: ./yabloc/yabloc_image_processing/schema/undistort.schema.json: ok -- validation done
./yabloc/yabloc_pose_initializer/schema/camera_pose_initializer.schema.json: ok -- validation done
./yabloc/yabloc_monitor/schema/yabloc_monitor.schema.json: ok -- validation done
./yabloc/yabloc_particle_filter/schema/camera_particle_corrector.schema.json: ./yabloc/yabloc_particle_filter/schema/gnss_particle_corrector.schema.json: ./yabloc/yabloc_particle_filter/schema/predictor.schema.json: ok -- validation done
./geo_pose_projector/schema/geo_pose_projector.schema.json: ok -- validation done
./ndt_scan_matcher/schema/ndt_scan_matcher.schema.json: ok -- validation done
./landmark_based_localizer/ar_tag_based_localizer/schema/ar_tag_based_localizer.schema.json: ok -- validation done
./localization_error_monitor/schema/localization_error_monitor.schema.json: ok -- validation done
./stop_filter/schema/stop_filter.schema.json: ok -- validation done

However, it seems that the pull request check is failing.
https://github.com/autowarefoundation/autoware.universe/actions/runs/7707283935/job/21135764003?pr=6229
./localization/ndt_scan_matcher/schema/ndt_scan_matcher.schema.json: Schema validation errors were encountered.
  ../config/ndt_scan_matcher.param.yaml::$./**.ros__parameters: 'frame' is a required property
  ../config/ndt_scan_matcher.param.yaml::$./**.ros__parameters: 'ndt' is a required property
  ../config/ndt_scan_matcher.param.yaml::$./**.ros__parameters: 'initial_pose_estimation' is a required property
  ../config/ndt_scan_matcher.param.yaml::$./**.ros__parameters: 'validation' is a required property
  ../config/ndt_scan_matcher.param.yaml::$./**.ros__parameters: 'score_estimation' is a required property
  ../config/ndt_scan_matcher.param.yaml::$./**.ros__parameters: 'covariance' is a required property
  ../config/ndt_scan_matcher.param.yaml::$./**.ros__parameters: 'dynamic_map_loading' is a required property
  ../config/ndt_scan_matcher.param.yaml::$./**.ros__parameters: Additional properties are not allowed ('base_frame', 'converged_param_nearest_voxel_transformation_likelihood', 'converged_param_transform_probability', 'converged_param_type', 'critical_upper_bound_exe_time_ms', 'dynamic_map_loading_map_radius', 'dynamic_map_loading_update_distance', 'estimate_scores_by_no_ground_points', 'initial_estimate_particles_num', 'initial_pose_distance_tolerance_m', 'initial_pose_offset_model_x', 'initial_pose_offset_model_y', 'initial_pose_timeout_sec', 'input_sensor_points_queue_size', 'lidar_radius', 'lidar_topic_timeout_sec', 'map_frame', 'max_iterations', 'n_startup_trials', 'ndt_base_frame', 'num_threads', 'output_pose_covariance', 'regularization_enabled', 'regularization_scale_factor', 'resolution', 'step_size', 'trans_epsilon', 'use_covariance_estimation', 'z_margin_for_ground_removal' were unexpected)

Do you know what the cause is?

Sorry.
I needed to update the branch after merging https://github.com/autowarefoundation/autoware.universe/pull/6208.

authors: SakodaShintaro YamatoAndo


text:
feat: add cgroup setter node

Description

This PR adds cgroup setter node which attach processes to your custom cgroup.
Related links

Tests performed

Confirmed that this node attach processes to some custom cgroups.
Confirmed that this node output error logs when it fail to write attach processes to a cgroup, pgrep fail to find a pid, or the config file is wrong.
Confirmed that this node publish proper /diagnostics.

Notes for reviewers

Assumptions, Write permission is required for a custom cgroup, and /sys/fs/cgroup/cgroup.procs to attach a PID to the cgroup.
Interface changes

ROS Topic Changes

ROS Parameter Changes

Effects on system behavior

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@TetsuKawa @ito-san Do you still need this modification?

authors: TetsuKawa mitsudome-r


text:
Added support for One-Shot Mode (OSM)

Just added the support for One-Shot Mode.
Simple usage is to call the "enableOSM" or "disableOSM" member function before configuring the mode of operation.
Let me know if any optimization is needed or could be done in a better way.

line 176 needs to be ==

I guess not. No change is necessary.
That line is simply storing the new value into the mode variable by the decision of osmFlag. osmFlag itself is conditional logic.

I get compiler errors the way it is:
C:\Users\andre\Documents\Arduino\libraries\arduino-mcp2515\mcp2515.cpp: In member function 'MCP2515::ERROR MCP2515::setMode(MCP2515::CANCTRL_REQOP_MODE)':
C:\Users\andre\Documents\Arduino\libraries\arduino-mcp2515\mcp2515.cpp:176:63: error: assignment of read-only parameter 'mode'
mode = osmFlag ? mode | CANCTRL_OSM : mode & ~(CANCTRL_OSM);
^
C:\Users\andre\Documents\Arduino\libraries\arduino-mcp2515\mcp2515.cpp:176:20: error: invalid conversion from 'int' to 'MCP2515::CANCTRL_REQOP_MODE' [-fpermissive]
mode = osmFlag ? mode | CANCTRL_OSM : mode & ~(CANCTRL_OSM);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
and since its basically the same as
if( mode = osmFlag)
{mode | CANCTRL_OSM}
else
{mode & ~(CANCTRL_OSM)}
I´d say it needs to be a comparison, not an assignment.
It still send 2 messages as a burst tho, not 1...

Haha thanks for showing me indirectly a mistake here.
The solution is to remove const keyword. SIMPLE. Or use a entirely new variable. I,ll make the changes tom its late here.
Plz consult how shorthand if are used.
https://www.w3schools.com/cpp/cpp_conditions_shorthand.asp

Here is the doc of MCP2515: http://ww1.microchip.com/downloads/en/DeviceDoc/80179g.pdf
It is a bug of this chip (see the page 2). If the SPI is not set to disabled (or using other solutions), the chip will keep pending. That is why the chip keep send can frames to the bus.
I think #30 solved the problem temporarily, we can direct operate SPI.
But "Use hardware pins (TXnRTS) to request transmission" may be the best solution.
@DeltaC6

This don't work: 179: modifyRegister(MCP_CANCTRL, CANCTRL_REQOP, mcpMode);
CANCTRL_REQOP mask exclude CANCTRL_OSM bit.
This work: modifyRegister(MCP_CANCTRL, CANCTRL_REQOP | CANCTRL_OSM, mcpMode);

This don't work: 179: modifyRegister(MCP_CANCTRL, CANCTRL_REQOP, mcpMode); CANCTRL_REQOP mask exclude CANCTRL_OSM bit.
This work: modifyRegister(MCP_CANCTRL, CANCTRL_REQOP | CANCTRL_OSM, mcpMode);

Very good catch. The CANCTRL_REQOP is 0xE0, which is excluding the OSM bit 0x8 on CANCTRL[3]
Here is a picture from the mcp2515 datashet;

I can also confirm this fixes it, tested with an osciloscope.
@Loverboy7000 This would be a great feature to have in the master, is there anything I could do to help?

anyone can merge this?


text:
add an enhanced config loader that runs based on load.properties

So in this one, we have something like ConfigurationSource but each implementation has a label that must be specified via load.properties in order for the loader to activate.
So If I've got an implementation:
@ServiceProvider
public class SuperENVSource implements SuperConfigSource {

  @Override
  public String label() {

    return "env";
  }

  @Override
  public Map<String, String> load(ConfigLoadCTX configuration) {

    Map<String, String> resultMap =  // get and tranform env variables via wacky logic

    return resultMap;
  }
}

I can activate it with:
load.properties=config-source:env

@agentgt how does this make you feel

EDIT question. How would profiles work with the above?

observe
@ServiceProvider
public class SuperProfileSource implements SuperConfigSource {

  @Override
  public String label() {

    return "profile";
  }

  @Override
  public Map<String, String> load(ConfigLoadCTX configuration) {

    var profileKey = configuration.getProperty("profiles").orElseThrow();

    var profileSources = configuration.getProperty("profile.sources").orElseThrow();
    var newLoadProperties = // expand the profiles using profile sources to replace _Profile_

    return Map.of("load.properties", newLoadProperties);
  }
}

and then
profiles=dev,canary
profile.sources=app-_Profile_.properties
load.properties=config-source:profile

I see. So our (snaphop-kvs) method of random token gets replaced instead of trying to use interpolation system.
I like it is just a that file, classpath, and config-source are special.
Perhaps this is a good stopgap solution for version 4.x and to build a file,classpath, or similar URI based one we add later.
The reason is I have no idea how you would do https://blah/${profile}. That is creating a config-source for traditional resources is awkard.

The other thing that kind of sucks with variables over URI query parameters is if you have multiple config-source calls of the same type and or matching variable names.
Profiles and loading rules (LoadFlag) is kind of the weird exception where we use variable names and we have a huge advantage in that each resource actually has a symbolic name as I mention in another comment.
_load_my_source=classpath://something.properties

The resource above has a symbolic name of my_source and thus you can namespace variables.
_var_my_source_my_var=1
_load_my_source=dotenv://${user.home}}/.config/${app}/.env

dotenv plugin asks from URI context what is my symbolic name = my_source. Then makes a call context.getProperty("_var_" + name + "_my_var"); except we can do this automagically like context.getProperty("my_var") and the variable resolution does the namespace check.
I suppose with config-source you could have a parameter for name spacing variables... or I guess you just live with this limitation.

Let me give you a better example of the variable problem and I think we can agree that config-source needs variables?
Imagine if a plugin uses password or username variables. The collision is probably pretty high. Even if it prefixes with its type like gcloud_username and gcloud_password you can't allow multiple gcloud in a load.properties with the same config. I suppose the trick to this is spread it out in multiple resources.
This also gets weird because file and classpath are basically configured with normal interpolation and thus through their URI.
So it begs the question what does config-source even get you over the URI loading mechanism other than a possible avoidance of long URI in load.properties (which can be fixed with interpolation anyway).
Profiles just happens to be a super weird exception but it could have been implemented as:
profile:classpath://__PROFILE__.properties#?profileVar=profiles
or just use the darn interpolation anyway
profile:classpath://__PROFILE__.properties#?profiles=${profiles}
Notice how I used #. That is the fragment part of the  URI and basically no real resources actually use it and thus you can go to town on putting whatever after it. Annoyingly though you would have to deal with the escaping of it in regular properties files.

The reason is I have no idea how you would do https://blah/${profile}. That is creating a config-source for traditional resources is awkward.

I don't follow.

I don't follow.

As a thought experiment make a file or classpath version of config-source plugin. Then in load.properties try to string multiple of those guys.

file or classpath version of config-source plugin. Then in load.properties try to string multiple of those guys.

config.files=app.properties,app.yml
load.properties=config-source:files

inside of app.yml
config:
    files: chain.properties
load:
    properties: config-source:files

@ServiceProvider
public class SuperFileSource implements SuperConfigSource {

  @Override
  public String label() {

    return "files";
  }

  String[] splitPaths(String location) {
    return Pattern.compile("[\\s,;]+").split(location);
  }

  @Override
  public Map<String, String> load(ConfigLoadCTX configuration) {

    var paths = configuration.getProperty("config.files").map(this::splitPaths).orElseThrow();

    Map<String, String> resultMap = // load em

    return resultMap;
  }
}

Yes I figured you would answer with multiple resources. That is what I meant by awkward in that you use the resource as a namespace (as the variables are overridden on the new load).
I thought I mentioned that somewhere as an option but again it isn't how file or classpath currently work so again you have different behavior.
Like currently load.properties has a mixture and if it was implemented like the above as a deep core solution you would have to do what you showed me above.
That is what I'm trying to get out with a solid model. file and classpath are not special. They are plugins that happen to be builtin.

makes sense

authors: SentryMan agentgt

repo: avaje/avaje-config


text:
IDE Fatal Errors AGAIN...

I'm sorry saw that after I updated to Version 1.3.1 yesterday.
It report another NullPointerException.
java.lang.NullPointerException
	at com.avast.android.butterknifezelezny.common.Utils.isClassAvailableForPsiFile(Utils.java:314)
	at com.avast.android.butterknifezelezny.butterknife.ButterKnifeFactory.findButterKnifeForPsiElement(ButterKnifeFactory.java:45)
	at com.avast.android.butterknifezelezny.navigation.NavigationMarkerProvider.getLineMarkerInfo(NavigationMarkerProvider.java:90)
	at com.intellij.codeInsight.daemon.impl.LineMarkersPass.addLineMarkers(LineMarkersPass.java:166)
	at com.intellij.codeInsight.daemon.impl.LineMarkersPass.doCollectInformation(LineMarkersPass.java:105)
	at com.intellij.codeHighlighting.TextEditorHighlightingPass.collectInformation(TextEditorHighlightingPass.java:67)
	at com.intellij.codeInsight.daemon.impl.PassExecutorService$ScheduledPass$1$1.run(PassExecutorService.java:438)
	at com.intellij.openapi.application.impl.ApplicationImpl.tryRunReadAction(ApplicationImpl.java:1104)
	at com.intellij.codeInsight.daemon.impl.PassExecutorService$ScheduledPass$1.run(PassExecutorService.java:429)
	at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:452)
	at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:402)
	at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:54)
	at com.intellij.codeInsight.daemon.impl.PassExecutorService$ScheduledPass.doRun(PassExecutorService.java:426)
	at com.intellij.codeInsight.daemon.impl.PassExecutorService$ScheduledPass.run(PassExecutorService.java:402)
	at com.intellij.concurrency.JobLauncherImpl$VoidForkJoinTask.exec(JobLauncherImpl.java:202)
	at jsr166e.ForkJoinTask.doExec(ForkJoinTask.java:260)
	at jsr166e.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:858)
	at jsr166e.ForkJoinPool.scan(ForkJoinPool.java:1687)
	at jsr166e.ForkJoinPool.runWorker(ForkJoinPool.java:1642)
	at jsr166e.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:109)

Thanks for fix this bug in advance~

Ok, a different problem. I'm working on it. It seems that that the file cannot be located in any module.

Hi, could you test this build https://www.dropbox.com/s/6ance9z7roaut9b/android-butterknife-zelezny-1.3.2.jar?dl=0 that everything is working for you. You seem to have some juicy projects ;)

@tomik-dev I have downloaded. I'm testing now. Plz waiting my response~

@tomik-dev Congratulation! It's worked. Ready to release!

OK, good to hear it. It's out.

authors: johnwatsondev tomik-dev

repo: avast/android-butterknife-zelezny


text:
Disable plugins for large file

Extremely large files are a problem for VIM. How about this plugin?
https://github.com/vim-scripts/LargeFile

Interesting

I don't think disabling plugins is useful, but disable their usage is.
Below a simple script to do that, i hope the code is clear :
fu! ProcessCommandList(alist)
  for l:opt_set in a:alist
    exe l:opt_set
  endfor
endfu

" file is large over 10mb; small under 24kb
let g:LargeFileSize = 1024 * 1024 * 10
let g:MediumFileSize = 1024 * 24

let s:LargeFileMsg = 'The file is larger than '
      \. (g:LargeFileSize / 1024 / 1024)
      \. ' MB, so some options are changed (see g:LargeFileSize).'

let g:SmallFileActionsOpen=[]
let g:SmallFileActionsEnter=[]
let g:MediumFileActionsOpen=[]
let g:MediumFileActionsEnter=[]
let g:LargeFileActionsEnter=[]
let g:LargeFileActionsOpen=[
      \ 'set eventignore+=Filetype',
      \ 'setlocal bufhidden=unload',
      \ 'setlocal buftype=nowrite',
      \ 'setlocal undolevels=-1',
      \ 'au VimEnter * echo "'.s:LargeFileMsg.'"'
      \]

fu! s:LargeFileSupport(...)
  if len(a:000)
    let b:filesize_at_init=a:000[0]
    let l:event='Open'
  else
    let l:event='Enter'
  endif
  let l:size = (b:filesize_at_init > g:LargeFileSize
        \ || b:filesize_at_init == -2) ? 'Large' :
        \ (b:filesize_at_init > g:MediumFileSize ? 'Medium' : 'Small')
  exe 'call ProcessCommandList(g:'.l:size.'FileActions'.l:event.')'
endfu

augroup LargeFile
  autocmd BufReadPre * silent call s:LargeFileSupport(getfsize(expand("<afile>")))
  autocmd BufEnter * silent call s:LargeFileSupport()
augroup END

We can use vim -u NONE to disable  plugins on large files, or script above. Thanks @luffah !

authors: cassiobotaro gilsondev lerrua luffah

repo: avelino/vim-bootstrap


text:
Add Feature: Node Status Report

We need Node Monitor to create and send a once-daily status report.
This status report must tell the recipient if any of their nodes are down, and if so, which ones.
It must be easily readable without the recipient having to do any math.
🩺
Method:

Create a new instance variable called self.last_status_report
On every step, Node Monitor should check if time.now() - self.last_status_report >= 1 day
If True, create and send out the status report.
If False, do nothing

The current notification message can be made more user friendly as it doesn't immediately tell the NP that their nodes are ok. NPs still need to remember the total number of nodes they have in production and make sure that is equal to the number of nodes "UP" + "UNASSIGNED"
Solution: The first line of the status report message should already indicate if action is required (this will tend to be what is seen on mobile notifications as well). More concretely:

#nodes 'UP' + #nodes 'Unassigned' = #nodes in production --> No action required
#nodes 'UP' + #nodes 'Unassigned' != #nodes in production --> Action required

After this first line, then the rest of details of the status report can be added (#nodes up, unassigned etc.) If you think of other data that could be included feel free to add that along.
Requirements:

[ ]  Add fields (probably in the preference or channel detail table) to show the number of nodes a NP has in production
[ ]  SQL query to get the number of nodes
[ ]  Function to construct message (maybe in the directory node_monitor_helpers

authors: louisevelayo mourginakis

repo: aviate-labs/node-monitor


text:
Set compat to conservative range

Do not assume compatibility with future versions of Julia, which may not be compatible with JET.
See comment here #417

Thanks!

authors: aviatesk jakobnissen


text:
Failed to authenticate

I'm trying to test out like this:
r = Redd.it(:script, client_id, cient_secret, username, password)
r.authorize!

The call above will make a request to /api/v1/access_token with a request header like
{
    "User-Agent": "Redd/Ruby, v0.7.3",
    "Authorization": "Basic …"
}

and a request body like
{
    grant_type: "password",
    username: "…",
    password: "…"
}

and I get this:
redd/lib/redd/response/raise_error.rb:12:in `on_complete': {:error=>"invalid_grant"} (Redd::Error::ExpiredCode)

I'm stuck and I'd appreciate if you could suggest me what I'm doing wrong. Thx!

Hmm...I'm genuinely baffled. This error should only pop up on "web" grants. I've just tested that the login works fine on my PC for both the gem and the edge versions and your request looks correct. Can you double-check some things?

[ ] The app was created as a "script" type in your preferences
[ ] The username you're logging in with is registered as a "developer" of the app.
[ ] Your credentials were copy-pasted correctly (I've had trouble with this twice :disappointed:)
[ ] As a last resort, maybe try changing your user agent? Redd.it(..., user_agent: "...")

I hope one of these solves your issue.

Okay, so I figure it. I'm using dotenv for storing a set of password, secret and such. And my password contained …$xxx,… and that got interpolated.  I'm so sorry for the hassle!
One suggest I could give here is that… maybe this error, you can return Redd::Error::InvalidCredentials instead of Redd::Error::ExpiredCode?

authors: avidw beatak

repo: avidw/redd


text:
Want to add Backtracking Algos

I want to add N-Queen, Rat In A Maze, Sudoku Solver etc. Please assign me

Go ahead  @ksalokya

I can add lot of backtracking problem-solutions including  Knight 's tour , subset partition , n-queen , rat-in-maze , sudoku-solver etc.
Plz assign me this.


text:
Added Program for Number of Provinces in CPP

Resolved Issue #161
Please merge this branch.

pull request merged, now please close the issue, you can also contribute to other repo's-https://github.com/avinash201199/Hacktoberfest-Guide
Note- only 2 pr per day on a single repo is accepted.
follow for more such repo to contribue :)


text:
Updated allcourses.json

Added two cloud computing courses to address issue #206

Sure @avinash201199.

Sure @avinash201199.

Hi @avinash201199, I have removed coursera course.
Could you please review it and merge.


text:
Myntra Clone Website

Title: Myntra Clone Website
Tech Tools: Html,Css and Js
Screenshort

Please assign me under OSEN

@Geeks-Arpan start working


text:
Github_Bomb_Issues

Description
Please include a summary of the change and which issue is fixed. List any dependencies that are required for this change.
Fixes #(issue_no)
Replace issue_no with the issue number which is fixed in this PR
Have you read the Contributing Guidelines on Pull Requests?

[x] Yes
[ ] No

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Documentation Update

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md
[x] My documentation follows Template for README.md
[x] My changes generate no new warnings
[x] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works.

This pull is for issue no #405 pls review it @avinashkranjan sir

repo: avinashkranjan/Amazing-Python-Scripts


text:
changes proposed by niels in #149

Review, but DO NOT MERGE This requires https://github.com/awalterschulze/regex-reexamined-coq/pull/157 to merge this. Let me worry about doing it in the right order.

Discussed offline: merging now and will post review

Discussed offline: merging now and will post review

repo: awalterschulze/regex-reexamined-coq


text:
CPP common test improvement

BA common test checking jacobian is extended (now it asserts all the values of BA sparse jacobian)
GMM test checking is refactored in a vector form
manualTests are renamed to commonTests

This looks like a good improvment.

authors: mikhailnikolaev tomjaguarpaw

repo: awf/ADBench


text:
add amplify studio blog

https://aws.amazon.com/jp/blogs/news/aws-amplify-studio-figma-to-fullstack-react-app-with-minimal-programming/

thank you for approved

repo: aws-amplify-jp/awesome-aws-amplify-ja


text:
CLI Crashes

Environment information
System:
  OS: macOS 13.3.1
  CPU: (10) arm64 Apple M2 Pro
  Memory: 182.00 MB / 16.00 GB
  Shell: /bin/zsh
Binaries:
  Node: 20.0.0 - ~/.nvm/versions/node/v20.0.0/bin/node
  Yarn: 4.2.1 - ~/.nvm/versions/node/v20.0.0/bin/yarn
  npm: 9.6.4 - ~/.nvm/versions/node/v20.0.0/bin/npm
  pnpm: undefined - undefined
NPM Packages:
  @aws-amplify/backend: Not Found
  @aws-amplify/backend-cli: Not Found
  aws-amplify: Not Found
  aws-cdk: Not Found
  aws-cdk-lib: Not Found
  typescript: Not Found
AWS environment variables:
  AWS_STS_REGIONAL_ENDPOINTS = regional
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
No CDK environment variables

Description
Since today, i'm not able to deploy locally nor in the pipeline, commands are crashing with:
TypeError: endpointFunctions[fn] is not a function

when i debug, the stack is:
[DEBUG] 2024-05-07T09:58:24.570Z: TypeError: endpointFunctions[fn] is not a function
    at callFunction (<project root>/node_modules/@aws-sdk/client-cloudformation/node_modules/@smithy/util-endpoints/dist-cjs/index.js:271:31)
    at evaluateCondition (<project root>/node_modules/@aws-sdk/client-cloudformation/node_modules/@smithy/util-endpoints/dist-cjs/index.js:280:17)
    at evaluateConditions (<project root>/node_modules/@aws-sdk/client-cloudformation/node_modules/@smithy/util-endpoints/dist-cjs/index.js:293:34)
    at evaluateTreeRule (<project root>/node_modules/@aws-sdk/client-cloudformation/node_modules/@smithy/util-endpoints/dist-cjs/index.js:412:39)
    at evaluateRules (<project root>/node_modules/@aws-sdk/client-cloudformation/node_modules/@smithy/util-endpoints/dist-cjs/index.js:433:35)
    at evaluateTreeRule (<project root>/node_modules/@aws-sdk/client-cloudformation/node_modules/@smithy/util-endpoints/dist-cjs/index.js:416:10)
    at evaluateRules (<project root>/node_modules/@aws-sdk/client-cloudformation/node_modules/@smithy/util-endpoints/dist-cjs/index.js:433:35)
    at resolveEndpoint (<project root>/node_modules/@aws-sdk/client-cloudformation/node_modules/@smithy/util-endpoints/dist-cjs/index.js:462:20)
    at Object.defaultEndpointResolver [as endpointProvider] (<project root>/node_modules/@aws-sdk/client-cloudformation/dist-cjs/endpoint/endpointResolver.js:7:49)
    at getEndpointFromInstructions (<project root>/node_modules/@aws-sdk/client-cloudformation/node_modules/@smithy/middleware-endpoint/dist-cjs/index.js:127:33)

When logging at the entrypoint of the stack, it seems Endpoint value is undefined:
{
  UseFIPS: false,
  Endpoint: undefined,
  Region: 'eu-west-3',
  UseDualStack: false
}

i had to delete my yarn.lock as mentioned here: https://github.com/aws/aws-sdk-js-v3/issues/5435#issuecomment-1790097191
and it seems working again, i can't figure why 🤷

Hey @JJK801, thank you for reaching out. Looks like you were able to mitigate the issue by reinstalling the AWS SDK v3. For further assistance i would suggest opening an issue on SDK repository. Closing this issue but do reach out if you are experiencing any issues with Amplify.

repo: aws-amplify/amplify-backend


text:
importing Schema model into lambda function is not recognised by typescript

Environment information
Using gen2. Want to import the schema into a lambda function. It is not recognised.

Describe the bug
Using gen2. Want to import the schema into a lambda function. It is not recognised.
Reproduction steps
Define a model:
  Connection: a
    .model({
      owner: a.string(),
      institutionId: a.string(),
      max_access_valid_for_days: a.integer(),
      transaction_total_days: a.integer(),
      refreshExpireTimestamp: a.integer(),
      connectionIdentifier: a.string(),
      status: a.string(),
      errorCounter: a.integer(),
      creationTimestamp: a.timestamp(),
      connectionTTL: a.integer()
    })
    .authorization((allow) => [allow.owner()]),

Try and use the schema definition in a lambda function:
import type { Schema } from '../../data/resource';

const connection = event.arguments.connection as Schema["Connection"];

Field types are not recognised:

Hey @cookiejest, thank you for reaching out. Refer to the following documentation providing an example on using the data client in a lambda function.
https://docs.amplify.aws/react/build-a-backend/functions/examples/create-user-profile-record/

while this approach allows for the function to execute against the model, it still doesn't allow for the Schema definition to be used like Schema["Connection"]. At least for me.

authors: cookiejest ykethan