scipy links to gfortran libraries with intel compilers.

Scipy built with icc/ifort links to gfortran libraries instead of intel fortran libraries. (intel compilers are used as per [1].) First reported here.
d_int_val comes from the libifcore library and should be linked. Instead gfortran libraries get linked and this results in missing symbols.  Adding  fcflags: -lifcore -fPIC  doesn't help either.
This happens because scipy thinks it's working with G95 compiler and gives -ffixed-form flag which ifort does not understand. Doesn't setting -fcompiler=intelem force the use of intel compiler ?
Though I'm not sure, I think scipy understands that it's using icc because some intel libraries are linked as shown by ldd.
Error message:
[sajid@xrmlite ~]$ python
Python 3.6.6 (default, Jul 19 2018, 15:02:18)
[GCC Intel(R) C++ gcc 7.3 mode] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy
>>> import scipy
>>> import scipy.optimize
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/intel-18.0.3/py-scipy-1.1.0-s5rupidaz3anzojgs6t6mzqbbbonfsg2/lib/python3.6/site-packages/scipy/optimize/__init__.py", line 270, in <module>
    from .optimize import *
  File "/home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/intel-18.0.3/py-scipy-1.1.0-s5rupidaz3anzojgs6t6mzqbbbonfsg2/lib/python3.6/site-packages/scipy/optimize/optimize.py", line 37, in <module>
    from .linesearch import (line_search_wolfe1, line_search_wolfe2,
  File "/home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/intel-18.0.3/py-scipy-1.1.0-s5rupidaz3anzojgs6t6mzqbbbonfsg2/lib/python3.6/site-packages/scipy/optimize/linesearch.py", line 18, in <module>
    from scipy.optimize import minpack2
ImportError: /home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/intel-18.0.3/py-scipy-1.1.0-s5rupidaz3anzojgs6t6mzqbbbonfsg2/lib/python3.6/site-packages/scipy/optimize/minpack2.cpython-36m-x86_64-linux-gnu.so: undefined symbol: for_cpystr
>>> import scipy.integrate
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/intel-18.0.3/py-scipy-1.1.0-s5rupidaz3anzojgs6t6mzqbbbonfsg2/lib/python3.6/site-packages/scipy/integrate/__init__.py", line 89, in <module>
    from .quadrature import *
  File "/home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/intel-18.0.3/py-scipy-1.1.0-s5rupidaz3anzojgs6t6mzqbbbonfsg2/lib/python3.6/site-packages/scipy/integrate/quadrature.py", line 10, in <module>
    from scipy.special import roots_legendre
  File "/home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/intel-18.0.3/py-scipy-1.1.0-s5rupidaz3anzojgs6t6mzqbbbonfsg2/lib/python3.6/site-packages/scipy/special/__init__.py", line 640, in <module>
    from ._ufuncs import *
ImportError: /home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/intel-18.0.3/py-scipy-1.1.0-s5rupidaz3anzojgs6t6mzqbbbonfsg2/lib/python3.6/site-packages/scipy/special/_ufuncs.cpython-36m-x86_64-linux-gnu.so: undefined symbol: d_int_val
>>>

Link info for scipy :
[sajid@xrmlite special]$ ldd _ufuncs.cpython-36m-x86_64-linux-gnu.so
        linux-vdso.so.1 =>  (0x00007ffc81bcd000)
        libmkl_rt.so => /home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/intel-18.0.3/intel-mkl-2018.2.199-y427ptu5mgmk34rjc4rsfhapxyf4j2fb/compilers_and_libraries/linux/mkl/lib/intel64/libmkl_rt.so (0x00002b3909b48000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00002b390a1e2000)
        libpython3.6m.so.1.0 => /home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/intel-18.0.3/python-3.6.6-iick7mjya7ytfu3bbytes7w7sr6wag7d/lib/libpython3.6m.so.1.0 (0x00002b390a3fe000)
        libgfortran.so.4 => /home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/gcc-4.8.5/gcc-7.3.0-xyzezhjmbiebkjfoakso464rhfshlkyq/lib64/libgfortran.so.4 (0x00002b390aa06000)
        libm.so.6 => /lib64/libm.so.6 (0x00002b390add9000)
        libgcc_s.so.1 => /home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/gcc-4.8.5/gcc-7.3.0-xyzezhjmbiebkjfoakso464rhfshlkyq/lib64/libgcc_s.so.1 (0x00002b390b0db000)
        libquadmath.so.0 => /home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/gcc-4.8.5/gcc-7.3.0-xyzezhjmbiebkjfoakso464rhfshlkyq/lib64/libquadmath.so.0 (0x00002b390b2f3000)
        libc.so.6 => /lib64/libc.so.6 (0x00002b390b532000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00002b390b8f5000)
        /lib64/ld-linux-x86-64.so.2 (0x000055a4d43c2000)
        libutil.so.1 => /lib64/libutil.so.1 (0x00002b390bafa000)
        libimf.so => /opt/intel/compilers_and_libraries_2018.3.222/linux/compiler/lib/intel64_lin/libimf.so (0x00002b390bcfe000)
        libsvml.so => /opt/intel/compilers_and_libraries_2018.3.222/linux/compiler/lib/intel64_lin/libsvml.so (0x00002b390c291000)
        libirng.so => /opt/intel/compilers_and_libraries_2018.3.222/linux/compiler/lib/intel64_lin/libirng.so (0x00002b390db9f000)
        libintlc.so.5 => /opt/intel/compilers_and_libraries_2018.3.222/linux/compiler/lib/intel64_lin/libintlc.so.5 (0x00002b390df14000)
~

Link info for intel-python-scipy :
[sajid@xrmlite special]$ ldd _ufuncs.cpython-36m-x86_64-linux-gnu.so
        linux-vdso.so.1 =>  (0x00007ffefbf84000)
        libmkl_rt.so => /opt/intel/intelpython3/lib/python3.6/site-packages/scipy/special/./../../../../libmkl_rt.so (0x00002aece4e3d000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00002aece54e9000)
        libpython3.6m.so.1.0 => /opt/intel/intelpython3/lib/python3.6/site-packages/scipy/special/./../../../../libpython3.6m.so.1.0 (0x00002aece5705000)
        libifport.so.5 => /opt/intel/intelpython3/lib/python3.6/site-packages/scipy/special/./../../../../libifport.so.5 (0x00002aece5c42000)
        libifcore.so.5 => /opt/intel/intelpython3/lib/python3.6/site-packages/scipy/special/./../../../../libifcore.so.5 (0x00002aece5e6d000)
        libimf.so => /opt/intel/intelpython3/lib/python3.6/site-packages/scipy/special/./../../../../libimf.so (0x00002aece61c8000)
        libsvml.so => /opt/intel/intelpython3/lib/python3.6/site-packages/scipy/special/./../../../../libsvml.so (0x00002aece6769000)
        libm.so.6 => /lib64/libm.so.6 (0x00002aece810c000)
        libintlc.so.5 => /opt/intel/intelpython3/lib/python3.6/site-packages/scipy/special/./../../../../libintlc.so.5 (0x00002aece840e000)
        libc.so.6 => /lib64/libc.so.6 (0x00002aece867f000)
        libgcc_s.so.1 => /home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/gcc-4.8.5/gcc-7.3.0-xyzezhjmbiebkjfoakso464rhfshlkyq/lib64/libgcc_s.so.1 (0x00002aece8a42000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00002aece8c59000)
        /lib64/ld-linux-x86-64.so.2 (0x0000560f5adc7000)
        libutil.so.1 => /lib64/libutil.so.1 (0x00002aece8e5e000)
        librt.so.1 => /lib64/librt.so.1 (0x00002aece9061000)

Scipy/Numpy/Python version information:
1.1.0 1.14.3 sys.version_info(major=3, minor=6, micro=6, releaselevel='final', serial=0)

Also, why are both libimf/libsvml and libm linked ? Isn't the first pair, the intel scalar/vector math library? And if the path to intel libraries is readable, why are only some libraries linked and the others not ?
Update :
Fixed the build flags but now f77 is ifort and f90 is gfortran. Build fails. Build log here.
compiling Fortran sources
Fortran f77 compiler: /home/sajid/packages/spack/lib/spack/env/intel/ifort -FI -fPIC -fp-model strict -O1 -qopenmp
Fortran f90 compiler: /home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/gcc-4.8.5/gcc-7.3.0-xyzezhjmbiebkjfoakso464rhfshlkyq/bin/gfortran -FR -fPIC -fp-model strict -O1 -qopenmp
Fortran fix compiler: /home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/gcc-4.8.5/gcc-7.3.0-xyzezhjmbiebkjfoakso464rhfshlkyq/bin/gfortran -FI -fPIC -fp-model strict -O1 -qopenmp

Full build logs, environment variables, and commands used?
On July 27, 2018 4:03:30 AM UTC, Sajid Ali<EMAIL_ADDRESS>wrote:

Scipy built with icc/ifort links to gfortran libraries instead of intel
fortran libraries. (intel compilers are used as per
[1].)
First reported here.
Adding  fcflags: -lifcore -fPIC  doesn't help either.
Error message:
[sajid@xrmlite ~]$ python
Python 3.6.6 (default, Jul 19 2018, 15:02:18)
[GCC Intel(R) C++ gcc 7.3 mode] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy
>>> import scipy
>>> import scipy.optimize
Traceback (most recent call last):
 File "<stdin>", line 1, in <module>
File
"/home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/intel-18.0.3/py-scipy-1.1.0-s5rupidaz3anzojgs6t6mzqbbbonfsg2/lib/python3.6/site-packages/scipy/optimize/__init__.py",
line 270, in <module>
   from .optimize import *
File
"/home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/intel-18.0.3/py-scipy-1.1.0-s5rupidaz3anzojgs6t6mzqbbbonfsg2/lib/python3.6/site-packages/scipy/optimize/optimize.py",
line 37, in <module>
   from .linesearch import (line_search_wolfe1, line_search_wolfe2,
File
"/home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/intel-18.0.3/py-scipy-1.1.0-s5rupidaz3anzojgs6t6mzqbbbonfsg2/lib/python3.6/site-packages/scipy/optimize/linesearch.py",
line 18, in <module>
   from scipy.optimize import minpack2
ImportError:
/home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/intel-18.0.3/py-scipy-1.1.0-s5rupidaz3anzojgs6t6mzqbbbonfsg2/lib/python3.6/site-packages/scipy/optimize/minpack2.cpython-36m-x86_64-linux-gnu.so:
undefined symbol: for_cpystr
>>> import scipy.integrate
Traceback (most recent call last):
 File "<stdin>", line 1, in <module>
File
"/home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/intel-18.0.3/py-scipy-1.1.0-s5rupidaz3anzojgs6t6mzqbbbonfsg2/lib/python3.6/site-packages/scipy/integrate/__init__.py",
line 89, in <module>
   from .quadrature import *
File
"/home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/intel-18.0.3/py-scipy-1.1.0-s5rupidaz3anzojgs6t6mzqbbbonfsg2/lib/python3.6/site-packages/scipy/integrate/quadrature.py",
line 10, in <module>
   from scipy.special import roots_legendre
File
"/home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/intel-18.0.3/py-scipy-1.1.0-s5rupidaz3anzojgs6t6mzqbbbonfsg2/lib/python3.6/site-packages/scipy/special/__init__.py",
line 640, in <module>
   from ._ufuncs import *
ImportError:
/home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/intel-18.0.3/py-scipy-1.1.0-s5rupidaz3anzojgs6t6mzqbbbonfsg2/lib/python3.6/site-packages/scipy/special/_ufuncs.cpython-36m-x86_64-linux-gnu.so:
undefined symbol: d_int_val
>>>

d_int_val comes from the libifcore library and should be
linked. Instead gfortran libraries get linked and the results in
missing symbols.
Link info for scipy :
[sajid@xrmlite special]$ ldd _ufuncs.cpython-36m-x86_64-linux-gnu.so
       linux-vdso.so.1 =>  (0x00007ffc81bcd000)
libmkl_rt.so =>
/home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/intel-18.0.3/intel-mkl-2018.2.199-y427ptu5mgmk34rjc4rsfhapxyf4j2fb/compilers_and_libraries/linux/mkl/lib/intel64/libmkl_rt.so
(0x00002b3909b48000)
       libpthread.so.0 => /lib64/libpthread.so.0 (0x00002b390a1e2000)
libpython3.6m.so.1.0 =>
/home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/intel-18.0.3/python-3.6.6-iick7mjya7ytfu3bbytes7w7sr6wag7d/lib/libpython3.6m.so.1.0
(0x00002b390a3fe000)
libgfortran.so.4 =>
/home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/gcc-4.8.5/gcc-7.3.0-xyzezhjmbiebkjfoakso464rhfshlkyq/lib64/libgfortran.so.4
(0x00002b390aa06000)
       libm.so.6 => /lib64/libm.so.6 (0x00002b390add9000)
libgcc_s.so.1 =>
/home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/gcc-4.8.5/gcc-7.3.0-xyzezhjmbiebkjfoakso464rhfshlkyq/lib64/libgcc_s.so.1
(0x00002b390b0db000)
libquadmath.so.0 =>
/home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/gcc-4.8.5/gcc-7.3.0-xyzezhjmbiebkjfoakso464rhfshlkyq/lib64/libquadmath.so.0
(0x00002b390b2f3000)
       libc.so.6 => /lib64/libc.so.6 (0x00002b390b532000)
       libdl.so.2 => /lib64/libdl.so.2 (0x00002b390b8f5000)
       /lib64/ld-linux-x86-64.so.2 (0x000055a4d43c2000)
       libutil.so.1 => /lib64/libutil.so.1 (0x00002b390bafa000)
libimf.so =>
/opt/intel/compilers_and_libraries_2018.3.222/linux/compiler/lib/intel64_lin/libimf.so
(0x00002b390bcfe000)
libsvml.so =>
/opt/intel/compilers_and_libraries_2018.3.222/linux/compiler/lib/intel64_lin/libsvml.so
(0x00002b390c291000)
libirng.so =>
/opt/intel/compilers_and_libraries_2018.3.222/linux/compiler/lib/intel64_lin/libirng.so
(0x00002b390db9f000)
libintlc.so.5 =>
/opt/intel/compilers_and_libraries_2018.3.222/linux/compiler/lib/intel64_lin/libintlc.so.5
(0x00002b390df14000)
~

Link info for intel-python-scipy :
[sajid@xrmlite special]$ ldd _ufuncs.cpython-36m-x86_64-linux-gnu.so
       linux-vdso.so.1 =>  (0x00007ffefbf84000)
libmkl_rt.so =>
/opt/intel/intelpython3/lib/python3.6/site-packages/scipy/special/./../../../../libmkl_rt.so
(0x00002aece4e3d000)
       libpthread.so.0 => /lib64/libpthread.so.0 (0x00002aece54e9000)
libpython3.6m.so.1.0 =>
/opt/intel/intelpython3/lib/python3.6/site-packages/scipy/special/./../../../../libpython3.6m.so.1.0
(0x00002aece5705000)
libifport.so.5 =>
/opt/intel/intelpython3/lib/python3.6/site-packages/scipy/special/./../../../../libifport.so.5
(0x00002aece5c42000)
libifcore.so.5 =>
/opt/intel/intelpython3/lib/python3.6/site-packages/scipy/special/./../../../../libifcore.so.5
(0x00002aece5e6d000)
libimf.so =>
/opt/intel/intelpython3/lib/python3.6/site-packages/scipy/special/./../../../../libimf.so
(0x00002aece61c8000)
libsvml.so =>
/opt/intel/intelpython3/lib/python3.6/site-packages/scipy/special/./../../../../libsvml.so
(0x00002aece6769000)
       libm.so.6 => /lib64/libm.so.6 (0x00002aece810c000)
libintlc.so.5 =>
/opt/intel/intelpython3/lib/python3.6/site-packages/scipy/special/./../../../../libintlc.so.5
(0x00002aece840e000)
       libc.so.6 => /lib64/libc.so.6 (0x00002aece867f000)
libgcc_s.so.1 =>
/home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/gcc-4.8.5/gcc-7.3.0-xyzezhjmbiebkjfoakso464rhfshlkyq/lib64/libgcc_s.so.1
(0x00002aece8a42000)
       libdl.so.2 => /lib64/libdl.so.2 (0x00002aece8c59000)
       /lib64/ld-linux-x86-64.so.2 (0x0000560f5adc7000)
       libutil.so.1 => /lib64/libutil.so.1 (0x00002aece8e5e000)
       librt.so.1 => /lib64/librt.so.1 (0x00002aece9061000)

Scipy/Numpy/Python version information:
1.1.0 1.14.3 sys.version_info(major=3, minor=6, micro=6,
releaselevel='final', serial=0)

As requested :

build env
build logs
build recipe (edited as per scipy docs to build and install in 1 step.)

Is this really the right build log? Note that it ends up with a build failure, so I don't think this is what produced the problematic output files you have.
The F77, F90 environment variables are not gfortran-specific, but override the compiler executable name. It thinks it's calling ifort (look at the flags to gfortran), so you should not set them to point to gfortran if the compiler is not gfortran.

Apologies for the confusion, I didn't set the compile flags correctly the first time and ended up with the broken build. Then I went back to carefully read the scipy docs and realized that it's recommended to use the -compiler arg to setup.py to specify the intel compiler. I changed the build recipe to include these and ended up being unable to build.

Works with setting the environment variable F90 to ifort. Thanks for the help!
(Would be great to add directives asking MKL_ROOT to be unset and F90 to be set for intel compilers. )

It should be also OK to leave F90 unset --- in the case above it appears it was explicitly set to gfortran.


tclgd does not work with Tcl/Tk 8.7.a5

Apply the following changes to make tclgd work with Tcl/Tk 8.7.a5:
Changed load functionality:
Change line in pkgIndex.tcl to:  package ifneeded tclgd 1.3 [list load [file join $dir tclgd13.dll] Tclgd]

Would you be able to submit the changes you had to make as a pull request?

Just change the pkgIndex.tcl.in file to:
package ifneeded tclgd @PACKAGE_VERSION@
[list load [file join $dir @PKG_LIB_FILE@] Tclgd]


how to set SPARK_WORKER_INSTANCES and Device?

Hello, i have 4 nodes, each has two GPU , enough memory and hard disk space.
So what's the good way to set the parameters (SPARK_WORKER_INSTANCES and Device), so i can use the resource more efficiently.
set 4 masters and slaves? SPARK_WORKER_INSTANCES = 4? Device =2?
ps: i've installed CaffeOnSpark(gpu version) on all of the machines.
One more question, the CUDA version has to be 7.5? can we use 8.0?
Thanks.

your config looks fine. If you compile with cuda 8.0, then you should be able to run with 8.0. Cudnn version is tricky. 5.1 works, but higher cudnn does not compile. https://github.com/BVLC/caffe/issues/5793

thanks


fix: hash_id catch wrong type.

🚀 🚀 Pull Request
Checklist:

[x]  My code follows the style guidelines of this project and the Contributing document
[x]  I have commented my code, particularly in hard-to-understand areas
[x]  I have kept the coverage-rate up
[x]  I have performed a self-review of my own code and resolved any problems
[x]  I have checked to ensure there aren't any other open Pull Requests for the same change
[x]  I have described and made corresponding changes to the relevant documentation
[x]  New and existing unit tests pass locally with my changes

Changes
.save_view()
fixes #2248

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Bernhard Conzelmann seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @drahnreb ! Thanks a lot for the proposed fix. Can you pls sign our CLA while we review the PR. Thanks again for the contribution!!

Hi @drahnreb ! Please resolve the last comment so we can merge this PR. Thanks in advance.

@tatevikh done.

Hey @drahnreb, thank you so much for the contribution. We typically send out some swag to new contributors. Do you mind joining our community (slack.activeloop.ai) so we coordinate the logistics?


Receive this error message sometimes in browser , goes away after reload.

Describe the bug
I get a wierd error message in browser and it goes away after reload.
Logs
Uncaught (in promise) TypeError: Cannot read property 'c' of undefined
at transition_out (index.mjs?v=1779436b:973)
at Object.outro [as o] (index.svelte? [sm]:72)
at transition_out (index.mjs?v=31cf6699:981)
at Object.update [as p] (root.svelte? [sm]:41)
at Object.update [as p] (root.svelte? [sm]:40)
at update_slot (index.mjs?v=31cf6699:91)
at Object.update [as p] (__layout.svelte? [sm]:29)
at Object.update [as p] (__layout.svelte? [sm]:27)
at update (index.mjs?v=31cf6699:929)
at flush (index.mjs?v=31cf6699:897)
Svelte versions
@sveltejs/kit 1.0.0-next.122
svelte 3.38.3
svelte 3.38.3

this might be related to the newest svelte update, try 3.38.2 🤔 Had similar issues

Please follow the bug reporting template. There's not enough info here to reproduce this


Please provide more information on how to install Ciphey

I've been coming back to this page trying to get Ciphey to work over and over and I'm simply not knowledgable enough to get it to work.
I downloaded a release of Ciphey, put it in a folder and put it on my desktop, then checked the installation section.
It basically tells me to run

python3 -m pip install -U ciphey

Okay, so, I downloaded python 3, restarted my pc, and the command doesn't work, turns out, I had to change it to

python -m pip install -U ciphey

Because I was upgrading from a previous version of python. Then, I kept getting:

ERROR: Could not find a version that satisfies the requirement cipheycore<0.2.0,>=0.1.4 (from ciphey) (from versions: 0.0.1, 0.1.0)
ERROR: No matching distribution found for cipheycore<0.2.0,>=0.1.4 (from ciphey)

And, of course, running

ciphey -t "encrypted text here"

won't do anything, because it didn't install correctly. So I decided to check out https://docs.ciphey.online/en/latest/ to try and understand what I was doing wrong.
The installation page there is completely different, telling me to run

$ pip3 install ciphey

Not only does CMD not run like this but it doesn't give me any links as to what pip3 comes from or what I need to run the command to begin with. Running the command returns another error

ERROR: Could not find a version that satisfies the requirement tensorflow<3.0.0,>=2.1.0 (from ciphey) (from versions: none)
ERROR: No matching distribution found for tensorflow<3.0.0,>=2.1.0 (from ciphey)

Ciphey looks amazing, but for someone like me who basically knows nothing about running python scripts and such, it's a complete maze to get working because of the lack of information. And even worse for someone who doesn't know the basics.
Just telling users to "run commands" is a bit.. hollow. For a total noob.

Hi there, thanks for reporting this issue! So many people in this situation silently give up, and then we never find out!
The main problem there is that your system is failing to install two packages, cipheycore and tensorflow. These packages are both binary packages, which have to be compiled for each version of python it supports, and so it is likely something to do with your python version.
Could you send us the output of python -c "import sys; print(sys.version)"

Also, the lack of documentation is a really big problem, and if people aren't even able to install ciphey, we REALLY need to prioritise it. Over the next week, @brandonskerritt and I will be writing a lot of docs, don't worry 🙂

output:

3.8.3 (tags/v3.8.3:6f8c832, May 13 2020, 22:20:19) [MSC v.1925 32 bit (Intel)]

Glad to hear from you guys, there's the output running the command you gave me.

Hey!
In response to your comment, I wrote an installation guide which explains what Pip and Python is and why we need them. However, I don't think it'll help you very much other than learning what Pip is :smile:
https://docs.ciphey.online/en/latest/install.html
I'm just going to copy and paste your issues, so I can more easily see them:
ERROR: Could not find a version that satisfies the requirement cipheycore<0.2.0,>=0.1.4 (from ciphey) (from versions: 0.0.1, 0.1.0)

ERROR: Could not find a version that satisfies the requirement tensorflow<3.0.0,>=2.1.0 (from ciphey) (from versions: none)

So, a quick explanation:
pip is the software used to install packages in Python, think of it as like an app store for the command line.
We tell users to run pip through Python python -m pip since users can have many versions of Python installed, and we want the main Python version. This solves a lot of headaches.
Also, since your default Python is 3.8.3, that means pip3 and python -m pip are the same command :smile_cat:
Our 'app' Ciphey, relies on other 'apps' to be downloaded through Pip.
We tell your version of pip what apps to download, through something called a requirements.txt file.
This file is just a list, like:
cipheycore
tensorflow

Your version of pip couldn't find the apps to download them. Or it could, but it could only find older versions.
Side note: pip apps are called packages, but that's kind of confusing for someone that's new to Python, as Python uses a lot of wacky terminology.
There are somethings that may have caused this.

We messed up our list of apps we want (our fault)
Your version of pip is out dated (Python's fault)
Something has happened and we don't know how to explain it (our fault, again)

The easiest solution may be to upgrade pip, so we'll try that first.
Can you please run :sparkles:
python -m pip install --upgrade pip

This tells pip to upgrade the app 'pip', which is just itself.
Then try to re-install Ciphey with:
python -m pip install -U ciphey

Since pip may be older, it may not have found the packages to install. This might fix it.
If that didn't fix it, let's go through some more things.
The 2nd reason might be that our requirements.txt has messed up. Which is our fault, sorry!
With your new upgraded version of pip, let's try to manually install the apps. Don't worry, it's not as hard as it sounds! We just ignore the requirements, and install them by hand.
This may come in handy in the future, for any Python apps that don't want to help you try to install it.
Every Python package (or app) is on PyPi.
You don't have to follow along, but I'll show you how to fix this problem in the future in case other developers aren't as nice.
CipheyCore is located here. https://pypi.org/project/cipheycore/0.1.5/. You can just search for the package name and find it.
Now click on "release history" on the left and you'll see a list:

Your error says this:

ERROR: Could not find a version that satisfies the requirement cipheycore<0.2.0,>=0.1.4 (from ciphey) (from versions: 0.0.1, 0.1.0)

So we want a version between 0.1.4 and 0.2.0.
The "rc" part of the version number means "release candidate", as in it is being tested. So we don't want that.
Let's install Cipheycore 0.1.5.
When you click on it, you'll see a command below cipheycore which tells you how to install it:

Now, we're using python and pip together. So run this command:
python -m pip install cipheycore==0.1.5

Now the 2nd issue you faced is Tensorflow. This is concerning, as Google maintains Tensorflow and if Google is having issues, that's very scary for us!
Try to install it without a specific version, such as:
python -m pip install tensorflow

If these installs don't work, try one more time with -U.
python -m pip install -U cipheycore==0.1.5

And then try to re-install Ciphey:
python -m pip install -U ciphey

Note: the install is 500mb, but the newest version of Ciphey (not yet released to the public) is ~20mb. If this puts you off, please watch the repo to find out when we release the much smaller Ciphey version :)
If these 2 things do not work, let us know! And we will dig out a Windows computer and try it ourselves :D
For @Cyclic3 For the installation blog post, I'm going to write:
python -m pip install -U ciphey==4.2.0 cipheycore==0.1.5 cipheydists==0.3.4

Since each version of the docs is now in line with the repo, we can use package pinning to specify the exact versions which may avoid issues like this in the future. I do not want to put this onto the main repo, as it is kind of a messy command. But, I will make sure it is #1 command in our trouble shooting guide :100:

I'm talking to someone else right now who has the same issue:

@Veeyu22 Please can you confirm your operating system, and your CPU. Or maybe if you're on a Raspberry Pi? Tensorflow, the package you had a problem with, isn't available for every device :(

I'm on Windows 10, running the leatest build of windows 10. My CPU is an i5-6400

Fix 1 step one:

Requirement already up-to-date: pip in c:\users\alexs\appdata\local\programs\python\python38-32\lib\site-packages (20.1.1)

Fix 1 step 2: (simply returns error as nothing has changed)

ERROR: Could not find a version that satisfies the requirement tensorflow<3.0.0,>=2.1.0 (from ciphey) (from versions: none)
ERROR: No matching distribution found for tensorflow<3.0.0,>=2.1.0 (from ciphey)

To save time, I decided to just go through all of them and only mention when something worked. All of fix 1 and two resulted in errors.
I also tried installing the wheel files directly. I did cd to the location of the file and ran a command to download it and I got this error:

C:\Users\name\Documents>pip install cipheycore-0.1.5-cp35-cp35m-win_amd64.whl
Fatal error in launcher: Unable to create process using '"c:\users\name\appdata\local\programs\python\python38-32\python.exe"  "C:\Users\name\AppData\Local\Programs\Python\Python38-32\Scripts\pip.exe" install cipheycore-0.1.5-cp35-cp35m-win_amd64.whl': The system cannot find the file specified.

After doing a bit of looking, Tensorflow or Tensorflow-gpu is supported only for 3.5.X versions of Python, so I'm going to try changing versions. I'll keep you posted.

Hey Vee,
I read that Tensorflow doesn't support 32 bit versions. I think maybe your Python install is 32 bit. although I am in bed and cannot confirm this.
Can you pretty please install Python 3.8 64 bit version?
And then:
Upgrade pip (using python 3 -m pip install --upgrade pip)
and then try to install tensorflow manually:
pytjon3 -m pip install tensorflow
We are releasing a version without tensorflow very very soon, so hopefully this problem won't persist. :)

Ah, okay, yeah the thread was outdated and I was coming here to mention that, sorry about that. Alright, I'll install a 64bit version

🤞 let's hope this fixed it! If not, we are maybe a week max away from releasing a non tensorflow version 😜

It's looking very promising.

all of this because of this button

all-contributors add @Veeyu22 for documentation and bugs

Without you mentioning this bug on our repo, we would have had many users just give up
I have tried for weeks to convince @Cyclic3 to write documentation and this has convinced him how important it is
Our first GitHub issue from someone not on the Dev team! 🎉

Your GitHub profile will be placed on the README as soon as I wake up.... 😜

@all-contributors add @Veeyu22 for documentation and bugs

Without you mentioning this bug on our repo, we would have had many users just give up
I have tried for weeks to convince @Cyclic3 to write documentation and this has convinced him how important it is
Our first GitHub issue from someone not on the Dev team! 🎉

Your GitHub profile will be placed on the README as soon as I wake up.... 😜

This seems to be sorted, thanks for the bug report!


Array: optimize shift and unshift

Revival of #8036 and more!
Fixes #5126
Fixes #10079
Closes #5148
How Array#shift used to work
Before this PR, an Array used to consist of a buffer, a size and a capacity. The buffer would have a capacity. As elements are pushed into it the size increases. Once the capacity is reached, the buffer is doubled in size. To do this, we call realloc on the buffer.
When calling shift, because we must remember the exact pointer where the buffer was allocated in order to do a realloc, the only thing we could do was to call realloc, then move all the elements "to the right":
If the array is:

  [1, 2, 3]

and we shift:

  4

we realloc:

  [1, 2, 3, _, _, _]

then we move the elements to the right:

  [_, 1, 2, 3, _, _]

then we put the new value:

  [4, 1, 2, 3, _, _]

The next time shift is called we must do the same thing again, except that, well, we don't need a realloc for a while, but we still need to copy the memory to the right.
How Array#shift is optimized
With this PR, Array now also tracks an offset to where the buffer starts. So for example:
If the array is:

  [1, 2, 3]
   ^
   buffer
   offset = 0

Initially, the buffer points to "1" and the offset to the buffer is zero.

If we shift:

  4

Then we can move the buffer (well, the point to it) to the right and remember that we have an offset of 1:

  [_, 2, 3]
      ^
      buffer
      offset = 1

This is very efficient because all we need to do is increment a couple of variables: no memory is moved.
Furthermore, if we later unshift a value, we can move the buffer to the left and decrement offset.
As explained in #8036, adding this offset to Array doesn't change its memory consumption, at least not in 64 bits platforms. And in 32 bits platforms it's just 4 more bytes per Array which isn't terrible.
How Array#unshift is optimized
This is something that wasn't done in #8036
The idea is that when we unshift an element and we have no more space left, we grow the array but leave the pointer to the buffer pointing to the middle of the buffer:
If the array is:

  [1, 2, 3]
   ^ buffer

and we unshift:

  4

Then we resize the array:

  [1, 2, 3, _, _, _]
   ^ buffer

We move the elements to the right and also the pointer to the buffer:

  [_, _, _, 1, 2, 3]
               ^
              buffer

In this way if another unshift comes we just need to move the buffer to the left. Just after 3 unshifts we'll need to reallocate and move the memory again, and then it will happen after 6 unshifts.
Also note how this is similar to push but in the other direction: when you push and there's no more space, some extra space remains on the left in case more pushes comes later on. This is exactly the same but in the other direction.
Why is this important?
I consider this change extremely important. With this, Array can be used as a list, as a queue, as a dequeue... whatever! Well, previously it could be used like that too, but it wasn't efficient in all cases. So with this, Array becomes a universal, efficient data structure. Just like in Ruby. No more fear of calling shift or unshift and thinking "Ugh, why do I have to pay this penalty?".
Benchmarks!
Shift
require "benchmark"

Benchmark.ips do |x|
  x.report("shift") do
    array = Array.new(10_000, &.itself)
    while array.shift?
    end
  end
end

I know this is allocating an array, but still, look at the times:
before  495.08 (  2.02ms) (± 3.56%)  39.1kB/op
after   40.19k ( 24.88µs) (± 0.98%)  39.1kB/op

Unshift
require "benchmark"

Benchmark.ips do |x|
  x.report("unshift") do
    array = [] of Int32
    10_000.times do |i|
      array.unshift(i)
    end
  end
end

before  535.09 (  1.87ms) (± 3.75%)  96.8kB/op  fastest
after   35.95k ( 27.81µs) (± 1.63%)  96.8kB/op  fastest

In both operations, this change leads to speed that's around 2 orders of magnitude faster.
Please
Can we have this in 1.0 pretty please? I don't mind undoing this if we later decide to go with a thread-safe Array. But until then everyone can enjoy a more efficient Array.

I believe that in the CrystalArraySyntheticProvider, the self.buffer initialization should change to self.buffer = self.valobj.child[3].

@bcardiff Where do I change that?

At https://github.com/crystal-lang/crystal/blob/master/etc/lldb/crystal_formatters.py#L14
Unfortunately, the manual specs that can be trigger by https://github.com/crystal-lang/crystal/blob/master/spec/debug/test.sh do not include a spec for Array.

(or you can change the ivars order 🤷♂ )

@bcardiff Good catch, done!
We can't change the ivars order because then the Array will occupy more space.

FYI, The linux_32 failure seems to be because of a different value of __pad1 : UShort which should not matter and has probably random date. But default struct equality compares all fields.

Thanks. We can fix that in a separate PR.

This is exciting! However, how does Deque compare now to Array? Is there still a performance benefit, or does its usefulness become limited to a more focused API?

This is a big deal.  I would love to see this particular optimization make it into the merge.  I am constantly having to refactor code that uses Array's to find different solutions than what comes most naturally.  Perhaps I'm just spoiled by Ruby's implementation of Arrays and I need to be less lazy, but old habits die hard and one great reason to use Crystal is precisely because so many Ruby concepts carry over.

However, how does Deque compare now to Array?

Good question. You can try doing some benchmarks on both data structures and see.
My guess is that Deque will be more memory efficient when used exclusively as a deque, compared to Array, but I don't know. For example rotate is more efficient in Deque. I wouldn't remove Deque from the standard library.


Set width dynamically

Not sure if its possible with css, but it would be really cool if we can set width dynamically without adding it to balloon css file.
Like so:
data-balloon-length="100px"

Sadly, as far as I know width cannot have attr() values, so it is not possible.


session-close is broken

After closing a session, the connection remains and one side still send heart-beats.

mistake of myself...


Hello, which way can i set custom cuntrols styles, or hide some controls?

How to hide, style, add, customise controll buttons? For example, now i want to hide the download button .

@againksy what URL are you playing? ReactPlayer does not provide custom controls, but allows you to render your own.

@CookPete i play from local file served by url , so i need to customise the player look styles

Playing files just uses the native browser controls.  See https://github.com/CookPete/react-player/issues/174 for more info.

To remove the download button you can use controlsList like so:
<ReactPlayer
  controls
  url='http://clips.vorwaerts-gmbh.de/big_buck_bunny.mp4'
  config={{ file: {
    attributes: {
      controlsList: 'nodownload'
    }
  }}}
/>

https://jsfiddle.net/ycq1g7rw/

Ok, thanks

@CookPete You saved my time! Thank you a lot! :-)

Thanks you
@CookPete
My attributes
<ReactPlayer config={{
     file: {
       attributes: {
         onContextMenu: e => e.preventDefault(),
         controlsList: 'nodownload'
       }
      }
    }} controls url='xx' />

config={{
file: {
attributes: {
controlsList: 'nodownload', //<- this is the important bit
},
},
}}


first look on refactoring

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
✔

Fixed issues

👍


Make great CLI help screen and arg checking.

We should probably handle --help, and --help, and --version, -v. I'm not sure if this should be handled at the bash wrapper, or the JS implementation, since usually by the time it gets to the JS implementation, its primary job is to just run the command that follows esy commandHere within the project's environment.
@kennetpostigo

There's some basic checking we need to. There's only a few basic commands like:
esy
esy install
esy build
esy add x

And if you don't supply x to add it should probably error and say what format x should take.

Awesome, I'll claim this then! I'll probably implement this with node. I'll have this done with a PR this weekend

I'm afraid CLI UI should be implemented in bash, because shell, build commands are implemened in bash. Also esy and esy CMD skip Node completely when env is ejected and cached into node_modiles/.cache.

That's a good point. I bet there are some nice bash CLI utilities we can use to make it tolerable

Hey,
I think I should learn bash and shell better to implement this. Got any resources for shell or bash to learn and any resources for building CLI UI in bash?

Mine is weak too. I think this one is just a typical argument parser in Bash. I would just end up googling something on stack overflow. In this case, the help screen is the most important part and that should be as simple as checking if the first arg is --help and then printing the text for various ways of calling esy

Alrighty! Will look into this more throughout the day

Working on it.


Developer essentials

Type of Change

[x] New feature

Description
Developer essentials tool to install few most used packages by developers
Checklist

[x] My code adheres to the coding and style guidelines of the 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 made corresponding changes to the documentation.
[x] My changes generate no errors/warnings/merge conflicts.

I think there already exist neovim script in linutil

I think there is a neovim script which already exist in linutil

moved it here.

I think there is a neovim script which already exist in linutil

didn't make a new one to clarify. it makes more sense including that script here.

I think there is a neovim script which already exist in linutil

moved it here.

No need for that leave it where it is

Love this Thanks @guruswarupa

:)


Facebook return status not updated. Return Status code :403.

In samples custom-ui and share button, when try to post a message, log returns:
02-05 13:16:39.757: I/FacebookImpl(28375): Updating status : yktjtktk
02-05 13:16:39.917: D/SocialAuthError(28375): org.brickred.socialauth.exception.SocialAuthException: org.brickred.socialauth.exception.SocialAuthException: Status not updated. Return Status code :403
02-05 13:16:39.917: D/Custom-UI(28375): Error
02-05 13:16:39.917: W/System.err(28375): org.brickred.socialauth.android.SocialAuthError: Message Not Posted
02-05 13:16:39.917: W/System.err(28375): 	at org.brickred.socialauth.android.SocialAuthAdapter$6.run(SocialAuthAdapter.java:862)
02-05 13:16:39.917: W/System.err(28375): 	at java.lang.Thread.run(Thread.java:841)

Log in is ok.
Auth app in FB is ok.
Other calls like User profile works.

Someone tell me what is the final Answer to solve this problem. I am trying it from last 4  months. Now I am tired.

After I've done everything EXACTLY as mentioned in Facebook Guide mentioned by @vineetmobile the issue disappeared.

I have resolved issue by upgrading socialauth-4.8.jar file.
Clear app data from setting and login again.

where can i download socailauth-4.8 jar file? @AnuvadiyaHiren

where can i download socailauth-4.8 jar file? @AnuvadiyaHiren

where can i download socailauth-4.8 jar file?

where can i download socailauth-4.8 jar file?

where can i download socailauth-4.8 jar file?

where can i download socailauth-4.8 jar file?

@AnuvadiyaHiren I have downloaded socialauth-4.8 jar from this link liquidtelecom.dl.sourceforge.net/project/socialauth/socialauth-java-sdk-4.8.zip .Even though it is not updating the status in my facebook wall and am getting return status code 400 sometimes and status code 403 sometimes.what may be the problem?

I get this same error in my app using socialauth 4.8. and socialauth-android 3.2
Error code:203
Please any one help??


Modal ugly animation by scrollbar disappearing

If I am in a page that have a scrollbar and I open a small modal, the scrollbar does obviously disappear, but this causes an ugly animation, because I can notice the modal moving to the right when opened and to the left when closed.
Here's a fiddle showing the problem: http://jsfiddle.net/andresespinosapc/s3fbhdhc/
Please resize the result window to the maximum possible to notice the problem in the animation with more detail, the larger the screen the more noticeable the problem is. Then click the "Open modal" button  and you will see the modal moving to the right abruptly, close the modal and you will see the opposite.
I remark that the movement is not much, but noticeable as an ugly animation effect.

Seems to be fixed with the current version, no ugly animation visible.

I think it’s a duplicate of #2061.

We fixed this in Fomantic-UI by https://github.com/fomantic/Fomantic-UI/pull/468
See https://jsfiddle.net/smudoy1k/5/


Hundreds of errors: "Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device"

I am getting hundreds of errors like this everyday:
Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>

The device (Air Purifier 3C) becomes unavailable every couple of minutes.
No connection issues, at least checking the wireless connectivity with a ping sensor.

Double-checked with latest logs, and also in the wireless router (that reports if a wireless client disconnects):
In the last 24 hours the ping sensor has failed 4 times:

Last ping sensor disconnection was at 8:09PM:

The Miot component registered in the last 24 hours 1600 errors (resetted HA logs):

The xiaomi_miot component appears to retry every 30 seconds (as per the configuration parameter).
Please find attached some logs below (marked in bold the start of a block of failures):
Log

Click to expand the log
2021-05-15 18:09:09 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:39:44 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:40:09 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:40:39 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:41:09 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:41:39 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:42:09 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:42:39 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:43:09 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:43:39 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:44:09 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:44:39 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:45:09 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:45:39 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:46:09 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:46:39 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:47:09 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:47:39 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:48:09 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:48:39 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:49:09 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:57:15 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:57:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:58:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:58:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:59:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 18:59:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:00:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:00:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:01:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:01:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:02:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:02:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:10:15 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:10:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:11:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:11:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:12:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:20:15 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:20:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:21:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:21:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:22:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:22:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:23:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:23:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:24:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:24:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:25:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:25:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:26:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:26:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:27:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:27:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:28:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:28:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:29:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:29:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:30:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:30:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:31:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:31:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:32:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:32:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:33:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:33:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:34:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:34:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:35:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:35:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:36:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:36:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:44:45 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:45:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:45:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:46:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:46:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:47:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:47:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:48:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:48:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:49:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:49:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:50:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:50:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:51:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:51:40 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:52:10 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:52:41 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:53:11 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:53:41 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 19:54:11 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 20:03:46 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 20:04:11 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 20:04:41 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 20:05:11 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 20:05:41 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 20:06:11 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 20:06:41 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 20:07:11 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 20:07:41 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 20:08:11 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 20:08:41 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 20:09:11 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 20:09:41 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 20:10:11 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 20:10:41 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 20:11:11 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 20:11:41 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>
2021-05-15 20:12:11 ERROR (MainThread) [custom_components.xiaomi_miot] Got MiioException while fetching the state for Xiaomi Miot Air Purifier: Unable to discover the device <IP_ADDRESS>

Also checked with miiocli from another computer. I have seen that not all requests are answered, when the device is "disconnected" from HA (with the wifi icon blinking fast), calling miiocli gives a similar error:
$ miiocli airpurifiermb4 --ip <IP_ADDRESS> --token (edited) info
Error: Unable to discover the device <IP_ADDRESS>
$ miiocli airpurifiermb4 --ip <IP_ADDRESS> --token (edited) info
Model: zhimi.airpurifier.mb4
Hardware version: esp32
Firmware version: 2.0.8

btw, Is there an "interface" option to specify which network interface should the component use ? (like it happens with other xiaomi related components): https://www.home-assistant.io/integrations/xiaomi_aqara/#interface

It is recommended that you enable cloud mode for this device, or integrate it through xiaomi account.

⚙ Configuration > 🧩 Integrations > Xiaomi Miot Auto > Options > ☑ Enable miot cloud

It is recommended that you enable cloud mode for this device, or integrate it through xiaomi account.

⚙ Configuration > 🧩 Integrations > Xiaomi Miot Auto > Options > ☑ Enable miot cloud

Thanks for pointing, closing the issue if this is the solution.


fields cut off, but no max length config?

 Issue by fogx
Thu Dec 16 07:21:30 2021
Originally opened as https://github.com/codelucas/newspaper/issues/925

Hi,
i'm extracting some articles and noticed that a few fields will be cut off during parse(), such as the meta_description, which seems to be limited to 130 characters. Is there a way to configure this limit? I couldn't find any setting in the config.

cannot confirm in v0.9.2


Error adding point to directory name in packed module archive

When installing from such an archive, files from such directories are not copied to the target directories.
For example

The error is not reproducible on the latest version 0.3.3-beta


[BUG] errors returned on api routes

What bug did you encounter?
visiting /api/news in the browser returns the expected data, but also the following error messages in the terminal:
[nodemon] starting `node src/app.js`
server running on PORT 8000
Error: ENOENT: no such file or directory, stat '/projects/workspace/views/not-found.html'
Error: ENOENT: no such file or directory, stat '/projects/workspace/views/not-found.html'
Error: ENOENT: no such file or directory, stat '/projects/workspace/views/not-found.html'
Error: ENOENT: no such file or directory, stat '/projects/workspace/views/not-found.html'
Error: ENOENT: no such file or directory, stat '/projects/workspace/views/not-found.html'
Error: ENOENT: no such file or directory, stat '/projects/workspace/views/not-found.html'

What did you expect to happen?
No errors as the route is working as expected.
Screenshots
All good on this end:

Additional information
The error is caused by code in ./src/server.js
...
  app.use('/api/news', apiNews);
  app.use('/api/twitter', apiTwitter);
  app.use((req, res, next) => {
    res.status(404).sendFile(path.resolve('./views/not-found.html'));
  });

  return app;
...

The above code needs to be:
...
  app.use('/api/news', apiNews);
  app.use('/api/twitter', apiTwitter);
  app.use((req, res, next) => {
    res.status(404).sendFile(path.resolve('./src/views/not-found.html'));
  });

  return app;
...

Oh, it seems like I screw up something, would you mind if I take it and try to figure out what's going on here??

Oh, it seems like I screwed up something, should it be fixed ASAP or let it for new contributors??

Don't worry about it! All it does is prove that we were right to implement a testing structure!
I would say for this one and the other two relatively easy and similar bugs, leave it and hopefully they are picked up soon by new contributors. The bug in #60 is a little more complex and maybe you'd prefer to fix that one however I think it best you take a look after these three get cleared up.

Hello there, could you assign me the issue? I'd like to contribute

Hi @SquatCub , I have to apologise because this particular issue was handled but the PR was mis-labeled and didn't close the issue. I am going to make a PR shortly and perhaps you wouldn't mind reviewing it before it is merged?
The PR will close a number of the most recent issues, but #27 is still definitely in need of attention if you'd like to take that on, let me know in the comments to assign you. Otherwise, star/watch this repo as I plan to do necessary housekeeping this week and there will be new issues raised, or get yourself familiar with the codebase and raise any issues you find.
Your input is greatly appreciated!


Feature request for grouping Systems

It would be great to have a segmentation of different server/locations on the website.
Could you split the view for servers trough the target variables?
Greetings

Thank you for your contribution!
Commit  0bdcb05 answers your feature request.


[AKS] Monitoring Addon - Improve Azure Monitor Private Link Scope Onboarding for Private clusters

Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

AKS

Could you please add a live test case for the new option?

Hi, @zhoxing-ms , @FumingZhang , can you please review this PR and also help on merging this PR?

Could you please add a live test case for the new option?

@ganga1980, will you add a live test case?

Could you please add a live test case for the new option?

@ganga1980, will you add a live test case?

@FumingZhang , added live test to cover this new option.

Queued live test to validate the change.

test_aks_create_with_private_cluster_with_monitoring_aad_auth_msi_with_ampls

Requeued new one

@FumingZhang ,  I fixed the test failure, can you please re-queue this test?

if (bool(re.match(r'/subscriptions/./resourcegroups/./providers/microsoft.insights/privateLinkscopes/.*', resource_id))) is False:

      raise InvalidArgumentValueError("--azure-monitor-private-link-scope-resource-id  not in the correct format. It should match `/subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/microsoft.insights/privateLinkscopes/<resourceName>`")

E           azure.cli.core.azclierror.InvalidArgumentValueError: --azure-monitor-private-link-scope-resource-id  not in the correct format. It should match /subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/microsoft.insights/privateLinkscopes/<resourceName>

if (bool(re.match(r'/subscriptions/./resourcegroups/./providers/microsoft.insights/privateLinkscopes/.*', resource_id))) is False:

      raise InvalidArgumentValueError("--azure-monitor-private-link-scope-resource-id  not in the correct format. It should match `/subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/microsoft.insights/privateLinkscopes/<resourceName>`")

E azure.cli.core.azclierror.InvalidArgumentValueError: --azure-monitor-private-link-scope-resource-id not in the correct format. It should match /subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/microsoft.insights/privateLinkscopes/<resourceName>

@FumingZhang , its my bad.  I see my latest commit and didnt pushed. I pushed the fix now, can you please trigger the live test now and see if this test gets passed?

Latest live test on case test_aks_create_with_private_cluster_with_monitoring_aad_auth_msi_with_ampls

Yet another live test

another live test

@ganga1980 Any update? Please note that we are launching the release for this sprint this week. Please resolve all comments by tomorrow, otherwise the release of this PR will have to be postponed to the next sprint (on 05-21)

@zhoxing-ms , can you please help on reviewing this PR, and triggering live test and  would like to get this change in May release?

Hi, @FumingZhang , @yonzhan , can one of you please help on reviewing this PR?

Since there are multiple changes in this PR, please list them respectively with corresponding commands in the History Notes section.
e.g.,
[AKS] az aks create: Add --azure-monitor-private-link-scope-resource-id optional parameter
...

Since there are multiple changes in this PR, please list them respectively with corresponding commands in the History Notes section. e.g., [AKS] az aks create: Add --azure-monitor-private-link-scope-resource-id optional parameter ...

done.

Please fix CI issues


Handle function pointers

This is a  hugely difficult task. Don't have enough time to deal with the issue in the upcoming release. Need to have a strong foundation first.


23.2.5 No RAISE NOTICE is displayed

Description
Execute the following SQL multiple times using Dbeaver
DO
$$
DECLARE

BEGIN
	RAISE NOTICE '1111';
END;
$$
;

Dbeaver <IP_ADDRESS>310221533

Dbeaver <IP_ADDRESS>311191730

DBeaver Version
<IP_ADDRESS>311191730
Operating System
Win 10
Database and driver
PostgreSQL : PostgreSQL 14.4 (Debian 14.4-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
Driver: 42.5.2
Steps to reproduce
No response
Additional context
No response

23.2.5 RAISE NOTICE Is Not Displayed

Thank you for bug report. It's a duplicate of #21902

@LiHanGod
Could you send the log files? You can find instructions here https://dbeaver.com/docs/wiki/Log-files/.

Uploading log.zip…

log.zip

Thank you


Add required/optional info to all fields in CRD reference pages

Goal
As a user, I want to understand what fields in a Keptn CRD are needed and which ones are just optional.
Details
Go through the CRD reference pages and add required/optional to all the field descriptions so that it's clear for users, what fields they need to fill out. If a field is required or not can be found from the go API *_types.go files. If a field in there is marked with omitempty, it's optional. If not, it's required.
DoD

all CRD reference pages adapted with required/optional fields

For coding of this information, I have been using:
* **<fieldname>:** (optional) -- <description>

It makes "(optional)" quite visible without obscuring the prominence of the bolded  -- just my opinion.  If you want to use a different coding, we can discuss...

I would actually go the other way and only mark things with (required) instead 🤷🏼

Fixed in https://github.com/keptn/lifecycle-toolkit/pull/2390, https://github.com/keptn/lifecycle-toolkit/pull/2356 and https://github.com/keptn/lifecycle-toolkit/pull/2388


--no-color is not available for crystal spec

I ran crystal spec --no-color but below was output.
Error: '--no-color' is not a file

I expected compiler to run specs and output result without ANSI colors.
I want --no-color because I want to run specs in Vim using vim-crystal.  Is it possible to add --no-color to crystal spec or is there any other workaround for this?

Sorry for the noob question @rhysd doesn't vim support ANSI colors?

@sdogruyol I'm sure it's not an issue of vim supporting ANSI colors, rather I think @rhysd wants to be able to parse raw spec output without having to worry about coloring characters messing with output.

@sdogruyol @k2b6s9j
Vim doesn't support ANSI color sequences directly.  As a workaround, it may be able to delete ANSI color sequence from the output. But it is not perfect because Vim can't know which color sequence is derived from compiler's output and derived from output of spec itself.
Many other subcommands have --no-color to disable ANSI color sequences, but crystal spec doesn't.  I think compiler gets more consistency by crystal spec supporting --no-color.
I looked some compiler code.  Color is controlled by instance variable @color of Compiler.  So I think it is not hard to add --no-color to crystal spec then I suggested it.  I think I can send PR for this.

I like this. You'd need to support it in the spec.cr program, and then pass it from the compiler into that subprogram, in case you want to tackle this :)

@asterite adding the logic to disable colors is easy:
diff --git a/src/spec/spec.cr b/src/spec/spec.cr
index ed5b3d4..f58639c 100644
--- a/src/spec/spec.cr
+++ b/src/spec/spec.cr
@@ -84,7 +84,11 @@ module Spec

   # :nodoc:
   def self.color(str, status)
-    str.colorize(COLORS[status])
+    if color?
+      str.colorize(COLORS[status])
+    else
+      str
+    end
   end

   # :nodoc:
@@ -109,6 +113,17 @@ module Spec
     @@aborted
   end

+  @@color = true
+
+  # :nodoc:
+  def self.color=(@@color)
+  end
+
+  # :nodoc:
+  def self.color?
+    @@color
+  end
+
   @@pattern = nil

   # :nodoc:
@@ -191,6 +206,9 @@ OptionParser.parse! do |opts|
   opts.on("--fail-fast", "abort the run on first failure") do
     Spec.fail_fast = true
   end
+  opts.on("--no-color", "disable color output") do
+    Spec.color = false
+  end
   opts.on("--help", "show this help") do |pattern|
     puts opts
     exit

But having problems to adding support to run_specs (the code is too smart for me :disappointed:)

When I run
crystal spec --no-color

I get a colored output. Here is  my crystal version:
crystal -v
Crystal 0.23.1 (2017-10-12) LLVM 4.0.1

I am on OSX 10.12.6

@martinos, please see comment here https://github.com/crystal-lang/crystal/issues/4292#issuecomment-294173988

I think crystal spec --no-color should work

Here's a screenshot:

It seems that the --no-color flag is consumed by setup_simple_compiler_options but not added to the process args for the spec runner. So the output from the compiler itself doesn't use color, but the output from the spec runner does.


⚠ ClamAV has degraded performance

In 0aa8279, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 478 ms

Resolved: ClamAV performance has improved in 5bd24e4.


Use buildkite elastic CI + Docker for faster builds

This PR adds

A docker container for running builds in an isolated context with different
ruby versions

A set of bash scripts for setting up this docker container and for easily
running rake tasks inside of the container

Initial configuration for the build matrix docker container which mirror
the ruby versions currently tested on Travis

Buildkite configuration (a pipeline definition and pre-command hook) that
replicates our build on buildkite

Using this setup should make it much quicker to test builds of rubocop-rspec.
I currently have a Buildkite's elastic-ci hooked up to a personal AWS account of mine. This setup
has a single EC2 instance always online waiting for builds. If some build activity
picks up then the elastic CI configuration will spin up as many as 10 instances
in order to satisfy the demand for build instances.
This buildkite setup is fast! Take a look at the difference:

If it isn't obvious from the picture:

Travis CI: 3 minutes 15 seconds
Buildkite: 23 seconds

So roughly 8x faster than Travis.
Travis runs one ruby build at a time per ruby version. Buildkite can afford to
run each step in parallel. Buildkite also doesn't need to download and install ruby for every build which saves a lot of time. This means I can scale up the supported rubies (or
the independent build steps) and incur almost not additional cost in build time.

That was the motivation for this PR. Here is what makes it tough:
By default each build step runs directly on the AWS instance. Therefore, if this
buildkite setup is open to outside contributors (which I would like it to be), someone
could make a PR like this
# anywhere in the codebase that is exercised by tests
system('rm -rf /')

or any other arbitrary command and this would affect the CI server permanently. This
is only one issue of course and there are plenty other malicious things people could
do. This is where the docker container comes in. Each build step is run like so:
$ build/run 2.2.5 spec

Inside the Docker container this is setting the ruby version to 2.2.5 and running
rake spec. The project directory is mounted inside of the docker container as a
read only filesystem (so the code running inside the container is not able to modify
the outside world) so the code executing inside cannot make changes to the CI server.
These commands are specified in the .buildkite/pipeline.yml file like so:
steps:
  - command: "build/run 2.2.5 spec"
    label: ":rspec: RSpec (2.2)"
    agents:
      - queue=elastic

  - command: "build/run 2.3.1 spec"
    label: ":rspec: RSpec (2.3)"
    agents:
      - queue=elastic

  - command: "build/run 2.2.5 internal_investigation"
    label: ":rubocop: RuboCop (2.2)"
    agents:
      - queue=elastic

  - command: "build/run 2.3.1 internal_investigation"
    label: ":rubocop: RubCop (2.3)"
    agents:
      - queue=elastic

  - command: "build/run 2.3.1 confirm_config"
    label: ":scroll: Configuration"
    agents:
      - queue=elastic

This docker isolation is nice and all but that alone doesn't secure the build
process. Any third party collaborator could just edit the pipeline.yml file and
add a step that does rm -rf / or whatever. Same for any of the scripts or the
dockerfile itself. To work around this, the buildkite pipeline is also configured
via the dashboard (which only I can control right now) and the first build step
is this:
gpg --keyserver pgp.mit.edu --recv 1B3C10C4

git_signature=$(git --no-pager show --quiet --pretty='%G?: %GS %GK' HEAD)
expected_signature="U: John Backus<EMAIL_ADDRESS>9A91898D0B0B2FBE"

if [[ "$git_signature" != "$expected_signature" ]]; then
  echo "Expected signature: $expected_signature"
  echo "Actual signature:   $git_signature"
  echo

  git diff --exit-code origin/master -- build .buildkite
fi

This is doing the following:

Download the PGP key I use to sign commits
Check the signature of the current HEAD commit
If the current head commit is not signed by me then fail the build if any
files were changed in the build/ or .buildkite directories

The buildkite settings then halts the build early if a commit not issued by
me altered the build steps.
With this leading check I am confident enough that a build for a 3rd party
PR can't just arbitrarily hijack an AWS box of mine :)

@dkubb flags addressed if you'd like to do another pass

@lukasmartinelli any chance you could help review this PR? This is the work that led me to hadolint :smile:

@andyw8 and @bquorning could you review also? It is fine if you aren't super familiar with bash / docker / buildkite. tl;dr is that buildkite is much faster and should allow us to add other checks to CI like jruby and mutation testing. One downside here is that buildkite doesn't yet have publicly viewable build pages so I'm going to keep travis on as a build step that 3rd party contributors can view if their build fails. Travis shouldn't be required for the build to be merged though.

The 2nd commit is named Fixup! ... and was probably intended to have been sqashed into the 1st commit :-)

@bquorning correct! You caught me fixing a tiny blemish

:+1:

Also @bquorning and @andyw8 buildkite is free for OSS so I can send you an invite so you can checkout the dashboard

@lukasmartinelli I addressed your flags. Thanks for reviewing :smile:

@bquorning did you get your buildkite invite?

@dkubb I'm going to merge this for now so that I can use the new CI setup for other PRs. I'm still waiting on getting review feedback here from the buildkite team but I think this is safe enough to use for the next few days if they don't have time to get to it immediately. If you have any other feedback I'll happily address it in a followup PR.


Aggregate logs from services

What is the expected behavior?
Aggregate logs from services.
Services (dependencies):

repository https://github.com/Qiskit-Extensions/quantum-serverless/pull/151
gateway  https://github.com/Qiskit-Extensions/quantum-serverless/pull/274

Epic https://github.com/Qiskit-Extensions/quantum-serverless/issues/174

PR #293 fixed this.


Automatical treeview arrows

I have a suggestion. I don't think it's good to create arrows one by one, so i put this code to AdminLTE.tree:

$(menu).find('.treeview-menu').parent("li").children("a").append('');

(insert the code of arrows into append, github doesn't show it)

Thank you for sharing. I will consider this approach in future releases.


Scope XBRL FERC Format Conversion

Research XBRL ecosystem, FERC's usage of XBRL, and develop a forward plan for integrating XBRL based FERC filings into PUDL.

[x] Research XBRL ecosystem, and decide on which tools to use for accessing and working with XBRL
[x] Understand the FERC XBRL taxonomy, and how to access data in XBRL filings
[x] Develop rough plan forward for how to integrate XBRL filings
[ ] Create issues to break XBRL integration into logical steps

XBRL Background
I'm far from an expert on XBRL at this point, but I think I understand the basic concepts well enough to work towards extracting relevant data. Importantly, an XBRL instance is composed of facts.  It contains a value and all information needed to interpret that value (concept, unit, time period). A taxonomy then describes relationships between facts and provides some structure to the data.
Tools
Arelle
Arelle seems to be the only particularly mature open source solution for interacting with XBRL. It was recently acquired by Workiva, and they claim it won't become proprietary. If this is true it could mean more support and consistent financial backing. Arelle provides a CLI, a GUI, and direct access through an API. No matter what method we use, it will most likely need to be scripted as Arelle is really not made for interacting with more than one filing at a time. For this reason, I think the API will probably be the most direct way to do this.
Arelle API
The API doesn't have much documentation, but digging around I think I've figured out enough to make use of it. I've figured out how to directly access the taxonomy, and the fact lists of individual filings. With access to both of these, I should be able to move forward with integrating the XBRL filings into the ETL.
Other options
There are many other tools for working with XBRL, but most of them are some combination of proprietary, targeted at helping companies doing filing, and focused on SEC data. XBRL-US seems to be the biggest player in the XBRL ecosystem, and they do provide several options for accessing FERC data, but only with a paid membership.
Integration
It seems that the easiest way to integrate new XBRL based data with the old Foxpro based  data would be to develop a method for extracting data and mapping it to the SQLlite db created by ferc1_to_sqlite. The taxonomy released for FERC form 1 very closely maps tables to the pages of the raw form, so it should be able to map this data to said SQLite db. As a starting place, I plan to try and implement this mapping for the tables currently being used by PUDL. From here we can attempt some data verification before working on the mapping for the rest of the tables.

Moving from scoping to integration


🚀 Feature: Add a new extension point to enable custom transport in the notifications-backend-module-email module.

🔖 Feature description
The notifications-backend-module-email plugin supports four types of transport (smtp, ses, sendmail, stream) for sending emails.
These transport options can be configured via app-config.yaml. However, the transport mechanism is not extensible, meaning it is not possible to use this plugin with other types of transport.
It would be beneficial for the plugin to provide an extension point that allows users to inject custom transport implementations.
🎤 Context
In my company, we use @microsoft/microsoft-graph-client to send emails. The other features of the notifications-backend-module-email plugin, such as retrieving users and broadcasting, are perfect for our needs. However, we cannot use the plugin because this transport option is not implemented.
I believe there are others with similar requirements.
✌ Possible Implementation
I would like to have an extension point that it would be something like this:
export interface NotificationEmailSender {
sendMail(options: Mail.Options)): Promise;
}
/**

@public
*/
export interface NotificationsEmailTemplateExtensionPoint {
setTemplateRenderer(renderer: NotificationTemplateRenderer): void;
setEmailSender(NotificationEmailSender): void;
}

👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

Pinging @backstage/notifications-maintainers on this one!
In general, we try to avoid making module extension points that people will commonly want to make published packages for. The reason for this is that it's a bit semantically unclear how to package up such a thing. So our hunch is, that the best outcome here may be to contribute more builtin transports in OSS, than making them pluggable.

Agreed with above. Would make either sense to create a new backend module for notifications for graph email only (basically copy from the current email module but with different send implementation) OR extend the email module to support this. Extension point on top of another extension point doesn't sound very nice.

Thanks, guys. In the end, we’re doing it just as @drodil mentioned. Once we have the implementation done, we’ll let you know in case we make a contribution. Many thx.


Save and Load Serialization.

Current, I doing test program MnistDemo.GPU but when I Load file *.json them program error.

Please help me solution.
Thanks.

I will at that when I'll be back from holidays

Serialization tests should be made generic to detect such error earlier

I have this problem. How do I fix it? I installed with nuget and I use regressionlayer. The exception seems to come from https://github.com/cbovar/ConvNetSharp/blob/f89f9649a63a924646ad2183f560849404bf89a0/src/ConvNetSharp.Core/Layers/LayerBase.cs#L101

Hi @Diapa ,
Could you try with the new nuget package (0.4.3) ?

Yes it works now thank you, but using this version GPU doesn't work. I get the same problem, but only using GPU. Additionally I get an ArgumentNullException when adding a convolutional layer to the network (only GPU version). It comes from ConvNetSharp.Volume.GPU.Single.Volume.LoadKernels().

Do you have a minimal code that reproduces this error?

Maybe there's some problem with my CUDA/cudnn installation if you don't get this problem... But I was able to run GPU version with v0.4.2.
using ConvNetSharp.Core;
using ConvNetSharp.Core.Layers;
using ConvNetSharp.Volume.GPU.Single;

namespace m
{
    class Program
    {
        static void Main(string[] args)
        {
            BuilderInstance.Volume = new VolumeBuilder();

            Net<float> net = new Net<float>();
            net.AddLayer(new InputLayer<float>(20, 20, 3));
            net.AddLayer(new ConvLayer<float>(5, 5, 48)); //System.ArgumentNullException
            /*
            System.IO.StreamReader..ctor(Stream stream, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean leaveOpen)
            System.IO.StreamReader..ctor(Stream stream)
            ConvNetSharp.Volume.GPU.KernelLoader`1.LoadKernel(String name, Stream stream)
            ConvNetSharp.Volume.GPU.Single.Volume.LoadKernels()
            ConvNetSharp.Volume.GPU.Single.VolumeBuilder.Random(Shape shape, Double mu, Double std)
            ConvNetSharp.Core.Layers.ConvLayer`1.UpdateOutputSize()
            ConvNetSharp.Core.Net`1.AddLayer(LayerBase`1 layer)
            [row 15 in this file]
            */
        }
    }
}


Reducers can not be accessed with at(0)

I'm failing to use the reducers. The following example builds but throws exception Number of arguments (1) us greater than the number of dimensions (0):
        xt::xtensor<double, 2> vImage({ 100, 100 });
        std::iota(vImage.begin(), vImage.end(), 0.0);
        const double vSum = xt::sum(vImage).at(0);

There is a working variant of accessing the member via sum(vImage)(). But I think if the expression has a dimension of 0 (scalar) it should still be fine to access it with an offset of 0?

at checks that the number of argument passed is less than the number of dimensions and that every argument is less than the corresponding dimension. So it is expected to get an exception if you pass it an argument when invoked on a 0D expression.
The correct call is at() (with no argument).

Dear @JohanMabille , I understand! Sorry for the confusion.

No problem ;)


Merge pull request #1 from sunkaixuan/master

合并

同步4.0

The current version is a perfect support for MYSQL


local class naming for exceptions

Got this message
src/zmockup_loader_switch_source.prog.abap[44, 7]     - Local class naming, expected ^LCL_.*$

On this
class lcx_error definition
  inheriting from cx_static_check ...

Is there any proper workaround except renaming the exception class ?

for now suggest allowing ^LC(X|L)_.*

indeed, maybe the fastest way. Thanks !

but there should be an option for local exception classes