Instalation Fails python3.8

pip install sklearn-contrib-py-earth
Collecting sklearn-contrib-py-earth
Using cached sklearn-contrib-py-earth-0.1.0.tar.gz (1.0 MB)
Requirement already satisfied: scipy>=0.16 in /home/tnt/PycharmProjects/mars/lib/python3.8/site-packages (from sklearn-contrib-py-earth) (1.6.0)
Requirement already satisfied: scikit-learn>=0.16 in /home/tnt/PycharmProjects/mars/lib/python3.8/site-packages (from sklearn-contrib-py-earth) (0.24.1)
Requirement already satisfied: six in /home/tnt/PycharmProjects/mars/lib/python3.8/site-packages (from sklearn-contrib-py-earth) (1.15.0)
Requirement already satisfied: numpy>=1.13.3 in /home/tnt/PycharmProjects/mars/lib/python3.8/site-packages (from scikit-learn>=0.16->sklearn-contrib-py-earth) (1.20.1)
Requirement already satisfied: threadpoolctl>=2.0.0 in /home/tnt/PycharmProjects/mars/lib/python3.8/site-packages (from scikit-learn>=0.16->sklearn-contrib-py-earth) (2.1.0)
Requirement already satisfied: joblib>=0.11 in /home/tnt/PycharmProjects/mars/lib/python3.8/site-packages (from scikit-learn>=0.16->sklearn-contrib-py-earth) (1.0.1)
Using legacy 'setup.py install' for sklearn-contrib-py-earth, since package 'wheel' is not installed.
Installing collected packages: sklearn-contrib-py-earth
Running setup.py install for sklearn-contrib-py-earth ... error
ERROR: Command errored out with exit status 1:
command: /home/tnt/PycharmProjects/mars/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-tpbrbmff/sklearn-contrib-py-earth_55157342455949e0ab32713d54e2384c/setup.py'"'"'; file='"'"'/tmp/pip-install-tpbrbmff/sklearn-contrib-py-earth_55157342455949e0ab32713d54e2384c/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' install --record /tmp/pip-record-1nkxfk0o/install-record.txt --single-version-externally-managed --compile --install-headers /home/tnt/PycharmProjects/mars/include/site/python3.8/sklearn-contrib-py-earth
cwd: /tmp/pip-install-tpbrbmff/sklearn-contrib-py-earth_55157342455949e0ab32713d54e2384c/
Complete output (142 lines):
running install
running build
running build_py
creating build
creating build/lib.linux-x86_64-3.8
creating build/lib.linux-x86_64-3.8/pyearth
copying pyearth/earth.py -> build/lib.linux-x86_64-3.8/pyearth
copying pyearth/export.py -> build/lib.linux-x86_64-3.8/pyearth
copying pyearth/_version.py -> build/lib.linux-x86_64-3.8/pyearth
copying pyearth/init.py -> build/lib.linux-x86_64-3.8/pyearth
creating build/lib.linux-x86_64-3.8/pyearth/test
copying pyearth/test/test_forward.py -> build/lib.linux-x86_64-3.8/pyearth/test
copying pyearth/test/test_util.py -> build/lib.linux-x86_64-3.8/pyearth/test
copying pyearth/test/test_qr.py -> build/lib.linux-x86_64-3.8/pyearth/test
copying pyearth/test/test_export.py -> build/lib.linux-x86_64-3.8/pyearth/test
copying pyearth/test/test_knot_search.py -> build/lib.linux-x86_64-3.8/pyearth/test
copying pyearth/test/testing_utils.py -> build/lib.linux-x86_64-3.8/pyearth/test
copying pyearth/test/test_pruning.py -> build/lib.linux-x86_64-3.8/pyearth/test
copying pyearth/test/test_earth.py -> build/lib.linux-x86_64-3.8/pyearth/test
copying pyearth/test/init.py -> build/lib.linux-x86_64-3.8/pyearth/test
creating build/lib.linux-x86_64-3.8/pyearth/test/record
copying pyearth/test/record/test_forward_pass.py -> build/lib.linux-x86_64-3.8/pyearth/test/record
copying pyearth/test/record/test_pruning_pass.py -> build/lib.linux-x86_64-3.8/pyearth/test/record
copying pyearth/test/record/init.py -> build/lib.linux-x86_64-3.8/pyearth/test/record
creating build/lib.linux-x86_64-3.8/pyearth/test/basis
copying pyearth/test/basis/test_missingness.py -> build/lib.linux-x86_64-3.8/pyearth/test/basis
copying pyearth/test/basis/test_hinge.py -> build/lib.linux-x86_64-3.8/pyearth/test/basis
copying pyearth/test/basis/base.py -> build/lib.linux-x86_64-3.8/pyearth/test/basis
copying pyearth/test/basis/test_smoothed_hinge.py -> build/lib.linux-x86_64-3.8/pyearth/test/basis
copying pyearth/test/basis/test_basis.py -> build/lib.linux-x86_64-3.8/pyearth/test/basis
copying pyearth/test/basis/test_linear.py -> build/lib.linux-x86_64-3.8/pyearth/test/basis
copying pyearth/test/basis/test_constant.py -> build/lib.linux-x86_64-3.8/pyearth/test/basis
copying pyearth/test/basis/init.py -> build/lib.linux-x86_64-3.8/pyearth/test/basis
running egg_info
writing sklearn_contrib_py_earth.egg-info/PKG-INFO
writing dependency_links to sklearn_contrib_py_earth.egg-info/dependency_links.txt
writing requirements to sklearn_contrib_py_earth.egg-info/requires.txt
writing top-level names to sklearn_contrib_py_earth.egg-info/top_level.txt
reading manifest file 'sklearn_contrib_py_earth.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching 'pyearth/test/pathological_data'
writing manifest file 'sklearn_contrib_py_earth.egg-info/SOURCES.txt'
copying pyearth/_basis.c -> build/lib.linux-x86_64-3.8/pyearth
copying pyearth/_basis.pxd -> build/lib.linux-x86_64-3.8/pyearth
copying pyearth/_forward.c -> build/lib.linux-x86_64-3.8/pyearth
copying pyearth/_forward.pxd -> build/lib.linux-x86_64-3.8/pyearth
copying pyearth/_knot_search.c -> build/lib.linux-x86_64-3.8/pyearth
copying pyearth/_knot_search.pxd -> build/lib.linux-x86_64-3.8/pyearth
copying pyearth/_pruning.c -> build/lib.linux-x86_64-3.8/pyearth
copying pyearth/_pruning.pxd -> build/lib.linux-x86_64-3.8/pyearth
copying pyearth/_qr.c -> build/lib.linux-x86_64-3.8/pyearth
copying pyearth/_qr.pxd -> build/lib.linux-x86_64-3.8/pyearth
copying pyearth/_record.c -> build/lib.linux-x86_64-3.8/pyearth
copying pyearth/_record.pxd -> build/lib.linux-x86_64-3.8/pyearth
copying pyearth/_types.c -> build/lib.linux-x86_64-3.8/pyearth
copying pyearth/_types.pxd -> build/lib.linux-x86_64-3.8/pyearth
copying pyearth/_util.c -> build/lib.linux-x86_64-3.8/pyearth
copying pyearth/_util.pxd -> build/lib.linux-x86_64-3.8/pyearth
copying pyearth/test/earth_linvars_regress.txt -> build/lib.linux-x86_64-3.8/pyearth/test
copying pyearth/test/earth_regress.txt -> build/lib.linux-x86_64-3.8/pyearth/test
copying pyearth/test/earth_regress_missing_data.txt -> build/lib.linux-x86_64-3.8/pyearth/test
copying pyearth/test/earth_regress_smooth.txt -> build/lib.linux-x86_64-3.8/pyearth/test
copying pyearth/test/forward_regress.txt -> build/lib.linux-x86_64-3.8/pyearth/test
copying pyearth/test/test_data.csv -> build/lib.linux-x86_64-3.8/pyearth/test
UPDATING build/lib.linux-x86_64-3.8/pyearth/_version.py
set build/lib.linux-x86_64-3.8/pyearth/_version.py to '0.1.0'
running build_ext
building 'pyearth._util' extension
creating build/temp.linux-x86_64-3.8
creating build/temp.linux-x86_64-3.8/pyearth
x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/home/tnt/PycharmProjects/mars/lib/python3.8/site-packages/numpy/core/include -I/home/tnt/PycharmProjects/mars/include -I/usr/include/python3.8 -c pyearth/_util.c -o build/temp.linux-x86_64-3.8/pyearth/_util.o
In file included from /home/tnt/PycharmProjects/mars/lib/python3.8/site-packages/numpy/core/include/numpy/ndarraytypes.h:1944,
from /home/tnt/PycharmProjects/mars/lib/python3.8/site-packages/numpy/core/include/numpy/ndarrayobject.h:12,
from /home/tnt/PycharmProjects/mars/lib/python3.8/site-packages/numpy/core/include/numpy/arrayobject.h:4,
from pyearth/_util.c:495:
/home/tnt/PycharmProjects/mars/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 "
|  ^~~~~~~
pyearth/_util.c: In function ‘__Pyx__ExceptionSave’:
pyearth/_util.c:8071:21: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_type’; did you mean ‘curexc_type’?
8071 |     *type = tstate->exc_type;
|                     ^~~~~~~~
|                     curexc_type
pyearth/_util.c:8072:22: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_value’; did you mean ‘curexc_value’?
8072 |     *value = tstate->exc_value;
|                      ^~~~~~~~~
|                      curexc_value
pyearth/_util.c:8073:19: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_traceback’; did you mean ‘curexc_traceback’?
8073 |     *tb = tstate->exc_traceback;
|                   ^~~~~~~~~~~~~
|                   curexc_traceback
pyearth/_util.c: In function ‘__Pyx__ExceptionReset’:
pyearth/_util.c:8080:24: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_type’; did you mean ‘curexc_type’?
8080 |     tmp_type = tstate->exc_type;
|                        ^~~~~~~~
|                        curexc_type
pyearth/_util.c:8081:25: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_value’; did you mean ‘curexc_value’?
8081 |     tmp_value = tstate->exc_value;
|                         ^~~~~~~~~
|                         curexc_value
pyearth/_util.c:8082:22: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_traceback’; did you mean ‘curexc_traceback’?
8082 |     tmp_tb = tstate->exc_traceback;
|                      ^~~~~~~~~~~~~
|                      curexc_traceback
pyearth/_util.c:8083:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_type’; did you mean ‘curexc_type’?
8083 |     tstate->exc_type = type;
|             ^~~~~~~~
|             curexc_type
pyearth/_util.c:8084:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_value’; did you mean ‘curexc_value’?
8084 |     tstate->exc_value = value;
|             ^~~~~~~~~
|             curexc_value
pyearth/_util.c:8085:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_traceback’; did you mean ‘curexc_traceback’?
8085 |     tstate->exc_traceback = tb;
|             ^~~~~~~~~~~~~
|             curexc_traceback
pyearth/_util.c: In function ‘__Pyx__GetException’:
pyearth/_util.c:8140:24: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_type’; did you mean ‘curexc_type’?
8140 |     tmp_type = tstate->exc_type;
|                        ^~~~~~~~
|                        curexc_type
pyearth/_util.c:8141:25: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_value’; did you mean ‘curexc_value’?
8141 |     tmp_value = tstate->exc_value;
|                         ^~~~~~~~~
|                         curexc_value
pyearth/_util.c:8142:22: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_traceback’; did you mean ‘curexc_traceback’?
8142 |     tmp_tb = tstate->exc_traceback;
|                      ^~~~~~~~~~~~~
|                      curexc_traceback
pyearth/_util.c:8143:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_type’; did you mean ‘curexc_type’?
8143 |     tstate->exc_type = local_type;
|             ^~~~~~~~
|             curexc_type
pyearth/_util.c:8144:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_value’; did you mean ‘curexc_value’?
8144 |     tstate->exc_value = local_value;
|             ^~~~~~~~~
|             curexc_value
pyearth/_util.c:8145:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_traceback’; did you mean ‘curexc_traceback’?
8145 |     tstate->exc_traceback = local_tb;
|             ^~~~~~~~~~~~~
|             curexc_traceback
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
----------------------------------------
ERROR: Command errored out with exit status 1: /home/tnt/PycharmProjects/mars/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-tpbrbmff/sklearn-contrib-py-earth_55157342455949e0ab32713d54e2384c/setup.py'"'"'; file='"'"'/tmp/pip-install-tpbrbmff/sklearn-contrib-py-earth_55157342455949e0ab32713d54e2384c/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' install --record /tmp/pip-record-1nkxfk0o/install-record.txt --single-version-externally-managed --compile --install-headers /home/tnt/PycharmProjects/mars/include/site/python3.8/sklearn-contrib-py-earth Check the logs for full command output.

What are you trying to do here? Install the forked version of scikit-learn that's used for py-earth? Or are you trying to install py-earth itself?

Same error here. I tried both:

sudo pip install sklearn-contrib-py-earth (as recommended on https://machinelearningmastery.com/multivariate-adaptive-regression-splines-mars-in-python/ to install pyearth, not sklearn as far as I understand) => fail with the error above
git clone git://github.com/scikit-learn-contrib/py-earth.git && sudo python setup.py install --cythonize => fail with :
...
building 'pyearth._util' extension
creating build/temp.linux-x86_64-3.8
creating build/temp.linux-x86_64-3.8/pyearth
x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include/python3.8 -c pyearth/_util.c -o build/temp.linux-x86_64-3.8/pyearth/_util.o
In file included from /usr/lib/python3/dist-packages/numpy/core/include/numpy/ndarraytypes.h:1832,
from /usr/lib/python3/dist-packages/numpy/core/include/numpy/ndarrayobject.h:12,
from /usr/lib/python3/dist-packages/numpy/core/include/numpy/arrayobject.h:4,
from pyearth/_util.c:495:
/usr/lib/python3/dist-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 "
|  ^~~~~~~
pyearth/_util.c: In function ‘__Pyx__ExceptionSave’:
pyearth/_util.c:8071:21: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_type’; did you mean ‘curexc_type’?
8071 |     *type = tstate->exc_type;
|                     ^~~~~~~~
|                     curexc_type
pyearth/_util.c:8072:22: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_value’; did you mean ‘curexc_value’?
8072 |     *value = tstate->exc_value;
|                      ^~~~~~~~~
|                      curexc_value
pyearth/_util.c:8073:19: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_traceback’; did you mean ‘curexc_traceback’?
8073 |     *tb = tstate->exc_traceback;
|                   ^~~~~~~~~~~~~
|                   curexc_traceback
pyearth/_util.c: In function ‘__Pyx__ExceptionReset’:
pyearth/_util.c:8080:24: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_type’; did you mean ‘curexc_type’?
8080 |     tmp_type = tstate->exc_type;
|                        ^~~~~~~~
|                        curexc_type
pyearth/_util.c:8081:25: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_value’; did you mean ‘curexc_value’?
8081 |     tmp_value = tstate->exc_value;
|                         ^~~~~~~~~
|                         curexc_value
pyearth/_util.c:8082:22: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_traceback’; did you mean ‘curexc_traceback’?
8082 |     tmp_tb = tstate->exc_traceback;
|                      ^~~~~~~~~~~~~
|                      curexc_traceback
pyearth/_util.c:8083:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_type’; did you mean ‘curexc_type’?
8083 |     tstate->exc_type = type;
|             ^~~~~~~~
|             curexc_type
pyearth/_util.c:8084:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_value’; did you mean ‘curexc_value’?
8084 |     tstate->exc_value = value;
|             ^~~~~~~~~
|             curexc_value
pyearth/_util.c:8085:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_traceback’; did you mean ‘curexc_traceback’?
8085 |     tstate->exc_traceback = tb;
|             ^~~~~~~~~~~~~
|             curexc_traceback
pyearth/_util.c: In function ‘__Pyx__GetException’:
pyearth/_util.c:8140:24: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_type’; did you mean ‘curexc_type’?
8140 |     tmp_type = tstate->exc_type;
|                        ^~~~~~~~
|                        curexc_type
pyearth/_util.c:8141:25: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_value’; did you mean ‘curexc_value’?
8141 |     tmp_value = tstate->exc_value;
|                         ^~~~~~~~~
|                         curexc_value
pyearth/_util.c:8142:22: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_traceback’; did you mean ‘curexc_traceback’?
8142 |     tmp_tb = tstate->exc_traceback;
|                      ^~~~~~~~~~~~~
|                      curexc_traceback
pyearth/_util.c:8143:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_type’; did you mean ‘curexc_type’?
8143 |     tstate->exc_type = local_type;
|             ^~~~~~~~
|             curexc_type
pyearth/_util.c:8144:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_value’; did you mean ‘curexc_value’?
8144 |     tstate->exc_value = local_value;
|             ^~~~~~~~~
|             curexc_value
pyearth/_util.c:8145:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_traceback’; did you mean ‘curexc_traceback’?
8145 |     tstate->exc_traceback = local_tb;
|             ^~~~~~~~~~~~~
|             curexc_traceback
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1

I'd like to install py-earth but it fails whatever the method chosen to install it. Config. Python 3.8.6, GCC 10.2.0, sklearn 0.24.2

@shidingan Looks to be a cython issue. Ensure you have a version of cython installed that is compatible with Python 3.8

Should not be a problem of Cython version IMO because it is the version provided by my distrib with python3: cython 0.29.21 which is compatible with python3.8...

If you believe all your dependencies are correct, you can try installing from from the issue 191 branch:
git clone -b issue191 git://github.com/jcrudy/py-earth.git
cd py-earth
python setup.py install --cythonize

Alternatively, you can specify to build in-place:
git clone git://github.com/jcrudy/py-earth.git
cd py-earth
python setup.py build_ext --inplace --cythonize

I have this issue too. Here is a minimal reproducibile example:
$ : conda create -n test-pyearth python=3.8.10 -y
$ : conda activate test-pyearth
$: pip install sklearn-contrib-py-earth

I also have this problem. Python 3.7, 3.8 and 3.9. Similar error message
Collecting sklearn-contrib-py-earth
  Downloading sklearn-contrib-py-earth-0.1.0.tar.gz (1.0 MB)
     |████████████████████████████████| 1.0 MB 6.6 MB/s
Requirement already satisfied: scipy>=0.16 in /shared-libs/python3.7/py/lib/python3.7/site-packages (from sklearn-contrib-py-earth) (1.6.3)
Requirement already satisfied: scikit-learn>=0.16 in /shared-libs/python3.7/py/lib/python3.7/site-packages (from sklearn-contrib-py-earth) (0.24.2)
Requirement already satisfied: six in /shared-libs/python3.7/py-core/lib/python3.7/site-packages (from sklearn-contrib-py-earth) (1.16.0)
Requirement already satisfied: threadpoolctl>=2.0.0 in /shared-libs/python3.7/py/lib/python3.7/site-packages (from scikit-learn>=0.16->sklearn-contrib-py-earth) (2.1.0)
Requirement already satisfied: joblib>=0.11 in /shared-libs/python3.7/py/lib/python3.7/site-packages (from scikit-learn>=0.16->sklearn-contrib-py-earth) (1.0.1)
Requirement already satisfied: numpy>=1.13.3 in /shared-libs/python3.7/py/lib/python3.7/site-packages (from scikit-learn>=0.16->sklearn-contrib-py-earth) (1.19.5)
Building wheels for collected packages: sklearn-contrib-py-earth
  Building wheel for sklearn-contrib-py-earth (setup.py) ... error
  ERROR: Command errored out with exit status 1:
   command: /root/venv/bin/python -u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-sm94q7b1/sklearn-contrib-py-earth_a77e074a32a545ae9887d82e345fbab5/setup.py'"'"'; __file__='"'"'/tmp/pip-install-sm94q7b1/sklearn-contrib-py-earth_a77e074a32a545ae9887d82e345fbab5/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-zhjjplel
       cwd: /tmp/pip-install-sm94q7b1/sklearn-contrib-py-earth_a77e074a32a545ae9887d82e345fbab5/
  Complete output (145 lines):
  /root/venv/lib/python3.7/site-packages/setuptools/dist.py:694: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead
    % (opt, underscore_opt))
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib.linux-x86_64-3.7
  creating build/lib.linux-x86_64-3.7/pyearth
  copying pyearth/_version.py -> build/lib.linux-x86_64-3.7/pyearth
  copying pyearth/__init__.py -> build/lib.linux-x86_64-3.7/pyearth
  copying pyearth/export.py -> build/lib.linux-x86_64-3.7/pyearth
  copying pyearth/earth.py -> build/lib.linux-x86_64-3.7/pyearth
  creating build/lib.linux-x86_64-3.7/pyearth/test
  copying pyearth/test/test_pruning.py -> build/lib.linux-x86_64-3.7/pyearth/test
  copying pyearth/test/testing_utils.py -> build/lib.linux-x86_64-3.7/pyearth/test
  copying pyearth/test/test_earth.py -> build/lib.linux-x86_64-3.7/pyearth/test
  copying pyearth/test/__init__.py -> build/lib.linux-x86_64-3.7/pyearth/test
  copying pyearth/test/test_util.py -> build/lib.linux-x86_64-3.7/pyearth/test
  copying pyearth/test/test_forward.py -> build/lib.linux-x86_64-3.7/pyearth/test
  copying pyearth/test/test_qr.py -> build/lib.linux-x86_64-3.7/pyearth/test
  copying pyearth/test/test_export.py -> build/lib.linux-x86_64-3.7/pyearth/test
  copying pyearth/test/test_knot_search.py -> build/lib.linux-x86_64-3.7/pyearth/test
  creating build/lib.linux-x86_64-3.7/pyearth/test/record
  copying pyearth/test/record/test_forward_pass.py -> build/lib.linux-x86_64-3.7/pyearth/test/record
  copying pyearth/test/record/__init__.py -> build/lib.linux-x86_64-3.7/pyearth/test/record
  copying pyearth/test/record/test_pruning_pass.py -> build/lib.linux-x86_64-3.7/pyearth/test/record
  creating build/lib.linux-x86_64-3.7/pyearth/test/basis
  copying pyearth/test/basis/test_hinge.py -> build/lib.linux-x86_64-3.7/pyearth/test/basis
  copying pyearth/test/basis/__init__.py -> build/lib.linux-x86_64-3.7/pyearth/test/basis
  copying pyearth/test/basis/test_missingness.py -> build/lib.linux-x86_64-3.7/pyearth/test/basis
  copying pyearth/test/basis/test_smoothed_hinge.py -> build/lib.linux-x86_64-3.7/pyearth/test/basis
  copying pyearth/test/basis/test_constant.py -> build/lib.linux-x86_64-3.7/pyearth/test/basis
  copying pyearth/test/basis/test_basis.py -> build/lib.linux-x86_64-3.7/pyearth/test/basis
  copying pyearth/test/basis/test_linear.py -> build/lib.linux-x86_64-3.7/pyearth/test/basis
  copying pyearth/test/basis/base.py -> build/lib.linux-x86_64-3.7/pyearth/test/basis
  running egg_info
  writing sklearn_contrib_py_earth.egg-info/PKG-INFO
  writing dependency_links to sklearn_contrib_py_earth.egg-info/dependency_links.txt
  writing requirements to sklearn_contrib_py_earth.egg-info/requires.txt
  writing top-level names to sklearn_contrib_py_earth.egg-info/top_level.txt
  reading manifest file 'sklearn_contrib_py_earth.egg-info/SOURCES.txt'
  reading manifest template 'MANIFEST.in'
  warning: no files found matching 'pyearth/test/pathological_data'
  adding license file 'LICENSE.txt'
  writing manifest file 'sklearn_contrib_py_earth.egg-info/SOURCES.txt'
  copying pyearth/_basis.c -> build/lib.linux-x86_64-3.7/pyearth
  copying pyearth/_basis.pxd -> build/lib.linux-x86_64-3.7/pyearth
  copying pyearth/_forward.c -> build/lib.linux-x86_64-3.7/pyearth
  copying pyearth/_forward.pxd -> build/lib.linux-x86_64-3.7/pyearth
  copying pyearth/_knot_search.c -> build/lib.linux-x86_64-3.7/pyearth
  copying pyearth/_knot_search.pxd -> build/lib.linux-x86_64-3.7/pyearth
  copying pyearth/_pruning.c -> build/lib.linux-x86_64-3.7/pyearth
  copying pyearth/_pruning.pxd -> build/lib.linux-x86_64-3.7/pyearth
  copying pyearth/_qr.c -> build/lib.linux-x86_64-3.7/pyearth
  copying pyearth/_qr.pxd -> build/lib.linux-x86_64-3.7/pyearth
  copying pyearth/_record.c -> build/lib.linux-x86_64-3.7/pyearth
  copying pyearth/_record.pxd -> build/lib.linux-x86_64-3.7/pyearth
  copying pyearth/_types.c -> build/lib.linux-x86_64-3.7/pyearth
  copying pyearth/_types.pxd -> build/lib.linux-x86_64-3.7/pyearth
  copying pyearth/_util.c -> build/lib.linux-x86_64-3.7/pyearth
  copying pyearth/_util.pxd -> build/lib.linux-x86_64-3.7/pyearth
  copying pyearth/test/earth_linvars_regress.txt -> build/lib.linux-x86_64-3.7/pyearth/test
  copying pyearth/test/earth_regress.txt -> build/lib.linux-x86_64-3.7/pyearth/test
  copying pyearth/test/earth_regress_missing_data.txt -> build/lib.linux-x86_64-3.7/pyearth/test
  copying pyearth/test/earth_regress_smooth.txt -> build/lib.linux-x86_64-3.7/pyearth/test
  copying pyearth/test/forward_regress.txt -> build/lib.linux-x86_64-3.7/pyearth/test
  copying pyearth/test/test_data.csv -> build/lib.linux-x86_64-3.7/pyearth/test
  UPDATING build/lib.linux-x86_64-3.7/pyearth/_version.py
  set build/lib.linux-x86_64-3.7/pyearth/_version.py to '0.1.0'
  running build_ext
  building 'pyearth._util' extension
  creating build/temp.linux-x86_64-3.7
  creating build/temp.linux-x86_64-3.7/pyearth
  gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -I/shared-libs/python3.7/py/lib/python3.7/site-packages/numpy/core/include -I/root/venv/include -I/usr/local/include/python3.7m -c pyearth/_util.c -o build/temp.linux-x86_64-3.7/pyearth/_util.o
  In file included from /shared-libs/python3.7/py/lib/python3.7/site-packages/numpy/core/include/numpy/ndarraytypes.h:1822,
                   from /shared-libs/python3.7/py/lib/python3.7/site-packages/numpy/core/include/numpy/ndarrayobject.h:12,
                   from /shared-libs/python3.7/py/lib/python3.7/site-packages/numpy/core/include/numpy/arrayobject.h:4,
                   from pyearth/_util.c:495:
  /shared-libs/python3.7/py/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]
   #warning "Using deprecated NumPy API, disable it with " \
    ^~~~~~~
  pyearth/_util.c: In function ‘__Pyx__ExceptionSave’:
  pyearth/_util.c:8071:21: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_type’; did you mean ‘curexc_type’?
       *type = tstate->exc_type;
                       ^~~~~~~~
                       curexc_type
  pyearth/_util.c:8072:22: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_value’; did you mean ‘curexc_value’?
       *value = tstate->exc_value;
                        ^~~~~~~~~
                        curexc_value
  pyearth/_util.c:8073:19: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_traceback’; did you mean ‘curexc_traceback’?
       *tb = tstate->exc_traceback;
                     ^~~~~~~~~~~~~
                     curexc_traceback
  pyearth/_util.c: In function ‘__Pyx__ExceptionReset’:
  pyearth/_util.c:8080:24: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_type’; did you mean ‘curexc_type’?
       tmp_type = tstate->exc_type;
                          ^~~~~~~~
                          curexc_type
  pyearth/_util.c:8081:25: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_value’; did you mean ‘curexc_value’?
       tmp_value = tstate->exc_value;
                           ^~~~~~~~~
                           curexc_value
  pyearth/_util.c:8082:22: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_traceback’; did you mean ‘curexc_traceback’?
       tmp_tb = tstate->exc_traceback;
                        ^~~~~~~~~~~~~
                        curexc_traceback
  pyearth/_util.c:8083:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_type’; did you mean ‘curexc_type’?
       tstate->exc_type = type;
               ^~~~~~~~
               curexc_type
  pyearth/_util.c:8084:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_value’; did you mean ‘curexc_value’?
       tstate->exc_value = value;
               ^~~~~~~~~
               curexc_value
  pyearth/_util.c:8085:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_traceback’; did you mean ‘curexc_traceback’?
       tstate->exc_traceback = tb;
               ^~~~~~~~~~~~~
               curexc_traceback
  pyearth/_util.c: In function ‘__Pyx__GetException’:
  pyearth/_util.c:8140:24: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_type’; did you mean ‘curexc_type’?
       tmp_type = tstate->exc_type;
                          ^~~~~~~~
                          curexc_type
  pyearth/_util.c:8141:25: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_value’; did you mean ‘curexc_value’?
       tmp_value = tstate->exc_value;
                           ^~~~~~~~~
                           curexc_value
  pyearth/_util.c:8142:22: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_traceback’; did you mean ‘curexc_traceback’?
       tmp_tb = tstate->exc_traceback;
                        ^~~~~~~~~~~~~
                        curexc_traceback
  pyearth/_util.c:8143:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_type’; did you mean ‘curexc_type’?
       tstate->exc_type = local_type;
               ^~~~~~~~
               curexc_type
  pyearth/_util.c:8144:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_value’; did you mean ‘curexc_value’?
       tstate->exc_value = local_value;
               ^~~~~~~~~
               curexc_value
  pyearth/_util.c:8145:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_traceback’; did you mean ‘curexc_traceback’?
       tstate->exc_traceback = local_tb;
               ^~~~~~~~~~~~~
               curexc_traceback
  error: command 'gcc' failed with exit status 1
  ----------------------------------------
  ERROR: Failed building wheel for sklearn-contrib-py-earth
  Running setup.py clean for sklearn-contrib-py-earth
Failed to build sklearn-contrib-py-earth
Installing collected packages: sklearn-contrib-py-earth
    Running setup.py install for sklearn-contrib-py-earth ... error
    ERROR: Command errored out with exit status 1:
     command: /root/venv/bin/python -u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-sm94q7b1/sklearn-contrib-py-earth_a77e074a32a545ae9887d82e345fbab5/setup.py'"'"'; __file__='"'"'/tmp/pip-install-sm94q7b1/sklearn-contrib-py-earth_a77e074a32a545ae9887d82e345fbab5/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-u0jxin_i/install-record.txt --single-version-externally-managed --compile --install-headers /root/venv/include/site/python3.7/sklearn-contrib-py-earth
         cwd: /tmp/pip-install-sm94q7b1/sklearn-contrib-py-earth_a77e074a32a545ae9887d82e345fbab5/
    Complete output (93 lines):
    /root/venv/lib/python3.7/site-packages/setuptools/dist.py:694: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead
      % (opt, underscore_opt))
    running install
    running build
    running build_py
    running egg_info
    writing sklearn_contrib_py_earth.egg-info/PKG-INFO
    writing dependency_links to sklearn_contrib_py_earth.egg-info/dependency_links.txt
    writing requirements to sklearn_contrib_py_earth.egg-info/requires.txt
    writing top-level names to sklearn_contrib_py_earth.egg-info/top_level.txt
    reading manifest file 'sklearn_contrib_py_earth.egg-info/SOURCES.txt'
    reading manifest template 'MANIFEST.in'
    warning: no files found matching 'pyearth/test/pathological_data'
    adding license file 'LICENSE.txt'
    writing manifest file 'sklearn_contrib_py_earth.egg-info/SOURCES.txt'
    UPDATING build/lib.linux-x86_64-3.7/pyearth/_version.py
    set build/lib.linux-x86_64-3.7/pyearth/_version.py to '0.1.0'
    running build_ext
    building 'pyearth._util' extension
    creating build/temp.linux-x86_64-3.7
    creating build/temp.linux-x86_64-3.7/pyearth
    gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -I/shared-libs/python3.7/py/lib/python3.7/site-packages/numpy/core/include -I/root/venv/include -I/usr/local/include/python3.7m -c pyearth/_util.c -o build/temp.linux-x86_64-3.7/pyearth/_util.o
    In file included from /shared-libs/python3.7/py/lib/python3.7/site-packages/numpy/core/include/numpy/ndarraytypes.h:1822,
                     from /shared-libs/python3.7/py/lib/python3.7/site-packages/numpy/core/include/numpy/ndarrayobject.h:12,
                     from /shared-libs/python3.7/py/lib/python3.7/site-packages/numpy/core/include/numpy/arrayobject.h:4,
                     from pyearth/_util.c:495:
    /shared-libs/python3.7/py/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]
     #warning "Using deprecated NumPy API, disable it with " \
      ^~~~~~~
    pyearth/_util.c: In function ‘__Pyx__ExceptionSave’:
    pyearth/_util.c:8071:21: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_type’; did you mean ‘curexc_type’?
         *type = tstate->exc_type;
                         ^~~~~~~~
                         curexc_type
    pyearth/_util.c:8072:22: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_value’; did you mean ‘curexc_value’?
         *value = tstate->exc_value;
                          ^~~~~~~~~
                          curexc_value
    pyearth/_util.c:8073:19: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_traceback’; did you mean ‘curexc_traceback’?
         *tb = tstate->exc_traceback;
                       ^~~~~~~~~~~~~
                       curexc_traceback
    pyearth/_util.c: In function ‘__Pyx__ExceptionReset’:
    pyearth/_util.c:8080:24: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_type’; did you mean ‘curexc_type’?
         tmp_type = tstate->exc_type;
                            ^~~~~~~~
                            curexc_type
    pyearth/_util.c:8081:25: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_value’; did you mean ‘curexc_value’?
         tmp_value = tstate->exc_value;
                             ^~~~~~~~~
                             curexc_value
    pyearth/_util.c:8082:22: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_traceback’; did you mean ‘curexc_traceback’?
         tmp_tb = tstate->exc_traceback;
                          ^~~~~~~~~~~~~
                          curexc_traceback
    pyearth/_util.c:8083:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_type’; did you mean ‘curexc_type’?
         tstate->exc_type = type;
                 ^~~~~~~~
                 curexc_type
    pyearth/_util.c:8084:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_value’; did you mean ‘curexc_value’?
         tstate->exc_value = value;
                 ^~~~~~~~~
                 curexc_value
    pyearth/_util.c:8085:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_traceback’; did you mean ‘curexc_traceback’?
         tstate->exc_traceback = tb;
                 ^~~~~~~~~~~~~
                 curexc_traceback
    pyearth/_util.c: In function ‘__Pyx__GetException’:
    pyearth/_util.c:8140:24: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_type’; did you mean ‘curexc_type’?
         tmp_type = tstate->exc_type;
                            ^~~~~~~~
                            curexc_type
    pyearth/_util.c:8141:25: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_value’; did you mean ‘curexc_value’?
         tmp_value = tstate->exc_value;
                             ^~~~~~~~~
                             curexc_value
    pyearth/_util.c:8142:22: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_traceback’; did you mean ‘curexc_traceback’?
         tmp_tb = tstate->exc_traceback;
                          ^~~~~~~~~~~~~
                          curexc_traceback
    pyearth/_util.c:8143:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_type’; did you mean ‘curexc_type’?
         tstate->exc_type = local_type;
                 ^~~~~~~~
                 curexc_type
    pyearth/_util.c:8144:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_value’; did you mean ‘curexc_value’?
         tstate->exc_value = local_value;
                 ^~~~~~~~~
                 curexc_value
    pyearth/_util.c:8145:13: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘exc_traceback’; did you mean ‘curexc_traceback’?
         tstate->exc_traceback = local_tb;
                 ^~~~~~~~~~~~~
                 curexc_traceback
    error: command 'gcc' failed with exit status 1
    ----------------------------------------
ERROR: Command errored out with exit status 1: /root/venv/bin/python -u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-sm94q7b1/sklearn-contrib-py-earth_a77e074a32a545ae9887d82e345fbab5/setup.py'"'"'; __file__='"'"'/tmp/pip-install-sm94q7b1/sklearn-contrib-py-earth_a77e074a32a545ae9887d82e345fbab5/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-u0jxin_i/install-record.txt --single-version-externally-managed --compile --install-headers /root/venv/include/site/python3.7/sklearn-contrib-py-earth Check the logs for full command output.
WARNING: You are using pip version 21.1.2; however, version 21.1.3 is available.
You should consider upgrading via the '/root/venv/bin/python -m pip install --upgrade pip' command.

I solved installing the dev branch

Can you give the actual procedure. I do not see a dev branch.

pip install sklearn-contrib-py-earth will not work on > python 3.6. Either use the solution outlined above or the solution outlined in the comments section of the article referenced above that uses the pip install method.

Indeed, it works when cloning the repo and installing manually. What's the issue with pip?

I used the instructions in the last comment in here https://stackoverflow.com/questions/66503039/how-to-install-pyearth-in-google-colab
pip install<EMAIL_ADDRESS>

Would it be possible to make a release on PyPI? Currently a plain pip install sklearn-contrib-py-earth also fails for me under a standard Ubuntu Python 3.8 environment (fresh/empty venv).

Would it be possible to make a release on PyPI? Currently a plain pip install sklearn-contrib-py-earth also fails for me under a standard Ubuntu Python 3.8 environment (fresh/empty venv).

pip install<EMAIL_ADDRESS>

Thank you! it works.


[dashboard] add build status indicator for the dashboard

Add build status indicator for the dashboard next to other build status indicators, color-coded as follows:

green: the latest build is successful
gray: the latest build was skipped due to broken waterfall
dancing red: one of the dashboard jobs failed on a SHA that was

Fixed by https://github.com/flutter/dashboard_box/commit/412edf5f8feb9e44f10c0320c29dc583beda4ba0


Add sanitized builds in CI

We are running tests on debug and release builds now (but IIRC postgres is built in debug mode for both cases -- that should be fixed). Would be good to add 1 or more other build with asan/msan/tsan/valgrind enabled. Both rust and c code should be sanitized.

Would be good to add 1 or more other build with valgrind enabled

This is going to be difficult; we use pg_ctl through the zenith binary to start the postgres backends that we need in the tests.
To run tests on valgrind-enabled builds, we would need to wrap / start the postgres cluster through valgrind, which pg_ctl (and the zenith cli utility) do not seem to support, and modifying either would require rewriting of those utilities.

To run tests on valgrind-enabled builds, we would need to wrap / start the postgres cluster through valgrind, which pg_ctl (and the zenith cli utility) do not seem to support, and modifying either would require rewriting of those utilities.

Fair enough. Yes, let's treat valgrind as a different task then

On 5 October 2021 17:46:28 EEST, MMeent @.***> wrote:

Would be good to add 1 or more other build with valgrind enabled

This is going to be difficult; we use pg_ctl through the zenith binary to start the postgres backends that we need in the tests.

I've been slightly annoyed by that too when I've wanted to run postgres with the 'rr' debugger. Similar to valgrind, it requires launching the binary with 'rr record '. Could we have e.g. an env variable to pass a prefix to the command when we launch postgres?

Heikki


Take optional filename argument in download

To redefine path where font is generated, for example, font/fontName.otf to place font to a directory

Thanks!


[Feature] allow submit rayjob when some worker nodes pending

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
when building a large scale of ray cluster in a rayjob, k8s may run out of resouces which causes some worker nodes pending.In this case, the ray cluster can already run job but rayjob think it is initializing, the job will wait for cluster util healthy. Can we add a available replicas to indicate that the cluster now can submit job even if cluster scale not meets the expected replicas , not just hang the job.
Use case
submit job as soon as possible not just hang to improve resouce usage in k8s
Related issues
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

cc @harryge00 @Jeffwan
I'm personally a bit behind on the status of RayJob support.

It does seems reasonable to allow a job to get started before resources are fully provisioned.

I wonder also if a tool like https://github.com/IBM/multi-cluster-app-dispatcher could help with ensuring that resources are available before submitting a job.

It does seems reasonable to allow a job to get started before resources are fully provisioned.

Now in ray-cluster's WorkerGroupSpec, there have MinReplicas and MaxReplicas. This actually indicates that ray cluster could run with elastic size for one job.

This can be solved by #1631. Close this one.


Update bundle to 4.8.4 (candidate channel)

/retest

/retest

retest this please

Fwiw, this has migrated to latest https://mirror.openshift.com/pub/openshift-v4/x86_64/clients/ocp/latest-4.8/


Update TOC.yml

Docs Build status updates of commit 4237bd2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Odata-docs/TOC.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


⚠ Everything Hub has degraded performance

In fa3f4c1, Everything Hub (https://hub.everythingbagel.me) experienced degraded performance:

HTTP code: 200
Response time: 7137 ms

Resolved: Everything Hub performance has improved in f2c365a after 5 minutes.


Wrongly infers any[] from Array.prototype.flat, Array.prototype.concat

TypeScript Version:  3.2.4, 3.3.0-dev.20190126
Search Terms: array, flat, concat, any, unsound
Code
const a: boolean[] = [[17], ["foo"]].flat();  // wrongly accepted
const b: boolean[] = Array.prototype.concat([17], [19], [21]);  // wrongly accepted

Using tsc --strict -t esnext.
(What I’m really trying to do: find a type safe way to concatenate an array of arrays. It’d be nice if [].concat(...arrays) were accepted, which I think would be a consequence of #26976, but that’s not the issue I’m reporting here. arrays.flat() and Array.prototype.concat(...arrays) are accepted but apparently provide no type safety.)
Expected behavior: [[17], ["foo"]].flat() should be typed (number | string)[] (if it’s accepted at all), and Array.prototype.concat([17], [19], [21]) should be typed number[]. In both cases the assignment to boolean[] should be rejected.
Actual behavior: TypeScript infers any[] for both right hand sides (even with --noImplicitAny implied by --strict), and accepts the assignments to boolean[] with no complaints.
Playground Link: Playground doesn’t support esnext, but here’s the second line.
Related Issues: #19535 for concat (but that one may have more to do with the difficulty of typing concat’s weird behavior when non-arrays are passed?), #26976

@andersk @fatcerberus any interest in writing a TL;DR of this thread?

The goalposts didn’t move as a result of the discussion AFAIK, the issue is still as described in the OP.

I happened to end up with a similar problem when playing with Metaprogramming https://github.com/Microsoft/TypeScript/issues/14833#issuecomment-460820626

Ran into what I would consider a related issue involving flatMap over at #31033, and ended coming up with a solution that essentially does the same as what @shicks has suggested here (i.e. using a conditional type with inference).
I also ran into this issue, so here's my version of a fix for flat() / flat(1) specifically (that's the overload I and most others probably care about):
interface Array<T> {
  flat<U>(this:
    ReadonlyArray<U>,
    depth?: 1
  ): (U extends ReadonlyArray<infer V> ? V : U)[];
}


LLaMA LoRA INT4 model outputs empty strings

The base model for LLaMA INT4 basically outputs empty strings everytime. For the script below -
from xturing.datasets.instruction_dataset import InstructionDataset
from xturing.models import BaseModel
import sys

# Initializes the model
model = BaseModel.create("llama_lora_int4")
output = model.generate(texts=["Why LLM models are becoming so important?"])
print("Generated output by the model: {}".format(output))

The output is  -
Generated output by the model: [' ']
Even with xturing chat command - xturing chat -m llama_lora_int4, the output is this

I am also having the same issue


rancher/shell setting not applied ?

Hi Rancher community,
First of all, thanks for your awesome work!
Please find a strange behavior below :)
Rancher Server Setup

Rancher version: 2.6.3
Installation option Helm chart on k8s 1.21
Proxy/Cert Details: no specific proxy

Information about the Cluster

Kubernetes version: 1.21
Cluster Type (Local/Downstream): Local and Imported (K3S, GKE, AKS)

User Information

What is the role of the user logged in? Admin/Cluster

Describe the bug
The aim is to use a custom shell for users through the UI.
I used the CLI to customize the shell-image parameter:
rancher settings set shell-image snahelou22/rch-shell-flux:0.1.14
( The image is just the rancher shell official image extended with FluxCD cli. )
$ rancher settings get shell-image
ID            NAME          VALUE                              DEFAULT                 CUSTOMIZED
shell-image   shell-image   snahelou22/rch-shell-flux:0.1.14   rancher/shell:v0.1.14   true

Everything is working fine on Local cluster

$ k get pods -n cattle-system -l pod-impersonation.cattle.io/token -o jsonpath='{.items..spec.containers..image}'
snahelou22/rch-shell-flux:0.1.14 snahelou22/rch-shell-flux:0.1.14

But not for other clusters. The dashboard-shell pod is still using the default value.
$ k get pods -n cattle-system -l pod-impersonation.cattle.io/token -o jsonpath='{.items..spec.containers..image}'
rancher/shell:v0.1.14 rancher/shell:v0.1.14

I tried to restart rancher server pods, cattle-cluster-agent on imported clusters but the setting is still ignored.
Do you have any idea ?
BR

Running into this too, seems related to the issue you linked

Bump

Bump


Generate betacoronavirus fastq files for user download

Description
This builds on #282 for IDSEQ-2600. We want to enable a special download for coronavirus. This change will generate a new pair of fastqs by filtering on the given taxid for coronavirus. It is very similar to https://github.com/chanzuckerberg/idseq-dag/pull/162/files .
Note the fastqs will be hidden from the list of downloads in the UI. I will be exposing them through a custom bulk download type. We can unhide them later as well if we want.
Version

[x] I have increased the appropriate version number in https://github.com/chanzuckerberg/idseq-dag/blob/master/idseq_dag/init.py. Guidelines here: https://github.com/chanzuckerberg/idseq-dag/blob/pr-template/README.md#release-notes
[x] I have added release notes for my new version to https://github.com/chanzuckerberg/idseq-dag/blob/master/README.md#release-notes
[x] I will push a git tag after merging in the form vX.Y.Z

Tests

[x] I have verified that the pipeline still completes successfully:

[ ] for single-end inputs
[x] for paired-end inputs
[ ] for FASTQ inputs
[ ] for FASTA inputs.

[x] I have validated that my change does not introduce any correctness bugs to existing output types.
[x] I have validated that my change does not introduce significant performance regressions or I have discussed with the team that the benefits of the change are substantial enough that we're comfortable accepting the size of the measured performance penalty.

Notes

#162 matched only on species taxid. I feel it's better to match on genus as well for generality. Taxids are tax level specific so there is no risk of mismatch.

I added type checks for clarity

#162 makes the output filename like betacoronavirus__RR004_water_2_S23A_R1_001.fastq, unlike the other fastqs for example nonhost_R1.fastq. It may be nice to make the others like nonhost__RR004_water_2_S23A_R1_001.fastq.

It should only run on demand when a user actually requests the betacoronavirus download type

Why is that an important requirement? At this point it seems easier to implement the fastq logic where we are generated the nonhost fastqs, as in the #162 . Is it to get started on IDSEQ-2599?

It should only run on demand when a user actually requests the betacoronavirus download type

Why is that an important requirement? At this point it seems easier to implement the fastq logic where we are generate the nonhost fastqs, as in the #162 . Is it to get started on IDSEQ-2599?

Because otherwise all the pipeline jobs are doing a bunch of potentially time-consuming work that is of zero relevance for 99% of users? :) Why would we pull out betacoronavirus reads for users that are not studying betacoronavirus?

Ok, I was interpreting "on demand" as part of a bulk download request. I agree that making it contingent on use_taxon_whitelist is a good idea. My question was about generating the betacoronavirus fastqs in the pipeline vs in bulk downloads.

Ok, I was interpreting "on demand" as part of a bulk download request. I agree that making it contingent on use_taxon_whitelist is a good idea. My question was about generating the betacoronavirus fastqs in the pipeline vs in bulk downloads.

Ah got it! Yes, as you pointed out, it seemed that encapsulating everything in the bulk download job would pave the way towards https://jira.czi.team/browse/IDSEQ-2599, where we won't know the taxid of interest upfront. But if you make the current change contingent on use_taxon_whitelist, that seems good enough for the current purpose!

I'll make change then here to use_taxon_whitelist, and start on the web PR to add the download type. And in #282 we just need to decide whether to limit it to use_taxon_whitelist as well.

I'll make change then here to use_taxon_whitelist, and start on the web PR to add the download type. And in #282 we just need to decide whether to limit it to use_taxon_whitelist as well.

Yes, let's definitely limit #282 to use_taxon_whitelist!

I know I was the one who wrote  #162 but I think it's much preferable to use names like betacoronavirus_R1.fastq as opposed to RR004_water_2_S23A_R1_001.fastq, for reasons of security and reduction of unnecessary complexity. Do you mind changing it? Apologies if my old PR misled you!

Changed the naming and now I will merge into #282 .


Changed flcbdfWrappers.pxd file for OSX fix

Moved the block
cdef extern from "FullDataFile.h" namespace "Daetk":                                                                                cdef cppclass FullDataFile:                                                                                FullDataFile(const double t0, const char* filename)
to the top of the flcbdfWrappers.pxd for fix on macOS.

@davidbrochart and @ejtovar this builds and runs fine on both osx (conda) and linux (conda and hashdist), but pytest is having some sort of issue on the osx build environment on travis. @ejtovar can you run pytest locally as it's run in  .travis.yml?

@tridelat and @zhang-alvin this adds an osx stage to travis and fixes a weird header ordering issue with the pxd. Also, it updates the stack to the latest master, which I've been using for months. I think it can go in.


Do not require validate_assignment to use Field.frozen

Change Summary
I find it a bit unusual to have the following working:
from pydantic import BaseModel, Field

class Model(BaseModel):
    a: int = 1
    model_config = {"frozen": True}

m = Model()
m.a = 2
#> Raises ValidationError

But not the following:
from pydantic import BaseModel, Field

class Model(BaseModel):
    a: int = Field(frozen=True)

m = Model(a=1)
m.a = 2
#> No ValidationError, unless model_config.validate_assignment is set to True

If you think the current behavior is as designed, I can revert my commit but I think a note on the Field.frozen docstring would be required.
Checklist

[ ] The pull request title is a good summary of the changes - it will be used in the changelog
[ ] Unit tests for the changes exist
[ ] Tests pass on CI
[ ] Documentation reflects the changes where applicable
[ ] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

It is intended behavior. The second example will work if config['validate_assignment'] = True. You can find it in the example in doc.
Probably we can improve the the docstring and documentation here

Then should the first example I gave follows the same idea (requiring validate_assignment=True)? As I feel this is a bit inconsistent

Please review


Markdown generation fails if solution contains AADUser (virtual) table

Describe the bug
We have a solution that utilizes the Azure Active Directory user table for Dataverse.
When generating the Markdown files, the generation fails at the step where the solution md file is being generated (to be more precise at the step where it is processing the customizations.xml). I've checked the exact point and it seems to be when it tries to process the virtual AADUser table.
The error message is: Security error. Error message: Sequence contains no elements. If needed I can provide the full screenshot of the error log, however I'm on mobile submitting this bug right now as I can't easily login to GitHub from my corporate device.
When I compare normal custom tables with the virtual AADUser table in the customizations.xml, I can see that the AADUser table only contains the <Name> and <RibbonDiffXml> tags and nothing else (no <EntityInfo>, <FormXml> or <SavedQueries>).
I assume that's why the error occurs as the generation tries to process the details of the table but there aren't any because it's a virtual table. Interestingly the Word generation works though - probably because it processes the customizations.xml differently 😉
To Reproduce
Steps to reproduce the behavior:

Create a new blank solution
Add the AADUsers virtual table into the solution
Export solution as Zip file
Generate the Markdown documentation with PowerDocu

Expected behavior
I'm not sure what exactly to expect. In the Word generation it just displays blank tables - I suppose this could be a quick and simple approach also for the Markdown generation (basically implementing some sort of skip / catch when processing a virtual table).
Virtual tables are quite new to us and we've only used the predefined AADUser table so far in our solutions - maybe other virtual tables behave the same way or completely different. In any case it would need to be further investigated to identify the exact documentation needs for virtual tables and how to approach them.

Hi Niqlash, thanks for the detailed write up! This has just been fixed and will be included in the next release

This should be fixed as part of the 2.0.0 release. Please reopen again in case this is still happening


Not getting good results using pretrained model

Thanks for open sourcing the code :)
I ran the pre-trained resnet-SAM model on the complete CAT2000 trainSet and caculated the mean CC. For me it is coming to be 0.65 which is much less than the test CC mentoined on MIT Saliency page (0.89).
I ran the model exactly as described in the README and am using this repo for CC metrics.
Is there something I am missing?

Hi @karandwivedi42,
thanks for downloading our code.
For the CAT2000 dataset, we fine-tuned our model, pre-trained on the SALICON, on the CAT2000 training set. We randomly selected 200 images as validation set (10 for each category) and we resized all images to 180 x 320.

Thanks a lot!
Also, I would be really grateful if you could tell what these 3 parameters should be for CAT2000 images.
Thanks again!

The other parameters are as follow:
`shape_r = 180
shape_c = 320
shape_r_gt = 23
shape_c_gt = 40
shape_r_fix = 360
shape_c_fix = 640
upsampling_factor = 16`
As you can see, due to memory occupation, we decided to not use the originally image size of the CAT2000 dataset. In fact, images from this dataset have all the same size of 1080 x 1920, which is a little too big. However, we brought our predictions to this size before the evaluation.
Additionaly, we use a Lambda layer before returning the output of the model (after the upsampling):
outs_up = Lambda(prepare_output, prepare_output_shape)(outs_up)
where the two functions are as follow:
`def prepare_output(x):
return x[:, :, :shape_r_fix, :]
def prepare_output_shape(s):
return s[:2] + (shape_r_fix, shape_c_fix)`
Hope it works now!

Thanks a lot :)


tracing: fixes C++ compilation issue

When tracing_cpu_stats.h is included by C++ file it will not compile
and link correctly due to missing #ifdef __cplusplus directives
in the header file.
Fixes #23072
Signed-off-by: Dariusz Lisik<EMAIL_ADDRESS>

@jhedberg FYI


feat: Add parse methods to all score implementations

Is there a reason why we're adding this?

Is there a reason why we're adding this?

Cause Score classes in Java has parse and it is extremely convenient for deserialization from score string?

Any chance we could call those Java solver methods under the hood, instead of duplicating the code?

Any chance we could call those Java solver methods under the hood, instead of duplicating the code?

No; these are pure Python objects so they can be handled by Python libraries


Skeleton for download excel file page

#18

user interface to select multiple mappings
submit selection to server and receive an Excel file back in response for download

Looks good, you might have to merge main in after the changes I made in previous PR


Long == Int64?

I thought that a long was Int64 - in which case the max value for long should be 9,223,372,036,854,775,807

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

ID: 262486b8-5d80-2c0b-f2eb-40c86aaf6a61
Version Independent ID: 26b45954-2bcc-263f-7522-0c72941141bb
Content: Integer Limits
Content Source: docs/cpp/integer-limits.md
Product: visual-cpp
GitHub Login: @mikeblome
Microsoft Alias: mblome

In MSVC, both long and int are 32-bits types. I know that isn't true of all C++ implementations, but that's because it's something the standard leaves up to implementers. If you need a 64-bit integer, long long is that size in MSVC, or you can use one of the portable definitions from <cstdint>, such as int64_t.


Make Code PEP8 compliant

The current code is not as per PEP8 guidelines:

Make the code to follow PEP8 coding standards.
http://pep8online.com/checkresult

solved in #10

Thanks @GregorGrasselli


Installation fails on Windows

Installing on windows doesn't work quite out of the box. npm i https://github.com/ArupAus/authenticate --save
results in
npm ERR! code EBADPLATFORM
npm ERR! notsup Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm ERR! notsup Valid OS:    darwin
npm ERR! notsup Valid Arch:  any
npm ERR! notsup Actual OS:   win32
npm ERR! notsup Actual Arch: x64

I was able to get around this with a simple -f on the command, but might be worth updating the readme and/or moving fsevents to optional dependecies

@jaredstock What versions of node (node --version) and npm (npm --version) are you using?
When installing on Windows with node v10.13.0 and npm v6.4.1 (that older npm version seems to have snuck in via Arup's default Anacoda install), I'm seeing:
...
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
...

For general interest, using npm i -ddd reveals:
npm sill saveTree   `--<EMAIL_ADDRESS>...
npm sill saveTree     +--<EMAIL_ADDRESS>npm sill saveTree     | `--<EMAIL_ADDRESS>...
npm sill saveTree     |   +--<EMAIL_ADDRESS>
i.e. fs-events comes in transitively via the above chain.
A few additional thoughts:

watchpack@2 betas have removed chokidar while 1.6.0 still uses it
I also suspect webpack (and its CLI) shouldn't need to be a dependency, just a devDependency.

I'm using node 11.5.0 and npm 6.4.1


how to run on windows???

hello how to run bot on windows?

Hello and bye @brantje

Use the wiki, it has instructions for this 👍


Fixes syntax typo in DirectManipulation section of docs

Fixing JSX tag in DirectManipulation section of the docs

By analyzing the blame information on this pull request, we identified @sunnylqm and @bestander to be potential reviewers.

@tegon updated the pull request.

@facebook-github-bot shipit

Thanks for importing. If you are an FB employee go to Phabricator to review.


Show item thumbnail on Start tiles for folders or libraries pinned to Start

Is your feature request related to a problem?
Currently, the default folder icon is shown on tiles for folders pinned to the Start Menu.
Describe the solution
Since we are moving towards using the built in thumbnails in other parts of Files, the same should be done for Start tiles. This would be more like what Windows Explorer does for pinned folders. This will also make it easier for users to differentiate folders.
This could be accomplished by getting two different sizes of the thumbnail, scaling them to match the standard scale for icons, then saving them to the local folder eg LocalState\Tiles so that they can be used as assets for Start tiles. A shadow effect could (may be unnecessary) also be added using Win2D.
Describe alternatives you've considered
Keep showing standard folder image.
Scope

Capability
Priority

This proposal will use folder thumbnails as assets for items pinned to the Start menu
Must

Add shadow effect to the thumbnail
Could

Additional comment
Files tile vs Explorer tile

Open questions
Should the tile images be updated in case the icon has been changed (eg. user has installed update with sun valley icons)? If so how often?

@winston-de I'd rather not include a copy of the built-in icons, is it possible to set the path to the shell icon?

This wouldn't be including a copy of them in Files, it would just create a copy of the image obtained through GetThumbnailAsync in the local folder. Also no, I don't think it's possible to do that. The only way I know of for providing assets is by providing an appx path to either an item included in the app  or in the local state folder.

This wouldn't be including a copy of them in Files, it would just create a copy of the image obtained through GetThumbnailAsync in the local folder.

That's fine, I just didn't want to include it with the source.

@yaichenbaum

@winston-de do you want to work on this?

I'd like to keep the behavior consistent even when Files isn't the default. Closing this for now but we can revisit if something changes.

@winston-de what are your thoughts on using the shell api for exe files as that doesn't depend on the default file manager?


[Add-to-app] Flutter view controller crashes when the debugger is not attached

Attached crash report.
ios-app  25-01-21, 12-43 PM.txt
Steps to Reproduce

A simple Hello World native App.
A flutter module with just a standard counter screen from the code lab.
Integrated the module with the native iOS app using cocoapods. (Option A)
Display the Flutter view controller. Copied code from the sample.

The app runs fine running from xcode. However, When the same app is launched after disconnecting from the debugger the app, crashes.

flutter analyze output
Analyzing flutter_module...
No issues found! (ran in 2.4s)

flutter doctor -v output below
[✓] Flutter (Channel stable, 1.22.5, on Mac OS X 10.15.7 19H2 darwin-x64, locale en-IN)
    • Flutter version 1.22.5 at /Users/akshayhegde/Repos/flutter
    • Framework revision<PHONE_NUMBER> (7 weeks ago), 2020-12-10 11:54:40 -0800
    • Engine revision ae90085a84
    • Dart version 2.10.4

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/akshayhegde/Library/Android/sdk
    • Platform android-29, build-tools 29.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode-12.3.0.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.1

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin installed
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.18.1

[✓] Connected device (1 available)
    • Akshay’s iPhone (mobile) • 00008030-xxxxxxxxxxxxxxxE • ios • iOS 14.3

• No issues found!

Hi @akshaynhegde
Thanks for filing the issue, I can reproduce the crash, I suspect this is because https://github.com/flutter/flutter/issues/60657#issuecomment-702307040

flutter doctor -v
[✓] Flutter (Channel stable, 1.22.5, on macOS 11.1 20C69 darwin-x64, locale en-GB)
    • Flutter version 1.22.5 at /Users/tahatesser/Code/flutter_stable
    • Framework revision<PHONE_NUMBER> (7 weeks ago), 2020-12-10 11:54:40 -0800
    • Engine revision ae90085a84
    • Dart version 2.10.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Volumes/Extreme/SDK
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Volumes/Extreme/SDK
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.1

[!] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.18.1

[✓] Connected device (2 available)
    • IN2011 (mobile)            • c9d8ee0c                             • android-arm64 • Android 11 (API 30)
    • iPhone 12 Pro Max (mobile) • DC25925E-876C-4CFE-A2F7-0640782D22A5 • ios           • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)

! Doctor found issues in 1 category.

[✓] Flutter (Channel master, 1.26.0-13.0.pre.144, on macOS 11.1 20C69 darwin-x64, locale en-GB)
    • Flutter version 1.26.0-13.0.pre.144 at /Users/tahatesser/Code/flutter_master
    • Framework revision 2007186d2e (16 hours ago), 2021-01-24 12:54:00 -0800
    • Engine revision fdddf87080
    • Dart version 2.12.0 (build 2.12.0-253.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Volumes/Extreme/SDK
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Volumes/Extreme/SDK
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.18.1

[✓] Connected device (4 available)
    • IN2011 (mobile)            • c9d8ee0c                             • android-arm64  • Android 11 (API 30)
    • iPhone 12 Pro Max (mobile) • DC25925E-876C-4CFE-A2F7-0640782D22A5 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                • darwin-x64     • macOS 11.1 20C69 darwin-x64
    • Chrome (web)               • chrome                               • web-javascript • Google Chrome 88.0.4324.96

• No issues found!

Thank you

Hi @akshaynhegde
Thanks for filing the issue, I can reproduce the crash, I suspect this is because https://github.com/flutter/flutter/issues/60657#issuecomment-702307040

flutter doctor -v
[✓] Flutter (Channel stable, 1.22.5, on macOS 11.1 20C69 darwin-x64, locale en-GB)
    • Flutter version 1.22.5 at /Users/tahatesser/Code/flutter_stable
    • Framework revision<PHONE_NUMBER> (7 weeks ago), 2020-12-10 11:54:40 -0800
    • Engine revision ae90085a84
    • Dart version 2.10.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Volumes/Extreme/SDK
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Volumes/Extreme/SDK
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.1

[!] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.18.1

[✓] Connected device (2 available)
    • IN2011 (mobile)            • c9d8ee0c                             • android-arm64 • Android 11 (API 30)
    • iPhone 12 Pro Max (mobile) • DC25925E-876C-4CFE-A2F7-0640782D22A5 • ios           • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)

! Doctor found issues in 1 category.

[✓] Flutter (Channel master, 1.26.0-13.0.pre.144, on macOS 11.1 20C69 darwin-x64, locale en-GB)
    • Flutter version 1.26.0-13.0.pre.144 at /Users/tahatesser/Code/flutter_master
    • Framework revision 2007186d2e (16 hours ago), 2021-01-24 12:54:00 -0800
    • Engine revision fdddf87080
    • Dart version 2.12.0 (build 2.12.0-253.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Volumes/Extreme/SDK
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Volumes/Extreme/SDK
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.18.1

[✓] Connected device (4 available)
    • IN2011 (mobile)            • c9d8ee0c                             • android-arm64  • Android 11 (API 30)
    • iPhone 12 Pro Max (mobile) • DC25925E-876C-4CFE-A2F7-0640782D22A5 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                • darwin-x64     • macOS 11.1 20C69 darwin-x64
    • Chrome (web)               • chrome                               • web-javascript • Google Chrome 88.0.4324.96

• No issues found!

Thank you

/cc @jmagman

/cc @jmagman

Launching debug mode applications without Xcode attached is not supported. Building the same app in release or profile mode should work fine. The default application template should display an error message indicating the same. But, since engines can be launched via the Flutter ObjC Embedder APIs, this application seems to have gotten into a fatal crash.
So, while this is not supported, I am repurposing this issue to investigate how to make the error message more actionable.

Launching debug mode applications without Xcode attached is not supported. Building the same app in release or profile mode should work fine. The default application template should display an error message indicating the same. But, since engines can be launched via the Flutter ObjC Embedder APIs, this application seems to have gotten into a fatal crash.
So, while this is not supported, I am repurposing this issue to investigate how to make the error message more actionable.

cc @xster for error messaging.

cc @xster for error messaging.

@akshaynhegde I re-visited the issue and checked it on the latest Flutter stable version 3.19.5, using this sample code but couldn't reproduce the crash. Or maybe I misunderstand the steps.

When the same app is launched after disconnecting from the debugger the app, crashes.

If you still experience the issue, could you please elaborate on this?


mbpfan: improve description, resolves #32266

Motivation for this change
See #32266. /cc @davidak
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg eval
(sorry for the noise, master was broken by a merge)

@yegortimoshenko i would also put "on all MacBook/MacBook Pros (probably all Apple computers)" and "using the applesmc module" in the description. That might be keywords people search for.
See https://github.com/dgraziotin/mbpfan

I don't like copying description from upstream :-)
I've checked mbpfan source code and all it relies on is applesmc module, which is indeed present in all Macs and MacBooks. I've ended up with "mbpfan, fan controller daemon for Apple Macs and MacBooks".

I've tried nixos-rebuild with this patch and it still evaluates.


SQLite Update to get it closer to Postgres with ecto.

I'm bringing the discussion here, changes so far and work todo

[x] DISTINCT is supported, just not column wise, need to check that distinct is called like MYSQL with distinct: true only

[x] remove order by code I added

[x] Converted JSON types to TEXT
[x] Added Proper casing to REALS
[x] Adding parens around sub commands for consistency with Postgres. (NOT union/except/intersect)
[x] STARTED adding actual errors when users try to use some unsupported features. This is incomplete.

[x] DROP Index
[x] Unsupported column type
[x] Joins not supported with CTE
[x] LOCKs not supported in general, CTE's as well
[x] UPDATE with joins
[x] ALTER table stuff has lots of unsupported behaviors

[x] Finish the "in" support tests
[x] Check I didn't miss any tests from the OLD connection test.
[x] Check the MYSQL tests to see if I have any others there that are relevant.

Exciting.

@jeregrine how's this coming along?

@warmwaffles I fixed the merge conflicts but integration tests will continue to fail until a new ecto version is cut with this in it https://github.com/elixir-ecto/ecto/pull/4083

Ah no problem then. Let's wait for them to cut a new version. There shouldn't be too many merge conflicts until then.

I want to give you all the credit for the work you did here. When I squash merge #107, it will consolidate under @fredwu's name.
What I can do is just bump to ecto 3.10, then you rebase this on top. Then @fredwu rebase his work after we merge your work @jeregrine.
How does that sound?

Actually @jeregrine let me just squash merge this and @fredwu can just rebase on top.


Allow using multiple nodes with use_click_away

I am implementing a component consisting of two part: a toggle and some content. The content is shows using a portal.
I do want to use use_click_away, but actually both elements (the toggle and the portal content) should be considered "inside". This works when not using portals by wrapping with an additional element. However, this strategy fails when using portals.
If use_click_away would accept an array of nodes instead, I would be able to define two (or more) nodes as "inside" and it would work.
Let me know if you want me to work on a PR for this.

I didn't test for portal usage, I will take a look for portal since portal is common for model dialogs etc.


Gatsby Site Starter Landing Page Error

Describe the bug
After deploying the gatsby site starter to netlify, the landing page preview shows this error:
ReferenceError: Can't find variable: ___loader
To Reproduce

Go to https://www.netlifycms.org/docs/start-with-a-template/
Click on Deploy to Netlify under Gatsby Site Starter
Follow instructions to create/build site
Go to <your-site>.netlify.com/admin
Click on pages in the left panel, then landing page

Expected behavior
The preview loads and there is no error
Screenshots

Applicable Versions:

netlify-cms-app 2.9.6
netlify-cms-core 2.12.1
Git provider: GitHub
OS: MacOS Mojave
Browser version Safari 12.0.3

Additional context
All files are default, I haven't altered any code nor saved any changes in the cms editor, just followed the instructions to get a gatsby site up

This seems to be localized to safari, the actual landing page of the site loads fine, it's only in the admin preview of the page.
I just tried firefox and chrome and it works as expected. I did hard refresh, empty caches, etc. on safari and the error still shows

It isn't Safari, worked for me (in 12.1.1) following the steps, but the error is present in the console - looks to be gatsby-link, which it seems we're erroneously importing into the landing page preview template. Porting this to the starter repo.


Difference in object creation

in rust-cpython:
PyDict::new  -> PyDict
PyTuple::new  -> PyTuple

in pyo3:
PyDict::new  -> &PyDict
PyTuple::new  -> Py<PyTuple>

Why such difference? And if I use PyDict::new in a function how do I return PyDict? &PyDict causes lifetime errors.

In pyo3 you can not own python objects like PyDict, PyTuple or custom classes because of safety.
Python requires GIL to access any c-api, so it is natural to express GIL lifetime with rust lifetimes.
when you get reference &PyDict it lifetime is the same as GIL lifetime. so it is possible statically
guarantee proper usage of GIL.
rust-cpython on other hand does not enforce GIL lifetime with rust lifetimes,
so you have to explicitly pass Python<'p> to every method call,
even for custom classes rust-cpython generates methods that accepts Python<'p>
this
in pyo3, if you need to store python object, you have two options, you can convert &PyDict into PyObject or convert it to Py<PyDict>. Both just pointers, but Py<PyDict> contains type information.  if you need to return it back to python, you can do .into() or just return reference,
pyo3 is able to convert both to *mut PyObject.
here are examples:
fn my_fun1(&PyString, &PyDict) -> PyResult<&PyDict> {
    PyDict::new(s.py())
}

fn my_fun2(s: &PyString, &PyDict) -> PyResult<Py<PyDict>> {
    let d = PyDict::new(s.py());
    Ok(d.into())
}

fn my_fun3(s: &PyString, &PyDict) -> PyResult<PyObject> {
    let d = PyDict::new(s.py());
    Ok(d.into())
}

because pyo3 does not require Python<'p> in method calls, it is possible to
use standard library traits like std::convert::From or ?, etc.
does it make sense?

Yes, thank you for answer.

Marking this as future documentation improvements.


Add custom types and api connection in donor-portal

I am not sure how to get the pledgedPercentage to render the aid packages based on "Goal Pending" and "Goal Reached" state of the packages.

Closing this because the ticket was pick up by @nipuna777


Update boost to 1.74

Checklist

[X] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[X] Reset the build number to 0 (if the version changed)
[X] 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.

The Rubin software stack does not currently build with boost 1.74.

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.

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.

This has been included in #17 .


Add error state for http poison

Add Error condition for httppoison errors.
Unfortunately, we need to return these errors differently bc when HTTPoison errors out, it doesn't return us a response (because there isn't one)

I'm going to add a follow up PR in the main repo that handles these new errors

🚢  not a blocker, just spitballing. i wonder if there is some way we can consolidate this, maybe with a macro or some fancy meta programming. anyway -- ship it! do we need to bump the version? i forget. i believe i bumped the version in a minor way, but did not release it, with my last PR. now that you've added some behavior (with the webhooks) and now this stuff, i think we can bump the middle number x.y.z -> x.y+1.0

@teedang19 That is an interesting idea re: meta programming. Something to tank on. I can do a version bump and release following this PR 👍


Can I use the RxDB instead of IDB in nohost?

idb is a bit slow when there are many image files in the folder.
I know Rxdb is more faster than idb so can I use Rxdb in this module?

You could try. I'm not maintaining this code anymore.

Ok.


Sth like this could be spotted by the docs-builder

https://github.com/symfony/symfony-docs/pull/11032
https://github.com/symfony/symfony-docs/pull/11030

I'm closing this as "won't fix" because I don't see any way in this could be automated. Many times, the references refer to old headlines which we reworded. So, we can't remove them because that'd break the links with anchors.
Thanks.


Get TryMyUI to review 50/50 mobile/desktop

50% of worldwide traffic is mobile.
Our #1 app, Dmail, doesn't even work on mobile. That means our App Mining rankings are not a good reflection of real user value.

@jasperjansz can you please add more detail to this? Who would review? How would they test? How would scores be generated? How will you prevent gaming? Thx.

@jasperjansz think this may be a good idea, but need more details.

While web apps can be designed to adapt to a wide range of devices and screen sizes, TMUI typically reviews web apps on larger displays. Hence, app mining doesn't provide incentive for developers to spend the extra resources on making web apps responsive so they also work well on smaller screens like mobile.

I should say what more than 40% of our users are coming from mobile, and I think it should be done as it is not 2010 anymore, and mobile compatibility is a must.
I suggest that TMUI aks 4 out of 10 of the testers to use mobile browsers (not resizing desktop browsers) so they can check the experience truthfully.
It may need more work from the TMUI side, but it will make sure that as NIL said about every app should support all major browsers, I think it should be the same for Mobile browsers too.


Migration fix for new query type

This PR is to fix the panel migrations for the non-query created clock panels.  It will also cleanup the (angular) configs if they are found outside of the config block.
Other modifications:

Forces yarn V1
Updates to node 20
Bumps min Grafana version to 8.3+ (was 8.0)

TODO:

[x] Migrates old panels and cleans up
[x] Updates create-plugin changes
[x] Adds basic playwright config (simple setup)

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

almost ready with this one, the migration tests ironed out some issues, but still need to test some real instances with dashboards that are throwing the error, and also with query-enabled clocks.

we'll need to update the docs in another PR, would like to get this fix out the door asap.

Fixes #189
Fixes #186


Cannot save the sheet

Hello,
I tried to save the sheet but it didn't work. I saw that the "raw" directory was missing causing the "No such file or directory" error. After I created it, I had no more problems.

How did you install the package? Did you use pip? Where did you create it?

I used pip. I got this error :
https://github.com/MatthiasLienhard/flowkey_dl/issues/5#issuecomment-752677830

The intention is that the raw directory is created during installation using pip - for me it works, no idea why it does not on other systems. If you find a hint whats missing please let me know and I'll add it.

The intention is that the raw directory is created during installation using pip - for me it works, no idea why it does not on other systems. If you find a hint whats missing please let me know and I'll add it.

Should be fixed in v0.0.3


Feature/move documents endpoint to nested

With this PR, the base shipment's documents enpoint has been changed from /api/v1/documents/ to /api/v1/shipments/{shipment_id}/documents/. The old endpoint has been deleted altogether and once approved, the documents creation and update will be performed respectively on:

/api/v1/shipments/{shipment_id}/documents/
/api/v1/shipments/{shipment_id}/documents/{document_id}/
The Swagger documentation has been updated to reflect these changes as well as the postman collection

Now that it is required to use the shipment path to access the documents, is there a reason for the shipment_id to be in the body for the document? It seems like it makes more sense to just grab the shipment_pk from the kwargs and add it in to a copy of the request.data

Good point James. The only issue I see will be that the django request.data have a special data structure for security reasons, see: https://docs.djangoproject.com/en/2.1/ref/request-response/#django.http.QueryDict
Adding a field data manually might break the serializer.


Paul/bug timedelta_2_seconds

There seems to be an error regarding the unit of fractional_seconds that was in [ns] instead of [s].

Closing this old PR.


Update meetups.json

Added Einundzwanzig Potsdam. Telegram-Link ("https://t.me/Einundzwanzig_Potsdam") was too long for being accepted. Now it's just "https://t.me/Einundzwanzig_Potsd"

Closing in favor of #99


change fromEvent to allow element of any type

this function can take a wide range of types for element as seen from docs: https://github.com/Reactive-Extensions/RxJS/blob/master/doc/api/core/operators/fromevent.md
"element (Any): The DOMElement, NodeList, jQuery element, Zepto Element, Angular element, Ember.js element or EventEmitter to attach a listener. For Backbone.Marionette this would be the application or an EventAggregator object."

@TrevorDev thanks mate!


why requiring python 3.9?

Any specific reason? I am struggling to install all the packages on a Raspberry, a lower version would be much easier. Is there any reason?

The docker container also uses 3.8, which for me runs fine with Binance. Btw, running docker (or podman) is probably easier than installing python yourself.

FYI. Ok, I managed to have it installed and running on a Raspberry 4 with Python 3.7. I just needed to install the required packages and sudo apt-get install libatlas-base-dev to fix an issue when importing numpy.

Great, thanks for the update and glad you got it working.


Fix wsgi to use env settings

Right now WSGI points to the module init file that contains nothing so no settings are set. This replicates manage.py to give wsgi.py the same settings file to use.
@kave

approved


Unnecessary high memory usage prevents using larger batch sizes.

Hey,
I have been doing various experiments with distributed and single node training and I noticed the following:
Using the default settings from the examples/training I am able to reach about 38000 WPS (with gradient dropping) during training on 8x Pascal Titan X. However I noticed that I was using just 4461 MB of the 12 GBs available on the GPU.
Now if I change a few things (-w 7000 --mini-batch 512 --maxi-batch 768, up from 300, 64 and 100 respectively) ) I am able to utilize a lot more memory (11137 MB) during training and reach 45500  WPS (averaged over a whole epoch).
However there is a crash during evaluation:
[2017-07-10 07:34:37] Ep. 1 : Up. 9000 : Sen. 2289954 : Cost 65.95 : Time 125.54s : 50420.62 words/s
[2017-07-10 07:35:29] Seen 2395954 samples
[2017-07-10 07:35:29] Starting epoch 2
[2017-07-10 07:35:29] [data] Shuffling files
[2017-07-10 07:35:40] [data] Done
[2017-07-10 07:37:10] Ep. 2 : Up. 10000 : Sen. 147799 : Cost 62.97 : Time 153.75s : 41551.93 words/s
[2017-07-10 07:37:11] Saving model to model/model.iter10000.npz
[2017-07-10 07:37:12] Saving model to model/model.npz
[2017-07-10 07:37:13] [memory] Extending reserved space to 7680 MB (device 3)
[2017-07-10 07:37:17] [memory] Extending reserved space to 14848 MB (device 3)
terminate called after throwing an instance of 'thrust::system::system_error'
terminate called recursively
terminate called recursively
  what():  after cub_::DeviceRadixSort::SortKeys(0): an illegal memory access was encountered

@tomekd suggests it's related to the computational graph being loaded a second time to calculate cross entropy. It should really be possible to swap out the currently unused GPU memory to RAM and then return it so that we can fully utilize the available GPU memory. This is not only a problem of the batch size, this sets an artificial limit of the size of the models trained.
Cheers,
Nick

Nope. This is not what is happening (my guess). What's more likely is that the validation set contains sentences that are longer than the training set sentences, so it needs more memory for the forward step. The validation step is not using any additional memory by itself (at least that's what I remember, it should be reusing all graph instances already).
However, this is what --dynamic-batching is for. Set the memory as high as possible and do not worry about the rest. Leave mini-batch at the default, because dynamic-batching is currently not being used during validation, so choose a smaller batch size to avoid the above issue.

BTW. maxi-batch size is just a muliplier for how many batches should be preloaded and sorted together from the corpus, it does not affect batch-size, it may only how a batch is filled.

And another comment, higher WPS is not necessarily better here. Take into account that larger batch size may very well mean slower convergence.

Yes, I am aware of the slower convergence issue. I'm trying to find a sweet spot.
I found that I can get better performance without hurting convergence with --mini-batch 128. With --mini-batch 192 (both of them with dynamic batching), i get even better performance with convergence delayed by one epoch, resulting in the same training time.
Also I found that when --dynamic-batching is omitted, --mini-batch and --maxi-batch are ignored (or at the very least they revert to the default according to the LOG info)

Yes, mini-batch is ignored with dynamic-batching as it should be, maxi-batch is not being ignored, or it should not. Can you verify this?
The sentence "With --mini-batch 192 (both of them with dynamic batching)" makes no sense? After all-mini-batch is ignored with dynamic batching (only used for validation)

I think we misunderstood each other: This is with dynamic batching and manually specifying minibatch.

Ok. So what we actually need here is a second option, something like --mini-batch-valid 64 to set the validation batch size independently.

So is the argument being ignored the second case or...?

--mini-batch will not affect actual mini-batch size if --dynamic-batching is used, it will however be used for validation and during calculating the amount of sentences to preload, as this is the product of mini-batch and maxi-batch.
Since with larger mini-batch the number of preloaded sentences increases it can affect training speed, because more sentences means better sorting according to target length which can increase WPS.
The issue reported here is caused by the fact that the large mini-batch meets long sentences that exceed the capped sentence length during training. There is no cap for validation as it should validate on the full validation set. Hence a second mini-batch option would solve that.

Ok, but why is --mini-batch not recognized when used by itself?

Is there a model.npz.yml file in the folder?

Wait... that's a bash error! Everything after the comment is ignored, isn't it?

Ugh, yeah, my bad... I thought bash didn't have multiline comments...

Anyway, having --mini-batch-valid 64 probably makes sense.

Definitely. It would certainly make things less confusing and it'd make it easy to do convergence experiments with batch size growth.

Option --valid-mini-batch is added with 713865c6ff36c20fafba7fc71f33dd4e373f1aad. It forces the mini-batch size, so that --mini-batch-words and --dynamic-batching are not used for validation any more. It's consistent with how translation and rescoring work.

@XapaJIaMnu Can you test this?

Yes, sorry for the delay. It seems to be working now.
Cheers,
Nick

Great, actually just had to use it myself. Thanks, @snukky


Sanitize Group links

The group link may contain whitespace due to user not being able to decide whether to put space after / before comma or not.
We should make sure the links do not contain whitespace.
https://github.com/oss2019/naarad/blob/72acc72c13dfe382d842ee614f60062df6ba4876/src/main.py#L36

okk sir

sorry sir i could not understand about this issue??
i mean if user inputs the following the result would be same and will open the group page...

"https://www.facebook.com/groups/DevCIndore"
"https://www.facebook.com/groups/DevCIndore/"
"https://www.facebook.com/groups/DevCIndore/       "
"https://www.facebook.com/groups/DevCIndore    "

Yes, but what about " https://www.facebook.com/groups/DevCIndore".
Apart from this, we want to store it in an appropriate manner in order to avoid any complications.


fix: add start and end column to Annotation

According to https://developer.github.com/v3/checks/runs/#annotations-object start_column and end_column are part of the Annotation
Additionally I noticed blob_href is no longer listed on the docs. Should I remove it in this PR or raise another?
https://github.com/google/go-github/pull/1241/files#diff-065d35fd95f6db43a7395a47966b9505R54

Thank you, @gauntface!
Merging.


Build Your First Automation Using Excel SDK of SAP Build Process Automation

This tutorial for about
Step 2
Use Excel Link in your Excel automations
This is failing and getting below error:
I guess there are some updates in process which are not included in tutorials.

@r3ksk Is there any update on given issue?