katib bundle integration tests stuck in the CI with ERROR    juju.client.connection:connection.py:665 RPC: Automatic reconnect failed

Bug Description
The katib bundle integration tests are never finishing execution in the CI, they are eventually getting cancelled after 6 hours (the GH runners limit).
From the logs, it looks like all the tests have passed, by pytest operator is never exiting at the end.
This is currently blocking the CI in main and might also affect other branches.
 Example run
To Reproduce
trigger a CI run in main
Environment
juju 3.4/stable
microk8s 1.29-strict/stable
Relevant Log Output
Added 'kubeflow' model on microk8s/localhost with credential 'microk8s' for user 'admin'
bundle-integration: install_deps> python -I -m pip install -r requirements-integration.txt
bundle-integration: freeze> python -m pip freeze --all
bundle-integration: anyio==4.0.0,asttokens==2.4.0,backcall==0.2.0,bcrypt==4.0.1,cachetools==5.3.1,certifi==2023.7.22,cffi==1.15.1,charset-normalizer==3.2.0,cryptography==41.0.3,decorator==5.1.1,exceptiongroup==1.1.3,executing==1.2.0,google-auth==2.22.0,h11==0.14.0,httpcore==0.17.3,httpx==0.24.1,hvac==1.2.0,idna==3.4,iniconfig==2.0.0,ipdb==0.13.13,ipython==8.12.2,jedi==0.19.0,Jinja2==3.1.2,juju==3.2.2,kubernetes==27.2.0,lightkube==0.14.0,lightkube-models==<IP_ADDRESS>,macaroonbakery==1.3.1,MarkupSafe==2.1.3,matplotlib-inline==0.1.6,mypy-extensions==1.0.0,oauthlib==3.2.2,packaging==23.1,paramiko==2.12.0,parso==0.8.3,pexpect==4.8.0,pickleshare==0.7.5,pip==24.1,pluggy==1.3.0,prompt-toolkit==3.0.39,protobuf==3.20.3,ptyprocess==0.7.0,pure-eval==0.2.2,pyasn1==0.5.0,pyasn1-modules==0.3.0,pycparser==2.21,Pygments==2.16.1,pyhcl==0.4.5,pymacaroons==0.13.0,PyNaCl==1.5.0,pyRFC3339==1.1,pytest==7.4.2,pytest-asyncio==0.21.1,pytest-operator==0.29.0,python-dateutil==2.8.2,pytz==2023.3.post1,PyYAML==6.0.1,requests==2.31.0,requests
bundle-integration: commands[0]> pytest -v --tb native --show-capture=no --log-cli-level=INFO -s --model kubeflow /home/runner/work/katib-operators/katib-operators/tests/integration
============================= test session starts ==============================
platform linux -- Python 3.8.10, pytest-7.4.2, pluggy-1.3.0 -- /home/runner/work/katib-operators/katib-operators/.tox/bundle-integration/bin/python
cachedir: .tox/bundle-integration/.pytest_cache
rootdir: /home/runner/work/katib-operators/katib-operators
configfile: pyproject.toml
plugins: operator-0.29.0, asyncio-0.21.1, anyio-4.0.0
asyncio: mode=strict
collecting ... collected 12 items
tests/integration/test_charms.py::test_deploy_katib_charms
-------------------------------- live log setup --------------------------------
INFO     pytest_operator.plugin:plugin.py:675 Connecting to existing model github-pr-fb181-microk8s:kubeflow on unspecified cloud
WARNING  juju.client.connection:connection.py:927 unexpected facade UserSecretsDrain received from the controller
WARNING  juju.client.connection:connection.py:927 unexpected facade UserSecretsManager received from the controller
-------------------------------- live log call ---------------------------------
INFO     pytest_operator.plugin:plugin.py:526 Using tmp_path: /home/runner/work/katib-operators/katib-operators/.tox/bundle-integration/tmp/pytest/kubeflow0
INFO     pytest_operator.plugin:plugin.py:975 Building charm katib-controller
INFO     pytest_operator.plugin:plugin.py:980 Built charm katib-controller in 612.53s
INFO     pytest_operator.plugin:plugin.py:526 Using tmp_path: /home/runner/work/katib-operators/katib-operators/.tox/bundle-integration/tmp/pytest/kubeflow0
INFO     pytest_operator.plugin:plugin.py:975 Building charm katib-db-manager
INFO     pytest_operator.plugin:plugin.py:980 Built charm katib-db-manager in 125.68s
INFO     pytest_operator.plugin:plugin.py:526 Using tmp_path: /home/runner/work/katib-operators/katib-operators/.tox/bundle-integration/tmp/pytest/kubeflow0
INFO     pytest_operator.plugin:plugin.py:975 Building charm katib-ui
INFO     pytest_operator.plugin:plugin.py:980 Built charm katib-ui in 1007.46s
INFO     juju.model:model.py:2069 Deploying local:focal/katib-controller-0
INFO     juju.model:model.py:2069 Deploying local:focal/katib-db-manager-0
INFO     juju.model:model.py:2069 Deploying local:focal/katib-ui-0
INFO     juju.model:model.py:2069 Deploying ch:amd64/jammy/mysql-k8s-153
WARNING  juju.model:model.py:1558 relate is deprecated and will be removed. Use integrate instead.
WARNING  juju.model:model.py:1558 relate is deprecated and will be removed. Use integrate instead.
INFO     juju.model:model.py:2759 Waiting for model:
  katib-controller/0 [allocating] waiting: agent initialising
  katib-db-manager/0 [allocating] waiting: installing agent
  katib-ui/0 [allocating] waiting: installing agent
  katib-db/0 [allocating] waiting: installing agent
INFO     juju.model:model.py:2759 Waiting for model:
  katib-controller/0 [executing] maintenance: Reconciling charm: executing component kubernetes:auths-webhooks-crds-configmaps
  katib-db-manager/0 [idle] waiting: Waiting for relational-db data
  katib-ui/0 [idle] active:
  katib-db/0 [allocating] waiting: agent initialising
INFO     juju.model:model.py:2759 Waiting for model:
  katib-controller/0 [idle] active:
  katib-db-manager/0 [idle] waiting: Waiting for relational-db data
  katib-db/0 [executing] active: Primary
INFO     juju.model:model.py:2759 Waiting for model:
  katib-db-manager/0 [idle] active:
  katib-db/0 [idle] active: Primary
INFO     juju.model:model.py:2069 Deploying ch:amd64/focal/kubeflow-profiles-393
INFO     juju.model:model.py:2759 Waiting for model:
  katib-controller/0 [idle] active:
  katib-db-manager/0 [idle] active:
  katib-ui/0 [idle] active:
  katib-db/0 [idle] active: Primary
  kubeflow-profiles/0 [allocating] waiting: installing agent
INFO     juju.model:model.py:2759 Waiting for model:
  katib-db/0 [idle] active: Primary
  kubeflow-profiles/0 [idle] active:
PASSED
------------------------------ live log teardown -------------------------------
INFO     pytest_operator.plugin:plugin.py:783 Model status:
Model     Controller                Cloud/Region        Version  SLA          Timestamp
kubeflow  github-pr-fb181-microk8s  microk8s/localhost  3.4.4    unsupported  10:03:25Z
App                Version                  Status  Scale  Charm              Channel      Rev  Address         Exposed  Message
katib-controller                            active      1  katib-controller                  0  <IP_ADDRESS>  no
katib-db           8.0.36-0ubuntu<IP_ADDRESS>  active      1  mysql-k8s          8.0/stable   153  <IP_ADDRESS>   no
katib-db-manager                            active      1  katib-db-manager                  0  <IP_ADDRESS>  no
katib-ui                                    active      1  katib-ui                          0  <IP_ADDRESS>  no
kubeflow-profiles                           active      1  kubeflow-profiles  latest/edge  393  <IP_ADDRESS>  no
Unit                  Workload  Agent  Address       Ports  Message
katib-controller/0*   active    idle   <IP_ADDRESS>
katib-db-manager/0*   active    idle   <IP_ADDRESS>
katib-db/0*           active    idle   <IP_ADDRESS>         Primary
katib-ui/0*           active    idle   <IP_ADDRESS>
kubeflow-profiles/0*  active    idle   <IP_ADDRESS>
INFO     pytest_operator.plugin:plugin.py:789 Juju error logs:
unit-katib-controller-0: 10:01:08 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:08 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:09 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:09 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:09 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:13 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:14 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:15 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:16 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:16 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-db-manager-0: 10:01:16 ERROR unit.katib-db-manager/0.juju-log Failed to handle <PebbleReadyEvent via KatibDBManagerOperator/on/katib_db_manager_pebble_ready[21]> with error: Waiting for relational-db data
unit-katib-db-manager-0: 10:01:18 ERROR unit.katib-db-manager/0.juju-log Failed to handle <ConfigChangedEvent via KatibDBManagerOperator/on/config_changed[26]> with error: Waiting for relational-db data
unit-katib-db-manager-0: 10:01:38 ERROR unit.katib-db-manager/0.juju-log relational-db:3: Failed to handle <RelationJoinedEvent via KatibDBManagerOperator/on/relational_db_relation_joined[46]> with error: Waiting for relational-db data
unit-katib-db-manager-0: 10:01:40 ERROR unit.katib-db-manager/0.juju-log relational-db:3: Failed to handle <RelationChangedEvent via KatibDBManagerOperator/on/relational_db_relation_changed[51]> with error: Waiting for relational-db data
INFO     pytest_operator.plugin:plugin.py:855 Forgetting main...
ERROR    websockets.protocol:protocol.py:881 Error in data transfer
Traceback (most recent call last):
  File "/home/runner/work/katib-operators/katib-operators/.tox/bundle-integration/lib/python3.8/site-packages/websockets/protocol.py", line 827, in transfer_data
    message = await self.read_message()
  File "/home/runner/work/katib-operators/katib-operators/.tox/bundle-integration/lib/python3.8/site-packages/websockets/protocol.py", line 895, in read_message
    frame = await self.read_data_frame(max_size=self.max_size)
  File "/home/runner/work/katib-operators/katib-operators/.tox/bundle-integration/lib/python3.8/site-packages/websockets/protocol.py", line 971, in read_data_frame
    frame = await self.read_frame(max_size)
  File "/home/runner/work/katib-operators/katib-operators/.tox/bundle-integration/lib/python3.8/site-packages/websockets/protocol.py", line 1047, in read_frame
    frame = await Frame.read(
  File "/home/runner/work/katib-operators/katib-operators/.tox/bundle-integration/lib/python3.8/site-packages/websockets/framing.py", line 105, in read
    data = await reader(2)
  File "/usr/lib/python3.8/asyncio/streams.py", line 723, in readexactly
    await self._wait_for_data('readexactly')
  File "/usr/lib/python3.8/asyncio/streams.py", line 517, in _wait_for_data
    await self._waiter
  File "/usr/lib/python3.8/asyncio/selector_events.py", line 910, in write
    n = self._sock.send(data)
OSError: [Errno 9] Bad file descriptor
tests/integration/test_katib_experiments.py::test_katib_experiments[tests/assets/crs/experiments/darts-cpu.yaml]
-------------------------------- live log setup --------------------------------
INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/apiextensions.k8s.io/v1/customresourcedefinitions "HTTP/1.1 200 OK"
INFO     httpx:_client.py:1013 HTTP Request: POST https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1/profiles?fieldManager=katib-operators "HTTP/1.1 201 Created"
INFO     pytest_operator.plugin:plugin.py:675 Connecting to existing model github-pr-fb181-microk8s:kubeflow on unspecified cloud
WARNING  juju.client.connection:connection.py:927 unexpected facade UserSecretsDrain received from the controller
WARNING  juju.client.connection:connection.py:927 unexpected facade UserSecretsManager received from the controller
-------------------------------- live log call ---------------------------------
INFO     httpx:_client.py:1013 HTTP Request: POST https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments?fieldManager=katib-operators "HTTP/1.1 201 Created"
INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/darts-cpu "HTTP/1.1 200 OK"
INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/darts-cpu/status "HTTP/1.1 200 OK"
INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/darts-cpu/status "HTTP/1.1 200 OK"
INFO     utils:utils.py:82 Experiment status is Created
INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/darts-cpu/status "HTTP/1.1 200 OK"
INFO     utils:utils.py:82 Experiment status is Created
INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/darts-cpu/status "HTTP/1.1 200 OK"
INFO     utils:utils.py:82 Experiment status is Created
INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/darts-cpu/status "HTTP/1.1 200 OK"
INFO     utils:utils.py:82 Experiment status is Running
INFO     httpx:_client.py:1013 HTTP Request: DELETE https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/darts-cpu "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment darts-cpu to be deleted.
INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/darts-cpu "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment darts-cpu to be deleted.

INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/bayesian-optimization "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment bayesian-optimization to be deleted.

INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/hyperband "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment hyperband to be deleted.

INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/median-stop "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment median-stop to be deleted.

INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/tfjob-mnist-with-summaries "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment tfjob-mnist-with-summaries to be deleted.

INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/enas-cpu "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment enas-cpu to be deleted.

INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/cmaes "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment cmaes to be deleted.

INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/random "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment random to be deleted.

INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/simple-pbt "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment simple-pbt to be deleted.

INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/grid "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment grid to be deleted.

INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/file-metrics-collector "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment file-metrics-collector to be deleted.
INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/file-metrics-collector "HTTP/1.1 404 Not Found"
INFO     utils:utils.py:107 Unable to get Experiment file-metrics-collector (status: 404)
PASSED
------------------------------ live log teardown -------------------------------
ERROR    juju.client.connection:connection.py:665 RPC: Automatic reconnect failed
ERROR    juju.client.connection:connection.py:665 RPC: Automatic reconnect failed
INFO     pytest_operator.plugin:plugin.py:783 Model status:
Model     Controller                Cloud/Region        Version  SLA          Timestamp
kubeflow  github-pr-fb181-microk8s  microk8s/localhost  3.4.4    unsupported  10:16:03Z
App                Version                  Status  Scale  Charm              Channel      Rev  Address         Exposed  Message
katib-controller                            active      1  katib-controller                  0  <IP_ADDRESS>  no
katib-db           8.0.36-0ubuntu<IP_ADDRESS>  active      1  mysql-k8s          8.0/stable   153  <IP_ADDRESS>   no
katib-db-manager                            active      1  katib-db-manager                  0  <IP_ADDRESS>  no
katib-ui                                    active      1  katib-ui                          0  <IP_ADDRESS>  no
kubeflow-profiles                           active      1  kubeflow-profiles  latest/edge  393  <IP_ADDRESS>  no
Unit                  Workload  Agent  Address       Ports  Message
katib-controller/0*   active    idle   <IP_ADDRESS>
katib-db-manager/0*   active    idle   <IP_ADDRESS>
katib-db/0*           active    idle   <IP_ADDRESS>         Primary
katib-ui/0*           active    idle   <IP_ADDRESS>
kubeflow-profiles/0*  active    idle   <IP_ADDRESS>
INFO     pytest_operator.plugin:plugin.py:789 Juju error logs:
unit-katib-controller-0: 10:01:08 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:08 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:09 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:09 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:09 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:13 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:14 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:15 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:16 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:16 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-db-manager-0: 10:01:16 ERROR unit.katib-db-manager/0.juju-log Failed to handle <PebbleReadyEvent via KatibDBManagerOperator/on/katib_db_manager_pebble_ready[21]> with error: Waiting for relational-db data
unit-katib-db-manager-0: 10:01:18 ERROR unit.katib-db-manager/0.juju-log Failed to handle <ConfigChangedEvent via KatibDBManagerOperator/on/config_changed[26]> with error: Waiting for relational-db data
unit-katib-db-manager-0: 10:01:38 ERROR unit.katib-db-manager/0.juju-log relational-db:3: Failed to handle <RelationJoinedEvent via KatibDBManagerOperator/on/relational_db_relation_joined[46]> with error: Waiting for relational-db data
unit-katib-db-manager-0: 10:01:40 ERROR unit.katib-db-manager/0.juju-log relational-db:3: Failed to handle <RelationChangedEvent via KatibDBManagerOperator/on/relational_db_relation_changed[51]> with error: Waiting for relational-db data
WARNING  juju.client.connection:connection.py:657 RPC: Connection closed, reconnecting
ERROR    juju.client.connection:connection.py:665 RPC: Automatic reconnect failed

Additional Context
No response

Relevant Log Output
Added 'kubeflow' model on microk8s/localhost with credential 'microk8s' for user 'admin'
bundle-integration: install_deps> python -I -m pip install -r requirements-integration.txt
bundle-integration: freeze> python -m pip freeze --all
bundle-integration: anyio==4.0.0,asttokens==2.4.0,backcall==0.2.0,bcrypt==4.0.1,cachetools==5.3.1,certifi==2023.7.22,cffi==1.15.1,charset-normalizer==3.2.0,cryptography==41.0.3,decorator==5.1.1,exceptiongroup==1.1.3,executing==1.2.0,google-auth==2.22.0,h11==0.14.0,httpcore==0.17.3,httpx==0.24.1,hvac==1.2.0,idna==3.4,iniconfig==2.0.0,ipdb==0.13.13,ipython==8.12.2,jedi==0.19.0,Jinja2==3.1.2,juju==3.2.2,kubernetes==27.2.0,lightkube==0.14.0,lightkube-models==<IP_ADDRESS>,macaroonbakery==1.3.1,MarkupSafe==2.1.3,matplotlib-inline==0.1.6,mypy-extensions==1.0.0,oauthlib==3.2.2,packaging==23.1,paramiko==2.12.0,parso==0.8.3,pexpect==4.8.0,pickleshare==0.7.5,pip==24.1,pluggy==1.3.0,prompt-toolkit==3.0.39,protobuf==3.20.3,ptyprocess==0.7.0,pure-eval==0.2.2,pyasn1==0.5.0,pyasn1-modules==0.3.0,pycparser==2.21,Pygments==2.16.1,pyhcl==0.4.5,pymacaroons==0.13.0,PyNaCl==1.5.0,pyRFC3339==1.1,pytest==7.4.2,pytest-asyncio==0.21.1,pytest-operator==0.29.0,python-dateutil==2.8.2,pytz==2023.3.post1,PyYAML==6.0.1,requests==2.31.0,requests
bundle-integration: commands[0]> pytest -v --tb native --show-capture=no --log-cli-level=INFO -s --model kubeflow /home/runner/work/katib-operators/katib-operators/tests/integration
============================= test session starts ==============================
platform linux -- Python 3.8.10, pytest-7.4.2, pluggy-1.3.0 -- /home/runner/work/katib-operators/katib-operators/.tox/bundle-integration/bin/python
cachedir: .tox/bundle-integration/.pytest_cache
rootdir: /home/runner/work/katib-operators/katib-operators
configfile: pyproject.toml
plugins: operator-0.29.0, asyncio-0.21.1, anyio-4.0.0
asyncio: mode=strict
collecting ... collected 12 items
tests/integration/test_charms.py::test_deploy_katib_charms
-------------------------------- live log setup --------------------------------
INFO     pytest_operator.plugin:plugin.py:675 Connecting to existing model github-pr-fb181-microk8s:kubeflow on unspecified cloud
WARNING  juju.client.connection:connection.py:927 unexpected facade UserSecretsDrain received from the controller
WARNING  juju.client.connection:connection.py:927 unexpected facade UserSecretsManager received from the controller
-------------------------------- live log call ---------------------------------
INFO     pytest_operator.plugin:plugin.py:526 Using tmp_path: /home/runner/work/katib-operators/katib-operators/.tox/bundle-integration/tmp/pytest/kubeflow0
INFO     pytest_operator.plugin:plugin.py:975 Building charm katib-controller
INFO     pytest_operator.plugin:plugin.py:980 Built charm katib-controller in 612.53s
INFO     pytest_operator.plugin:plugin.py:526 Using tmp_path: /home/runner/work/katib-operators/katib-operators/.tox/bundle-integration/tmp/pytest/kubeflow0
INFO     pytest_operator.plugin:plugin.py:975 Building charm katib-db-manager
INFO     pytest_operator.plugin:plugin.py:980 Built charm katib-db-manager in 125.68s
INFO     pytest_operator.plugin:plugin.py:526 Using tmp_path: /home/runner/work/katib-operators/katib-operators/.tox/bundle-integration/tmp/pytest/kubeflow0
INFO     pytest_operator.plugin:plugin.py:975 Building charm katib-ui
INFO     pytest_operator.plugin:plugin.py:980 Built charm katib-ui in 1007.46s
INFO     juju.model:model.py:2069 Deploying local:focal/katib-controller-0
INFO     juju.model:model.py:2069 Deploying local:focal/katib-db-manager-0
INFO     juju.model:model.py:2069 Deploying local:focal/katib-ui-0
INFO     juju.model:model.py:2069 Deploying ch:amd64/jammy/mysql-k8s-153
WARNING  juju.model:model.py:1558 relate is deprecated and will be removed. Use integrate instead.
WARNING  juju.model:model.py:1558 relate is deprecated and will be removed. Use integrate instead.
INFO     juju.model:model.py:2759 Waiting for model:
  katib-controller/0 [allocating] waiting: agent initialising
  katib-db-manager/0 [allocating] waiting: installing agent
  katib-ui/0 [allocating] waiting: installing agent
  katib-db/0 [allocating] waiting: installing agent
INFO     juju.model:model.py:2759 Waiting for model:
  katib-controller/0 [executing] maintenance: Reconciling charm: executing component kubernetes:auths-webhooks-crds-configmaps
  katib-db-manager/0 [idle] waiting: Waiting for relational-db data
  katib-ui/0 [idle] active:
  katib-db/0 [allocating] waiting: agent initialising
INFO     juju.model:model.py:2759 Waiting for model:
  katib-controller/0 [idle] active:
  katib-db-manager/0 [idle] waiting: Waiting for relational-db data
  katib-db/0 [executing] active: Primary
INFO     juju.model:model.py:2759 Waiting for model:
  katib-db-manager/0 [idle] active:
  katib-db/0 [idle] active: Primary
INFO     juju.model:model.py:2069 Deploying ch:amd64/focal/kubeflow-profiles-393
INFO     juju.model:model.py:2759 Waiting for model:
  katib-controller/0 [idle] active:
  katib-db-manager/0 [idle] active:
  katib-ui/0 [idle] active:
  katib-db/0 [idle] active: Primary
  kubeflow-profiles/0 [allocating] waiting: installing agent
INFO     juju.model:model.py:2759 Waiting for model:
  katib-db/0 [idle] active: Primary
  kubeflow-profiles/0 [idle] active:
PASSED
------------------------------ live log teardown -------------------------------
INFO     pytest_operator.plugin:plugin.py:783 Model status:
Model     Controller                Cloud/Region        Version  SLA          Timestamp
kubeflow  github-pr-fb181-microk8s  microk8s/localhost  3.4.4    unsupported  10:03:25Z
App                Version                  Status  Scale  Charm              Channel      Rev  Address         Exposed  Message
katib-controller                            active      1  katib-controller                  0  <IP_ADDRESS>  no
katib-db           8.0.36-0ubuntu<IP_ADDRESS>  active      1  mysql-k8s          8.0/stable   153  <IP_ADDRESS>   no
katib-db-manager                            active      1  katib-db-manager                  0  <IP_ADDRESS>  no
katib-ui                                    active      1  katib-ui                          0  <IP_ADDRESS>  no
kubeflow-profiles                           active      1  kubeflow-profiles  latest/edge  393  <IP_ADDRESS>  no
Unit                  Workload  Agent  Address       Ports  Message
katib-controller/0*   active    idle   <IP_ADDRESS>
katib-db-manager/0*   active    idle   <IP_ADDRESS>
katib-db/0*           active    idle   <IP_ADDRESS>         Primary
katib-ui/0*           active    idle   <IP_ADDRESS>
kubeflow-profiles/0*  active    idle   <IP_ADDRESS>
INFO     pytest_operator.plugin:plugin.py:789 Juju error logs:
unit-katib-controller-0: 10:01:08 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:08 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:09 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:09 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:09 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:13 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:14 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:15 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:16 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:16 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-db-manager-0: 10:01:16 ERROR unit.katib-db-manager/0.juju-log Failed to handle <PebbleReadyEvent via KatibDBManagerOperator/on/katib_db_manager_pebble_ready[21]> with error: Waiting for relational-db data
unit-katib-db-manager-0: 10:01:18 ERROR unit.katib-db-manager/0.juju-log Failed to handle <ConfigChangedEvent via KatibDBManagerOperator/on/config_changed[26]> with error: Waiting for relational-db data
unit-katib-db-manager-0: 10:01:38 ERROR unit.katib-db-manager/0.juju-log relational-db:3: Failed to handle <RelationJoinedEvent via KatibDBManagerOperator/on/relational_db_relation_joined[46]> with error: Waiting for relational-db data
unit-katib-db-manager-0: 10:01:40 ERROR unit.katib-db-manager/0.juju-log relational-db:3: Failed to handle <RelationChangedEvent via KatibDBManagerOperator/on/relational_db_relation_changed[51]> with error: Waiting for relational-db data
INFO     pytest_operator.plugin:plugin.py:855 Forgetting main...
ERROR    websockets.protocol:protocol.py:881 Error in data transfer
Traceback (most recent call last):
  File "/home/runner/work/katib-operators/katib-operators/.tox/bundle-integration/lib/python3.8/site-packages/websockets/protocol.py", line 827, in transfer_data
    message = await self.read_message()
  File "/home/runner/work/katib-operators/katib-operators/.tox/bundle-integration/lib/python3.8/site-packages/websockets/protocol.py", line 895, in read_message
    frame = await self.read_data_frame(max_size=self.max_size)
  File "/home/runner/work/katib-operators/katib-operators/.tox/bundle-integration/lib/python3.8/site-packages/websockets/protocol.py", line 971, in read_data_frame
    frame = await self.read_frame(max_size)
  File "/home/runner/work/katib-operators/katib-operators/.tox/bundle-integration/lib/python3.8/site-packages/websockets/protocol.py", line 1047, in read_frame
    frame = await Frame.read(
  File "/home/runner/work/katib-operators/katib-operators/.tox/bundle-integration/lib/python3.8/site-packages/websockets/framing.py", line 105, in read
    data = await reader(2)
  File "/usr/lib/python3.8/asyncio/streams.py", line 723, in readexactly
    await self._wait_for_data('readexactly')
  File "/usr/lib/python3.8/asyncio/streams.py", line 517, in _wait_for_data
    await self._waiter
  File "/usr/lib/python3.8/asyncio/selector_events.py", line 910, in write
    n = self._sock.send(data)
OSError: [Errno 9] Bad file descriptor
tests/integration/test_katib_experiments.py::test_katib_experiments[tests/assets/crs/experiments/darts-cpu.yaml]
-------------------------------- live log setup --------------------------------
INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/apiextensions.k8s.io/v1/customresourcedefinitions "HTTP/1.1 200 OK"
INFO     httpx:_client.py:1013 HTTP Request: POST https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1/profiles?fieldManager=katib-operators "HTTP/1.1 201 Created"
INFO     pytest_operator.plugin:plugin.py:675 Connecting to existing model github-pr-fb181-microk8s:kubeflow on unspecified cloud
WARNING  juju.client.connection:connection.py:927 unexpected facade UserSecretsDrain received from the controller
WARNING  juju.client.connection:connection.py:927 unexpected facade UserSecretsManager received from the controller
-------------------------------- live log call ---------------------------------
INFO     httpx:_client.py:1013 HTTP Request: POST https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments?fieldManager=katib-operators "HTTP/1.1 201 Created"
INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/darts-cpu "HTTP/1.1 200 OK"
INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/darts-cpu/status "HTTP/1.1 200 OK"
INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/darts-cpu/status "HTTP/1.1 200 OK"
INFO     utils:utils.py:82 Experiment status is Created
INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/darts-cpu/status "HTTP/1.1 200 OK"
INFO     utils:utils.py:82 Experiment status is Created
INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/darts-cpu/status "HTTP/1.1 200 OK"
INFO     utils:utils.py:82 Experiment status is Created
INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/darts-cpu/status "HTTP/1.1 200 OK"
INFO     utils:utils.py:82 Experiment status is Running
INFO     httpx:_client.py:1013 HTTP Request: DELETE https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/darts-cpu "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment darts-cpu to be deleted.
INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/darts-cpu "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment darts-cpu to be deleted.

INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/bayesian-optimization "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment bayesian-optimization to be deleted.

INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/hyperband "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment hyperband to be deleted.

INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/median-stop "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment median-stop to be deleted.

INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/tfjob-mnist-with-summaries "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment tfjob-mnist-with-summaries to be deleted.

INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/enas-cpu "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment enas-cpu to be deleted.

INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/cmaes "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment cmaes to be deleted.

INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/random "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment random to be deleted.

INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/simple-pbt "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment simple-pbt to be deleted.

INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/grid "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment grid to be deleted.

INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/file-metrics-collector "HTTP/1.1 200 OK"
INFO     utils:utils.py:102 Waiting for Experiment file-metrics-collector to be deleted.
INFO     httpx:_client.py:1013 HTTP Request: GET https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1beta1/namespaces/test-kubeflow/experiments/file-metrics-collector "HTTP/1.1 404 Not Found"
INFO     utils:utils.py:107 Unable to get Experiment file-metrics-collector (status: 404)
PASSED
------------------------------ live log teardown -------------------------------
ERROR    juju.client.connection:connection.py:665 RPC: Automatic reconnect failed
ERROR    juju.client.connection:connection.py:665 RPC: Automatic reconnect failed
INFO     pytest_operator.plugin:plugin.py:783 Model status:
Model     Controller                Cloud/Region        Version  SLA          Timestamp
kubeflow  github-pr-fb181-microk8s  microk8s/localhost  3.4.4    unsupported  10:16:03Z
App                Version                  Status  Scale  Charm              Channel      Rev  Address         Exposed  Message
katib-controller                            active      1  katib-controller                  0  <IP_ADDRESS>  no
katib-db           8.0.36-0ubuntu<IP_ADDRESS>  active      1  mysql-k8s          8.0/stable   153  <IP_ADDRESS>   no
katib-db-manager                            active      1  katib-db-manager                  0  <IP_ADDRESS>  no
katib-ui                                    active      1  katib-ui                          0  <IP_ADDRESS>  no
kubeflow-profiles                           active      1  kubeflow-profiles  latest/edge  393  <IP_ADDRESS>  no
Unit                  Workload  Agent  Address       Ports  Message
katib-controller/0*   active    idle   <IP_ADDRESS>
katib-db-manager/0*   active    idle   <IP_ADDRESS>
katib-db/0*           active    idle   <IP_ADDRESS>         Primary
katib-ui/0*           active    idle   <IP_ADDRESS>
kubeflow-profiles/0*  active    idle   <IP_ADDRESS>
INFO     pytest_operator.plugin:plugin.py:789 Juju error logs:
unit-katib-controller-0: 10:01:08 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:08 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:09 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:09 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:09 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:13 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:14 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:15 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:16 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:16 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-db-manager-0: 10:01:16 ERROR unit.katib-db-manager/0.juju-log Failed to handle <PebbleReadyEvent via KatibDBManagerOperator/on/katib_db_manager_pebble_ready[21]> with error: Waiting for relational-db data
unit-katib-db-manager-0: 10:01:18 ERROR unit.katib-db-manager/0.juju-log Failed to handle <ConfigChangedEvent via KatibDBManagerOperator/on/config_changed[26]> with error: Waiting for relational-db data
unit-katib-db-manager-0: 10:01:38 ERROR unit.katib-db-manager/0.juju-log relational-db:3: Failed to handle <RelationJoinedEvent via KatibDBManagerOperator/on/relational_db_relation_joined[46]> with error: Waiting for relational-db data
unit-katib-db-manager-0: 10:01:40 ERROR unit.katib-db-manager/0.juju-log relational-db:3: Failed to handle <RelationChangedEvent via KatibDBManagerOperator/on/relational_db_relation_changed[51]> with error: Waiting for relational-db data
WARNING  juju.client.connection:connection.py:657 RPC: Connection closed, reconnecting
ERROR    juju.client.connection:connection.py:665 RPC: Automatic reconnect failed

I was able to reproduce this issue in a local machine.
The issue seems to be at teardown time. Right after the last test case is executed, the pytest-operator will show the juju status and pytest_operator.plugin:plugin.py:789 Juju error logs:, the latter will just hang w/o any automatic resolution causing the GH runner to just run for ~6h until it times out:
------------------------------ live log teardown -------------------------------
ERROR    juju.client.connection:connection.py:665 RPC: Automatic reconnect failed
ERROR    juju.client.connection:connection.py:665 RPC: Automatic reconnect failed
INFO     pytest_operator.plugin:plugin.py:783 Model status:
Model     Controller                Cloud/Region        Version  SLA          Timestamp
kubeflow  github-pr-fb181-microk8s  microk8s/localhost  3.4.4    unsupported  10:16:03Z
App                Version                  Status  Scale  Charm              Channel      Rev  Address         Exposed  Message
katib-controller                            active      1  katib-controller                  0  <IP_ADDRESS>  no
katib-db           8.0.36-0ubuntu<IP_ADDRESS>  active      1  mysql-k8s          8.0/stable   153  <IP_ADDRESS>   no
katib-db-manager                            active      1  katib-db-manager                  0  <IP_ADDRESS>  no
katib-ui                                    active      1  katib-ui                          0  <IP_ADDRESS>  no
kubeflow-profiles                           active      1  kubeflow-profiles  latest/edge  393  <IP_ADDRESS>  no
Unit                  Workload  Agent  Address       Ports  Message
katib-controller/0*   active    idle   <IP_ADDRESS>
katib-db-manager/0*   active    idle   <IP_ADDRESS>
katib-db/0*           active    idle   <IP_ADDRESS>         Primary
katib-ui/0*           active    idle   <IP_ADDRESS>
kubeflow-profiles/0*  active    idle   <IP_ADDRESS>
INFO     pytest_operator.plugin:plugin.py:789 Juju error logs:
unit-katib-controller-0: 10:01:08 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:08 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:09 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:09 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:09 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:13 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:14 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:15 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:16 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-controller-0: 10:01:16 ERROR unit.katib-controller/0.juju-log Empty or missing data. Got: No data found in relation k8s-service-info data bag.
unit-katib-db-manager-0: 10:01:16 ERROR unit.katib-db-manager/0.juju-log Failed to handle <PebbleReadyEvent via KatibDBManagerOperator/on/katib_db_manager_pebble_ready[21]> with error: Waiting for relational-db data
unit-katib-db-manager-0: 10:01:18 ERROR unit.katib-db-manager/0.juju-log Failed to handle <ConfigChangedEvent via KatibDBManagerOperator/on/config_changed[26]> with error: Waiting for relational-db data
unit-katib-db-manager-0: 10:01:38 ERROR unit.katib-db-manager/0.juju-log relational-db:3: Failed to handle <RelationJoinedEvent via KatibDBManagerOperator/on/relational_db_relation_joined[46]> with error: Waiting for relational-db data
unit-katib-db-manager-0: 10:01:40 ERROR unit.katib-db-manager/0.juju-log relational-db:3: Failed to handle <RelationChangedEvent via KatibDBManagerOperator/on/relational_db_relation_changed[51]> with error: Waiting for relational-db data
WARNING  juju.client.connection:connection.py:657 RPC: Connection closed, reconnecting
ERROR    juju.client.connection:connection.py:665 RPC: Automatic reconnect failed

@rgildein suggested this could be an incompatibility issue between juju 3.4 (3.4.4) and python-libjuju (3.2.2, currently used in our tests). After bumping the version, I was able to run the tests:
error: Please add required database relation: eg. relational-db
unit-katib-db-manager-0: 00:57:34 ERROR unit.katib-db-manager/0.juju-log Failed to handle <ConfigChangedEvent via KatibDBManagerOperator/on/config_changed[26]> with error: Please add required database relation: eg. relational-db
unit-katib-db-manager-0: 00:57:53 ERROR unit.katib-db-manager/0.juju-log mysql:93: Failed to handle <RelationJoinedEvent via KatibDBManagerOperator/on/mysql_relation_joined[46]> with error: Please add required database relation: eg. relational-db
unit-katib-db-manager-0: 00:57:54 ERROR unit.katib-db-manager/0.juju-log mysql:93: Failed to handle <RelationChangedEvent via KatibDBManagerOperator/on/mysql_relation_changed[51]> with error: Please add required database relation: eg. relational-db
unit-katib-db-manager-0: 00:57:55 ERROR unit.katib-db-manager/0.juju-log mysql:93: Missing attribute 'root_password' in mysql relation data
unit-katib-db-manager-0: 00:57:55 ERROR unit.katib-db-manager/0.juju-log mysql:93: Failed to handle <RelationChangedEvent via KatibDBManagerOperator/on/mysql_relation_changed[56]> with error: Incorrect/incomplete data found in relation mysql. See logs

WARNING  juju.client.connection:connection.py:654 RPC: Connection closed, reconnecting
ERROR    juju.client.connection:connection.py:662 RPC: Automatic reconnect failed
INFO     pytest_operator.plugin:plugin.py:947 Forgetting model main...
INFO     httpx:_client.py:1013 HTTP Request: DELETE https://<IP_ADDRESS>:16443/apis/kubeflow.org/v1/profiles/test-kubeflow "HTTP/1.1 200 OK"

================================================================================ warnings summary ================================================================================
tests/integration/test_katib_experiments.py::test_katib_experiments[tests/assets/crs/experiments/grid-example.yaml]
tests/integration/test_katib_experiments.py::test_katib_experiments[tests/assets/crs/experiments/grid-example.yaml]
tests/integration/test_katib_experiments.py::test_katib_experiments[tests/assets/crs/experiments/grid-example.yaml]
  /home/ubuntu/katib-operators/.tox/bundle-integration/lib/python3.10/site-packages/juju/client/connection.py:659: DeprecationWarning: The explicit passing of coroutine objects to asyncio.wait() is deprecated since Python 3.8, and scheduled for removal in Python 3.11.
    await jasyncio.wait([self.reconnect()])

tests/integration/test_katib_experiments.py::test_katib_experiments[tests/assets/crs/experiments/grid-example.yaml]
  /home/ubuntu/katib-operators/.tox/bundle-integration/lib/python3.10/site-packages/_pytest/runner.py:140: RuntimeWarning: coroutine 'training_operator' was never awaited
    item.funcargs = None  # type: ignore[attr-defined]
  Enable tracemalloc to get traceback where the object was allocated.
  See https://docs.pytest.org/en/stable/how-to/capture-warnings.html#resource-warnings for more info.

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=================================================================== 12 passed, 4 warnings in 596.21s (0:09:56) ===================================================================
  bundle-integration: OK (610.19=setup[13.07]+cmd[597.12] seconds)
  congratulations :) (610.25 seconds)

#210 should fix this issue


Adding in proxy options and slackcat-example.conf

Adding support for proxy option
Added a slackcat-example.conf
Updated README.md

Merged, thank you!


clair.log grow too fast every day  9.7G！！

version：v1.2.0
OS：CentOS  7.2
du -sh * /var/log/harbor/2017-10-22
36K	adminserver.log
4.0K	anacron.log
1.4M	clair-db.log
9.7G	clair.log
4.0K	crond.log
4.0K	CROND.log
664K	jobservice.log
52K	mysql.log
120K	proxy.log
5.4M	registry.log
4.0K	run-parts.log
1.1M	ui.log

刷新频繁
Oct 23 16:09:07 <IP_ADDRESS> clair[9892]: {"Event":"Handled HTTP request","Level":"info","Location":"router.go:57","Time":"2017-10-23 08:09:07.993535","elapsed time":6937237,"method":"GET","remote addr":"<IP_ADDRESS>:52213","request uri":"/v1/notifications/167f8469-34e0-4715-9a3b-beee5d96b988?limit=2","status":"200"}
Oct 23 16:09:07 <IP_ADDRESS> clair[9892]: {"Event":"Handled HTTP request","Level":"info","Location":"router.go:57","Time":"2017-10-23 08:09:07.997718","elapsed time":1110168,"method":"DELETE","remote addr":"<IP_ADDRESS>:52213","request uri":"/v1/notifications/167f8469-34e0-4715-9a3b-beee5d96b988","status":"200"}
Oct 23 16:09:07 <IP_ADDRESS> clair[9892]: {"Event":"successfully sent notification","Level":"info","Location":"notifier.go:184","Time":"2017-10-23 08:09:07.998208","notification name":"167f8469-34e0-4715-9a3b-beee5d96b988"}
Oct 23 16:09:08 <IP_ADDRESS> clair[9892]: {"Event":"found and locked a notification","Level":"info","Location":"notifier.go:143","Time":"2017-10-23 08:09:08.034668","notification name":"16fb9c19-9253-4741-850c-300bd70bf9e5"}
Oct 23 16:09:08 <IP_ADDRESS> clair[9892]: true
Oct 23 16:09:08 <IP_ADDRESS> clair[9892]: {"Event":"Handled HTTP request","Level":"info","Location":"router.go:57","Time":"2017-10-23 08:09:08.041954","elapsed time":6322468,"method":"GET","remote addr":"<IP_ADDRESS>:52213","request uri":"/v1/notifications/16fb9c19-9253-4741-850c-300bd70bf9e5?limit=2","status":"200"}
Oct 23 16:09:08 <IP_ADDRESS> clair[9892]: {"Event":"Handled HTTP request","Level":"info","Location":"router.go:57","Time":"2017-10-23 08:09:08.045305","elapsed time":828889,"method":"DELETE","remote addr":"<IP_ADDRESS>:52213","request uri":"/v1/notifications

@Yeefoner The log content in your description doesn't seem problematic.   Are all of the 9.7 G log about notifications?  Could you gzip your log files and upload to a storage so we can check?

@reasonerjt
The log.gzip sent emails to<EMAIL_ADDRESS>

@Yeefoner I didn't receive your Email, probably filtered out due to the large size, could you upload to some 3rd party storage (Google, Baidu) and share it to me?

@reasonerjt 链接: https://pan.baidu.com/s/1mhVsDss 密码: q8fw

@Yeefoner
I see a lot of errors connecting "<IP_ADDRESS>:8089" and got connection refused.
Like this:
Oct 23 08:00:00 <IP_ADDRESS> clair[4915]: {"Event":"could not get NVD data feed hash","Level":"warning","Location":"nvd.go:137","Time":"2017-10-23 00:00:00.113550","data feed name":"2013","error":"Get http://static.nvd.nist.gov/feeds/xml/cve/nvdcve-2.0-2013.meta: proxyconnect tcp: dial tcp <IP_ADDRESS>:8089: getsockopt: connection refused"}

Seems Clair's code has an issue that it keep retrying when encounter unexpected error.
We will refine the strategy to package log files to mitigate the problem but this is essentially a problem in your env.


[EPIC] The ngsildUpdateBridge must be able to update and replace properties/relationship

Details
The NGSI-LD updateBridge API needs to be revised and documented to make sure we cover still what is needed
The RBAC use of the API needs to be reviewd
(what about subscription? merge?) Today we have Factory_Admin, Factory_Reader, Factory_Editor(?), Factory_Writer, Factory_Subscriber. We need an API Mapping to roles.
User Stories: #557
Notes

Merge endpoints behave erroneously, an issue is opened.

Key findings about merge patch implementation:

There are no unit tests for merge patch behavior neither for singular entities nor batch handling, which makes the probability of a regression high.
The main merge patch logic for singular entities is implemented as a postgresql function, which complicates debugging the issue. The most recent update to the function is from 15.10.2023, 10 months ago. For batch operations a separate but similar function is defined, which is more recent.
The surface level reading of the functions suggests an overwriting behavior resulting in a shallow merge instead of a recursive deep merge that is aligned with the specification.
The implementation and the handled datatype makes using a dedicated Postgresql Debugger necessary to understand why exactly it fails.

A pull request was merged, which is supposed to fix the merge patch issue and some more (100k+ LOC change).
Also I received a response to the original issue claiming that the issue will be fixed with this upcoming change and a new release will be made soon including the implementation of NGSI-LD 1.8.1.

A new release has been created. Aside from the merge fix, NGSI-LD 1.8.1 changes are implemented and there's a topics overhaul. Will check out how it fares

Already tested Scorpio version 5.0.2 with merge request,

deep merge possible
merge test to be implemented
Probably next week we can do rebase

The datasetId in mergepatch issue:
https://github.com/ScorpioBroker/ScorpioBroker/issues/612

The datasetId in mergepatch issue:
https://github.com/ScorpioBroker/ScorpioBroker/issues/612

New release 5.0.3 claims to have fixed this, will rebase and see if it's working.


However, if you confirm it by clicking outside, it will not crash, but output this error instead:
scene/gui/control.cpp:2186 - Condition ' !is_inside_tree() ' is true.
Changing the Easing also doesn't crash, but the inspector will go blank once it's changed.

By the way, I tested this prior to my commit, and still happens, so the cause has to be something older.

I can confirm this on commit https://github.com/godotengine/godot/commit/500fe8960079400140f5459c482d8e116f589172.

I bisected it to this:
ca80ebe9f6319f3caf008

CC @timoschwarzer

also crash when changing Interpolcation mode.

Will take a look later today. Thanks for bisecting! :)

No problem.  Hope its nothing too serious.

Hope its nothing too serious.

Worst case would be reverting and rewriting the PR. It wasn't a too large of a PR :wink:

I can confirm this (clicking on other the controls to unfocus or editing with the arrow key doesn't cause a crash).
Stack trace:
Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGABRT)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000008
Exception Note:        EXC_CORPSE_NOTIFY

VM Regions Near 0x8:
-->
    __TEXT<PHONE_NUMBER>847000-000000010815a000 [ 73.1M] r-x/rwx SM=COW  /Volumes/VOLUME/*/Godot.app/Contents/MacOS/Godot

Application Specific Information:
abort() called

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x00007fff73c642c6 __pthread_kill + 10
1   libsystem_pthread.dylib       	0x00007fff73d1fbf1 pthread_kill + 284
2   libsystem_c.dylib             	0x00007fff73bce6a6 abort + 127
3   godot                         	0x0000000103849a03 handle_crash(int) + 3203 (crash_handler_osx.mm:153)
4   libsystem_platform.dylib      	0x00007fff73d14b5d _sigtramp + 29
5   ???<PHONE_NUMBER>00000000 0 + 0
6   godot                         	0x0000000106923eac HashMap<StringName, Object::Signal, HashMapHasherDefault, HashMapComparatorDefault<StringName>, (unsigned char)3, (unsigned char)8>::getptr(StringName const&) + 76 (hash_map.h:320)
7   godot                         	0x0000000106922da0 Object::emit_signal(StringName const&, Variant const**, int) + 96 (object.cpp:1177)
8   godot                         	0x00000001069216d8 Object::emit_signal(StringName const&, Variant const&, Variant const&, Variant const&, Variant const&, Variant const&) + 200 (object.cpp:1296)
9   godot                         	0x0000000105cd4088 CanvasItem::_propagate_visibility_changed(bool) + 296 (canvas_item.cpp:389)
10  godot                         	0x0000000105cd46c3 CanvasItem::hide() + 131 (canvas_item.cpp:430)
11  godot                         	0x0000000104ec276a EditorSpinSlider::_value_input_entered(String const&) + 42 (editor_spin_slider.cpp:340)
12  godot                         	0x000000010694312b MethodBind1<String const&>::call(Object*, Variant const**, int, Variant::CallError&) + 747 (method_bind.gen.inc:775)
13  godot                         	0x0000000106920d60 Object::call(StringName const&, Variant const**, int, Variant::CallError&) + 1456 (object.cpp:940)
14  godot                         	0x000000010692369a Object::emit_signal(StringName const&, Variant const**, int) + 2394 (object.cpp:1240)
15  godot                         	0x00000001069216d8 Object::emit_signal(StringName const&, Variant const&, Variant const&, Variant const&, Variant const&, Variant const&) + 200 (object.cpp:1296)
16  godot                         	0x0000000105902a72 LineEdit::_gui_input(Ref<InputEvent>) + 6274 (line_edit.cpp:306)
17  godot                         	0x0000000105804dab MethodBind1<Ref<InputEvent> >::call(Object*, Variant const**, int, Variant::CallError&) + 747 (method_bind.gen.inc:775)
18  godot                         	0x000000010691f344 Object::call_multilevel(StringName const&, Variant const**, int) + 948 (object.cpp:775)
19  godot                         	0x0000000106920785 Object::call_multilevel(StringName const&, Variant const&, Variant const&, Variant const&, Variant const&, Variant const&) + 213 (object.cpp:880)
20  godot                         	0x00000001057cf65d Viewport::_gui_input_event(Ref<InputEvent>) + 15485 (viewport.cpp:2266)
21  godot                         	0x00000001057c9658 Viewport::input(Ref<InputEvent> const&) + 296 (viewport.cpp:2686)
22  godot                         	0x00000001057c94e7 Viewport::_vp_input(Ref<InputEvent> const&) + 247 (viewport.cpp:1316)
23  godot                         	0x0000000106ad5dcb MethodBind1<Ref<InputEvent> const&>::call(Object*, Variant const**, int, Variant::CallError&) + 747 (method_bind.gen.inc:775)
24  godot                         	0x0000000106920d60 Object::call(StringName const&, Variant const**, int, Variant::CallError&) + 1456 (object.cpp:940)
25  godot                         	0x0000000106920660 Object::call(StringName const&, Variant const&, Variant const&, Variant const&, Variant const&, Variant const&) + 272 (object.cpp:865)
26  godot                         	0x000000010578c829 SceneTree::call_group_flags(unsigned int, StringName const&, StringName const&, Variant const&, Variant const&, Variant const&, Variant const&, Variant const&) + 1785 (scene_tree.cpp:267)
27  godot                         	0x000000010578da20 SceneTree::input_event(Ref<InputEvent> const&) + 432 (scene_tree.cpp:422)
28  godot                         	0x000000010386a2fa InputDefault::_parse_input_event_impl(Ref<InputEvent> const&, bool) + 7130 (input_default.cpp:442)
29  godot                         	0x000000010386870f InputDefault::parse_input_event(Ref<InputEvent> const&) + 31 (input_default.cpp:260)
30  godot                         	0x000000010386c24a InputDefault::flush_accumulated_events() + 90 (input_default.cpp:671)
31  godot                         	0x0000000103857674 OS_OSX::process_events() + 276 (os_osx.mm:2606)
32  godot                         	0x0000000103857c5f OS_OSX::run() + 175 (os_osx.mm:2682)
33  godot                         	0x000000010385f814 main + 1444 (godot_main_osx.mm:100)
34  libdyld.dylib                 	0x00007fff73b293d5 start + 1

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x00000001179385c0  rcx: 0x00007ffeec3b1fa8  rdx: 0x0000000000000000
  rdi: 0x0000000000000307  rsi: 0x0000000000000006  rbp: 0x00007ffeec3b1fe0  rsp: 0x00007ffeec3b1fa8
   r8: 0x00000000000130a8   r9: 0x00007fffaa209048  r10: 0x0000000000000000  r11: 0x0000000000000206
  r12: 0x0000000000000307  r13: 0x0000000000000000  r14: 0x0000000000000006  r15: 0x000000000000002d
  rip: 0x00007fff73c642c6  rfl: 0x0000000000000206  cr2: 0x00007fffaa207188

Logical CPU:     0
Error Code:      0x02000148
Trap Number:     133

I found the issue but I cannot really tell why exactly is segfaults.
The issue is this line: https://github.com/godotengine/godot/blob/master/editor/plugins/animation_player_editor_plugin.cpp#L326
Any suggestions? I can't seem to get my head around it... :sweat_smile:

probably caused by same reason.
can't control easing.


WIP: widget showcase

direct link https://widget-showcase.ratatui.pages.dev/showcase/widgets/

+1, nice.

I'm going to merge this as incomplete, the latest has instructions on how to contribute linking to https://github.com/ratatui-org/website/issues/249


can not run the code

@rwightman ,
i am so appreciated with your great job. i try to run imagenet_train.py, but it does not run correctly.
i do not know how to place the data. i have no idea of what type of data, and the architecture of data.
when i run to 'feed = FeedImagesWithLabels(dataset=dataset, processor=processor)'
it cames this  error:

It requires the Imagenet (or an Imagenet like dataset) to be encoded in sharded TF records format.
The scripts required to convert the imagenet dataset into records is in https://github.com/rwightman/tensorflow-litterbox/tree/master/litterbox/data
Those scripts were taken from Google's earlier Inception network and preprocessing scripts at https://github.com/tensorflow/models/tree/master/inception/inception/data
Since I wrote this code to learn about Tensorflow, Google themselves have released a number of the newer networks with trained weights that I built here including Inception V4 and Inception-Resnet V2. I'd recommend using them if you're looking to actual run the models vs a learning exercise: https://github.com/tensorflow/models/tree/master/slim/nets
My models are likely out of date/not working with the latest Tensorflow releases...


[README] Fix "swift" capitalization

A capitalized "Swift" matches usage in the rest of the README.

Thanks!


App Update: Update Icon in Nav and Sidebar

As a run app user, I would like a visual indicator that I need to update my app in the nav, so that I know to check out the 'about' tab for the latest version.
Acceptance Criteria

When user's Run App version is behind the latest Run App version:
-- Display visual indicator (orange dot) on 'About' icon in left nav tab
-- Display visual indicator (orange dot) on 'About' icon sidebar nav

Design

https://projects.invisionapp.com/d/main#/console/13154070/277137159/comments
Note design does not show left nav icon or orange dot (@howisthisnamenottakenyet)

Closed by 1125


chore: Remove ValueIds from SSA

Description
Problem*
Summary*
Removes ValueIds from SSA to reduce memory usage and hopefully improve compiler performance as well.

ValueIds are replaced by the Value enum itself, which is now thinner and implements Copy.
Several functions for iterating over values (block_parameters, instruction_results) now no longer require references to the DFG, so we don't need as much cloning in several passes.
Related to the previous point, values can be created much more often without referencing the DFG at all now, e.g. Value::constant just needs a field and a type since we don't need the separate map to keep each valueid unique to each constant value any more. Similarly, even Value::Instruction only needs an instruction id and a position. No need to store instruction id values in an external map in the dfg. This means we can get rid of quite a few fields on the DFG to save memory.
DFG::set_value_from_id can no longer mutate the value a ValueId points to, and instead relies solely on the internal map between values.

Additional Context
The integration tests are currently all passing, but there is a stack overflow somewhere within the test runner when running the unit tests, in between running the actual tests.
I have not started migrating all the SSA parser tests in the evaluator, these are expected to be failing currently since the display of valueids has changed.
Documentation*
Check one:

[x] No documentation needed.
[ ] Documentation included in this PR.
[ ] [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist*

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Initial results are very ungood, I think this is because FieldElement is 256bits causing Value to be 320 bits.
I'll re-add constant ids which should bring Value down to 96 bits. If we could embed the enum tag in the value somehow we could get it to 64.

Value's size has been reduced, although I'm unsure why the changes aren't more dramatic. I'd think removing the instruction_results map alone would have been a decent improvement. We're also cloning Vecs less throughout. I think I'll have to profile this more before fixing the ssa parser but as is this may not be worth merging with the regression in ram_blowup_regression.

Potentially an increased size of the replaced values map due to holding the actual values now?

Yes, but even then the increase is only from 32 to 64 bits which I'd expect to be offset by the other removals in this PR.

From manually timing programs, it seems this PR is about ~7% faster compiling programs compared to master

After some more perf testing, I'm going to close this PR. Testing it against master on rollup-base-private, this PR is compiling in ~90s compared to master's ~60s. Unsure if this is from the same regression as conditional_1 but this PR has been enough of a rabbit hole already that I'd rather close it.


tear-out should not require you to drag outside of the window

Currently you have to drag a tile until it is entirely outside of the windows bounds. I think it should tear out as soon as you drag beyond the favourites pane bounds (possibly plus a small tolerance).
i.e. copy Chrome ;-)

Would this also be the behaviour for tear in? I.e. the card will only tear in when intersected with a favourites pane.

Closed by #440


feat(#1195): Global checkbox behavior

closes #1195
This RP activates the global checkbox when all visible records are checked

"Deselect all" by clicking the global action checkbox cannot be applied with this logic.


Bug/injector strictdi

Fix the angular error:
[$injector:strictdi] $pgCheckout is not using explicit annotation and cannot be invoked in strict mode

Also, please, remember to publish the updates to npm as well. The current version is different from this repository.

Hi @herzinger, thanks for your pull request! :+1:
I have noticed that you have reindented a big block of code in your PR. Although we like good indentation and we welcome it, we suggest that you send indentation fixes in a separate PR, for traceability reasons.
If you don't mind, please rebase your commits, keeping only the needed changes to fix the issue, and be welcome to send another PR with indentation fixes! :)
Thanks again for you contribution!!

Sorry, my IDE is configured to automatically set indentation to 2 spaces. It should be okay now.
I can make a second PR with code organization if you'd like, but this one will fix the problem at hand.

Hey, thanks @herzinger, looks much better now :+1:
cc\ @grvcoelho @felquis, could you guys take care of this and also give some tests?

Please, give me a heads up when it's merged and published to NPM. I'm using it in production, so there should be no problems, but I would appreciate some testing, and I would prefere to use the package instead of my own copy of the file, as I'm doing right now.

:+1:  I was having the unknown provider error, thanks a ton for this!

@derekstavis The pull-request was merged, but it was never re-published to npm. The version there is still the same, and the bug is still there. You need to bump the version and publish it again for the change the apply.


Cannot read property 'push' of undefined(…)

Here is my store.js calling the routerMiddleware
// tooling modules
import { applyMiddleware, createStore, compose } from 'redux'
import { routerMiddleware } from 'react-router-redux'
import { browserHistory } from 'history'
import thunk from 'redux-thunk'
import promise from 'redux-promise-middleware'
import logger from 'redux-logger'

// rootReducer
import rootReducer from '../reducers'

// middleware
const middleware = applyMiddleware(
  thunk,
  promise(),
  logger(),
  routerMiddleware(browserHistory),
)

// default export
export default createStore(rootReducer, compose(
  middleware,
  window.devToolsExtension ? window.devToolsExtension() : f => f
));

Here is my main.js performing syncHistoryWithStore
// tooling modules
import React from 'react'
import { render as mount } from 'react-dom'
import { Provider } from 'react-redux'
import { Router, Route, browserHistory } from 'react-router'
import { syncHistoryWithStore } from 'react-router-redux'

// components
import Auth from './components/Auth'
import App from './components/App'

// styles
import styles from './styles.less'

// store
import store from './store'

// sync store and routing history
const history = syncHistoryWithStore(browserHistory, store)

// mounting
const root = document.getElementById('root')
mount(
  <Provider store={store}>
    <Router history={history}>
      <Route path="/" component={Auth}></Route>
        <Route path="/app(/:view)" component={App}></Route>
    </Router>
  </Provider>
,root)

Here is my rootReducer applying the routerReducer
// tooling modules
import { combineReducers } from 'redux'
import { routerReducer as routing } from 'react-router-redux'

// reducers
import auth from './auth'

// combine and export reducers
export default combineReducers({
  routing,
  auth,
})

Here is my App.js component calling and firing push
// tooling modules
import React, { Component } from 'react'
import { connect } from 'react-redux'
import { push } from 'react-router-redux'

// connect to store
@connect((state) => {
  return {
    isAuthenticated: state.auth.isAuthenticated
  }
})

export default class App extends Component {
  componentWillMount() {
    if (!this.props.isAuthenticated) {
      this.props.dispatch(push('/'))
    }
  }
  render() {
    return (

bye world!

    )
  }
}

Now the action gets dispatched with this error:

Have tried few variations in the code and tried calling the push method on different places, but to no  avail.

import { browserHistory } from 'history' This should be importing from react-router.

Haha that was a much smaller change then what I was expecting. Thanks @timdorr.

import { browserHistory } from 'react-router' still don't work...

├─┬<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>deduped
├──<EMAIL_ADDRESS>import { browserHistory } from 'react-router'
browserHistory.push(...
Uncaught TypeError: Cannot read property 'push' of undefined !!!!!!!!!!!!!!!!!!!!!!!!!!!

@Jekshmek You're using the wrong version of react-router. This version is for react-router v2/3.


types package not found?

Hello,
As per readme, trying to install typescript package.
npm i @types/react-leaflet-location-picker -D
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@types%2freact-leaflet-location-picker - Not found

https://www.npmjs.com/package/%40types%2Freact-leaflet-location-picker brings me to npm login page.
What am I doing wrong?
@Ben-Bourne

Thanks for raising the issue. It seems theres something wrong with the setup, the types should still be included in the package anyway so it shouldn't be a hinderance but I'll try and get a patch out to fix it soon.


Crash when instantiating SpoutReceiver on standalone DX12 build, Unity 2<IP_ADDRESS>b, GTX1660 SUPER

I have a standalone Unity build running on a GTX1660 SUPER.
At a certain moment I try to instantiate a prefab with a SpoutReceiver on it.
The SpoutReceiver renders to a render texture, the "renderer" field is not set.
The render texture is displayed via a RawImage on a UI canvas.
During development, it works in the editor on my laptop with a RTX 2060.
In the build on a GTX1660 SUPER, it crashes with the following error:
d3d12 : CreateCommittedResource 'TexturesD3D12::CreateTextureInternal() Texture' (1920 x 1080) format 72 failed (887a0005).
	Device Remove Reason (HRESULT): 0x887a002b
	Device Memory Stats:
		Local AvailableForReservation: 2739 MB, Budget: 5223 MB, CurrentUsage: 1983 MB, CurrentReservation: 64 MB
		Non-local AvailableForReservation: 1867 MB, Budget: 3539 MB, CurrentUsage: 393 MB, CurrentReservation: 0 MB
d3d12: failed to create 2D texture id=457 w=1920 h=1080 mips=1 d3dfmt=72
d3d12 : CreateCommittedResource 'GfxDeviceD3D12::ReserveScratchMemorySlow() Scratch' (1228800 x 1) format 0 failed (887a0005).
	Device Remove Reason (HRESULT): 0x887a002b
	Device Memory Stats:
		Local AvailableForReservation: 2739 MB, Budget: 5223 MB, CurrentUsage: 1983 MB, CurrentReservation: 64 MB
		Non-local AvailableForReservation: 1867 MB, Budget: 3539 MB, CurrentUsage: 393 MB, CurrentReservation: 0 MB
Crash!!!

Does it reproduce with the sample project (the project contained in this repository)?

The sample project also crashes.
I did the following:

Downloaded the repository
Opened the project with Unity 2<IP_ADDRESS>b, which upgraded some things
Switched the render API from directx11 to directx12
Made a build of the "Test" scene

The reason why it crashes is different, but it also seems to be related to DirectX 12 memory management:
Device removed reason (887a0001).
GfxDevice was not out of Local memory
Local memory usage:
 Budget:<PHONE_NUMBER>
 CurrentUsage: 458534912
 AvailableForReservation: 67108864
 CurrentReservation:<PHONE_NUMBER>
GfxDevice was not out of Non-Local memory
Non-Local memory usage:
 Budget:<PHONE_NUMBER>
 CurrentUsage: 163983360
 AvailableForReservation: 0
 CurrentReservation:<PHONE_NUMBER>
Set -force-d3d12-debug for more information on device removal
Crash!!!

I'm not bound to DirectX12 for my project. I might go back to DirectX11 for now. I've read that one of the big differences between DX11 and DX12 is memory management, so the source of my problem might very well lie there.

Thanks for the clarification.
I only found very few similar cases. Unfortunately, the root cause of the problem is unknown. Sometimes it disappears by upgrading the graphics driver.
I'd recommend switching to DX11 if it reproduces with the latest driver.

Switching to DX11 fixes the problem. Thanks for looking into it!

I'm closing this issue. Although the issue still exists, there is nothing to do on my side at the moment. I'll reopen it when I get more information about it.


Fix mutated values after validation in constructor

Change Summary

Fix mutated values after validation in constructor:

use a copy of previously validated fields to feed next validators
add tests, both at construction time but also at assignement (even if it's not a problem because a single field is validated)

Related issue number
Closes #4273

Checklist

[x] Unit tests for the changes exist
[x] Tests pass on CI and coverage remains at 100%
[ ] Documentation reflects the changes where applicable
[ ] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)
[ ] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

This will have a significant impact on performance. I'm opposed to it. I'll reply more on the issue.


fix: Require admin user for users/{user_id}, closes #413

I think in the frontend this route is only used by admins.

I think in the frontend this route is only used by admins.

Correct


Added cord image to header in website

Looks pretty good.

Could you approve the PR please then?

Looking good


vm-latency, e2e: Add bridge NetworkAttachmentDefinition

Currently, the NetworkAttachmentDefinition for a bridge network is created on-the-fly in the e2e.sh script.
Add bridge NetworkAttachmentDefinition manifest as a file, so users could also consume it as an example.
Signed-off-by: Orel Misan<EMAIL_ADDRESS>

@EdDev we have an example for SR-IOV NetworkAttachmentDefinition at checkups/kubevirt-vm-latency/manifests/sriov-network-attachment-definition.yaml

@EdDev we have an example for SR-IOV NetworkAttachmentDefinition at checkups/kubevirt-vm-latency/manifests/sriov-network-attachment-definition.yaml

It needs to be dropped.

@EdDev, I've opened PR #106 to delete the SR-IOV NetworkAttachmentDefinition manifest.


[Macros] Specify introduced names for example member macro.

This is required in https://github.com/apple/swift/pull/64097

@swift-ci please test


Update streamly

Need to update the streamly version bound.

The other two PRs are based on this. Please merge those as well once you merge this.

Can you add 9.2.1 CI as well?


TypeError when using middlewares

🐛 Current behavior
I would like to use middlewares like described here: https://www.algolia.com/doc/api-reference/widgets/middleware/vue/#examples
If I return the subscribe function like
function middleware({ instantSearchInstance }) {     return {       subscribe() {         // Do something when the InstantSearch instance starts.       },     }   }
`<AisInstantSearch
:middlewares="middleware"

.....`

I get this error in the console:
vue-instantsearch_vue3_es.js?v=5425bfd0:12830 Uncaught TypeError: (n6 || []).filter is not a function

vue 3.4.21
vue instantsearch 4.15.0

🔍 Steps to reproduce

create a function like https://www.algolia.com/doc/api-reference/widgets/middleware/vue/#examples
add to the instant search instance
reload page
open console

Live reproduction
code sandbox has a node js error...
💭 Expected behavior
I expect to not see a javascript error
Package version
vue instantsearch 4.15.0
Operating system
macOS 14.4.1
Browser
1.64.116
Code of Conduct

[X] I agree to follow this project's Code of Conduct

sorry, my fault. realised now that the prop "middlewares" on instantSearch expects an array instead of a function


GH-1745 - Improve RetryTopicConfigurer flexibility

Just opening some doors for advanced users who want to have more control over the RetryTopicConfigurer. Since the PR from @apolci already covered many use cases through DI it didn't look like it was worth having another DI setup for this.

Hi @artembilan and @garyrussell, thanks a lot for your input! I've made the changes as suggested, please let me know if there's anything else.

Is there any known issues with this test? Doesn't look like anything related to this PR.
org.springframework.kafka.core.reactive.ReactiveKafkaProducerTemplateTransactionIntegrationTests.shouldSendOneRecordTransactionallyViaTemplateAsSenderRecordAndReceiveItExactlyOnce(ReactiveKafkaProducerTemplateTransactionIntegrationTests.java:319)

@tomazfernandes Yes, it's a known flaky test; the latest commit on main has a fix for it.
https://github.com/spring-projects/spring-kafka/commit/ad1ae60cd8fe98333b16696ba4c37aa5ad07a43a
Try rebasing your PR.

Hmmm - looks like my "fix" just moved the flakiness someplace else 😦


Add a 'question' issue template

This can be helpful for those who have questions about Calculator. @YojanProductions, please check this file as your guide for this task: https://github.com/ApplicationCoding/calculator/blob/question_issue_template/question_issue_template_for_YojanProductions'%20Task.txt

Are you doing it?

Please click the link sent with the description @YojanProductions. Just chat me if still struggling.

Re-assigned to @MKilo24

Maybe it's better to ask questions on Discussions?

Yes, I think that's better.


fixed issue-5126

Fixes the issue #5126
Added the intended labels to the tag from the issue.
Lint :+1:
Test :+1:

Abhinai Sai your emails are not known to GitHub and thus it is impossible to know if you have signed the Plone Contributor Agreement, which is required to merge this pull request.
Learn about the Plone Contributor Agreement: https://plone.org/foundation/contributors-agreement How to add more emails to your GitHub account: https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account

Abhinai Sai your emails are not known to GitHub and thus it is impossible to know if you have signed the Plone Contributor Agreement, which is required to merge this pull request.
Learn about the Plone Contributor Agreement: https://plone.org/foundation/contributors-agreement How to add more emails to your GitHub account: https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account

Abhinai Sai your emails are not known to GitHub and thus it is impossible to know if you have signed the Plone Contributor Agreement, which is required to merge this pull request.
Learn about the Plone Contributor Agreement: https://plone.org/foundation/contributors-agreement How to add more emails to your GitHub account: https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account

@sneridagh
Can you help me in this?

@abhinaisai2002 If you signed alteady the contributor agreement we are good, and it can be merged. If not, you need to follow the instructions in the contributor guide.
You pushed a npm lock file, please remove it. The changelog need to be only one line, take a look at other PRs as reference. Also please read the contributor guide in plone.org.
@Wagner3UB could you please review the changes?

I have already sign the document actually, but the error was still showing in the workflow checks

Abhinai Sai your emails are not known to GitHub and thus it is impossible to know if you have signed the Plone Contributor Agreement, which is required to merge this pull request.
Learn about the Plone Contributor Agreement: https://plone.org/foundation/contributors-agreement How to add more emails to your GitHub account: https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account

@stevepiercy The error is still showing even if i am a member of this organization. How to get rid of this issue,

@abhinaisai2002 it sounds like the emails on your Plone Contributor Agreement and GitHub do not match. Please follow @mister-roboto's helpful advice to resolve it.


MINOR: Remove tag from metric to measure process-rate on source nodes

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Call for review: @guozhangwang

test this please

Cherry-picked to 2.5


Test against Edge

Ideally we could set up saucelabs. At the very least need to do manual testing in all browsers before a release.

Just did a manual test and it works in Chrome, Firefox, Safari, and Edge.

I can get saucelabs set up next week, but if someone else wants to do it the steps are here: https://github.com/canjs/canjs/issues/3586. I'm not positive they're still 100% accurate.