No module named pyross.ContactMatrix

Hello everybody, I'm novice on github. For my trainee, I have to work on SEAIR model. So I tried to use Pyross, since this morning I struggled to install all the module now when I open Python 3.8.2 Editor and try to import pyross it gives me this.
File "C:\Python38-32\lib\pyross_init_.py", line 1, in
import pyross.contactMatrix
ModuleNotFoundError: No module named 'pyross.contactMatrix'
About the setup.py when I use the install command It gives me :
C:\Python38-32\k>python setup.py install
running install
running build
running build_py
running build_ext
running install_lib
byte-compiling C:\Python38-32\Lib\site-packages\pyross\utils.py to utils.cpython-38.pyc
File "C:\Python38-32\Lib\site-packages\pyross\utils.py", line 2
cimport numpy as np
^
SyntaxError: invalid syntax
running install_egg_info
Removing C:\Python38-32\Lib\site-packages\PyRoss-1.0.0-py3.8.egg-info
Writing C:\Python38-32\Lib\site-packages\PyRoss-1.0.0-py3.8.egg-info
Can you please guide me or if a video is available?

@Mouvoh thanks for your interest in PyRoss.
I suppose that you are trying to install PyRoss in Microsoft Windows. We are aware that the installation causes some issues in this case. Solutions are available in https://github.com/rajeshrinet/pyross/issues/14 and https://github.com/rajeshrinet/pyross/issues/3
Hope this helps!
Best, Rajesh

Thanks Sir @rajeshrinet  it works now but there is still one error : AttributeError: module 'pyross' has no attribute 'deterministic'
I do not know which file to replace now.

@Mouvoh, please can you go to the example folder? I want you to run this example and share the screenshot of the first three cells. Thanks

Okay but let me please tell you that i do not know why but the files are ipynb and unable to open in python so I copy paste the code in new file of the interpreter

This is what I get as error :
Traceback (most recent call last):
File "C:\Python38-32\examples\deterministic\SIR.py", line 30, in
model = pyross.deterministic.SIR(parameters, M, Ni)
AttributeError: module 'pyross' has no attribute 'deterministic'

Did you install it as described in #14.
Alternatively, pplease can I suggest to use binder ()
Please be patient while it loads but after that, there is no difference in running from your own computer.

Please also try again with the latest version of PyRoss.

Thank you ! I will use launch binder it's wonderful ! It works. Can you please tell me which line do I modify in the example If I want to modify for example I0. I saw Is0 = np.array([20]) does it mean there is 20 infected or is it 20% ?

It means the absolute value, ie the former you said.
Is0 = np.array([20])  ## 20 symptomatic infectives

Alright then N is equal to 10.000
Thanks you !

Re hello Sir I have a small issue on Binder sometimes it tells me that there is no module named pyross.
 about installing it on my desktop I saw you asked somebody who had the same problem to change the folder in #3 BUT where should I move the init file ?
My error is Traceback (most recent call last):
File "C:\Python38-32\pyross-master\pyross-master\pyross\test.py", line 127, in test_run_models
deterministic_models = dict(inspect.getmembers(pyross.deterministic,
AttributeError: module 'pyross' has no attribute 'deterministic' when I launch the test py

@Mouvoh I just tried binder on my phone and it works fine. The path to core is not correct in the first cell. I will fix it later today.

You do not need to move the init file. Please (a) install all requirements as defined in the project's readme. (b) Then install PyRoss and (c) run examples from the example folder. Let me know if either of (a-c) don't work.
There is only one folder from which the code will not work. This is the folder which contains setup.py. Apart from this run the codes from any folder.  Moreover you do not need to change the files or their location in core for the example to work.
Best,
Rajesh

I tried to lauch the setup.py but there is still this small problem about deterministic
Error compiling Cython file:
...
from numpy.polynomial.chebyshev import chebfit, chebval
cimport numpy as np
cimport cython
import pyross.deterministic
cimport pyross.deterministic
^
pyross\inference.pyx:11:8: 'pyross\deterministic.pxd' not found
Traceback (most recent call last):
File "C:\Users\asus\Desktop\pyross-master\pyross-master\setup.py", line 19, in
ext_modules=cythonize([ Extension("pyross/", ["pyross/.pyx"],
File "C:\Python38-32\lib\site-packages\Cython\Build\Dependencies.py", line 1102, in cythonize
cythonize_one(*args)
File "C:\Python38-32\lib\site-packages\Cython\Build\Dependencies.py", line 1225, in cythonize_one
raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: pyross\inference.pyx

It seems you don't have latest version of pyross as the core folder does not contains .pxd file. Please can you pull the latest version?

@Mouvoh it could be a windows specific problem. I will get back to you on this. For now, please use Binder!

Please can you try the following using a terminal and see if it works?

git clone https://github.com/rajeshrinet/pyross.git
cd pyross
make env
make

this is what i get

Resolved. I had to install make command. I'm now running the command

It stopped here. Is it over or ?

can you now go to examples folder and try to run the examples?

Traceback (most recent call last):
File "C:\Users\asus\Desktop\pyross\examples\deterministic\ex07-age-structured-SEIR-for-India.py", line 9, in
get_ipython().run_cell_magic('capture', '', "## compile PyRoss for this notebook\nimport os\nowd = os.getcwd()\nos.chdir('../')\n%run setup.py install\nos.chdir(owd)")
NameError: name 'get_ipython' is not defined
I GET This

By the way can i close the command window ?

Yes, you can close the command window. Also, you do not need to run the first cell (it can be commented).
Can you see if you can now import in the second cell?

Traceback (most recent call last):
File "C:\Users\asus\Desktop\pyross\examples\deterministic\ex07-age-structured-SEIR-for-India.py", line 33, in
CH, CW, CS, CO = pyross.contactMatrix.India()
AttributeError: module 'pyross' has no attribute 'contactMatrix'
From there's no module named it is now no attribute lol

I will need to look into this. Unfortunately, I do not have a windows machine at hand to check it out myself. I will get back to you on this...

I deal with with launch binder AND WONDERING what if I install a virtual Linux to run pyross ?
But can you please tell me about covid cases data for other countries ?

Yes. That is a possibility apart from running Binder. I do not know a systematic way to get covid cases for any country. I do it case-by-case.

May I know how do you ?

See here: https://github.com/owid/covid-19-data/tree/master/public/data
UBUNTU should be fine.

Since the beginning I open issues hahah I'm glad to purpose a solution about the data now

From https://github.com/owid/covid-19-data/tree/master/public/data

Download the .csv file
Open with excel
Select the first column then in the Data button of excel, select convert , delimit Next use as delimiter the comma.
Now you have all well presented. If you want  a special covid cases select the country and the lines corresponding copy paste in a new excel file then delete the other columns except the first and the second. Choose  save as txt file now we have the country Case.
Sir @rajeshrinet I have already rearrange the file as said. Hope this will be helpful
owid-covid-data.xlsx

Thanks @Mouvoh. Since the data is very dynamic it will be very useful to use the instructions in your last comment.

Thanks
I'm currently installing a virtual machine for use ubuntu. When done the installing process for pyross is it the same with the command invite ?

https://github.com/rajeshrinet/pyross#installation
Please use either of the two possibilities. Both should work. Please be sure to install all dependencies for the latter.

I'm now on Linux I installed All requirement except odespy where they said could not find a version that meets requirements but you said it is optional.
I get this error :
kazuki@kazuki:~$ git clone https://github.com/rajeshrinet/pyross.git
Clonage dans 'pyross'...
remote: Enumerating objects: 137, done.
remote: Counting objects: 100% (137/137), done.
remote: Compressing objects: 100% (102/102), done.
remote: Total 3266 (delta 83), reused 72 (delta 35), pack-reused 3129
Réception d'objets: 100% (3266/3266), 68.05 Mio | 913.00 Kio/s, fait.
Résolution des deltas: 100% (2078/2078), fait.
kazuki@kazuki:~$ cd pyross
kazuki@kazuki:~/pyross$ make env
creating conda environment...
conda env create --file environment.yml
make: conda: Command not found
make: *** [Makefile:18: env] Error 127
kazuki@kazuki:~/pyross$ make
Installing pyross...
python setup.py install
make: python: Command not found
make: *** [Makefile:6: make] Error 127

home/kazuki/anaconda3/lib/python3.7/site-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:17:2: warning: #warning "Using deprecated NumPy API, disable it with " "#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
   17 | #warning "Using deprecated NumPy API, disable it with " \
      |  ^~~~~~~
gcc -pthread -shared -B /home/kazuki/anaconda3/compiler_compat -L/home/kazuki/anaconda3/lib -Wl,-rpath=/home/kazuki/anaconda3/lib -Wl,--no-as-needed -Wl,--sysroot=/ build/temp.linux-x86_64-3.7/pyross/control.o -o build/lib.linux-x86_64-3.7/pyross/control.cpython-37m-x86_64-linux-gnu.so
building 'pyross.deterministic' extension
gcc -pthread -B /home/kazuki/anaconda3/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/kazuki/anaconda3/lib/python3.7/site-packages/numpy/core/include -I/home/kazuki/anaconda3/include/python3.7m -c pyross/deterministic.c -o build/temp.linux-x86_64-3.7/pyross/deterministic.o
In file included from /home/kazuki/anaconda3/lib/python3.7/site-packages/numpy/core/include/numpy/ndarraytypes.h:1832,
                 from /home/kazuki/anaconda3/lib/python3.7/site-packages/numpy/core/include/numpy/ndarrayobject.h:12,
                 from /home/kazuki/anaconda3/lib/python3.7/site-packages/numpy/core/include/numpy/arrayobject.h:4,
                 from pyross/deterministic.c:619:

and what i get from the setup.py

(base) kazuki@kazuki:~/pyross$ make env
creating conda environment...
conda env create --file environment.yml

CondaValueError: prefix already exists: /home/kazuki/anaconda3/envs/pyross

make: *** [Makefile:18: env] Error 1
(base) kazuki@kazuki:~/pyross$ make
Installing pyross...
python setup.py install
running install
running build
running build_py
running build_ext
running install_lib
running install_egg_info
Removing /home/kazuki/anaconda3/lib/python3.7/site-packages/PyRoss-1.0.0-py3.7.egg-info
Writing /home/kazuki/anaconda3/lib/python3.7/site-packages/PyRoss-1.0.0-py3.7.egg-info
adding githook...
cp .githooks/pre-push .git/hooks/
chmod +x .git/hooks/pre-push
(base) kazuki@kazuki:~/pyross$ make test
testing pyross...
cd ~ && python -m unittest pyross.test
E
======================================================================
ERROR: pyross (unittest.loader._FailedTest)
----------------------------------------------------------------------
ImportError: Failed to import test module: pyross
Traceback (most recent call last):
  File "/home/kazuki/anaconda3/lib/python3.7/unittest/loader.py", line 154, in loadTestsFromName
    module = __import__(module_name)
  File "/home/kazuki/anaconda3/lib/python3.7/site-packages/pyross/__init__.py", line 6, in <module>
    import pyross.inference
  File "pyross/inference.pyx", line 14, in init pyross.inference
  File "/home/kazuki/anaconda3/lib/python3.7/site-packages/pyross/utils_python.py", line 6, in <module>
    import nlopt
ModuleNotFoundError: No module named 'nlopt'

----------------------------------------------------------------------
Ran 1 test in 0.000s

FAILED (errors=1)
make: *** [Makefile:24: test] Error 1

Hello Right now I am on linux I followed all the steps I even saw make env install nlopt but it said there is no module named nlopt when i run the test python. As i don't master linux can you tell me what to do please

Here is what i get from the notebook

I had installed nlopt even before the make env where i saw its installation I'm despaired now I tried everything

@Mouvoh please can you try the following

Download and install anaconda from https://www.anaconda.com/products/individual

Put anaconda in the path and make it your default python. https://askubuntu.com/questions/886983/how-to-set-anaconda-as-a-default-python

Follow the steps

(base) kazuki@kazuki:~/pyross$ make env
creating conda environment...
conda env create --file environment.yml
CondaValueError: prefix already exists: /home/kazuki/anaconda3/envs/pyross
make: *** [Makefile:18: env] Error 1
(base) kazuki@kazuki:~/pyross$ make
Installing pyross...
python setup.py install
running install
running build
running build_py
running build_ext
running install_lib
running install_egg_info
Removing /home/kazuki/anaconda3/lib/python3.7/site-packages/PyRoss-1.0.0-py3.7.egg-info
Writing /home/kazuki/anaconda3/lib/python3.7/site-packages/PyRoss-1.0.0-py3.7.egg-info
adding githook...
cp .githooks/pre-push .git/hooks/
chmod +x .git/hooks/pre-push
(base) kazuki@kazuki:~/pyross$ make test
testing pyross...
cd ~ && python -m unittest pyross.test
E
ERROR: pyross (unittest.loader._FailedTest)
ImportError: Failed to import test module: pyross
Traceback (most recent call last):
File "/home/kazuki/anaconda3/lib/python3.7/unittest/loader.py", line 154, in loadTestsFromName
module = import(module_name)
File "/home/kazuki/anaconda3/lib/python3.7/site-packages/pyross/init.py", line 6, in
import pyross.inference
File "pyross/inference.pyx", line 14, in init pyross.inference
File "/home/kazuki/anaconda3/lib/python3.7/site-packages/pyross/utils_python.py", line 6, in
import nlopt
ModuleNotFoundError: No module named 'nlopt'

Ran 1 test in 0.000s
FAILED (errors=1)
make: *** [Makefile:24: test] Error 1

Alternatively, please can you just run
python setup.py install instead of make?
Thanks

import nlopt

ModuleNotFoundError: No module named 'nlopt'

You need to activate the environment to use the installation:
conda activate pyross

Install instructions have been updated. It seems conda activate <env> needs to be run outside of the makefile in order to successfully activate the envrionment.

(base) kazuki@kazuki:~/pyross$ python setup.py install
running install
running build
running build_py
running build_ext
running install_lib
running install_egg_info
Removing /home/kazuki/anaconda3/lib/python3.7/site-packages/PyRoss-1.0.0-py3.7.egg-info
Writing /home/kazuki/anaconda3/lib/python3.7/site-packages/PyRoss-1.0.0-py3.7.egg-info
(base) kazuki@kazuki:~/pyross$ conda activate pyross
(pyross) kazuki@kazuki:~/pyross$ python setup.py install
running install
running build
running build_py
creating build/lib.linux-x86_64-3.8
creating build/lib.linux-x86_64-3.8/pyross
copying pyross/init.py -> build/lib.linux-x86_64-3.8/pyross
copying pyross/utils_python.py -> build/lib.linux-x86_64-3.8/pyross
copying pyross/test.py -> build/lib.linux-x86_64-3.8/pyross
copying pyross/deterministic.pxd -> build/lib.linux-x86_64-3.8/pyross
running build_ext
building 'pyross.contactMatrix' extension
creating build/temp.linux-x86_64-3.8
creating build/temp.linux-x86_64-3.8/pyross
gcc -pthread -B /home/kazuki/anaconda3/envs/pyross/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include -I/home/kazuki/anaconda3/envs/pyross/include/python3.8 -c pyross/contactMatrix.c -o build/temp.linux-x86_64-3.8/pyross/contactMatrix.o
In file included from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/ndarraytypes.h:1832,
from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/ndarrayobject.h:12,
from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/arrayobject.h:4,
from pyross/contactMatrix.c:619:
/home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:17:2: warning: #warning "Using deprecated NumPy API, disable it with " "#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
17 | #warning "Using deprecated NumPy API, disable it with "
|  ^~~~~~~
gcc -pthread -shared -B /home/kazuki/anaconda3/envs/pyross/compiler_compat -L/home/kazuki/anaconda3/envs/pyross/lib -Wl,-rpath=/home/kazuki/anaconda3/envs/pyross/lib -Wl,--no-as-needed -Wl,--sysroot=/ build/temp.linux-x86_64-3.8/pyross/contactMatrix.o -o build/lib.linux-x86_64-3.8/pyross/contactMatrix.cpython-38-x86_64-linux-gnu.so
building 'pyross.control' extension
gcc -pthread -B /home/kazuki/anaconda3/envs/pyross/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include -I/home/kazuki/anaconda3/envs/pyross/include/python3.8 -c pyross/control.c -o build/temp.linux-x86_64-3.8/pyross/control.o
In file included from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/ndarraytypes.h:1832,
from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/ndarrayobject.h:12,
from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/arrayobject.h:4,
from pyross/control.c:619:
/home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:17:2: warning: #warning "Using deprecated NumPy API, disable it with " "#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
17 | #warning "Using deprecated NumPy API, disable it with "
|  ^~~~~~~
make test
^[[B^[[Agcc -pthread -shared -B /home/kazuki/anaconda3/envs/pyross/compiler_compat -L/home/kazuki/anaconda3/envs/pyross/lib -Wl,-rpath=/home/kazuki/anaconda3/envs/pyross/lib -Wl,--no-as-needed -Wl,--sysroot=/ build/temp.linux-x86_64-3.8/pyross/control.o -o build/lib.linux-x86_64-3.8/pyross/control.cpython-38-x86_64-linux-gnu.so
building 'pyross.deterministic' extension
gcc -pthread -B /home/kazuki/anaconda3/envs/pyross/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include -I/home/kazuki/anaconda3/envs/pyross/include/python3.8 -c pyross/deterministic.c -o build/temp.linux-x86_64-3.8/pyross/deterministic.o
In file included from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/ndarraytypes.h:1832,
from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/ndarrayobject.h:12,
from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/arrayobject.h:4,
from pyross/deterministic.c:619:
/home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:17:2: warning: #warning "Using deprecated NumPy API, disable it with " "#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
17 | #warning "Using deprecated NumPy API, disable it with "
|  ^~~~~~~
gcc -pthread -shared -B /home/kazuki/anaconda3/envs/pyross/compiler_compat -L/home/kazuki/anaconda3/envs/pyross/lib -Wl,-rpath=/home/kazuki/anaconda3/envs/pyross/lib -Wl,--no-as-needed -Wl,--sysroot=/ build/temp.linux-x86_64-3.8/pyross/deterministic.o -o build/lib.linux-x86_64-3.8/pyross/deterministic.cpython-38-x86_64-linux-gnu.so
building 'pyross.forecast' extension
gcc -pthread -B /home/kazuki/anaconda3/envs/pyross/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include -I/home/kazuki/anaconda3/envs/pyross/include/python3.8 -c pyross/forecast.c -o build/temp.linux-x86_64-3.8/pyross/forecast.o
In file included from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/ndarraytypes.h:1832,
from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/ndarrayobject.h:12,
from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/arrayobject.h:4,
from pyross/forecast.c:620:
/home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:17:2: warning: #warning "Using deprecated NumPy API, disable it with " "#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
17 | #warning "Using deprecated NumPy API, disable it with "
|  ^~~~~~~
gcc -pthread -shared -B /home/kazuki/anaconda3/envs/pyross/compiler_compat -L/home/kazuki/anaconda3/envs/pyross/lib -Wl,-rpath=/home/kazuki/anaconda3/envs/pyross/lib -Wl,--no-as-needed -Wl,--sysroot=/ build/temp.linux-x86_64-3.8/pyross/forecast.o -o build/lib.linux-x86_64-3.8/pyross/forecast.cpython-38-x86_64-linux-gnu.so
building 'pyross.hybrid' extension
gcc -pthread -B /home/kazuki/anaconda3/envs/pyross/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include -I/home/kazuki/anaconda3/envs/pyross/include/python3.8 -c pyross/hybrid.c -o build/temp.linux-x86_64-3.8/pyross/hybrid.o
In file included from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/ndarraytypes.h:1832,
from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/ndarrayobject.h:12,
from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/arrayobject.h:4,
from pyross/hybrid.c:619:
/home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:17:2: warning: #warning "Using deprecated NumPy API, disable it with " "#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
17 | #warning "Using deprecated NumPy API, disable it with "
|  ^~~~~~~
gcc -pthread -shared -B /home/kazuki/anaconda3/envs/pyross/compiler_compat -L/home/kazuki/anaconda3/envs/pyross/lib -Wl,-rpath=/home/kazuki/anaconda3/envs/pyross/lib -Wl,--no-as-needed -Wl,--sysroot=/ build/temp.linux-x86_64-3.8/pyross/hybrid.o -o build/lib.linux-x86_64-3.8/pyross/hybrid.cpython-38-x86_64-linux-gnu.so
building 'pyross.inference' extension
gcc -pthread -B /home/kazuki/anaconda3/envs/pyross/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include -I/home/kazuki/anaconda3/envs/pyross/include/python3.8 -c pyross/inference.c -o build/temp.linux-x86_64-3.8/pyross/inference.o
In file included from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/ndarraytypes.h:1832,
from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/ndarrayobject.h:12,
from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/arrayobject.h:4,
from pyross/inference.c:619:
/home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:17:2: warning: #warning "Using deprecated NumPy API, disable it with " "#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
17 | #warning "Using deprecated NumPy API, disable it with "
|  ^~~~~~~
gcc -pthread -shared -B /home/kazuki/anaconda3/envs/pyross/compiler_compat -L/home/kazuki/anaconda3/envs/pyross/lib -Wl,-rpath=/home/kazuki/anaconda3/envs/pyross/lib -Wl,--no-as-needed -Wl,--sysroot=/ build/temp.linux-x86_64-3.8/pyross/inference.o -o build/lib.linux-x86_64-3.8/pyross/inference.cpython-38-x86_64-linux-gnu.so
building 'pyross.stochastic' extension
gcc -pthread -B /home/kazuki/anaconda3/envs/pyross/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include -I/home/kazuki/anaconda3/envs/pyross/include/python3.8 -c pyross/stochastic.c -o build/temp.linux-x86_64-3.8/pyross/stochastic.o
In file included from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/ndarraytypes.h:1832,
from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/ndarrayobject.h:12,
from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/arrayobject.h:4,
from pyross/stochastic.c:620:
/home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:17:2: warning: #warning "Using deprecated NumPy API, disable it with " "#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
17 | #warning "Using deprecated NumPy API, disable it with "
|  ^~~~~~~
pyross/stochastic.c: In function ‘__pyx_f_6pyross_10stochastic_22stochastic_integration_simulate_tau_leaping_events’:
pyross/stochastic.c:11966:20: warning: ‘__pyx_v_cur_tau’ may be used uninitialized in this function [-Wmaybe-uninitialized]
11966 |       __pyx_t_9 = ((struct __pyx_vtabstruct_6pyross_10stochastic_stochastic_integration *)__pyx_v_self->__pyx_vtab)->tau_leaping_update_state(__pyx_v_self, __pyx_v_cur_tau); if (unlikely(!__pyx_t_9)) __PYX_ERR(0, 766, __pyx_L1_error)
|                   ~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
pyross/stochastic.c: In function ‘__pyx_f_6pyross_10stochastic_22stochastic_integration_simulate_tau_leaping’:
pyross/stochastic.c:10200:20: warning: ‘__pyx_v_cur_tau’ may be used uninitialized in this function [-Wmaybe-uninitialized]
10200 |       __pyx_t_1 = ((struct __pyx_vtabstruct_6pyross_10stochastic_stochastic_integration *)__pyx_v_self->__pyx_vtab)->tau_leaping_update_state(__pyx_v_self, __pyx_v_cur_tau); if (unlikely(!__pyx_t_1)) __PYX_ERR(0, 628, __pyx_L1_error)
|                   ~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
gcc -pthread -shared -B /home/kazuki/anaconda3/envs/pyross/compiler_compat -L/home/kazuki/anaconda3/envs/pyross/lib -Wl,-rpath=/home/kazuki/anaconda3/envs/pyross/lib -Wl,--no-as-needed -Wl,--sysroot=/ build/temp.linux-x86_64-3.8/pyross/stochastic.o -o build/lib.linux-x86_64-3.8/pyross/stochastic.cpython-38-x86_64-linux-gnu.so
building 'pyross.utils' extension
gcc -pthread -B /home/kazuki/anaconda3/envs/pyross/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include -I/home/kazuki/anaconda3/envs/pyross/include/python3.8 -c pyross/utils.c -o build/temp.linux-x86_64-3.8/pyross/utils.o
In file included from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/ndarraytypes.h:1832,
from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/ndarrayobject.h:12,
from /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/arrayobject.h:4,
from pyross/utils.c:619:
/home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:17:2: warning: #warning "Using deprecated NumPy API, disable it with " "#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
17 | #warning "Using deprecated NumPy API, disable it with "
|  ^~~~~~~
gcc -pthread -shared -B /home/kazuki/anaconda3/envs/pyross/compiler_compat -L/home/kazuki/anaconda3/envs/pyross/lib -Wl,-rpath=/home/kazuki/anaconda3/envs/pyross/lib -Wl,--no-as-needed -Wl,--sysroot=/ build/temp.linux-x86_64-3.8/pyross/utils.o -o build/lib.linux-x86_64-3.8/pyross/utils.cpython-38-x86_64-linux-gnu.so
running install_lib
creating /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/pyross
copying build/lib.linux-x86_64-3.8/pyross/forecast.cpython-38-x86_64-linux-gnu.so -> /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/pyross
copying build/lib.linux-x86_64-3.8/pyross/init.py -> /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/pyross
copying build/lib.linux-x86_64-3.8/pyross/utils.cpython-38-x86_64-linux-gnu.so -> /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/pyross
copying build/lib.linux-x86_64-3.8/pyross/deterministic.cpython-38-x86_64-linux-gnu.so -> /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/pyross
copying build/lib.linux-x86_64-3.8/pyross/deterministic.pxd -> /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/pyross
copying build/lib.linux-x86_64-3.8/pyross/hybrid.cpython-38-x86_64-linux-gnu.so -> /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/pyross
copying build/lib.linux-x86_64-3.8/pyross/control.cpython-38-x86_64-linux-gnu.so -> /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/pyross
copying build/lib.linux-x86_64-3.8/pyross/stochastic.cpython-38-x86_64-linux-gnu.so -> /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/pyross
copying build/lib.linux-x86_64-3.8/pyross/contactMatrix.cpython-38-x86_64-linux-gnu.so -> /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/pyross
copying build/lib.linux-x86_64-3.8/pyross/utils_python.py -> /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/pyross
copying build/lib.linux-x86_64-3.8/pyross/test.py -> /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/pyross
copying build/lib.linux-x86_64-3.8/pyross/inference.cpython-38-x86_64-linux-gnu.so -> /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/pyross
byte-compiling /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/pyross/init.py to init.cpython-38.pyc
byte-compiling /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/pyross/utils_python.py to utils_python.cpython-38.pyc
byte-compiling /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/pyross/test.py to test.cpython-38.pyc
running install_egg_info
Writing /home/kazuki/anaconda3/envs/pyross/lib/python3.8/site-packages/PyRoss-1.0.0-py3.8.egg-info
(pyross) kazuki@kazuki:~/pyross$ make test
testing pyross...
cd ~ && python -m unittest pyross.test
....odespy is not installed, skipping...
odespy-rkf45 is not installed, skipping...
odespy-rk4 is not installed, skipping...
.......
Ran 11 tests in 4.270s
OK
(pyross) kazuki@kazuki:~/pyross$ make test
testing pyross...
cd ~ && python -m unittest pyross.test
....odespy is not installed, skipping...
odespy-rkf45 is not installed, skipping...
odespy-rk4 is not installed, skipping...
.......
Ran 11 tests in 3.915s
OK
(pyross) kazuki@kazuki:~/pyross$

Finally the test returned ok now I amafraid to close lol. What should I do right now please

you need to activate the environment every time using conda activate pyross. Now you can go to examples folder and launch Jupyter
jupyter notebook

THnaks Sir It does work ! ShoulD i ALWAYS run setup.py or just conda activate pyross

Please activate the environment every time you open the terminal for a new session using:
conda activate pyross

shoul I activate into the terminal of the folder outside ?

You need to do it for every session before launching Jupyter using jupyter notebook. It is better to do it from the same folder, but it should not make a difference. Here, a session means when you open a terminal. The session ends when you close the terminal.

Please in the The readme of datayou said  file for India has four columns: days since the first case, recovered cases and mortality, date, the cumulative number of infected individuals to date.
What do you mean by recovered case and mortality ? You meant the difference between recoverd case and mortality  ? Just let me know which column of the https://github.com/rajeshrinet/pyross/files/4599173/owid-covid-data.xlsx it is please

In the SIR model: R is removed, that is, the population which is neither susceptible nor infected. Since both recovered and mortality satisfy this criteria, they jointly belong to this class. So you need to subtract both of these from cumulative number of infected to match with Is in the SIR model. Please do the same for your data file. Hope this is helpful.

Very Helpful Thanks. But in the https://github.com/rajeshrinet/pyross/files/4599173/owid-covid-data.xlsx there is not recovered colum. Is it available somewhere else than there ? How did you do please ?

Can you please tell me where did you obtain recovered cases ?


New API

Addresses: #12 and #9

Coverage increased (+7.3%) to 75.439% when pulling 38fe10710d2b20364b0bbbd8c769d8258c5252e0 on issue-12-new-api into f5bd8836bb455001a57d64f50e0409e93eacbf1a on master.

Coverage increased (+1.2%) to 69.355% when pulling 72ef5b7170204d7899f694d2a40ab5ca811cf01c on issue-12-new-api into f5bd8836bb455001a57d64f50e0409e93eacbf1a on master.

Coverage decreased (-2.03%) to 66.154% when pulling 4aaa9de48c1935c08f4e5da56779d993c8e466c5 on issue-12-new-api into f5bd8836bb455001a57d64f50e0409e93eacbf1a on master.

Coverage decreased (-2.5%) to 65.672% when pulling 306cb712eee3b72c3605e23f903e1319b98e71c6 on issue-12-new-api into f5bd8836bb455001a57d64f50e0409e93eacbf1a on master.

Coverage increased (+3.9%) to 72.059% when pulling 35f826be0ec2ec0d5884b991c3f232d5534698e9 on issue-12-new-api into f5bd8836bb455001a57d64f50e0409e93eacbf1a on master.

Coverage increased (+3.9%) to 72.059% when pulling<PHONE_NUMBER>660ba07eb44a138a6dff44aac17969 on issue-12-new-api into f5bd8836bb455001a57d64f50e0409e93eacbf1a on master.

Coverage increased (+8.4%) to 76.563% when pulling 89b790847374b7077ba4a82e001206e95d1c52b3 on issue-12-new-api into f5bd8836bb455001a57d64f50e0409e93eacbf1a on master.

Coverage increased (+8.4%) to 76.563% when pulling 2fa7a52ffdeeff3e13216706fa037b74a77af6a2 on issue-12-new-api into f5bd8836bb455001a57d64f50e0409e93eacbf1a on master.

Coverage increased (+8.4%) to 76.563% when pulling 5df229a5881a0f6a2ced35eb860c742374dae7ed on issue-12-new-api into f5bd8836bb455001a57d64f50e0409e93eacbf1a on master.

Coverage increased (+8.4%) to 76.563% when pulling 3ccd08d9f7bb52270d0435c15767d0a320438131 on issue-12-new-api into f5bd8836bb455001a57d64f50e0409e93eacbf1a on master.

@ShaneKilkelly congrats!


Is V2 ready for use?

I wonder if the branch is ready for use or if not then when?

Not yet, probably within the next month or so.


Feedback

Hi @ThorbenSpankas,
Please can you resolve the compilation error with your contract? - See attached - error relates to priceorakle,.sol
Once you have resolved and tested your changes please resubmit ASAP.
Thank you
Amma

Hi,
sorry for the issue. Hope all is working now. The compilation at least
works. For the test, it remains a problem that my internet is to
unstable to check (see screencast) if you have the same issue you
might need to try several times. The problem is that some of the test
require orakle data from chainlink so test need to be done on rinkeby.
Please let me know if I can help with anything else.
Best,
Thorben
https://github.com/ThorbenSpankas/blockchain-developer-bootcamp-final-project
Quoting abakus00 @.***>:

Hi @ThorbenSpankas,
Please can you resolve the compilation error with your contract? -
See attached - error relates to priceorakle,.sol
Once you have resolved and tested your changes please resubmit ASAP.
Thank you
Amm

a
--
Reply to this email directly or view it on GitHub:
https://github.com/ThorbenSpankas/blockchain-developer-bootcamp-final-project/issues/1
You are receiving this because you were mentioned.
Message ID:
@.***>


[ALS-5244] Add phenotype copy functionality to package data modal.

Updates package dataset modal copy.
Propagates dataset save modal name validation from core.

Reviewed in office hours Nov 6, 2023.


chef verify fails on windows ("Verification of component 'chefspec' failed.")

Hi everybody,
I'm currently upgrading to ChefDK 0.3.6 in my windows based dev environment. As part of the tests I'm also running chef verify, which now fails with "Verification of component 'chefspec' failed."
This is all I got from running chef verify --verbose:
C:\Repos\_github\bills-kitchen\target\build>chef verify --verbose
Running verification for component 'berkshelf'
Running verification for component 'test-kitchen'
Running verification for component 'chef-client'
Running verification for component 'chef-dk'
Running verification for component 'chefspec'
Running verification for component 'rubocop'
Running verification for component 'fauxhai'
Running verification for component 'knife-spork'
Running verification for component 'kitchen-vagrant'
Running verification for component 'package installation'
....

The system cannot find the path specified.

...

....
Inspecting 1 file
.

1 file inspected, no offenses detected

.................................
Compiling Cookbooks...
Recipe: code_generator::cookbook
  * directory[C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example] action create
    - create new directory C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example
  * template[C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/metadata.rb] action create_if_missing
    - create new file C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/metadata.rb
    - update content in file C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/metadata.rb from none to 283e7e
    (diff output suppressed by config)
  * template[C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/README.md] action create_if_missing
    - create new file C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/README.md
    - update content in file C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/README.md from none to 3659e2
    (diff output suppressed by config)
  * cookbook_file[C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/chefignore] action create
    - create new file C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/chefignore
    - update content in file C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/chefignore from none to 44d134
    (diff output suppressed by config)
  * cookbook_file[C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/Berksfile] action create_if_missing
    - create new file C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/Berksfile
    - update content in file C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/Berksfile from none to 4e4c91
    (diff output suppressed by config)
  * template[C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/.kitchen.yml] action create_if_missing
    - create new file C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/.kitchen.yml
    - update content in file C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/.kitchen.yml from none to a6d259
    (diff output suppressed by config)
  * directory[C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/test/integration/default/serverspec] action create
    - create new directory C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/test/integration/default/serverspec
  * cookbook_file[C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/test/integration/default/serverspec/spec_helper.rb] action create_if_missing
    - create new file C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/test/integration/default/serverspec/spec_helper.rb
    - update content in file C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/test/integration/default/serverspec/spec_helper.rb from none to 93910b
    (diff output suppressed by config)
  * template[C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/test/integration/default/serverspec/default_spec.rb] action create_if_missing
    - create new file C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/test/integration/default/serverspec/default_spec.rb
    - update content in file C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/test/integration/default/serverspec/default_spec.rb from none to d9e254
    (diff output suppressed by config)
  * directory[C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/spec/unit/recipes] action create
    - create new directory C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/spec/unit/recipes
  * cookbook_file[C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/spec/spec_helper.rb] action create_if_missing
    - create new file C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/spec/spec_helper.rb
    - update content in file C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/spec/spec_helper.rb from none to 587075
    (diff output suppressed by config)
  * template[C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/spec/unit/recipes/default_spec.rb] action create_if_missing
    - create new file C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/spec/unit/recipes/default_spec.rb
    - update content in file C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/spec/unit/recipes/default_spec.rb from none to 94d095
    (diff output suppressed by config)
  * directory[C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/recipes] action create
    - create new directory C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/recipes
  * template[C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/recipes/default.rb] action create_if_missing
    - create new file C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/recipes/default.rb
    - update content in file C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/recipes/default.rb from none to c73dcf
    (diff output suppressed by config)
  * execute[initialize-git] action run
    - execute git init .
  * cookbook_file[C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/.gitignore] action create
    - create new file C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/.gitignore
    - update content in file C:/Users/tkn/AppData/Local/Temp/d20150121-157284-1txnmiq/example/.gitignore from none to 33d469
    (diff output suppressed by config)

Config Hash:
{}

Plugins:
KnifeSpork::Plugins::Campfire: disabled
KnifeSpork::Plugins::Eventinator: disabled
KnifeSpork::Plugins::Foodcritic: disabled
KnifeSpork::Plugins::Git: disabled
KnifeSpork::Plugins::Graphite: disabled
KnifeSpork::Plugins::Grove: disabled
KnifeSpork::Plugins::HipChat: disabled
KnifeSpork::Plugins::Irccat: disabled
KnifeSpork::Plugins::Jabber: disabled
KnifeSpork::Plugins::Rubocop: disabled
KnifeSpork::Plugins::Slack: disabled
KnifeSpork::Plugins::StatusNet: disabled

WARNING: No knife configuration file found

Resolving cookbook dependencies...

[2015-01-21T23:06:23+01:00] INFO: Run List is []
[2015-01-21T23:06:23+01:00] INFO: Run List expands to []

kitchen-vagrant (0.15.0)

      create  .kitchen.yml
      create  test/integration/default
Successfully installed kitchen-vagrant-0.15.0
Parsing documentation for kitchen-vagrant-0.15.0
1 gem installed

fauxhai (2.2.0)

---------------------------------------------
Verification of component 'chefspec' failed.
Verification of component 'package installation' succeeded.
Verification of component 'rubocop' succeeded.
Verification of component 'chef-dk' succeeded.
Verification of component 'knife-spork' succeeded.
Verification of component 'berkshelf' succeeded.
Verification of component 'chef-client' succeeded.
Verification of component 'kitchen-vagrant' succeeded.
Verification of component 'test-kitchen' succeeded.
Verification of component 'fauxhai' succeeded.

This is on Win7 x64.
I see a "The system cannot find the path specified." inbetween, but don't know where it's coming from.
Any ideas?

Oh, it seems that rspec is missing

Oh, it's actually there (C:\Repos\_github\bills-kitchen\target\build\tools\chef-dk\embedded\bin\rspec.bat) but references C:\opscode\chefdk\embedded\bin\ruby.exe...
See https://github.com/opscode/chef/issues/1512#issuecomment-70933804
(you can close this as a dup of #1512 I guess...)


MannWhitneyWIlcoxon tests cannot tollerate more than 34 total samples between groups

Describe the bug
If you perform more than 34 total iterations for a single test and then pass that data to a MannWhitneyWilcoxon test object, the test encounters an overflow, when it tries to allocate more elements in a array than is allowed (over 9 billion for a  2 and change billion limit).
To Reproduce
Steps to reproduce the behavior:

Create a test - set NumIterations to 15
Run the test twice with auto-testing enabled
See the error (or the program will hang).

Expected behavior
The test should complete regardless of sample sizes.
Solution
Lets try this using Math.NET Numerics and see if we avoid the error. If we do, lets migrate over to Math.Net Numerics or Meta.Numerics if thats stil maintained.

Instead, we can downsample to solve this problem. Refactoring to the other libs is not ideal - and may require custom implementations for certain tests.
We'll continue to lean on Accord for now - until a clear solution (that won't take too large an investment of time) presents itself (or is presented to us :D )

Fixed by https://github.com/paulegradie/Sailfish/pull/50


UIEvent is not defined

Hi.
Thanks for fixing the documentation issue the other day - i am now using your component with great pleasure :)
However, i keep running into a new error everytime i refresh my vue app:
ReferenceError
UIEvent is not defined

The error is thrown consistently on line 3713 in file vue-photo-zoom-pro.js.
Any suggestions to how i might fix that?

What is your browser environment?

Chrome, version 96.0.4664.93, 64-bit

I haven't had that problem, can you provide a screenshot or repo?

Chrome, version 96.0.4664.93, 64-bit

I haven't had that problem, can you provide a screenshot or repo?

It happens after i have initialized the component, and then refresh the browser window (f5).

Looks like it's SSR, right?

Yeah it is, nuxt SSR.

This is because there are no window in SSR environments, and I think you need to skip rendering vue-photo-zoom-pro in SSR environments.

I included the module as a plugin with flag ssr: false, this fixed the issue. Once again. thank you.

怎么做的？


doc: Add nip47 pay_invoice example

Description
An example of how to use NIP-47 from rust-nostr
Notes to the reviewers
I hope this is helps people to easily get started sending payments with NWC.
It feels a bit low-level for the SDK, but it relies on the SDK to connect to the relay. Maybe a higher-level NIP-47 library could be added in the future?
Checklists
All Submissions:

[x] I followed the contribution guidelines
[ ] I ran make precommit before committing

Thanks!


Tiny Mouse Cursor in with HiDPI screen in clion/intellij/...

Issue description
When using the current unstable package for clion (same happend with intellij), the mouse cursor becomes tiny when hovering over the clion window.
This seems to be a packaging issue because it does not occur when I download the clion archive directly from jetbrains, unpack & run it.
See the videos in the following file, screenshots hide the cursor unfortunately:
clion.zip
This was also reported to jetbrains, see IDEA-186602.
Steps to reproduce

In Gnome, Start clion/intellij on a HiDPI screen with "200%" scaling enabled:

Move cursor into the opened window

=> The cursor changes to a tiny size. Basically, it looks as if the scaling was not effective inside of that window.
Technical details

system: "x86_64-linux"
host os: Linux 4.17.19, NixOS, 18.03.133185.a960b87ac21 (Impala)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.0.4
channels(root): "nixos-18.03.133185.a960b87ac21, nixos-18.03-18.03, nixos-unstable-18.09pre150708.083220867c7"
channels(peter): "nixos-18.03.133185.a960b87ac21, nixos-unstable-18.09pre150708.083220867c7"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

Closing as #50344 has been fixed and the default cursor is also now scaled automatically if services.xserver.dpi and hardware.video.hidpi.enable are set.


added extra weight for diagonal nodes

I just noticed that the project contains some non-grid (GPS) pathfinding. I'm not sure if this change is compatible with that. But if that is a problem I will look into that again.

Thanks!


Implement also prestart for other bonus apps

With prestart already bonus apps like RTL or Blockexplorer make sure that their config is correct by themselves on service start or restart. This seems to work well since 1.7.2
Now for v1.8 make this a standard and implement also for the rest of the apps - as listed here that need manual change after passwordB change: https://github.com/rootzoll/raspiblitz/blob/3969edc9fd5723807b61c7588debc2fd56b3d5ba/home.admin/config.scripts/blitz.setpassword.sh#L234
Those are:

[ ] RaspiBlitz WebUI
[ ] ElectRS
[ ] BTCPayServer
[x] JoinMarket (also check JoinMarketWebUI)
[ ] Thunderhub
[ ] LIT

Hi prio on apps that are also part of WebUi


Rendering a string with unescaped dollars

Even throwOnError set false, KaTeX always throws the parser error when rendering a string with unescaped dollars.
> console.log(katex.renderToString('$', {throwOnError: false})
ParseError: KaTeX parse error: Expected 'EOF', got '$' at position 1: $̲

KaTeX starts in math mode so the dollar symbol must be escaped.

See also #475 as relevant. (Maybe we should improve that documentation...)

I think KaTeX should throw another type of error for this.
It is confusing because both of them look same type. Most people would expect same behavior.
Unescaped dollars :KaTeX parse error: Expected 'EOF', got '$' at position 1: $̲
Invalid command : KaTeX parse error: Expected 'EOF', got '\alpa' at position 1: \a̲l̲p̲a̲


Add OTP support

Could you add OTP support?
I was about to submit my 1Password-login plugin, but you seem to beat me to it :)
For inspiration, you can have a look at my plugin: https://github.com/elgbar/1Password-login

Hey. Thats awesome. I am open to PRs if you want to merge the functionality. If not I might take a look at it myself!


Move all repository rule invocations to deps() function

There's more work to be done here, but this should ensure we don't break bazel repos dependent on us.

@jtattermusch it won't work anyway. You can't call these functions from a skylark macro.

@nicolasnoble is right. I learned the hard way. This really is a major deficiency with Bazel.


Add unit test for replay with side effect

Need to address couple complains raised by the error checker:
internal/internal_worker_test.go:2189:7:	Sleep(ctx, time.Second)
internal/internal_worker_test.go:2196:19:	encodedRandom.Get(&random)
internal/internal_worker_test.go:2209:10:	a1F.Get(ctx, &A1Result)

Need to address couple complains raised by the error checker:
internal/internal_worker_test.go:2189:7:	Sleep(ctx, time.Second)
internal/internal_worker_test.go:2196:19:	encodedRandom.Get(&random)
internal/internal_worker_test.go:2209:10:	a1F.Get(ctx, &A1Result)


UXD Composability (cargo tests)

An early warning compatibility test like this sounds nice!
I'm a bit concerned about the security implications of checking out a foreign repo and running code from it in the github action. I think they have pretty wide permissions. Possibly there's a way to drop these permissions in the steps that interact with the uxd code? Maybe this is already done?

Possibly there's a way to drop these permissions in the steps that interact with the uxd code?

Could you give more info on this if you had a specific solution in mind? I've googled a bit on downgrading permission during a GH workflow but not sure I had the right keywords

I'm a bit concerned about the

After going through https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions
I can see that this is not the most ideal way of doing things.
Maximilian and Daffy are part of our org and have access to the repo, but that's still not ideal.
In the coming weeks (depending of workload and launch), I'll work on transferring the mango-logic back to mango.
I also want to make a "anchor_mango" rust dep, hosted on mango possibly, well not directly related to the tests. (Need to do some rewrite)

I think the test simply fails on the 0.2 mint amount as it's small enough to have this discrepancy shows. Basically the execution price and the "test validation price" might not be the same? A bit out of idea on this one

In the CI the exec price was 148.479 (perp price)

In the CI the perp price fetched from mango by the test was  148.4945 (perp price)

https://explorer.solana.com/tx/4dptKDYrL43vJ9b5isqvSRWqrQy76gpyCfUeDt3KinqBen5kX9rMzWtMQ9nAWey8vDtc2bf98vLqGh1nRUEwVsG2?cluster=devnet

Possibly there's a way to drop these permissions in the steps that interact with the uxd code?

Could you give more info on this if you had a specific solution in mind? I've googled a bit on downgrading permission during a GH workflow but not sure I had the right keywords

I was thinking specifically of the job having the permissions of the github org and potentially being able to read private repos or make commits. But after reading https://docs.github.com/en/actions/security-guides/automatic-token-authentication it sounds like as long as we don't explicitly pass the GITHUB_TOKEN secret into the job, it'll not be able to use these permissions.

Updating the provider to be reset for each test seems to fix the problems. LGTM. Need a squash

Still too much instability to be able to add this as a auto run as it would break quite often.
It's mostly due to devnet :

sometimes the oracle price is too far from the perp price, causing slippage errors (maybe the ci doesn't run the MM bot properly in these cases)
sometimes the getBalance does not return the proper balance even after a succesful TX (still not sure why this happen, same connection. Seems to have some kind of latency, don't have this issue on local machine)

is there a part of the tests that doesnt need a working mango group and could just be run against the binary?
we do use the stub oracle for our own tests rather then pyth etc on devnet

@microwavedcola1 This one is ready to go. I've remove the E2E test as it's still too janky, will make another PR.

in principle I approve, but you might need to adapt code to work with latest master/main

Yes updating tomorrow

Updated with the planned patch branch v2.3.0 - I'm still wondering how we will proceed for deployment, as it would again need to be done in sync. Let me know your thoughs, cheers.

(seeing https://github.com/blockworks-foundation/mango-v3/pull/144 , I believe this CI will keep UXD released version as checkout)

no need to deploy in sync, the current data layout simply has time in force always set to 0

no need to deploy in sync, the current data layout simply has time in force always set to 0

This will break without us updating I believe? Post audit we will use place_order_v2 to remove this composability weakness

no need to deploy in sync, the current data layout simply has time in force always set to 0

This will break if we don't update on our side. And if we update before you it will break too.
This will be remove after audit for place_perp_order_v2, keeping minimal change for now

Looks good to merge


Signal blocks when a reorg happens

It was agreed in a call that we will implement reorg signalling.
This requires some changes to CM.
There will be introduced a MaxBlocksInStore constant that will allow storing enough blocks in store to allow signalling of blocks that have been reorged.
This effects mainly pruned nodes and light wallets.
Ont thing to investigate is light wallets.
One suggestion was to signal block hashes not full block.

there is an issue for that that is a part of activation
closing because it's a duplicate


Add a new List App-React.js

Describe the project
I want to add a React.js project named LIST APP . It uses React.js, HTML, and CSS.
Issue Type:

[ ] Bug Report
[ ] Feature Request
[ ] Documentation
[x] New Project

Please assign me this issue.

@TusharKesarwani I want to work on this issue under SSOC, kindly assign me this issue.

@TusharKesarwani I would love to work on this. I already have experience in this task. So, kindly assign me this task under SSoC '23.

I would like to work on this issue. I will be using Framer Motion and TailwindCSS for efficient animations.

I would like to work on it under SSOC'23, please assign it to me and oblige. Thank you.

I would like to work on this project. I have done similar kind of project kindly assign it  to me.

I would like to contribute to this project, Please assign me this project.

React projects are not accepted

Okay @TusharKesarwani, please assign me this issue, I can work on it with only HTML, CSS, Javascript.
Thank You.


SMT query batching

Pulse issues separate SMT queries for every proof obligation, effectively behaving like --split_queries always.
This can be needlessly slow when a program has many small queries.
We should add support to batch queries.

The mechanism is already implemented (#65) but it didn't look like a clear improvement, so we'll revisit to see if it makes sense to enable it.


How to evaluate the prompt score, not at the time of attack, but only?

Because the accuracy of my experimental results does not match the paper. Because I want to directly evaluate the prompt after being attacked by text to see if the score is wrong?

Hi, thanks for your interest! You could find the results on this website.


Upgrade ember-runtime-enumerable-includes-polyfill to 2.0.0

This project uses semver, please check the scope of this pr:

[x] #patch# - backwards-compatible bug fix
[ ] #minor# - adding functionality in a backwards-compatible manner
[ ] #major# - incompatible API change

The only changes to ember-runtime-enumerable-includes-polyfill for 2.0.0 is moving to Babel 6. As covered in #48, we lint dependencies at Salsify and would like to remove our overrides for this project
CHANGELOG
Upgrade ember-runtime-enumerable-includes-polyfill to 2.0.0

Coverage remained the same at 57.143% when pulling 277f679d7a797387523d3485fe84c06e91503cb0 on salsify:feature/upgrade-ember-runtime-enumerable-includes-polyfill into 52cbdc59e355d488d1cb94110632f35c3d2117ae on ciena-blueplanet:master.

Approved

It looks like the Travis failures are due to a pr-bumper incompatibility with Node 5?

Sorry I'm not able to focus much on this currently - I would think it would
be acceptable to bump the try matrix up to 6
On Jul 19, 2017 5:36 PM, "Dan Freeman"<EMAIL_ADDRESS>wrote:

It looks like the Travis failures are due to a pr-bumper incompatibility
with Node 5?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ciena-blueplanet/ember-block-slots/pull/51#issuecomment-316525134,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIm6lpoeFKBU1evUb4NdlfBLktZWkQR9ks5sPnbcgaJpZM4Oakd_
.

Coverage remained the same at 57.143% when pulling 64801c393fa83d47512dc0be029c2947bcea3866 on salsify:feature/upgrade-ember-runtime-enumerable-includes-polyfill into 52cbdc59e355d488d1cb94110632f35c3d2117ae on ciena-blueplanet:master.

Coverage remained the same at 57.143% when pulling 64801c393fa83d47512dc0be029c2947bcea3866 on salsify:feature/upgrade-ember-runtime-enumerable-includes-polyfill into 52cbdc59e355d488d1cb94110632f35c3d2117ae on ciena-blueplanet:master.

@sglanzer this should be good to go

Approved


Question / Request: Unique Plugin Mass Update

Hi,
I don't know if it is allready possible, but is there a way to mass update the portals unique visits and captures without having to click every single portal to update?
Like, in the portal list in view, "Update Uniques" or something? Now I have to click every portal to update the status.

No, because the data required to do so is not available. See FAQ.

note: the unique-plugin is able to extract the status from the chat-log too.


Fixes for client dockerization

Description
This PR updates the node, nginx, and lock file versions for the client docker build process. docker-compose should work as a local development environment now without the problems discussed in #259.
Issue ticket number and link

closes #259
Checklist

[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

Other Stuff

@Badrri-Narayanan Can you take a look at this and verify you are able to start the local dev environment?

@dpgraham4401 sure. Let me check

@dpgraham4401 , I tried running with your latest changes but now I am getting a different error. It is as follows:
 => [haztrak_client builder 5/6] COPY . .                                                                          0.0s
 => ERROR [haztrak_client builder 6/6] RUN npm run build                                                           1.0s
------
 > [haztrak_client builder 6/6] RUN npm run build:
#0 0.924
#0 0.924 ><EMAIL_ADDRESS>build
#0 0.924 > react-scripts build
#0 0.924
#0 0.978 node:internal/modules/cjs/loader:998
#0 0.978   throw err;
#0 0.978   ^
#0 0.978
#0 0.978 Error: Cannot find module 'react-dev-utils/crossSpawn'
#0 0.978 Require stack:
#0 0.978 - /app/node_modules/react-scripts/bin/react-scripts.js
#0 0.978     at Module._resolveFilename (node:internal/modules/cjs/loader:995:15)
#0 0.978     at Module._load (node:internal/modules/cjs/loader:841:27)
#0 0.978     at Module.require (node:internal/modules/cjs/loader:1061:19)
#0 0.978     at require (node:internal/modules/cjs/helpers:103:18)
#0 0.978     at Object.<anonymous> (/app/node_modules/react-scripts/bin/react-scripts.js:18:15)
#0 0.978     at Module._compile (node:internal/modules/cjs/loader:1159:14)
#0 0.978     at Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
#0 0.978     at Module.load (node:internal/modules/cjs/loader:1037:32)
#0 0.978     at Module._load (node:internal/modules/cjs/loader:878:12)
#0 0.978     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) {
#0 0.978   code: 'MODULE_NOT_FOUND',
#0 0.978   requireStack: [ '/app/node_modules/react-scripts/bin/react-scripts.js' ]
#0 0.978 }
#0 0.978
#0 0.978 Node.js v18.12.1
------
failed to solve: executor failed running [/bin/sh -c npm run build]: exit code: 1

@Badrri-Narayanan Appreciate your help, I've updated the docker-compose so npm run build is not run anymore. Can you pull the latest changes and try again?
This is interesting, I'm open to suggestions on how to make the onboarding experience smoother.

@dpgraham4401 I appreciate you try to fix this issue. I will try with your current change. Thanks

@dpgraham4401 removing npm run build didn't help. I spent some time and I may have found a workaround. I will raise a new PR. It may not be the most efficent way but it could simplify local setup and onboarding.


globalSetup and globalTeardown not being re-ran on watch

My setup and teardown scripts are only being run once at the beginning of watch, but not being re-run when I change a file. It seems like people are having the opposite issue.
globalSetup.ts
import { startTestServer } from './testServer';

const setup = async (): Promise<void> => {
  await startTestServer();
};

export = setup;

jest.config.js
module.exports = {
  globalSetup: '<rootDir>/test/globalSetup.ts',
  globalTeardown: '<rootDir>/test/globalTeardown.ts',
  preset: 'ts-jest',
  testEnvironment: 'jsdom',
  testMatch: ['**/*.(test|integration).ts?(x)'],
};

hi @ericyliu for me I see globalSetup.ts and globalTeardown always reruns whenever I change anything in my test files.


Feature request to show "germline biallelic" statistics in the portal

Moved from: https://github.com/genome-nexus/genome-nexus-importer/issues/43
Show "# germline homozygous" in gene and variant level pages.

In the gene level page, show "# germline homozygous" column in the table between "% Prevalence" and "Cancer type" columns. This data is in the "n_germline_homozygous" column in 'signaldb_all_variants_frequencies.txt'.

In the variant level page, show "# germline homozygous" column in the table between "# Carriers" and "% Prevalence" columns. This data is in the "n_germline_homozygous" column in 'signaldb_variants_by_cancertype_summary_statistics.txt'

In the variant level page, show "% germline homozygous" in the "cancer patient prevalence field. This data is in "signal.pancancer_somatic_germline_stats.txt" file. For example:

in https://www.signaldb.org/variant/1:g.45797228C>T
cancer patient prevalence: Germline 0.8% (Biallelic: 18.4%, Germline homozygous: 0.02%)

Thank you.

Questions:

We are not using signal.cancertype_specific_somatic_germline_stats.txt anywhere, right?


OpenVSX publish failed

Seems like OpenVSX had some downtime, which caused the 0.0.13 release to fail. Could you manually publish it to the registry? Thanks!

yeah was waiting for it to resolve, published version 0.0.13 to openvsx


UMS is not detected by fwup on Windows 11

I am on Windows 11 using the latest version of fwup, installed via the executable.
When using .\fwup.exe -z, I'm getting:
fwup: No memory cards found. Try reinserting the card.
Now when I use Get-PhysicalDisk, I can view my Linux UMS disk as physical disk number 1.
So I try to use .\fwup.exe -d 1 .\firmware.fw where firmware.fw is my firmware.
This sort of works, it appears to work as intended but nothing is actually written to the MMC.
Additionally, the write time is just far too short compared to another computer running fedora and fwup (2 seconds instead of 2 plus minutes).
Im wondering if this is a windows issue, a physical drive number issue, or something else.
The target is an eMMC exported to the host PC as a USB mass storage device. Windows recognizes it and gives it a disk letter.
Additionally, the device is using u-boot to create the UMS.
This has been done before on a different PC, on Windows 10, but I'm unsure how they did it.
Thank you for your time!

Oh no. I haven't used Windows 11 with fwup and don't have a Windows 11 machine handy.
As an temporary workaround, you can create a disk image fwup -d imagefile.img and then use Etcher or another tool to write to the eMMC.
I think that I'll need help to fix Windows 11 and that might take a while. I hope that the workaround is ok for now.

Ok thank you for the speedy response, Ill try it out.

Update:
Using the command .\fwup -d firmware.img .\firmware.fw works just fine, I realized what what was going on, and etcher is able to write to the UMS as well, and everything works on the device.
Additionally, when trying to use the command:
.\fwup.exe -d \.\PhysicalDrive1 .\firmware.fw
fwup is able to recognize this as device namespace but throws some errors, starting with:
"fwup: Error determining the size of \.\PhysicalDrive1"
Do you know what I could do to fix this such that I can use fwup by itself?
For now, I'm going to pursue the workaround of creating the .img with fwup and then uploading it with etcher.
Additionally, there is a misleading error message about formatting when trying to use:
.\fwup.exe -d \.\PhysicalDisk1 .\firmware.fw
"fwup: Target device must be formatted like \.\PhysicalDisk# where ..."
The formatting actually prefers "... \.\PhysicalDrive# .."
Thanks again for the help!

Update 2:
Good news! fwup works just fine on Windows 11 and is able to program my UMS eMMC as expected.
The issue was I wasn't executing fwup with elevated privileges!
It's pretty obvious now, because balena cli requires them too, but Im just glad I got it working, and that there was never an issue with fwup.
So don't worry, fwup works fine on Windows 11.

Thanks for letting me know that it works!
I also fixed the error message that you pointed out was wrong in ac340b44c4b95f3785981b20f112cf7094ae12ca.


Fallback schedules should get a distinct source

In case of an infeasible problem, the StorageScheduler falls back to using the fallback_charging_policy, while schedule data is still being attributed to the StorageScheduler. It would help debugging to be able to visually distinguish schedule data originating from one or the other, by having fallback schedules saved with their own distinct source.
I propose we refactor fallback_charging_policy to its own FallbackStorageScheduler, and think about triggering. For example:

We could let the original scheduling job fail, and upon failure set up the fallback scheduling job. This would then also require something clever for retrieving schedules (getting a schedule using the ID of the failed job should result in obtaining the fallback job).
Alternatively, we compute the fallback schedule within the same job (thereby dispensing with the issue of scheduling job IDs). We let the StorageScheduler.compute method fail, and trigger the fallback within the services.scheduling.make_schedule method.

Good idea!
Just wanted to add that another benefit from option (1) is that we'll be able to track if a certain schedule failed via the rq job dashboard. This option also allows for recursive fallback mechanisms (in case the fallback fails).
Option (2) is simpler which is nicer IMO.
Aside, I think we should link the fallback mechanism to the StorageScheduler, for example, as a class attribute. That way, we can have specific fallback for the different schedulers. I was thinking in something like:
class StorageScheduler:
    fallback_scheduler : Scheduler
    [...]
    def __init__(...):
        [...]
        self.fallback_scheduler = StorageSchedulerFallback([...])

    def compute_fallback(...):
        return self.fallback_scheduler.compute()

we should link the fallback mechanism to the StorageScheduler, for example, as a class attribute

Good idea.
Also, I realised that fetching schedules is done on the basis of the data source ID of the Scheduler, so the issue of pointing users that are getting a schedule to the right place, is an issue for both options. Luckily, I found that we store the data source ID on the job already after we call the compute function (in make_schedule), so it should be relatively easy to point users that are getting a schedule to the right data, just by saving the data source ID of the FallbackScheduler on the job.

Also, we should add the source id (maybe the name too) to the response. Perhaps it's also a good idea to add an open field to share unstructured info regarding the state of the schedule.
An alternative to keep the Job ID but relying on RQ is to set the retry = 1 and if it fails, check the number of trials and call the fallback schedule. We can even set the retry > 1 to allow for multiple retries.
The benefit is that the setup part of the main scheduler can be the same but instead of calling compute we call compute_fallback.

My one fear is that retrying the job will make us lose the error trace. But even if it's not lost, I think creating a new job would be cleaner, so a failed compute call doesn't end up showing under a successful job.

Good point!
Let's create a new job in case of failure and link them via meta attributes.
Regarding the fetching of the schedules (GET /<id>/schedules/<uuid> endpoint), I'm considering two different ways:

Return in the same request for the StorageScheduler the contents of the Fallback, adding details on the status message.
Use redirect to funnel the request to  /<id>/schedules/<uuid-fallback> endpoint with the status code 302 (See Other).

I favor more the second as not to mix both jobs info.

Closed as completed by:
https://github.com/FlexMeasures/flexmeasures/blob/78e20233903440c1ce3e831a79152689c116f915/flexmeasures/api/v3_0/tests/test_sensor_schedules.py#L460-L473


5 sign up validations

Validates user email & password at registration

prevents invalid emails
prevents duplicate emails
validates password with password_confirmation
stores unsaved form information for reuse to prevent the need to reenter correct information

Good work - looks like some real progress.


Prepare for release

Fixes https://github.com/Azure/azure-sdk-for-python/issues/19618

/azp run python - monitor - tests


Epoch state for the new indexer

Several things are missing at the moment:

the epoch nonce and epoch SDD indexers are placeholder
we don't clean up outdated files
the performance isn't good, especially because we don't really take advantage of the catchup mechanism

Why do we propose it then?
Once these points are covered, we should be able to have a better alternative than the current epoch state, especially once synced:

we store only new blocks, not epoch-state, after each block
we've decomposed the monolithic indexer into smaller parts.

Pre-submit checklist:

Branch

[ ] Tests are provided (if possible)
[ ] Commit sequence broadly makes sense and have useful messages
[ ] Important changes are reflected in changelog.d of the affected packages
[ ] Relevant tickets are mentioned in commit messages

PR

[ ] (For external contributions) Corresponding issue exists and is linked in the description
[ ] Targeting main unless this is a cherry-pick backport
[ ] Self-reviewed the diff
[ ] Useful pull request description
[ ] If relevant, reference the ADR in the PR and reference the PR in the ADR
[ ] Reviewer requested

Not ready for a merge but I'd be happy to have feedback.


Add Mac OS X 32bit x86 release

I've noticed there is no Mac OS X 32bit x86 target from adoptopenjdk.
Do you have plans to add this?

Apple removed 32 bit support throughout the system. Why should we do this and what for?

Unfortunately, we don't support OS's which are no longer supported.


Being able to listen on Core Events and propagate to the state

Description
I want to listen to Core events to change my charts, inputs, and outputs depending on Core events. This means propagating changes to the state without using Gui Core visual elements.
Acceptance Criteria

[ ] Propose an implementation design
[ ] Create an application as a demo
[ ] Create related issues

The Gui is now able to broadcast a callback to all clients, so the only remaining part is on taipy-doc.


Add Safari support to web extension (desktop and mobile)

The web extension currently supports installation for only Chrome and Firefox browsers. Safari should be supported next given its general popularity.
Blocked by https://github.com/hirosystems/stacks-wallet-web/issues/706

please can we get this moved up in the priority list? apple just added support for extensions in safari on iPadOS and iOS too. i think it's vital we get this out ASAP, because i really want to be able use my wallet on iOS. should be sorta simple to make the extension an app too. idk, but please let's just get this shipped 🔥

@SyAsteria We can take a look at making this a priority for Q4. If you need this earlier, we'd love to review a PR!

An added benefit here would be supporting mobile (iOS) in addition to desktop out of the gate: https://developer.apple.com/videos/play/wwdc2021/10104/

Like @0xAsteria, Safari is also my go to browser, so I was just trying this out today on Safari 15 and Xcode 13.

Good news is the "Warning: The following keys in your manifest.json are not supported by your current version of Safari. If these are critical to your extension, you should review your code to see if you need to make changes to support Safari:" errors are gone!
More good news is that it responds to a the connect sign in event on btc.us.
Bad news is that it looks like this:

The error in the extension is "unable to get origin from request"

Thanks @larrysalibra, interesting that the TypeError is thrown, as its inside a try/catch

@larrysalibra super helpful, thanks!
Is our sense here that getting the extension supported for Safari might be a relatively modest compatibility tweak undertaking?

I think Safari desktop should be quite manageable. But it's not 1:1 with mobile. Non-persistent background pages for example may cause some issues.

This is predominately necessary for enabling native application development on iOS via ionicframework.  I tried going the cocoapods route too but that repository is 2 years old and unmaintained (broken).


RG351V: No more systems shown after Update to Test Release 1.8

Hi,
i just updated to ArkOS Test Release 1.8 (from 1.6) via Wifi on my RG351V.
After the Update was finished, the search for the systems took 1 second and no systems from my 50+ systems
are shown. ArkOS ist just showing "RetroArch" and "Options" in the main menu.
I use a single 128GB SanDisk SD-Card with the EASYROMS-Partition in exFAT format.
I looked into the SD-Card and everything seems O.K., no data has been deleted.
Even tried to restore a backup, but that didn't help either.
Could it be the old issue "exFAT not readable", use FAT32?
Could you please investigate what went wrong? The "V" is now rendered useless...
Thanks for looking into it..

Ooops...my bad.  Forgot to put a check in to see if a second sd card is being used and adjust the updated es_systems.cfg based on that or not.  I've added an update for that to fix it.  Just update as usual and you should be at 1.8.1.  Thanks for reporting this.

Thank you for fixing it so quickly.


Clean up and add tacaswell

This is to add @tacaswell to the list of maintainers of this feedstock. There was a problem before.

Checklist

[x] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged) no need for that
[ ] Reset the build number to 0 (if the version changed) no need for that
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged. (it's in the packaged archive)

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

@conda-forge-admin, please rerender.

@mrakitin why switch to PyPI instead of GitHub?

Thanks @hhslepicka! The background behind switching from the GitHub archives to PyPI sources is here: https://matplotlib.org/devdocs/devel/release_guide.html#id2. Thanks to @tacaswell for pointing out to this and welcome to the maintenance ~hell~ team!


Issue with returning presentationId in slides API

Hi,
I am trying to use the slides API with node on cloud functions. There seems to be an issue with the response that the slides api is returning. There seems to be no "presentationId" in the response body.
return new Promise((resolve, reject) => {
	slides.presentations.create({
		auth: oauth2Client,
		title: "test preso",
	}, (err, presentation) => {
		if (err) {
			console.log(err);
		}
		else {
			resolve(presentation);
		}
	})
})
.then(function(presentation){
	console.log(presentation.presentationId);
})

The console log return >> undefined
EDIT: Just to clarify, the presentation gets created in my drive, but there is no presentationId in the response json.
Thanks!

Greetings!  You can really simplify all of this :)  We now return promises by default, so you don't have to do your own promise wrapping.
async function main() {
  const res = slides.presentations.create({
    auth: oauth2Client,
    title: "test preso"
  });
  console.log(res.data);
  return res.data;
}

main().then(p => {
  console.log(p.presentationId);
}).catch(console.error);

Hope this helps!


Content out of date in multiple places,

Content out of date in multiple places, the UI has significantly changed and many of the suggested paths are not accurate to the new menu.  Please review these paths and correct them.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: faf5c5df-c3ab-8448-aef0-af05977db9b9
Version Independent ID: adade895-f42b-1029-9948-5ddb5b038257
Content: Quarantine policies - Office 365
Content Source: microsoft-365/security/office-365-security/quarantine-policies.md
Product: m365-security
Technology: mdo
GitHub Login: @chrisda
Microsoft Alias: chrisda

@bruceburge, the only thing that I could find that was out-of-date was the very first step for getting to quarantine policies in 5 locations It said this:

In the Microsoft 365 Defender portal, go to Email & collaboration > Threat policies > Rules section > Quarantine policies and then select Quarantine policies.

It should say this:

In the Microsoft 365 Defender portal, go to Email & collaboration > Policies & Rules > Threat policies > Quarantine policies in the Rules section.

I fixed all 5 instances. That was all that I could find wrong.

@bruceburge Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


[DO NOT MERGE]Use JDK's JAXP / WFLY-4704 Remove Xalan from WildFly

This is using jboss-modules 1.5.0.Beta1-SNAPSHOT and is as such still experimental.

Windows Build 1584 is now running using a merge of 3929903f832935f6e1fb78aaec39ab078860c838

Linux Build 2041 is now running using a merge of 3929903f832935f6e1fb78aaec39ab078860c838

Core - Full Integration Build 1178 is now running using a merge of 3929903f832935f6e1fb78aaec39ab078860c838

Windows Build 1584 outcome was SUCCESS using a merge of 3929903f832935f6e1fb78aaec39ab078860c838
Summary: Tests passed: 3224, ignored: 71 Build time: 0:22:31

Linux Build 2041 outcome was SUCCESS using a merge of 3929903f832935f6e1fb78aaec39ab078860c838
Summary: Tests passed: 3224, ignored: 71 Build time: 0:25:29

Core - Full Integration Build 1178 outcome was FAILURE using a merge of 3929903f832935f6e1fb78aaec39ab078860c838
Summary: Tests failed: 4 (4 new), passed: 2870, ignored: 395 Build time: 0:48:36
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ejb.security.EJBSecurityTestCase: <no details avaliable>

org.jboss.as.test.integration.ejb.security.SecurityDDOverrideTestCase: <no details avaliable>

org.jboss.as.test.integration.jpa.cfgfile.CfgFileTestCase: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCForEarModulesTestCase: <no details avaliable>

Core - Full Integration Build 1179 is now running using a merge of 12f1dbeec747cb0d958c6d80e15b4ebedccfaf82

Linux Build 2042 is now running using a merge of 12f1dbeec747cb0d958c6d80e15b4ebedccfaf82

Windows Build 1585 is now running using a merge of 12f1dbeec747cb0d958c6d80e15b4ebedccfaf82

Windows Build 1585 outcome was SUCCESS using a merge of 12f1dbeec747cb0d958c6d80e15b4ebedccfaf82
Summary: Tests passed: 3224, ignored: 71 Build time: 0:22:19

Linux Build 2042 outcome was SUCCESS using a merge of 12f1dbeec747cb0d958c6d80e15b4ebedccfaf82
Summary: Tests passed: 3224, ignored: 71 Build time: 0:25:10

Core - Full Integration Build 1179 outcome was FAILURE using a merge of 12f1dbeec747cb0d958c6d80e15b4ebedccfaf82
Summary: Tests failed: 5 (1 new), passed: 2868, ignored: 395, muted: 1 Build time: 0:47:41
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.clustering.cluster.sso.ClusteredSingleSignOnTestCase(SYNC-tcp).testNoAuthSingleSignOn: <no details avaliable>

org.jboss.as.test.integration.ejb.security.EJBSecurityTestCase: <no details avaliable>

org.jboss.as.test.integration.ejb.security.SecurityDDOverrideTestCase: <no details avaliable>

org.jboss.as.test.integration.jpa.cfgfile.CfgFileTestCase: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCForEarModulesTestCase: <no details avaliable>

Windows Build 1652 is now running using a merge of 58e9200a881a28413d4a069df9b4a2c7bc251245

Core - Full Integration Build 1253 is now running using a merge of 58e9200a881a28413d4a069df9b4a2c7bc251245

Linux Build 2118 is now running using a merge of 58e9200a881a28413d4a069df9b4a2c7bc251245

Windows Build 1652 outcome was SUCCESS using a merge of 58e9200a881a28413d4a069df9b4a2c7bc251245
Summary: Tests passed: 3360, ignored: 62 Build time: 0:32:51

Linux Build 2118 outcome was SUCCESS using a merge of 58e9200a881a28413d4a069df9b4a2c7bc251245
Summary: Tests passed: 3360, ignored: 62 Build time: 0:34:36

Core - Full Integration Build 1253 outcome was FAILURE using a merge of 58e9200a881a28413d4a069df9b4a2c7bc251245
Summary: Tests failed: 4, passed: 2919, ignored: 367 Build time: 0:49:40
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ejb.security.EJBSecurityTestCase: <no details avaliable>

org.jboss.as.test.integration.ejb.security.SecurityDDOverrideTestCase: <no details avaliable>

org.jboss.as.test.integration.jpa.cfgfile.CfgFileTestCase: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCForEarModulesTestCase: <no details avaliable>

As discussed this cannot happen reliably in time for 10.
But should be revisited after JDK9 comes out.


Create buttons for backup and loadBackup

VSCode has shortcut buttons at the top right corner, such as "Git: View File History", "Open Preview", etc.
Create buttons for backup and loadBackup similar to those existing.

Note that vscode doesn't allow more than one icon/button per extension. Will need to link the operations to that icon


Image streaming

Given the format of the two webcams, I have rotated the screen, but to cover the part with the shell, you will want to add a third fake webcam that transmits a black image.
Can I add streaming of an image?

No, you just use the screen blanking option right in the configuration
files.
On Tue, May 19, 2020, 9:45 AM WirelessMind<EMAIL_ADDRESS>wrote:

Given the format of the two webcams, I have rotated the screen, but to
cover the part with the shell, you will want to add a third fake webcam
that transmits a black image.
Can I add streaming of an image?
[image: image]
https://user-images.githubusercontent.com/18408814/82334003-b4eac000-99e7-11ea-83ad-93c98adb2da5.jpg
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Anonymousdog/displaycameras/issues/52, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHIYIKMEAWP6CB6TIHCNHTDRSKEPTANCNFSM4NFASX6Q
.

 Sorry I didn't understand it was for that. My English is terrible!

No worries. Enjoy!
On Tue, May 19, 2020, 1:39 PM WirelessMind<EMAIL_ADDRESS>wrote:

You are right! Sorry I didn't understand it was for that. My English is
terrible!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Anonymousdog/displaycameras/issues/52#issuecomment-630974295,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHIYIKJSGBJFCN6UI3FK7H3RSK74BANCNFSM4NFASX6Q
.


Monitoring - Cluster member can enable/disable monitoring on cluster level

Bug.
Rancher master on 12/5
Steps:

logged in as admin to add a standard user to a cluster as a cluster member
logged in as the cluster member, go to the cluster -> Tools-> Monitoring

Result:
The cluster member can see settings and turn on the monitoring.
Expected result:
The cluster member should not be able to turn on the monitoring.
Other details might be helpful:
If the monitoring is already enabled by the admin/cluster owner, then the cluster member will see the following uncompleted sentences:

Related issue - https://github.com/rancher/rancher/issues/16889

This issue also happens on HA setup.

The fix is validated on master 1/3
Steps:

logged in as admin to enable Github Auth
then add a Github user (standard user role) to a cluster as a cluster member
logged in as the cluster member, go to the cluster -> Tools-> Monitoring

Result:

The cluster member cannot turn on the monitoring.
The cluster member cannot see live metrics and graphs when the monitoring is on.


Main and Staging different git histories

Main and staging have different git histories and this needs to be resolved before we move further.

I think if you branch for staging then people are not running into this error, not sure though.

Yeah totally agree. Just worried incase we have to merge into main at the end of the week and run into some errors.

So after some discussion before standup, this will only become an issue if you mistakenly branch off staging. Closing this now.

My bad, I see that Robbie opened a branch for this and will leave this open.

Hi @robzwolf This is the issue as per what you mentioned in the standup. Can't PR into main.


✨(courses) add organization plugin

Purpose
This allows us to add a preview of organizations as a plugin in placeholders.It shows the logo and the title. By having the possibility of adding organization plugin, we can create a nice overall presentation page. Fulfill the need of issue: Organization list page #313
Proposal
Create the plugin based on what was done for the Person Plugin.

[x] Add the plugin
[x] Manual test
[x] Automate test

Improvements were added on top of this PR:
Make organization logo a placeholder #322

[x] make the organization logo a plugin in a specific placeholder instead of a field on the page exgtension model
[x] refactor the factories for page extension models to better handle i18n and publication

Review:
It's all good from my point of view.


[Bug Fix] subtract all remaining gas before checking for address collision in the CREATE opcode

What was wrong?
While trying to pass a test related to address collision I learned that all the remaining gas needs to be subtracted before checking address collision in the CREATE opcode.
How was it fixed?
subtracted all remaining gas before checking for address collision in the CREATE opcode
Cute Animal Picture

Pic credits: www.pexels.com

Codecov Report

Merging #348 (d7c5b20) into master (a4b3687) will increase coverage by 0.08%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #348      +/-   ##
==========================================
+ Coverage   95.31%   95.39%   +0.08%
==========================================
  Files          46       46
  Lines        2367     2367
==========================================
+ Hits         2256     2258       +2
+ Misses        111      109       -2

Flag
Coverage Δ

unittests
95.39% <100.00%> (+0.08%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/ethereum/frontier/vm/instructions/system.py
90.20% <100.00%> (+1.39%)
:arrow_up:

Continue to review full report at Codecov.

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


Prompt weight converter

converts (word:1.05) to (word)1.05

Thankyou for the code, I already integrated in my local copy and have been testing, works well :)

merged here https://github.com/ausbitbank/stable-diffusion-discord-bot/commit/5aa394cb1b432b1cfbb06a7610aa681ccb27282f


integration with specimen micropublication

We are creating github repos and versioned zenodo pubications for sharing images and data about specimens from our project. There are many reasons to do micropublication based on specimens, including enabling linking to single specimens, providing all images for datasets used in photogrammetry, etc.
Here is an example:
https://github.com/Big-Bee-Network/UCSB-IZC00012194
How could we integrate trait information into these specimen micropublications to 1) increase findability and 2) provide trait information to be usable for wikidata or other derivative products?

"Traditionally" the way that annotations for anatomical structures have been incorporated into publications has been by adding an IRI/URI table (for example: https://dfzljdn9uc3pi.cloudfront.net/2016/2682/1/Table_S3.pdf).
This issue can also be understood as how to annotate images, which would be related to https://github.com/phenoscape/TraitFest-2023/issues/7

@JCGiron true! And that would be a good first addition for describing what structures are visible in the images. Specially we are recording body size measurements for 100/1000s specimens for the project. These are what I would like to include in the specimen publication. Perhaps with a methodology similar to https://pubmed.ncbi.nlm.nih.gov/23652347


Configure persistent volumes with ceph-csi cephfs or rbd

As mentioned in https://github.com/DataONEorg/k8s-cluster/pull/2#issuecomment-854284130, now that CephFS has been setup on our k8s clusters, we can setup dynamic provisioning for persistent volumes.
This can be enabled on the dev cluster, as CephFS has been enabled for the control and worker nodes. Once this has been setup and tested, it can be setup for the production cluster (once the control node has been enabled for CephFS).

Regarding dynamic provisioning of k8s storage - it appears that the most up-to-date method to enable this is to use external (to the k8s distribution) storage provisioners that adhere to the Container Storage Interface.
This is important as there are legacy versions of these provisioners that might not be maintained, and it appears that the k8s documentation has not caught up, e.g. at https://kubernetes.io/docs/concepts/storage/storage-classes/. Installing the legacy version of the provisioner for CephFS didn't work, i.e. following the example at https://www.velotio.com/engineering-blog/kubernetes-storage-using-ceph
The next step is to try the CSI CephFS found at https://github.com/ceph/ceph-csi/tree/devel/examples/cephfs

The Ceph cluster has been setup and made available for use by the k8s clusters as described here.
After attempting to setup ceph-csi rbd for k8s dev, I noticed that ceph-csi rbd doesn't support the access mode that is needed by k8s services - at least by the quality services, which is 'ReadWriteMany'. Here is a quick synopsis from the k8s docs:

ReadWriteOnce -- the volume can be mounted as read-write by a single node
ReadOnlyMany -- the volume can be mounted read-only by many nodes
ReadWriteMany -- the volume can be mounted as read-write by many nodes
ReadWriteOncePod -- the volume can be mounted as read-write by a single Pod. This is only supported for CSI volumes and Kubernetes version 1.22+.

A description of why ceph-csi rbd doesn't support ReadWriteMany is here.
Therefore, the next best option is to use statically provisioned ceph-csi cephfs persistent volumes, as described here.
@nickatnceas for this I need to setup the cephfs subvolume as detailed in the document mentioned above, for dev k8s initially, with commands such as:
ceph fs volume create k8sdevfs
ceph fs subvolumegroup create k8sdevfs k8sdevGroup
ceph fs subvolume create k8sdevfs k8sdevSubVolume k8sdevGroup --size=1073741824

@nickatnceas does that look reasonable to you?

Hi @gothub , I deployed a subvol for the k8sdev CephFS. The username, secret, and path are all new, here's the info:
username: k8sdevsubvoluser
subvolgroup: k8sdevsubvolgroup
subvolume: k8sdevsubvol
subvolume path: /volumes/k8sdevsubvolgroup/k8sdevsubvol/4b7cd044-4055-49c5-97b4-d1240d276856
secret: /etc/ceph/ceph.client.k8sdevsubvoluser.keyring (on docker-dev-ucsb-1 and docker-dev-ucsb-2)
Verifying that it works:
outin@docker-dev-ucsb-1:~$ sudo mount -t ceph <IP_ADDRESS>:6789,<IP_ADDRESS>:6789,<IP_ADDRESS>:6789,<IP_ADDRESS>:6789,<IP_ADDRESS>:6789:/volumes/k8sdevsubvolgroup/k8sdevsubvol/4b7cd044-4055-49c5-97b4-d1240d276856 /mnt/k8sdevsubvol -o name=k8sdevsubvoluser,secretfile=/etc/ceph/k8sdevsubvoluser.secret
outin@docker-dev-ucsb-1:~$ df -Th /mnt/k8sdevsubvol
Filesystem                                                                                Type  Size  Used Avail Use% Mounted on
<IP_ADDRESS>:6789,<IP_ADDRESS>:6789,<IP_ADDRESS>:6789,<IP_ADDRESS>:6789,<IP_ADDRESS>:6789:/volumes/k8sdevsubvolgroup/k8sdevsubvol/4b7cd044-4055-49c5-97b4-d1240d276856 ceph  889T     0  889T   0% /mnt/k8sdevsubvol
outin@docker-dev-ucsb-1:~$ cd /mnt/k8sdevsubvol/
outin@docker-dev-ucsb-1:/mnt/k8sdevsubvol$ sudo mkdir testdir
outin@docker-dev-ucsb-1:/mnt/k8sdevsubvol$ sudo chmod 777 testdir
outin@docker-dev-ucsb-1:/mnt/k8sdevsubvol$ echo hi > testdir/test.file
outin@docker-dev-ucsb-1:/mnt/k8sdevsubvol$ cat testdir/test.file
hi
outin@docker-dev-ucsb-1:/mnt/k8sdevsubvol$ sudo rm -rf testdir

The commands I used to create the subvol are at https://github.nceas.ucsb.edu/NCEAS/Computing/blob/master/cephfs.md#commands-used-to-create-cephfs-subvolumes-on-the-dataone-ceph-cluter-ceph-15
I'll setup prod next.

Production is now ready and tested.
username: k8ssubvoluser
subvolgroup: k8ssubvolgroup
subvolume: k8ssubvol
subvolume path: /volumes/k8ssubvolgroup/k8ssubvol/af348873-2be8-4a99-b1c1-ed2c80fe098b
secret: /etc/ceph/ceph.client.k8ssubvoluser.keyring (on docker-ucsb-4, 5, 6, and 7)
root@docker-ucsb-4:~# mount -t ceph <IP_ADDRESS>:6789,<IP_ADDRESS>:6789,<IP_ADDRESS>:6789,<IP_ADDRESS>:6789,<IP_ADDRESS>:6789:/volumes/k8ssubvolgroup/k8ssubvol/af348873-2be8-4a99-b1c1-ed2c80fe098b /mnt/k8ssubvol -o name=
k8ssubvoluser,secretfile=/etc/ceph/k8ssubvoluser.secret
root@docker-ucsb-4:/mnt/k8ssubvol# df -Th /mnt/k8ssubvol
Filesystem                                                                                Type  Size  Used Avail Use% Mounted on
<IP_ADDRESS>:6789,<IP_ADDRESS>:6789,<IP_ADDRESS>:6789,<IP_ADDRESS>:6789,<IP_ADDRESS>:6789:/volumes/k8ssubvolgroup/k8ssubvol/af348873-2be8-4a99-b1c1-ed2c80fe098b ceph  888T     0  888T   0% /mnt/k8ssubvol
root@docker-ucsb-4:~# cd /mnt/k8ssubvol/
root@docker-ucsb-4:/mnt/k8ssubvol# mkdir testdir
root@docker-ucsb-4:/mnt/k8ssubvol# echo hi > testdir/test.file
root@docker-ucsb-4:/mnt/k8ssubvol# cat testdir/test.file
hi
root@docker-ucsb-4:/mnt/k8ssubvol# rm -rf testdir

ceph-csi for cephfs has been configured on dev k8s and metadig-engine is currently running using a persistent volume (PV) provisioned with ceph-csi. This PV uses the subvolume described above. The steps to install and configure ceph-csi the PV and persistent volume claim will be described https://github.com/DataONEorg/k8s-cluster/blob/develop/storage/Ceph/Ceph-CSI.md (I have a bit more work to do on the docs).
Although this test was done by installing and configuring ceph-csi by manually editing k8s manifest files (.yaml), the goal is to perform the install, config and updates using Helm.


Add k8s deployment, standalone app Dockerfile.

Tested with Rancher k3s and a couple of NixOS containers running tailscale clients against it.

This looks excellent to me!
@cure, what do you think?

Let's start with this :)


Paste the value by double-click on it in the Yippy popup window

As a user, I want to have the value I double-clicked on inserted so that I don't have to select it and then press cmd+V.

It's probably not what you're looking for, but you can also click the value once and then hit Enter

@meichthys I'm also suffer because of lack this feature. Could you please add it? So we can paste items just with double click. Thanks in advance!

@laazybeard I'm not the developer here and am not familiar with the code, so i don't think i can help out in adding the feature :/

@meichthys oh sorry then, I thought that you are developer of the app.