text:
Cannot install nlm-ingestor

Linux Mint. I tried to run !pip install nlm-ingestor in a notebook or pip install nlm-ingestor in a terminal but it always fails. Below the output that I get in an existing conda environment. Looks like it has issues with pandas. I tried a new clean conda environment without other packages, it then has issues with thinc, even if I install the latest version of thinc.
Collecting nlm-ingestor
Using cached nlm_ingestor-0.1.7-py3-none-any.whl.metadata (8.4 kB)
Collecting flask (from nlm-ingestor)
Using cached flask-3.1.0-py3-none-any.whl.metadata (2.7 kB)
Collecting flask-restful (from nlm-ingestor)
Using cached Flask_RESTful-0.3.10-py2.py3-none-any.whl.metadata (1.0 kB)
Collecting flask-jsonpify (from nlm-ingestor)
Using cached Flask-Jsonpify-1.5.0.tar.gz (3.0 kB)
Preparing metadata (setup.py) ... done
Collecting gunicorn (from nlm-ingestor)
Using cached gunicorn-23.0.0-py3-none-any.whl.metadata (4.4 kB)
Collecting werkzeug (from nlm-ingestor)
Using cached werkzeug-3.1.3-py3-none-any.whl.metadata (3.7 kB)
Collecting tika (from nlm-ingestor)
Using cached tika-2.6.0.tar.gz (27 kB)
Preparing metadata (setup.py) ... done
Collecting bs4 (from nlm-ingestor)
Using cached bs4-0.0.2-py2.py3-none-any.whl.metadata (411 bytes)
Collecting nltk (from nlm-ingestor)
Using cached nltk-3.9.1-py3-none-any.whl.metadata (2.9 kB)
Collecting python-magic (from nlm-ingestor)
Using cached python_magic-0.4.27-py2.py3-none-any.whl.metadata (5.8 kB)
Requirement already satisfied: numpy in /home/denis/miniconda3/envs/langchain/lib/python3.12/site-packages (from nlm-ingestor) (1.26.4)
Requirement already satisfied: tqdm in /home/denis/miniconda3/envs/langchain/lib/python3.12/site-packages (from nlm-ingestor) (4.67.1)
Collecting symspellpy>=6.7.0 (from nlm-ingestor)
Using cached symspellpy-6.7.8-py3-none-any.whl.metadata (3.9 kB)
Requirement already satisfied: pandas>=1.2.4 in /home/denis/miniconda3/envs/langchain/lib/python3.12/site-packages (from nlm-ingestor) (2.2.3)
Collecting mistune==2.0.3 (from nlm-ingestor)
Using cached mistune-2.0.3-py2.py3-none-any.whl.metadata (1.5 kB)
Collecting lxml==4.9.1 (from nlm-ingestor)
Using cached lxml-4.9.1.tar.gz (3.4 MB)
Preparing metadata (setup.py) ... done
Collecting unidecode (from nlm-ingestor)
Using cached Unidecode-1.3.8-py3-none-any.whl.metadata (13 kB)
Collecting nlm-utils (from nlm-ingestor)
Using cached nlm_utils-0.1.2-py3-none-any.whl.metadata (5.5 kB)
Requirement already satisfied: python-dateutil>=2.8.2 in /home/denis/miniconda3/envs/langchain/lib/python3.12/site-packages (from pandas>=1.2.4->nlm-ingestor) (2.9.0.post0)
Requirement already satisfied: pytz>=2020.1 in /home/denis/miniconda3/envs/langchain/lib/python3.12/site-packages (from pandas>=1.2.4->nlm-ingestor) (2024.2)
Requirement already satisfied: tzdata>=2022.7 in /home/denis/miniconda3/envs/langchain/lib/python3.12/site-packages (from pandas>=1.2.4->nlm-ingestor) (2024.2)
Collecting editdistpy>=0.1.3 (from symspellpy>=6.7.0->nlm-ingestor)
Using cached editdistpy-0.1.5-cp312-cp312-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (7.9 kB)
Requirement already satisfied: beautifulsoup4 in /home/denis/miniconda3/envs/langchain/lib/python3.12/site-packages (from bs4->nlm-ingestor) (4.12.3)
Requirement already satisfied: Jinja2>=3.1.2 in /home/denis/miniconda3/envs/langchain/lib/python3.12/site-packages (from flask->nlm-ingestor) (3.1.4)
Collecting itsdangerous>=2.2 (from flask->nlm-ingestor)
Using cached itsdangerous-2.2.0-py3-none-any.whl.metadata (1.9 kB)
Requirement already satisfied: click>=8.1.3 in /home/denis/miniconda3/envs/langchain/lib/python3.12/site-packages (from flask->nlm-ingestor) (8.1.7)
Collecting blinker>=1.9 (from flask->nlm-ingestor)
Using cached blinker-1.9.0-py3-none-any.whl.metadata (1.6 kB)
Requirement already satisfied: MarkupSafe>=2.1.1 in /home/denis/miniconda3/envs/langchain/lib/python3.12/site-packages (from werkzeug->nlm-ingestor) (3.0.2)
Collecting aniso8601>=0.82 (from flask-restful->nlm-ingestor)
Using cached aniso8601-9.0.1-py2.py3-none-any.whl.metadata (23 kB)
Requirement already satisfied: six>=1.3.0 in /home/denis/miniconda3/envs/langchain/lib/python3.12/site-packages (from flask-restful->nlm-ingestor) (1.16.0)
Requirement already satisfied: packaging in /home/denis/miniconda3/envs/langchain/lib/python3.12/site-packages (from gunicorn->nlm-ingestor) (24.2)
Collecting aiohttp==3.8.5 (from nlm-utils->nlm-ingestor)
Using cached aiohttp-3.8.5.tar.gz (7.4 MB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Collecting dateparser (from nlm-utils->nlm-ingestor)
Using cached dateparser-1.2.0-py2.py3-none-any.whl.metadata (28 kB)
Collecting dnspython==2.1.0 (from nlm-utils->nlm-ingestor)
Using cached dnspython-2.1.0-py3-none-any.whl.metadata (1.9 kB)
Collecting word2number (from nlm-utils->nlm-ingestor)
Using cached word2number-1.1.zip (9.7 kB)
Preparing metadata (setup.py) ... done
Collecting minio==7.1.0 (from nlm-utils->nlm-ingestor)
Using cached minio-7.1.0-py3-none-any.whl.metadata (4.2 kB)
Collecting money==1.3.0 (from nlm-utils->nlm-ingestor)
Using cached money-1.3.0.tar.gz (18 kB)
Preparing metadata (setup.py) ... done
Collecting msgpack==1.0.2 (from nlm-utils->nlm-ingestor)
Using cached msgpack-1.0.2.tar.gz (123 kB)
Preparing metadata (setup.py) ... done
Collecting nltk (from nlm-ingestor)
Using cached nltk-3.6.2-py3-none-any.whl.metadata (2.9 kB)
INFO: pip is looking at multiple versions of nlm-utils to determine which version is compatible with other requirements. This could take a while.
Collecting nlm-utils (from nlm-ingestor)
Using cached nlm_utils-0.1.1-py3-none-any.whl.metadata (5.4 kB)
Collecting pandas>=1.2.4 (from nlm-ingestor)
Using cached pandas-2.2.3-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (89 kB)
Using cached pandas-2.2.2-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (19 kB)
Using cached pandas-2.2.1-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (19 kB)
INFO: pip is still looking at multiple versions of nlm-utils to determine which version is compatible with other requirements. This could take a while.
Using cached pandas-2.2.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (19 kB)
Using cached pandas-2.1.4-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (18 kB)
Using cached pandas-2.1.3-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (18 kB)
INFO: This is taking longer than usual. You might need to provide the dependency resolver with stricter constraints to reduce runtime. See https://pip.pypa.io/warnings/backtracking for guidance. If you want to abort this run, press Ctrl + C.
Using cached pandas-2.1.2-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (18 kB)
Using cached pandas-2.1.1-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (18 kB)
Using cached pandas-2.1.0.tar.gz (4.3 MB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Installing backend dependencies ... done
Preparing metadata (pyproject.toml) ... error
error: subprocess-exited-with-error
× Preparing metadata (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [107 lines of output]
+ meson setup /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/.mesonpy-yp756y_1/build -Dbuildtype=release -Db_ndebug=if-release -Db_vscrt=md --vsenv --native-file=/tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/.mesonpy-yp756y_1/build/meson-python-native-file.ini
The Meson build system
Version: 1.0.1
Source dir: /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f
Build dir: /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/.mesonpy-yp756y_1/build
Build type: native build
Project name: pandas
Project version: 2.1.0
C compiler for the host machine: cc (gcc 11.4.0 "cc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0")
C linker for the host machine: cc ld.bfd 2.38
C++ compiler for the host machine: c++ (gcc 11.4.0 "c++ (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0")
C++ linker for the host machine: c++ ld.bfd 2.38
Cython compiler for the host machine: cython (cython 0.29.37)
Host machine cpu family: x86_64
Host machine cpu: x86_64
Program python found: YES (/home/denis/miniconda3/envs/langchain/bin/python3.12)
Found pkg-config: /usr/bin/pkg-config (0.29.2)
Build targets in project: 53
  pandas 2.1.0

    User defined options
      Native files: /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/.mesonpy-yp756y_1/build/meson-python-native-file.ini
      buildtype   : release
      b_ndebug    : if-release
      b_vscrt     : md

  Found ninja-1.11.1.git.kitware.jobserver-1 at /tmp/pip-build-env-5_yw6dxk/normal/bin/ninja
  + /tmp/pip-build-env-5_yw6dxk/normal/bin/ninja
  [1/151] Generating pandas/_libs/index_class_helper_pxi with a custom command
  [2/151] Generating pandas/_libs/algos_common_helper_pxi with a custom command
  [3/151] Generating pandas/_libs/hashtable_class_helper_pxi with a custom command
  [4/151] Generating pandas/_libs/intervaltree_helper_pxi with a custom command
  [5/151] Generating pandas/_libs/algos_take_helper_pxi with a custom command
  [6/151] Generating pandas/_libs/khash_primitive_helper_pxi with a custom command
  [7/151] Generating pandas/_libs/sparse_op_helper_pxi with a custom command
  [8/151] Generating pandas/_libs/hashtable_func_helper_pxi with a custom command
  [9/151] Generating pandas/__init__.py with a custom command
  [10/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/tslibs/base.pyx
  [11/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/tslibs/ccalendar.pyx
  [12/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/tslibs/np_datetime.pyx
  [13/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/tslibs/dtypes.pyx
  [14/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/tslibs/nattype.pyx
  [15/151] Compiling C object pandas/_libs/tslibs/base.cpython-312-x86_64-linux-gnu.so.p/meson-generated_pandas__libs_tslibs_base.pyx.c.o
  [16/151] Linking target pandas/_libs/tslibs/base.cpython-312-x86_64-linux-gnu.so
  [17/151] Compiling C object pandas/_libs/tslibs/parsing.cpython-312-x86_64-linux-gnu.so.p/.._src_parser_tokenizer.c.o
  [18/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/arrays.pyx
  [19/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/tslibs/timezones.pyx
  [20/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/indexing.pyx
  [21/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/hashing.pyx
  [22/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/tslibs/parsing.pyx
  [23/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/tslibs/fields.pyx
  [24/151] Compiling C object pandas/_libs/tslibs/ccalendar.cpython-312-x86_64-linux-gnu.so.p/meson-generated_pandas__libs_tslibs_ccalendar.pyx.c.o
  [25/151] Linking target pandas/_libs/tslibs/ccalendar.cpython-312-x86_64-linux-gnu.so
  [26/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/tslibs/strptime.pyx
  [27/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/tslibs/vectorized.pyx
  [28/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/tslibs/conversion.pyx
  [29/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/tslibs/timedeltas.pyx
  [30/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/tslibs/timestamps.pyx
  [31/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/tslibs/tzconversion.pyx
  [32/151] Compiling C object pandas/_libs/indexing.cpython-312-x86_64-linux-gnu.so.p/meson-generated_pandas__libs_indexing.pyx.c.o
  [33/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/tslibs/offsets.pyx
  [34/151] Linking target pandas/_libs/indexing.cpython-312-x86_64-linux-gnu.so
  [35/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/tslibs/period.pyx
  [36/151] Compiling C object pandas/_libs/tslibs/np_datetime.cpython-312-x86_64-linux-gnu.so.p/meson-generated_pandas__libs_tslibs_np_datetime.pyx.c.o
  [37/151] Linking target pandas/_libs/tslibs/np_datetime.cpython-312-x86_64-linux-gnu.so
  [38/151] Compiling C object pandas/_libs/arrays.cpython-312-x86_64-linux-gnu.so.p/meson-generated_pandas__libs_arrays.pyx.c.o
  [39/151] Linking target pandas/_libs/arrays.cpython-312-x86_64-linux-gnu.so
  [40/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/internals.pyx
  [41/151] Compiling C object pandas/_libs/tslibs/dtypes.cpython-312-x86_64-linux-gnu.so.p/meson-generated_pandas__libs_tslibs_dtypes.pyx.c.o
  [42/151] Linking target pandas/_libs/tslibs/dtypes.cpython-312-x86_64-linux-gnu.so
  [43/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/index.pyx
  [44/151] Compiling C object pandas/_libs/tslibs/nattype.cpython-312-x86_64-linux-gnu.so.p/meson-generated_pandas__libs_tslibs_nattype.pyx.c.o
  [45/151] Compiling C object pandas/_libs/lib.cpython-312-x86_64-linux-gnu.so.p/src_parser_tokenizer.c.o
  [46/151] Linking target pandas/_libs/tslibs/nattype.cpython-312-x86_64-linux-gnu.so
  [47/151] Compiling C object pandas/_libs/pandas_datetime.cpython-312-x86_64-linux-gnu.so.p/src_vendored_numpy_datetime_np_datetime.c.o
  FAILED: pandas/_libs/pandas_datetime.cpython-312-x86_64-linux-gnu.so.p/src_vendored_numpy_datetime_np_datetime.c.o
  cc -Ipandas/_libs/pandas_datetime.cpython-312-x86_64-linux-gnu.so.p -Ipandas/_libs -I../../pandas/_libs -I../../../../pip-build-env-5_yw6dxk/overlay/lib/python3.12/site-packages/numpy/_core/include -I../../pandas/_libs/include -I/home/denis/miniconda3/envs/langchain/include/python3.12 -fvisibility=hidden -fdiagnostics-color=always -DNDEBUG -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=c99 -O3 -DNPY_NO_DEPRECATED_API=0 -DNPY_TARGET_VERSION=NPY_1_21_API_VERSION -fPIC -MD -MQ pandas/_libs/pandas_datetime.cpython-312-x86_64-linux-gnu.so.p/src_vendored_numpy_datetime_np_datetime.c.o -MF pandas/_libs/pandas_datetime.cpython-312-x86_64-linux-gnu.so.p/src_vendored_numpy_datetime_np_datetime.c.o.d -o pandas/_libs/pandas_datetime.cpython-312-x86_64-linux-gnu.so.p/src_vendored_numpy_datetime_np_datetime.c.o -c ../../pandas/_libs/src/vendored/numpy/datetime/np_datetime.c
  ../../pandas/_libs/src/vendored/numpy/datetime/np_datetime.c: In function ‘get_datetime_metadata_from_dtype’:
  ../../pandas/_libs/src/vendored/numpy/datetime/np_datetime.c:946:52: error: ‘PyArray_Descr’ {aka ‘struct _PyArray_Descr’} has no member named ‘c_metadata’
    946 |     return (((PyArray_DatetimeDTypeMetaData *)dtype->c_metadata)->meta);
        |                                                    ^~
  ../../pandas/_libs/src/vendored/numpy/datetime/np_datetime.c:947:1: warning: control reaches end of non-void function [-Wreturn-type]
    947 | }
        | ^
  [48/151] Compiling C object pandas/_libs/hashing.cpython-312-x86_64-linux-gnu.so.p/meson-generated_pandas__libs_hashing.pyx.c.o
  [49/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/missing.pyx
  [50/151] Compiling C object pandas/_libs/tslibs/timezones.cpython-312-x86_64-linux-gnu.so.p/meson-generated_pandas__libs_tslibs_timezones.pyx.c.o
  [51/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/lib.pyx
  [52/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/interval.pyx
  [53/151] Compiling C object pandas/_libs/tslibs/conversion.cpython-312-x86_64-linux-gnu.so.p/meson-generated_pandas__libs_tslibs_conversion.pyx.c.o
  [54/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/hashtable.pyx
  [55/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/groupby.pyx
  [56/151] Compiling C object pandas/_libs/tslibs/vectorized.cpython-312-x86_64-linux-gnu.so.p/meson-generated_pandas__libs_tslibs_vectorized.pyx.c.o
  [57/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/algos.pyx
  [58/151] Compiling C object pandas/_libs/tslibs/fields.cpython-312-x86_64-linux-gnu.so.p/meson-generated_pandas__libs_tslibs_fields.pyx.c.o
  [59/151] Compiling C object pandas/_libs/tslibs/tzconversion.cpython-312-x86_64-linux-gnu.so.p/meson-generated_pandas__libs_tslibs_tzconversion.pyx.c.o
  [60/151] Compiling Cython source /tmp/pip-install-i098cnnr/pandas_06b681c6c3f9456ab03597e6eb58aa4f/pandas/_libs/join.pyx
  [61/151] Compiling C object pandas/_libs/tslibs/strptime.cpython-312-x86_64-linux-gnu.so.p/meson-generated_pandas__libs_tslibs_strptime.pyx.c.o
  [62/151] Compiling C object pandas/_libs/tslibs/parsing.cpython-312-x86_64-linux-gnu.so.p/meson-generated_pandas__libs_tslibs_parsing.pyx.c.o
  [63/151] Compiling C object pandas/_libs/internals.cpython-312-x86_64-linux-gnu.so.p/meson-generated_pandas__libs_internals.pyx.c.o
  [64/151] Compiling C object pandas/_libs/tslibs/timedeltas.cpython-312-x86_64-linux-gnu.so.p/meson-generated_pandas__libs_tslibs_timedeltas.pyx.c.o
  [65/151] Compiling C object pandas/_libs/tslibs/period.cpython-312-x86_64-linux-gnu.so.p/meson-generated_pandas__libs_tslibs_period.pyx.c.o
  [66/151] Compiling C object pandas/_libs/tslibs/timestamps.cpython-312-x86_64-linux-gnu.so.p/meson-generated_pandas__libs_tslibs_timestamps.pyx.c.o
  [67/151] Compiling C object pandas/_libs/tslibs/offsets.cpython-312-x86_64-linux-gnu.so.p/meson-generated_pandas__libs_tslibs_offsets.pyx.c.o
  [68/151] Compiling C object pandas/_libs/index.cpython-312-x86_64-linux-gnu.so.p/meson-generated_pandas__libs_index.pyx.c.o
  ninja: build stopped: subcommand failed.
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

any updates
not able to solve it

Hello @Denis-Kazakov, So I have tried this with python3.9 and also the docker image that they have either should work. You can find the below steps which I have followed.
NLM Ingestor Setup
Python (Locally)

Create a python environment

python3.9 -m venv nlm-ingestor

Install the required python packages

pip install nlm-ingestor llmsherpa ipython

Additionally run the below code for installing nltk

import nltk
nltk.download('punkt')
nltk.download('stopwords')

Run the ingestor

python -m nlm_ingestor.ingestion_daemon

Expected output

INFO:__main__:Starting ingestor service..
 * Serving Flask app '__main__'
 * Debug mode: off
INFO:werkzeug:WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
 * Running on all addresses (0.0.0.0)
 * Running on http://127.0.0.1:5001
 * Running on http://10.10.1.62:5001
INFO:werkzeug:Press CTRL+C to quit

Docker

Pull the docker image

docker pull ghcr.io/nlmatics/nlm-ingestor:latest

Run the docker image mapping the port 5001 to port of your choice

docker run -p 5001:5001 ghcr.io/nlmatics/nlm-ingestor:latest

Expected output

 * Serving Flask app '__main__'
 * Debug mode: off
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
 * Running on all addresses (0.0.0.0)
 * Running on http://127.0.0.1:5001
 * Running on http://172.17.0.2:5001
Press CTRL+C to quit

repo: nlmatics/nlm-ingestor


text:
Allow hex numbers

Allowing hexadecimal numbers for integer constants would be very useful.  This would be a JSON extension, but as far as I can tell it wouldn't change the interpretation of any valid JSON syntax, just allow correctly parsing a format that is currently invalid.

I am against implementing JSON extensions, because such extensions break interoperability.
(Sorry, but creating JSON output with hexadecimal numbers is a problem in the first place)

source: gharchive/issue

authors: ianmccul nlohmann

repo: nlohmann/json

license: MIT

license_type: permissive

license_source: github-api


text:
in vs can't find linkageId

string payload = "{\"linkageId\":\"L.4028044806278569\",\"conditions\":{\"content\":[{\"op\":0,\"beginTimeSpan\":\"\",\"isHeartbeatTrigger\":0,\"serialNum\":0,\"delayTime\":0,\"rid\":\"13.1.85\",\"type\":16,\"value\":\"1\",\"did\":\"lumi.158d00010fd68d\",\"endTimeSpan\":\"\"}],\"relation\":\"0\"},\"actions\":{\"content\":[{\"duration\":1800,\"serialNum\":0,\"autoReset\":0,\"increase_value\":0,\"delayTime\":0,\"priority\":5,\"rid\":\"4.1.85\",\"type\":2,\"value\":\"2\",\"did\":\"lumi.158d0001254584\",\"onTriggerResetDelay\":0}]}}";

json linkage_pack = payload;
string linkageID = linkage_pack["linkageId"];
//================
json linkage_pack = json::parse(payload.c_str());
string linkageID = linkage_pack["linkageId"];
it's ok

json linkage_pack = json::parse(payload.c_str());
string linkageID = linkage_pack["linkageId"];
it's ok

You can also just json::parse(payload) - there is no need to call c_str().

authors: lumigit nlohmann


text:
Implement more flexible updateMessage

With these changes, it's possible to update message attachments
and other parameters the chat.update provides.

Thanks for the input! You're right. I was too quick to hack something together to make my use case work and didn't take time to understand your API correctly 😅
I'll update this PR with a sane solution as soon as I have time

Need also attachments at UpdateMessage

Anyway I can send advanced message using this method?

@rrupesh you need to be more specific about what you're trying to accomplish.
but it should be pretty straight forward if you spend the time to read what SendMessage does and how it interacts with the higher order functions like PostMessage.

source: gharchive/pull-request

authors: JamiKarvanen baba2k james-lawrence rrupesh

repo: nlopes/slack

license_source: bigquery


text:
RecursionError in PorterStemmer._is_consonant

RecursionError occurs in PorterStemmer._is_consonant when trying to stem a word containing 'yyyyyyy....'.
If the length of 'yyyyyyy....' is larger than the maximum recursion depth, PorterStemmer cannot stem the word.
>> from nltk.stem import PorterStemmer
>>> stemmer = PorterStemmer()
>>> stemmer.stem('y'*10000)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/ubuntu/.pyenv/versions/anaconda3-5.1.0/lib/python3.6/site-packages/nltk/stem/porter.py", line 667, in stem
    stem = self._step1c(stem)
  File "/home/ubuntu/.pyenv/versions/anaconda3-5.1.0/lib/python3.6/site-packages/nltk/stem/porter.py", line 421, in _step1c
    else original_condition
  File "/home/ubuntu/.pyenv/versions/anaconda3-5.1.0/lib/python3.6/site-packages/nltk/stem/porter.py", line 268, in _apply_rule_list
    if condition is None or condition(stem):
  File "/home/ubuntu/.pyenv/versions/anaconda3-5.1.0/lib/python3.6/site-packages/nltk/stem/porter.py", line 411, in nltk_condition
    return len(stem) > 1 and self._is_consonant(stem, len(stem) - 1)
  File "/home/ubuntu/.pyenv/versions/anaconda3-5.1.0/lib/python3.6/site-packages/nltk/stem/porter.py", line 144, in _is_consonant
    return (not self._is_consonant(word, i - 1))
  File "/home/ubuntu/.pyenv/versions/anaconda3-5.1.0/lib/python3.6/site-packages/nltk/stem/porter.py", line 144, in _is_consonant
    return (not self._is_consonant(word, i - 1))
  File "/home/ubuntu/.pyenv/versions/anaconda3-5.1.0/lib/python3.6/site-packages/nltk/stem/porter.py", line 144, in _is_consonant
    return (not self._is_consonant(word, i - 1))
  [Previous line repeated 990 more times]
  File "/home/ubuntu/.pyenv/versions/anaconda3-5.1.0/lib/python3.6/site-packages/nltk/stem/porter.py", line 140, in _is_consonant
    if word[i] == 'y':
RecursionError: maximum recursion depth exceeded in comparison
>>>

I think it is not very important to fix because it is a very rare case.
However, this error is completely unexpected to me.
It is important to know the special token pattern that causes deep recursion.
I'll be careful of the token length and the special pattern when using the stemmer:)

Ah, that's because of this rule at https://github.com/nltk/nltk/blob/develop/nltk/stem/porter.py#L140
As long as the token ends with >990 y the RecursionError will kick in.
If we do it with other characters, it'll work fine, e.g.
>>> from nltk.stem import PorterStemmer
>>> porter = PorterStemmer()
>>> word = 'x'* 100000
>>> porter.stem(word) # This works fine.

It's because of the recursion when self._is_consonant calls itself inside the function.
   def _is_consonant(self, word, i):
        """Returns True if word[i] is a consonant, False otherwise

        A consonant is defined in the paper as follows:

            A consonant in a word is a letter other than A, E, I, O or
            U, and other than Y preceded by a consonant. (The fact that
            the term `consonant' is defined to some extent in terms of
            itself does not make it ambiguous.) So in TOY the consonants
            are T and Y, and in SYZYGY they are S, Z and G. If a letter
            is not a consonant it is a vowel.
        """
        if word[i] in self.vowels:
            return False
        if word[i] == 'y':
            if i == 0:
                return True
            else:
                return (not self._is_consonant(word, i - 1))
        return True

P/S: There's a way to set a higher limit globally (sys.setrecursionlimit(10000)) but I think users shouldn't do that.

I also hit this case when stemming a lot of text from the internet. I think the obvious solution is to rewrite the algorithm so that it uses a loop rather than recursion. It should just be a case of replacing the body with:
result = False
while i >= 0:
    if word[i] in self.vowels:
        return result
    elif word[i] == 'y':
        result = not result
    else:
        return not result

    i -= 1

return result

Simple test:
def _is_consonant(word, i):
    if word[i] in 'aeiou':
        return False
    if word[i] == 'y':
        if i == 0:
            return True
        else:
            return (not _is_consonant(word, i - 1))
    return True

def _is_consonant_alt(word, i):
    result = False
    while i >= 0:
        if word[i] in 'aeiou':
            return result
        elif word[i] == 'y':
            result = not result
        else:
            return not result

        i -= 1

    return result

assert all([
    _is_consonant('a', 0) == _is_consonant_alt('a', 0),
    _is_consonant('n', 0) == _is_consonant_alt('n', 0),
    _is_consonant('ay', 0) == _is_consonant_alt('ay', 0),
    _is_consonant('ayy', 0) == _is_consonant_alt('ayy', 0),
    _is_consonant('ny', 0) == _is_consonant_alt('ny', 0),
    _is_consonant('nyy', 0) == _is_consonant_alt('nyy', 0),
])

I'm open to a PR on this, preferably with some tests for the new is_consonant.

authors: altescy alvations batterseapower tomaarsen

repo: nltk/nltk


text:
Create DOI

using Zenodo

Upon second thought, this does not appear to be necessary.


text:
[BUG]

Describe the bug
Tables added within the Contentful content editor do not show up in the blog post once published to team page.
Your League ID
784407599985639424
To Reproduce
Steps to reproduce the behavior:

Go to Contentful > Content
Create new content with content type = Blog Post
Add tabular content using the rich text editor 2x2 table button and publish content
See unexpected display on Vercel team page

Expected behavior
Blog post on page should display the table as it's created in the Contentful content editor
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS:Windows 10
Browser= Chrome
Version [e.g. 22]

I'm going to track this in https://github.com/nmelhado/league-page/issues/140 instead, as it has more issues highlighted. I will try to get this finished before the start of the season.

repo: nmelhado/league-page


text:
Integrate Firebase Messaging Service into COWJ

We would like to use COWJ to send notifications to users using COWJ. However, a multicast using Firebase REST API https://firebase.google.com/docs/cloud-messaging/send-message#send-messages-to-multiple-devices requires using sub requests which is not usually exposed as a part of http libraries. Therefore we want to integrate firebase library into COWJ. Specifically the com.google.firebase.messaging library

In this case we need to integrate it as data source.
We add the library into the mix in the build.gradle - and we have to expose the important Class instance of firebase as DataSource interface as done in the file:
https://github.com/nmondal/cowj/blob/main/app/src/main/java/cowj/DataSource.java
Specifically add a datasource type "firebase" and add it up in the UNIVERSAL.
G_STORAGE is a sample data source.

authors: hemil-ruparel-blox nmondal

repo: nmondal/cowj


text:
[nmstate-1.0] sriov: New way to wait VF been created

By checking /sys/class/net/<pf_name>/device/virtfn<sriov_id>/net/
we could tell the interface name of VF.
The old VF name guessing method is removed. The verify_sriov_vf() is
created to collect all VF interfaces name, then comparing it with
total_vfs count and check whether they exists in current state.
The test indicate kernel/udev does not require extra time to remove VF
interface when decreasing SR-IOV VF count.

QE approved at https://bugzilla.redhat.com/show_bug.cgi?id=2019457#c6

repo: nmstate/nmstate


text:
Wrong length for HorizontalBar

When displaying data as horizontal bars, length of bars are not consistent with data.
Example : data: [45, 0, 14, 12]
=> length of bar 45 is (OK)
=> length of bar 14 is too small by comparison with bar 45 (1/15 of length of 45) (not OK)
=> length of bar 12 is 0 (not OK)

var barChartData_canvas1 = {
labels: ["45", "0", "14", "12"],
labelvalues: ["45", "0", "14", "12"],
datasets: [
{
fillColor: "rgba(220,220,220,0.5)",
strokeColor: "rgba(220,220,220,0.8)",
highlightFill: "rgba(220,220,220,0.75)",
highlightStroke: "rgba(220,220,220,1)",
data: [45, 0, 14, 12]
}
]
ctx = document.getElementById("canvas1").getContext("2d");
window.myBar3 = new Chart(ctx).HorizontalBarPlus(barChartData_canvas1, {
showScale: false,
barShowStroke: false,
barValueSpacing: 3,
responsive: false,
scaleShowLabels: true,
showLabel: false
});

Lengh of bars are consistent with data in case the biggest data is twice the lowest, example :  ["10", "12", "14", "18", "20"]
If you use data in which the biggest number is more than twice the lowest, the result is bad, example : ["45", "0", "14", "12"]

Nobody answered me => i guess i am the only guy having this issue on earth !

@juvisy horizontal bars are not supported in Chart.js by default. what extension are you using?

Issue solved : in fact, a colleague modified the source code of :
https://github.com/tomsouthall/Chart.HorizontalBar.js
... in order to add some labels. but it doesn't work
Thank you for your answer. I found the explanation when searching for the extension you asked me

authors: etimberg juvisy

license: mit


text:
[wait for nnstreamer#1637] [android] Cleanup after testing

Use patch file to apply the patch
Cleanup the patch applied (for non-tizen cases) after build completes
Ubuntu build cleanup is handled in ubuntu build script
Self evaluation:

Build test: [x]Passed [ ]Failed [ ]Skipped
Run test: [ ]Passed [ ]Failed [*]Skipped

Signed-off-by: Parichay Kapoor pk.kapoor@samsung.com

:memo: Version: 1.20190225. Thank you for submitting PR #540. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

authors: kparichay taos-ci

repo: nnsuite/TAOS-CI


text:
hota指标

你好跟着你的readme在mot17数据集上测试，只得到 IDF1   IDP   IDR  Rcll  Prcn  GT  MT  PT ML   FP   FN IDs   FM  MOTA  MOTP IDt IDa IDm num_objects这些指标，请问如何获得hota指标？

Have you resolved this issue? @congyao123456

you can follow 'https://github.com/DanceTrack/DanceTrack/tree/main/TrackEval' to get HOTA metrics. @congyao123456


text:
Feature Request: Support for Restart sampling

Please consider adding support for the Restart sampler. It's a new sampler that promises to be both faster and produce better quality images than the existing ones. It would be great to have it available in SHARK too!
https://github.com/newbeeer/diffusion_restart_sampling

it could be added once you find it here: https://huggingface.co/docs/diffusers/main/en/api/schedulers/overview

authors: Oggom cstueckrath

repo: nod-ai/SHARK


text:
Importing the Nock npm module creates error when running npm test

If I remove the nock import I won't get an error message. I've already npm installed nock.
Test file
import configureMockStore from 'redux-mock-store'
import { promiseHandler } from '../middleware'
import * as actions from './index'
import nock from 'nock'
import expect from 'expect'

const middlewares = [promiseHandler]
const mockStore = configureMockStore(middlewares)

Error Message
FAIL  src/actions/index.test.js
Runtime Error
  - TypeError: debug is not a function
        at overrideClientRequest (node_modules/nock/lib/intercept.js:221:3)
        at activate (node_modules/nock/lib/intercept.js:320:3)
        at Object.<anonymous> (node_modules/nock/lib/intercept.js:383:1)
        at Runtime._execModule (node_modules/jest-cli/src/Runtime/Runtime.js:261:17)
        at Object.<anonymous> (node_modules/nock/lib/recorder.js:6:17)
        at Object.<anonymous> (node_modules/nock/index.js:1:135)
        at Object.<anonymous> (src/actions/index.test.js:4:39)
        at jasmine2 (node_modules/jest-jasmine2/src/index.js:252:16)
        at handle (node_modules/worker-farm/lib/child/index.js:41:8)
        at process.<anonymous> (node_modules/worker-farm/lib/child/index.js:47:3)
        at emitTwo (events.js:100:13)
        at process.emit (events.js:185:7)
        at handleMessage (internal/child_process.js:718:10)
        at Pipe.channel.onread (internal/child_process.js:444:11)

I'm having the same problem. If you're using Jest, I believe you need to unmock these modules before using them because Jest will automock everything.
At the top of your file, add:
jest.unmock('nock');
jest.unmock('redux-mock-store');
jest.unmock('redux-thunk');

Confirming this was the issue.
On Mon, Jun 27, 2016 at 12:35 PM, Danny notifications@github.com wrote:

I'm having the same problem. If you're using Jest, I believe you need to
unmock these modules before using them because Jest will automock
everything.
At the top of your file, add:
jest.unmock('nock');
jest.unmock('redux-mock-store');
jest.unmock('redux-thunk');
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/node-nock/nock/issues/584#issuecomment-228851326, or mute
the thread
https://github.com/notifications/unsubscribe/AS016_Y3IuGrCnLQFOse-kcX3cRaYZFEks5qQCYfgaJpZM4I226_
.

Also confirming I was able to resolve this by putting this my package.json file:
  "jest": {
    "unmockedModulePathPatterns": [
      "<rootDir>/node_modules/nock",
      "<rootDir>/node_modules/redux-thunk",
      "<rootDir>/node_modules/redux-mock-store",
    ]
  },

Anyone have this issue with jasmine?

authors: dannyid mjabraham47 tinder-dyakobian tylerchilds

repo: node-nock/nock


text:
release 4.1.1 -> master

Summary 📖
This simple PR merges the changes from development into master.
View the CHANGELOG for what was added and changed.

I will manually publish since it's a hotfix


text:
Update jsonata to 1.6.5 which should fix #2183

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes
Update JSONata to 1.6.5 to fix #2183
Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the mailing list/slack team.
[ ] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

You'll need to update the individual package.json files as well.
Run node scripts/verify-package-dependencies.js to see which and rerun with --fix to update them and commit any changes

Thanks ! will do

Coverage increased (+0.04%) to 76.418% when pulling c2167a2c5f4230db183641e4d7a3f673700a12a9 on natcl:patch-4 into f49d1ae8602c618f2e2e3707f3353389a3dd7dd8 on node-red:master.

authors: coveralls knolleary natcl

repo: node-red/node-red


text:
is SerialPort fitting Raspbian?

hey guys i have an Raspbian OS installed on my raspberry,
i would like to know if it is ok to use this OS or I need to switch it.
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)" NAME="Raspbian GNU/Linux" VERSION_ID="9" VERSION="9 (stretch)" ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

Everything is perfectly working on rasbian, you have issues?

repo: node-serialport/node-serialport


text:
Add missing minutes docs — 2019-05-02 thru 2019-08-08

This catches up minutes between 2019-05-02 and 2019-08-08.
Please see gist used to semi-automate the batching process — https://gist.github.com/SMotaal/f4ce43463e455831e9e572ac5e03f82c

Co-Authored-By: Saulo Nunes saulo@paralink.com.br

Links

meetings/2019-05-02.md
meetings/2019-05-16.md
meetings/2019-06-13.md
meetings/2019-06-27.md
meetings/2019-07-11.md
meetings/2019-07-25.md
meetings/2019-08-08.md

Just realized I somehow committed 2019-10-17 notes here as well as in #545… thoughts?
/cc @mhdawson @WaleedAshraf

If there are duplicates I'd say just pull the duplicate out of this one.

@mhdawson (not to sound gitty) a new revert commit or is there a way to roll it out of existence on the PR?

authors: SMotaal mhdawson

repo: nodejs/community-committee


text:
Oppdatert FAQ på website repoet

Hei!
På nodejs/website#357 er det merget at FAQ seksjonen skal omformuleres bittelitt. Jeg oppdaterte den norske oversettelsen av dette på nodejs/website#377, men den trenger vel en +1 fra noen andre i det norske teamet.
Jepp, det var bare det. God helg :)

Denne kan vel lukkes nå?

Jepp!

authors: Andersos eiriksm mikaelbr

repo: nodejs/iojs-no


text:
add travis build checks to git-node-land

https://github.com/nodejs/node-core-utils/pull/369 is a round-about way of doing it, but apparently not reliable (https://github.com/nodejs/node-core-utils/pull/369#issuecomment-548953916). If it was reliable, then all the specific code to check Jenkins or Travis would be unnecessary, so  that's unfortunate.
Note that since https://github.com/nodejs/node/pull/30330 only Travis has been required for doc-only tests.
There have also been musings (some by me) of using Travis more for actual CI testing:

https://github.com/nodejs/build/issues/1593#issuecomment-554485910
https://github.com/nodejs/build/issues/2016#issuecomment-548858369

This would require Travis failures to block landing PRs.

Closing as Node.js PRs now use Jenkins and GitHub actions, checks for both of which are included in git-node-land logic :)

authors: codebytere sam-github

repo: nodejs/node-core-utils


text:
Weird error MSB6006: "cmd.exe" exited with code 1 on some packages

We've been facing a very strange issue at Etcher (https://github.com/resin-io/etcher). We have node-sass as a development dependency, and lzma-native as a production dependency.
When node-gyp was updated to v3.6.0, node-sass picked up this change, causing lzma-native to fail with the following error on Windows:
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(171,5): error MSB6006: "cmd.exe" exited with code 1. [C:\projects\etcher\node_modules\lzma-native\build\liblzma.vcxproj]

So to make it clear, after the node-gyp upgrade on a development dependency (node-sass), a totally unrelated production dependency, lzma-native, suddenly starts to fail on Windows. What's even more strange is that node-sass compiles just fine, and removing node-sass from the development dependencies causes lzma-native to start working again. As a fix, we've started shrinkwrapping development dependencies as well, and locking node-gyp to v3.5.0, which makes everything work again.
The problem seems to have been introduced by https://github.com/nodejs/node-gyp/commit/ae141e19060ecb1c596a96acf9510d66b7376c18, however I don't understand why.
See https://github.com/resin-io/etcher/pull/1191. You can probably reproduce by cloning Etcher, checking out a commit before such fix, and running make electron-develop (which is a Makefile target that we use to pass some node-gyp options to npm, run bower, etc).

The problem seems to have been introduced by ae141e1, however I don't understand why.

Hmm, I wonder if the problem might be that this part of the change:
  function findMsbuild () {
    if (config.variables.msbuild_path) {
      command = config.variables.msbuild_path

means that the MSBuild command is now run with its full-path "C:\Program Files (x86)\MSBuild\...\MSBuild.exe", whereas previously it was just run as MSBuild.exe, and this additional "C:\Program Files (x86)\MSBuild\..." is now just enough to push the lzma-native compilation command over the cmd.exe command-line length limit on Windows? http://stackoverflow.com/questions/3205027/maximum-length-of-command-line-string

cc @refack @joaocgreis

hmmm... giving this some thought...

It's not a "length of command line" issue, it's a "not run from VS console" issue.
The lzma-native build calls lib.exe which is not in the path unless vsvarsall.bat (or it's derivatives) is run.
Up till node-gyp:v3.5.x the whole thing would fail. Now we can find & call msbuild.exe in the general case, but than we fail if the build is complicated ;(

Scratch that!
It's probably a bug in GYP. It eronuesly transforms
'action': [
  'lib -def:"<(module_root_dir)\\deps\\doc\\liblzma.def" -out:"<(module_root_dir)\\deps\\bin_x86-64\\lzma.lib" -machine:x64 && if not exist <(dlldir) mkdir <(dlldir) && copy "<(module_root_dir)\\deps\\bin_x86-64\\liblzma.dll" "<(dlldir)\\liblzma.dll"'
]

to
call call "lib -def:"C:\code\3party\lzma-native\deps\doc\liblzma.def" -out:"C:\code\3party\lzma-native\deps\bin_x86-64\lzma.lib" -machine:x64 && if not exist C:\code\3party\lzma-native\binding-v2.0.0-node-v51-win32-x64 mkdir C:\code\3party\lzma-native\binding-v2.0.0-node-v51-win32-x64 && copy "C:\code\3party\lzma-native\deps\bin_x86-64\liblzma.dll" "C:\code\3party\lzma-native\binding-v2.0.0-node-v51-win32-x64\liblzma.dll""
if %errorlevel% neq 0 exit /b %errorlevel%

Instead of
lib -def:"C:\code\3party\lzma-native\deps\doc\liblzma.def" -out:"C:\code\3party\lzma-native\deps\bin_x86-64\lzma.lib" -machine:x64 && if not exist C:\code\3party\lzma-native\binding-v2.0.0-node-v51-win32-x64 mkdir C:\code\3party\lzma-native\binding-v2.0.0-node-v51-win32-x64 && copy "C:\code\3party\lzma-native\deps\bin_x86-64\liblzma.dll" "C:\code\3party\lzma-native\binding-v2.0.0-node-v51-win32-x64\liblzma.dll""
if %errorlevel% neq 0 exit /b %errorlevel%

Awesome, great to hear you found the root cause of this issue! BTW, could you explain why in our case lzma-native started failing after node-gyp was upgraded by node-sass? I'm assuming that such upgrade caused lzma-native to start re-using node-sass's node-gyp version, which built node-sass fine, but caused errors on lzma-native because lzma-native uses lib.exe during build.
Is this correct?

node-gyp come with npm. It's a tool that compiles "native bindings" for some modules.
Unfortunately native bindings need to be re-compiled for every version of node (or in this case electron).
lzma-native has an online cache of precompiled bindings, seems like the new version couldn't find a precompiled pack for your platform. In that case it tries to compile it with node-gyp which triggered the bug (bug might have been there for a while)

@refack Yeah, but it’s still a curious thing how the node-sass upgrade made the difference?

I'm afraid I'll have to disagree with the (bug might have been there for a while) comment.
Up until 5 days ago all our Windows CI builds were working fine on Appveyor (including building lzma-native from source) but then all of a sudden (after the release of node-gyp 3.6.0) all our Windows CI builds started failing.
And our workaround for the problem in https://github.com/resin-io/etcher/pull/1191 was to basically version-lock node-gyp to 3.5.0 which got everything working again.

Up until 5 days ago all our Windows CI builds were working fine on Appveyor (including building lzma-native from source) but then all of a sudden (after the release of node-gyp 3.6.0) all our Windows CI builds started failing.

I said might... 🤷
I'm still digging...

Found it
Added escaping of custom actions, which may lead to broken commands
/cc @kunalspathak

Thanks @refack for the investigation. I went back and checked and it seems the quote_cmd issue was fixed in node-chakracore but https://github.com/nodejs/node-gyp/pull/873 was not updated with the fix. I will send another PR to fix this.

resolved in @3.6.1

Having the same problem in 3.6.2
$ npm install

> ref@1.3.5 install C:\Users\xavier\Documents\Carestream\server\node_modules\ref
> node-gyp rebuild

C:\Users\xavier\Documents\Carestream\server\node_modules\ref>if not defined npm_config_node_gyp (node "C:\Program Files (x86)\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "C:\Program Files (x86)\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(356,5): error MSB6006: "CL.exe" exited with code -1073741515. [C:\Users\xavier\Documents\Carestream\server\node_modules\ref\build\binding.vcxproj]
gyp ERR! build error
gyp ERR! stack Error: `C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\Program Files (x86)\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:258:23)
gyp ERR! stack     at emitTwo (events.js:126:13)
gyp ERR! stack     at ChildProcess.emit (events.js:214:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Windows_NT 6.3.9600
gyp ERR! command "C:\\Program Files (x86)\\nodejs\\node.exe" "C:\\Program Files (x86)\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\xavier\Documents\Carestream\server\node_modules\ref
gyp ERR! node -v v8.9.4
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
npm WARN @nestjs/common@4.6.6 requires a peer of reflect-metadata@0.1.10 but none is installed. You must install peer dependencies yourself.
npm WARN @nestjs/core@4.6.6 requires a peer of reflect-metadata@0.1.10 but none is installed. You must install peer dependencies yourself.
npm WARN @nestjs/microservices@4.6.6 requires a peer of reflect-metadata@0.1.10 but none is installed. You must install peer dependencies yourself.
npm WARN @nestjs/swagger@1.1.4 requires a peer of reflect-metadata@0.1.10 but none is installed. You must install peer dependencies yourself.
npm WARN @nestjs/websockets@4.6.6 requires a peer of reflect-metadata@0.1.10 but none is installed. You must install peer dependencies yourself.
npm WARN nest-typescript-starter@1.0.0 No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.1.3 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"ia32"})

authors: addaleax bnoordhuis jviotti kunalspathak lurch marcelfalliere refack rvagg

repo: nodejs/node-gyp


text:
Make output should filter through "info" and "warn" loglevels.

Output from Make should be filtered into loglevels. That is, Make's stdout should be pushed to log.info and stderr should be pushed to log.warn. For example, for a small library I created:
jason@ginny:~/src/rasterize$ node-gyp rebuild --loglevel warn
make: Entering directory `/home/jason/src/rasterize/build'
  CXX(target) Release/obj.target/rasterize/rasterize.o
  SOLINK_MODULE(target) Release/obj.target/rasterize.node
  SOLINK_MODULE(target) Release/obj.target/rasterize.node: Finished
  COPY Release/rasterize.node
make: Leaving directory `/home/jason/src/rasterize/build'

I would expect no output whatsoever from a successful build when the loglevel is set to warn.
Thanks!

closing due to staleness, a pull request for this would be great though

Is there no way to make make quiet? (This issue is the top hit for "node-gyp make make quiet" for me)
My inkling is that binding.gyp should have some option to make make quiet but I'm not finding it. Notably, I've tried setting MAKEFLAGS and MAKEOVERRIDES with  gyp defines to no avail. Looking at the generated Makefile, the quiet mode "is the brief-output summary of the command".
Maybe the only option is to capture the output as this issue suggests and do different things with it.

I can't recall which addon it was, a popular websockets library I think, that used to have a "build", or "install" script in package.json that would send the build output to a file (bash redirect, I think it might have manually invoked something like node-gyp build >& build.out) and then on non-zero exit code would spit out the build output to stdout, otherwise it would be silent. I have only vague memories of this and it was annoying at the time because it was difficult to debug problems with it. But you could pursue something like this if this really bothered you.
Otherwise I don't think it bothers any of us enough to pursue it. But as I said above, pull requests are welcome, but it'd have to not be too invasive (i.e. it's not the kind of feature we're going to take on a ton of risky new code for).

Yeah, I'm not a fan of that method at all.

Is there a reason this issue is closed? Would it make sense to leave it open?

Looking at the code, I only see a couple usages of spawn.
The first is a test, so we can ignore it.
The second is the implementation that I presume actually calls python/gyp. Interestingly, it looks like there was an attempt at adding a quiet option: https://github.com/nodejs/node-gyp/blob/3555ff4f0031f067bda9a49cbb2dbe6c04f4b5c7/lib/node-gyp.js#L169-L171
The last two files with spawn occurrences are:
https://github.com/nodejs/node-gyp/blob/5d76938e55b17d5633bb9d4f71b7f73034848505/lib/build.js#L188-L189
https://github.com/nodejs/node-gyp/blob/3555ff4f0031f067bda9a49cbb2dbe6c04f4b5c7/lib/configure.js#L344-L345
Looking at those usages, neither sets the optional 3rd argument opts which would set the quiet mode that prevents the spawned process from making any outputs.
It should be easy enough to add something to those calls, but what do we pass to them? Currently, node-gyp seems to pass all the logging (and related verboseness) to the npmlog package. So the right solution I think is to capture the output from the spawned commands (instead of always passing them through to stdin/stdout/stderr).
This does get a little bit more complicated when you think about changing the verboseness of gyp's output and possibly filtering those outputs to multiple npmlog log levels.
If we had to pick just one log level to capture make's output, what would we use?
https://github.com/npm/npmlog/blob/541407008c509755255a4819606e7916d26a77f5/log.js#L296-L304
I'm thinking notice makes sense. Or maybe we add one?

notice seems like a good choice to me, I have my npm set to http, so I'd get it, but the default is warn, so the majority of people wouldn't https://github.com/npm/npmconf/blob/22827e4038d6eebaafeb5c13ed2b92cf97b8fb82/config-defs.js#L180
Unless someone else speaks up here, I'd encourage you to pursue a pull request that pipes the output line by line through npmlog. I'm not sure what to do about stderr, maybe that needs to go to warn? Without looking in detail at how, off the top of my head I reckon piping the streams to split2 and then terminating in a transform stream that sends the chunks to npmlog. Off the top of my head, something like:
stdout.pipe(split2()).pipe(new Transform({
  transform: (chunk, enc, cb) => {
    log.notice(chunk.toString()); cb();
  }
})

Unless you have a better idea (or the reality of the codebase makes that too tricky).
Feel free to do a PR as a draft to start with to get feedback if you need it.

authors: cinderblock ironwallaby rvagg


text:
dropping subgraph onto itself explodes the universe

I only did this by accident (was trying to choose a different component and clicked the same subgraph I was working on)
noflo-ui seemed OK with it, but it annihilated my runtime (nodejs), which spat out a few hundred of the following lines and then crashed.
(node) warning: Recursive process.nextTick detected. This will break in the next version of node. Please use setImmediate for recursive deferral.

Seems maybe the ui needs to filter the component list to prevent this type of recursion from happening.

This was fixed in #95 but seems like we have a regression. See also noflo/noflo#147

My apologies again for the issue duplication, will try to do a better job searching existing issues going forward...

@ryedin no problem, in this case we already fixed it once, but there was a regression. So new issue is OK :-)

authors: bergie ryedin

repo: noflo/noflo-ui


text:
Epic: Update barretenberg CLI to be compatible with Noir

### Tasks
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/1647
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/1650

Should we transfer this to https://github.com/AztecProtocol/aztec-packages?

This is here so it can be tracked on the Noir project board.

Huh, I didn't know that. Thanks!
I'm going to close this issue as both tasks have been addressed.

authors: Savio-Sou TomAFrench

repo: noir-lang/acvm-backend-barretenberg


text:
Unreachable annotations are used incorrectly

LIBNPLN_DETAIL_UNREACHABLE is used to insert unreachable code annotations after total switches. This is incorrect because a switch cannot be total without a default case. For example, libnpln::machine::get_name(Register) can hit the unreachable annotation by calling it with a cast enum, like so:
libnpln::machine::get_name(static_cast<libnpln::machine::Register>(0xFF));

This causes a segfault on my Linux machine. These scenarios should be handled better.

Closed by 083e0e6.

repo: nokurn/npln

license: ISC


text:
Adapt for ember-data 1.0.0-beta16

Starting in ember-data 1.0.0-beta16, adapters will no longer receive actual records. They will receive snapshots instead. See emberjs/data#2883.
This is a placeholder for any work that's necessary to adapt to this — it's possible that no changes will be necessary.

It looks like the necessary changes will be pretty extensive to avoid deprecation warnings. I'd vote to drop backwards compatibility and go to version 2.0.0.

DEPRECATION: You called _createSnapshot on what's already a DS.Snapshot. You shouldn't manually create snapshots in your adapter since the store passes snapshots to adapters by default. does not mean we have to go for a major version upgrade for every ember-data beta step but dropping backwards compatibility for snapshots seems OK to me. I don't know if it is the snapshots but ember-pouch does not seem aware of change you make in an other browser instance or new data coming in. See http://exmer.com/bloggrcouch/  I will update to beta16 today to check if this helps. Ember data 1.0 will be released June 12 so  if we need a new major version perhaps on June 12 ;-)

@rsutphin ember-data beta16 does not solve my problem and switching back to 1.2.3 does not help so I think my problem is no a snapshot problem and does not belong in your issue. I have created a new issue for this: https://github.com/nolanlawson/ember-pouch/issues/50

DEPRECATION: You called _createSnapshot on what's already a DS.Snapshot. You shouldn't manually create snapshots in your adapter since the store passes snapshots to adapters by default. does not mean we have to go for a major version upgrade for every ember-data beta step but dropping backwards compatibility for snapshots seems OK to me.

If there was just that one deprecation warning, then I wouldn't worry about it. But it seems from the blog post that the API for a snapshot is entirely different from a model (id instead of get('id'), attr for scalar attributes, hasMany and belongsTo for associations, etc.) and the old versions will all print deprecation warnings. If that's the case, then your logs will be filled with deprec warnings to the exclusion of everything else.
Anyway, just my vote for 2.0.0 if it does turn out to be a deprecation nightmare. Unfortunately I probably won't be able to help with this right away (unless it turns out I to need to update past beta.15 for another reason).

It seems Ember-Date 16.1 removed the Deprecation warnings?

As an intermediate solution before moving to a version 2.0.0 we could also extend the check for snapshot in _recordToData:
    if (typeof record.record === 'undefined' && typeof record._createSnapshot === 'function') {
      recordToStore = record._createSnapshot();
    }

The 'if' statement will make the deprecation message go away in 1.0.0-beta16 and keep the adapter compatible with 14 and 15.
This solution is just pragmatic and not beautiful and should be removed when EmberData is final.
(@ broerse: I still see the deprecation warnings in 1.0.0-beta16.1)

@OleRoel I was too fast. My deprecation warnings changed from always to sometimes but perhaps that was because I also update my application. @nolanlawson can you take a look or are you planning updates after 12 June ?

@OleRoel, I like that idea. Does it really get rid of all deprecation warnings? I was concerned more with the accessor-based ones, but maybe ember-pouch delegates all that to the serializer and so would be fine. (Unfortunately, I still haven't had a chance to try out beta.16 myself.)

Sorry, I've been busy with other stuff these days. If y'all have time, a pull request would be awesome. :)

I'll take the PR.

@OleRoel Thanks. I am a beginner but can test it for you!

@broerse thank you for your offer! I am going to test my code tomorrow.

@OleRoel Your fix is working fine! Just updated to 1.2.5

Cool beans. :)

authors: OleRoel broerse nolanlawson rsutphin

repo: nolanlawson/ember-pouch


text:
video slide works incorrect with cube effect

Check that this is really a bug

[x] I confirm

Reproduction link
https://codesandbox.io/s/swiper-with-image-and-video-xzt835?file=/index.html
Bug description
I have a swiper with image slide and video slide, the height of them are different, when I swipe the video slide to the image slide, the previous video slide is still visible.
ps: I've tested v6.8.4 and 8.3.2

Expected Behavior
No response
Actual Behavior
No response
Swiper version
v6.8.4 and 8.3.2
Platform/Target and Browser Versions
windows chome 103.0.5060.134
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[X] I'm willing to open a PR

I think you need to set a fixed height with overflow:hidden
It only seems to work fine with images/videos with the exact same ratio.

authors: dijkermans yuuk


text:
CASTEP parser: charge reading from MD/GEOM jobs fails

I have noticed the parsing of CASTEP outputs from geometry optimisations fail on parsing charges from the file. This prevents the whole file from being parsed and published.
code: Castep v21.11, calculation has been performed on Archer 2 in the UK
See traceback from the log file below:
Traceback (most recent call last):
  File "/app/nomad/processing/data.py", line 466, in parsing
    self._parser_results, logger=logger)
  File "/usr/local/lib/python3.7/site-packages/castepparser/castep_parser.py", line 1202, in parse
    self.parse_configurations()
  File "/usr/local/lib/python3.7/site-packages/castepparser/castep_parser.py", line 1099, in parse_configurations
    parse_calculation(calculation.get('final'))
  File "/usr/local/lib/python3.7/site-packages/castepparser/castep_parser.py", line 1045, in parse_calculation
    sec_scc = parse_scc(source)
  File "/usr/local/lib/python3.7/site-packages/castepparser/castep_parser.py", line 932, in parse_scc
    sec_mulliken.x_castep_mulliken_charge = mulliken['Charge'][n]
KeyError: 'Charge'

Plus find the example upload & log file form the platform here:
48ewILIbTZSloT-zx2PGWQ.zip
YBhZO21WfBLDdo1vvAA-QmgEQy8R.log

@ladinesa could you address this rather soon? Maybe we should merge this into both 1.0.x and 1.1.x.

I do not see any error both on staging and public.

You are right, re-uploading works now. I have uploaded and published it on the site. Thanks!

authors: ladinesa markus1978 stenczelt

repo: nomad-coe/nomad


text:
False negative: |- (∑' (n :Nat), _ ^ n) =

The query |- (∑' (n : Nat), _ ^ n) = _ doesn’t work, while |- (∑' (n : _), _ ^ n) = _  works.
Something with type classes, because it says

Found 40 definitions mentioning HPow.hPow, tsum and Eq. Of these, 7 match your pattern(s).

but

Found 0 definitions mentioning instPowNat, instTopologicalSpaceNat, Nat.addCommMonoid, HPow.hPow, tsum, Nat, instHPow and Eq. Of these, 0 match your pattern(s).

Maybe related:
|- (∑' (n :  _), _ ^ n) = (_ : Real)

works but
|- (∑' (n :  _), (_ ^ n : Real)) = (_ : Real)

doesn’t. Difference: Real.instPowReal and instHPow.

Ah, maybe this is due to https://github.com/leanprover/lean4/issues/2220 somehow.

yay, this got fixed along with  https://github.com/leanprover/lean4/issues/2220!

repo: nomeata/loogle


text:
Missing/Unsupported Features

Missing:

Tables & Columns
Storage
Data Plotting
Value() Helpers
Tabs
Docking (enabled by default, no functions for it yet)
Viewports
Logging
Drag & Drop
Clip Rect
Callbacks
Drawlists
Input (maybe not, since GM already has this)

Unsupported:

Non-Windows platforms: ImGui_GM uses the graphics context and device from os_get_info to render draw data, unfortunately this is not provided for non-Windows platforms. Hypothetically, ImDrawData can be passed into GameMaker and handled via GML but there are some performance concerns there, and GM does not support index buffers

Updated this issue with newly implemented wrappers (tables/plots/tabs/cliprects), see COVERAGE.md to track progress

How far down the pipeline would GetIO and SaveIni functions come around? It would be great to return to a workspace with all the original window positions and docks in the same configuration. Thanks

authors: constlet nommiin


text:
求帮助

为什么不加/无法触发啊，以前都还可以的

请确定你的 COMMAND_START 配置起了作用，在 DEBUG 模式下可以在 NoneBot2 启动时看到 [DEBUG] nonebot | Loaded Config:

我知道是什么问题了

感觉是群聊学习这个插件的锅

请你在 DEBUG 模式下分别用 npm /npm  给 Bot 发消息，然后把日志发上来。

感觉是群聊学习这个插件的锅

对，它会自动删除为空的命令前缀。

删了群聊学习就解决了。。。

repo: nonepkg/nonebot-plugin-manager


text:
AMQPClient should support more than one connection

Would be nice if, once send/receive supported URIs and not just source/target, we could manage multiple connections to different hosts from a single client (e.g. rx from bus1, tx to bus2).

This is really not worth supporting - they can just instantiate multiple clients.

yeah I wondered why you had this, it works quite well with multiple instances of AMQPClient :smile:

My mind works in mysterious ways.

authors: mbroadst noodlefrenzy


text:
exposed new Money properties: currency, minorUnit

resolves https://github.com/noojee/money.dart/issues/2

Excellent idea, thanks for the work :)

authors: bsutton oysterpack


text:
Rent and setup a CCJ Tumbler on testnet

After: CCJ Tumbler is built.

I have a CloudMX server with a spare IP address that we can use for development. Windows virtual machine with .net installed, IIS etc. SQL Server as well if we want to persist any data. Can increase the ram and CPU count dynamically if needed. Has unlimited network usage contract already paid for.

Alright, I let the server configuration to you when we get there.

Done.


text:
refact: Faster makefile

I've been studying C again recently and I found those changes improves the compile/test time a lot.

Codecov Report

Merging #53 (f382f8c) into main (cb48714) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #53   +/-   ##
=======================================
  Coverage   89.38%   89.38%
=======================================
  Files           4        4
  Lines         678      678
  Branches       57       57
=======================================
  Hits          606      606
  Misses         43       43
  Partials       29       29

Continue to review full report at Codecov.

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

authors: codecov-commenter rafaeldelboni

license: Unlicense


text:
Problem with Training / tools.train.py

Once again me ... another problem:
When i start training i get the following result:
python tools.train.py
Pictures and names are recognized .. but then this follows:
Training model with threshold 80 Traceback (most recent call last):   File "tools.train.py", line 14, in <module>     ToolsTrain().train()   File "/home/pi/MagicMirror/modules/MMM-Facial-Recognition-OCV3/lib/tools/train.py", line 71, in train     model = ToolsConfig.model()   File "/home/pi/MagicMirror/modules/MMM-Facial-Recognition-OCV3/lib/tools/config.py", line 99, in model     return CommonConfig.model(cls.POSITIVE_THRESHOLD)   File "/home/pi/MagicMirror/modules/MMM-Facial-Recognition-OCV3/lib/common/commonconfig.py", line 51, in model     model = cv2.face.LBPHFaceRecognizer_create(threshold=thresh) AttributeError: 'module' object has no attribute 'face'

Still nobody have found a way to this problem? I have it myself, and it's kinda annoying, after that i have been using multiple days to figure out the cv2 can't be found problem.

I fixed the issue by replacing:
cv2.face.LBPHFaceRecognizer_create(threshold=thresh)
with:
cv2.face.createLBPHFaceRecognizer(threshold=thresh)

@Blauenfeldt your fix helped, but then I ended up with the following. Is there a solution for this one?
Training model with threshold 80
Traceback (most recent call last):
File "tools.train.py", line 14, in
ToolsTrain().train()
File "/home/pi/MagicMirror/modules/MMM-Facial-Recognition-OCV3/lib/tools/train.py", line 74, in train
model.write(ToolsConfig.TRAINING_FILE)
AttributeError: 'cv2.face_LBPHFaceRecognizer' object has no attribute 'write'

I got it all working that time. the problem is, as I can remember, that from Python, as it was programmed in, to Python3.1 there was some changes to got things are spelled. Like @JahFyahh said, "write" was used in Python, and in Python3.1 "save" is used instead.
@JahFyahh I think you can mark this as solved.

authors: 666Necrom Blauenfeldt JahFyahh


text:
Fixes making the plugin actually work

If you'd prefer to still be the maintainer of the repo, feel free to pull my work in to make this plugin usable. Basically the original version had the following issues:

Failed deployment on first deployment
Did not use the proper SHA1 from the latest git commit (but the previous deployments commit SHA1).

Note you'd probably also want to change the README in such case.

Thanks for the fixes! I'm no longer using this, so I'll update the README to point to your fork.

authors: cjblomqvist nornagon

repo: nornagon/dokku-git-rev


text:
Importing cleave.js for react does not work in Version 1.3.1

Using Version 1.3.1 and trying to import cleave for eact
import Cleave from 'cleave.js/react';
results in error
ERROR in ./src/xxx/yyy.js
Module not found: Error: Can't resolve 'cleave.js/react' in 'xx/yyy/zzz.js'

using Version 1.2.0 works fine.

I can confirm this is happening!

This seems to be because package.json contains
"version": "1.3.1",
"files": [
"src",
"dist"
],
thus we only include folders src and dist

I don't know if this is really the problem, since the dist folder contains the cleave-react.js file too...

A quick and easy way to test, this is the case:
in any app using import Cleave from 'cleave.js/react';
with cleave 1.3.1 when we try to start/build the project, it gives an error
Module not found: Error: Cannot resolve module 'cleave.js/react' in
go to node_modules\cleave.js and put the file react.js (from version 1.2.1 or root of this repo)
try to start/build the project again, then it is OK.
I will try to provide a complete example soon.

Sorry guys,
I’ve merged the PR.
Will bump version and release when home.

Hi guys. Fix release in v1.3.2, sorry again.
Can I close this?

Things started working again :D

authors: khaosdoctor mayurdange mlaug nosir


text:
fix(cleave.react.js): fixed android backspace bug from issue 147 in r…

…eact component
Discussed in issue 147, but the PR never had changes to the React component

Thanks @jasongi-at-sportsbet all your PR merged 👍

authors: jasongi-at-sportsbet nosir


text:
Comments api missing

Subreddit, user and multireddit should expose a method to retrieve the last comments.
Some examples:

/r/redditdev
/u/spez
/u/multi-mod/m/cats

It should be as easy as adding a ._getListing({uri: url + '/comments', qs: options});
I've used it on my tool.
Thanks for snoowrap.

Sorry, I lost track of this issue.
Actually, I think there are methods for the first two:

Subreddit#getNewComments
RedditUser#getComments

But you're right that the API for multireddit comments is missing.

authors: not-an-aardvark timendum

repo: not-an-aardvark/snoowrap


text:
Use gitattributes to keep your tests out of other people’s production

https://madewithlove.be/gitattributes/

see https://github.com/notFloran/mjml-bundle/commit/7e987cd861a8674142b054e29d36e84eb44d22ab

repo: notFloran/mjml-bundle


text:
fix: fix MessageImprint.HashAlgorithm.Parameters

This PR fixes MessageImprint.HashAlgorithm.Parameters and added corresponding validation in TSA response based on RFC 3161.
The issue that this PR is trying to fix is:
Golang's asn1.RawValue has zero value with Tag 0, which is actually not a valid asn1 tag (https://luca.ntop.org/Teaching/Appunti/asn1.html).
The correct zero value of the struct should be asn1.NullRawValue with Tag 5. However, asn1.NullRawValue is not a valid asn1 object either. The valid struct, as added by this PR, should be:
asn1.RawValue{
     Tag: 5,
     FullBytes: []bytes{5, 0}  // tag and length
}

If running the below piece of code:
v1 := asn1.NullRawValue
fmt.Println("v1:", v1)

b, _:= asn1.Marshal(v1)
var v2 asn1.RawValue
asn1.Unmarshal(b, &v2)
fmt.Println("v2:", v2)

The printouts will be:
v1: {0 5 false [] []}
v2: {0 5 false [] [5 0]}   --> unmarshal returns the correct struct

(This is a known issue of golang encoding/asn1 package: https://github.com/golang/go/issues/30414. The issue was closed without any code update though)

https://cs.opensource.google/go/go/+/master:src/encoding/asn1/asn1_test.go;l=1045-1068?q=NullRawValue&ss=go%2Fgo
Could you have a look at this test? Is it by design?

https://cs.opensource.google/go/go/+/master:src/encoding/asn1/asn1_test.go;l=1045-1068?q=NullRawValue&ss=go%2Fgo
Could you have a look at this test? Is it by design?

Yes, it is by design by the golang library, but that's not by design of RFC 3161. When a TSA request contains asn1.NullRawValue, the TSA response may contain the correct null raw value struct instead. And this would fail tspclient-go's response validation. Therefore, we need to make sure we send out the correct asn1 object in the request.

authors: JeyJeyGao Two-Hearts

repo: notaryproject/tspclient-go


text:
Add an option to use notice instead of privmsg.

Please add an option to use NOTICE instead of PRIVMSG. For example, Github has a little checkbox for this option:

Many IRC clients allow users to disable notifications (beeps, etc) for notices. This is often useful in channels where notifico messages are considered of much lesser importance than messages from users.

The RFC says:
4.4.2 Notice

      Command: NOTICE
   Parameters: <nickname> <text>

   The NOTICE message is used similarly to PRIVMSG.  The difference
   between NOTICE and PRIVMSG is that automatic replies must never be
   sent in response to a NOTICE message.  This rule applies to servers
   too - they must not send any error reply back to the client on
   receipt of a notice.  The object of this rule is to avoid loops
   between a client automatically sending something in response to
   something it received.  This is typically used by automatons (clients
   with either an AI or other interactive program controlling their
   actions) which are always seen to be replying lest they end up in a
   loop with another automaton.

   See PRIVMSG for more details on replies and examples.

The difference between NOTICE and PRIVMSG is that automatic replies must never be sent in response to a NOTICE message.

As said before, this isn't the case with IRC in practice (thanks mIRC), but nowadays there is also Matrix which doesn't have this issue.
Matrix uses m.notice for messages by bots (like was supposed to be done with IRC) and native clients (mainly Riot) have option to not highlight on messages by bots thanks to it.
How this is related to IRC commit announcer bot is that Matrix has bridges to multiple IRC networks (https://github.com/matrix-org/matrix-appservice-irc/issues/208 (can be thought of as a stupid bouncer)) and thus the users encounter notifico and committetters/authors get pinged by it. If Notifico was able to use NOTICE, that didn't happen as the bridge turns NOTICE to m.notice.

https://matrix.org/
https://riot.im/

In addition to having this option, there should be a way to mass edit channels or at least edit channels. I would be happy with option to make all channels under my account to use NOTICEs or at least default to it unless I otherwise specified.

repo: notifico/notifico


text:
Crash when counting commits in multiple repos

Node Version: v7.2.1
tiny-core-terminal version: 1.0.8
Shell: bash
Terminal Program: iTerm2
Operating System: macOS
I have quite a few repos in ~/dev. The dashboard starts up, starts counting commits for a second and then crashes. Using TTC_REPOS=/single/repo works fine for the ones I tried. Didn't try very hard to debug into the blessed library since I don't know what the code is doing. What I can tell you that at that given code location in blessed (/usr/local/lib/node_modules/tiny-care-terminal/node_modules/blessed/lib/program.js:2543), we have part == "cpp" and val == "cpp".
Unsetting env vars other than TTC_REPOS doesn't make a difference.
$ set | grep TTC
TTC_APIKEYS=false
TTC_BOTS=tinycarebot,selfcare_bot
TTC_REPOS='~/dev'
TTC_WEATHER=Munich
$ tiny-care-terminal
TypeError: Cannot read property 'slice' of null
    at /usr/local/lib/node_modules/tiny-care-terminal/node_modules/blessed/lib/program.js:2543:35
    at Array.forEach (native)
    at Program._attr (/usr/local/lib/node_modules/tiny-care-terminal/node_modules/blessed/lib/program.js:2542:11)
    at Box.Element._parseTags (/usr/local/lib/node_modules/tiny-care-terminal/node_modules/blessed/lib/widgets/element.js:498:26)
    at Box.Element.parseContent (/usr/local/lib/node_modules/tiny-care-terminal/node_modules/blessed/lib/widgets/element.js:393:22)
    at Box.Element.render (/usr/local/lib/node_modules/tiny-care-terminal/node_modules/blessed/lib/widgets/element.js:1839:8)
    at /usr/local/lib/node_modules/tiny-care-terminal/node_modules/blessed/lib/widgets/screen.js:738:8
    at Array.forEach (native)
    at Screen.render (/usr/local/lib/node_modules/tiny-care-terminal/node_modules/blessed/lib/widgets/screen.js:735:17)
    at Socket.week.stdout.on.data (/usr/local/lib/node_modules/tiny-care-terminal/care.js:120:12)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at readableAddChunk (_stream_readable.js:176:18)
    at Socket.Readable.push (_stream_readable.js:134:10)
    at Pipe.onread (net.js:551:20)

It looks like you only have 2 bots in TTC_BOTS -- i think that's where the slice is failing, maybe. Might adding a third?

What do you mean

I also tried with the default TTC_BOTS and an empty value. As mentioned, only the TTC_REPOS variable affects this issue.

Justin R Erwin
Lol well that sucks thanks bud for letting me know.... have yuo made
moneyvdoing this
On Apr 23, 2017 4:05 AM, "Andreas Sommer" notifications@github.com wrote:

I also tried with the default TTC_BOTS and an empty value. As mentioned,
only the TTC_REPOS variable affects this issue.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/notwaldorf/tiny-care-terminal/issues/47#issuecomment-296435481,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AanLawBKT0OvyHcSxM8NjAVdz94xAkqCks5ryzB2gaJpZM4NFBvY
.

Internet smaller then i thought
bitcoin:18kdVv5HREb44kcKYZ6cgnsQUXv8RoJ5Co?label=JUSTIN%20RAY%20ERWIN

I really can't repro this, nor have heard of anyone else having problems in this way :(

Then I'm happy for everyone else 👍 I'll leave this open and try to debug myself.

As of version 1.2.0 there's a new way to use the terminal that doesn't involve the bash script/ Would you mind updating to that and setting the TTC_GITBOT environment variable to gitlog, to see if that fixes your problems?

The problem resolved on its own recently. Hard to find out afterwards what the real reason was (such as the state of my 200+ Git repos)... 1.2.0 is also working fine for me. We can close this and hope it doesn't happen anymore ;) Thanks!

I'm also getting this error, and it's caused by a specific one of my git repos, it seems. :cry:

@jarednorman I've noticed I couldn't use a git repo with a dot in the name. Maybe it's that? :(

No dot or any other weird characters. It's just of the format "fooBar".

I've noticed I couldn't use a git repo with a dot in the name. Maybe it's that? :(

@notwaldorf Is this a git-log or an git-standup issue? I think this should be fixed!

Changing between git-log/git-standup has no effect on the error for me. The only thing that changes whether I get this error is whether I include this one repo I have in TTC_REPOS.

Mysteriously just started working today. :confounded:

I had the same problem, and traced it to curly braces in the commit messages wreaking havoc with the "tag parser" implemented in the blessed library.  The simplest fix is to set tags: false in makeBox(), but I'm not sure if there is an unrelated reason it needs to be set to true.  The alternative is to do something like content = content.replace(/[{}]/g, m => m === '{' ? '{open}' : '{close}'); inside getCommits().  Happy to submit a tiny-PR if you let me know which solution you think would be more appropriate :)

I also had this problem with just one repo, which had curly braces in commit messages. I applied @cfinucane's patch and it works. 😀

Having the same issue:
TypeError: Cannot read property 'slice' of null
    at /usr/local/lib/node_modules/tiny-care-terminal/node_modules/blessed/lib/program.js:2543:35
    at Array.forEach (<anonymous>)
    at Program._attr (/usr/local/lib/node_modules/tiny-care-terminal/node_modules/blessed/lib/program.js:2542:11)
    at Box.Element._parseTags (/usr/local/lib/node_modules/tiny-care-terminal/node_modules/blessed/lib/widgets/element.js:498:26)
    at Box.Element.parseContent (/usr/local/lib/node_modules/tiny-care-terminal/node_modules/blessed/lib/widgets/element.js:393:22)
    at Box.Element.render (/usr/local/lib/node_modules/tiny-care-terminal/node_modules/blessed/lib/widgets/element.js:1839:8)
    at /usr/local/lib/node_modules/tiny-care-terminal/node_modules/blessed/lib/widgets/screen.js:738:8
    at Array.forEach (<anonymous>)
    at Screen.render (/usr/local/lib/node_modules/tiny-care-terminal/node_modules/blessed/lib/widgets/screen.js:735:17)
    at gitbot.getCommitsFromRepos (/usr/local/lib/node_modules/tiny-care-terminal/care.js:207:16)
    at async.each.err (/usr/local/lib/node_modules/tiny-care-terminal/gitbot.js:88:5)
    at /usr/local/lib/node_modules/tiny-care-terminal/node_modules/async/lib/async.js:52:16
    at done (/usr/local/lib/node_modules/tiny-care-terminal/node_modules/async/lib/async.js:246:17)
    at /usr/local/lib/node_modules/tiny-care-terminal/node_modules/async/lib/async.js:44:16
    at gitlog (/usr/local/lib/node_modules/tiny-care-terminal/gitbot.js:82:9)
    at /usr/local/lib/node_modules/tiny-care-terminal/node_modules/gitlog/index.js:132:5

> node -v
v8.11.2

> npm -v
5.6.0

Probably also due to commits titled like
Rename ./build{,-dev}.sh to ./webpack-build{,-dev}.sh

I won't find the time in the near future to work on this issue. Maybe somebody can create a pull-request? It shouldn't be that hard. :crossed_fingers:

authors: AndiDog LeoniePhiline cfinucane cpuntryfried91 jarednorman mojoaxel notwaldorf timbeadle

repo: notwaldorf/tiny-care-terminal


text:
Add Support for Editing Text-only Files

Description
Non-previewable files, e.g. the .svelte-in-motion.json workspace configuration file, should not have a preview visible. And should have proper syntax highlighting.

Added e38e89250d597c0cdbc0c13c238fa62e8ebb076f

repo: novacbn/svelte-in-motion


text:
Fixed swap validation payload

#869347k4d

Task linked: CU-869347k4d Android. Must remain ed after non-sufficient swap

authors: antonijzelinskij stepanLav

repo: novasamatech/nova-wallet-android


text:
Menu error

After installing iceberg on Windows environment the world menu don't work anymore and fallback to a simpler version of it. Clicking on debug I get the following:
Author: vitor
ByteSymbol(Object)>>doesNotUnderstand: #asIcon
IceRepositoriesBrowser class>>icon
IceRepositoriesBrowser class>>menuCommandOn:
[ prg methodClass theNonMetaClass perform: prg selector with: menu ] in [ :prg |
self
currentRoot: self
while: [ prg methodClass theNonMetaClass perform: prg selector with: menu ] ] in PragmaMenuBuilder>>collectRegistrations
[ aBlock value ] in PragmaMenuBuilder>>currentRoot:while:
BlockClosure>>ensure:
PragmaMenuBuilder>>currentRoot:while:
[ :prg |
self
currentRoot: self
while: [ prg methodClass theNonMetaClass perform: prg selector with: menu ] ] in PragmaMenuBuilder>>collectRegistrations
OrderedCollection>>do:
PragmaCollector>>do:
PragmaMenuBuilder>>collectRegistrations
PragmaMenuBuilder>>buildTree
PragmaMenuBuilder>>menuSpecAt:
PragmaMenuBuilder>>menuSpec
[ builder menuSpec asMenuMorph ] in FallbackMenu>>debug
BlockClosure>>ensure:
FallbackMenu>>debug
[ | selArgCount |
"show cursor in case item opens a new MVC window"
(selArgCount := selector numArgs) = 0
ifTrue: [ target perform: selector ]
ifFalse: [ selArgCount = arguments size
ifTrue: [ target perform: selector withArguments: arguments ]
ifFalse: [ target perform: selector withArguments: (arguments copyWith: evt) ].
self showShortcut ].
self changed ] in ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent:
BlockClosure>>ensure:
CursorWithMask(Cursor)>>showWhile:
ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent:
ToggleMenuItemMorph(MenuItemMorph)>>mouseUp:
ToggleMenuItemMorph(MenuItemMorph)>>handleMouseUp:
MouseButtonEvent>>sentTo:
ToggleMenuItemMorph(Morph)>>handleEvent:
MorphicEventDispatcher>>dispatchDefault:with:
MorphicEventDispatcher>>handleMouseUp:
MouseButtonEvent>>sentTo:
[ ^ anEvent sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with:
BlockClosure>>ensure:
MorphicEventDispatcher>>dispatchEvent:with:
ToggleMenuItemMorph(Morph)>>processEvent:using:
MorphicEventDispatcher>>dispatchDefault:with:
MorphicEventDispatcher>>handleMouseUp:
MouseButtonEvent>>sentTo:
[ ^ anEvent sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with:
BlockClosure>>ensure:
MorphicEventDispatcher>>dispatchEvent:with:
MenuMorph(Morph)>>processEvent:using:
MenuMorph(Morph)>>processEvent:
MenuMorph>>handleFocusEvent:
[ ActiveHand := self.
ActiveEvent := anEvent.
result := focusHolder
handleFocusEvent: (anEvent transformedBy: (focusHolder transformedFrom: self)) ] in HandMorph>>sendFocusEvent:to:clear:
BlockClosure>>on:do:
WorldMorph(PasteUpMorph)>>becomeActiveDuring:
HandMorph>>sendFocusEvent:to:clear:
HandMorph>>sendEvent:focus:clear:
HandMorph>>sendMouseEvent:
HandMorph>>handleEvent:
HandMorph>>processEvents
[ :h |
ActiveHand := h.
h processEvents.
ActiveHand := nil ] in WorldState>>doOneCycleNowFor:
Array(SequenceableCollection)>>do:
WorldState>>handsDo:
WorldState>>doOneCycleNowFor:
WorldState>>doOneCycleFor:
WorldMorph>>doOneCycle
[ [ World doOneCycle.
Processor yield.
false ] whileFalse: [  ] ] in MorphicUIManager>>spawnNewProcess
[ self value.
Processor terminateActive ] in BlockClosure>>newProcess

i am sorry, I was using pharo 5

repo: npasserini/iceberg


text:
Error: unrecognized flag --no-opt

Hello,
we are getting this error when we try to install bower with npm , on docker with base image ruby-2.3.0
  => [rmdc_backend_app  4/18] RUN rm /etc/apt/sources.list                                                                                0.3s
  => [rmdc_backend_app  5/18] RUN echo "deb http://archive.debian.org/debian/ jessie main" | tee -a /etc/apt/sources.list                                            0.2s
   => [rmdc_backend_app  6/18] RUN echo "deb-src http://archive.debian.org/debian/ jessie main" | tee -a /etc/apt/sources.list                                        0.3s
 => [rmdc_backend_app  7/18] RUN echo "Acquire::Check-Valid-Until false;" | tee -a /etc/apt/apt.conf.d/10-nocheckvalid                                              0.3s
 => [rmdc_backend_app  8/18] RUN echo 'Package: *\nPin: origin "archive.debian.org"\nPin-Priority: 500' | tee -a /etc/apt/preferences.d/10-archive-pin              0.3s
 => [rmdc_backend_app  9/18] RUN apt-get update                                                                                7.3s
 => [rmdc_backend_app 10/18] RUN apt-get install -yq --force-yes build-essential git libpq-dev libmysqlclient-dev libav-tools libxml2-dev libxslt-dev nodejs-lega  38.8s
 => [rmdc_backend_app 11/18] RUN apt-get install -yq --force-yes npm                                                                                18.9s
 => ERROR [rmdc_backend_app 12/18] RUN npm install -g bower                                                                                0.6s
------
 > [rmdc_backend_app 12/18] RUN npm install -g bower:
0.314 Error: unrecognized flag --no-opt
0.314 Try --help for options
0.561
0.563 module.js:340
0.565     throw err;
0.565           ^
0.592 Error: Cannot find module 'process'
0.592     at Function.Module._resolveFilename (module.js:338:15)
0.592     at Function.Module._load (module.js:280:25)
0.592     at Module.require (module.js:364:17)
0.592     at require (module.js:380:17)
0.592     at Object.<anonymous> (/proc/.reset:1:71)
0.592     at Module._compile (module.js:456:26)
0.592     at Object.Module._extensions..js (module.js:474:10)
0.592     at Module.load (module.js:356:32)
0.592     at Function.Module._load (module.js:312:12)
0.592     at Function.Module.runMain (module.js:497:10)
------
failed to solve: process "/bin/sh -c npm install -g bower" did not complete successfully: exit code: 8

any Idea how to solve it ? and remove the place that call this option ?

What node and npm version is being used?
Either way, bower is long since dead and deprecated afaik. What do you need it for?

Please use the issue template

I need  (last value recorded) node -v => v14.17.6, npm -v  ===> 5.6.0
we need to install bower , so I used this in dockerfile
SHELL ["/bin/bash", "--login", "-i", "-c"]
RUN curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.2/install.sh | bash
RUN source /root/.bashrc && nvm install node
SHELL ["/bin/bash", "--login", "-c"]

but bower is not define in the entrypoint.sh
here is my old lines
RUN rm /etc/apt/sources.list
RUN echo "deb http://archive.debian.org/debian/ jessie main" | tee -a /etc/apt/sources.list
RUN echo "deb-src http://archive.debian.org/debian/ jessie main" | tee -a /etc/apt/sources.list
RUN echo "Acquire::Check-Valid-Until false;" | tee -a /etc/apt/apt.conf.d/10-nocheckvalid
RUN echo 'Package: *\nPin: origin "archive.debian.org"\nPin-Priority: 500' | tee -a /etc/apt/preferences.d/10-archive-pin
RUN apt-get update

RUN apt-get install -yq --force-yes \
build-essential \
git \
libpq-dev \
libmysqlclient-dev \
libav-tools \
libxml2-dev \
libxslt-dev \
nodejs-legacy \
imagemagick \
tzdata \
&& rm -rf /var/cache/apt/* \
&& mkdir -p $APP_PATH

RUN apt-get install -yq --force-yes npm
RUN npm install -g bower

RUN echo '{ "allow_root": true }' > /root/.bowerrc

in entrypoint.sh
bower cache clean
bower install --save moment

authors: eftikharEmad ljharb wraithgar

repo: npm/documentation


text:
インポート結果画面のプレビューアイコンが反応しない

そのバグについて
インポート結果画面のプレビューアイコンが反応しない
再現手順
ブックのインポート結果画面を見る
期待していた動作
プレビューが見える．もしくは，結果画面ではプレビューアイコンを表示させない．
UIデザインの改修も今後あるので，現時点でやるなら楽な方で良い．
スクリーンショット

デスクトップ再現環境 (下記をうめてください):

OS:Windows10
ブラウザ: chrome
Version:  93.0.4577.63

@ties-makimura #523 で対応したので、最新のmasterにて確認いただいて問題なければcloseをお願いします :pray:

プレビューが表示されるようになりました．問題ないです．

repo: npocccties/chibichilo


text:
document.write blocked by chrome 54

http://blog.dareboost.com/en/2016/09/avoid-using-document-write-scripts-injection/

Where are you using document.write in pym.js?

authors: AlainVagner jjelosua


text:
fix: python 3.11 support.

resolves #228

Codecov Report

Merging #229 (fa21295) into main (5084c38) will decrease coverage by 0.06%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #229      +/-   ##
==========================================
- Coverage   90.16%   90.09%   -0.07%
==========================================
  Files          31       31
  Lines        1464     1464
==========================================
- Hits         1320     1319       -1
- Misses        144      145       +1

Impacted Files
Coverage Δ

gqlauth/captcha/models.py
74.57% <100.00%> (ø)

gqlauth/core/utils.py
79.33% <0.00%> (-0.83%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

authors: codecov-commenter nrbnlulu

repo: nrbnlulu/strawberry-django-auth


text:
update icons

COR-481
replacing the icons with new icons without the vacant space around them to facilitate sizing them in other components
also introduces new icons, for e.g. the accordion

/lgtm

repo: nrc-no/core


text:
switch to vanilla @angular/cli 1.5.0

Thanks for your excellent work. Do you guys plan to switch to vanilla cli 1.5.x?

See https://github.com/nrwl/nx/wiki/FAQ

authors: emilio-martinez vecernik

repo: nrwl/fix-cli-build


text:
TODO: ring buffer

Either create one or use Boost circular buffer

Resolved in #17

repo: nsdrozario/guitar-amp