install scripts failing (was collect_mail.py broken)

I made two clean installs, on two machines, both with anaconda and with pip, and I get the same error when trying to run this script:
$ python bin/collect_mail.py -f examples/url_collections/mm.ietf.org.txt
Traceback (most recent call last):
  File "bin/collect_mail.py", line 3, in <module>
    import bigbang.mailman as mailman
ImportError: No module named bigbang.mailman

Are you creating a virtualenv or conda environment for bigbang and then running conda-setup.sh (or pip install -r requirements.txt) from within it? I generally try to do that and then run scripts like bin/collect_mail from within that environment.
This error message looks like the "pip install -e ." command wasn't run, and so the bigbang modules aren't in the pythonpath.

Thanks @npdoty
This happened when I used pip (TL;DR: I got it to work by making it explicit that I use Python3 - probably we should add that to the README.md, as well as 'cd bigbang', before running 'pip install -r requirements.txt')
Conda is still a problem, it is below this code blob.
(bigbang) ➜  Data git clone https://github.com/datactive/bigbang
Cloning into 'bigbang'...
remote: Enumerating objects: 230, done.
remote: Counting objects: 100% (230/230), done.
remote: Compressing objects: 100% (194/194), done.
remote: Total 3256 (delta 100), reused 91 (delta 34), pack-reused 3026
Receiving objects: 100% (3256/3256), 39.10 MiB | 2.99 MiB/s, done.
Resolving deltas: 100% (1943/1943), done.
(bigbang) ➜  Data cd bigbang
(bigbang) ➜  bigbang git:(master) pip install -r requirements.txt
Obtaining file:///home/lem/Data/bigbang (from -r requirements.txt (line 1))
Collecting git+https://github.com/gitpython-developers/GitPython.git (from -r requirements.txt (line 31))
  Cloning https://github.com/gitpython-developers/GitPython.git to /tmp/pip-req-build-beqb_7a1
  Running command git clone -q https://github.com/gitpython-developers/GitPython.git /tmp/pip-req-build-beqb_7a1
  Running command git submodule update --init --recursive -q
Requirement already satisfied (use --upgrade to upgrade): GitPython==3.1.2 from git+https://github.com/gitpython-developers/GitPython.git in /home/lem/.local/lib/python3.8/site-packages (from -r requirements.txt (line 31))
Requirement already satisfied: beautifulsoup4 in /usr/lib/python3/dist-packages (from -r requirements.txt (line 3)) (4.9.0)
Requirement already satisfied: chardet in /usr/lib/python3/dist-packages (from -r requirements.txt (line 4)) (3.0.4)
Requirement already satisfied: coverage in /home/lem/.local/lib/python3.8/site-packages (from -r requirements.txt (line 5)) (5.1)
Requirement already satisfied: enlighten in /home/lem/.local/lib/python3.8/site-packages (from -r requirements.txt (line 6)) (1.5.2)
Requirement already satisfied: gender-detector in /home/lem/.local/lib/python3.8/site-packages (from -r requirements.txt (line 7)) (0.1.0)
Requirement already satisfied: html2text in /usr/lib/python3/dist-packages (from -r requirements.txt (line 8)) (2020.1.16)
Requirement already satisfied: ipython in /home/lem/.local/lib/python3.8/site-packages (from -r requirements.txt (line 9)) (7.14.0)
Requirement already satisfied: jinja2 in /usr/lib/python3/dist-packages (from -r requirements.txt (line 10)) (2.10.1)
Requirement already satisfied: jupyter in /home/lem/.local/lib/python3.8/site-packages (from -r requirements.txt (line 11)) (1.0.0)
Requirement already satisfied: jsonschema in /home/lem/.local/lib/python3.8/site-packages (from -r requirements.txt (line 12)) (3.2.0)
Requirement already satisfied: gitpython in /home/lem/.local/lib/python3.8/site-packages (from -r requirements.txt (line 13)) (3.1.2)
Requirement already satisfied: matplotlib in /home/lem/.local/lib/python3.8/site-packages (from -r requirements.txt (line 14)) (3.2.1)
Requirement already satisfied: networkx in /home/lem/.local/lib/python3.8/site-packages (from -r requirements.txt (line 15)) (2.4)
Requirement already satisfied: nltk in /home/lem/.local/lib/python3.8/site-packages (from -r requirements.txt (line 16)) (3.5)
Requirement already satisfied: numpy in /usr/lib/python3/dist-packages (from -r requirements.txt (line 17)) (1.17.4)
Requirement already satisfied: pandas in /home/lem/.local/lib/python3.8/site-packages (from -r requirements.txt (line 18)) (1.0.3)
Requirement already satisfied: pytest in /home/lem/.local/lib/python3.8/site-packages (from -r requirements.txt (line 19)) (5.4.2)
Requirement already satisfied: python-dateutil in /usr/lib/python3/dist-packages (from -r requirements.txt (line 20)) (2.8.1)
Requirement already satisfied: python-Levenshtein in /home/lem/.local/lib/python3.8/site-packages (from -r requirements.txt (line 21)) (0.12.0)
Requirement already satisfied: pytz in /home/lem/.local/lib/python3.8/site-packages (from -r requirements.txt (line 22)) (2020.1)
Requirement already satisfied: pyzmq in /home/lem/.local/lib/python3.8/site-packages (from -r requirements.txt (line 23)) (19.0.1)
Requirement already satisfied: tornado in /home/lem/.local/lib/python3.8/site-packages (from -r requirements.txt (line 24)) (6.0.4)
Requirement already satisfied: requests in /usr/lib/python3/dist-packages (from -r requirements.txt (line 25)) (2.23.0)
Requirement already satisfied: pyyaml in /usr/lib/python3/dist-packages (from -r requirements.txt (line 26)) (5.3.1)
Requirement already satisfied: common in /home/lem/.local/lib/python3.8/site-packages (from -r requirements.txt (line 27)) (0.1.2)
Requirement already satisfied: powerlaw in /home/lem/.local/lib/python3.8/site-packages (from -r requirements.txt (line 28)) (1.4.6)
Requirement already satisfied: validators in /home/lem/.local/lib/python3.8/site-packages (from -r requirements.txt (line 29)) (0.15.0)
Requirement already satisfied: testfixtures in /home/lem/.local/lib/python3.8/site-packages (from -r requirements.txt (line 30)) (6.14.1)
Requirement already satisfied: gitdb<5,>=4.0.1 in /home/lem/.local/lib/python3.8/site-packages (from GitPython==3.1.2->-r requirements.txt (line 31)) (4.0.5)
Requirement already satisfied: blessed>=1.17.2 in /home/lem/.local/lib/python3.8/site-packages (from enlighten->-r requirements.txt (line 6)) (1.17.5)
Requirement already satisfied: setuptools>=18.5 in /usr/lib/python3/dist-packages (from ipython->-r requirements.txt (line 9)) (46.1.3)
Requirement already satisfied: jedi>=0.10 in /home/lem/.local/lib/python3.8/site-packages (from ipython->-r requirements.txt (line 9)) (0.17.0)
Requirement already satisfied: backcall in /home/lem/.local/lib/python3.8/site-packages (from ipython->-r requirements.txt (line 9)) (0.1.0)
Requirement already satisfied: prompt-toolkit!=3.0.0,!=3.0.1,<3.1.0,>=2.0.0 in /home/lem/.local/lib/python3.8/site-packages (from ipython->-r requirements.txt (line 9)) (3.0.5)
Requirement already satisfied: pygments in /usr/lib/python3/dist-packages (from ipython->-r requirements.txt (line 9)) (2.3.1)
Requirement already satisfied: decorator in /home/lem/.local/lib/python3.8/site-packages (from ipython->-r requirements.txt (line 9)) (4.4.2)
Requirement already satisfied: traitlets>=4.2 in /home/lem/.local/lib/python3.8/site-packages (from ipython->-r requirements.txt (line 9)) (4.3.3)
Requirement already satisfied: pexpect; sys_platform != "win32" in /usr/lib/python3/dist-packages (from ipython->-r requirements.txt (line 9)) (4.6.0)
Requirement already satisfied: pickleshare in /home/lem/.local/lib/python3.8/site-packages (from ipython->-r requirements.txt (line 9)) (0.7.5)
Requirement already satisfied: qtconsole in /home/lem/.local/lib/python3.8/site-packages (from jupyter->-r requirements.txt (line 11)) (4.7.4)
Requirement already satisfied: notebook in /home/lem/.local/lib/python3.8/site-packages (from jupyter->-r requirements.txt (line 11)) (6.0.3)
Requirement already satisfied: jupyter-console in /home/lem/.local/lib/python3.8/site-packages (from jupyter->-r requirements.txt (line 11)) (6.1.0)
Requirement already satisfied: nbconvert in /home/lem/.local/lib/python3.8/site-packages (from jupyter->-r requirements.txt (line 11)) (5.6.1)
Requirement already satisfied: ipywidgets in /home/lem/.local/lib/python3.8/site-packages (from jupyter->-r requirements.txt (line 11)) (7.5.1)
Requirement already satisfied: ipykernel in /home/lem/.local/lib/python3.8/site-packages (from jupyter->-r requirements.txt (line 11)) (5.3.0)
Requirement already satisfied: attrs>=17.4.0 in /home/lem/.local/lib/python3.8/site-packages (from jsonschema->-r requirements.txt (line 12)) (19.3.0)
Requirement already satisfied: six>=1.11.0 in /usr/lib/python3/dist-packages (from jsonschema->-r requirements.txt (line 12)) (1.14.0)
Requirement already satisfied: pyrsistent>=0.14.0 in /home/lem/.local/lib/python3.8/site-packages (from jsonschema->-r requirements.txt (line 12)) (0.16.0)
Requirement already satisfied: kiwisolver>=1.0.1 in /home/lem/.local/lib/python3.8/site-packages (from matplotlib->-r requirements.txt (line 14)) (1.2.0)
Requirement already satisfied: pyparsing!=2.0.4,!=2.1.2,!=2.1.6,>=2.0.1 in /usr/lib/python3/dist-packages (from matplotlib->-r requirements.txt (line 14)) (2.4.7)
Requirement already satisfied: cycler>=0.10 in /home/lem/.local/lib/python3.8/site-packages (from matplotlib->-r requirements.txt (line 14)) (0.10.0)
Requirement already satisfied: click in /usr/lib/python3/dist-packages (from nltk->-r requirements.txt (line 16)) (7.0)
Requirement already satisfied: regex in /usr/lib/python3/dist-packages (from nltk->-r requirements.txt (line 16)) (2019.8.19)
Requirement already satisfied: tqdm in /home/lem/.local/lib/python3.8/site-packages (from nltk->-r requirements.txt (line 16)) (4.46.0)
Requirement already satisfied: joblib in /home/lem/.local/lib/python3.8/site-packages (from nltk->-r requirements.txt (line 16)) (0.15.1)
Requirement already satisfied: wcwidth in /home/lem/.local/lib/python3.8/site-packages (from pytest->-r requirements.txt (line 19)) (0.1.9)
Requirement already satisfied: pluggy<1.0,>=0.12 in /home/lem/.local/lib/python3.8/site-packages (from pytest->-r requirements.txt (line 19)) (0.13.1)
Requirement already satisfied: py>=1.5.0 in /home/lem/.local/lib/python3.8/site-packages (from pytest->-r requirements.txt (line 19)) (1.8.1)
Requirement already satisfied: more-itertools>=4.0.0 in /home/lem/.local/lib/python3.8/site-packages (from pytest->-r requirements.txt (line 19)) (8.3.0)
Requirement already satisfied: packaging in /home/lem/.local/lib/python3.8/site-packages (from pytest->-r requirements.txt (line 19)) (20.4)
Requirement already satisfied: mpmath in /home/lem/.local/lib/python3.8/site-packages (from powerlaw->-r requirements.txt (line 28)) (1.1.0)
Requirement already satisfied: scipy in /home/lem/.local/lib/python3.8/site-packages (from powerlaw->-r requirements.txt (line 28)) (1.4.1)
Requirement already satisfied: smmap<4,>=3.0.1 in /home/lem/.local/lib/python3.8/site-packages (from gitdb<5,>=4.0.1->GitPython==3.1.2->-r requirements.txt (line 31)) (3.0.4)
Requirement already satisfied: parso>=0.7.0 in /home/lem/.local/lib/python3.8/site-packages (from jedi>=0.10->ipython->-r requirements.txt (line 9)) (0.7.0)
Requirement already satisfied: ipython-genutils in /home/lem/.local/lib/python3.8/site-packages (from traitlets>=4.2->ipython->-r requirements.txt (line 9)) (0.2.0)
Requirement already satisfied: jupyter-client>=4.1 in /home/lem/.local/lib/python3.8/site-packages (from qtconsole->jupyter->-r requirements.txt (line 11)) (6.1.3)
Requirement already satisfied: jupyter-core in /home/lem/.local/lib/python3.8/site-packages (from qtconsole->jupyter->-r requirements.txt (line 11)) (4.6.3)
Requirement already satisfied: qtpy in /home/lem/.local/lib/python3.8/site-packages (from qtconsole->jupyter->-r requirements.txt (line 11)) (1.9.0)
Requirement already satisfied: nbformat in /home/lem/.local/lib/python3.8/site-packages (from notebook->jupyter->-r requirements.txt (line 11)) (5.0.6)
Requirement already satisfied: prometheus-client in /home/lem/.local/lib/python3.8/site-packages (from notebook->jupyter->-r requirements.txt (line 11)) (0.7.1)
Requirement already satisfied: terminado>=0.8.1 in /home/lem/.local/lib/python3.8/site-packages (from notebook->jupyter->-r requirements.txt (line 11)) (0.8.3)
Requirement already satisfied: Send2Trash in /home/lem/.local/lib/python3.8/site-packages (from notebook->jupyter->-r requirements.txt (line 11)) (1.5.0)
Requirement already satisfied: testpath in /home/lem/.local/lib/python3.8/site-packages (from nbconvert->jupyter->-r requirements.txt (line 11)) (0.4.4)
Requirement already satisfied: pandocfilters>=1.4.1 in /home/lem/.local/lib/python3.8/site-packages (from nbconvert->jupyter->-r requirements.txt (line 11)) (1.4.2)
Requirement already satisfied: mistune<2,>=0.8.1 in /home/lem/.local/lib/python3.8/site-packages (from nbconvert->jupyter->-r requirements.txt (line 11)) (0.8.4)
Requirement already satisfied: defusedxml in /usr/lib/python3/dist-packages (from nbconvert->jupyter->-r requirements.txt (line 11)) (0.6.0)
Requirement already satisfied: bleach in /home/lem/.local/lib/python3.8/site-packages (from nbconvert->jupyter->-r requirements.txt (line 11)) (3.1.5)
Requirement already satisfied: entrypoints>=0.2.2 in /home/lem/.local/lib/python3.8/site-packages (from nbconvert->jupyter->-r requirements.txt (line 11)) (0.3)
Requirement already satisfied: widgetsnbextension~=3.5.0 in /home/lem/.local/lib/python3.8/site-packages (from ipywidgets->jupyter->-r requirements.txt (line 11)) (3.5.1)
Requirement already satisfied: ptyprocess; os_name != "nt" in /home/lem/.local/lib/python3.8/site-packages (from terminado>=0.8.1->notebook->jupyter->-r requirements.txt (line 11)) (0.6.0)
Requirement already satisfied: webencodings in /usr/lib/python3/dist-packages (from bleach->nbconvert->jupyter->-r requirements.txt (line 11)) (0.5.1)
Installing collected packages: BigBang
  Running setup.py develop for BigBang
Successfully installed BigBang
(bigbang) ➜  bigbang git:(master) python3 setup.py develop
running develop
error: can't create or remove files in install directory

The following error occurred while trying to add or remove files in the
installation directory:

    [Errno 13] Permission denied: '/usr/local/lib/python3.8/dist-packages/test-easy-install-374560.write-test'

The installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:

    /usr/local/lib/python3.8/dist-packages/

Perhaps your account does not have write access to this directory?  If the
installation directory is a system-owned directory, you may need to sign in
as the administrator or "root" account.  If you do not have administrative
access to this machine, you may wish to choose a different installation
directory, preferably one that is listed in your PYTHONPATH environment
variable.

For information on other options, you may wish to consult the
documentation at:

  https://setuptools.readthedocs.io/en/latest/easy_install.html

Please make the appropriate changes for your system and try again.

(bigbang) ➜  bigbang git:(master) sudo python3 setup.py develop
running develop
running egg_info
writing BigBang.egg-info/PKG-INFO
writing dependency_links to BigBang.egg-info/dependency_links.txt
writing requirements to BigBang.egg-info/requires.txt
writing top-level names to BigBang.egg-info/top_level.txt
reading manifest file 'BigBang.egg-info/SOURCES.txt'
writing manifest file 'BigBang.egg-info/SOURCES.txt'
running build_ext
Creating /usr/local/lib/python3.8/dist-packages/BigBang.egg-link (link to .)
BigBang 0.1 is already the active version in easy-install.pth

Installed /home/lem/Data/bigbang
Processing dependencies for BigBang==0.1
Searching for tornado==6.0.4
Best match: tornado 6.0.4
Processing tornado-6.0.4-py3.8-linux-x86_64.egg
tornado 6.0.4 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/tornado-6.0.4-py3.8-linux-x86_64.egg
Searching for requests==2.23.0
Best match: requests 2.23.0
Adding requests 2.23.0 to easy-install.pth file

Using /usr/lib/python3/dist-packages
Searching for pyzmq==19.0.1
Best match: pyzmq 19.0.1
Processing pyzmq-19.0.1-py3.8-linux-x86_64.egg
pyzmq 19.0.1 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/pyzmq-19.0.1-py3.8-linux-x86_64.egg
Searching for PyYAML==5.3.1
Best match: PyYAML 5.3.1
Adding PyYAML 5.3.1 to easy-install.pth file

Using /usr/lib/python3/dist-packages
Searching for pytz==2020.1
Best match: pytz 2020.1
Processing pytz-2020.1-py3.8.egg
pytz 2020.1 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/pytz-2020.1-py3.8.egg
Searching for python-dateutil==2.8.1
Best match: python-dateutil 2.8.1
Adding python-dateutil 2.8.1 to easy-install.pth file

Using /usr/lib/python3/dist-packages
Searching for python-Levenshtein==0.12.0
Best match: python-Levenshtein 0.12.0
Processing python_Levenshtein-0.12.0-py3.8-linux-x86_64.egg
python-Levenshtein 0.12.0 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/python_Levenshtein-0.12.0-py3.8-linux-x86_64.egg
Searching for pytest==5.4.2
Best match: pytest 5.4.2
Processing pytest-5.4.2-py3.8.egg
pytest 5.4.2 is already the active version in easy-install.pth
Installing py.test script to /usr/local/bin
Installing pytest script to /usr/local/bin

Using /usr/local/lib/python3.8/dist-packages/pytest-5.4.2-py3.8.egg
Searching for powerlaw==1.4.6
Best match: powerlaw 1.4.6
Processing powerlaw-1.4.6-py3.8.egg
powerlaw 1.4.6 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/powerlaw-1.4.6-py3.8.egg
Searching for pandas==1.0.3
Best match: pandas 1.0.3
Processing pandas-1.0.3-py3.8-linux-x86_64.egg
pandas 1.0.3 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/pandas-1.0.3-py3.8-linux-x86_64.egg
Searching for numpy==1.17.4
Best match: numpy 1.17.4
Adding numpy 1.17.4 to easy-install.pth file
Installing f2py script to /usr/local/bin
Installing f2py3 script to /usr/local/bin
Installing f2py3.7 script to /usr/local/bin
Installing f2py3.8 script to /usr/local/bin

Using /usr/lib/python3/dist-packages
Searching for networkx==2.4
Best match: networkx 2.4
Processing networkx-2.4-py3.8.egg
networkx 2.4 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/networkx-2.4-py3.8.egg
Searching for matplotlib==3.2.1
Best match: matplotlib 3.2.1
Processing matplotlib-3.2.1-py3.8-linux-x86_64.egg
matplotlib 3.2.1 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/matplotlib-3.2.1-py3.8-linux-x86_64.egg
Searching for jsonschema==3.2.0
Best match: jsonschema 3.2.0
Processing jsonschema-3.2.0-py3.8.egg
jsonschema 3.2.0 is already the active version in easy-install.pth
Installing jsonschema script to /usr/local/bin

Using /usr/local/lib/python3.8/dist-packages/jsonschema-3.2.0-py3.8.egg
Searching for Jinja2==2.10.1
Best match: Jinja2 2.10.1
Adding Jinja2 2.10.1 to easy-install.pth file

Using /usr/lib/python3/dist-packages
Searching for ipython==7.14.0
Best match: ipython 7.14.0
Processing ipython-7.14.0-py3.8.egg
ipython 7.14.0 is already the active version in easy-install.pth
Installing iptest script to /usr/local/bin
Installing iptest3 script to /usr/local/bin
Installing ipython script to /usr/local/bin
Installing ipython3 script to /usr/local/bin

Using /usr/local/lib/python3.8/dist-packages/ipython-7.14.0-py3.8.egg
Searching for html2text==2020.1.16
Best match: html2text 2020.1.16
Adding html2text 2020.1.16 to easy-install.pth file
Installing html2text script to /usr/local/bin

Using /usr/lib/python3/dist-packages
Searching for coverage==5.1
Best match: coverage 5.1
Processing coverage-5.1-py3.8-linux-x86_64.egg
coverage 5.1 is already the active version in easy-install.pth
Installing coverage script to /usr/local/bin
Installing coverage-3.8 script to /usr/local/bin
Installing coverage3 script to /usr/local/bin

Using /usr/local/lib/python3.8/dist-packages/coverage-5.1-py3.8-linux-x86_64.egg
Searching for common==0.1.2
Best match: common 0.1.2
Processing common-0.1.2-py3.8.egg
common 0.1.2 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/common-0.1.2-py3.8.egg
Searching for chardet==3.0.4
Best match: chardet 3.0.4
Adding chardet 3.0.4 to easy-install.pth file
Installing chardetect script to /usr/local/bin

Using /usr/lib/python3/dist-packages
Searching for beautifulsoup4==4.9.0
Best match: beautifulsoup4 4.9.0
Adding beautifulsoup4 4.9.0 to easy-install.pth file

Using /usr/lib/python3/dist-packages
Searching for setuptools==46.1.3
Best match: setuptools 46.1.3
Adding setuptools 46.1.3 to easy-install.pth file
Installing easy_install script to /usr/local/bin

Using /usr/lib/python3/dist-packages
Searching for wcwidth==0.1.9
Best match: wcwidth 0.1.9
Processing wcwidth-0.1.9-py3.8.egg
wcwidth 0.1.9 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/wcwidth-0.1.9-py3.8.egg
Searching for py==1.8.1
Best match: py 1.8.1
Processing py-1.8.1-py3.8.egg
py 1.8.1 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/py-1.8.1-py3.8.egg
Searching for pluggy==0.13.1
Best match: pluggy 0.13.1
Processing pluggy-0.13.1-py3.8.egg
pluggy 0.13.1 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/pluggy-0.13.1-py3.8.egg
Searching for packaging==20.4
Best match: packaging 20.4
Processing packaging-20.4-py3.8.egg
packaging 20.4 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/packaging-20.4-py3.8.egg
Searching for more-itertools==8.3.0
Best match: more-itertools 8.3.0
Processing more_itertools-8.3.0-py3.8.egg
more-itertools 8.3.0 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/more_itertools-8.3.0-py3.8.egg
Searching for attrs==19.3.0
Best match: attrs 19.3.0
Processing attrs-19.3.0-py3.8.egg
attrs 19.3.0 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/attrs-19.3.0-py3.8.egg
Searching for scipy==1.4.1
Best match: scipy 1.4.1
Processing scipy-1.4.1-py3.8-linux-x86_64.egg
scipy 1.4.1 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/scipy-1.4.1-py3.8-linux-x86_64.egg
Searching for mpmath==1.1.0
Best match: mpmath 1.1.0
Processing mpmath-1.1.0-py3.8.egg
mpmath 1.1.0 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/mpmath-1.1.0-py3.8.egg
Searching for decorator==4.4.2
Best match: decorator 4.4.2
Processing decorator-4.4.2-py3.8.egg
decorator 4.4.2 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/decorator-4.4.2-py3.8.egg
Searching for pyparsing==2.4.7
Best match: pyparsing 2.4.7
Adding pyparsing 2.4.7 to easy-install.pth file

Using /usr/lib/python3/dist-packages
Searching for kiwisolver==1.2.0
Best match: kiwisolver 1.2.0
Processing kiwisolver-1.2.0-py3.8-linux-x86_64.egg
kiwisolver 1.2.0 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/kiwisolver-1.2.0-py3.8-linux-x86_64.egg
Searching for cycler==0.10.0
Best match: cycler 0.10.0
Processing cycler-0.10.0-py3.8.egg
cycler 0.10.0 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/cycler-0.10.0-py3.8.egg
Searching for six==1.14.0
Best match: six 1.14.0
Adding six 1.14.0 to easy-install.pth file

Using /usr/lib/python3/dist-packages
Searching for pyrsistent==0.16.0
Best match: pyrsistent 0.16.0
Processing pyrsistent-0.16.0-py3.8-linux-x86_64.egg
pyrsistent 0.16.0 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/pyrsistent-0.16.0-py3.8-linux-x86_64.egg
Searching for traitlets==4.3.3
Best match: traitlets 4.3.3
Processing traitlets-4.3.3-py3.8.egg
traitlets 4.3.3 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/traitlets-4.3.3-py3.8.egg
Searching for Pygments==2.3.1
Best match: Pygments 2.3.1
Adding Pygments 2.3.1 to easy-install.pth file
Installing pygmentize script to /usr/local/bin

Using /usr/lib/python3/dist-packages
Searching for prompt-toolkit==3.0.5
Best match: prompt-toolkit 3.0.5
Processing prompt_toolkit-3.0.5-py3.8.egg
prompt-toolkit 3.0.5 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/prompt_toolkit-3.0.5-py3.8.egg
Searching for pickleshare==0.7.5
Best match: pickleshare 0.7.5
Processing pickleshare-0.7.5-py3.8.egg
pickleshare 0.7.5 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/pickleshare-0.7.5-py3.8.egg
Searching for pexpect==4.6.0
Best match: pexpect 4.6.0
Adding pexpect 4.6.0 to easy-install.pth file

Using /usr/lib/python3/dist-packages
Searching for jedi==0.17.0
Best match: jedi 0.17.0
Processing jedi-0.17.0-py3.8.egg
jedi 0.17.0 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/jedi-0.17.0-py3.8.egg
Searching for backcall==0.1.0
Best match: backcall 0.1.0
Processing backcall-0.1.0-py3.8.egg
backcall 0.1.0 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/backcall-0.1.0-py3.8.egg
Searching for ipython-genutils==0.2.0
Best match: ipython-genutils 0.2.0
Processing ipython_genutils-0.2.0-py3.8.egg
ipython-genutils 0.2.0 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/ipython_genutils-0.2.0-py3.8.egg
Searching for parso==0.7.0
Best match: parso 0.7.0
Processing parso-0.7.0-py3.8.egg
parso 0.7.0 is already the active version in easy-install.pth

Using /usr/local/lib/python3.8/dist-packages/parso-0.7.0-py3.8.egg
Finished processing dependencies for BigBang==0.1
(bigbang) ➜  bigbang git:(master) python3 bin/collect_mail.py -f examples/url_collections/mm.ietf.org.txt

This is what happened when I used conda:
git clone https://github.com/datactive/bigbang
Cloning into 'bigbang'...
remote: Enumerating objects: 230, done.
remote: Counting objects: 100% (230/230), done.
remote: Compressing objects: 100% (194/194), done.
remote: Total 3256 (delta 100), reused 91 (delta 34), pack-reused 3026
Receiving objects: 100% (3256/3256), 39.10 MiB | 3.26 MiB/s, done.
Resolving deltas: 100% (1943/1943), done.
➜  Data conda ~/Data/anaconda3/bin/conda create -n bigbang
zsh: command not found: conda
➜  Data ~/Data/anaconda3/bin/conda create -n bigbang
WARNING: A conda environment already exists at '/home/lem/Data/anaconda3/envs/bigbang'
Remove existing environment (y/[n])? y

Collecting package metadata (current_repodata.json): done
Solving environment: done

==> WARNING: A newer version of conda exists. <==
  current version: 4.8.2
  latest version: 4.8.3

Please update conda by running

    $ conda update -n base -c defaults conda

## Package Plan ##

  environment location: /home/lem/Data/anaconda3/envs/bigbang

Proceed ([y]/n)? y

Preparing transaction: done
Verifying transaction: done
Executing transaction: done
#
# To activate this environment, use
#
#     $ conda activate bigbang
#
# To deactivate an active environment, use
#
#     $ conda deactivate

➜  Data cd bigbang
➜  bigbang git:(master) bash conda-setup.sh
conda-setup.sh: line 1: conda: command not found
conda-setup.sh: line 2: activate: No such file or directory
Requirement already satisfied: chardet in /usr/lib/python3/dist-packages (3.0.4)
Requirement already satisfied: enlighten in /home/lem/.local/lib/python3.8/site-packages (1.5.2)
Requirement already satisfied: blessed>=1.17.2 in /home/lem/.local/lib/python3.8/site-packages (from enlighten) (1.17.5)
Requirement already satisfied: six>=1.9.0 in /usr/lib/python3/dist-packages (from blessed>=1.17.2->enlighten) (1.14.0)
Requirement already satisfied: wcwidth>=0.1.4 in /home/lem/.local/lib/python3.8/site-packages (from blessed>=1.17.2->enlighten) (0.1.9)
Requirement already satisfied: html2text in /usr/lib/python3/dist-packages (2020.1.16)
Requirement already satisfied: gender_detector in /home/lem/.local/lib/python3.8/site-packages (0.1.0)
Requirement already satisfied: python-Levenshtein in /home/lem/.local/lib/python3.8/site-packages (0.12.0)
Requirement already satisfied: setuptools in /usr/lib/python3/dist-packages (from python-Levenshtein) (46.1.3)
Requirement already satisfied: common in /home/lem/.local/lib/python3.8/site-packages (0.1.2)
Requirement already satisfied: validators in /home/lem/.local/lib/python3.8/site-packages (0.15.0)
Requirement already satisfied: decorator>=3.4.0 in /home/lem/.local/lib/python3.8/site-packages (from validators) (4.4.2)
Requirement already satisfied: six>=1.4.0 in /usr/lib/python3/dist-packages (from validators) (1.14.0)
Collecting git+https://github.com/gitpython-developers/GitPython.git
  Cloning https://github.com/gitpython-developers/GitPython.git to /tmp/pip-req-build-mlpkbkqs
  Running command git clone -q https://github.com/gitpython-developers/GitPython.git /tmp/pip-req-build-mlpkbkqs
  Running command git submodule update --init --recursive -q
Requirement already satisfied (use --upgrade to upgrade): GitPython==3.1.2 from git+https://github.com/gitpython-developers/GitPython.git in /home/lem/.local/lib/python3.8/site-packages
Requirement already satisfied: gitdb<5,>=4.0.1 in /home/lem/.local/lib/python3.8/site-packages (from GitPython==3.1.2) (4.0.5)
Requirement already satisfied: smmap<4,>=3.0.1 in /home/lem/.local/lib/python3.8/site-packages (from gitdb<5,>=4.0.1->GitPython==3.1.2) (3.0.4)
Building wheels for collected packages: GitPython
  Building wheel for GitPython (setup.py) ... done
  Created wheel for GitPython: filename=GitPython-3.1.2-py3-none-any.whl size=451056 sha256=4bb521a1c806adecf985e28138734f2e9305309a4decbf340c5b08dc6651aaae
  Stored in directory: /tmp/pip-ephem-wheel-cache-agfinaha/wheels/ea/6b/f4/385a843befdf6715afb0fc68594be9dafbb3e318512dc3ecaf
Successfully built GitPython
Obtaining file:///home/lem/Data/bigbang
Requirement already satisfied: beautifulsoup4 in /usr/lib/python3/dist-packages (from BigBang==0.1) (4.9.0)
Requirement already satisfied: chardet in /usr/lib/python3/dist-packages (from BigBang==0.1) (3.0.4)
Requirement already satisfied: common in /home/lem/.local/lib/python3.8/site-packages (from BigBang==0.1) (0.1.2)
Requirement already satisfied: coverage in /home/lem/.local/lib/python3.8/site-packages (from BigBang==0.1) (5.1)
Requirement already satisfied: html2text in /usr/lib/python3/dist-packages (from BigBang==0.1) (2020.1.16)
Requirement already satisfied: ipython in /home/lem/.local/lib/python3.8/site-packages (from BigBang==0.1) (7.14.0)
Requirement already satisfied: jinja2 in /usr/lib/python3/dist-packages (from BigBang==0.1) (2.10.1)
Requirement already satisfied: jsonschema in /home/lem/.local/lib/python3.8/site-packages (from BigBang==0.1) (3.2.0)
Requirement already satisfied: matplotlib in /home/lem/.local/lib/python3.8/site-packages (from BigBang==0.1) (3.2.1)
Requirement already satisfied: networkx in /home/lem/.local/lib/python3.8/site-packages (from BigBang==0.1) (2.4)
Requirement already satisfied: numpy in /usr/lib/python3/dist-packages (from BigBang==0.1) (1.17.4)
Requirement already satisfied: pandas in /home/lem/.local/lib/python3.8/site-packages (from BigBang==0.1) (1.0.3)
Requirement already satisfied: powerlaw in /home/lem/.local/lib/python3.8/site-packages (from BigBang==0.1) (1.4.6)
Requirement already satisfied: pytest in /home/lem/.local/lib/python3.8/site-packages (from BigBang==0.1) (5.4.2)
Requirement already satisfied: python-Levenshtein in /home/lem/.local/lib/python3.8/site-packages (from BigBang==0.1) (0.12.0)
Requirement already satisfied: python-dateutil in /usr/lib/python3/dist-packages (from BigBang==0.1) (2.8.1)
Requirement already satisfied: pytz in /home/lem/.local/lib/python3.8/site-packages (from BigBang==0.1) (2020.1)
Requirement already satisfied: pyyaml in /usr/lib/python3/dist-packages (from BigBang==0.1) (5.3.1)
Requirement already satisfied: pyzmq in /home/lem/.local/lib/python3.8/site-packages (from BigBang==0.1) (19.0.1)
Requirement already satisfied: requests in /usr/lib/python3/dist-packages (from BigBang==0.1) (2.23.0)
Requirement already satisfied: tornado in /home/lem/.local/lib/python3.8/site-packages (from BigBang==0.1) (6.0.4)
Requirement already satisfied: traitlets>=4.2 in /home/lem/.local/lib/python3.8/site-packages (from ipython->BigBang==0.1) (4.3.3)
Requirement already satisfied: pexpect; sys_platform != "win32" in /usr/lib/python3/dist-packages (from ipython->BigBang==0.1) (4.6.0)
Requirement already satisfied: decorator in /home/lem/.local/lib/python3.8/site-packages (from ipython->BigBang==0.1) (4.4.2)
Requirement already satisfied: setuptools>=18.5 in /usr/lib/python3/dist-packages (from ipython->BigBang==0.1) (46.1.3)
Requirement already satisfied: prompt-toolkit!=3.0.0,!=3.0.1,<3.1.0,>=2.0.0 in /home/lem/.local/lib/python3.8/site-packages (from ipython->BigBang==0.1) (3.0.5)
Requirement already satisfied: backcall in /home/lem/.local/lib/python3.8/site-packages (from ipython->BigBang==0.1) (0.1.0)
Requirement already satisfied: pygments in /usr/lib/python3/dist-packages (from ipython->BigBang==0.1) (2.3.1)
Requirement already satisfied: pickleshare in /home/lem/.local/lib/python3.8/site-packages (from ipython->BigBang==0.1) (0.7.5)
Requirement already satisfied: jedi>=0.10 in /home/lem/.local/lib/python3.8/site-packages (from ipython->BigBang==0.1) (0.17.0)
Requirement already satisfied: pyrsistent>=0.14.0 in /home/lem/.local/lib/python3.8/site-packages (from jsonschema->BigBang==0.1) (0.16.0)
Requirement already satisfied: six>=1.11.0 in /usr/lib/python3/dist-packages (from jsonschema->BigBang==0.1) (1.14.0)
Requirement already satisfied: attrs>=17.4.0 in /home/lem/.local/lib/python3.8/site-packages (from jsonschema->BigBang==0.1) (19.3.0)
Requirement already satisfied: cycler>=0.10 in /home/lem/.local/lib/python3.8/site-packages (from matplotlib->BigBang==0.1) (0.10.0)
Requirement already satisfied: pyparsing!=2.0.4,!=2.1.2,!=2.1.6,>=2.0.1 in /usr/lib/python3/dist-packages (from matplotlib->BigBang==0.1) (2.4.7)
Requirement already satisfied: kiwisolver>=1.0.1 in /home/lem/.local/lib/python3.8/site-packages (from matplotlib->BigBang==0.1) (1.2.0)
Requirement already satisfied: mpmath in /home/lem/.local/lib/python3.8/site-packages (from powerlaw->BigBang==0.1) (1.1.0)
Requirement already satisfied: scipy in /home/lem/.local/lib/python3.8/site-packages (from powerlaw->BigBang==0.1) (1.4.1)
Requirement already satisfied: more-itertools>=4.0.0 in /home/lem/.local/lib/python3.8/site-packages (from pytest->BigBang==0.1) (8.3.0)
Requirement already satisfied: pluggy<1.0,>=0.12 in /home/lem/.local/lib/python3.8/site-packages (from pytest->BigBang==0.1) (0.13.1)
Requirement already satisfied: py>=1.5.0 in /home/lem/.local/lib/python3.8/site-packages (from pytest->BigBang==0.1) (1.8.1)
Requirement already satisfied: wcwidth in /home/lem/.local/lib/python3.8/site-packages (from pytest->BigBang==0.1) (0.1.9)
Requirement already satisfied: packaging in /home/lem/.local/lib/python3.8/site-packages (from pytest->BigBang==0.1) (20.4)
Requirement already satisfied: ipython-genutils in /home/lem/.local/lib/python3.8/site-packages (from traitlets>=4.2->ipython->BigBang==0.1) (0.2.0)
Requirement already satisfied: parso>=0.7.0 in /home/lem/.local/lib/python3.8/site-packages (from jedi>=0.10->ipython->BigBang==0.1) (0.7.0)
Installing collected packages: BigBang
  Running setup.py develop for BigBang
Successfully installed BigBang
➜  bigbang git:(master) source activate bigbang
source: no such file or directory: activate
➜  bigbang git:(master) source ~/Data/anaconda3/bin/activate bigbang
(bigbang) ➜  bigbang git:(master) python bin/collect_mail.py -f examples/url_collections/mm.ietf.org.txt
Traceback (most recent call last):
  File "bin/collect_mail.py", line 3, in <module>
    import bigbang.mailman as mailman
ImportError: No module named bigbang.mailman

The log from the conda example makes it look like the environment isn't getting activated for the install steps:

conda-setup.sh: line 1: conda: command not found
conda-setup.sh: line 2: activate: No such file or directory

I think the conda environment needs to be activated before the rest of the install steps are run, and then collect_mail.py needs to be executed from that same environment. So either we could note in the documentation that you should activate the conda environment before you run the bash script, or we should try to debug why the script on your machine failed to activate the environment before running the other steps.

On 5/25/20 9:29 PM, Nick Doty wrote:
So either we could note in the documentation that you should activate the conda environment before you run the bash script,
Sounds like the way to go! Thanks for catching that! Will make PR tomorrow.
--
Twitter         :   @nielstenoever
PGP fingerprint :   8D9F C567 BEE4 A431 56C4
678B 08B5 A0F2 636D 68E9

@nllz do you want to open a PR with clearer documentation on this?


Tons of celery.chord_unlock tasks repeating in logs. Is this okay?

Need to look into whether this might be slowing things down.

Not concerned about this anymore with new celery patterns.


Example code is wrong

Wrong data

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

ID: e3b91464-040d-48a2-28fc-300a16cce125
Version Independent ID: e3b91464-040d-48a2-28fc-300a16cce125
Content: Block Documentation - minecraft:queued_ticking
Content Source: creator/Reference/Content/BlockReference/Examples/BlockTriggers/minecraftBlock_queued_ticking.md
Product: gaming
GitHub Login: @mammerla
Microsoft Alias: v-jillheaden

Fixed - thank you!


Fix for #3688

Looking for review of this. I do not have the appropriate hardware to test properly.

User from G+ confirm this fixes the issue.


Support CUE_STATS_FILE with the SDK

Is your feature request related to a problem? Please describe.
CUE_STATS_FILE can be set be end users of the CLI to get helpful info about how their code runs in the evaluator. Users of the SDK cannot make use of this (accurately) because some of the stats API requires access to internal packages
https://github.com/cue-lang/cue/blob/901604a413b7a00bdd25d00049c46bfc9ebd8385/cmd/cue/cmd/root.go#L118
Describe the solution you'd like
CUE_STATS_FILE to work via the SDK
Describe alternatives you've considered
It doesn't seem possible to access stats directly because much of it requires access to the adt package
Additional context
hof user asked why this doesn't work with hof

I've brought up the same to Marcel in the past, this would indeed be nice to have. We just have to be careful to clearly document that the structure of the stats is unstable and may change with future CUE versions. We could make the struct fully opaque to hide the fields from the user entirely, or use a map[string]any, although that also makes using the stats directly in Go rather annoying. I'd be fine with exposing a plain struct with exported fields as long as the documentation is clear.


Limit self-upgrade to cert-manager org

Fixes cert-manager/cert-manager#7183
See https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs

/approve
/lgtm


Specify packaging version

https://github.com/nexB/pip-requirements-parser/issues/10

@wellshs Thanks.... I think we need a bit more than this. In particular we would need to either:

update the setup.cfg to put a temporary cap on the packaging version
alternatively vendoring packaging would be best short term

Your proposed requirements.update only work if using a checkout and running configure, and will not fix a pip install pip-audit

I am closing in this in favor of https://github.com/nexB/pip-requirements-parser/pull/3
Thank you ++ for reporting the issue and helping fixing this.

Oh, thanks for kind explanation and fixing this issue!
I will check out patch work to me!


Inconsistent handling of error events by wildcard observers

When there is no 'error' event listener, wildcard event listeners do not observe 'error' events and the process is killed, e.g.
var EventEmitter2 = require('eventemitter2').EventEmitter2;

var emitter = new EventEmitter2({
  wildcard: true
, delimiter: ':'
, newListener: false
});

emitter.on('*', function () {
  console.log('not reached');
});

emitter.emit('error', new Error());
console.log('not reached');

This script will not reach either of the console.log statements because the unhandled 'error' event causes the program to exit.
On the other hand, when there is an 'error' event handler, the wildcard observer also observes the 'error' event, e.g
var EventEmitter2 = require('eventemitter2').EventEmitter2;

var emitter = new EventEmitter2({
  wildcard: true
, delimiter: ':'
, newListener: false
});

emitter.on('*', function () {
  console.log('wildcard handler called');
});

emitter.on('error', function () {
  console.log('error handler called');
});

emitter.emit('error', new Error());
console.log('reached');

In this script, both both the 'error' handler and the '*' handler observe the error event, and all console.log statements are reached.
It would be much more consistent to either:

Explicitly specify that a wildcard observer will handle error events (and thus not cause the program to exit).

Explicitly specify that the special nature of error events means that they will not ever be handled by wildcard observers.

My opinion is that error events should never be handled by wildcard listeners. Errors are already special (in that they throw if there's no handler), and they should remain special.

Personally I don't think that wildcards should handle error events. Mostly because error events have the side effect of crashing node if they're uncaught, which I think should require explicit listening. In my opinion it would be unexpected for wildcard listeners preventing that behavior.


Add SearchApi search and Google Serper plugin

Describe what this PR does / why we need it
Add SearchApi search and Google Serper plugin
Does this pull request fix one issue?

Describe how you did it
Describe how to verify it
Special notes for reviews

@superhandsomeg please refer the pr #191 to fix similar probs.


fix: typo in setup.py

Codecov Report

Merging #103 (ff457d9) into main (55bdb8d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #103   +/-   ##
=======================================
  Coverage   96.58%   96.58%
=======================================
  Files           9        9
  Lines         527      527
=======================================
  Hits          509      509
  Misses         18       18

Flag
Coverage Δ

unittests
96.58% <ø> (ø)

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

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 55bdb8d...ff457d9. Read the comment docs.


Update frontend nextJS to 13.4.7

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Work merged in as:
https://github.com/euanwm/OpenWeightlifting/pull/200


Fix meeting page tiles

Closes #64

/preview

/preview

:tada: This PR is included in version 1.2.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Fix log level for embeddings generation

Some weeks ago, we wanted to see progress... We used the log for that. Now, it works great using background tasks.
The log messages should not be there

Should I change them to debug level?

Should I change them to debug level?

Yes.


⚠ Bofrost.be has degraded performance

In 97b39e9, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1992 ms

Resolved: Bofrost.be performance has improved in 8d3de40 after 46 minutes.


Tap on cell containing "Add / Hide Tokens" in Wallet tab shouldn't select the 0th token

This is because the didSelect function doesn't check for the section number.

Maybe it should also just perform "Add / Hide Tokens"? Bigger touch area is good.


0.73.1 iOS build failed on Apple Silicon Mac(M1 Pro), but I can do build on 0.72.4 version of React Native

Old Version
0.72.4
New Version
0.73.1
Description
I'm trying to upgrade to latest version and getting
Generating Pods project
Setting USE_HERMES build settings
Setting REACT_NATIVE build settings
[!] An error occurred while processing the post-install hook of the Podfile.

[!] The plist file at path `/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/ios/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/ios/kepit-development-Info.plist` doesn't exist.

/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/vendor/bundle/ruby/3.2.0/gems/xcodeproj-1.22.0/lib/xcodeproj/plist.rb:17:in `read_from_path'
/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/node_modules/react-native/scripts/cocoapods/utils.rb:553:in `block in update_ats_in_plist'
/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/node_modules/react-native/scripts/cocoapods/utils.rb:551:in `each'
/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/node_modules/react-native/scripts/cocoapods/utils.rb:551:in `update_ats_in_plist'
/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/node_modules/react-native/scripts/cocoapods/utils.rb:575:in `apply_ats_config'
/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/node_modules/react-native/scripts/react_native_pods.rb:310:in `react_native_post_install'
/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/ios/Podfile:99:in `block (3 levels) in from_ruby'
/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/vendor/bundle/ruby/3.2.0/gems/cocoapods-core-1.12.1/lib/cocoapods-core/podfile.rb:196:in `post_install!'
/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/vendor/bundle/ruby/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/installer.rb:1013:in `run_podfile_post_install_hook'
/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/vendor/bundle/ruby/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/installer.rb:1001:in `block in run_podfile_post_install_hooks'
/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/vendor/bundle/ruby/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/user_interface.rb:149:in `message'
/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/vendor/bundle/ruby/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/installer.rb:1000:in `run_podfile_post_install_hooks'
/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/vendor/bundle/ruby/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/installer.rb:337:in `block (2 levels) in create_and_save_projects'
/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/vendor/bundle/ruby/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/installer/xcode/pods_project_generator/pods_project_writer.rb:61:in `write!'
/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/vendor/bundle/ruby/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/installer.rb:336:in `block in create_and_save_projects'
/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/vendor/bundle/ruby/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/user_interface.rb:64:in `section'
/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/vendor/bundle/ruby/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/installer.rb:315:in `create_and_save_projects'
/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/vendor/bundle/ruby/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/installer.rb:307:in `generate_pods_project'
/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/vendor/bundle/ruby/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/installer.rb:183:in `integrate'
/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/vendor/bundle/ruby/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/installer.rb:170:in `install!'
/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/vendor/bundle/ruby/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/command/install.rb:52:in `run'
/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/vendor/bundle/ruby/3.2.0/gems/claide-1.1.0/lib/claide/command.rb:334:in `run'
/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/vendor/bundle/ruby/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/command.rb:52:in `run'
/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/vendor/bundle/ruby/3.2.0/gems/cocoapods-1.12.1/bin/pod:55:in `<top (required)>'
/Users/harbolaez/.rvm/gems/ruby-3.2.1/bin/pod:25:in `load'
/Users/harbolaez/.rvm/gems/ruby-3.2.1/bin/pod:25:in `<main>'
/Users/harbolaez/.rvm/gems/ruby-3.2.1/bin/ruby_executable_hooks:22:in `eval'
/Users/harbolaez/.rvm/gems/ruby-3.2.1/bin/ruby_executable_hooks:22:in `<main>'

I'm not sure why is doing /Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/ios/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/ios/kepit-development-Info.plist
Steps to reproduce
I have deleted ndoe_modules, yarn.lock, Podfile.lock. and ran pod deintegrate; pod update; pod install
Affected Platforms
Runtime - iOS
Output of npx react-native info
System:
  OS: macOS 13.4.1
  CPU: (10) arm64 Apple M1 Pro
  Memory: 635.14 MB / 32.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.9.0
    path: ~/.nvm/versions/node/v20.9.0/bin/node
  Yarn:
    version: 1.22.21
    path: ~/.nvm/versions/node/v20.9.0/bin/yarn
  npm:
    version: 10.1.0
    path: ~/.nvm/versions/node/v20.9.0/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.12.1
    path: /Users/harbolaez/.rvm/gems/ruby-3.2.1/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 22.4
      - iOS 16.4
      - macOS 13.3
      - tvOS 16.4
      - watchOS 9.4
  Android SDK: Not Found
IDEs:
  Android Studio: 2022.3 AI-223.8836.35.2231.11090377
  Xcode:
    version: 14.3.1/14E300c
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 19.0.2
    path: /usr/bin/javac
  Ruby:
    version: 3.2.1
    path: /Users/harbolaez/.rvm/rubies/ruby-3.2.1/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react: Not Found
  react-native: Not Found
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found

### Stacktrace or Logs

```text
NA

Reproducer
na
Screenshots and Videos
No response

[!] The plist file at path /Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/ios/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/ios/kepit-development-Info.plist doesn't exist.

The error message is clear, your build is trying to access a file that doens't exist.
We can't help without a reproducer (or by looking at your code)

I have the same error on CD, using Firebase.
After the pod install, getting the error :
Setting REACT_NATIVE build settings
[!] An error occurred while processing the post-install hook of the Podfile.

[!] The plist file at path `/Users/runner/work/mobile-news/mobile-news/ios/mobileNews/GoogleService-Info.plist` doesn't exist.

The error is located in the post_install function of the podfile, when executing the update_ats_in_plist: it looks for any file terminating by Info.plist to modify their NSAllowsArbitraryLoads, NSAppTransportSecurity... properly.
But I have 3 customs GoogleService-Info.plist for my 3 environnements :

The matching is made in the build phase - here an extract of my pbxproj:
		93E6EB9EE4D3433C96007083 /* Set environment GoogleService-Info.plist */ = {
			isa = PBXShellScriptBuildPhase;
			buildActionMask =<PHONE_NUMBER>;
			files = (
			);
			inputFileListPaths = (
			);
			inputPaths = (
			);
			name = "Set environment GoogleService-Info.plist";
			outputFileListPaths = (
			);
			outputPaths = (
				"$(PROJECT_DIR)/$(PROJECT_NAME)/GoogleService-Info.plist",
			);
			runOnlyForDeploymentPostprocessing = 0;
			shellPath = /bin/sh;
			shellScript = "cp ${PROJECT_NAME}/GoogleService-Info.${ENV}.plist ${PROJECT_NAME}/GoogleService-Info.plist\n";
		};

So in the post_install function, the GoogleService-Info.plist does not yet exists and the Xcodeproj::Plist.read_from_path(fullPlistPath) fails.
@harbolaez I guess it's the same for you, as you have a kepit-development-Info.plist -> a plist for your development env, matched later to its real value.
@jayscottthomas changing for the initial path without the parent does not fix in our case.
Different ideas for the fix:

check if the file exists before trying to modify it :

# node_modules/react-native/scripts/cocoapods/utils.rb:550
def self.update_ats_in_plist(plistPaths, parent)
        plistPaths.each do |plistPath|
            fullPlistPath = File.join(parent, plistPath.path)
            if File.exist?(fullPlistPath) # ✅ Add me here!
                plist = Xcodeproj::Plist.read_from_path(fullPlistPath)
                ats_configs = {
                    "NSAllowsArbitraryLoads" => false,
                    "NSAllowsLocalNetworking" => true,
                }
                if plist.nil?
                    plist = {
                        "NSAppTransportSecurity" => ats_configs
                    }
                else
                    plist["NSAppTransportSecurity"] ||= {}
                    plist["NSAppTransportSecurity"] = plist["NSAppTransportSecurity"].merge(ats_configs)
                end
                Xcodeproj::Plist.write_to_path(plist, fullPlistPath)
            else # ℹ Also add a log here
                Pod::UI.puts "Ignore #{plistPath} in post-install->update_ats_in_plist".red
            end
        end
    end

But then the customed plist would not be modified. But I don't know if it really needs to have the modification, it's not the main Info.plist of the app!
Or we could generate the final plist (without the env) in the pre-install hook ? Instead of doing it in a build phase

@philIip as you are the author of the initial PR https://github.com/facebook/react-native/pull/38086, do you have any insight on it?

I don't think not modifying the GoogleService-Info.plist will be a problem on second thoughts ; it's literally what was happening when I deployed locally - post_install modified the gitignored GoogleService-Info.plist copied in a previous build, then on the build phase it was erased and replaced by the unmodified GoogleService-Info.production.plist.
So here's the patch - may open a PR with it:
react-native+0.73.2.patch

We are experiencing the same error as OP and @delphinebugner's patch worked flawlessly, thanks!
In my case, and as I see in the OP's post, it's computing the wrong path for one of my target's info plist. As you see in OPs, it's concatenating the ios folder path twice:

[!] The plist file at path `/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/ios/Users/harbolaez/Desktop/code/personal/kepit-apps/kepit/ios/kepit-development-Info.plist

Hi, I had same problem. To solve this, I did some changes in one ruby file. In //node_modules/react-native/scripts/cocoapods/utils.rb line 553, change the line plist = Xcodeproj::Plist.read_from_path(fullPlistPath) with plist = Xcodeproj::Plist.read_from_path(plistPath.path)
and go to line 566, change the line Xcodeproj::Plist.write_to_path(plist, fullPlistPath) with Xcodeproj::Plist.write_to_path(plist, plistPath.path)

this solution is working fine. When you create a new scheme and try to make the pod install this issue occurs for me

Note: after bumping to react-native 0.73.6, patch is no longer need 🎉  issue fixed!


Graceful error handling of mv-param "cpu-pin": "numa" when PCIe has no numa

This happened on Bill M's AMD machine when BIOS setting to 1 NUMA.  W/o this error check, the cpu_list is ":-1" leading to later failure at "taskset --cpu_list :-1"

Please re-open as a branch on the upstream repo and with rebasing it from the base branch.


Log peer's userId, clientId and instanceId in send and receive trace

Log peer's userId, clientId and instanceId in send and receive trace.

Done in https://github.com/uProxy/uproxy/pull/1012


PDF Tron - Remove 'Redact all' button

Title of ticket:
Description
Discovered during demo that you can click redact all, and it will apply redactions to pages while in the reviewer, and it is not reversible.
Note: are there any other pathways to analysts triggering the 'redact all' feature?
See ticket #3488 (closed) - Kyle's comment has an observation that shows another way a page can be irreversibly redacted
Dependencies
Are there any dependencies?
DOD

[ ] Remove Redact All Button
[ ] Remove other pathways in app to redact all
[ ]
[ ]
[ ]

5/12/2023 standup - redact button in full page redaction modal is disabled through pdftron config, but redact all button in right panel is disabled with a workaround (directly changing pdftron files) If pdftron version is upgraded, need to apply fix again. need to decide as a team how often we are upgrading and/or if we need to make a feature request to pdftron to make that button officially configurable

NOTE: another way to apply permanent redaction in redaction app - the 'Apply' checkmark icon/feature in toolbar - this is available when clicking on a redaction box/highlight.

Confirmed permanent redact functions in redaction app (three total, included out of box) have been removed. These will be replaced by the ability to create layers/packages which apply redactions.


wsen-itds:  Add support for wsen-itds Accel Sensor

Add support for wsen-itds 3-axis accel sensor, provides the acceleration,
die-temperature data reading. Driver support added to access over I2C and sample application to demonstrate.

ping for review

@MaureenHelm @galak @nashif ping for review

@gmarull @MaureenHelm @carlescufi
Ping for review/merge

@ssekar15 thank you! Will you please rebase and fix the merge conflict?

@MaureenHelm  done

Thanks @ssekar15, good job!


style edit button

Description
stylized the button edit for page "my profile". due to button looking too generic i decided to change it a bit and make it more interesting.
Video Link
https://www.loom.com/share/deaff77dd82d430fa36b89feb248a8cc
Type of change

[x] New feature (style change)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have removed unnecessary comments/console logs from my code
[x] My changes generate no new warnings
[x] I have checked my code and corrected any misspellings
[x] No duplicate code left within changed files
[x] Size of pull request kept to a minimum
[x] Pull request description clearly describes changes made & motivations for said changes

@arsalan2243 I would highly recommend taking a look at @BrittniKarat's comment above here - we want to keep things consistent! If you can make adjustments for this, this PR would likely be good to merge up.


Download: Add a stage to import all channels

After the APPLYING_EXTERNAL_TAGS stage, the DownloadManager will enter a new IMPORTING_EXTRA_CHANNELS stage. In this stage, it should download metadata for any channels which are listed in another content collection.
Issue #548

The parent issue here wants this stage to happen in the background, and I took a look at that in #579. But I think there's some overlap with #568, so I'm opting for something quick and dirty in this pull request and we can deal with downloading channel metadata in the background separately.

I made a small change here based on our talk earlier, so the progress bar updates correctly as additional channels are downloaded (and that part of the operation is between 90% and 100%). It could do with another quick look to be sure it's still all right :)

Available in Ladybird 6.8-338


set AWS_SHARED_CREDENTIALS_FILE for eks in kubeconfig ENV var

Describe the solution you'd like:
in case of EKS, set AWS_SHARED_CREDENTIALS_FILE env var in kubeconfig along with AWS_PROFILE in env var
Why do you want this feature:
In case user wants to store AWS creds to any other location, then kubectl (with aws-iam-authenticator) will fail authentication because without AWS_SHARED_CREDENTIALS_FILE in kubeconfig env var, it will search at default location.
Anything else you would like to add:
This will also help when there is many user sessions on same machine or Docker container.

@seankelly001 Which kconnect version will it be part of?

@seankelly001 Which kconnect version will it be part of?

It will be part of 0.5.6, which will be released in a few weeks time


Signal arg and Callback function param type missmatch nulls value without error

Godot version:

3.1
Issue description:

emit_signal("hey", my_dictionary)

func _on_hey(my_value: Directory) -> void: # Wrong type
    print(my_value)

>null

No error. No warning. Value simply becomes null and the code keeps running.
This should probably be caught as it can be difficult to notice.

This would probably require types in signal definitions, which is already planned.
Also related (if not duplicate) to #24013

Actually this was another issue which was fixed by #37318


refactor: migrate to app platform [TECH-339]

Implements https://jira.dhis2.org/browse/TECH-339

Redoing in another branch


installation-device.nix: explain sshd usage, don't include clone-config

Motivation for this change
The configuration used to build an installation medium isn't really
suitable to be (re)used when building a real system.
For example, it enables automatic root login without a password on the
console, installs sshd, but prevents it from starting on boot.
This can be very misleading when users try to derive their real system
from it - they should use nixos-generate-config instead, as described in
the manual.
Also update the mingetty helpLine to describe the sshd setup.
Closes #63576
Closes #26776
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg test installer

@GrahamcOfBorg eval
??!?

Oh, missed the profiles documentation because I don't think I noticed when this was added.

@samueldr, could you give this a try once sd_image builds again?

Probably immediately easy enough to revert https://github.com/NixOS/nixpkgs/pull/63835 for the image

Rebased on top of master, as https://github.com/NixOS/nixpkgs/pull/66850 landed.


test: use snapshot matchers

Using Jests snapshot matchers make it easier to maintain since you get richer diffs and an easy way to regenerate snapshots when making changes.
The only downside is that a version of Prettier v2 needs to be installed as currently v3 is not supported due to not providing an async API - this should be resolved in future.

@G-Rath happt to merge this once the conflict is resolved!

@marcolink friendly ping - would appreciate getting some of my PRs landed :)

@marcolink friendly bump about these PRs - I'm keen to get these landed and continue on with #302; do let me know if there's anything I can do to make it easier - I've done dedicated PRs for each change since they're technically unrelated, but I'm happy to merge them into a single PR if that'd be easier for you.

@marcolink @veu I've closed my PRs since they've stalled, but let me know if you get the bandwidth to review them sometime in the future and I can reopen + rebase.
I'm still keen to see #292 be supported :)


Automated Prometheus version update 0.63.0-45.8.1

Automated changes by the cron-prometheus-update GitHub action
Adds [Prometheus add-on](https://kurl.sh/docs/add-ons/prometheus) version 0.63.0-45.8.1.

Passing in all tests.


Proper documentation required ...

Spring petclinic previously had a really good documentation for beginners like me, but it`s outdated now. I have no idea on how it is working ... as it does not have proper documentation. Presentation attached is also very old one.
WITHOUT PROPER DOCUMENTATION(README) ITS NOT VERY DEVELOPER AND BEGINNER FRIENDLY.
This documentation must have all howtos and how is it working in boot app...
Following can be some pointers....

Testing(Types of testing done)
Profiles
Internationalization
Validation
Explaining package structure.
SQL scripts
Caching
Templates
Application Configuration
JMX

I think documentation must also have a section of what is the difference between legacy spring app and this one:
Following can be noted differences:

Previously, app followed 3 layer architecture, which is now outdated.(Why I don't know)
Current package structure is also very VERY different, previously all entities were stored in org.springframework.samples.petclinic.model.
Now, all settings are stored in application-* properties.
Where did many things go.... it seems magic....
and so on....

Please make sure the documentation is very detailed like this. but with much more details.

I am having the same issues.  Looking at the slide deck labelled "Data Access" it says "...inside web.xml...".  There is no web.xml, so am at a loss for what is happening here.
I find this a great example and would love to be able to use it to better understand Spring MVC, ... .
Thx.

@dsyer started to rework the outdated documentation in the gh-pages branch. The result is published by GitHub at http://projects.spring.io/spring-petclinic/. It should replaced the old doc
The main documentation (markdown syntax) remains into the index.html file.
Anybody interested to refresh it could ask Dave.

Ok, a quick glance seems like it is more complete.  Will take a look at this.  Does "gh" stand for anything I should know?  Thanks.

gh is just an acronym for GitHub pages

Nope, still can't find anything which is up-to-date.

I think the README is adequate for most purposes, especially in combination with the many Spring Boot guides and tutorials that are out there. Closing as "won't fix".


Bug: Status center shows TB/s instead of MB/s on speed

Description
Copying files sometimes show transfer rates as TB/s instead of MB/s... I freaked out the first time when I saw 390 TB/s transfer rates...

Steps To Reproduce
Right after I updated to this release. When I was copying files.
I was trying to duplicate a file, then I saw this.
Requirements
Show the correct measurements
Files Version
<IP_ADDRESS>
Windows Version
10.0.22635.2700
Log File
debug.log

Thanks for the report, I've added this to the project board.

Looks like a bug in the file size. How large was this file?

Unfortunately I could not reproduce the bug. I tried copying a 3.5GB file a few times and it always showed speed in MB/S. Are there any other details about the issue?

@maxxsteal does the issue persist in the latest Files version?

@maxxsteal

This happened again when I was trying to copy a file from a portable device to a local drive in Files <IP_ADDRESS>

Is it only from portable drives or can you also repro this on fixed drives?

On a related note, @Qin-shihuang I noticed you've been pretty active here and I wanted to take a moment to thank you for your participation in the community.

Is it only from portable drives or can you also repro this on fixed drives?

Only from portable drive.

mine is doing the something except instead of TB its PB


collapsible sections on component docs pages?

Inspired by this comment
As we add more examples to component pages on the docs site, it's possible users will feel overwhelmed with the amount of information presented at once.
It'd be great to ensure we don't overwhelm users, without scaling back the number of examples we provide for components.
One possible way to address this would be to add collapsible sections to the docs pages, so examples could be shown/hidden.
I'm sure there are other solutions to consider as well (hence marking this issue as "discovery")

Related, there has been some design discovery in the past to redesign the component pages on the documentation site: Figma.
For example, it splits out content into different tabs for "Design guidelines" vs. "Implementation" (but it could also have "Accessibility", etc.). That said, even then, the "Implementation" tab alone could be quite large given what we have today.

Design guidelines and Implementation tabs would definitely go a long way!
One thing to consider is what we want to have above the fold on the implementation tab.
If the tabs go where they are in Figma at the moment

above the fold would stay the same between guidelines and implementation.
Another idea would be to split off the implementation examples into separate files. Possibly use cards to show/link to all the different examples that exist.
I'm just kind of throwing ideas around, I'm excited to see what design comes up with!


SQL script consolidation

This is a late-breaking request, I know, but I think we'll want a mothership schema change for https://www.labkey.org/home/Developer/issues/issues-details.view?issueId=38803
If we can hold on that module it would be great, otherwise I'll deal with it as a 19.31 update.

Ian will back out the mothership version bump. We're assuming we'll deal with the new script and version bump on the 19.3 branch.

@labkey-adam yes, exactly. Thank you both


Python.DataScience keyboard shortcuts disappeared

Environment data

VS Code version: 1.51.1
Extension version (available under the Extensions sidebar): 2020.11.371526539
Jupyter Extension version (available under the Extensions sidebar): v2020.11.372831992
OS (Windows | Mac | Linux distro) and version: Mac Pro, mac Catalina 10.15.7
Python and/or Anaconda version: 3.8.5
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): Conda virtual environment
Jupyter server running: Local

Expected behaviour
The full set of data science shortcuts should be visible. However, they disappeared a few days ago.
Actual behaviour
Only the keyboard shortcuts gotoNextCell, gotoPrevCell, notebookedit and restartkernel are available when I searh for python.data in the keyboard shortcuts. Which actually are the only 4 keyboard shortcuts that i manually changed. How can i retrieve the full list of keyboard shortcuts for data science again?

All keyboard shortcuts have been migrated to jupyter.
We have moved the data science functionally from the option extension into a separate extension named Jupyter.

Closing for now as I believe that addresses your question.
I'm sorry three new extension didn't automatically migrate your keyboard shortcuts. We plan on fixing that in the next release , hopefully find time today.


Dart IO delete method does not delete file from internal storage.

Steps to reproduce

On your emulator or physical device, make sure to atleast have 1 image in your gallery.
Import the code sample.
Run flutter pub get.
Run the code sample that is provided in this issue.
Select an image from your gallery using the 'Select Image' button.
Delete the image using the 'Delete Image' button.

Expected results
What I expect to happen is that:
a) The image gets deleted from the gallery (and thereby also from the phone).
Actual results
What is actually happening:
The image will get removed from the UI, but when pressing the 'Select Image' button again, the earlier deleted picture is still present in storage.
Code sample
Code sample
import 'dart:developer';
import 'dart:io';

import 'package:flutter/material.dart';
import 'package:image_picker/image_picker.dart';

void main() {
  runApp(const MainApp());
}

class MainApp extends StatefulWidget {
  const MainApp({super.key});

  @override
  State<MainApp> createState() => _MainAppState();
}

class _MainAppState extends State<MainApp> {
  XFile? selectedImage;

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: SafeArea(
          child: Center(
            child: Column(
              children: [
                FilledButton(
                  onPressed: selectedImage != null
                      ? () async {
                          try {
                            File file = File(selectedImage!.path);
                            if (!file.existsSync()) {
                              return;
                            }

                            await file.delete();

                            setState(() {
                              selectedImage = null;
                            });

                            log('Image deleted');
                          } on Exception catch (e) {
                            log('Error with deleting the image', error: e);
                          }
                        }
                      : null,
                  style: FilledButton.styleFrom(
                    backgroundColor: Colors.red,
                  ),
                  child: const Text('Delete image'),
                ),
                FilledButton.icon(
                  onPressed: () async {
                    ImagePicker picker = ImagePicker();
                    XFile? image =
                        await picker.pickImage(source: ImageSource.gallery);

                    if (image == null) {
                      return;
                    }

                    setState(() {
                      selectedImage = image;
                    });
                  },
                  icon: const Icon(Icons.download),
                  label: const Text('Select image'),
                ),
                if (selectedImage != null)
                  Image.file(
                    File(selectedImage!.path),
                    fit: BoxFit.cover,
                  ),
              ],
            ),
          ),
        ),
      ),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration

Logs
Logs (Debug Console)
Launching lib\main.dart on sdk gphone64 x86 64 in debug mode...
√ Built build\app\outputs\flutter-apk\app-debug.apk
I/mple.delete_bug( 7054): Compiler allocated 4355KB to compile void android.view.ViewRootImpl.performTraversals()
Connecting to VM Service at ws://<IP_ADDRESS>:61204/2uG8TCFhyR0=/ws
D/ProfileInstaller( 7054): Installing profile for com.example.delete_bug
D/EGL_emulation( 7054): app_time_stats: avg=1161.08ms min=10.10ms max=2312.07ms count=2
D/CompatibilityChangeReporter( 7054): Compat change id reported: 78294732; UID 10174; state: ENABLED
E/OpenGLRenderer( 7054): Unable to match the desired swap behavior.
D/EGL_emulation( 7054): app_time_stats: avg=732.27ms min=24.88ms max=3203.82ms count=5
[log] Image deleted
D/EGL_emulation( 7054): app_time_stats: avg=133.10ms min=7.02ms max=2200.22ms count=21

Flutter Doctor output
Doctor output
[√] Flutter (Channel stable, 3.22.3, on Microsoft Windows [Version 10.0.26100.2605], locale nl-NL)
    • Flutter version 3.22.3 on channel stable at D:\Flutter\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision b0850beeb2 (6 months ago), 2024-07-16 21:43:41 -0700
    • Engine revision 235db911ba
    • Dart version 3.4.4
    • DevTools version 2.34.3

[√] Windows Version (Installed version of Windows is version 10 or higher)

[√] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at D:\Android\Sdk
    • Platform android-Baklava, build-tools 34.0.0
    • Java binary at: D:\Program Files\Android\Android Studio\jbr\bin\java
    • Java version OpenJDK Runtime Environment (build 17.0.11+0--11852314)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[!] Visual Studio - develop Windows apps (Visual Studio Enterprise 2022 17.12.1)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Enterprise
    • Visual Studio Enterprise 2022 version 17.12.35514.174
    X Visual Studio is missing necessary components. Please re-run the Visual Studio installer for the "Desktop development with C++" workload, and
      include these components:
        MSVC v142 - VS 2019 C++ x64/x86 build tools
         - If there are multiple build tool versions available, install the latest
        C++ CMake tools for Windows
        Windows 10 SDK

[√] Android Studio (version 2024.2)
    • Android Studio at D:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.11+0--11852314)

[√] VS Code (version 1.96.2)
    • VS Code at C:\Users\bj\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.102.0

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.26100.2605]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 114.0.5735.134
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 127.0.2651.74

[√] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

image_picker on Android returns an app-storage-local copy of the image (due to the inability to return a content URI as a file), so what you are deleting in the provided code is that copy. Closing as a duplicate of https://github.com/flutter/flutter/issues/88557 since that tracks the fact that a copy is returned.


ZEPPELIN-506 Expand "create notebook" of REST API to have initial paragraphs

What is this PR for?
To provide initial paragraphs when creating new notebook via REST API
What type of PR is it?
Improvement
Todos

[ ] -

Is there a relevant Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-506
How should this be tested?

Request http://<zeppelin host>:<zeppelin port>/api/notebook with POST method including JSON payload,

{
    "name": "Test for initial paragraphs2",
    "paragraphs": [
        {
            "text": "%spark\nvar hello: Int=1"
        },
        {
            "text": "%spark\nhello = hello + 1"
        },
        {
            "text": "%spark\nimport java.util.Date\n\nprintln(hello + \", current time is <\" + new Date + \">\")"
        }
    ]
}

Check notebook is made with initial paragraphs via UI or REST API or Web socket.

Screenshots (if appropriate)
Questions:

Does the licenses files need update? (No)
Is there breaking changes for older versions? (No, added parameter is optional.)
Does this needs documentation? (Yes, I've updated related doc.)

@Leemoonsoo Addressed your comment.

@HeartSaVioR Thank you for very useful improvement.
Looks good to me

Tested looks good to me :+1:

Merge if there're no more discussions

@Leemoonsoo Thanks for merging!


lib/methods.js sending unnecessary code to the client

The following code in lib/methods.js doesn't need to be sent to the client:
if (Meteor.isServer) {
    Meteor.methods({
        ATCreateUserServer: function(options){

Most of that file is server only code.

That's a good point!
we could save a few bytes but that's still an improovement...

Methods are now separated into two different files.
Thanks for the pointer!


port news posts

Added news, quick and dirty f534c99a9b3d0d7144c6fdb8de09a5c230817dd2.

Looks good! I will give it a tiny CSS polishing.

Be my guest!
/Joel
Sent from TypeApp
On Mar 6, 2017, 16:46, at 16:46, Radovan Bast<EMAIL_ADDRESS>wrote:

Looks good! I will give it a tiny CSS polishing.
--
You are receiving this because you were assigned.
Reply to this email directly or view it on GitHub:
https://github.com/neicnordic/experimental.neic.nordforsk.org/issues/14#issuecomment-284435167

CSS work postponed until we get the design so from my perspective this issue can be closed.


Establish C++ coding guidelines

Introduction
Establish C++ coding guidelines to be used in the Zephyr repository, and implement means to enforce them.
Problem description
While we have multiple coding and style guideline checkers such as checkpatch.pl and guideline_check.py for the C language, we do not for the C++ language. It is necessary to establish and enforce repository-wide C++ coding and style guidelines in order to ensure code quality and consistency.
Proposed change

Adopt one or more C++ coding and style guidelines for use in the Zephyr repository.

Refer to the "Guideline Candidates" below.

Adopt tools to enforce such guidelines in the CI.
Document the guidelines.

Guideline Candidates

C++ Core Guidelines, maintained by the Standard C++ Foundation
Google C++ Style Guide, maintained by Google

(please feel free to edit this RFC and add any other guidelines that you think would be good for consideration)
Enforcement Tool Candidates

clang-tidy, enforces C++ Core Guidelines (and more)
Cpplint, enforces Google C++ Style Guide

cc @alexanderwachter @yperess @nashif @carlescufi @MaureenHelm @mbolivar-nordic @tejlmand

Hey, just wanted to post here and let you know I haven't forgotten about this. I'm looking at the options and will post my thoughts about this as soon as I have formed a strong opinion.

I think it might be worth to consider the styles supported by clang-tidy and check if one of them can be used, see https://clang.llvm.org/docs/ClangFormatStyleOptions.html#configurable-format-style-options (below BasedOnStyle)
There are also links to style guides from other projects.

OK, so a likely unpopular opinion. I've uploaded a .clang-format file here with a rough guideline. It's non standard in C/C++ but it's close to the style guide for Kotlin. The driving factor here is to minimize diffs and merge conflicts.
clang-format.txt

@yperess Can you provide some examples/sample code in that style? It is hard to see what it looks like with just the .clang-format file.

@yperess Can you provide some examples/sample code in that style? It is hard to see what it looks like with just the .clang-format file.

Sure, here are some examples, it mostly revolves around having things on separate lines. It takes up more vertical space, but makes reviews easier and results in fewer merge conflicts.
int action(
  int color,
  char alpha,
  float
);

int fooNS::FooClass::action(
    int color,
    char alpha,
    float
) {
  return doSomething(
      color,
      alpha
  );
}

ptr
  ->getSelf()
  ->getSelf()
  ->getSelf()
  ->getSelf();

FYI @cfriedt

In terms of linter (clang-tidy), it's possible to run it only on changes too
https://clang.llvm.org/extra/doxygen/clang-tidy-diff_8py_source.html
@stephanosio

C++ Core Guidelines, maintained by the Standard C++ Foundation certainly has my vote. Those guys really though it through.
In addition to those guidelines, please consider following convention of file namings (I'm not sure how it may be enforced except core review remarks):

header files containing C++ code incompatible with C (eg. namespaces, class definitions) should have ".hpp" extension
header files containing mixed C/C++ code should have currently used ".h" extension

This way it would be easy to find files that should not be included by C code. Just an idea.


Added ba.js

Easy to use library for CSS animations

You linked to the minified source code for your library. You need to link to the unminified source.

(Selected for inclusion in commit bundle)

Fixed

Could someone close this PR please? I included it in #735.


Provide Java driver

(you don't have to strictly follow this form)

Use case
As a chDB user I'd like to embedd the chDB inside a Java process
Describe the solution you'd like
Provide a self contained jar providing the library with JDBC bindings similar to https://github.com/duckdb/duckdb-java
Describe alternatives you've considered
Maybe provide some sort of ODBC binding or server endpoint compatible with CH
Additional context

Add any other context or screenshots about the feature request here.

Any Java master could help with this?

Currently, there are 2 Java bindings builing:

https://github.com/linux-china/chdb-java-ffm
https://github.com/chdb-io/chdb-java

Company goes with consolidated JNI and linux-china went with state of the art ffm approach. Love it!


Historical Data Requests for Daily Data Don't Return the Target Quantity with Tick Subscription

Expected Behavior
The response of historical data requests should not depend on the subscription resolution.
Actual Behavior
Historical data requests for daily data don't return the target quantity with tick subscription.
Potential Solution

Reproducing the Problem
class HistoryBug(QCAlgorithm):

    def Initialize(self):
        self.SetStartDate(2021, 10, 28)
        self.SetEndDate(2021, 10, 28)
        self.SetCash(100000) # Set Strategy Cash
        self.symbol = self.AddEquity("F", Resolution.Tick).Symbol

    def OnData(self, data):
        history = self.History([self.symbol], 10, Resolution.Daily)
        assert(history.loc[self.symbol]["close"].count() == 10)

The history has 9 elements instead of 10.
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues
[x] I have provided detailed steps to reproduce the issue

Closing for now since this is due to a data issue.

hmm, you sure? it works correctly if you set
       self.symbol = self.AddEquity("F", Resolution.Minute).Symbol

you sure? it works correctly if you set

Hey Yul! We've addressed the data issue and the reported algorithm now returns 10 data points:
class HistoryBug(QCAlgorithm):

    def Initialize(self):
        self.SetStartDate(2021, 10, 28)
        self.SetEndDate(2021, 10, 28)
        self.SetCash(100000) # Set Strategy Cash
        self.symbol = self.AddEquity("F", Resolution.Tick).Symbol

    def OnData(self, data):
        history = self.History([self.symbol], 10, Resolution.Daily)
        self.Quit(history.loc[self.symbol]["close"].count() == 10)


Linux Release

Are there any plans to release this plugin for Linux? I can see that the windows binaries are available for download, but what about Linux? I'm asking because my friend and I are running a ci/cd pipeline where we grab the windows binaries every time we export our game for windows. I can build the Linux binaries myself, but I figured it would be a bit easier and save a few steps if we could grab the Linux version of the plugin straight from the git repo instead of me having to build it every time there's an updated version.

I though of having a GitHub action to build for windows, Linux and OSX but won't that need putting the EOS SDK code in the repo. I'm unsure about the legality of that.

Got it working.
https://github.com/3ddelano/epic-online-services-godot/actions/runs/7206875017

Got it working. https://github.com/3ddelano/epic-online-services-godot/actions/runs/7206875017

Awesome.  But i'm curious, how did you do it? I had posted on the Epic Games developer forum and I was told that downloading via CLI isn't possible. Are you downloading the sdk via curl? Or using some other method?
Also, apparently it's fine to commit the SDK to a repo so as long as it's a private repo. Here's the post I got:

Yes that's exactly what I did. I made a private GitHub repo with the SDK files. Then made a Personal access token (PAT) for that specific repo with the read repo permission.
Then I added the private repo as a git submodule in the plugin repo. Finally in the in the plugin repo I setup a GitHub action to pull the SDK from the private repo using the PAT and then build the gdextension.


0.3.1rc1 seems to have some leftover debug logs

It seems to be logging some output / input:
hyde.css
styles.css

I will be looking into this. Besides that, the release seems stable.

This was fixed in the above-mentioned PR.


viewport.change fires even when viewport has not changed

I was debugging an off-canvas nav on mobile devices, and ultimately tracked the problem to code that looks something like this:
$(window).resize(
    viewport.change(function() {
        //close off-canvas nav and reset to default
    });
);

When the off-canvas nav "appears", window.resize fires (which is unexpected but at least understandable; we did push something over the edge of the window boundary), but since viewport has not changed (e.g., viewport.current() still reports 'xs') I would not have expected this event to fire.
Maybe this is working as intended, but it's not clear from the documentation. It's easy to workaround, e.g.
$(document).ready(
var __initialviewport = viewport.current();
$(window).resize(function() {
      if (__initialviewport !== viewport.current()) {
        //close off-canvas nav and reset to default
      }
   });
});

So again, I don't know if this really is a bug or just needs better documentation.

Function changed is warper of setTimeout, look at code:
changed: function(fn, ms) {             var timer;             return function(){                 clearTimeout(timer);                 timer = setTimeout(function(){                     fn();                 }, ms || self.interval);             };         }
:-)

@bussemac I think I see how that could have been confusing. You've interpreted viewport.changed as meaning breakpoint changed, due to the fact that viewport.current() returns current breakpoint alias, not viewport size (or any of viewports' dimensions). However, changed method merely serves (as @artvorlov mentioned), as a wrapper around code you want executed on window.resize (= viewport resize).
I'm afraid I cannot supplement changed method with a conditional statement you used, since it's impossible to know how other developers are using said method. Some might use it just for debouncing window resize events, in which case all such checks would cease to work. What I could do however, is to create either

a new method (differs?) returning true/false whenever breakpoint actually differs, or doesn't
a new method, (previous?) that would contain alias of previous breakpoint

I'm open for suggestions which way would be more natural to solve this.

Hmm, doesn't seem that useful, but I guess if you want to respond to any
screen resize, as opposed to a breakpoint change (which makes more sense
since bootstrap isn't going to change your layout unless the breakpoint
changed). Maybe I'll write up breakpointchanged and send a pull request.
On Oct 1, 2015 1:35 AM, "artvorlov"<EMAIL_ADDRESS>wrote:

Function changed is warper of setTimeout, look at code:
changed: function(fn, ms) {
var timer;
return function(){
clearTimeout(timer);
timer = setTimeout(function(){
fn();
}, ms || self.interval);
};
}
:-)
—
Reply to this email directly or view it on GitHub
https://github.com/maciej-gurban/responsive-bootstrap-toolkit/issues/26#issuecomment-144626108
.

I thought about it a little, and I agree with your logic. Due to reasons already mentioned, I cannot apply this change currently, however, I do plan on introducing this change in the next major release. There'll be a ticket with proposed v3 changes soon.


Display vintage on maxar layer

Maxar has a WFS API to display the metadata and vintage (imagery acquisition dates and mosaic cutlines) for the Maxar Premium Imagery. This can be made available for integration into iD.
A couple of links related to the Maxar Mosaic WFS:

User documentation

MaxarCatalogMosaicProducts This Feature type provides users with access to Vivid Mosaic product metadata via a single Feature.
MaxarCatalogMosaicSeamlines This Feature type provides users with access to the seamline information that is available for each Vivid production block.

GitHub link

Maxar is available to discuss access when needed.

With #9710, this is obsolete at the moment. If access to Maxar imagery were restored at some point in the future, we should definitely try to implement this, though!


property className is not supported

I've encountered a bug in my jest jests. I have a very simple test
test('when only icon name is provided', () => {
  render(<Tag iconName='home' />);
});

where Tag is defined as this
import 'styled-components/macro';
...
export const Tag = ({ label, iconName, iconColor, style }: TagProps) => {
  return (
    <View
      css={`
        align-self: flex-start;
        height: 44px;
        flex-direction: row;
        align-items: center;
        border-radius: 100px;
        border-width: 2px;
        border-color: rgba(68, 82, 95, 0.08);
      `}
      style={style}
    >
      {iconName !== undefined && (
        <SvgIcon
          css={`
            margin-left: 14px;
          `}
          color={`${iconColor !== undefined ? iconColor : '#262F56'}`}
          icon={['far', iconName]}
          size={24}
        />
      )}

      {label && (
        <Text
          css={`
            font-family: Gilroy-SemiBold;
            font-size: 17px;
            color: rgba(68, 82, 95, 1);
            text-align: ${iconName !== undefined ? 'left' : 'center'};
            text-align-vertical: top;
            margin-left: ${iconName !== undefined ? 4 : 0}px;
            margin-right: ${iconName !== undefined ? 20 : 0}px;
          `}
        >
          {label}
        </Text>
      )}
    </View>
  );
};

export default Tag;

iconName is directly forwarded into SvgIcon component, which has some assertions checking only valid properties are allowed

assert(
  Object.getOwnPropertyNames(otherProps).length === 0,
    `[ERROR]: properties [${Object.getOwnPropertyNames(
    otherProps
  )}] are not supported`
);

In tests I see this message
[ERROR]: properties [className] are not supported

which means somehow property className were provided into SvgIcon which is not supported by react-native. I think this is a bug in css-to-react-native which incorrectly transpiles css styles into className instead of style.

className property's value is "Tag___StyledSvgIcon-sc-102s8o3-1 iqYFlc" which might be somehow relevant to "jest-styled-components" package.
But I'm not sure how all of these are working together.

You’ve filed this in the wrong project, but I don’t know enough about what you’re doing to point you to the right project. Sorry I can’t be of more help!


[maintenance] cleanup one click training and related

remove unused imports
remove unused gpus6 param from train1key fn
improve readability and reusability for various pathing strings main

Nice. I'll create a workflow for unsed import


fix(es/parser): Revert "Allow arrows without parenthesized param in typescript ( #4138)"

Description:
Context: https://github.com/swc-project/swc/pull/4138#issuecomment-1117976098
Typescript compiler has reverted https://github.com/microsoft/TypeScript/pull/47550 in https://github.com/microsoft/TypeScript/pull/48940 and plan to release this change in 4.8 instead of 4.7 so we should revert support until then.

BREAKING CHANGE:

Related issue (if exists):

breaks https://github.com/swc-project/swc/issues/4067

@dsherret fyi ^


/packit retest-failed and /packit rebuild-failed don't work as expected

Expected behavior is to restart/rebuild only failed tests/builds.
Currently these commands:

rebuild-failed restarts everything - should restart only failed builds
retest-failed restarts every tests - should restart only failed tests.

everything seems to working fine to this point. *_targets_override fills up with correct targets to rebuild/retest. Something after that might be broken.

It looks like it restarts everything for Retry button in the Checks UI as well...;(
I hit that here: https://github.com/packit/specfile/pull/25/checks?check_run_id=5656718240

Do you mean the Re-run button next to a failed job?

Do you mean the Re-run button next to a failed job?

Yes, sorry about the bad text for that, but I really meant Re-run for a single result.

Also Re-run for individual jobs works correctly... seems like there is something between which overrides the targets_override

I don't think so. Maybe I mixed that with something else but still think it triggered everything...

I don't think so. Maybe I mixed that with something else (multi-job scenario, identifiers,...) but still think it triggered everything...

 It works... but for builds everything is restarted :/
It definitely worked when Laura implemented #1227 so something definitely overrides the targets_override :D

closed with #1479


Friends List Update - per-player login/out mute

As in the title, good to be able to control players who we see login/logout messages from

Added in 4fe37f978cd72a4b31e3efaee73bbdf0fcae3b20


Create readonly UI

This PR provides that when rill start --readonly:

Sources and Models are hidden from the navigation sidebar. Any direct navigation to these pages results in a 404.
The Edit Metrics button is hidden from the Dashboard workspace

Noted over Slack that we should probably hide some of the bullets on the splash page in readonly mode as well.

lgtm. If a metrics config is invalid, it does still show up in the sidebar in readonly mode.
Feel free to merge once that's addressed.

I think that's addressed by the CLI's --strict flag. Since we're going to run rill start --readonly --strict, if any artifact fails to validate, the process will exit with a fatal error.


Update autoscaler version

Marking stale. Pleae update within one week.

1.1.0 released

It was not always clear what is really what. See  https://github.com/kubernetes/autoscaler/issues/346#issuecomment-351348942

http://blog.kubernetes.io/2017/12/kubernetes-19-workloads-expanded-ecosystem.html

Hey @bhack @timstoop any word on whether this can work with 1.8 and 1.9?

Looks like this is already updated in master by https://github.com/kubernetes/charts/pull/3248
Suggest to close, the readme is also out of date
Re @timstoop 's comment, 1.1.0 is used by the kops addon for K8S 1.8. 1.1.1 dropped earlier this month

/ok-to-test