lesson 3 poetry Installing training-pipeline (0.1.0): Failed

So I configured pypi credentials:
sudo apt install -y apache2-utils
pip install passlib
mkdir ~/.htpasswd
htpasswd -sc ~/.htpasswd/htpasswd.txt energy-forecasting
poetry config repositories.my-pypi http://localhost
poetry config http-basic.my-pypi energy-forecasting <password>

That gave me this, the password seems missing, but not sure if it is expected here or not:
❯ cat ~/.config/pypoetry/auth.toml
[http-basic.my-pypi]
username = "energy-forecasting"

set up the pypi server separately:
docker run -p 80:8080 -v ~/.htpasswd:/data/.htpasswd pypiserver/pypiserver:latest run -P .htpasswd/htpasswd.txt --overwrite

Built and published in training-pipeline
But poetry install in batch-predictions-pipeline failed:
Using python3 (3.9.10)
Installing dependencies from lock file

Package operations: 1 install, 0 updates, 0 removals

 • Installing training-pipeline (0.1.0): Failed

 RuntimeError

 Retrieved digest for link training_pipeline-0.1.0.tar.gz(md5:ddbaa...) not in poetry.lock metadata {'sha256:acf4ba6c...', 'sha256:b5db651b07...'}

 at ~/.local/share/pypoetry/venv/lib/python3.10/site-packages/poetry/installation/chooser.py:117 in _get_links
     113│
     114│             selected_links.append(link)
     115│
     116│         if links and not selected_links:
   → 117│             raise RuntimeError(
     118│                 f"Retrieved digest for link {link.filename}({h}) not in poetry.lock"
     119│                 f" metadata {hashes}"
     120│             )
     121│

can you try to manually run  --trusted-host <IP_ADDRESS> --extra-index-url http://<IP_ADDRESS> training_pipeline to see if it throws the same error?
If yes, check if docker is using <IP_ADDRESS> as its bridge IP.
Also, as a sanity check, have you managed to run everything inside Airflow? There everything is packed together and should work without issues.

Sorry which command should I tag --trusted-host <IP_ADDRESS> --extra-index-url http://<IP_ADDRESS> training_pipeline to?
For airflow, after setting the credentials for wandb gcp etc, getting this error :
❯ docker compose up airflow-init
[+] Building 33.1s (5/6)
 => [airflow-init internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [airflow-init internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 331B                                                                                0.0s
 => [airflow-init internal] load metadata for docker.io/apache/airflow:2.5.2                                                                                0.7s
 => CACHED [airflow-init 1/3] FROM docker.io/apache/airflow:2.5.2@sha256:d6e2b5ed0832bdf32a07f8fef0c905ad89ccc0c5921dd6aedbf4bd2af855dac0                                                             0.0s
 => ERROR [airflow-init 2/3] RUN apt-get -y update && apt-get -y upgrade                                                                                32.3s
------
 > [airflow-init 2/3] RUN apt-get -y update && apt-get -y upgrade:
#0 0.574 Get:1 http://deb.debian.org/debian bullseye InRelease [116 kB]
#0 0.715 Get:2 http://deb.debian.org/debian-security bullseye-security InRelease [48.4 kB]
#0 0.770 Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
#0 0.772 Get:4 https://packages.microsoft.com/debian/11/prod bullseye InRelease [3629 B]
#0 0.996 Get:5 http://deb.debian.org/debian bullseye/main amd64 Packages [8183 kB]
#0 1.095 Get:6 http://repo.mysql.com/apt/debian bullseye InRelease [12.9 kB]
#0 1.280 Get:7 https://packages.microsoft.com/debian/11/prod bullseye/main armhf Packages [14.5 kB]
#0 1.389 Get:8 https://packages.microsoft.com/debian/11/prod bullseye/main all Packages [1088 B]
#0 1.391 Get:9 https://packages.microsoft.com/debian/11/prod bullseye/main amd64 Packages [93.2 kB]
#0 1.411 Get:10 http://repo.mysql.com/apt/debian bullseye/mysql-8.0 amd64 Packages [8596 B]
#0 1.447 Get:11 http://deb.debian.org/debian-security bullseye-security/main amd64 Packages [245 kB]
#0 1.453 Get:12 http://deb.debian.org/debian bullseye-updates/main amd64 Packages [14.8 kB]
#0 1.522 Get:13 https://packages.microsoft.com/debian/11/prod bullseye/main arm64 Packages [15.9 kB]
#0 2.157 Get:14 https://apt.postgresql.org/pub/repos/apt bullseye-pgdg InRelease [117 kB]
#0 3.120 Get:15 https://apt.postgresql.org/pub/repos/apt bullseye-pgdg/main amd64 Packages [274 kB]
#0 3.778 Fetched 9192 kB in 3s (2691 kB/s)
#0 3.778 Reading package lists...
#0 4.253 Reading package lists...
#0 4.719 Building dependency tree...
#0 4.856 Reading state information...
#0 4.883 Calculating upgrade...
#0 5.187 The following packages will be upgraded:
#0 5.187   base-files bind9-host bind9-libs debian-archive-keyring grep libc-bin
#0 5.188   libc-l10n libc6 libmysqlclient21 libncursesw6 libpq5 libssl1.1 libsystemd0
#0 5.188   libtinfo6 libudev1 libxml2 locales msodbcsql18 mysql-client mysql-common
#0 5.188   mysql-community-client mysql-community-client-core
#0 5.188   mysql-community-client-plugins ncurses-base ncurses-bin openssl
#0 5.188   postgresql-client postgresql-client-15 postgresql-client-common tzdata
#0 5.332 30 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
#0 5.332 Need to get 27.0 MB of archives.
#0 5.332 After this operation, 6712 kB of additional disk space will be used.
#0 5.332 Get:1 http://deb.debian.org/debian bullseye/main amd64 base-files amd64 11.1+deb11u7 [70.1 kB]
#0 5.369 Get:2 http://deb.debian.org/debian bullseye/main amd64 grep amd64 3.6-1+deb11u1 [398 kB]
#0 5.403 Get:3 http://deb.debian.org/debian bullseye/main amd64 ncurses-bin amd64 6.2+20201114-2+deb11u1 [429 kB]
#0 5.424 Get:4 http://deb.debian.org/debian bullseye/main amd64 libc6 amd64 2.31-13+deb11u6 [2827 kB]
#0 5.505 Get:5 http://deb.debian.org/debian bullseye/main amd64 libc-bin amd64 2.31-13+deb11u6 [824 kB]
#0 5.529 Get:6 http://deb.debian.org/debian bullseye/main amd64 ncurses-base all 6.2+20201114-2+deb11u1 [272 kB]
#0 5.537 Get:7 http://deb.debian.org/debian bullseye/main amd64 libsystemd0 amd64 247.3-7+deb11u2 [376 kB]
#0 5.546 Get:8 http://deb.debian.org/debian-security bullseye-security/main amd64 libssl1.1 amd64 1.1.1n-0+deb11u5 [1559 kB]
#0 5.586 Get:9 https://packages.microsoft.com/debian/11/prod bullseye/main amd64 msodbcsql18 amd64 <IP_ADDRESS>-1 [753 kB]
#0 5.588 Get:10 http://deb.debian.org/debian bullseye/main amd64 libudev1 amd64 247.3-7+deb11u2 [168 kB]
#0 5.591 Get:11 http://deb.debian.org/debian bullseye/main amd64 libncursesw6 amd64 6.2+20201114-2+deb11u1 [132 kB]
#0 5.595 Get:12 http://deb.debian.org/debian bullseye/main amd64 libtinfo6 amd64 6.2+20201114-2+deb11u1 [341 kB]
#0 5.606 Get:13 http://deb.debian.org/debian bullseye/main amd64 debian-archive-keyring all 2021.1.1+deb11u1 [110 kB]
#0 5.610 Get:14 http://deb.debian.org/debian bullseye/main amd64 tzdata all 2021a-1+deb11u10 [286 kB]
#0 5.617 Get:15 http://deb.debian.org/debian bullseye/main amd64 libxml2 amd64 2.9.10+dfsg-6.7+deb11u4 [693 kB]
#0 5.632 Get:16 http://deb.debian.org/debian-security bullseye-security/main amd64 bind9-libs amd64 1:9.16.42-1~deb11u1 [1427 kB]
#0 5.668 Get:17 http://deb.debian.org/debian-security bullseye-security/main amd64 bind9-host amd64 1:9.16.42-1~deb11u1 [310 kB]
#0 5.675 Get:18 http://deb.debian.org/debian bullseye/main amd64 libc-l10n all 2.31-13+deb11u6 [865 kB]
#0 5.697 Get:19 http://deb.debian.org/debian bullseye/main amd64 locales all 2.31-13+deb11u6 [4086 kB]
#0 5.771 Get:20 http://repo.mysql.com/apt/debian bullseye/mysql-8.0 amd64 mysql-client amd64 8.0.33-1debian11 [68.4 kB]
#0 5.804 Get:21 http://deb.debian.org/debian-security bullseye-security/main amd64 openssl amd64 1.1.1n-0+deb11u5 [854 kB]
#0 6.169 Get:22 http://repo.mysql.com/apt/debian bullseye/mysql-8.0 amd64 libmysqlclient21 amd64 8.0.33-1debian11 [1378 kB]
#0 6.739 Get:23 http://repo.mysql.com/apt/debian bullseye/mysql-8.0 amd64 mysql-community-client amd64 8.0.33-1debian11 [3477 kB]
#0 6.899 Get:24 https://apt.postgresql.org/pub/repos/apt bullseye-pgdg/main amd64 libpq5 amd64 15.3-1.pgdg110+1 [185 kB]
#0 7.036 Get:25 http://repo.mysql.com/apt/debian bullseye/mysql-8.0 amd64 mysql-community-client-core amd64 8.0.33-1debian11 [1908 kB]
#0 7.181 Get:26 http://repo.mysql.com/apt/debian bullseye/mysql-8.0 amd64 mysql-community-client-plugins amd64 8.0.33-1debian11 [1309 kB]
#0 7.289 Get:27 http://repo.mysql.com/apt/debian bullseye/mysql-8.0 amd64 mysql-common amd64 8.0.33-1debian11 [69.6 kB]
#0 7.481 Get:28 https://apt.postgresql.org/pub/repos/apt bullseye-pgdg/main amd64 postgresql-client-common all 250.pgdg110+1 [93.3 kB]
#0 7.485 Get:29 https://apt.postgresql.org/pub/repos/apt bullseye-pgdg/main amd64 postgresql-client-15 amd64 15.3-1.pgdg110+1 [1689 kB]
#0 8.113 Get:30 https://apt.postgresql.org/pub/repos/apt bullseye-pgdg/main amd64 postgresql-client all 15+250.pgdg110+1 [68.2 kB]
#0 8.803 Preconfiguring packages ...
#0 8.993 Fetched 27.0 MB in 3s (9254 kB/s)
(Reading database ... 12079 files and directories currently installed.)
#0 9.049 Preparing to unpack .../base-files_11.1+deb11u7_amd64.deb ...
#0 9.072 Unpacking base-files (11.1+deb11u7) over (11.1+deb11u6) ...
#0 9.294 Setting up base-files (11.1+deb11u7) ...
#0 9.303 Installing new version of config file /etc/debian_version ...
(Reading database ... 12079 files and directories currently installed.)
#0 9.476 Preparing to unpack .../grep_3.6-1+deb11u1_amd64.deb ...
#0 9.501 Unpacking grep (3.6-1+deb11u1) over (3.6-1) ...
#0 9.643 Setting up grep (3.6-1+deb11u1) ...
(Reading database ... 12079 files and directories currently installed.)
#0 9.763 Preparing to unpack .../ncurses-bin_6.2+20201114-2+deb11u1_amd64.deb ...
#0 9.786 Unpacking ncurses-bin (6.2+20201114-2+deb11u1) over (6.2+20201114-2) ...
#0 9.913 Setting up ncurses-bin (6.2+20201114-2+deb11u1) ...
(Reading database ... 12079 files and directories currently installed.)
#0 10.07 Preparing to unpack .../libc6_2.31-13+deb11u6_amd64.deb ...
#0 10.27 Unpacking libc6:amd64 (2.31-13+deb11u6) over (2.31-13+deb11u5) ...
#0 12.04 Setting up libc6:amd64 (2.31-13+deb11u6) ...
(Reading database ... 12079 files and directories currently installed.)
#0 13.38 Preparing to unpack .../libc-bin_2.31-13+deb11u6_amd64.deb ...
#0 13.41 Unpacking libc-bin (2.31-13+deb11u6) over (2.31-13+deb11u5) ...
#0 13.76 Setting up libc-bin (2.31-13+deb11u6) ...
(Reading database ... 12079 files and directories currently installed.)
#0 13.97 Preparing to unpack .../ncurses-base_6.2+20201114-2+deb11u1_all.deb ...
#0 13.99 Unpacking ncurses-base (6.2+20201114-2+deb11u1) over (6.2+20201114-2) ...
#0 14.36 Setting up ncurses-base (6.2+20201114-2+deb11u1) ...
(Reading database ... 12079 files and directories currently installed.)
#0 14.48 Preparing to unpack .../libsystemd0_247.3-7+deb11u2_amd64.deb ...
#0 14.51 Unpacking libsystemd0:amd64 (247.3-7+deb11u2) over (247.3-7+deb11u1) ...
#0 14.67 Setting up libsystemd0:amd64 (247.3-7+deb11u2) ...
(Reading database ... 12079 files and directories currently installed.)
#0 14.81 Preparing to unpack .../mysql-client_8.0.33-1debian11_amd64.deb ...
#0 14.85 Unpacking mysql-client (8.0.33-1debian11) over (8.0.32-1debian11) ...
#0 15.00 Preparing to unpack .../libssl1.1_1.1.1n-0+deb11u5_amd64.deb ...
#0 15.03 Unpacking libssl1.1:amd64 (1.1.1n-0+deb11u5) over (1.1.1n-0+deb11u4) ...
#0 15.28 Setting up libssl1.1:amd64 (1.1.1n-0+deb11u5) ...
(Reading database ... 12079 files and directories currently installed.)
#0 15.52 Preparing to unpack .../libmysqlclient21_8.0.33-1debian11_amd64.deb ...
#0 15.55 Unpacking libmysqlclient21:amd64 (8.0.33-1debian11) over (8.0.32-1debian11) ...
#0 15.82 Preparing to unpack .../libudev1_247.3-7+deb11u2_amd64.deb ...
#0 15.84 Unpacking libudev1:amd64 (247.3-7+deb11u2) over (247.3-7+deb11u1) ...
#0 15.99 Setting up libudev1:amd64 (247.3-7+deb11u2) ...
(Reading database ... 12079 files and directories currently installed.)
#0 16.11 Preparing to unpack .../mysql-community-client_8.0.33-1debian11_amd64.deb ...
#0 16.13 Unpacking mysql-community-client (8.0.33-1debian11) over (8.0.32-1debian11) ...
#0 16.88 Preparing to unpack .../mysql-community-client-core_8.0.33-1debian11_amd64.deb ...
#0 16.90 Unpacking mysql-community-client-core (8.0.33-1debian11) over (8.0.32-1debian11) ...
#0 17.28 Preparing to unpack .../mysql-community-client-plugins_8.0.33-1debian11_amd64.deb ...
#0 17.31 Unpacking mysql-community-client-plugins (8.0.33-1debian11) over (8.0.32-1debian11) ...
#0 17.68 Preparing to unpack .../libncursesw6_6.2+20201114-2+deb11u1_amd64.deb ...
#0 17.71 Unpacking libncursesw6:amd64 (6.2+20201114-2+deb11u1) over (6.2+20201114-2) ...
#0 17.87 Preparing to unpack .../libtinfo6_6.2+20201114-2+deb11u1_amd64.deb ...
#0 17.89 Unpacking libtinfo6:amd64 (6.2+20201114-2+deb11u1) over (6.2+20201114-2) ...
#0 18.03 Setting up libtinfo6:amd64 (6.2+20201114-2+deb11u1) ...
(Reading database ... 12079 files and directories currently installed.)
#0 18.16 Preparing to unpack .../mysql-common_8.0.33-1debian11_amd64.deb ...
#0 18.19 Unpacking mysql-common (8.0.33-1debian11) over (8.0.32-1debian11) ...
#0 18.33 Preparing to unpack .../debian-archive-keyring_2021.1.1+deb11u1_all.deb ...
#0 18.68 Unpacking debian-archive-keyring (2021.1.1+deb11u1) over (2021.1.1) ...
#0 18.93 Setting up debian-archive-keyring (2021.1.1+deb11u1) ...
#0 19.06 Removing obsolete conffile /etc/apt/trusted.gpg.d/debian-archive-stretch-automatic.gpg ...
#0 19.07 Removing obsolete conffile /etc/apt/trusted.gpg.d/debian-archive-stretch-security-automatic.gpg ...
#0 19.07 Removing obsolete conffile /etc/apt/trusted.gpg.d/debian-archive-stretch-stable.gpg ...
(Reading database ... 12079 files and directories currently installed.)
#0 19.21 Preparing to unpack .../00-tzdata_2021a-1+deb11u10_all.deb ...
#0 19.24 Unpacking tzdata (2021a-1+deb11u10) over (2021a-1+deb11u8) ...
#0 25.33 Preparing to unpack .../01-libxml2_2.9.10+dfsg-6.7+deb11u4_amd64.deb ...
#0 25.36 Unpacking libxml2:amd64 (2.9.10+dfsg-6.7+deb11u4) over (2.9.10+dfsg-6.7+deb11u3) ...
#0 25.53 Preparing to unpack .../02-bind9-libs_1%3a9.16.42-1~deb11u1_amd64.deb ...
#0 25.56 Unpacking bind9-libs:amd64 (1:9.16.42-1~deb11u1) over (1:9.16.37-1~deb11u1) ...
#0 25.78 Preparing to unpack .../03-bind9-host_1%3a9.16.42-1~deb11u1_amd64.deb ...
#0 25.81 Unpacking bind9-host (1:9.16.42-1~deb11u1) over (1:9.16.37-1~deb11u1) ...
#0 25.95 Preparing to unpack .../04-libc-l10n_2.31-13+deb11u6_all.deb ...
#0 25.97 Unpacking libc-l10n (2.31-13+deb11u6) over (2.31-13+deb11u5) ...
#0 26.14 Preparing to unpack .../05-locales_2.31-13+deb11u6_all.deb ...
#0 26.17 Unpacking locales (2.31-13+deb11u6) over (2.31-13+deb11u5) ...
#0 29.66 Preparing to unpack .../06-libpq5_15.3-1.pgdg110+1_amd64.deb ...
#0 29.69 Unpacking libpq5:amd64 (15.3-1.pgdg110+1) over (15.2-1.pgdg110+1) ...
#0 29.85 Preparing to unpack .../07-openssl_1.1.1n-0+deb11u5_amd64.deb ...
#0 29.88 Unpacking openssl (1.1.1n-0+deb11u5) over (1.1.1n-0+deb11u4) ...
#0 30.07 Preparing to unpack .../08-postgresql-client-common_250.pgdg110+1_all.deb ...
#0 30.09 Unpacking postgresql-client-common (250.pgdg110+1) over (248.pgdg110+1) ...
#0 30.24 Preparing to unpack .../09-postgresql-client-15_15.3-1.pgdg110+1_amd64.deb ...
#0 30.27 Unpacking postgresql-client-15 (15.3-1.pgdg110+1) over (15.2-1.pgdg110+1) ...
#0 31.70 Preparing to unpack .../10-postgresql-client_15+250.pgdg110+1_all.deb ...
#0 31.73 Unpacking postgresql-client (15+250.pgdg110+1) over (15+248.pgdg110+1) ...
#0 31.86 Preparing to unpack .../11-msodbcsql18_<IP_ADDRESS>-1_amd64.deb ...
#0 32.09 ERROR: The EULA was not accepted. Installation aborted.
#0 32.10 dpkg: error processing archive /tmp/apt-dpkg-install-HgI3pj/11-msodbcsql18_<IP_ADDRESS>-1_amd64.deb (--unpack):
#0 32.10  new msodbcsql18 package pre-installation script subprocess returned error exit status 1
#0 32.22 Errors were encountered while processing:
#0 32.22  /tmp/apt-dpkg-install-HgI3pj/11-msodbcsql18_<IP_ADDRESS>-1_amd64.deb
#0 32.27 E: Sub-process /usr/bin/dpkg returned an error code (1)
------
failed to solve: process "/bin/bash -o pipefail -o errexit -o nounset -o nolog -c apt-get -y update && apt-get -y upgrade" did not complete successfully: exit code: 100

Added RUN apt-get -y update && ACCEPT_EULA=Y apt-get -y upgrade seems to solve the above docker error. But now som issue with airflow:
❯ docker compose up airflow-init
[+] Building 0.0s (0/0)
[+] Running 3/3
 ✔ Container airflow-redis-1         Running                                                                                0.0s
 ✔ Container airflow-postgres-1      Running                                                                                0.0s
 ✔ Container airflow-airflow-init-1  Recreated                                                                                0.1s
Attaching to airflow-airflow-init-1
airflow-airflow-init-1  | The container is run as root user. For security, consider using a regular user account.
airflow-airflow-init-1  |
airflow-airflow-init-1  | /home/airflow/.local/lib/python3.7/site-packages/airflow/models/base.py:49 MovedIn20Warning: Deprecated API features detected! These feature(s) are not compatible with SQLAlchemy 2.0. To prevent incompatible upgrades prior to updating applications, ensure requirements files are pinned to "sqlalchemy<2.0". Set environment variable SQLALCHEMY_WARN_20=1 to show all deprecation warnings.  Set environment variable SQLALCHEMY_SILENCE_UBER_WARNING=1 to silence this message. (Background on SQLAlchemy 2.0 at: https://sqlalche.me/e/b8d9)
airflow-airflow-init-1  | DB: postgresql+psycopg2://airflow:***@postgres/airflow
airflow-airflow-init-1  | Performing upgrade with database postgresql+psycopg2://airflow:***@postgres/airflow
airflow-airflow-init-1  | [2023-06-27 15:43:47,078] {migration.py:205} INFO - Context impl PostgresqlImpl.
airflow-airflow-init-1  | [2023-06-27 15:43:47,078] {migration.py:212} INFO - Will assume transactional DDL.
airflow-airflow-init-1  | [2023-06-27 15:43:47,084] {db.py:1572} INFO - Creating tables
airflow-airflow-init-1  | INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
airflow-airflow-init-1  | INFO  [alembic.runtime.migration] Will assume transactional DDL.
airflow-airflow-init-1  | Traceback (most recent call last):
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/alembic/script/base.py", line 240, in _catch_revision_errors
airflow-airflow-init-1  |     yield
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/alembic/script/base.py", line 450, in _upgrade_revs
airflow-airflow-init-1  |     for script in reversed(list(revs))
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/alembic/script/revision.py", line 802, in iterate_revisions
airflow-airflow-init-1  |     assert_relative_length=assert_relative_length,
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/alembic/script/revision.py", line 1452, in _collect_upgrade_revisions
airflow-airflow-init-1  |     current_revisions = self.get_revisions(lower)
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/alembic/script/revision.py", line 525, in get_revisions
airflow-airflow-init-1  |     return sum([self.get_revisions(id_elem) for id_elem in id_], ())
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/alembic/script/revision.py", line 525, in <listcomp>
airflow-airflow-init-1  |     return sum([self.get_revisions(id_elem) for id_elem in id_], ())
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/alembic/script/revision.py", line 552, in get_revisions
airflow-airflow-init-1  |     for rev_id in resolved_id
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/alembic/script/revision.py", line 552, in <genexpr>
airflow-airflow-init-1  |     for rev_id in resolved_id
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/alembic/script/revision.py", line 633, in _revision_for_ident
airflow-airflow-init-1  |     resolved_id,
airflow-airflow-init-1  | alembic.script.revision.ResolutionError: No such revision or branch 'c804e5c76e3e'
airflow-airflow-init-1  |
airflow-airflow-init-1  | The above exception was the direct cause of the following exception:
airflow-airflow-init-1  |
airflow-airflow-init-1  | Traceback (most recent call last):
airflow-airflow-init-1  |   File "/home/airflow/.local/bin/airflow", line 8, in <module>
airflow-airflow-init-1  |     sys.exit(main())
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/airflow/__main__.py", line 48, in main
airflow-airflow-init-1  |     args.func(args)
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/airflow/cli/cli_parser.py", line 52, in command
airflow-airflow-init-1  |     return func(*args, **kwargs)
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/airflow/utils/cli.py", line 108, in wrapper
airflow-airflow-init-1  |     return f(*args, **kwargs)
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/airflow/cli/commands/db_command.py", line 88, in upgradedb
airflow-airflow-init-1  |     reserialize_dags=args.reserialize_dags,
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/airflow/utils/session.py", line 75, in wrapper
airflow-airflow-init-1  |     return func(*args, session=session, **kwargs)
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/airflow/utils/db.py", line 1579, in upgradedb
airflow-airflow-init-1  |     command.upgrade(config, revision=to_revision or "heads")
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/alembic/command.py", line 378, in upgrade
airflow-airflow-init-1  |     script.run_env()
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/alembic/script/base.py", line 576, in run_env
airflow-airflow-init-1  |     util.load_python_file(self.dir, "env.py")
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/alembic/util/pyfiles.py", line 94, in load_python_file
airflow-airflow-init-1  |     module = load_module_py(module_id, path)
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/alembic/util/pyfiles.py", line 110, in load_module_py
airflow-airflow-init-1  |     spec.loader.exec_module(module)  # type: ignore
airflow-airflow-init-1  |   File "<frozen importlib._bootstrap_external>", line 728, in exec_module
airflow-airflow-init-1  |   File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/airflow/migrations/env.py", line 117, in <module>
airflow-airflow-init-1  |     run_migrations_online()
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/airflow/migrations/env.py", line 111, in run_migrations_online
airflow-airflow-init-1  |     context.run_migrations()
airflow-airflow-init-1  |   File "<string>", line 8, in run_migrations
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/alembic/runtime/environment.py", line 867, in run_migrations
airflow-airflow-init-1  |     self.get_context().run_migrations(**kw)
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/alembic/runtime/migration.py", line 611, in run_migrations
airflow-airflow-init-1  |     for step in self._migrations_fn(heads, self):
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/alembic/command.py", line 367, in upgrade
airflow-airflow-init-1  |     return script._upgrade_revs(revision, rev)
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/alembic/script/base.py", line 450, in _upgrade_revs
airflow-airflow-init-1  |     for script in reversed(list(revs))
airflow-airflow-init-1  |   File "/usr/local/lib/python3.7/contextlib.py", line 130, in __exit__
airflow-airflow-init-1  |     self.gen.throw(type, value, traceback)
airflow-airflow-init-1  |   File "/home/airflow/.local/lib/python3.7/site-packages/alembic/script/base.py", line 272, in _catch_revision_errors
airflow-airflow-init-1  |     raise util.CommandError(resolution) from re
airflow-airflow-init-1  | alembic.util.exc.CommandError: Can't locate revision identified by 'c804e5c76e3e'
airflow-airflow-init-1  | ERROR: You need to upgrade the database. Please run `airflow db upgrade`. Make sure the command is run using Airflow version 2.5.2.
airflow-airflow-init-1  | 2.5.2
airflow-airflow-init-1 exited with code 0

Yes it seems I can download the packages from <IP_ADDRESS>.
Not sure if this is the correct way of checking the bridge IP but here:
❯ docker ps
CONTAINER ID   IMAGE                          COMMAND                  CREATED          STATUS                    PORTS                                   NAMES
a7f7f9606b99   pypiserver/pypiserver:latest   "/entrypoint.sh run …"   3 minutes ago    Up 3 minutes              <IP_ADDRESS>:80->8080/tcp, :::80->8080/tcp   friendly_faraday
7a37e812f067   postgres:13                    "docker-entrypoint.s…"   30 minutes ago   Up 30 minutes (healthy)   5432/tcp                                airflow-postgres-1
b33307d20811   redis:latest                   "docker-entrypoint.s…"   30 minutes ago   Up 30 minutes (healthy)   6379/tcp                                airflow-redis-1
976730dac03d   postgres:13                    "docker-entrypoint.s…"   7 weeks ago      Up 9 days (healthy)       5432/tcp                                airflow-ispo-api-postgres-1
❯ docker container inspect -f '{{ .NetworkSettings.IPAddress }}' a7f7f9606b99
<IP_ADDRESS>

I solved the airflow issue. Pull the latest code, and it should work. Note that I solved some additional bugs, so I strongly suggest you pull the latest changes.
Also, you should add your Hopsworks project name in the .env file under the FS_PROJECT_NAME = "<your-feature-store-project-name>" variable.
Let me know if you have any other questions.

got a fresh repo - reran feature_pipeline and training_pipeline that's ok.
There's a typo in Dockerfile for airflow -  removed the last line 2.6.2}
Airflow and Pypi running, but still getting the training pipeline error:
❯ poetry install
Warning: In a future version of Poetry, PyPI will be disabled automatically if at least one custom source is configured with another priority than 'explicit'. In order to avoid a breaking change and make your pyproject.toml forward compatible, add PyPI explicitly via 'poetry source add pypi'. By the way, this has the advantage that you can set the priority of PyPI as with any other source.
The currently activated Python version 3.10.9 is not supported by the project (~3.9).
Trying to find and use a compatible version.
Using python3 (3.9.10)
Installing dependencies from lock file

Package operations: 2 installs, 5 updates, 0 removals

  • Installing dataclasses (0.6)
  • Updating avro (1.10.2 -> 1.11.0)
  • Updating great-expectations (0.14.12 -> 0.14.13)
  • Updating hsfs (3.0.5 -> 3.2.0)
  • Updating hsml (3.0.3 -> 3.2.0)
  • Updating hopsworks (3.0.5 -> 3.2.0)
  • Installing training-pipeline (0.1.0): Failed

  RuntimeError

  Retrieved digest for link training_pipeline-0.1.0.tar.gz(md5:052e6f71...) not in poetry.lock metadata {'sha256:f1b068ce2d...', 'sha256:e062741...'}

  at ~/.local/share/pypoetry/venv/lib/python3.10/site-packages/poetry/installation/chooser.py:117 in _get_links
      113│
      114│             selected_links.append(link)
      115│
      116│         if links and not selected_links:
    → 117│             raise RuntimeError(
      118│                 f"Retrieved digest for link {link.filename}({h}) not in poetry.lock"
      119│                 f" metadata {hashes}"
      120│             )
      121│

Did you run
cd training-pipeline
poetry build
poetry publish -r my-pypi
cd ..

before doing poetry install inside the batch-prediction-pipeline?

Yes I did @iusztinpaul

That is strange.
Thanks for highlining the Docker typo. I fixed it.
I couldn't replicate the issue. So let's do the following.
To ensure that your PyPi server is working properly. Please do it end-to-end using only Airflow. Because the Python modules within Airflow are installed with pip, not Poetry. Like this, we can see if the issue is from the PyPi server or Poetry.
You are trying to access the code locally, which should be fine, but it is more complex to set up.
Let me know what your results are. We will make this work.

Oh, I thought the following already spins up pypi with airflow end-to-end?
docker compose up airflow-init
docker compose --env-file .env up --build -d

Sorry not to sure how to do it otherwise. This is the complete steps I used for airflow:
cd airflow
mkdir -p ./logs ./plugins
sudo chmod 777 ./logs ./plugins
echo -e "AIRFLOW_UID=$(id -u)" > .env
echo "ML_PIPELINE_ROOT_DIR=/opt/airflow/dags" >> .env
cd ./dags
cp .env.default .env
mkdir -p credentials/gcp/energy_consumption
cp -r /path/to/admin/gcs/credentials/admin-buckets.json credentials/gcp/energy_consumption
cd ..
docker compose up airflow-init
docker compose --env-file .env up --build -d

@mayofunk Thank you for your answer and help.
@hududed If what @mayofunk proposed doesn’t work, could you please show me the logs when running the Airflow DAG? (the commands you showed me look fine)

Okay that works! I think. So I pulled latest repo and ran these:
sudo docker run -p 80:8080 -v ~/.htpasswd:/data/.htpasswd pypiserver/pypiserver:latest run -P .htpasswd/htpasswd.txt --overwrite
pip install --trusted-host <IP_ADDRESS> --extra-index-url http://<IP_ADDRESS> training_pipeline
poetry install

Tested it with the airflow steps above (or in the readme), that also works - so this must have not finished when I ran it somehow pip install --trusted-host <IP_ADDRESS> --extra-index-url http://<IP_ADDRESS> training_pipeline to solve this issue.


 Are you able to have the test passing somewhere else ?

@lebauce / @safchain - I have verified that when ISTIO is installed the K8S tests (when run together) fail while individual K8S tests run. I suggest we postpone handling this PR for 2 weeks (until progressing with some of the open k8s items)

run skydive-k8s-tests

run skydive-k8s-tests


feat(cursor): Add CursorReplayStrategy with red dot painting and self-correction

Fixes #760
/claim #760
What kind of change does this PR introduce?
Feature
Summary
This PR introduces the CursorReplayStrategy feature, which allows the AI model to suggest coordinates for a red dot on a screenshot representing the intended action target location. This new strategy provides the ability to visualize and self-correct initial suggestions, improving replay accuracy. It also includes an update to the screenshot capturing functionality to support capturing all monitors.
Checklist

[x] My code follows the style guidelines of OpenAdapt
[x] I have performed a self-review of my code
[ ] If applicable, I have added tests to prove my fix is functional/effective
[x] I have linted my code locally prior to submission
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation (e.g. README.md, requirements.txt)
[ ] New and existing unit tests pass locally with my changes

How can your code be run and tested?

Test the CursorReplayStrategy by running the AI model and verifying the red dot is correctly suggested and visualized on the screenshot.
Use the self-correction mechanism to adjust the red dot position and verify the corrections are applied accurately.

Other information
No additional context needed.

Thank you @onyedikachi-david !
Can you please update your PR description with images containing the screenshot with the red dot?


Cherry-pick changes for v0.5.x

This cherry-picks most of the changes labeled with merge-0.5 to branch v0.5.x

@googlebot I consent.

@googlebot I consent.


Added Roboto font

PR for the issue mentioned
https://github.com/ishanbagchi/fibonacci-clock/issues/5#issue-700512724

@asi309, add the code in the hackit branch.


Cannot return null for non-nullable field Token.asset - Truncate does not help.

Environment
cardano-graphql v5.1.0-mainnet
cardano-node-ogmios-v4.0.0-mainnet
cardano-db-sync:11.0.0
Platform

[ ] Linux / Ubuntu
[X] Linux / Other
[ ] macOS
[ ] Windows

Platform version:
Runtime

[X] Node.js
[ ] Docker

Runtime version:
node v10.24.0
Steps to reproduce the bug
I get an Cannot return null for non-nullable field Token.asset when executing this query
  blocks(where: { number: { _eq: 6298956 } }) {
    forgedAt
    transactions {
      fee
      deposit
      hash
      inputs {
        address
        sourceTxHash
        sourceTxIndex
        value
        tokens {
          asset {
            assetName
            policyId
          }
          quantity
        }
      }
      outputs {
        address
        index
        value
        tokens {
          asset {
            assetName
            policyId
          }
          quantity
        }
      }
    }
  }
}

I’ve already reported this error here :  #612. The resolution was to run a truncate on the PostgreSQL DB. I did it, it took a very long time to rebuild the table but then the error was gone. Now the thing is that the fix is working for a few hundreds blocks and then it comes back. I don’t know if this issue comes from graphql or db-sync or another component but it seems that something is messing with table regularly.
What is the expected behavior?
After a full rebuild of the table the query is working again permanently.

Correct. Comparing the aggregate sum of all unique tokenMints to the assets table indicates if the two chain-following services are in sync at the tip of the node.

Maybe we don’t put enough resources on it.

What does your stack look like?

same issue on block 6566501: Cannot return null for non-nullable field Token.asset

@rhyslbw will a future version of cardano-graphql correct itself if it detects that Token.asset has gone out of sync? I just came across this on one of my testnet servers. Due to the ever-growing size of the Cardano, I'm trying to find ways to avoid doing DB rebuilds.

I think this issue needs to be re-opened. On cardano-graphql 6.1.0 I've come across this after migrating. I restarted Docker thinking the migration was finished but now some of the TokenMint assets are missing and you can't query that TokenMint.

I'm facing lots of these issues lately and I do agree with @CyberCyclone, I think cardano-graphql should do some check/resync on its side whenever an asset is missing from the table.

I'm facing lots of these issues lately and I do agree with @CyberCyclone, I think cardano-graphql should do some check/resync on its side whenever an asset is missing from the table. cc @rhyslbw

In fact, what I've just observed is that it will stop syncing assets when a db connection problem raises, and for whatever reason it has stopped for me around 4% of the sync:
{"name":"cardano-graphql","hostname":"cardano-graphql-95d5cd9fd-sjlwv","pid":1,"level":30,"module":"HasuraClient","assetId":"5acc52d5696e52345aec108468050d9d743eb21d6e41305bbc23a27b4154484f4d","msg":"Adding metadata to asset","time":"2022-06-03T00:52:12.711Z","v":0}
{"name":"cardano-graphql","hostname":"cardano-graphql-95d5cd9fd-sjlwv","pid":1,"level":20,"module":"DataFetcher","instance":"ServerHealth","value":{"startTime":"2022-05-27T08:49:05.529355378Z","lastKnownTip":{"slot":62630859,"hash":"f019d9ef9daaad5f110659b5653c0dbe4c8b6aeb1419dd08367d05d0afc49500","blockNo":7325468},"lastTipUpdate":"2022-06-02T19:12:31.503215526Z","networkSynchronization":0.99999,"currentEra":"Alonzo","metrics":{"sessionDurations":{"max":0,"min":0,"mean":135406113.08333334},"totalMessages":11510323,"runtimeStats":{"currentHeapSize":3156,"maxHeapSize":16330,"gcCpuTime":730487446667,"cpuTime":6582718759330},"activeConnections":3,"totalUnrouted":0,"totalConnections":15},"connectionStatus":"connected","currentEpoch":342,"slotInEpoch":250059},"msg":"value fetched after 30 seconds","time":"2022-06-03T00:52:34.406Z","v":0}
{"name":"cardano-graphql","hostname":"cardano-graphql-95d5cd9fd-sjlwv","pid":1,"level":20,"module":"DataFetcher","instance":"ServerHealth","value":{"startTime":"2022-05-27T08:49:05.529355378Z","lastKnownTip":{"slot":62630859,"hash":"f019d9ef9daaad5f110659b5653c0dbe4c8b6aeb1419dd08367d05d0afc49500","blockNo":7325468},"lastTipUpdate":"2022-06-02T19:12:31.503215526Z","networkSynchronization":0.99999,"currentEra":"Alonzo","metrics":{"sessionDurations":{"max":0,"min":0,"mean":135406113.08333334},"totalMessages":11510323,"runtimeStats":{"currentHeapSize":3156,"maxHeapSize":16330,"gcCpuTime":730487446667,"cpuTime":6582718759330},"activeConnections":3,"totalUnrouted":0,"totalConnections":15},"connectionStatus":"connected","currentEpoch":342,"slotInEpoch":250059},"msg":"value fetched after 30 seconds","time":"2022-06-03T00:53:04.411Z","v":0}
{"name":"cardano-graphql","hostname":"cardano-graphql-95d5cd9fd-sjlwv","pid":1,"level":30,"module":"Server","msg":"Sync Progress: cardano-db-sync: 99.96% | Asset: 4%","time":"2022-06-03T00:53:12.645Z","v":0}
{"name":"cardano-graphql","hostname":"cardano-graphql-95d5cd9fd-sjlwv","pid":1,"level":20,"module":"CardanoNodeClient","slotNo":62651286,"msg":"getTipSlotNo","time":"2022-06-03T00:53:12.690Z","v":0}
{"name":"cardano-graphql","hostname":"cardano-graphql-95d5cd9fd-sjlwv","pid":1,"level":30,"module":"HasuraClient","assetId":"2ad8fbdc6f18d97ce61b113301f05ff6b2a241c4e0bf5d06127d30a24f4343","msg":"Adding metadata to asset","time":"2022-06-03T00:53:18.644Z","v":0}
{"name":"cardano-graphql","hostname":"cardano-graphql-95d5cd9fd-sjlwv","pid":1,"level":20,"module":"Worker","qty":500,"msg":"Processing jobs","time":"2022-06-03T00:53:27.470Z","v":0}
(node:1) UnhandledPromiseRejectionWarning: Error [ERR_UNHANDLED_ERROR]: Unhandled error. ({
  errno: -113,
  code: 'EHOSTUNREACH',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 5432,
  queue: '__pgboss__maintenance',
  worker: 'f9a214d5-9653-44f7-8fe2-71497541ab9e'
})
    at new NodeError (internal/errors.js:322:7)
    at PgBoss.emit (events.js:389:17)
    at Manager.<anonymous> (/app/node_modules/pg-boss/src/index.js:86:37)
    at Manager.emit (events.js:400:28)
    at Worker.onError (/app/node_modules/pg-boss/src/manager.js:198:12)
    at Worker.start (/app/node_modules/pg-boss/src/worker.js:60:14)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 40)
{"name":"cardano-graphql","hostname":"cardano-graphql-95d5cd9fd-sjlwv","pid":1,"level":20,"module":"DataFetcher","instance":"ServerHealth","value":{"startTime":"2022-05-27T08:49:05.529355378Z","lastKnownTip":{"slot":62630859,"hash":"f019d9ef9daaad5f110659b5653c0dbe4c8b6aeb1419dd08367d05d0afc49500","blockNo":7325468},"lastTipUpdate":"2022-06-02T19:12:31.503215526Z","networkSynchronization":0.99999,"currentEra":"Alonzo","metrics":{"sessionDurations":{"max":0,"min":0,"mean":135406113.08333334},"totalMessages":11510323,"runtimeStats":{"currentHeapSize":3156,"maxHeapSize":16330,"gcCpuTime":730487446667,"cpuTime":6582718759330},"activeConnections":3,"totalUnrouted":0,"totalConnections":15},"connectionStatus":"connected","currentEpoch":342,"slotInEpoch":250059},"msg":"value fetched after 30 seconds","time":"2022-06-03T00:53:34.413Z","v":0}
(node:1) UnhandledPromiseRejectionWarning: Error: connect EHOSTUNREACH <IP_ADDRESS>:5432
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)
(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 42)
{"name":"cardano-graphql","hostname":"cardano-graphql-95d5cd9fd-sjlwv","pid":1,"level":30,"module":"Server","msg":"Sync Progress: cardano-db-sync: 99.96% | Asset: 4%","time":"2022-06-03T00:53:52.301Z","v":0}
{"name":"cardano-graphql","hostname":"cardano-graphql-95d5cd9fd-sjlwv","pid":1,"level":20,"module":"CardanoNodeClient","slotNo":62651337,"msg":"getTipSlotNo","time":"2022-06-03T00:53:52.316Z","v":0}
(node:1) UnhandledPromiseRejectionWarning: Error: connect EHOSTUNREACH <IP_ADDRESS>:5432
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)
(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 43)
{"name":"cardano-graphql","hostname":"cardano-graphql-95d5cd9fd-sjlwv","pid":1,"level":20,"module":"DataFetcher","instance":"ServerHealth","value":{"startTime":"2022-05-27T08:49:05.529355378Z","lastKnownTip":{"slot":62630859,"hash":"f019d9ef9daaad5f110659b5653c0dbe4c8b6aeb1419dd08367d05d0afc49500","blockNo":7325468},"lastTipUpdate":"2022-06-02T19:12:31.503215526Z","networkSynchronization":0.99999,"currentEra":"Alonzo","metrics":{"sessionDurations":{"max":0,"min":0,"mean":135406113.08333334},"totalMessages":11510323,"runtimeStats":{"currentHeapSize":3156,"maxHeapSize":16330,"gcCpuTime":730487446667,"cpuTime":6582718759330},"activeConnections":3,"totalUnrouted":0,"totalConnections":15},"connectionStatus":"connected","currentEpoch":342,"slotInEpoch":250059},"msg":"value fetched after 30 seconds","time":"2022-06-03T00:54:04.421Z","v":0}
{"name":"cardano-graphql","hostname":"cardano-graphql-95d5cd9fd-sjlwv","pid":1,"level":20,"module":"DataFetcher","instance":"ServerHealth","value":{"startTime":"2022-05-27T08:49:05.529355378Z","lastKnownTip":{"slot":62630859,"hash":"f019d9ef9daaad5f110659b5653c0dbe4c8b6aeb1419dd08367d05d0afc49500","blockNo":7325468},"lastTipUpdate":"2022-06-02T19:12:31.503215526Z","networkSynchronization":0.99999,"currentEra":"Alonzo","metrics":{"sessionDurations":{"max":0,"min":0,"mean":135406113.08333334},"totalMessages":11510323,"runtimeStats":{"currentHeapSize":3156,"maxHeapSize":16330,"gcCpuTime":730487446667,"cpuTime":6582718759330},"activeConnections":3,"totalUnrouted":0,"totalConnections":15},"connectionStatus":"connected","currentEpoch":342,"slotInEpoch":250059},"msg":"value fetched after 30 seconds","time":"2022-06-03T00:54:34.424Z","v":0}
(node:1) UnhandledPromiseRejectionWarning: Error [ERR_UNHANDLED_ERROR]: Unhandled error. ({
  errno: -113,
  code: 'EHOSTUNREACH',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 5432,
  queue: 'asset-metadata-fetch-update',
  worker: 'dbdc7e98-b44b-4afc-8b46-df1a5728198c'
})
    at new NodeError (internal/errors.js:322:7)
    at PgBoss.emit (events.js:389:17)
    at Manager.<anonymous> (/app/node_modules/pg-boss/src/index.js:86:37)
    at Manager.emit (events.js:400:28)
    at Worker.onError (/app/node_modules/pg-boss/src/manager.js:198:12)
    at Worker.start (/app/node_modules/pg-boss/src/worker.js:60:14)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 44)
{"name":"cardano-graphql","hostname":"cardano-graphql-95d5cd9fd-sjlwv","pid":1,"level":20,"module":"DataFetcher","instance":"ServerHealth","value":{"startTime":"2022-05-27T08:49:05.529355378Z","lastKnownTip":{"slot":62630859,"hash":"f019d9ef9daaad5f110659b5653c0dbe4c8b6aeb1419dd08367d05d0afc49500","blockNo":7325468},"lastTipUpdate":"2022-06-02T19:12:31.503215526Z","networkSynchronization":0.99999,"currentEra":"Alonzo","metrics":{"sessionDurations":{"max":0,"min":0,"mean":135406113.08333334},"totalMessages":11510323,"runtimeStats":{"currentHeapSize":3156,"maxHeapSize":16330,"gcCpuTime":730487446667,"cpuTime":6582718759330},"activeConnections":3,"totalUnrouted":0,"totalConnections":15},"connectionStatus":"connected","currentEpoch":342,"slotInEpoch":250059},"msg":"value fetched after 30 seconds","time":"2022-06-03T00:55:04.427Z","v":0}


added include for direct connect

Added include for the site http://www.kaliburg.de:11235/
Will work if port is changed.

Looks good!


Loss functions do not match the paper?

Hi, in your paper you state that you use two loss functions to train the feature extractor (SupCL and SelfSupCL). But in your code I can see 4 losses where there is a cross entropy loss between targets and outputs of the feature extractor:
train.py:

                # clustering, sup
                sup_logits = torch.cat([f[mask_lab] for f in (student_out / 0.1).chunk(2)], dim=0)
                sup_labels = torch.cat([class_labels[mask_lab] for _ in range(2)], dim=0)
                cls_loss = nn.CrossEntropyLoss()(sup_logits, sup_labels)

                # clustering, unsup
                cluster_loss = cluster_criterion(student_out, teacher_out, epoch)
                avg_probs = (student_out / 0.1).softmax(dim=1).mean(dim=0)
                me_max_loss = - torch.sum(torch.log(avg_probs**(-avg_probs))) + math.log(float(len(avg_probs)))
                cluster_loss += args.memax_weight * me_max_loss

                # represent learning, unsup
                contrastive_logits, contrastive_labels = info_nce_logits(features=student_proj)
                contrastive_loss = torch.nn.CrossEntropyLoss()(contrastive_logits, contrastive_labels)

                # representation learning, sup
                student_proj = torch.cat([f[mask_lab].unsqueeze(1) for f in student_proj.chunk(2)], dim=1)
                student_proj = torch.nn.functional.normalize(student_proj, dim=-1)
                sup_con_labels = class_labels[mask_lab]
                sup_con_loss = SupConLoss()(student_proj, labels=sup_con_labels)

This loss also seems to have effect on the feature extractor, can you elaborate?

Hi, our method SimGCD is introduced in the section 4 of our paper, and from the section 4.1 and section 4.2, you can see the four losses we used to train the model.

Thanks for clarification, I misunderstood that one


Document Translator June milestone

Published https://www.nuget.org/packages/Azure.AI.Translation.Document


Exceptions raised by a method

This is sorta similar to #7154, but takes more of the documentation approach versus a compiler feature.
I wanted to start a discussion about a possible improvement that could be made to the auto generated API docs; that shows the exceptions that could be raised by a method.
Currently this can be handled by doing like "# Raises SomeError if xyz" within your api docs.  The main problem with this is it would be mixed up in the type's documentation, versus separated out into its own section to improve visibility.
One option would be to have some new keyword within the docs that could be used to say list the possible exceptions after the rest of the documentation.
# RAISES: ParseException When the input is invalid
def some_method

I think ideally this would be parsed out by the doc generator automatically, however that's probably not easily (or at all) doable, so taking a keyword based approach is also fine.

Yard has https://www.rubydoc.info/gems/yard/file/docs/Tags.md#raise
PHPDoc has https://docs.phpdoc.org/references/phpdoc/tags/throws.html

tl;dr: Do we think having a built in syntax for rendering exceptions a method may throw is worthwhile?

I'd very much appreciate a standardized approach to document exceptions. Using a structured format would be great for this.
There are a few options though. We could continue with the admonition styled approach or consider something like Java-Doc inspired tags.
Another option is to declare exceptions not in the doc string, but in code, as an annotation:
@[Raises(ParseException, "When the input is invalid")]
def some_method
end

That's already a structured format understood by the compiler, so implementation would be pretty minimal. And it would make it easier to analyze the exceptions. Maybe some kind of linter could validate that all possible exceptions are listed, and maybe even check whether all exceptions are rescued up the line.
This would also be possible when defined inside the doc string, but then it requires understanding of the doc parsing. Annotations are more accessible.
This would be slightly similar to Java's throws clause, which is used to implement checked exceptions. I suppose we won't get that in Crystal, so it won't be a language feature. Java still has a @throws doc tag, though - probably to document unchecked exceptions.
I'm not sure whether using an annotation is the best idea. After all, it's primarily about documentation and we probably won't need to know exceptions at compile time, only in the doc generator (or some kind of analysis tool).

An annotation might be good. The compiler already knows whether a method raises or not, and we could easily enhance it to know which exceptions are thrown. Then checking that this info matches the annotation is easy.

actually, we already have an annotation Raises, but if let's the compiler know a method raises.

Mainly for the main raise method.

I really like the idea of doing this automatically/statically. I bet there are places in the standard library where few people know the exceptions that might be thrown.
Barring that, the annotation syntax is very clean, easy to implement, and easy to use, and I like it.

It can't be done automatically.

The compiler already knows whether a method raises or not, and we could easily enhance it to know which exceptions are thrown.

@asterite I assume by this you mean there could be some like Def.exceptions macro method that returns an array of exception types a given method could raise?

@Blacksmoke16 in theory the compiler could know all the exception types. In practice it doesn't.

Partial automatically generated documentation may still be useful depending on it's completeness.  How much is missing?


Preserve lazy data in cube math operations

Cube mathematics operations do not preserve lazy data on either the resultant cube or any input cubes to the mathematics :cry:
To demonstrate this:
>>> a1b = iris.load_cube(iris.sample_data_path('A1B_north_america.nc'))
>>> a1b.has_lazy_data()
True
>>> e1 = iris.load_cube(iris.sample_data_path('E1_north_america.nc'))
>>> e1.has_lazy_data()
True
>>> scenario_difference = a1b - e1
>>> print scenario_difference.has_lazy_data()
False
>>> print a1b.has_lazy_data()
False
>>> print e1.has_lazy_data()
False

With the recent versions of biggus, this is a nice small, self contained problem. @scmc72 might be interested in taking this on (ping @bjlittle).

A big amount of this got done. Use of biggus and then subsequently dask really helped with its implementation.


Build AppImageS of all binaries

This will require redesigning the group of ks-download binaries into one. We can leverage optparse-applicative here with sub-command features.


Dpnp.trace and dpnp.diagonal

CI fails because there is no DPNP package on Windows. Please protect test run as in other tests.

@Rubtsowa please add description to your PR. A PR without any description is a very hard to understand and just the title is not enough. Please describe in detail the changes, reason for changes, and expected outcome of the PR.

Hi @diptorupd. Let me introduce you. PRs marked as dpnp label are related to DPNP integration. This PR is for untegrate with new DPNP functions trace and diagonal.
There is also meta issue with a list and progress about new function integration - #383.


After upgrading react-native-iap 4.4.7 version in ios -getAvailablePurchases() not responding and other methods also not working in ios

Version of react-native-iap 4.4.7
Version of react-native 0.61.5
Platforms you faced the error (IOS or Android or both?) IOS
Expected behavior - available purchase items listing
Actual behavior - not responding
Tested environment (Emulator? Real Device?) Real device
Steps to reproduce the behavior - with 4.4.3 it's working but after upgrading the version 4.4.7 in ios it's not working and also i have test in android it's working.
Could you please help me on this my app in production and i need to update it asap.
Please help me

Can you verify you've called initConnection in iOS just as in android?

I've just ran the code in our example project and please check IapExample code either.

Can you verify you've called initConnection in iOS just as in android?
Yes we have called initConnection in both iOS and Android and it was not working and then I have downgrade my version from 4.4.7 to 4.4.3.
After downgrading version now we are facing issue with purchaseUpdatedListener in android , it's calling every time but it need to call when I am taking subscriptions.
In ios it's working correct but in android not.
Could you please help me on this.
Thanks.

Can you verify you've called initConnection in iOS just as in android?
Yes we have called initConnection in both iOS and Android and it was not working and then I have downgrade my version from 4.4.7 to 4.4.3.
After downgrading version now we are facing issue with purchaseUpdatedListener in android , it's calling every time but it need to call when I am taking subscriptions.
In ios it's working correct but in android not.
Could you please help me on this.
Thanks.

Have you run pod install after installing a new package? I just can't understand why 4.4.7 isn't working. Could you compare the code with the IapExample or share some of yours?

Yes I have run pod install after installing new package and it's not working properly and I will share the detailed code but for now can you please help me for purchaseUpdatedListener is running every time in android

I'm with the same problem...

Have you guys also called endConnnection when you've finished using billing functionalities?

I already solved it, the problem was not having called acknowledgePurchaseAndroid and finishTransaction after first buy.

@GuilhermeGabriel this was about IOS, your issue was about android... so it dosnt good to mention this here :)

I had this same problem and fixed it with the initConnection and endConnection. Thanks for the help!


Return promise object on error

Made changes to error handling by external users (on feedback from trusted dev)

Just looked into this. Tomas correct me if wrong but all of the tests "pass", however an error is logged to the console because we are using Promise.reject to handle the cases where no furniture is found. Since the same occurred before this PR, it makes sense to merge this as is and talk about the appropriate use of Promise.reject another time. Maybe there are other places in the lib which follow this pattern.

thx @bnjm!


bodyParser is not working for multi-form

Hi @cmather
Could you please look into this bug? I'm trying to parse inbound emails from Sendgrid, but this.request.body returns nothing. Thank you.
Router.onBeforeAction(Iron.Router.bodyParser.urlencoded({
    extended: false
}));

Router.route('/sendgrid/inbound', {where: 'server'})
    .post(function () {
        console.log('params', this.params);
        console.log('body', this.request.body);
        InboundEmails.insert(this.request.body);
        this.response.end('success')
    });

Have a look here, do the same for urlencoded:
#1435

I'm having the same issue with SendGrid, anyone get this to work

@AlmogRnD did you look at the above solution?

@chrisbutler I did but it did not work ?

do you have the code that you're working with in a repo somewhere, so i can look at it?

So SendGrid sends the request in multipart/form-data which I guess iron-router does not support I was able to fix this using Formidable. More info here - http://stackoverflow.com/questions/36253438/sendgrid-inbound-webhook-sending-empty-body

@AlmogRnD would you be able to test this.request.files instead of .body?


discover template in local directory if applicable

look for template in local directory
user looser check for SSH git URL

Coverage increased (+9.9%) to 89.857% when pulling ffde79693206ff4b9c0ad874298a661e5d5f8328 on mojavelinux:issue-2153-template-dir into 334b07330e1227d2e5dfb4bf6d33cc565cb63066 on middleman:master.

Coverage increased (+9.9%) to 89.857% when pulling ffde79693206ff4b9c0ad874298a661e5d5f8328 on mojavelinux:issue-2153-template-dir into 334b07330e1227d2e5dfb4bf6d33cc565cb63066 on middleman:master.

Coverage increased (+9.9%) to 89.857% when pulling ffde79693206ff4b9c0ad874298a661e5d5f8328 on mojavelinux:issue-2153-template-dir into 334b07330e1227d2e5dfb4bf6d33cc565cb63066 on middleman:master.

Coverage increased (+9.9%) to 89.857% when pulling ffde79693206ff4b9c0ad874298a661e5d5f8328 on mojavelinux:issue-2153-template-dir into 334b07330e1227d2e5dfb4bf6d33cc565cb63066 on middleman:master.

I wonder if we should require that the local directory be an absolute path (using Pathname(repo_name).absolute?). That might make it less likely to accidentally find a matching local path. wdyt?
I also split out the clone operation to a dedicated function.

@mojavelinux I think it's a good idea to make it absolute and error loudly in case of conflict.

In that case, let's do it!

I'll rebase.

Rebase complete!


Union type update

Clarify missing Union type in SSZ spec
Use "selector" wording instead of "type", since there may be multiple options of the same type in rare cases.
Reduce selector to 1 byte, and reserve the top 128 values (most significant bit) for future backwards-compatible extensions
Fix null reference in python-ish spec. It's referenced as the native-none/nil/null of the implementation anyway.
Update serialization and merkleization to cover None case in the Union

Note: this change is assumed to be backwards-compatible, since Union is not used anywhere in the spec. Outside of the spec there is one known case in the DB format of Lighthouse, but the old serialization/deserialization can be kept around there.
TODO:

See https://github.com/protolambda/remerkleable/pull/9 for remerkleable update. If I get an ACK on this PR, I will make a new remerkleable release, and update the pyspec, so we can start using Union in the spec and testing.

fixes #2270

Tagging this with the Altair label. It's not critical, nor used in consensus, but I like to ship the SSZ update before the old Union type gets more actual uses outside of the spec. And we are looking to use it in the Merge and Sharding specs.


Website Stuck on loading file

Describe the bug
Website Stuck on loading file
To Reproduce
Steps to reproduce the behavior:

Go to 'the website'
upload file
stuck on Loading file...

Expected behavior
it should generate the midi
Desktop (please complete the following information):

OS: [Win11]
Browser [chrome]
Version [130

I've had this problem for over two weeks. I've tried different browsers and cleared all cache.

maybe related to #151

I had this same issue on Mac with Safari.

I just tested it and it worked normally, are you still having this problem?

Same here, stuck in loading. Tried both Safari and Chrome and tried it to 3 different devices. Any fix?

Same here in Chrome Version 131.0.6778.86 (Official Build) (arm64)

Same here with two different computers and two different browsers in each one of them. Stuck on Loading file


How to log exceptions in Asp.NET Core

Is this supported in Asp.NET Core? I read I have to install AppIns ADK, but it is not for Asp.NET Core right?
Any sample of ILogger implementation using AppIns?
Thank you.

https://github.com/hishamco/ApplicationInsightsLogging


Clustering?

Have you been able to cluster nifi?

Yep.
There will be something to address this coming up soon.  Have some work I've been tinkering with locally and would like to migrate to use all the docker goodness like compose and machine.  spoiler alert This work will drive a lot of my talk at the next DMV Apache NiFi Meetup, October 29th.

I am running both the master and nodes with --net=host. I have confirmed the configs are right but the nodes are not connecting to the master. Any quick suggestions?

That's peculiar.  Any errors in either the node or manager nifi-app.log when the connections are attempted?

any chance of emailing me the nifi.properties files for a cluster to me<EMAIL_ADDRESS>I will see you at the meetup..

Will get something to you in the nearish future. On the road currently.

Thanks. Take your time!

@apiri any update on this?  Any slides from your talk?

@andrewserff I ended up creating my own version : https://github.com/clemenko/nifi

@andrewserff Eegads! I forgot to upload those.  Will get them up shortly as another source in addition to  @clemenko's way of doing it.

Hi @clemenko , take a look at https://github.com/aperepel/docker-nifi
Maybe we will merge this effort into an 'official' one eventually :)

Cool. I will have to play with this.


Use dry-types for coercions

Coverage decreased (-0.01%) to 98.756% when pulling 6be866d2237b9e525c5adc3b45c64d62cb644fb9 on dry-types into 209d76619fd80ee4c5b22d60844d35198731fdd3 on master.


Update Send Christmas visit slots

Unbookable - Christmas Eve, Christmas Day, Boxing Day, New Year's Eve, New Year's Day
Additional slots - 23rd + 30th Dec 1415-1545

@kyliemulholland Tested locally.


chore(deps): upgrade runtime dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-runtime-dependencies-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2796

Questions ?
Please refer to the Backport tool documentation


Bug: Update Inactvity Timer styling

Context
The inactvity  timer countdown component does not have any styling. Need to update the timer
Steps to Reproduce

Log into ECMPS
Remain inactive to activate the inactivity timer

The timer  countdown component does not have any styling. Need to update the timer

Styling was broken during the REACT upgrade. The timer is still functional. Adding this ticket to General backlog until it is prioritized

package is not compatible with React 18 so we can not style the circle. the time works and the styling currently is fine so closing


Can't create multiple devices

When trying to call the constructor twice, for two PCF8574A devices with different addresses :

I get the following error from the arduino compiler :

I couldn't find an example with two devices, so here I am !
Edit : My bad, I found an example in test1 but it still doesnt explain the error...

My bad, somehow the library manager duplicated the file, thus the dual include...

No problem, happens to all of use some day


feat(EndpointDataReferenceReceiver): backward compatibility via TranserStarted event

What this PR changes/adds
Implements the backward compatibility with EndpointDataReferenceReceiver on the new dsp protocol.
Why it does that
backward compatibility
Further notes
The EndpointDataReferenceReceiverRegistryImpl now implements an EventSubscriber that operates
on the TransferStarted event. If the event contains the dataAddress(EDR) it will forward it to the registered
receiver.
Linked Issue(s)
Closes #2926
Checklist

[x] added appropriate tests?
[x] performed checkstyle check locally?
[x] added/updated copyright headers?
[ ] documented public classes/methods?
[ ] added/updated relevant documentation?
[x] assigned appropriate label? (exclude from changelog with label no-changelog)
[x] formatted title correctly? (take a look at the CONTRIBUTING and Etiquette for pull requests for details)

Codecov Report
Patch coverage: 70.58% and no project coverage change.

Comparison is base (e2efdb9) 66.20% compared to head (84231ab) 66.20%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2965   +/-   ##
=======================================
  Coverage   66.20%   66.20%
=======================================
  Files        1040     1040
  Lines       21307    21319   +12
  Branches     1261     1263    +2
=======================================
+ Hits        14106    14115    +9
  Misses       6676     6676
- Partials      525      528    +3

Impacted Files
Coverage Δ

.../edc/connector/transfer/TransferCoreExtension.java
0.00% <0.00%> (ø)

...e/flow/ConsumerPullTransferDataFlowController.java
94.11% <71.42%> (-5.89%)
:arrow_down:

...edr/EndpointDataReferenceReceiverRegistryImpl.java
91.30% <77.77%> (-8.70%)
:arrow_down:

... and 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

@ndr-brt  I've put a fix also for #2975 here could you please check it?


Button variants

Summary
https://werkbotstudios.teamwork.com/#/tasks/27923273
Testing Steps

[x] set a site to use this version of the framewerk

[x] add a component map to your theme like:
  $component-button-properties: (
      textTransform: uppercase,
      fontWeight: 700,
      fontFamily: cursive,
      fontSize: 1.5rem,
      variants: (
          orange-btn: (
            background-color: orange,
            color: white,
            hoverStyle: (
              background-color: black,
              color: grey,
            )
          )
      )
  );

[x] create whatever button variants you added styles for on your site and test frontend

[x] confirm the default white-btn variant works, along with your custom variants

[x] test hover styles

[x] confirm the added font/text properties work too

@aletail https://github.com/werkbot/framewerk/blob/button-variants/docs/en/button.md


Best fork around.

https://github.com/CrackerakiUA/ngImgCropFullExtended

Came here to ask what the best fork was. I am not disappointed.

@CrackerakiUA thanks!!!


Show player colors on mobile

There doesn't seem to be any side effects when removing these lines, but I could be wrong...
Closes #98.

Thanks @yishn. I will take a look later today. The main issue is ensuring that long names fit even on smaller mobile screens.


combine with re-ranking

Hi, Thanks for the code, I'm new to this subject.
In the paper, you combine with re-ranking. I add a little code to compute gallery-gallery distances, but error: OOM when allocating tensor with shape[19732,19732,128].
So could you teow you combine the code with re-ranking.
Thank you!

Hi Zoesxw,
the error you mention isn't related to the re-ranking but simply based on the fact you can't compute the full gallery to gallery distance matrix. However, our eval code runs in a batched fashion, meaning this shouldn't happen and I guess you use a too large batch size. On the other hand you say you added code to compute the gallery-gallery distances, which you should simply be able to do by providing the correct files to our unaltered evaluation code.
Regarding the re-ranking, we will not release any code. For this we used the original Matlab code as provided by the authors.


Container logs can very large and should be compressed

Containers logs (particularly nginx and service) can be very large and take up a lot of space. Also, it isn't fast to docker logs container | grep foo them for issues.
We can't use logrotate inside the containers because they all report out on stdout/err, but it looks like we can configure the “local” logging driver and it does log-rotation by default and still works with docker logs, so we can do docker logs --since 10m <container_id>.
My bias is to do this for every container in the docker-compose.yml file.

I looked at the logs on server and here's what is taking up space since the server started in July 2021 (roughly 3 months) and has 550k submissions
nginx 637M
service  14M
enketo  27K
postgres  56K
pyxform  45K
redis  54K
redis 118K
smtp 1.2K

Given this, I propose we only deal with logging for nginx and service.


Model architecture evaluated in the paper

I checked your source code closely and found there is a toy model given in your demo.
I want to reproduce your paper's results. Can you share me the  model and search space you used to evaluate in the paper?
It would be very nice if you can provide the script used in the paper directly.
Thanks.

Search Space for replication: LR = [0.001, 0.1], NM = [0.5, 3] and System Used: Tesla P100 16GB - GPU & 13GB RAM Intel Xeon - CPU. Models will be refined and uploaded for reproduction. In the mean time, I've sent the version we've used directly to you.


CI Process Failed

Hi, I Created operator for my company and its been tests in many k8s distributions and in openshift. i add the details to the upstream-community-operators for uploading it to operatorhub.io and the ci /cd build process failed.
the reason don't mentioned in the output its seems like its search for the operator but its not installing it.
@estroz
link
https://travis-ci.com/operator-framework/community-operators/builds/105277805

Looks like we both have the same problem. Search for "Error", then you'll find something.

@niso120b @FxKu have you been able to deploy your operators with OLM prior to making a PR to this repo? The CI scripts might have kinks that need ironing out.

No. Thought I could get around it :)
I'll have a look. So if things are broken, OLM helps me to fix it?

@estroz No, I only deploy it with the yaml or with helm that I created.
But I used the the operator-courier to validate

@FxKu yes it’s look like it’s the same problem

When you've deployed your operators in the past, were there any extra objects you had to manually create in-cluster, aside from what's in the CSV and CRD's you've submitted here?

Yes with service account,
This is automatically generated by the operator SDK.
I need to deploy the operator with OLM in the cluster first?

@estroz

now its failed from other reason

@estroz
I also deploy in OLM every thing was good.
but now i update the package and its have an error from the ci travis environment
https://travis-ci.com/operator-framework/community-operators/jobs/187289655

do you have any way to help me with it please?

@estroz usually the first thing we create is a ConfigMap followed by the ServiceAccount + Cluster Roles. Afaik the latter is also part of the CSV, right? I could resolve my previous error, but now face a similar error than @niso120b (probably would get the same error, but in my case the Subscription is processed first):
error: unable to recognize "/tmp/tmp.K1VlQWgnKp_test_pr/deploy/postgres-operator.subscription.yaml": no matches for kind "Subscription" in version "operators.coreos.com/v1alpha1"

There was an issue installing OLM in CI. We're working on a fix. That's what's causing the errors you're seeing, as CatalogSources and Subscriptions are part of OLM.

This issue should be fixed with #232, closing now.
To get tests running on your PRs again, please update the PR by pushing an empty "dummy" commit for now.


chore(main): release 0.22.0

:robot: I have created a release beep boop
0.22.0 (2023-03-20)
Features

heart-rate: smoother progress (568bd27)

Bug Fixes

heart-rate: correct device check (a8145d1)

Performance Improvements

heart-rate: shorten learning phase (7d08f57)

Miscellaneous Chores

update PanTompkinsQRS submodule (0899689)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/CCXXXI/ecg_monitor/releases/tag/v0.22.0 :sunflower:


Support for Typesafe-IDREFS

When trying to use the fluent builder in the project vec-model the following error occurs:
incompatible types: java.util.List<java.lang.Object> cannot be converted to java.util.List<com.foursoft.harness.vec.v113.VecCartesianPoint3D>
incompatible types: java.lang.Object cannot be converted to com.foursoft.harness.vec.v113.VecVariantConfiguration
However, the plugin does not work smoothly with our Typesafe-IDREFS. Is it possible to support this?

In which plugin does it happen? Is there more stacktrace output?

Cannot reproduce this bug. I added a new unit test "idrefs-test.xsd" which verifies IDREF behavior and it seem to work OK. It is also OK to not generate sub-builders in this case, since there is no containment but a reference


Search with Auto-Complete

Need to be able to search through all projects in database.

@TarekRamesses @nithesh1510
Working good. Can be closed. Thanks.


Using in Vue 2 pulls in copy of Vue 1

Hi,
I'm using this under Vue @ ^2.0.1, and noticed that in my compiled source when I include vue-typeahead there's also a full copy of Vue @ 1.0.28 included, adding ~90k of unneeded code after compression. If I remove node_modules/vue-typeahead/node_modules/vue this goes away, and it just uses Vue 2 as expected.
I believe all your dependencies should maybe just be devDependencies, so a package local copy of an old Vue doesn't get installed?

Totally agree, faced with the same issue, please do this

+1

+1

+1 this is also breaking vue-devtools for me

+1


Set tomcat_protocol_ssl based on jira version if undef

Improvement on #219, will now default to the correct ssl connector protocol value for any jira version.

Hi @markleary, thanks for this PR!