feat(package-managers/python)!: Support Python 3.11

Add "3.11" to the list of python versions which ORT allows to pass to python-inspector via the -p option. Doing so leads to a successful analysis of python projects which require python version 3.11. This also work for any analysis triggered from Poetry.kt via the approch to generate the requirements file from pyproject.toml. In particular, this works without upgrading the installed python verison to 3.11
The change is breaking, because also the default python version is changed to 3.11. For analyzing Python projects targeting 3.10 the Python version as of now must be explicitly specified.
Fixes #7476.

Note: This PR conflicts with [1], I didn't intentionally repeat the work from [1], but have been debugging analyzing pyproject.toml without being aware [1] is related, and this is the result from it. So, I believe this PR minimizes the changes for supporting 3.11.
[1] https://github.com/oss-review-toolkit/ort/pull/7533

If this is sufficient to support analysis of pyproject.toml files with python 3.11 as requirement I'm happy and we can close https://github.com/oss-review-toolkit/ort/pull/7533 - Thanks :)

If this is sufficient to support analysis of pyproject.toml files with python 3.11 as requirement I'm happy and we can close #7533 - Thanks :)

Let's see. There is this diff in the test, which some solution for is needed. Did you run into the same @mawl ?

Let's see. There is this diff in the test, which some solution for is needed. Did you run into the same @mawl ?
@fviernau: I saw the diff of the PoetryFunTest in my PR but haven't tried to fix it.


Enabling std feature doesnt seem to actually use std features

Testing around I didn't find anything in particular that would be causing this.
Particular issue that made me aware of the issue: DigestParseError doesnt implement std::error::Error:
https://i.imgur.com/v2RND5Z.png https://i.imgur.com/POSG6j3.png
Ref: uuid-rs/uuid#144

I'm not entirely understanding what's happening here. The digest parse error is defined like this:
#[cfg(feature="std")]
impl std::error::Error for DigestParseError {
    fn description(&self) -> &str {
        "not a valid sha1 hash"
    }
}

Thats what really confused me, since that should ideally work. I have been messing around with a local clone of the project trying this to work. building the sha1 crate itself this seems to work but when using it from another crate error seems to not exist

That looks more like the additional feature is not set at all, also indicated by the warnings.

Going to close this here. This seems unrelated to this crate.

Right, this defin I asked for help on the users forum, although no one came forward https://users.rust-lang.org/t/need-help-with-feature-gates-because-cargo-and-feature-gates-are-fun-ie-not/15602
I have more details there that you can look at.


Log dart messages to file

This will allow to log messages using the FLog, which allows to export any logs to file.
resolves #103

bors r+

bors r+


Better (but not completely fixed) treatment of venv

- get rid of requirements check for recreation

- store .devenv_interpreter because the venv
  python binary resolves to the origin
  python of the wrapper, not the wrapper
  python

In practice, merging this commit will mean that

a) the invocation of pip install -r will
need to take care of any changed requirements.

b) the venv, once created, will never be recreated
unless the Python wrapper changes.  The Python
wrapper doesn't seem to change when you add
Python packages to your packages = list, I'm
not sure what the other circumstances might be.

In reality, this fix sucks because the venv is
not actually based on the wrapper.  The wrapper,
in fact, seems to never get used.  That will
need to be addressed in some other commit, though.

Sorry, I thought I squashed all those commits.

Nice! If we can get the wrapper to be passed to the virtualenv correctly that will solve all the issues with dynamic linking :)

I wonder, why get rid of requirements checking? I like that it would rebuild the venv if it changes and I'd expect it to.

I wonder, why get rid of requirements checking? I like that it would rebuild the venv if it changes and I'd expect it to.

The particular form of requirements checking that I took out didn't make too much sense, I don't think.  It checked for a literal "requirements.txt" inside the devenv root, which can't really work generically.
In addition (and maybe unrelatedly), I think I would prefer it if "devenv up" did not try to run pip install -r again.  I think that job should be relegated to the flake rebuild.

Nice! If we can get the wrapper to be passed to the virtualenv correctly that will solve all the issues with dynamic linking :)

If the venv's "python" resolves to the wrapper we won't need the .devev_interpreter thing at all.  I just can't figure out how to make the venv's python resolve to the wrapper.

See also my rationale at https://github.com/cachix/devenv/pull/745#issuecomment-1859298847

The reason that the venv's bin/python resolves to the bin/python of the parent of the wrapper (and doesn't resolve to the wrapper's bin/python) is due to how sys._base_executable works in Python.  It somehow detects that the wrapper is based on the parent, and returns the wrapper's parent rather than the wrapper.  There is a bit of documentation saying that you might be able to set PYVENV_LAUNCHER to point at the wrapper, but it does not work under 3.11.6 at least.

I think maybe this is another reason to not pip install on devenv up.  This is me starting a container that was generated via devenv container <containername> --docker-run.  It really should not be pip installing anything here IMO, or at least there should be an option such that it doesn't.
❯ docker start -i lucid_wing
WARNING: pre-commit-hooks.nix: git command not found; skipping installation.
Obtaining file:/// (from -r /nix/store/2cjacq6j9ms8f588fy4395h3d246gadk-requirements.txt (line 2))
  Installing build dependencies ... done
  Checking if build backend supports build_editable ... done
  Getting requirements to build editable ... done
  Installing backend dependencies ... done
  Preparing editable metadata (pyproject.toml) ... done
Requirement already satisfied: amqp==5.1.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 1)) (5.1.1)
Requirement already satisfied: async-timeout==4.0.2 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 2)) (4.0.2)
Requirement already satisfied: billiard==4.1.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 3)) (4.1.0)
Requirement already satisfied: blinker==1.6.2 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 4)) (1.6.2)
Requirement already satisfied: Brotli==1.0.9 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 5)) (1.0.9)
Requirement already satisfied: cachelib==0.10.2 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 6)) (0.10.2)
Requirement already satisfied: celery==5.3.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 7)) (5.3.0)
Requirement already satisfied: certifi==2023.5.7 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 8)) (2023.5.7)
Requirement already satisfied: cffi==1.15.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 9)) (1.15.1)
Requirement already satisfied: charset-normalizer==3.1.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 10)) (3.1.0)
Requirement already satisfied: click==8.1.3 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 11)) (8.1.3)
Requirement already satisfied: click-didyoumean==0.3.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 12)) (0.3.0)
Requirement already satisfied: click-plugins==1.1.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 13)) (1.1.1)
Requirement already satisfied: click-repl==0.2.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 14)) (0.2.0)
Requirement already satisfied: cryptography==40.0.2 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 15)) (40.0.2)
Requirement already satisfied: dash==2.10.2 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 16)) (2.10.2)
Requirement already satisfied: dash-bootstrap-components==1.4.2 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 17)) (1.4.2)
Requirement already satisfied: dash-core-components==2.0.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 18)) (2.0.0)
Requirement already satisfied: dash-html-components==2.0.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 19)) (2.0.0)
Requirement already satisfied: dash-table==5.0.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 20)) (5.0.0)
Requirement already satisfied: decorator==5.1.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 21)) (5.1.1)
Requirement already satisfied: dnspython==2.3.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 22)) (2.3.0)
Requirement already satisfied: email-validator==2.0.0.post2 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 23)) (2.0.0.post2)
Requirement already satisfied: et-xmlfile==1.1.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 24)) (1.1.0)
Requirement already satisfied: Flask==2.2.5 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 25)) (2.2.5)
Requirement already satisfied: Flask-Admin==1.6.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 26)) (1.6.1)
Requirement already satisfied: Flask-Compress==1.13 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 27)) (1.13)
Requirement already satisfied: Flask-Login==0.6.2 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 28)) (0.6.2)
Requirement already satisfied: Flask-Mail==0.9.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 29)) (0.9.1)
Requirement already satisfied: flask-mongoengine==1.0.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 30)) (1.0.0)
Requirement already satisfied: Flask-PyMongo==2.3.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 31)) (2.3.0)
Requirement already satisfied: Flask-Session==0.5.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 32)) (0.5.0)
Requirement already satisfied: Flask-SQLAlchemy==2.5.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 33)) (2.5.1)
Requirement already satisfied: Flask-WTF==1.1.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 34)) (1.1.1)
Requirement already satisfied: flower==1.2.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 35)) (1.2.0)
Requirement already satisfied: future==0.18.3 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 36)) (0.18.3)
Requirement already satisfied: greenlet==2.0.2 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 37)) (2.0.2)
Requirement already satisfied: gunicorn==20.1.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 38)) (20.1.0)
Requirement already satisfied: humanize==4.6.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 39)) (4.6.0)
Requirement already satisfied: idna==3.4 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 40)) (3.4)
Requirement already satisfied: importlib-metadata==6.6.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 41)) (6.6.0)
Requirement already satisfied: infinity==1.5 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 42)) (1.5)
Requirement already satisfied: intervals==0.9.2 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 43)) (0.9.2)
Requirement already satisfied: itsdangerous==2.1.2 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 44)) (2.1.2)
Requirement already satisfied: Jinja2==3.1.2 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 45)) (3.1.2)
Requirement already satisfied: kombu==5.3.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 46)) (5.3.0)
Requirement already satisfied: lxml==4.9.2 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 47)) (4.9.2)
Requirement already satisfied: MarkupSafe==2.1.3 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 48)) (2.1.3)
Requirement already satisfied: mongoengine==0.27.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 49)) (0.27.0)
Requirement already satisfied: mpmath==1.3.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 50)) (1.3.0)
Collecting numpy==1.24.3 (from -r //requirements.txt (line 51))
  Using cached numpy-1.24.3-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (17.3 MB)
Requirement already satisfied: openpyxl==3.1.2 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 52)) (3.1.2)
Requirement already satisfied: packaging==23.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 53)) (23.1)
Collecting pandas==2.0.2 (from -r //requirements.txt (line 54))
  Using cached pandas-2.0.2-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (18 kB)
Requirement already satisfied: plotly==5.14.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 55)) (5.14.1)
Requirement already satisfied: prometheus-client==0.17.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 56)) (0.17.0)
Requirement already satisfied: prompt-toolkit==3.0.38 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 57)) (3.0.38)
Requirement already satisfied: pycparser==2.21 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 58)) (2.21)
Requirement already satisfied: Pygments==2.15.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 59)) (2.15.1)
Requirement already satisfied: pymongo==4.3.3 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 60)) (4.3.3)
Requirement already satisfied: pyodbc==4.0.39 in /nix/store/c7sz3pcjkf8bar9vjxp6b8fa5aszlyf9-devenv-profile/lib/python3.11/site-packages (from -r //requirements.txt (line 61)) (4.0.39)
Requirement already satisfied: PyPDF2==3.0.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 62)) (3.0.1)
Requirement already satisfied: pysolr==3.9.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 63)) (3.9.0)
Requirement already satisfied: python-dateutil==2.8.2 in /nix/store/1ldddmwidjj4q9c6x24zn29qzbjr3d44-python3.11-python-dateutil-2.8.2/lib/python3.11/site-packages (from -r //requirements.txt (line 64)) (2.8.2)
Requirement already satisfied: python-dotenv==1.0.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 65)) (1.0.0)
Collecting pytz==2023.3 (from -r //requirements.txt (line 66))
  Using cached pytz-2023.3-py2.py3-none-any.whl (502 kB)
Requirement already satisfied: redis==4.5.5 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 67)) (4.5.5)
Requirement already satisfied: requests==2.31.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 68)) (2.31.0)
Requirement already satisfied: scipy==1.10.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 69)) (1.10.1)
Requirement already satisfied: simplejson==3.19.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 70)) (3.19.1)
Requirement already satisfied: six==1.16.0 in /nix/store/4sc3q00ml4hb9drlsmvvbim9czrf6isx-python3.11-six-1.16.0/lib/python3.11/site-packages (from -r //requirements.txt (line 71)) (1.16.0)
Requirement already satisfied: SQLAlchemy==1.4.48 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 72)) (1.4.48)
Requirement already satisfied: SQLAlchemy-Utils==0.41.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 73)) (0.41.1)
Requirement already satisfied: sympy==1.12 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 74)) (1.12)
Requirement already satisfied: tenacity==8.2.2 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 75)) (8.2.2)
Requirement already satisfied: tornado==6.3.2 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 76)) (6.3.2)
Requirement already satisfied: typing_extensions==4.6.3 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 77)) (4.6.3)
Requirement already satisfied: unyt==2.9.5 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 78)) (2.9.5)
Requirement already satisfied: urllib3==1.26 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 79)) (1.26.0)
Requirement already satisfied: validators==0.20.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 80)) (0.20.0)
Requirement already satisfied: vine==5.0.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 81)) (5.0.0)
Collecting Wand==0.6.11 (from -r //requirements.txt (line 82))
  Using cached Wand-0.6.11-py2.py3-none-any.whl (143 kB)
Requirement already satisfied: wcwidth==0.2.6 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 83)) (0.2.6)
Requirement already satisfied: Werkzeug==2.2.3 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 84)) (2.2.3)
Requirement already satisfied: WTForms==3.0.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 85)) (3.0.1)
Requirement already satisfied: WTForms-Components==0.10.5 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 86)) (0.10.5)
Requirement already satisfied: zipp==3.15.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 87)) (3.15.0)
Requirement already satisfied: alabaster==0.7.13 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 89)) (0.7.13)
Requirement already satisfied: Babel==2.12.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 90)) (2.12.1)
Requirement already satisfied: bleach==6.0.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 91)) (6.0.0)
Requirement already satisfied: bump2version==1.0.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 92)) (1.0.1)
Requirement already satisfied: cachetools==5.3.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 93)) (5.3.1)
Requirement already satisfied: chardet==5.1.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 94)) (5.1.0)
Requirement already satisfied: colorama==0.4.6 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 95)) (0.4.6)
Requirement already satisfied: coverage==7.2.7 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 96)) (7.2.7)
Requirement already satisfied: distlib==0.3.6 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 97)) (0.3.6)
Requirement already satisfied: docutils==0.20.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 98)) (0.20.1)
Requirement already satisfied: filelock==3.12.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 99)) (3.12.0)
Requirement already satisfied: flake8==6.0.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 100)) (6.0.0)
Requirement already satisfied: imagesize==1.4.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 101)) (1.4.1)
Requirement already satisfied: inflect==6.0.4 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 102)) (6.0.4)
Requirement already satisfied: iniconfig==2.0.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 103)) (2.0.0)
Requirement already satisfied: jaraco.classes==3.2.3 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 104)) (3.2.3)
Requirement already satisfied: jeepney==0.8.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 105)) (0.8.0)
Requirement already satisfied: keyring==23.13.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 106)) (23.13.1)
Requirement already satisfied: markdown-it-py==2.2.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 107)) (2.2.0)
Requirement already satisfied: mccabe==0.7.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 108)) (0.7.0)
Requirement already satisfied: mdurl==0.1.2 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 109)) (0.1.2)
Requirement already satisfied: more-itertools==9.1.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 110)) (9.1.0)
Requirement already satisfied: pkginfo==1.9.6 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 111)) (1.9.6)
Requirement already satisfied: platformdirs==3.5.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 112)) (3.5.1)
Requirement already satisfied: pluggy==1.0.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 113)) (1.0.0)
Requirement already satisfied: pycodestyle==2.10.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 114)) (2.10.0)
Requirement already satisfied: pydantic==1.10.8 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 115)) (1.10.8)
Requirement already satisfied: pyflakes==3.0.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 116)) (3.0.1)
Requirement already satisfied: pyproject_api==1.5.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 117)) (1.5.1)
Requirement already satisfied: pytest==7.3.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 118)) (7.3.1)
Requirement already satisfied: pytest-mock==3.10.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 119)) (3.10.0)
Requirement already satisfied: pytest-runner==6.0.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 120)) (6.0.0)
Requirement already satisfied: readme-renderer==37.3 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 121)) (37.3)
Requirement already satisfied: requests-toolbelt==1.0.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 122)) (1.0.0)
Requirement already satisfied: rfc3986==2.0.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 123)) (2.0.0)
Requirement already satisfied: rich==13.4.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 124)) (13.4.1)
Requirement already satisfied: SecretStorage==3.3.3 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 125)) (3.3.3)
Requirement already satisfied: snowballstemmer==2.2.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 126)) (2.2.0)
Requirement already satisfied: snowflake_connector_python==3.0.4 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 127)) (3.0.4)
Requirement already satisfied: Sphinx==7.0.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 128)) (7.0.1)
Requirement already satisfied: sphinxcontrib-applehelp==1.0.4 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 129)) (1.0.4)
Requirement already satisfied: sphinxcontrib-devhelp==1.0.2 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 130)) (1.0.2)
Requirement already satisfied: sphinxcontrib-htmlhelp==2.0.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 131)) (2.0.1)
Requirement already satisfied: sphinxcontrib-jsmath==1.0.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 132)) (1.0.1)
Requirement already satisfied: sphinxcontrib-qthelp==1.0.3 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 133)) (1.0.3)
Requirement already satisfied: sphinxcontrib-serializinghtml==1.1.5 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 134)) (1.1.5)
Requirement already satisfied: sqlacodegen==2.3.0.post1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 135)) (2.3.0.post1)
Requirement already satisfied: tox==4.6.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 136)) (4.6.0)
Requirement already satisfied: twine==4.0.2 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 137)) (4.0.2)
Requirement already satisfied: tzdata==2023.3 in /nix/store/nm4ihmxpjzhvm6yw2q5iwdj6bw4snj42-python3.11-tzdata-2023.3/lib/python3.11/site-packages (from -r //requirements.txt (line 138)) (2023.3)
Requirement already satisfied: virtualenv==20.23.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 139)) (20.23.0)
Requirement already satisfied: watchdog==3.0.0 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 140)) (3.0.0)
Requirement already satisfied: webencodings==0.5.1 in /.devenv/state/venv/lib/python3.11/site-packages (from -r //requirements.txt (line 141)) (0.5.1)
Requirement already satisfied: setuptools>=3.0 in /nix/store/y8yq448xka665bqyd5gvdhajqdbsnyys-python3.11-setuptools-68.2.2/lib/python3.11/site-packages (from gunicorn==20.1.0->-r //requirements.txt (line 38)) (68.2.2.post0)
Requirement already satisfied: asn1crypto<2.0.0,>0.24.0 in /.devenv/state/venv/lib/python3.11/site-packages (from snowflake_connector_python==3.0.4->-r //requirements.txt (line 127)) (1.5.1)
Requirement already satisfied: oscrypto<2.0.0 in /.devenv/state/venv/lib/python3.11/site-packages (from snowflake_connector_python==3.0.4->-r //requirements.txt (line 127)) (1.3.0)
Requirement already satisfied: pyOpenSSL<24.0.0,>=16.2.0 in /.devenv/state/venv/lib/python3.11/site-packages (from snowflake_connector_python==3.0.4->-r //requirements.txt (line 127)) (23.2.0)
Requirement already satisfied: pycryptodomex!=3.5.0,<4.0.0,>=3.2 in /.devenv/state/venv/lib/python3.11/site-packages (from snowflake_connector_python==3.0.4->-r //requirements.txt (line 127)) (3.19.0)
Requirement already satisfied: pyjwt<3.0.0 in /.devenv/state/venv/lib/python3.11/site-packages (from snowflake_connector_python==3.0.4->-r //requirements.txt (line 127)) (2.8.0)
Requirement already satisfied: sortedcontainers>=2.4.0 in /.devenv/state/venv/lib/python3.11/site-packages (from snowflake_connector_python==3.0.4->-r //requirements.txt (line 127)) (2.4.0)
Using cached pandas-2.0.2-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (12.2 MB)
Building wheels for collected packages: eao_dash
  Building editable for eao_dash (pyproject.toml) ... done
  Created wheel for eao_dash: filename=eao_dash-0.43.0.dev20231223-0.editable-py2.py3-none-any.whl size=3352 sha256=c91ba3f14e7333ca09096cd9058595c7003a3cbac2e30ac04a4f6d1d6df1ac24
  Stored in directory: /tmp/nix-shell.s9m41w/pip-ephem-wheel-cache-swlgxdaz/wheels/0a/e6/5f/7890bed7e6ede0be54e51a5211aa22f3998e0f39a540b02155
Successfully built eao_dash
Installing collected packages: Wand, pytz, numpy, pandas, eao_dash
  Attempting uninstall: Wand
    Found existing installation: Wand 0.6.13
    Not uninstalling wand at /nix/store/c7sz3pcjkf8bar9vjxp6b8fa5aszlyf9-devenv-profile/lib/python3.11/site-packages, outside environment /.devenv/state/venv
    Can't uninstall 'Wand'. No files were found to uninstall.
  Attempting uninstall: pytz
    Found existing installation: pytz 2023.3.post1
    Not uninstalling pytz at /nix/store/fj8jr8zghq5abfa6a04qq32bmgxz3gpd-python3.11-pytz-2023.3.post1/lib/python3.11/site-packages, outside environment /.devenv/state/venv
    Can't uninstall 'pytz'. No files were found to uninstall.
  Attempting uninstall: numpy
    Found existing installation: numpy 1.26.1
    Not uninstalling numpy at /nix/store/hpr19vaw5alwnmnd8nyf6r50n4hwwj1a-python3.11-numpy-1.26.1/lib/python3.11/site-packages, outside environment /.devenv/state/venv
    Can't uninstall 'numpy'. No files were found to uninstall.
  Attempting uninstall: pandas
    Found existing installation: pandas 2.1.1
    Not uninstalling pandas at /nix/store/c7sz3pcjkf8bar9vjxp6b8fa5aszlyf9-devenv-profile/lib/python3.11/site-packages, outside environment /.devenv/state/venv
    Can't uninstall 'pandas'. No files were found to uninstall.
  Attempting uninstall: eao_dash
    Found existing installation: eao_dash 0.43.0.dev20231223
    Uninstalling eao_dash-0.43.0.dev20231223:
      Successfully uninstalled eao_dash-0.43.0.dev20231223
Successfully installed Wand-0.6.11 eao_dash-0.43.0.dev20231223 numpy-1.24.3 pandas-2.0.2 pytz-2023.3
✨ devenv 0.6.3 is out of date. Please update to 1.0: https://devenv.sh/getting-started/#installation
'FLASK_ENV' is deprecated and will not be used in Flask 2.3. Use 'FLASK_DEBUG' instead.
[2023-12-23 19:56:09,472] ERROR in errors: Logging level: 10: user:None, ip:None, url:None
/.devenv/state/venv/lib/python3.11/site-packages/flask_admin/model/base.py:1416: UserWarning: Fields missing from ruleset: TowerPaint,DAType,InterfaceName,AveragingInterval,TimeFromUTM,StartDate,EndDate,ElevationUnits,HeightUnits,long_UTM,lat_UTM,Coordinatesystem,Projection,StateName,County,InstallcrewManager,InstallContractor,Updateddate,Access_Key,Access_Method,AcquiredFrom,Describe,DataContractor,CreateDate,Createdby,UpdateDate,Updatedby,OldName,OldGisStationID,exposure,MagneticDeclanation,datum,Location,LandQualityCheck,ApexActionItems,GHActionItems,ThirdPartyActionItems,LastRecord,WorkStatus,landcomment,Add_Comments,ZipCode,TaxDistrictNumber,Township,DateFiledLast,cost,MarkerBalls,MarkerBallSets,GuyGuards,Logger_Make,Logger_Model,Logger_Rev,Logger_serialnumber,Logger_timezone,ipack_Callintime,ipack_Callfrequency,ipack_networktype,ipack_make,ipack_serialnumber,ipack_simnum,ipack_IMEI_ESN,ipack_IMSI,ipack_MSISDNCMDN,ipack_activationdate,ipack_lastcall,OAC_Notification,OAC_Type,OAC_Date,OAC_Compliance,ODM,ipack_NetworkProvider,ScheduledMainDate,rldlogger,subjectline
  warnings.warn(text)
/.devenv/state/venv/lib/python3.11/site-packages/flask_admin/model/base.py:1416: UserWarning: Fields missing from ruleset: _cls
  warnings.warn(text)
[2023-12-23 19:56:10,921] ERROR in __init__: badash.availability did not load.: user:None, ip:None, url:None
[2023-12-23 19:56:10,922] ERROR in __init__: badash.generation_revenue did not load.: user:None, ip:None, url:None
[2023-12-23 19:56:10,922] ERROR in __init__: badash.swap_old_settler did not load.: user:None, ip:None, url:None
[2023-12-23 19:56:10,923] ERROR in __init__: badash.park_summary did not load.: user:None, ip:None, url:None
[2023-12-23 19:56:10,923] ERROR in __init__: badash.sensor_snapshot_windspeed did not load.: user:None, ip:None, url:None
[2023-12-23 19:56:10,924] ERROR in __init__: badash.single_turb_sensr did not load.: user:None, ip:None, url:None
[2023-12-23 19:56:10,924] ERROR in __init__: badash.single_turb_performance did not load.: user:None, ip:None, url:None
[2023-12-23 19:56:10,925] ERROR in __init__: phade.app did not load.: user:None, ip:None, url:None
'FLASK_ENV' is deprecated and will not be used in Flask 2.3. Use 'FLASK_DEBUG' instead.
'FLASK_ENV' is deprecated and will not be used in Flask 2.3. Use 'FLASK_DEBUG' instead.
 * Serving Flask app 'eao_dash.wsgi:application'
 * Debug mode: on
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
 * Running on all addresses (<IP_ADDRESS>)
 * Running on http://<IP_ADDRESS>:5150
 * Running on http://<IP_ADDRESS>:5150
Press CTRL+C to quit
 * Restarting with watchdog (inotify)
'FLASK_ENV' is deprecated and will not be used in Flask 2.3. Use 'FLASK_DEBUG' instead.
[2023-12-23 19:56:12,292] ERROR in errors: Logging level: 10: user:None, ip:None, url:None
/.devenv/state/venv/lib/python3.11/site-packages/flask_admin/model/base.py:1416: UserWarning: Fields missing from ruleset: TowerPaint,DAType,InterfaceName,AveragingInterval,TimeFromUTM,StartDate,EndDate,ElevationUnits,HeightUnits,long_UTM,lat_UTM,Coordinatesystem,Projection,StateName,County,InstallcrewManager,InstallContractor,Updateddate,Access_Key,Access_Method,AcquiredFrom,Describe,DataContractor,CreateDate,Createdby,UpdateDate,Updatedby,OldName,OldGisStationID,exposure,MagneticDeclanation,datum,Location,LandQualityCheck,ApexActionItems,GHActionItems,ThirdPartyActionItems,LastRecord,WorkStatus,landcomment,Add_Comments,ZipCode,TaxDistrictNumber,Township,DateFiledLast,cost,MarkerBalls,MarkerBallSets,GuyGuards,Logger_Make,Logger_Model,Logger_Rev,Logger_serialnumber,Logger_timezone,ipack_Callintime,ipack_Callfrequency,ipack_networktype,ipack_make,ipack_serialnumber,ipack_simnum,ipack_IMEI_ESN,ipack_IMSI,ipack_MSISDNCMDN,ipack_activationdate,ipack_lastcall,OAC_Notification,OAC_Type,OAC_Date,OAC_Compliance,ODM,ipack_NetworkProvider,ScheduledMainDate,rldlogger,subjectline
  warnings.warn(text)
/.devenv/state/venv/lib/python3.11/site-packages/flask_admin/model/base.py:1416: UserWarning: Fields missing from ruleset: _cls
  warnings.warn(text)
[2023-12-23 19:56:13,686] ERROR in __init__: badash.availability did not load.: user:None, ip:None, url:None
[2023-12-23 19:56:13,687] ERROR in __init__: badash.generation_revenue did not load.: user:None, ip:None, url:None
[2023-12-23 19:56:13,688] ERROR in __init__: badash.swap_old_settler did not load.: user:None, ip:None, url:None
[2023-12-23 19:56:13,688] ERROR in __init__: badash.park_summary did not load.: user:None, ip:None, url:None
[2023-12-23 19:56:13,689] ERROR in __init__: badash.sensor_snapshot_windspeed did not load.: user:None, ip:None, url:None
[2023-12-23 19:56:13,689] ERROR in __init__: badash.single_turb_sensr did not load.: user:None, ip:None, url:None
[2023-12-23 19:56:13,690] ERROR in __init__: badash.single_turb_performance did not load.: user:None, ip:None, url:None
[2023-12-23 19:56:13,690] ERROR in __init__: phade.app did not load.: user:None, ip:None, url:None
'FLASK_ENV' is deprecated and will not be used in Flask 2.3. Use 'FLASK_DEBUG' instead.
'FLASK_ENV' is deprecated and will not be used in Flask 2.3. Use 'FLASK_DEBUG' instead.
 * Debugger is active!
 * Debugger PIN: 106-155-814

It's likely I should close this PR and open several that break out the changes.

This PR is superseded by #905 #911 and #912


server+tor: add support for Tor HASHEDPASSWORD authentication method

Tested and confirmed locally that all three authentication methods (SAFECOOKIE, HASHEDPASSWORD, NULL) work as intended. SAFECOOKIE remains as the default unless a control password is provided.
Replaces https://github.com/lightningnetwork/lnd/pull/2548.

Would be cool to update docs/configuring_tor.md to indicate that there's an option other than safecookie available.

@carlaKC added!


$$__Adding visualizer for songs

Sir I think we should add visualizer also for better user experience  while listening songs without logging in Spotify website because in general no one wants to login in any extra website .please assign this task to me

Awesome Idea , Yeah @MayankRaje go ahead !

sir i have created a pull request on git hub please have a look on it about
adding a new audio visualiser feature
On Mon, Dec 6, 2021 at 11:15 AM Ghulam Yazdani @.***>
wrote:

Assigned #19 https://github.com/ghulamyazdani/TruHealth/issues/19 to
@MayankRaje https://github.com/MayankRaje.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/ghulamyazdani/TruHealth/issues/19#event-5718242475,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARC4HUFYUG2DSQH2CVNV4YDUPREYJANCNFSM5JNAVUVA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

sir i have merged a branch for adding an audio visualizer so can i close
this issue #19
On Sun, Dec 12, 2021 at 12:20 AM MAYANK RAJE @.***>
wrote:

sir i have created a pull request on git hub please have a look on it
about adding a new audio visualiser feature
On Mon, Dec 6, 2021 at 11:15 AM Ghulam Yazdani @.***>
wrote:

Assigned #19 https://github.com/ghulamyazdani/TruHealth/issues/19 to
@MayankRaje https://github.com/MayankRaje.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/ghulamyazdani/TruHealth/issues/19#event-5718242475,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARC4HUFYUG2DSQH2CVNV4YDUPREYJANCNFSM5JNAVUVA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Investigating final link on Who? Makers FAQ

@linderr this doesn't quite resolve the problem, the problem is in en.json -- the text in the template only ever comes through if en.json doesn't have a matching key (or if our i18n javascript breaks).
the issue is at the end of that line: They are also collating <a href=\"https://www.nationofmakers.us/covid-19-maker-response\"resources for makers responding to COVID-19." doesn't actually close the opening  tag. So you just need to add > after the URL. https://github.com/findthemasks/findthemasks/blob/master/public/i18n/en.json#L255

oi - I skimmed that line like 3 times and didn't catch it!!
A volunteer saw it on our main site so apparently it's been like this for weeks lol!

waiting for deployment for final check then merging - thank you!


Use Jest properly

Make use of test.each functionality instead of running for loops for some tests using multiple input files.

Fixed in #166 (or somewhere around there 🤷)


Find Lapack

hello
I'm using mingw, i compiled openblas and install it under /opt
But cmake can't find lapack, is there a way to set the root folder of openblas ?
best regards.

something like
cmake -Bbuild -DLAPACK_ROOT=/opt


Add ability to set how often the docker image should be downloaded

When Bring Your Own image, sometimes you might be still building the docker image and need to have KFP to always download new images.

This option is available as a container argument image_pull_policy on the ContainerOp.  The default is IfNotPresent so we'd need the ability to set Always.
I think the bigger question is where will this value come from?  Intuitively, it seems reasonable to have this be a field in the runtime-images metadata.  But there are two issues with that:

We currently set the actual image_name:tag in the pipeline information, so elyra (where this information is required) has no way to definitively locate the runtime-images metadata instance to get the pull policy from.
If there are multiple nodes in the pipeline using this image, do you really want the execution of every node to pull the image?  I suspect you'd only want the image pulled if the downstream node in the pipeline is not running on the same machine.

I think instead, you'd want this property set at the UI level since the user knows which of the nodes first uses the Docker image in question.  But again, the converse of 2 is a question, what about the downstream nodes running on different hosts?
Hmm - I guess you'd want the image always updated - even if the current node is colocated with its upstream node using the same image - and just hope the always-pull logic does a SHA comparison (which I suspect it does) so as to not incur that overhead.
So item 2 can be resolved as a non-issue (with the assumption that the pull policy logic is efficient).  Item 1 should be addressed by using the runtime-images name rather than its image_name field within the pipeline and let Elyra lookup the runtime-images instance to get both image_name and its pull_policy values.
Thoughts?


Auto-labels 'Gemma' on 'gemma' issues/PRs.

This workflow automatically identifies issues and pull requests (PRs) related to Gemma.
It searches for the keyword Gemma (case-insensitive) in both the title and description of the issue/PR.
If a match is found, the workflow adds the label Gemma to the issue/PR.
On first run, the workflow will try to create the label Gemma. If unsuccessful, the repository owner will need to create it manually.
label: Gemma

Hi @shmishra99 the repo is gemma.cpp so on one hand every issue could be tagged as gemma related. On the other hand filtering for "gemma" as a keyword is not going to get additional specificity of whether the issue is about gemma the model or some other part of the repo.
There's already some amount of workflow automation complexity to this repo between copybara + CI automation, so we're trying not to add more than is needed. If I'm missing context here, feel free to ping me offline directly.


LSTM - Stock Price Prediction

Description
(Write your answer here.)
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
#104

Hi, please link the notebook to the readme of the machine learning directory.

Hello the requested changes is done now

Hi, please link the notebook to the readme of the main ML directory.

Link added successfully to the main readme file


Workload: Add warning if manifest parse contains errors

fixes #390

Codecov Report

Merging #391 into master will increase coverage by 0.15%.
The diff coverage is 40.00%.

@@            Coverage Diff             @@
##           master     #391      +/-   ##
==========================================
+ Coverage   59.19%   59.35%   +0.15%
==========================================
  Files        1052     1052
  Lines       33119    33124       +5
  Branches     4643     4645       +2
==========================================
+ Hits        19606    19661      +55
+ Misses      13513    13463      -50


contentStyle CSS not in the build

How to reproduce : clone the project, yarn + yarn dev, load in Chrome -> Unable to load the contentStyle16801943738.chunk.css file.
It's not present in the css dir in the dist.

With a previous version of the boilerplate on the main branch (March 8) it's working.

@hugoobauer

https://github.com/Jonghakseo/chrome-extension-boilerplate-react-vite/pull/82

I'm sorry. We inadvertently merged the above dependency update PR and it caused a problem. It shouldn't happen now. We apologize for the inconvenience.

@all-contributors please add @hugoobauer for bug


Game crash while farming, planting threes

Steps to reproduce:

Plant some turnip/carrot seeds.
Planting some Beech seeds.

Observed behavior:
Game crash. The following errors (multiple instances) are observed in LogOutput.log:
[Info   : Unity Log] 03/06/2021 10:35:02: Placed sapling_carrot
[Error  :Crafting with Containers] Invalid state reached! You might want to report this to the mod developer.
When removing 1 of $item_carrotseeds, amount of resources left to remove was still 1
Containers: 0. Players: 1.
Removed 1 "Carrot seeds". Touched 0 inventories
...
[Info   : Unity Log] 03/06/2021 10:39:49: Placed Beech_Sapling
[Error  :Crafting with Containers] Invalid state reached! You might want to report this to the mod developer.
When removing 1 of $item_beechseeds, amount of resources left to remove was still 1
Containers: 0. Players: 1.
Removed 1 "Beech seeds". Touched 0 inventories
Attached please find complete LogOutput.log
LogOutput.log.zip

Hello. Thank you for your report! This is a bug with the error reporting code that reports errors when it only took items from the players inventory and didn't touch any of the tests. The mod (and game) should work perfectly otherwise.
Apart from just seeing the message did you experience any issues?

Yep, just reconfirmed this. Fix already implemented. Will be released in 0.0.8

Actually, yes. My game crashed for the first time, not sure if this is the reason tho. I am attaching my Player.log as well.
One thing I notice here is that the number of reported Players in the message grows from 1 to 4 immediately before the crash and this is single player, not a server:
Containers: 0. Players: 4.
Player.log.zip

The players counter would've been a good indicator. But I just checked and.. well. I did a bad job coding the player indicator. It searches for "Character"s, but all animals are also considered a character... So while that indicator is not "wrong" per se, the label is. It's actually showing the amount of all character-like entities around. I fixed the indicator going forward, but this doesn't really help us with your crash...
As for this crash, you are running with Vulkan on Linux. I myself have had some issues from time to time with some Unity games on my Ubuntu setup, including crashes.
Valheim also seems crashy in general. I checked the Player.log you provided for more details, and while my knowledge of the inner workings of Unity, Linux, and Vulkan are nowhere near enough to properly assess this, my best guess is that's it has something to do with the Vulkan implementation on Linux.
At this point I don't think this is related to Crafting With Containers or other mods (unless they do some gpu-level stuff via native libraries).
I will release a new version that fixes the false positives in the console output, so thank you for alerting me on this. I will close this ticket once the logging issues are released.

False positive error messages fixed in 1.0.8. Closing issue.
If you still encounter crashes and still suspect Crafting with Containers, please reopen!


Refactor is_project_func method for Windows compatibility

The previous implementation of the is_project_func method had issues related to path handling on Windows systems, potentially leading to incorrect identification of project code.
Changes made:

Utilized os.path.normpath() for path normalization.
Modified file path comparison to correctly identify project code.
Implemented exclusion of 'site-packages' and 'dist-packages' directories.

Fixes: #1836

@DraKen0009 do you have a test that confirms that this fixes the problem on windows? I doubt we'll run it in CI, but it'll make me feel better if there were a test along with this.

@tim-schilling  ,  I haven't created tests yet , but I can create a simple unit test for it, can you guide me where in project directory do I need to create it ?

It probably belongs in the test file for the profile panel. If you look at the tests directory, there should be a panels directory with files for each of the panels.

@DraKen0009 is there any option to continue using pathlib?

Tests pass and the implementation is strictly superior to the current one. I have removed the pathlib flake8 rules from my own projects since it's annoying and using pathlib isn't always better.
Thanks!


#7 dependencies update

Closes #7
Snyk report updates for dependencies

Hey @florentinvintila there are some pretty major version bumps on the dependencies. Has this been tested?

Hey @florentinvintila there are some pretty major version bumps on the dependencies. Has this been tested?

Hi Tyson, all of these are devDependecies

Even if they are bigger I don't see the impact for the library. Mostly of them are lints, testing frameworks and so on, I would considere this to be a better option rather than keeping them old. Dev should be up to date.


Fixes MSAL/#915

Issue:
https://github.com/AzureAD/microsoft-authentication-library-for-android/issues/915
Expands:
https://github.com/AzureAD/microsoft-authentication-library-common-for-android/pull/807
Summary:
Conditionally perform AccountRecord lookup from cache by home_account_id if B2C == Authority.type

Looks good to me!

lgtm. we'll need to merge this to dev as well.

Thanks @rpdome , PR is open here: #812


Add sample recipes to customize openssl package

Purpose of pull request
This commit adds sample recipes to customize openssl package.

@Yoshihiro-Okada-ML Could you change filenames of *.bb to *.bb.sample?

I think it would be nice to simply describe what openssl-apt and openssl-http are in the README.md.

Add short description for sample recipes.

Thanks!


partition_ppt parsing the ppt, the content is empty

When I use partition_ppt parsing the ppt file, the content cannot be parsed and the result is empty
[Document(page_content='', metadata={'source': '[./CV_Cheng](https://file+.vscode-resource.vscode-cdn.net/c%3A/code/parseppt/CV_Cheng) Binkui.pptx'})]

@chen-lee-li - We haven't been able to reproduce this error. Are you able to provide an example that reproduces it?

Closing this one because we weren't able to replicate. We can reopen it if someone provides an example or reproducible code snippet we can use for testing.


Replace 'Maybe Bool'  with a dedicated sum-type.

Issue Number

#1701
Overview

9aaf4ad62c6b5982ef381073f84f2b76d5251f2f
:round_pushpin: log when no migration is needed

7c3d459adfbd86353bd84b31f8d9220bd9c9532f
:round_pushpin: replace 'Maybe Bool' with a dedicated sum-type for more clarity

Comments

Caught me one time already... Won't caught anyone else.

Unfortunately I still see behavior as in: https://github.com/input-output-hk/cardano-wallet/issues/1552
To reproduce:

Launch server using cardano-wallet v2020-03-16

cd lib/jormungandr/test/data/jormungandr/test_scripts
./wallet_launch.sh

Create a wallet (e.g. faucet shelley wallet from integration tests: absurd seat ball together donate bulk sustain loop convince capital peanut mutual notice improve jewel)
Stop wallet and start wallet  with version from this branch
Submit transaction from that wallet
Result:

Code = 403,
Message = {"code":"no_root_key","message":"I couldn't find a root private key for the given wallet: f425f750be117385fb7c4280dee5cf9be2f0e71c. However, this operation requires that I do have such a key. Either there's no such wallet, or I don't fully own it."}

What is interesting that after point 4 (from the above) when you restart wallet again (using the same version) you are able to send transaction... :thinking:

@piotr-iohk My guess here is that, when you first restart it, the automatic migration hasn't happened yet, so the column doesn't yet exists and can't be populated (so, running into the bug as before). Manual migrations are ran BEFORE automatic migration. which is, somewhat necessary for the active slot coeff as it requires to alter the tables before attempting an automatic migration, but problematic for this one which requires the passphrase_scheme to be set :| ...
We could "force-create" the column if it doesn't exist. It won't hurt and we are sure it's there.

bors r+


[WIP] A few improvements to the redesign

Removed the link entirely & replaced with a button, thanks though!


Index filters visible in ModelViewSet history view

Issue Summary
The index filters are visible in a ModelViewSet's history. It might be in other mixin views, this was just the one I noticed. They don't do anything when clicked except update the url

Steps to Reproduce
# models.py
from wagtail.models import RevisionMixin

class Product(RevisionMixin):
    name = models.CharField(max_length=255)
    in_stock = models.BooleanField()

    panels = [
        FieldPanel('name'),
        FieldPanel('in_stock')
    ]

 # wagtail_hooks.py
 from wagtail.admin.viewsets.model import ModelViewSet
 from .models import Product

 class ProductViewSet(ModelViewSet):
    model = Product
    list_filter = ('in_stock',)

# register viewset via the hook

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: no

Technical details

Python version: 3.11
Django version: 4.2
Wagtail version: 6.0.1

Thanks for the report, but I wasn't able to replicate this with a fresh Wagtail project and the given model and the following viewset registered:
from wagtail import hooks
from wagtail.admin.viewsets.model import ModelViewSet
from .models import Product

class ProductViewSet(ModelViewSet):
    model = Product
    list_filter = ("in_stock",)
    add_to_admin_menu = True
    icon = "pick"

# register viewset via the hook
@hooks.register("register_admin_viewset")
def register_product_viewset():
    return ProductViewSet("products")

The history view shows the filters for the log actions and can be used to filter the listing:

If you encounter this issue, perhaps check whether you pass the viewset's list_filter to the history view, e.g. via get_history_view_kwargs, get_common_view_kwargs, or the history_view property. Passing a list_filter to the HistoryView could give you unexpected behaviour.

ah my mistake, I didn't realise these filters were for filtering the history view and got a bit mixed up. I'll close this


where is the generated export

Hello, where is the output stored? (foundryvtt version 12_327)

Hello, without error a pop up should appeared to select the location. If there is an error could you show the console error with F12 .

Close because I ve got no answer.


net/http/httputil: handle escaped paths in SingleHostReverseProxy

When forwarding a request, a SingleHostReverseProxy appends the
request's path to the target URL's path. However, if certain path
elements are encoded, (such as %2F for slash in either the request or
target path), simply joining the URL.Path elements is not sufficient,
since the field holds the decoded path.
Since 87a605, the RawPath field was added which holds a decoding
hint for the URL. When joining URL paths, this decoding hint needs
to be taken into consideration.
As an example, if the target URL.Path is /a/b, and URL.RawPath
is /a%2Fb, joining the path with /c should result in /a/b/c
in URL.Path, and /a%2Fb/c in RawPath.
The added joinURLPath function combines the two URL's Paths,
while taking into account escaping, and replaces the previously used
singleJoiningSlash in NewSingleHostReverseProxy.
Fixes #35908

@googlebot I signed it!

Hi, just wanted to check on this PR, and make sure it isn't lost in the current chaos. I have implemented the requested modifications - please let me know if there is anything more I can do to help in fixing the issue!


Update README.md

Run spellcheck.

Thanks for checking. And sorry for delay 😔

Never a rush.  I hope you have more important things to do!
On Sun, Apr 9, 2023, 12:13 PM Alex Kozack @.***> wrote:

Thanks for checking. And sorry for delay 😔
—
Reply to this email directly, view it on GitHub
https://github.com/cawa-93/unplugin-auto-expose/pull/10#issuecomment-1501173284,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXESHTQAXENJ2OPJXMK2Z5TXALU3LANCNFSM6AAAAAAWXFY57M
.
You are receiving this because you authored the thread.Message ID:
@.***>


compress generated pdf

I think it would be good if the riscv adoc documents were as small as the latex ones.
Especially considering the fact that I often approach github repos/releases that download at less than 500kbps.
Currently the adoc unpriv is 8x the size of the latex one.
There is a simple -a compress command to put in a makefile, which in my case, yielded 314KiB document out of 1.2MiB. Didn't visibly affect build time.
There are also some external tools that claim to strip more.

@wmat any suggestion here? We are using the compress instruction already.

I am looking into optimizing the output.  There is asciidoctor-pdf
extensions such as
https://docs.asciidoctor.org/pdf-converter/latest/optimize-pdf/ that can be
used.  We'll test this out and see how effective it is.
On Thu, Apr 27, 2023 at 5:27 PM Rafael Sene @.***>
wrote:

@wmat https://github.com/wmat any suggestion here? We are using the
compress instruction already.
—
Reply to this email directly, view it on GitHub
https://github.com/riscv/docs-spec-template/issues/9#issuecomment-1526513723,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAN6ZBZFY6XNCGLQORUMETXDLQFNANCNFSM6AAAAAAUJXEBLM
.
You are receiving this because you were mentioned.Message ID:
@.***>

The asciidoc compression parameter is already in place https://github.com/riscv/docs-spec-template/blob/main/Makefile#L26.


Docs: fix links to methods with String default values

The double-quotes value in the id need to be escaped with " in order to work.
For example https://crystal-lang.org/api/0.34.0/Path.html#new(name:String=""):Path-class-method is not working without this PR.

Fixes #8809.

Wait, why is there any JS  for this? Browsers should support scrolling to an element with the right id natively, as long as we keep consistency in generating links and id= tags, it should just work, no?

I would expect that also @jhass . I'm not sure how what other JS are required in the documentation html to expand/hightlight methods.
Maybe @straight-shoota is more aware.

Seems like this was introduced in #3623 to fix an issue with scroll position being reset when reloading the page. Affecting every fragment link action seems quite intrusive, though.
/cc @Sija

I actually can't notice any difference in the user experience when this method is removed. #3623 lacks a detailled explanation what exactly goes wrong, so I might be missing something.

@straight-shoota That was ~3,5yrs ago, I lot could have changed since then (and did), so I'd suggest trying out whether this workaround is still needed and applicable these days.

Yeah, but I'm not even sure what exactly this workaround fixed. Can you recall any specific behaviour we can test?

@straight-shoota It was related to scrolling - as mentioned in the original PR - this should be enough to  let you test it - both ff and chrome woud be needed as their behavior differs in such matters.

Okay so I found the faulty behaviour. When you reload the page in Chrome it always scrolls the main content pane to the top, even if the URL points to an anchor. This seems to be related to the script responsible for the sidebar to scroll the currently selected entry into view. That should just affect the sidebar. But Chrome seems to disagree.
But the fix to this problem should be simpler than what we currently do.
var elem = document.getElementById(window.location.hash.substr(1))
if (elem) elem.scrollIntoView();

This only needs to be executed once, not on every hashchange event. Klicking anchor links on the page should not be affected. It's only relevant when the page is loaded.

It seems unrelated to this change then.
For ids with quotes  the following is still needed:
document.getElementById(unescape(window.location.hash.substr(1)).replace(/"/g, '"'))

Another approach would be to use safe chars for ids.
Either way, a story for another PR it seems.

No, this is the wrong change. It just fixes a symptom in our JavaScript code. Instead we should fix the cause, that is the anchor names and link targets must work even when special characters are involved.

It's not even enough because there are other characters that cause issues (for example |).
This is the fragment for File.open that Firefox produces when clicking on the link in the constructors section:
#open(filename:Path%7CString,mode="r",perm=DEFAULT_CREATE_PERMISSIONS,encoding=nil,invalid=nil):self-class-method

This fragment actually works
#open(filename:Path|String,mode="r",perm=DEFAULT_CREATE_PERMISSIONS,encoding=nil,invalid=nil):self-class-method

But is wrong because we are mixing how " need to be escaped in uri and html.
The ideal is to use safe chars for ids.

The ideal is to use safe chars for ids.

Maybe. But the characters arenot really the problem. They actually work fine:
goto
target

So the error is on our side how we process the anchor values. For example, id values must not be URI escaped.

Ok, drilled down a little bit, the issue was that the arguments are escaped twice.
I removed the query selector in favor of getElementById
I removed the hashchange event
But I didn't add the scrollIntoView because the note at https://caniuse.com/#search=scrollIntoView

I removed the hashchange event

Did you tested did the current version works with the Back browser button - i.e. correctly scrolls to the given id?

Now I did @Sija . Thanks 🙈

We need to make add a comment to explain why this code is there and how it works.

We need to make add a comment to explain why this code is there and how it works.

Definitely, but I only know that is need. I haven't tracked why/how it works.


With no consent for data sharing and exception-reporting & metrics packages disabled, Atom still appears to contact some internet service in case of an error

Prerequisites

[ ] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
With no consent for data sharing and exception-reporting & metrics packages disabled, Atom still appears to contact some internet service in case of an error.
Because this is a one time error incident, I haven't tested this in safe mode.
What did I do to prevent data collection:
I disabled the exception-reporting and metrics package (before this incident occurred, and they are still disabled).
Additionally, in the initial new launch dialog which asks for data sharing consent, I haven't clicked yes on all of my machines, although I'm not sure if on this machine where I just ran into this I had Atom already installed before that dialog was introduced. (so I might not have said no on that dialog)
How was the internet service connected
I got an exception, and it clearly refers to an issue on github which was already reported. I didn't click anything to make this happen, and still it clearly connected to some service to get this sort of information:

Steps to Reproduce
Since this is a one time incident for me, I'm not perfectly sure. It might be enough to just observe some exception.
Expected behavior: With exception-reporting and metrics disabled and no consent given for data collection, no internet service should be consulted ever without user interaction (package install, explicit query for error details, ..)
Actual behavior: Some online service appears to be consulted
Reproduces how often: unknown
Versions
jonas@cyberman:~$ atom --version
Atom    : 1.12.7
Electron: 1.3.13
Chrome  : 52.0.2743.82
Node    : 6.5.0
jonas@cyberman:~$ apm --version
apm  1.12.9
npm  3.10.5
node 4.4.5
python 2.7.12
git 2.9.3
jonas@cyberman:~$

Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.

How this works is it connects directly to GitHub and looks to see if there's already an issue open with the exception message.  If there isn't, it then offers you the option to create an issue on GitHub by going through is.gd (a URL-shortening service due to numerous problems with opening long URLs).
I believe that this was not covered by the metrics consent screen because you are explicitly in control of whether you want to file an issue or not.  That being said, this is otherwise a duplicate of https://github.com/atom/notifications/issues/144, so feel free to subscribe there for updates.

I believe that this was not covered by the metrics consent screen because you are explicitly in control of whether you want to file an issue or not.

I believe this is a mistake because GitHub appears to be immediately contacted to check if there is already an issue reported on the error. Therefore, clearly this should be covered by the initial metrics consent screen. If no metrics and exceptions reporting consent was given, the notifications dialog should ask first whether it should contact GitHub, instead of doing it automatically as of now.


[react-form] Remove useMountedRef check in useSubmit

Description
Fixes #2500 and #2508 - maybe more things related to useSubmit
I believe the early exit inside submit is being triggered unwantingly in Next.js environments. This is a fix for that, but I'm not sure if it is then a regression for other scenarios.

@jokull, are you able to produce a test case that fails without this change but passes with the change? I am wary of merging this change without proof that it fixes an issue and doesn't produce regressions in react 17.

This is no longer needed in Next 13.2.

You can try it on vite + react fresh setup, it's still a problem.

strict mode is breaking it!


Remove REST endpoints from the reward module's tx.proto.

Description
closes: #1077
Remove the REST endpoint definitions from the reward module's tx.proto.
None of the other tx.proto files have them (in our stuff and the Cosmos-SDK). And they aren't actually usable. All of my attempts to use them (through the swagger UI) resulted in a resource not found. So whatever automatically makes them wasn't actually making them. And even if they were wired up, I'm not even sure how it would work when it comes to fees and signatures and stuff not contained in the Msg protos.

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

I think the query.proto rest endpoints are used by the GRPC gateway that auto generates the REST endpoints...

Should these endpoints also be removed from query.proto?

We want the query.proto ones as they get automatically wired up and allow querying through REST. But the tx.proto ones don't work because of the extra things you need in order to run a TX.
With a Tx, you need the request message to be placed in a tx message with a few other details filled in (e.g. signature and fees). You can't just send one of the tx.proto request messages by itself like you can with the query.proto request messages.
Plus, it looks like the SDK doesn't automatically wire those endpoints into the api like it does with the query.proto ones. For example, posting to http://localhost:1317/provenance/reward/v1/reward_programs, I get a 501 Not Implemented with {"code": 12,"message": "Not Implemented","details": []}:
> curl --verbose http://localhost:1317/provenance/reward/v1/reward_programs --header 'accept: application/json' --data '{"title":"Program Title","description":"A short description","distribute_from_address":"tp1dcak3vsy5rteuh6lh2v0q9sf7wzlspn2klmujf","total_reward_pool":{"denom":"nhash","amount":"580"},"max_reward_per_claim_address":{"denom":"nhash","amount":"10"},"program_start_time":"2022-10-10T00:00:00Z","claim_periods":"52","claim_period_days":"7","max_rollover_claim_periods":"4","expire_days":"14","qualifying_actions":{"delegate":{"minimum_actions":"0","maximum_actions":"1","minimum_delegation_amount":{"denom":"nhash","amount":"0"},"maximum_delegation_amount":{"denom":"nhash","amount":"100"},"minimum_active_stake_percentile":"0.000000000000000000","maximum_active_stake_percentile":"1.000000000000000000"}}}'
*   Trying <IP_ADDRESS>:1317...
* Connected to localhost (<IP_ADDRESS>) port 1317 (#0)
> POST /provenance/reward/v1/reward_programs HTTP/1.1
> Host: localhost:1317
> User-Agent: curl/7.79.1
> accept: application/json
> Content-Length: 702
> Content-Type: application/x-www-form-urlencoded
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 501 Not Implemented
< Content-Type: application/json
< X-Server-Time:<PHONE_NUMBER>
< Date: Tue, 27 Sep 2022 16:43:25 GMT
< Content-Length: 68
<
{
  "code": 12,
  "message": "Not Implemented",
  "details": [
  ]
* Connection #0 to host localhost left intact
}


Default Scopes

Is it right to say that "Rails 3.2 onwards, the last designated default scope overrides any prior scopes and will invalidate multi-tenanting"? Rails docs says "If you use multiple default_scope declarations in your model then they will be merged together". I tested it myself:
class Article < ActiveRecord::Base
  acts_as_tenant
  default_scope {
    where("created_at > '2015-01-01'")
  }
end

Console:
Tenant.set_current_tenant(1)
Article.all
SELECT "articles".* FROM "articles" WHERE (articles.tenant_id = 1) AND (created_at > '2015-01-01')

My understanding is that the last-used default_scope overrides anything
else. Milia won't work in those situations.
On Wed Feb 11 2015 at 11:07:18 AM JP Barbosa<EMAIL_ADDRESS>wrote:

Is it right to say that "Rails 3.2 onwards, the last designated default
scope overrides any prior scopes and will invalidate multi-tenanting"?
Rails docs says "If you use multiple default_scope declarations in your
model then they will be merged together". I tested it myself:
class Article < ActiveRecord::Base
acts_as_tenant
default_scope {
where("created_at > '2015-01-01'")
}
end
Console:
Tenant.set_current_tenant(1)
Article.all
SELECT "articles".* FROM "articles" WHERE (articles.tenant_id = 1) AND (created_at > '2015-01-01')
—
Reply to this email directly or view it on GitHub
https://github.com/dsaronin/milia/issues/49.

I agree with @jp7jp.
From http://api.rubyonrails.org/classes/ActiveRecord/Scoping/Default/ClassMethods.html#method-i-default_scope:

If you use multiple default_scope declarations in your model then they will be merged together. This is also the case with inheritance and module includes where the parent or module defines a default_scope and the child or including class defines a second one.

We should prove this with some scoping tests and remove the according warning from the Readme.

Added according info on default_scopes to https://github.com/jekuno/milia/blob/rails5-support/README.md


How can I set the Developer menu to open devTools?

I can open it from the right-click menu with "Inspect Element", but it's inconvenient, I want to open the console directly to see the logs. The shortcut cmd+opt+I doesn't work either. How do I set up a menu or set up a shortcut?
Browser console logs, is it possible to print them to the command line console ?
I tried the following code but it doesn't work.
ApplicationMenu.setApplicationMenu([

  {
    label: "Developer",
    submenu: [
      {
        label: "Toggle Developer Tools",
        role: "toggleDevTools"
        accelerator: process.platform === "darwin" ? "Cmd+Alt+I" : "Ctrl+Shift+I",
      },
    ],
  },
]);

Adding the cmd+opt+i shortcut is on my todo list. Let's keep this issue open to track that.
As far as I can tell there's no default role that macos automatically wires up, that's a Safari behaviour but not a WKWebkit feature. Especially since technically an application menu can be shown for an application with multiple Webviews.
So I believe this is functionality I need to add into electrobun's objc code to support it.
I'd want to:

support keyboard shortcut to open devtools for the current window's main webview
add a property in BrowserView({ showDevtoolsOnStartup: true }) so you can automatically open it as soon as the window's BrowserView initializes

I'm actually not sure that WKWebkit has a programmatic way (in objc or otherwise) to launch devtools.
So this might only be something we can enable in the future when we add the option to bundle a webview (like chromium) with your electrobun app or maybe when we support window's development since the system webview on windows is Edge which is chromium based and I think has an api to open devTools programmatically.


factor: Fix withLibs wrapper

Description of changes
The withLibs Attribute was broken due to changes in how if ... then ... else ... expressions are evaluated and due to trying to wrap a missing binary.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3262


Please update https://www.kubeflow.org/docs/gke/private-clusters/

I tried to deploy KF to private-cluster as the document says.
But I got errors when deploying after remove kustomizeConfig cert-manager, cert-manager-crds and cert-manager-kube-system-resources.
Besides, there is no file called iap-ingress.yaml to set privateGKECluster !!
I found this privateGKECluster from manifestes repo, in a params.env of folder /gcp/basic-auth-ingress/base/params.env
But I cannot find anywhere it is used, it seems that it is just created in configMap but not used anywhere. Please correct me if I am wrong.

@rduan Thank you for reporting this issue. We have a P1 issue (https://github.com/kubeflow/website/issues/1705) to update the doc for private clusters and VPC service controls.
@zhenghuiwang Do you have an input on this specific question from @rduan?

I found this privateGKECluster from manifestes repo, in a params.env of folder /gcp/basic-auth-ingress/base/params.env
But I cannot find anywhere it is used, it seems that it is just created in configMap but not used anywhere. Please correct me if I am wrong.

But I got errors when deploying after remove kustomizeConfig cert-manager, cert-manager-crds and cert-manager-kube-system-resources.

Can you paste the error message? thanks
(I think the error is related to KFServing, but want to confirm it. If that's the case, you may have to remove it similarly to removing cert-manager)

I found this privateGKECluster from manifestes repo, in a params.env of folder /gcp/basic-auth-ingress/base/params.env
But I cannot find anywhere it is used, it seems that it is just created in configMap but not used anywhere. Please correct me if I am wrong.

Seems you are deploying with basic auth. I would recommend deploying kubeflow with IAP setting (step 7 in https://www.kubeflow.org/docs/gke/deploy/deploy-cli/)
/cc @kunmingg @abhi-g

Hi Zhenghui,
Thanks for your reply.
I got errors as below when I was doing setp 7:

Remove components which are not useful in private clusters:
Open ${KF_DIR}/kfctl_gcp_iap.v1.0.0.yaml and remove kustomizeConfig
cert-manager, cert-manager-crds, and cert-manager-kube-system-resources. 1.
Create the deployment:
cd ${KF_DIR}
kfctl apply -V -f ${CONFIG_FILE}
BTW, there is no statement about $CONFIG_FILE, I assume it is the changed
kfctl_gcp_iap.v1.0.0.yaml file.
[image: WeChat Image_20200317083657.png]
In the document , after step 7, there is

Update iap-ingress component parameters:
cd ${KF_DIR}/kustomize
gvim iap-ingress.yaml

  Find and set the privateGKECluster parameter to true:

  privateGKECluster: "true"

  -

  Then apply your changes:

  kubectl apply -f iap-ingress.yaml

I could not find iap-ingress.yaml file in the kustomize folder. Not sure
where to change privateGKECluster to true.
Cheers,
Richard Duan
On Tue, 17 Mar 2020 at 05:41, Zhenghui Wang<EMAIL_ADDRESS>wrote:

But I got errors when deploying after remove kustomizeConfig cert-manager,
cert-manager-crds and cert-manager-kube-system-resources.
Can you paste the error message? thanks
(I think the error is related to KFServing, but want to confirm it. If
that's the case, you may have to remove it similarly to removing
cert-manager)
I found this privateGKECluster from manifestes repo, in a params.env of
folder /gcp/basic-auth-ingress/base/params.env
But I cannot find anywhere it is used, it seems that it is just created in
configMap but not used anywhere. Please correct me if I am wrong.
Seems you are deploying with basic auth. I would recommend deploying
kubeflow with IAP setting (step 7 in
https://www.kubeflow.org/docs/gke/deploy/deploy-cli/)
/cc @kunmingg https://github.com/kunmingg @abhi-g
https://github.com/abhi-g
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubeflow/website/issues/1811#issuecomment-599699613,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD2SEPKGLCRRHLGNC53R7KLRHZXDZANCNFSM4LLP42SA
.

I had an issue with CloudEndpoint deploying correctly on privateGKE with IAP_v1.0.0 (the controller would set up but then no endpoint would be set up)- is this not the general experience? To remedy, we removed the cloud endpoint controller from KustomizeConfig, set an endpoint using gcloud endpoints services deploy openapi.yaml then used this as the host name in iap-ingess/base/params.env. Not sure if that's helpful?

Hi Joepeskett,
I am not very understanding your points because I just started to
use/deploy kubeflow.
The thing I noticed is that  "privateGKECluster=false" was defined in
params.env , but I cannot find this parameter is used anywhere.
Could you tell me how this parameter is used when deploying KF?
Thanks,
Richard
On Tue, 17 Mar 2020 at 09:09, joepeskett<EMAIL_ADDRESS>wrote:

I had an issue with CloudEndpoint deploying correctly on privateGKE with
IAP_v1.0.0 (the controller would set up but then no endpoint would be set
up)- is this not the general experience? To remedy, we removed the cloud
endpoint controller from KustomizeConfig, set an endpoint using gcloud
endpoints services deploy openapi.yaml then used this as the host name in
iap-ingess/base/params.env. Not sure if that's helpful?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubeflow/website/issues/1811#issuecomment-599780085,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD2SEPPAMDSHDEOTZPKRIVDRH2PQXANCNFSM4LLP42SA
.

/area gcp
/area docs
/kind bug
/priority p1

/platform gcp

The steps to modify the IAP ingress and the certificate should no longer be needed because we are using GKE managed certificates.


MYSQL_PASS_STR erroneous

Connection to mysql database not possible, but when changing the MYSQL_PASS_STR from
        [[ ( -n "${DB_PASS}" ) ]] && MYSQL_PASS_STR=" -p'${DBPASS}'"

to
        [[ ( -n "${DB_PASS}" ) ]] && MYSQL_PASS_STR=" -p${DBPASS}"

all works fine

We recently made a change to wrap them in quotes - By chance does your password contain any special characters in it?

No special characters in my password, only characters and numbers. My feeling is that the functions 'backup_mysql()' and 'check_availability' handle things differently. If I set DB_PASS to "Password", check_availability failed, removing the double quotes then made backup_mysql() fail. Could it be that as it stands, the script for 'mysql' doesn't work whatever password is used?

Thanks. To look into today - I'm not seeing this sort of activity on my end and running a couple dozen of these containers. It's very much possible something has broken when I altered the base images, in some of my other projects quite a few quirks have popped up- Will see what I can find.

See tiredofit/db-backup:1.18.2 for the fix, please confirm we're back on track!

Thanx, I'll do so until tomorrow and give feedback


Enable more assists to generate default trait body impls

Enable more assists to benefit from trait body generation. Follow-up to #9825 and #9814.
edit: I'd like to move the existing tests to this new file too, but I'll do that in a follow-up PR.

bors r+


Google map location sharing TypeError: 'NoneType' object is not subscriptable

Home Assistant release with the issue:
0.80.0
Last working Home Assistant release (if known):
0.73.3
Operating environment (Hass.io/Docker/Windows/etc.):
Hassbian
Component/platform:
https://www.home-assistant.io/components/device_tracker.google_maps/
Description of problem:
Error only when the device is charging
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
- platform: google_maps
  username: !secret ga_loc_user
  password: !secret ga_loc_pass

Traceback (if applicable):
2018-10-14 06:02:47 ERROR (MainThread) [homeassistant.components.device_tracker] Error setting up platform google_maps
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.5/site-packages/locationsharinglib/locationsharinglib.py", line 109, in _populate
    self._charging = data[13][0]
TypeError: 'NoneType' object is not subscriptable

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/device_tracker/__init__.py", line 184, in async_setup_platform
    disc_info)
  File "/usr/lib/python3.5/asyncio/futures.py", line 380, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.5/asyncio/tasks.py", line 304, in _wakeup
    future.result()
  File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result
    raise self._exception
  File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/device_tracker/google_maps.py", line 46, in setup_scanner
    scanner = GoogleMapsScanner(hass, config, see)
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/device_tracker/google_maps.py", line 66, in __init__
    self._update_info()
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/device_tracker/google_maps.py", line 78, in _update_info
    for person in self.service.get_all_people():
  File "/srv/homeassistant/lib/python3.5/site-packages/locationsharinglib/locationsharinglib.py", line 459, in get_all_people
    people = self.get_shared_people() + [self.get_authenticated_person()]
  File "/srv/homeassistant/lib/python3.5/site-packages/locationsharinglib/locationsharinglib.py", line 451, in get_authenticated_person
    None,
  File "/srv/homeassistant/lib/python3.5/site-packages/locationsharinglib/locationsharinglib.py", line 95, in __init__
    self._populate(data)
  File "/srv/homeassistant/lib/python3.5/site-packages/locationsharinglib/locationsharinglib.py", line 113, in _populate
    raise InvalidData
locationsharinglib.locationsharinglibexceptions.InvalidData

Additional information:

This is different from https://github.com/home-assistant/home-assistant/issues/17410
I only get error when the device is charging.

Temporary fix
Change google_map.py requirement to REQUIREMENTS = ['locationsharinglib==3.0.6']

3.0.6 is the release which will be shipped with 0.81.


PIA-1595: Integrate purchases for signup tvos

Summary
This PR adds the subscribe functionality for Sign up on tvOS and the sign up email view. It also adds unit tests.
Error handling and strings will be added on a different PR.

Great job @kp-said-rehouni
The tvOS e2e tests are failing in this PR but I am not sure if it is related to some missing stub because of new apis and interfaces introduced in this PR or not

Thank you @kp-laura-sempere! It looks that there are some flaky tests. Now it's passing


Add more Info to Logs "Too many publish request error"

Is your feature request related to a problem? Please describe.
We have configured multiple OPC Servers on the same Publisher module. When a server (or multiple) response "Too many publish request" it is unclear which connection caused it from the logs, for example:
[24-05-22 12:41:18.3553] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaStack[0] Publish #512, Reconnecting=False, Error: BadTooManyPublishRequests
Describe the solution you'd like
Add more information to the logs like the subscription id or connection endpoint, for example
[24-05-22 12:41:18.3553] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaStack[0] Publish #512, Reconnecting=False, Error: BadTooManyPublishRequests, SubscriptionId: XYZ
Describe alternatives you've considered
Have a separate module with only one connection configured to troubleshoot which connection causes the issue
Additional context
None

That would be totally fine as well. as long as we can assign it to one connection we would be more than happy!

I added the client session name to every client log message and also log all publish errors with the session name.

Just tested it and works fine, thank you very much for the quick implementation!


LFS parallel transfers for git read-tree

I'm using the sparse-checkout trick to selectively download files from an LFS-enabled repo. It boils down to:
# No files for you
git clone --no-checkout

# Prep list of files
git config --local core.sparsecheckout true
echo '*!' > .git/info/sparse-checkout
echo '.gitattributes' >> .git/info/sparse-checkout
echo 'file1' >> .git/info/sparse-checkout
...
echo 'fileX' >> .git/info/sparse-checkout

# Go go go!
git read-tree -mu HEAD

This causes all files to be downloaded sequentially by LFS. No amount of -c lfs.concurrenttransfers=10 added to git read-tree helps.
Is this somewhere on the roadmap?
Thanks,
Clément

Untested, but this could work:
git -c filter.lfs.smudge=cat read-tree -mu HEAD
git-lfs pull

Alternatively try:
git lfs clone

git lfs clone won't work since it will download the whole repository.
I also tried your first suggestion @larsxschneider, but LFS will download all the files in the archive (same things that git lfs clone does).
I'm open to suggestions.
Thanks,
Clément

@woopla look at the include/exclude options for the git lfs pull command. Building off of @larsxschneider's suggestion:
git -c filter.lfs.smudge=cat read-tree -mu HEAD
git-lfs pull -I file1


Projects/Dynamic js Quiz

Is your feature request related to a problem? Please describe.
We can make it more dynamic by API integration that sends 10 random questions so a person cannot just read the answers from javascript file. we can also make it such that if a person leaves the screen for more than 5 seconds then the document will automatically submitted.
Describe the solution you'd like
Using an API "https://the-trivia-api.com/" we can make it more dynamic and use javascript to make it difficult to cheat making it a nearly perfect quiz app.
Describe alternatives you've considered

API integration: https://the-trivia-api.com which makes the site more dynamic.
feature which doesn't allow the person handling quiz to leave the screen for more than 5 seconds.

great idea dude 👍


Instagram # number to join Threads

Instagram has started to put a badge on user profiles that indicates the ‘n-th’ user to make that Threads.net account. Is there a way to access this through the API.

Looks like this comes from instagram api's /users/<id>/info in the app in a property called text_post_app_joiner_number. Full request example here: https://pastebin.com/2Z7wrHBz if anyone wants to try it out and/or take on the work. I'll be out of commission until Monday
This call returns a ton of data -- email, phone number, whatsapp number, on & on -- I assume the user has made it all public though... Just the typing for this response object is ~300 lines of code 😅
I guess we could have a getUserProfileLoggedIn or something that makes this call instead of the gql which just gives back basic data u see on the unauthenticated website...

If anyone wants to try it out and/or take on the work. I'll be out of commission until Monday

Woah, I owe you this — as also a dev I would really love this fetcher going live. Will be happy to work on this!

I guess we could have a getUserProfileLoggedIn or something that makes this call instead of the gql which just gives back basic data u see on the unauthenticated website...

Yup it's also reasonable 👍


math/big: optimize amd64 asm shlVU and shrVU for shift==0 case

When shift == 0, shlVU and shrVU reduce to a memcopy. When z.ptr == x.ptr, it further reduces to a no-op. The pure Go implementation has these optimizations, as of https://go-review.googlesource.com/c/go/+/164967. The arm64 implementation has one of them (see https://github.com/golang/go/issues/31084#issuecomment-477406354). We should add both to the amd64 implementation.
cc @griesemer

Can this be done in the wrappers/callers instead so the per-arch assembler as well as the generic can just assume that this optimization has been applied?
This also allows SSA to see where these conditions might be constant either now or in the future.

Good question. As of this moment there aren’t any pure go wrappers for these functions—they all go straight to the assembly implementations. Now that we have mid-stack inlining, it might make sense to change that, and do optimizations like this in the wrappers, so they can skip the call entirely. Want to experiment and send a CL for 1.16 if appropriate?


Prepare support for Debian 11 (Bullseye)

Debian 11 (codename bullseye) is in the final stages of development and will be released quite soon.
The only "glaring" issue in here is that they're moving the PHP version to 7.4 (same as Ubuntu 20.04), but that shouldn't be too much of an issue.
The goal is to start working on adding support for it as soon as it is released. Debian 10 (buster) should remain supported for the near future, ideally until it gets obsolete.

Tentative release date is set to 31st July 2021 at the time I wrote this.

Debian 11 was released today Integration work is being done in #25 and a compatible release should be coming hopefully in the next week.

try to run the setup...

This script must be run on a system running Debian 10 OR Ubuntu 20.04 LTS.
when will you release ?

I don't really have a release schedule here as the plan is to merge everything when Josh decides to release v0.55
That way I can just ship all the new features at once 😄


lets-plot-batik: META-INF/services files specify xalan

Apologies if this is not the right place to report issues in lets-plot-batik.
The lets-plot-batik jar has META-INF/services files for javax.xml, org.apache.xml and org.apache.xalan that refer to xalan classes.
xalan has an open CVE that is not likely to be fixed and the community is mulling shutting down the project. There has only been one xalan-j release since 2008.
Would it be possible to remove these refs to xalan?

https://lists.apache.org/thread/s8kjny5270ssfcp46v0fl39lk98987w7
https://lists.apache.org/thread/2qvl7r43wb4t8p9dd9om1bnkssk07sn8

Sure, we will take a look.

However, org.apache.xmlgraphics:batik-dom:1.14 has dependency on xalan:xalan:2.7.2 artefact so, we likely will not be able to get rid  of xalan entirely.

https://issues.apache.org/jira/browse/BATIK-1329 is open.
Still, it would be useful if lets-plot-batik did not set the META-INF/services settings - because they affect all code that runs in a JVM. If lets-plot-batik really needs to use xalan, as opposed to the Java runtime JAXP built-ins or saxon, it could create the xalan factories explicitly.

A merge has been done for https://issues.apache.org/jira/browse/BATIK-1329 - I'm not sure when a release will be done.


Apimap Plugin

Repository URL
https://github.com/apimap/plugin-jenkins
New Repository Name
apimap-plugin
Description
Why is this project useful? Lost track of all the API functionality provided inside your organization? Don't want to be tied to an API proxy or management solution? The Apimap.io project uploads, indexes and enables discoverability of all your organizations APIs. We care about the source code, removing the limitation of where the API is hosted and how your network is constructed.
GitHub users to have commit permission
@msulland
Jenkins project users to have release permission
msulland
Issue tracker
GitHub issues

/hosting re-check

Superficial security audit:

doTestConnection must be protected, missing CSRF and missing permission check. Recommended documentation: https://www.jenkins.io/doc/developer/security/form-validation/
I imagine that the token is something confidential, so PublishStep/config.jelly#L10 should be changed to f:password and PublishStep.java#L47 from String to hudson.util.Secret. Recommended documentation: https://www.jenkins.io/doc/developer/security/secrets/

@Wadeck ?

@Wadeck I have added a check to enable the feature only for administrators, and added a short test to see if the user has any arguments in the URL (just to help people to use only the root resource). Does this help?

@msulland the permission check is good, thanks. Now the method is still vulnerable to CSRF, you have to add the @RequirePOST or @POST annotation, and ensure the related UI is sending POST requests.
Related documentation: https://www.jenkins.io/doc/developer/security/form-validation/#protecting-from-csrf

@Wadeck Added @POST

If everything reported was changed 👍

@Wadeck I deleted the test button instead. Just removed the functionallity

@Wadeck to confirm you're happy?

@timja Exactly 👍

/hosting re-check

/hosting host


url patterns are not entirely consistent between webserver and proxy modes

e.g:
Actual endpoint - http://REALHOST:REALPORT/user/data/{userid}
We have captured the req by setting  the proxy. (localhost:8500)
Then we start the server as ./hoverfly -webserver
Set the response delay as below:
 curl -H "Content-Type application/json" -X PUT -d '{"data":[{"urlPattern":"localhost\\:8500","delay":1000}]}' http://${HOVERFLY_HOST}:8888/api/delays

Now when i ran the req http://localhost:8500/user/data/{userid} the response delay is not working.

Hey @agnibrata,
Thank you for raising this. Using your example and a sample data set I had, I was able to recreate the issue. Response delays work slightly differently depending on how you run Hoverfly.
In proxy mode, a delay will match against a string combination of the host and the path. In web server mode, it is just the path.
To get delays working with Hoverfly running as a web server, you can only match on the path, ignoring the destination. This is something that isn't well documented.
To match any request and add a delay:
{
	"data": [{
		"urlPattern": ".",
		"delay": 20000
	}]
}

To match a specific endpoint:
{
	"data": [{
		"urlPattern": "/api/endpoint",
		"delay": 20000
	}]
}

My thinking is that regardless if Hoverfly is running as a proxy or a web server, matching should still be available on both host and path. The way I am thinking of doing this is making sure the host is always set.
In web server mode, I am unsure what the host should be. Should the host be "localhost" or the name of the original host?
Using localhost means that any delays written for Hoverfly will only work when running as a web server, unless the original request response was recorded as being from localhost. Using the original host name means that you could reuse the delay for both proxy and web server, but then in web server mode, you probably wouldn't use that host to access Hoverfly, which might cause confusion.
This issue has brought attention to the fact that the web server mode of Hoverfly does not operate exactly the same as proxy mode and that there are still a lot of unknowns around how it should behave. We would love to hear your thoughts on this.

I understand this is a more general issue of consistency between webserver and proxy mode, so I've changed the title. Please correct if I have misunderstood @benjih

Splitting the urlPattern into hostPattern and pathPattern might be a simple way to fix this problem. In webserver mode, only pathPattern is checked, and the same simulation will work for both proxy or webserver modes.
Another solution is to move the delay settings to the response, and allow granular control of delays using the request matcher.
Either way will be a breaking change and requires a schema upgrade.

We can perhaps avoid breaking the schema by announcing we shall deprecate urlPattern. Let's introduce a distinct replacement (maybe 'fixedDelay' rather than 'delay') and give users a few months minimum to move over to the replacement. Unfortunately I don't think we can justify delaying the 1.0.0 release to do it.

Let's do this with the per-response delays #807

More info about using delay urlPattern for webserver and proxy mode has been added to the doc: https://docs.hoverfly.io/en/latest/pages/tutorials/basic/delays/multiplelocations/multiplelocations.html