text:
opal client error

Hi OPAL team, hmm, I started to get this error today for this repo. Any idea? Thanks!
➜ docker-compose up

[+] Building 13.2s (10/10) FINISHED
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 31B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for docker.io/authorizon/opal-client:latest                                                                                3.2s
 => [1/5] FROM docker.io/authorizon/opal-client:latest@sha256:1da4cc56616d777cef36d26de4d82916fc392afeba2aae5519afea19c7dccbcf                                                                                0.0s
 => [internal] load build context                                                                                0.1s
 => => transferring context: 1.30MB                                                                                0.1s
 => CACHED [2/5] WORKDIR /app/                                                                                0.0s
 => [3/5] COPY . ./                                                                                0.1s
 => [4/5] RUN python setup.py install                                                                                1.5s
 => [5/5] RUN pip install wait-for-it                                                                                8.1s
 => exporting to image                                                                                0.1s
 => => exporting layers                                                                                0.1s
 => => writing image sha256:4b5659aa6f2b54c312ba3b93c55bc0d3c509181ef872aff0847ab07c2d7ba52b                                                                                0.0s
 => => naming to docker.io/library/opal-fetcher-postgres_opal_client                                                                                0.0s

Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
[+] Running 4/4
 ⠿ Container opal-fetcher-postgres_broadcast_channel_1  Created                                                                                0.0s
 ⠿ Container opal-fetcher-postgres_example_db_1         Created                                                                                0.0s
 ⠿ Container opal-fetcher-postgres_opal_server_1        Created                                                                                0.0s
 ⠿ Container opal-fetcher-postgres_opal_client_1        Recreated                                                                                0.1s
Attaching to broadcast_channel_1, example_db_1, opal_client_1, opal_server_1
broadcast_channel_1  |
broadcast_channel_1  | PostgreSQL Database directory appears to contain a database; Skipping initialization
broadcast_channel_1  |
broadcast_channel_1  | 2021-09-09 17:30:19.918 UTC [1] LOG:  starting PostgreSQL 13.4 on x86_64-pc-linux-musl, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 64-bit
broadcast_channel_1  | 2021-09-09 17:30:19.918 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
broadcast_channel_1  | 2021-09-09 17:30:19.918 UTC [1] LOG:  listening on IPv6 address "::", port 5432
broadcast_channel_1  | 2021-09-09 17:30:19.921 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
broadcast_channel_1  | 2021-09-09 17:30:19.924 UTC [21] LOG:  database system was shut down at 2021-09-09 17:29:57 UTC
broadcast_channel_1  | 2021-09-09 17:30:19.937 UTC [1] LOG:  database system is ready to accept connections
example_db_1         |
example_db_1         | PostgreSQL Database directory appears to contain a database; Skipping initialization
example_db_1         |
example_db_1         | 2021-09-09 17:30:20.076 UTC [1] LOG:  starting PostgreSQL 13.4 (Debian 13.4-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
example_db_1         | 2021-09-09 17:30:20.076 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
example_db_1         | 2021-09-09 17:30:20.076 UTC [1] LOG:  listening on IPv6 address "::", port 5432
example_db_1         | 2021-09-09 17:30:20.079 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
example_db_1         | 2021-09-09 17:30:20.084 UTC [27] LOG:  database system was shut down at 2021-09-09 17:29:57 UTC
example_db_1         | 2021-09-09 17:30:20.090 UTC [1] LOG:  database system is ready to accept connections
opal_server_1        | [2021-09-09 17:30:21 +0000] [1] [INFO] Starting gunicorn 20.1.0
opal_server_1        | [2021-09-09 17:30:21 +0000] [1] [INFO] Listening at: http://0.0.0.0:7002 (1)
opal_server_1        | [2021-09-09 17:30:21 +0000] [1] [INFO] Using worker: uvicorn.workers.UvicornWorker
opal_server_1        | [2021-09-09 17:30:21 +0000] [9] [INFO] Booting worker with pid: 9
opal_server_1        | [2021-09-09 17:30:21 +0000] [10] [INFO] Booting worker with pid: 10
opal_server_1        | [2021-09-09 17:30:21 +0000] [11] [INFO] Booting worker with pid: 11
opal_server_1        | [2021-09-09 17:30:21 +0000] [12] [INFO] Booting worker with pid: 12
opal_server_1        | 2021-09-09T17:30:21.657897+0000 |opal_common.authentication.signer       | INFO  | OPAL was not provided with JWT encryption keys, cannot verify api requests!
opal_server_1        | 2021-09-09T17:30:21.709369+0000 |opal_common.authentication.signer       | INFO  | OPAL was not provided with JWT encryption keys, cannot verify api requests!
opal_server_1        | 2021-09-09T17:30:21.736570+0000 |opal_server.server                      | INFO  | triggered startup event
opal_server_1        | 2021-09-09T17:30:21.736989+0000 |opal_common.topics.publisher            | INFO  | started topic publisher
opal_server_1        | 2021-09-09T17:30:21.737376+0000 |opal_server.server                      | INFO  | leadership lock acquired, leader pid: 9
opal_server_1        | 2021-09-09T17:30:21.737518+0000 |opal_server.server                      | INFO  | listening on webhook topic: 'webhook'
opal_server_1        | 2021-09-09T17:30:21.738816+0000 |fastapi_websocket_pubsub.event_notifier | INFO  | New subscription {'id': '41deef66f4714d4da2edec6ef1078b0b', 'subscriber_id': '9080fb2e6a82434095246fa9cda352b7', 'topic': 'webhook', 'callback': functools.partial(<function trigger_repo_watcher_pull at 0x7fc532fb0310>, <opal_server.policy.watcher.task.RepoWatcherTask object at 0x7fc532fb3640>), 'notifier_id': None}
opal_server_1        | 2021-09-09T17:30:21.739108+0000 |opal_server.policy.watcher.task         | INFO  | Launching repo watcher
opal_server_1        | 2021-09-09T17:30:21.739778+0000 |opal_common.git.repo_cloner             | INFO  | Cloning repo from 'https://github.com/authorizon/opal-example-policy-repo' to '/regoclone'
opal_server_1        | 2021-09-09T17:30:21.739956+0000 |opal_common.git.repo_cloner             | INFO  | Repo already exists in '/regoclone'
opal_server_1        | 2021-09-09T17:30:21.800354+0000 |opal_server.server                      | INFO  | triggered startup event
opal_server_1        | 2021-09-09T17:30:21.800808+0000 |opal_common.topics.publisher            | INFO  | started topic publisher
opal_server_1        | 2021-09-09T17:30:21.854116+0000 |opal_common.authentication.signer       | INFO  | OPAL was not provided with JWT encryption keys, cannot verify api requests!
opal_server_1        | 2021-09-09T17:30:21.906423+0000 |opal_server.server                      | INFO  | triggered startup event
opal_server_1        | 2021-09-09T17:30:21.906625+0000 |opal_common.topics.publisher            | INFO  | started topic publisher
opal_server_1        | 2021-09-09T17:30:21.956982+0000 |opal_common.authentication.signer       | INFO  | OPAL was not provided with JWT encryption keys, cannot verify api requests!
opal_server_1        | 2021-09-09T17:30:22.013798+0000 |opal_server.server                      | INFO  | triggered startup event
opal_server_1        | 2021-09-09T17:30:22.014042+0000 |opal_common.topics.publisher            | INFO  | started topic publisher
opal_client_1        | [2021-09-09 17:30:22 +0000] [9] [INFO] Starting gunicorn 20.1.0
opal_client_1        | [2021-09-09 17:30:22 +0000] [9] [INFO] Listening at: http://0.0.0.0:7000 (9)
opal_client_1        | [2021-09-09 17:30:22 +0000] [9] [INFO] Using worker: uvicorn.workers.UvicornWorker
opal_client_1        | [2021-09-09 17:30:22 +0000] [11] [INFO] Booting worker with pid: 11
opal_client_1        | 2021-09-09T17:30:22.776529+0000 |opal_common.fetcher.fetcher_register    | INFO  | Loading FetcherProvider 'FastApiRpcFetchProvider' found at: <class 'opal_common.fetcher.providers.fastapi_rpc_fetch_provider.FastApiRpcFetchProvider'>
opal_client_1        | 2021-09-09T17:30:22.776886+0000 |opal_common.fetcher.fetcher_register    | INFO  | Loading FetcherProvider 'HttpFetchProvider' found at: <class 'opal_common.fetcher.providers.http_fetch_provider.HttpFetchProvider'>
opal_client_1        | 2021-09-09T17:30:22.802421+0000 |opal_common.fetcher.fetcher_register    | INFO  | Loading FetcherProvider 'PostgresFetchProvider' found at: <class 'opal_fetcher_postgres.provider.PostgresFetchProvider'>
opal_client_1        | 2021-09-09T17:30:22.802631+0000 |opal_common.fetcher.fetcher_register    | INFO  | Fetcher Register loaded
opal_client_1        | 2021-09-09T17:30:22.825239+0000 |opal_client.opa.runner                  | INFO  | Launching opa runner
opal_client_1        | 2021-09-09T17:30:22.826799+0000 |opal_client.opa.runner                  | INFO  | Running OPA inline: opa run --server --addr=:8181 --authentication=off --authorization=off --log-level=info
opal_client_1        | 2021-09-09T17:30:22.842910+0000 |opal_client.opa.logger                  | INFO  | Initializing server. {'addrs': [':8181'], 'diagnostic-addrs': [], 'time': '2021-09-09T17:30:22Z'}
opal_server_1        | 2021-09-09T17:30:23.451689+0000 |opal_common.git.repo_watcher            | INFO  | Launching polling task, interval: 30 seconds
opal_client_1        | 2021-09-09T17:30:23.834381+0000 |opal_client.opa.runner                  | INFO  | Running OPA initial start callbacks
opal_client_1        | 2021-09-09T17:30:23.834992+0000 |opal_client.data.updater                | INFO  | Launching data updater
opal_client_1        | 2021-09-09T17:30:23.835351+0000 |opal_client.policy.updater              | INFO  | Launching policy updater
opal_client_1        | 2021-09-09T17:30:23.835596+0000 |opal_client.data.updater                | INFO  | Subscribing to topics: ['policy_data']
opal_client_1        | 2021-09-09T17:30:23.836373+0000 |opal_client.policy.updater              | INFO  | Subscribing to topics: ['policy:.']
opal_client_1        | 2021-09-09T17:30:23.837027+0000 |fastapi_websocket_pubsub.pub_sub_client | INFO  | Trying to connect to Pub/Sub server - ws://opal_server:7002/ws
opal_client_1        | 2021-09-09T17:30:23.837917+0000 |fastapi_websocket_rpc.websocket_rpc_c...| INFO  | Trying server - ws://opal_server:7002/ws
opal_client_1        | 2021-09-09T17:30:23.843181+0000 |fastapi_websocket_pubsub.pub_sub_client | INFO  | Trying to connect to Pub/Sub server - ws://opal_server:7002/ws
opal_client_1        | 2021-09-09T17:30:23.843570+0000 |fastapi_websocket_rpc.websocket_rpc_c...| INFO  | Trying server - ws://opal_server:7002/ws
opal_server_1        | 2021-09-09T17:30:23.849333+0000 |fastapi_websocket_pubsub.event_broadc...| INFO  | Listening for incoming events from broadcast channel (first listener started)
opal_server_1        | 2021-09-09T17:30:23.849735+0000 |fastapi_websocket_pubsub.event_broadc...| INFO  | Spawning broadcast listen task
opal_server_1        | 2021-09-09T17:30:23.874777+0000 |fastapi_websocket_pubsub.event_broadc...| INFO  | Subscribing to ALL TOPICS, and sharing messages with broadcast channel
opal_server_1        | 2021-09-09T17:30:23.875580+0000 |fastapi_websocket_pubsub.event_notifier | INFO  | New subscription {'id': '1d521aff17ce49cba19c32833ff51f7c', 'subscriber_id': '95cfad20c966449c93fd01fe5eae0fae', 'topic': '__EventNotifier_ALL_TOPICS__', 'callback': <bound method EventBroadcaster.__broadcast_notifications__ of <fastapi_websocket_pubsub.event_broadcaster.EventBroadcaster object at 0x7fc532fb7580>>, 'notifier_id': None}
opal_server_1        | 2021-09-09T17:30:23.876083+0000 |fastapi_websocket_rpc.websocket_rpc_e...| INFO  | Client connected
opal_server_1        | 2021-09-09T17:30:23.876830+0000 |fastapi_websocket_pubsub.event_broadc...| INFO  | Starting broadcaster listener
opal_server_1        | 2021-09-09T17:30:23.894454+0000 |fastapi_websocket_rpc.websocket_rpc_e...| INFO  | Client connected
opal_server_1        | 2021-09-09T17:30:23.904230+0000 |fastapi_websocket_pubsub.event_notifier | INFO  | New subscription {'id': 'c7e4128addde41f9b41e78d6e21bb9c7', 'subscriber_id': '96aa370defc74f14ab2ace2ee874faa3', 'topic': 'policy_data', 'callback': <function RpcEventServerMethods.subscribe.<locals>.callback at 0x7fc532a8fe50>, 'notifier_id': None}
opal_client_1        | 2021-09-09T17:30:23.908319+0000 |opal_client.data.updater                | INFO  | Connected to server
opal_client_1        | 2021-09-09T17:30:23.908431+0000 |opal_client.data.updater                | INFO  | Performing data configuration, reason: Initial load
opal_server_1        | 2021-09-09T17:30:23.908219+0000 |fastapi_websocket_pubsub.event_notifier | INFO  | New subscription {'id': '17bb79917a5e4d478fbd707a1fd535e5', 'subscriber_id': '3b5a87e12519497ebce614d10932d49b', 'topic': 'policy:.', 'callback': <function RpcEventServerMethods.subscribe.<locals>.callback at 0x7fc532a8fdc0>, 'notifier_id': None}
opal_client_1        | 2021-09-09T17:30:23.908553+0000 |opal_client.data.updater                | INFO  | Getting data-sources configuration from 'http://opal_server:7002/data/config'
opal_client_1        | 2021-09-09T17:30:23.911477+0000 |opal_client.policy.updater              | INFO  | Connected to server
opal_client_1        | 2021-09-09T17:30:23.911853+0000 |opal_client.policy.updater              | INFO  | Refetching policy code (full bundle)
opal_server_1        | 2021-09-09T17:30:23.914931+0000 |opal_server.data.api                    | INFO  | Serving source configuration
opal_server_1        | 2021-09-09T17:30:23.915966+0000 |uvicorn.protocols.http.httptools_impl   | INFO  | 172.25.0.5:60762 - "GET /data/config HTTP/1.1" 200
opal_client_1        | 2021-09-09T17:30:23.917804+0000 |opal_client.data.updater                | INFO  | Triggering data update with id: ca7697c68c3f4c489bd4bc663a0eb82d
opal_client_1        | 2021-09-09T17:30:23.918044+0000 |opal_client.data.updater                | INFO  | Fetching policy data
opal_client_1        | 2021-09-09T17:30:23.918305+0000 |opal_client.data.fetcher                | INFO  | Fetching data from url: postgresql://postgres@example_db:5432/postgres
opal_server_1        | 2021-09-09T17:30:23.936952+0000 |uvicorn.protocols.http.httptools_impl   | INFO  | 172.25.0.5:60764 - "GET /policy?path=. HTTP/1.1" 200
opal_client_1        | 2021-09-09T17:30:23.936638+0000 |fastapi_websocket_pubsub.pub_sub_client | INFO  | Connected to PubSub server ws://opal_server:7002/ws
opal_client_1        | 2021-09-09T17:30:23.939081+0000 |opal_client.policy.updater              | INFO  | got policy bundle, commit hash: '6d849b1ce92bae05c31146470e66e07c3c41b164'
opal_client_1        | 2021-09-09T17:30:23.942061+0000 |opal_client.opa.logger                  | INFO  | Received request.    GET /v1/policies
opal_client_1        | 2021-09-09T17:30:23.942817+0000 |opal_client.opa.logger                  | INFO  | Sent response.       GET /v1/policies -> 200
opal_client_1        | 2021-09-09T17:30:23.944976+0000 |opal_client.opa.logger                  | INFO  | Received request.    PUT /v1/data
opal_client_1        | 2021-09-09T17:30:23.945914+0000 |opal_client.opa.logger                  | INFO  | Sent response.       PUT /v1/data -> 204
example_db_1         | 2021-09-09 17:30:23.948 UTC [35] ERROR:  relation "city" does not exist at character 15
example_db_1         | 2021-09-09 17:30:23.948 UTC [35] STATEMENT:  SELECT * from city;
opal_client_1        | 2021-09-09T17:30:23.948788+0000 |opal_client.opa.logger                  | INFO  | Received request.    PUT /v1/policies/rbac.rego
opal_client_1        | 2021-09-09T17:30:23.956322+0000 |opal_client.opa.logger                  | INFO  | Sent response.       PUT /v1/policies/rbac.rego -> 200
opal_client_1        | 2021-09-09T17:30:23.958569+0000 |opal_client.opa.logger                  | INFO  | Received request.    PUT /v1/policies/utils.rego
opal_client_1        | 2021-09-09T17:30:23.961442+0000 |opal_client.opa.logger                  | INFO  | Sent response.       PUT /v1/policies/utils.rego -> 200
opal_client_1        | 2021-09-09T17:30:23.962971+0000 |fastapi_websocket_pubsub.pub_sub_client | INFO  | Connected to PubSub server ws://opal_server:7002/ws
example_db_1         | 2021-09-09 17:30:24.421 UTC [35] ERROR:  current transaction is aborted, commands ignored until end of transaction block
example_db_1         | 2021-09-09 17:30:24.421 UTC [35] STATEMENT:  SELECT * from city;
example_db_1         | 2021-09-09 17:30:25.058 UTC [35] ERROR:  current transaction is aborted, commands ignored until end of transaction block
example_db_1         | 2021-09-09 17:30:25.058 UTC [35] STATEMENT:  SELECT * from city;
example_db_1         | 2021-09-09 17:30:27.559 UTC [35] ERROR:  current transaction is aborted, commands ignored until end of transaction block
example_db_1         | 2021-09-09 17:30:27.559 UTC [35] STATEMENT:  SELECT * from city;
opal_client_1        | 2021-09-09T17:30:33.938164+0000 |opal_client.data.fetcher                |ERROR  | Timeout while fetching url: postgresql://postgres@example_db:5432/postgres
opal_client_1        | Traceback (most recent call last):
opal_client_1        |
opal_client_1        |   File "/root/.local/bin/gunicorn", line 8, in <module>
opal_client_1        |     sys.exit(run())
opal_client_1        |     │   │    └ <function run at 0x7f4ef9412940>
opal_client_1        |     │   └ <built-in function exit>
opal_client_1        |     └ <module 'sys' (built-in)>
opal_client_1        |   File "/root/.local/lib/python3.8/site-packages/gunicorn/app/wsgiapp.py", line 67, in run
opal_client_1        |     WSGIApplication("%(prog)s [OPTIONS] [APP_MODULE]").run()
opal_client_1        |     └ <class 'gunicorn.app.wsgiapp.WSGIApplication'>
opal_client_1        |   File "/root/.local/lib/python3.8/site-packages/gunicorn/app/base.py", line 231, in run
opal_client_1        |     super().run()
opal_client_1        |   File "/root/.local/lib/python3.8/site-packages/gunicorn/app/base.py", line 72, in run
opal_client_1        |     Arbiter(self).run()
opal_client_1        |     │       └ <gunicorn.app.wsgiapp.WSGIApplication object at 0x7f4ef93ed7f0>
opal_client_1        |     └ <class 'gunicorn.arbiter.Arbiter'>
opal_client_1        |   File "/root/.local/lib/python3.8/site-packages/gunicorn/arbiter.py", line 202, in run
opal_client_1        |     self.manage_workers()
opal_client_1        |     │    └ <function Arbiter.manage_workers at 0x7f4ef8d22160>
opal_client_1        |     └ <gunicorn.arbiter.Arbiter object at 0x7f4ef93ed910>
opal_client_1        |   File "/root/.local/lib/python3.8/site-packages/gunicorn/arbiter.py", line 551, in manage_workers
opal_client_1        |     self.spawn_workers()
opal_client_1        |     │    └ <function Arbiter.spawn_workers at 0x7f4ef8d22280>
opal_client_1        |     └ <gunicorn.arbiter.Arbiter object at 0x7f4ef93ed910>
opal_client_1        |   File "/root/.local/lib/python3.8/site-packages/gunicorn/arbiter.py", line 622, in spawn_workers
opal_client_1        |     self.spawn_worker()
opal_client_1        |     │    └ <function Arbiter.spawn_worker at 0x7f4ef8d221f0>
opal_client_1        |     └ <gunicorn.arbiter.Arbiter object at 0x7f4ef93ed910>
opal_client_1        |   File "/root/.local/lib/python3.8/site-packages/gunicorn/arbiter.py", line 589, in spawn_worker
opal_client_1        |     worker.init_process()
opal_client_1        |     │      └ <function UvicornWorker.init_process at 0x7f4ef83fdca0>
opal_client_1        |     └ <uvicorn.workers.UvicornWorker object at 0x7f4ef83ff130>
opal_client_1        |   File "/root/.local/lib/python3.8/site-packages/uvicorn/workers.py", line 64, in init_process
opal_client_1        |     super(UvicornWorker, self).init_process()
opal_client_1        |           │              └ <uvicorn.workers.UvicornWorker object at 0x7f4ef83ff130>
opal_client_1        |           └ <class 'uvicorn.workers.UvicornWorker'>
opal_client_1        |   File "/root/.local/lib/python3.8/site-packages/gunicorn/workers/base.py", line 142, in init_process
opal_client_1        |     self.run()
opal_client_1        |     │    └ <function UvicornWorker.run at 0x7f4ef83fddc0>
opal_client_1        |     └ <uvicorn.workers.UvicornWorker object at 0x7f4ef83ff130>
opal_client_1        |   File "/root/.local/lib/python3.8/site-packages/uvicorn/workers.py", line 77, in run
opal_client_1        |     loop.run_until_complete(server.serve(sockets=self.sockets))
opal_client_1        |     │    │                  │      │             │    └ [<gunicorn.sock.TCPSocket object at 0x7f4ef83eef40>]
opal_client_1        |     │    │                  │      │             └ <uvicorn.workers.UvicornWorker object at 0x7f4ef83ff130>
opal_client_1        |     │    │                  │      └ <function Server.serve at 0x7f4ef8631d30>
opal_client_1        |     │    │                  └ <uvicorn.server.Server object at 0x7f4ef88f94c0>
opal_client_1        |     │    └ <method 'run_until_complete' of 'uvloop.loop.Loop' objects>
opal_client_1        |     └ <uvloop.Loop running=True closed=False debug=False>
opal_client_1        | > File "/usr/local/lib/python3.8/site-packages/opal_client-0.1.13-py3.8.egg/opal_client/data/fetcher.py", line 63, in handle_url
opal_client_1        |     response = await self._engine.handle_url(url, config=config)
opal_client_1        |                      │    │       │          │           └ {'fetcher': 'PostgresFetchProvider', 'query': 'SELECT * from city;', 'connection_params': {'password': 'postgres'}}
opal_client_1        |                      │    │       │          └ 'postgresql://postgres@example_db:5432/postgres'
opal_client_1        |                      │    │       └ <function FetchingEngine.handle_url at 0x7f4ef736f310>
opal_client_1        |                      │    └ <opal_common.fetcher.engine.fetching_engine.FetchingEngine object at 0x7f4ef88ed8e0>
opal_client_1        |                      └ <opal_client.data.fetcher.DataFetcher object at 0x7f4ef72fce20>
opal_client_1        |   File "/usr/local/lib/python3.8/site-packages/opal_common-0.1.13-py3.8.egg/opal_common/fetcher/engine/fetching_engine.py", line 104, in handle_url
opal_client_1        |     await asyncio.wait_for(wait_event.wait(), timeout)
opal_client_1        |           │       │        │          │       └ 10
opal_client_1        |           │       │        │          └ <function Event.wait at 0x7f4ef8760040>
opal_client_1        |           │       │        └ <asyncio.locks.Event object at 0x7f4ef6f09460 [unset]>
opal_client_1        |           │       └ <function wait_for at 0x7f4ef8769940>
opal_client_1        |           └ <module 'asyncio' from '/usr/local/lib/python3.8/asyncio/__init__.py'>
opal_client_1        |   File "/usr/local/lib/python3.8/asyncio/tasks.py", line 501, in wait_for
opal_client_1        |     raise exceptions.TimeoutError()
opal_client_1        |           │          └ <class 'asyncio.exceptions.TimeoutError'>
opal_client_1        |           └ <module 'asyncio.exceptions' from '/usr/local/lib/python3.8/asyncio/exceptions.py'>
opal_client_1        |
opal_client_1        | asyncio.exceptions.TimeoutError
opal_client_1        | 2021-09-09T17:30:33.949107+0000 |opal_client.data.updater                |ERROR  | Failed to fetch url postgresql://postgres@example_db:5432/postgres, got exception:
example_db_1         | 2021-09-09 17:30:35.103 UTC [35] ERROR:  current transaction is aborted, commands ignored until end of transaction block
example_db_1         | 2021-09-09 17:30:35.103 UTC [35] STATEMENT:  SELECT * from city;
example_db_1         | 2021-09-09 17:30:37.384 UTC [35] ERROR:  current transaction is aborted, commands ignored until end of transaction block
example_db_1         | 2021-09-09 17:30:37.384 UTC [35] STATEMENT:  SELECT * from city;
opal_server_1        | 2021-09-09T17:30:53.428806+0000 |opal_common.git.repo_watcher            | INFO  | Pulling changes from remote: 'origin'
opal_server_1        | 2021-09-09T17:30:55.551686+0000 |opal_common.git.repo_watcher            | INFO  | No new commits: HEAD is at '6d849b1ce92bae05c31146470e66e07c3c41b164'
example_db_1         | 2021-09-09 17:31:08.056 UTC [35] ERROR:  current transaction is aborted, commands ignored until end of transaction block
example_db_1         | 2021-09-09 17:31:08.056 UTC [35] STATEMENT:  SELECT * from city;
opal_server_1        | 2021-09-09T17:31:25.531347+0000 |opal_common.git.repo_watcher            | INFO  | Pulling changes from remote: 'origin'
opal_server_1        | 2021-09-09T17:31:27.180727+0000 |opal_common.git.repo_watcher            | INFO  | No new commits: HEAD is at '6d849b1ce92bae05c31146470e66e07c3c41b164'
opal_client_1        | 2021-09-09T17:31:32.875584+0000 |opal_client.opa.logger                  | INFO  | Received request.    GET /v1/data
opal_client_1        | 2021-09-09T17:31:32.876693+0000 |opal_client.opa.logger                  | INFO  | Sent response.       GET /v1/data -> 200
example_db_1         | 2021-09-09 17:31:45.503 UTC [35] ERROR:  current transaction is aborted, commands ignored until end of transaction block
example_db_1         | 2021-09-09 17:31:45.503 UTC [35] STATEMENT:  SELECT * from city;
opal_server_1        | 2021-09-09T17:31:57.159742+0000 |opal_common.git.repo_watcher            | INFO  | Pulling changes from remote: 'origin'
opal_server_1        | 2021-09-09T17:31:58.816467+0000 |opal_common.git.repo_watcher            | INFO  | No new commits: HEAD is at '6d849b1ce92bae05c31146470e66e07c3c41b164'

Seems the database got polluted, manually dropped all tables and created again solves the issue!

@Hongbo-Miao
For some reason the default behavior for docker compose is to reuse existing containers, even when not using volumes.
This is not very intuitive, because the db is not recreated every time you run compose - and indeed the db can be polluted.
The best way to circumnavigate this, is to run docker compose with --force-recreate.
this command will recreate all containers (from the docker image) and give you clean state on load:
docker compose up --force-recreate

@Hongbo-Miao
also, you can see in the output which containers are recreated and which ones are reused:
[+] Running 4/4
 ⠿ Container opal-fetcher-postgres_broadcast_channel_1  Created                                                                                0.0s
 ⠿ Container opal-fetcher-postgres_example_db_1         Created                                                                                0.0s
 ⠿ Container opal-fetcher-postgres_opal_server_1        Created                                                                                0.0s
 ⠿ Container opal-fetcher-postgres_opal_client_1        Recreated

I was using docker compose --build -V, and not work.
It is --force-recreate. Thanks for sharing!

authors: Hongbo-Miao asafc

repo: authorizon/opal-fetcher-postgres


text:
Hello!

Hi all -- I see that you're working here on a successor to oidc-client. That's great!
Often people don't know the protocol well enough and miss nuances that was done in oidc-client, so I'm happy to answer any questions about why something might have been done a certain way.
Thanks.

That support is offering is great, we really appreciate that! As you said there are many nuances. Our goal is to keep as much of the original API, design and features intact. We will post questions in this issue.

The CordovaI feature looks broken. Do you know if somebody still needs that feature? I am thinking about removing this completely.

What is the benefit for having an OidcClient and UserManager class? For the library it would be easier to have only one class...

The CordovaI feature looks broken. Do you know if somebody still needs that feature? I am thinking about removing this completely.

Yes, please remove it. AppAuth is the preferred way these days and is there is a reference implementation here that people can use instead.

What is the benefit for having an OidcClient and UserManager class? For the library it would be easier to have only one class...

OidcClient is the protocol class, and UserManager adds session management on top. That was the intent for the separation.

What is the benefit for having an OidcClient and UserManager class? For the library it would be easier to have only one class...

OidcClient is the protocol class, and UserManager adds session management on top. That was the intent for the separation.

I will make functions like createSigninRequest protected instead of public. Would mean if somebody wants to use it he must inherit from OidcClient like UserManager too, which makes sense. The exposed public API is cleaner though.

I will make functions like createSigninRequest protected instead of public. Would mean if somebody wants to use it he must inherit from OidcClient like UserManager too, which makes sense. The exposed public API is cleaner though.

The other thing you can do is just have the USerManager contain OidcClient instead. That way if someone is using OidcClient for raw protocol things, it's still usable.

The SessionMonitor code _start looks for user.session_state. But not all authority servers return a user session_state. In those cases the SessionMonitor makes nothing. Also if it would do something the check interval of 2sec (default) seems very small.
I will disable monitorSession by default for now.

@pamapa great work here. I would love to contribute in any way. What work items can I pick and work on?

@elfico Would be great if you find time for testing the 2.0.0-alpha2 or higher with your flow. Also reviewing the code regrading types would be nice. Additionally MonitorSession does not work when user.session_state is undefined and UserInfoService has a lot of duplicated code with ResponseValidator.

I also want to move to this library, but I am using it with response type of id_token. Is that supported with this library, as it looks that only possible value is code?

response_type=code + scope=openid should give back an id_token, which is supported.

@brockallen i guess we should still support the hybrid flow aka response_type=code id_token?

@brockallen v2.0.0 is now ready. Would be really nice if you could add a link from your oidc-client github project's README.md to this project. You may also add a npm install deprecated warning like:
npm WARN deprecated oidc-client@1.11.5: this library is no longer supported. Upgrade to oidc-client-ts.
or
npm WARN deprecated oidc-client@1.11.5: Please see https://github.com/IdentityModel/oidc-client-js#deprecated

@brockallen  a friendly ping, have you seen my comment above?

Hi, yes, sorry. What wording might you like on my side?

Something simple in your README.md, replacing the chapter "Looking for a new maintainer":
## Development stopped

This project halted its development in June 2021. The successor project oidc-client-ts can be found [here](https://github.com/authts/oidc-client-ts).

And a npm install deprecated warning (see comment above) would be really nice, as not everybody is visiting repository pages of libraries all the time...

source: gharchive/issue

authors: brockallen elfico pamapa selfrefactor

repo: authts/oidc-client-ts

license_type: permissive

license_source: github-api


text:
🛑 Do Práce na Kole - reg test § test.dopracenakole.cz is down

In 222e0c6, Do Práce na Kole - reg test § test.dopracenakole.cz (https://test.dopracenakole.cz) was down:

HTTP code: 502
Response time: 3883 ms

Resolved: Do Práce na Kole - reg test § test.dopracenakole.cz is back up in 23f6f31.

repo: auto-mat/automat-statuspage

license: MIT


text:
Error messages for group and member view

When changing enrollment status, approving, editing or deleting groups fails, there were no error messages shown to the user.

Coverage remained the same at 34.806% when pulling 98d88e09a9d58aea278c50642ddcaf5aa5b4232e on ui_error_messages into cea3e8b98206e3f4c635044f11add2aaf9637876 on master.

source: gharchive/pull-request

repo: autograde/aguis


text:
fix(ndt_scan_matcher): fix to pass clang-tidy's check

Description
(1)
To avoid warning: function 'callback_sensor_points_main' has cognitive complexity of 26 (threshold 25) [readability-function-cognitive-complexity], I changed from for statement to stl algorithm.
This change was made only to avoid warnings, and it is possible that readability has not improved but has actually decreased. I think it would be reasonable for this pull request to be judged as Reject on this reason. There is a possibility that it is better to properly separate the big function callback_sensor_points_main.
(2)
To solve warning: do not access members of unions; use (boost::)variant instead [cppcoreguidelines-pro-type-union-access], I added // NOLINT to those lines.
Tests performed
logging_simulator works well as before.
Effects on system behavior
There are no effects on system behavior.
Interface changes
There are no interface changes.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

This change was made only to avoid warnings, and it is possible that readability has not improved but has actually decreased. I think it would be reasonable for this pull request to be judged as Reject on this reason.

Honestly, I think the source code has become harder to understand :cry:

Thank you for your comment.
I will fix this pull request because I found it difficult to read when I read the changes again.

authors: KYabuuchi SakodaShintaro


text:
feat(planning_evaluator): rename to include/autoware/{package_name}

Description
Added autoware_ prefix to the package.
Renamed include/autoware_{package_name}/ to include/autoware/{package_name}.

Tests performed

Unit test
Effects on system behavior

Nothing
Interface changes

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

cc @yuki-takagi-66

I've confirmed that we can engage on psim


text:
refactor(compare_map_segmentation): add package name prefix of autoware_

Description
This PR adds the autoware_ prefix to the package name.
Changes are as following.

Folder name (appears as file renaming)
Package names in CMakeLists.txt, package.xml
README.md
Launch files $(find-pkg-share ...)
.github/CODEOWNERS

This PR do not contains any logic change.
Related links
Part of: https://github.com/autowarefoundation/autoware/issues/4569
How was this PR tested?

Tested Perception performance in the TIER IV Cloud environment.:
https://evaluation.tier4.jp/evaluation/reports/67843b47-8807-5ad2-b456-5105127cbc2c?project_id=prd_jt

Tested Planning_simulator in local machine:

Notes for reviewers
None.
Interface changes
None.
Effects on system behavior
None.

@badai-nguyen
There is a PR for this work, earlier than this.
https://github.com/autowarefoundation/autoware.universe/pull/7592
Please ask @esteve and get alignment.

@technolojin thanks for your notice,
@esteve I'm sorry for miss-checking that you already created the PR for compare_map_segmentation. I will close this PR if you can handle at your side? Please note that tier4_perception_launch/package.xml also need to be updated.
Otherwise, I can continue to handle it with my PR.

@esteve Since we would focus to complete prefix update this week, I will take responsibility for compare_map_segmentation package and open this PR for review.

I would like to ask review from you for this PR:

Regarding compare_map_segmentation @yukkysaito
Regarding tier4_planning_launch @takayuki5168 @kosuke55
Regarding  elevation_map_loader @Shin-kyoto
Regarding Map_loader @YamatoAndo  @KYabuuchi

@badai-nguyen I was away for the past two weeks, so I couldn't respond. Please check PRs before submitting a new one. Thanks for working on this, I'll close #7592

authors: badai-nguyen esteve technolojin


text:
Test pixrem sourcemaps support

https://github.com/gummesson/gulp-pixrem/issues/4

pixrem should be removed in the next version, so sourcemap support isn't exactly a high priority at this point

repo: avalanchesass/avalanche

license: mit

license_source: bigquery


text:
Enum as const so it can be used, don't add semicolon as it is invalid TS

This makes two changes to make the update to using enums functional.

Removes the errant semicolon that is added to the type declaration.
Declares enum as a const so it is available to the typescript compiler.

I've spent about an hour trying to figure out what is not matching between the snap test version. It looks like an extra space or something but I cannot find it...

@brettjurgens  updated to be much more concise.

@brettjurgens  on the change log what version should I put?

@raysuelzer just put it as "master" for now and when I do a release I'll swap that for the version

@brettjurgens   there you go!

Any timeline on getting this one shipped? Just hate having to fix the typescript errors whenever I update the schema. :)

Will ship tomorrow morning 😁
On Sun, Jul 22, 2018, 14:19 Raymond Suelzer notifications@github.com
wrote:

Any timeline on getting this one shipped? Just hate having to fix the
typescript errors whenever I update the schema. :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/avantcredit/gql2ts/pull/202#issuecomment-406889916,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABK4ngTdFAMojsQZQ0trg0DLM0hqsL8eks5uJNAlgaJpZM4VTT0g
.

--
This e-mail is only intended for the person(s) to whom it is addressed and
may contain confidential information.  Any unauthorized review, use,
disclosure, or distribution is prohibited. If you received this e-mail in
error, please notify the sender by reply e-mail and then delete this
message and any attachments from your system. Thank you for your
cooperation.

@raysuelzer released as 1.8.1

authors: brettjurgens raysuelzer


text:
feat: check on custom labels

Describe your changes
Issue ticket number and link
Checklist before requesting a review

[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] If it is a core feature, I have added thorough tests.

Codecov Report
Base: 71.97% // Head: 72.02% // Increases project coverage by +0.04% :tada:

Coverage data is based on head (64dc92b) compared to base (af2acba).
Patch coverage: 87.50% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #53      +/-   ##
==========================================
+ Coverage   71.97%   72.02%   +0.04%
==========================================
  Files          55       55
  Lines        2566     2574       +8
==========================================
+ Hits         1847     1854       +7
- Misses        719      720       +1

Impacted Files
Coverage Δ

src/wanna/core/utils/validators.py
67.81% <83.33%> (+1.14%)
:arrow_up:

src/wanna/core/models/base_instance.py
100.00% <100.00%> (ø)

src/wanna/core/models/gcp_profile.py
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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

authors: JacekHebda codecov-commenter

repo: avast/wanna-ml


text:
Fix https://github.com/aviatesk/JET.jl/issues/267

With this change OP's test shows the same result as
import Pkg

Pkg.status()

Codecov Report

Merging #276 (287bff9) into master (5e1edf6) will decrease coverage by 0.21%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##           master     #276      +/-   ##
==========================================
- Coverage   89.02%   88.80%   -0.22%
==========================================
  Files          10       10
  Lines        2223     2225       +2
==========================================
- Hits         1979     1976       -3
- Misses        244      249       +5

Impacted Files
Coverage Δ

src/toplevel/virtualprocess.jl
96.87% <50.00%> (-0.23%)
:arrow_down:

src/JET.jl
71.59% <0.00%> (-0.91%)
:arrow_down:

Continue to review full report at Codecov.

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

Maybe can you add a simple test in https://github.com/aviatesk/JET.jl/blob/master/test/test_misc.jl like:
@test to_simple_module_usages(:(import Pkg as P)) == Expr[:(import Pkg as P)]

authors: aviatesk codecov-commenter goerch


text:
Github automation Script

Description
This script allows user to completely automate github workflow. This script keeps track of changed files and generates a diff, then auto adds and commits(asks for a commit message) the changed files.
Fixes #(#223)
Have you read the Contributing Guidelines on Pull Requests?

[x] Yes

Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md
[x] My documentation follows Template for README.md
[x] My changes generate no new warnings
[x] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works.

@avinashkranjan Please review when you can.

@avinashkranjan Please review when you can.

repo: avinashkranjan/Amazing-Python-Scripts


text:
Using with-correlation-id scope separates the parent span

When tracing:with-correlation-id scope is used to change the correlation id, spans for all processors inside the scope gets separated from the original trace.
Example flow processors -

Generated traces for this setup shows two traces -

/api/* for api request received on apikit
create-shipment-sys for the flow ref inside the scope

hey @manikmagar - sorry for piggybacking on this, but i wondered if there is a way to get clearer names on APIKit calls?
Are there any config options to tell it to use parts of the http.target value as the trace name or something like that?
For example, /api/v1/sessions/venues/001/events/321 to be named as something like /api/v1/sessions/venues/{venueID}/events/{eventID} rather than "/api/v1/*" for everything

@StephenGoodall - I think that is something that is worth looking into, could you create that as a separate issue that we can track?

Yes, we have noticed the same issue. Using the With CorrelationID scope creates a new Trace ID which is undesirable as we also use the With CorrelationID scope to use an incoming transaction reference to be able to track a transaction through our systems which cannot be traced by the Trace ID alone

authors: StephenGoodall adesjardin hamerpr manikmagar


text:
Trouble getting the plugin to provide url at startup.

Hi, I'm having trouble getting the uni_links plugin to provide the URI at startup using getInitialLink. While I can get it to trigger an event using a stream this doesn't work when the app is first open.  I'm not sure if its a problem with the plugin or if I'm not doing something right.  Could I get some help. I'm not getting any errors. the getInitialLink function is just returning null.

Are you using the plugin with https:// URIs or custom scheme?

custom uri scheme.

Custom URI schemes are the easiest. They can be easily tested with little effort. They also work fine on the iOS Simulator.
Follow the guide in the (README.md)[https://github.com/avioli/uni_links#for-ios] line by line.
Here's the checklist:

[ ] Declare your Custom URI scheme in ios/Runner/Info.plist;
[ ] Add dart code for Initial Link (and on-change event);
[ ] Run app and quit/detach;
[ ] Ensure the app has terminated on the simulator/device by checking the recently used apps (aka app switcher). If not - flick it up to terminate it;
[ ] Run any of the testing commands from the README.md.

NOTE: The simulator/device may ask you if you want to open the link in the app.
The most common problem is that you cannot get the initial link, unless the app was terminated and then started, because of the Custom URI Link.
If you still have problems - clone the repo and open up the example project - it is setup for Custom URI scheme. Run the example app, terminate it and run any of the testing commands.

The plugin works once the app is loaded. If I run the app and then open up the link from a browser it works. It doesn't work if the app is not loaded and we load the app by clicking on the link. Then it just loads the app but doesn't return the initial link or execute the on change event.
I'm using an Ipod touch for my device, not the simulator.

I've tried what you've mentioned here as what I should do. Its not working. It won't provide the URI on launch. It works if the app is already loaded. But not on launch.

Thanks for the help. I think I just found the problem I was having. It was an issue with asynchronous function calls. not executing in time.

Just fyi - initial link should be ALWAYS the same if the app was started with one, no matter how late you request it.

thanks. I'll keep that in mind.


text:
Update dependency molecule-docker to v2

This PR contains the following updates:

Package
Type
Update
Change

molecule-docker
dev-dependencies
major
^1.1.0 -> ^2.0.0

Release Notes

ansible-community/molecule-docker
v2.0.0
Compare Source
Major Changes

Require molecule 4.0 or newer (#157) @ssbarnea
Require ansible-core 2.12 or newer (#156) @ssbarnea
Drop python 3.6 and 3.7 support (#141) @ziegenberg

Bugfixes

Require community-docker>=3.0.0a2 (#155) @ssbarnea
Add docker_host option in README (#148) @zhan9san
change IRC room from ansible-molecule to ansible-devtools (#133) @ziegenberg
Add platform to the Build an Ansible compatible image task (#122) @madrover

Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: poetry.lock
Installing v1 tool poetry v1.2.0
The canonical source for Poetry's installation script is now https://install.python-poetry.org. Please update your usage to reflect this.
Retrieving Poetry metadata

# Welcome to Poetry!

This will download and install the latest version of Poetry,
a dependency and package manager for Python.

It will add the `poetry` command to Poetry's bin directory, located at:

/home/ubuntu/poetry/1.2.0/bin

You can uninstall at any time by executing this script with the --uninstall option,
and these changes will be reverted.

Installing Poetry (1.2.0)
Installing Poetry (1.2.0): Creating environment
Installing Poetry (1.2.0): Installing Poetry
Installing Poetry (1.2.0): Creating script
Installing Poetry (1.2.0): Done

Poetry (1.2.0) is installed now. Great!

To get started you need Poetry's bin directory (/home/ubuntu/poetry/1.2.0/bin) in your `PATH`
environment variable.

Add `export PATH="/home/ubuntu/poetry/1.2.0/bin:$PATH"` to your shell configuration file.

Alternatively, you can call Poetry explicitly with `/home/ubuntu/poetry/1.2.0/bin/poetry`.

You can test that everything is set up by executing:

`poetry --version`

Poetry (version 1.2.0)
Installed v1 poetry in 12 seconds
Creating virtualenv ansible-role-flux-nuUqfyLY-py3.10 in /home/ubuntu/.cache/pypoetry/virtualenvs
Updating dependencies
Resolving dependencies...

Because molecule-docker (2.0.0) depends on molecule (>=4.0.0)
 and no versions of molecule-docker match >2.0.0,<3.0.0, molecule-docker (>=2.0.0,<3.0.0) requires molecule (>=4.0.0).
So, because ansible-role-flux depends on both molecule-docker (^2.0.0) and molecule (^3.5.2), version solving failed.

repo: avnes/ansible-role-flux


text:
Trace dont have user area code

Describe the bug
When application is down in third party package StackTrace didn't have pointer at user script who call thrown code.
In common php application, we have at least /var/www/public/index.php in start of trace.
In rr application first script is /var/www/vendor/avto-dev/roadrunner-laravel/bin/rr-worker
Because of that scripts that are based on information about the script that caused the error or use debug_backtrace may not work correctly with this behavior.
An example of that libraries is a laravel/telescope
https://github.com/laravel/telescope/blob/3.x/src/Watchers/FetchesStackTrace.php by default try to find first non vendor class, and with rr - we don't has no one.
This makes it impossible to work with the telescope.
This can be partially solved by changing the settings of the telescope (ignoring the vendor folder), but this will result to the incorrect initializer script being displayed in the telescope.
Expected behaviour
Caller script should be displayed in the trace.
Steps to reproduce the behavior:
Simple way - use laravel/telescope with php7.4 and going to queries page in telescope.
Direct way (debug) - throw exception in any vendor package - are you will see only vendors scripts in trace.
System information

PHP version(s): [7.4.2]
Package version(s): [3.0.2]
Telescope version: [3.0.0]

Can you try to make ln -s ./vendor/avto-dev/roadrunner-laravel/bin/rr-worker ./rr-worker and use this link as roadrunner worker?

If I use ln - I still get "file":"/var/www/vendor/avto-dev/roadrunner-laravel/src/Worker.php" in trace
If I copy ./vendor/avto-dev/roadrunner-laravel/bin/rr-worker to ./rr-worker than path is "file":"/var/www/rr-worker" - is is OK
Buth than I need edit file and add '.' path to Find Application Base Path block
https://github.com/avto-dev/roadrunner-laravel/blob/master/bin/rr-worker#L50
It would be nice to get this more native

Ok, one more try - replace file ./rr-worker with next content:
#!/usr/bin/env php
<?php

require __DIR__ . "/vendor/bin/rr-worker";

Do not forget to set x attribute - chmod +x ./rr-worker

This is more clean way in your case, I think

Unfortunately not =(

ERRO[0000] [http]: unable to connect to worker: PHP Fatal error:  strict_types declaration must be the very first statement in the script in /var/www/vendor/avto-dev/roadrunner-laravel/bin/rr-worker on line 4

And if i add strict_types to ./rr-worker and comment in vendor/bin/rr-worker i get error

ERRO[0000] [http]: unable to connect to worker: unexpected response, header is missing: signal: killed

Ok, cp ./vendor/avto-dev/roadrunner-laravel/bin/rr-worker . looks like last possible way in your case (if telescope package overriding is not allowed). This can helps you?

Closed due inactivity

authors: dmekhov tarampampam

repo: avto-dev/roadrunner-laravel


text:
JavaVersionDetector class fails with NumberFormatException on Temurin JDK 23 EA builds

The JavaVersionDetector class fails on specific version strings that java.version property can hold. In this case it's 23-beta, which results in:
Caused by: java.lang.NumberFormatException: For input string: "23-beta"
	at java.base@23-beta/java.lang.Integer.parseInt(Integer.java:588)
	at java.base@23-beta/java.lang.Integer.parseInt(Integer.java:685)
	at org.awaitility.core.JavaVersionDetector.getJavaMajorVersion(JavaVersionDetector.java:21)
	at org.awaitility.core.LambdaErrorMessageGenerator.getLambdaDetectionClassName(LambdaErrorMessageGenerator.java:86)
	at org.awaitility.core.LambdaErrorMessageGenerator.isLambdaClass(LambdaErrorMessageGenerator.java:30)
	at org.awaitility.core.AssertionCondition.generateDescriptionPrefix(AssertionCondition.java:87)
	at org.awaitility.core.AssertionCondition.getMatchMessage(AssertionCondition.java:73)
	at org.awaitility.core.AssertionCondition.lambda$new$0(AssertionCondition.java:54)
	at org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:248)
	at org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:235)

Consider using the Runtime.Version API which is available for JDK 11+
jshell> var v = Runtime.getRuntime().version();
v ==> 23-beta+14-ea

jshell> v.feature()
$3 ==> 23

Steps to reproduce:

Download a JDK 23 EA build from Adoptium. Example here: https://adoptium.net/temurin/nightly/?version=23
Run JavaVersionDetector.getJavaMajorVersion() on it.
Observe NumberFormatException

Aditional Info:
The existing code seems to not account for the - in 23-beta. See:
https://github.com/awaitility/awaitility/blob/fbe16add874b4260dd240108304d5c0be84eabc8/awaitility/src/main/java/org/awaitility/core/JavaVersionDetector.java#L6-L22

Got similar error with our CI/CD pileline java.lang.NumberFormatException: For input string: "17-ea"

Bumping minimum Java version from the current 1.8 to at least 9 (better yet, 11 as "lts") will provide access to Runtime.version() which will remove the need to parse the string.

authors: estekhin jerboaa manoj2411

repo: awaitility/awaitility


text:
Describe the process of color calibration

Feature request

What problem does this feature solve?
Currently it's not clear how to match my wled + led strip colors to the colors on my TV
What does the proposed API look like?
It might be just a page in docs somewhere, like this one
https://github.com/AEtHeLsYn/hyperion/wiki/Color-Calibration. I imagine it's somewhat outdated, given it's for another product and 8 years old.
How should this be implemented in your opinion?
But in a perfect world it's should be android app, of course, that looks at pictures of TV with ambilight enabled and changes settings on the fly
Are you willing to work on this yourself?
I'm not sure. I can help a bit, but I'll not sure how

I think the most important part is not having a "perfect white", but having colors matching TV as close as possible. My TV is constantly running is the "Night shift" or whatever this thing is called when the level of blues is lower than it should be.
So yes, my goal is not to make the colors pleasant, my goal is to make the match TV's colors as good as possible to have this "augmentation" effect. And this thingie, I think, can even be automated, at least for SDR.

At least for static images
...
my goal is to make the match TV's colors

So these are exactly the cases no. 1 and 3 described by me :wink: As I have already explained, from my point of view it is unrealistic and I will not undertake it myself, but I am open to suggestions along with their possible implementation in the code if changes are needed. So I leave this request feature opened for others.

I think the current code shouldn't be touched at all, it's more a question of an external android/iOS application, that takes photos and tunes parameters accordingly. Contrary to the human eye phone can catch differences and the tune settings very quickly.
But I get your point, thanks for the answer

repo: awawa-dev/HyperHDR


text:
PicoHyperSerial

Sorry, resolved.
Wrong GPIO connected.

2024-07-12T14:05:58.796Z [LEDDEVICE0_ADALIGHT] Opening UART: ttyACM0
2024-07-12T14:05:58.796Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:209) _serialPort.open(QIODevice::ReadWrite): ttyACM0, Baud rate [200000]bps
2024-07-12T14:05:58.870Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:214) portName:          ttyACM0
2024-07-12T14:05:58.870Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:215) systemLocation:    /dev/ttyACM0
2024-07-12T14:05:58.870Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:216) description:       Pico
2024-07-12T14:05:58.870Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:217) manufacturer:      Raspberry Pi
2024-07-12T14:05:58.870Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:218) productIdentifier: 0xa
2024-07-12T14:05:58.870Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:219) vendorIdentifier:  0x2e8a
2024-07-12T14:05:58.870Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:220) serialNumber:      DF62585783634936
2024-07-12T14:05:58.876Z [LEDDEVICE0_ADALIGHT] Detected Rp2040 type board. HyperHDR skips the reset. State: 1, 1
2024-07-12T14:05:58.880Z [LEDDEVICE0_ADALIGHT] DETECTED DEVICE USING HyperSerialEsp8266/HyperSerialESP32/HyperSerialPico FIRMWARE (HyperHDR frames: 0 (FPS), receiv.: 0, good: 0, incompl.: 0, mem1: 0, mem2: 460, heap: 123232  Welcome! Awa driver 9.) at 2 msec
2024-07-12T14:05:58.880Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:64) Switch on
2024-07-12T14:05:58.880Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:140) Power On
2024-07-12T14:05:58.880Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:367) Starting timer with interval = 20ms
2024-07-12T14:05:58.881Z [COMPONENTCTRL0] LED device: enabled
2024-07-12T14:05:58.882Z [SMOOTHING0] Using alternative smoothing input (0)
2024-07-12T14:05:58.921Z [SMOOTHING0] Using alternative smoothing procedure (0)
2024-07-12T14:06:18.321Z [IMAGETOLED_MNG0] Total index number is: 36800 (memory: 36800). User sparse processing is: disabled, image size: 800 x 600, area number: 160
2024-07-12T14:06:42.057Z [IMAGETOLED_MNG0] Total index number is: 38400 (memory: 38400). User sparse processing is: disabled, image size: 800 x 600, area number: 160
2024-07-12T14:06:48.938Z [V4L2:AUTO] Video cache: size: 3, hits: 7049, needed: 1, cleanup: 0, limit: 8
2024-07-12T14:07:10.306Z [IMAGETOLED_MNG0] Total index number is: 28704 (memory: 28704). User sparse processing is: disabled, image size: 800 x 600, area number: 160

Resolved

repo: awawa-dev/HyperSerialPico


text:
Error with Erlang 19.2 and Elixir 1.4.0

Hi,
We start to have the following error since we bumped our versions of Erlang and Elixir:
[error] Process #PID<0.212.0> raised an exception
** (CaseClauseError) no case clause matching: {:halted, []}
    (sweet_xml) lib/sweet_xml.ex:582: anonymous fn/4 in SweetXml.continuation_opts/2
    (xmerl) xmerl_scan.erl:825: :xmerl_scan.scan_misc/4
    (xmerl) xmerl_scan.erl:578: :xmerl_scan.scan_document/2
    (xmerl) xmerl_scan.erl:291: :xmerl_scan.string/2

The error happens when we run Elixir 1.4.0, SweetXml 0.6.4, and Erlang 19.0 or 19.2. If we run the same code on Elixir 1.3.2, SweetXml 0.6.4, and Erlang 19.0 or 19.2 it works properly.
You can find a repository reproducing the error here: https://github.com/kdisneur/sweat_xml.
The README includes the error logs we have after trying the same script on different versions of Erlang and Elixir.
I hope the error report is clear enough and don't hesitate to ask if I can be of any help :)
Thanks

The problem raises when running mix test
I'm working on it...

Thanks @jeanparpaillon 👍 - I hope it will be merged soon

authors: jeanparpaillon kdisneur


text:
boss module window not centered

not sure why but the boss module window doesnt show my character unless i rotate my camera. i can only see about half of the room inside the window

Probably your window is smaller than what arena would need for the scale you've set. Try resizing the window.

authors: awgil davechopz


text:
Make statusbar font color white

It's a minor thing, I just really hate when the background is dark and the statusbar color is black.
Would it be ok if I changed it to white?
It's also great to people to see how that is done.

Sure, I can see that. Please send a pull request.

Ok I'll send one later :)
Den 17/04/2015 kl. 21.24 skrev Adam notifications@github.com:
Sure, I can see that. Please send a pull request.
—
Reply to this email directly or view it on GitHub
https://github.com/awolf/Xamarin-Forms-InAnger/issues/3#issuecomment-94057410
.

Thank you for the pull request.

authors: Laumania awolf

repo: awolf/Xamarin-Forms-InAnger


text:
Use amplify-appsync-simulator standalone?

Amplify CLI Version
10.7.1
Question
I am wondering if it is possible to use the amplify-appsync-simulator in a standalone manner. We have an AWS AppSync API built out of CloudFormation templates and Python, not using the Amplify framework. It would be a big benefit in terms of cheap integration testing if we could run the AppSync API locally. We have a docker-compose based local environment with dynamodb-local where we already run basic integration tests with dynamodb.
So my question is would such a use case be something you are seeking to support with the amplify-appsync-simulator package? And if so, perhaps there could be some lightweight documentation on how to do so in a stable/supported way.

Hi @dylanfprice 👋 ,Thank you for asking this question. In order to provide better support, we have created a ticket in the Appsync repository. To stay updated, please subscribe to this issue.

authors: AnilMaktala dylanfprice

repo: aws-amplify/amplify-category-api


text:
Error when trying to add a new environment from cli

How did you install the Amplify CLI?
$ npm install -g @aws-amplify/cli
If applicable, what version of Node.js are you using?
20.2.0
Amplify CLI Version
12.2.3
What operating system are you using?
Mac M1
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No
Describe the bug
Hello !
I am trying to add a new env called prod on my project using
amplify env add
After submitting the name and the authentication method, I got this error:
✖ Initializing your environment: prod
✖ There was an error initializing your environment
🛑 Could not initialize platform for 'prod': Missing required key 'Bucket' in params
But using the command amplify env list, the env is created (probably due to a new empty bloc named prod inside team-provider-info.json) and I am currently using this env:
| Environments |
| ------------ |
| staging      |
| *prod        |

Then, when I try to checkout to my staging env with amplify env checkout staging, I got this error:

✖ Initializing your environment: staging
✖ There was an error initializing your environment.
🛑 There was an error building the custom resources
No package manager found. Please install npm, yarn, or pnpm to compile overrides for this project.\
Resolution: There may be errors in your custom resource file. If so, fix the errors and try again.\ Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/
But I am indeed inside my staging env, as stated when using the command amplify status:
Current Environment: staging
But now, If I want to push some changes using amplify push to staging, I get this error:
No package manager found. Please install npm, yarn, or pnpm to compile overrides for this project.
Now, I can't create a new environment, and when returning to my previous environment, it also doesn't work anymore.
Is there any possible solution to resolve this ? Thanks !!
Expected behavior
New env is successfully created
Reproduction steps

amplify env add
amplify env checkout newEnv
amplify push

Project Identifier
No response
Log output

# Put your logs below this line

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hey @wangdavidhao :wave: thanks for raising this! I was not able to immediately reproduce this using CLI 12.4.0, however I have a few follow-up questions to better understand the context of the issue you are experiencing:

would you mind posting the project ID output from amplify diagnose --send-report?
are you able to consistently reproduce this? if so, what is the error and stack trace output from running the same command with --debug?
the "npm missing" error is interesting, similar to the previous ask what is the output of amplify env checkout staging --debug?

Despite the issue, as a workaround, can you try the following:

remove gitignored files with git clean -fXd (this will remove the local prod env references stored in amplify/.config/ and remove the affected amplify-meta.json file)
if the prod CloudFormation stack exists, delete it
if the prod S3 bucket remains after deleting the stack, empty and delete
pull the staging env with amplify pull --appId <your-app-id> --envName staging (this will initialize the project locally with the staging env)
retry creation of prod env with amplify env add

Hey @wangdavidhao  I wanted to follow up here and see if you're still experiencing this?

closing the issue due to inactivity. please feel free in reaching out to us, we would be happy in diving deeper.

Hey @wangdavidhao 👋 thanks for raising this! I was not able to immediately reproduce this using CLI 12.4.0, however I have a few follow-up questions to better understand the context of the issue you are experiencing:

would you mind posting the project ID output from amplify diagnose --send-report?
are you able to consistently reproduce this? if so, what is the error and stack trace output from running the same command with --debug?
the "npm missing" error is interesting, similar to the previous ask what is the output of amplify env checkout staging --debug?

Despite the issue, as a workaround, can you try the following:

remove gitignored files with git clean -fXd (this will remove the local prod env references stored in amplify/.config/ and remove the affected amplify-meta.json file)
if the prod CloudFormation stack exists, delete it
if the prod S3 bucket remains after deleting the stack, empty and delete
pull the staging env with amplify pull --appId <your-app-id> --envName staging (this will initialize the project locally with the staging env)
retry creation of prod env with amplify env add

It helps me!

authors: Dmitresky josefaidt wangdavidhao ykethan

repo: aws-amplify/amplify-cli


text:
Unable to add AWS Amplify categories after updating to CLI version 4.16.1

Describe the bug
I was initially having issues using the Node 8.x runtime and amplify-cli recommended me to update to node 10.x or higher, so I updated Node to the latest 12.x runtime but it was not being reflected and the issues persisted. I updated amplify-cli to the latest version that is 4.16.1 to ensure that the updated Node runtime is reflected. After updating to the latest versions, amplify init works fine but when I try adding a new category such as:
amplify add auth
I receive the following error:

amplify add api
I receive the following error:

Amplify CLI Version
4.16.1
To Reproduce
Create a new basic iOS App, initialize Amplify, and add a new category using the following command:
cd $Project_Directory
amplify init
amplify add auth / amplify add api
Expected behavior
Add an authentication backend by setting up an Amazon Cognito User Pool to act as the backend for letting users sign up and sign in.
Screenshots

Desktop:

OS: Mac
Node Version: 12.2.0
NPM Version: 6.9.0

@Jay2113 this might be related to outdated ESM cache. Could you try evicting the ESM cache. It should be located inside the node_modules folder of Amplify CLI
You could use the following command to clean it up
cd "$(npm -g prefix)/lib/node_modules/@aws-amplify/cli/node_modules/.cache"
rm -rf esm

Also, did you use yarn or npm to install the CLI?

Yes, evicting the ESM cache worked!! I used npm to install the CLI. Thank you for the quick response.


text:
Unable to Push - Get Message: UPDATE_FAILED ... Parameters: [authProviders] must have values

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
d30fzi40a51bhx
Region
us-east-1
Amplify Console feature
Backend builds
Describe the bug
I made a few minor changes to a GraphQL schema we have pushed many times in the past, and ran amplify push.  That resulted in the failure shown below, followed by a cloud formation rollback.
UPDATE_FAILED               authvepwebae8b813dae8b813d AWS::CloudFormation::Stack Sat May 15 2021 14:02:43 GMT-0400 (Eastern Daylight Time) Parameters: [authProviders] must have values
Not sure if this is related, but I had just upgraded the amplify CLI to version 4.51.0 before I saw this error the first time.
Also, in case it's related somehow - One of my colleagues said he attempted to push an auth only change in the last several days as well, but it failed.  I don't have the exact error message, but he said he didn't check in anything related to that.
Full console output is included in additional details.  Thanks for your help!
Expected behavior
Push to complete, updating the GraphQL resources in App Sync
Reproduction steps

run npm i -g @aws-amplify/cli to get version 4.51.0 (not sure if this is related), but it is a step I took
run amplify push
confirm push, and say yes to all prompts to re-generare and over-write

Build Settings
amplify\backend\api\vepapi\build\parameters.json

{
    "CreateAPIKey": 1,
    "AppSyncApiName": "vepapi",
    "DynamoDBBillingMode": "PAY_PER_REQUEST",
    "DynamoDBEnableServerSideEncryption": false,
    "AuthCognitoUserPoolId": {
        "Fn::GetAtt": [
            "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
            "Outputs.UserPoolId"
        ]
    },
    "S3DeploymentBucket": "amplify-xxxxxxxxxxxxxxxxxxxxxx",
    "S3DeploymentRootKey": "amplify-appsync-files/xxxxxxxxxxxxxxxxxxxxx"
}

Additional information
Console Output

amplify push
√ Successfully pulled backend environment dev from the cloud.

Current Environment: dev

Category
Resource name
Operation
Provider plugin

Api
vepapi
Update
awscloudformation

Auth
userPoolGroups
No Change
awscloudformation

Auth
vepwebae8b813dae8b813d
No Change
awscloudformation

? Are you sure you want to continue? Yes

GraphQL schema compiled successfully.
Edit your schema at C:\...\schema.graphql or place .graphql files in a directory at C:\...\schema
? Do you want to update code for your updated GraphQL API Yes
? Do you want to generate GraphQL statements (queries, mutations and subscription) based on your schema types?
This will overwrite your current graphql queries, mutations and subscriptions Yes
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS amplify-vepweb-dev-195208 AWS::CloudFormation::Stack Sat May 15 2021 14:02:37 GMT-0400 (Eastern Daylight Time) User Initiated
| Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS          authuserPoolGroups         AWS::CloudFormation::Stack Sat May 15 2021 14:02:43 GMT-0400 (Eastern Daylight Time)

UPDATE_IN_PROGRESS          authvepwebae8b813dae8b813d AWS::CloudFormation::Stack Sat May 15 2021 14:02:43 GMT-0400 (Eastern Daylight Time)

UPDATE_COMPLETE             authuserPoolGroups         AWS::CloudFormation::Stack Sat May 15 2021 14:02:43 GMT-0400 (Eastern Daylight Time)

UPDATE_FAILED               authvepwebae8b813dae8b813d AWS::CloudFormation::Stack Sat May 15 2021 14:02:43 GMT-0400 (Eastern Daylight Time) Parameters: [authProviders] must have values

UPDATE_ROLLBACK_IN_PROGRESS amplify-vepweb-dev-195208  AWS::CloudFormation::Stack Sat May 15 2021 14:02:44 GMT-0400 (Eastern Daylight Time) The following resource(s) failed to update: [authvepwebae8b813dae8b813d].
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE authvepwebae8b813dae8b813d AWS::CloudFormation::Stack Sat May 15 2021 14:03:02 GMT-0400 (Eastern Daylight Time)
/ Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack

UPDATE_IN_PROGRESS                           authuserPoolGroups         AWS::CloudFormation::Stack Sat May 15 2021 14:03:03 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE                              authuserPoolGroups         AWS::CloudFormation::Stack Sat May 15 2021 14:03:03 GMT-0400 (Eastern Daylight Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS amplify-vepweb-dev-195208  AWS::CloudFormation::Stack Sat May 15 2021 14:03:04 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE                              authvepwebae8b813dae8b813d AWS::CloudFormation::Stack Sat May 15 2021 14:03:06 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE                              authuserPoolGroups         AWS::CloudFormation::Stack Sat May 15 2021 14:03:06 GMT-0400 (Eastern Daylight Time)
UPDATE_ROLLBACK_COMPLETE                     amplify-vepweb-dev-195208  AWS::CloudFormation::Stack Sat May 15 2021 14:03:06 GMT-0400 (Eastern Daylight Time)

Following resources failed

× An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete
An error occurred during the push operation: Resource is not in the state stackUpdateComplete

I also had issues, just updated to 4.51.0 and its resolved in my case.

@tim-weisbrod Do you mind sharing the schema?

Sorry for my delayed response.
Yes, am happy to share my schema privately if you want to reach out to me.
Thanks,
Tim
From: Ammar @.>
Sent: Thursday, May 20, 2021 6:14 PM
To: aws-amplify/amplify-cli @.>
Cc: Tim Weisbrod @.>; Mention @.>
Subject: Re: [aws-amplify/amplify-cli] Unable to Push - Get Message: UPDATE_FAILED ... Parameters: [authProviders] must have values (#7343)
Closed #7343https://github.com/aws-amplify/amplify-cli/issues/7343.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/aws-amplify/amplify-cli/issues/7343#event-4776258403, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AT65JXAHLMN2HD5EBL72RYTTOWCTZANCNFSM45AQET7A.

authors: ammarkarachi myfairshare tim-weisbrod


text:
fix: specify default auth role name on import auth

Description of changes

If imported authRoleName is undefined (which is the case when only importing a user pool), then ref the root stack AuthRoleName by default
Issue #, if available

https://github.com/aws-amplify/amplify-cli/issues/7920
Description of how you validated changes
manually pushed project
Checklist

[x] PR description included
[x] yarn test passes

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@jhockett added E2E test

Any idea when this fix will be published?

authors: adam-nygate edwardfoyle


text:
codegen for subscriptions defaults to requiring an owner when not needed.

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
16
Amplify CLI Version
8.3.1
What operating system are you using?
mac
Amplify Codegen Command
codegen
Describe the bug
Given the following schema and focusing on just the first two auth rules:
type Order
	@model
	@auth(
		rules: [
			{ allow: owner, operations: [create, read] }
			{ allow: groups, groups: ["admin"], operations: [read, update] }
			{ allow: private, provider: iam, operations: [read, update] }
		]
	) {
	id: ID!
	product: String!
	status: ORDER_STATUS! @index(name: "byStatus", queryField: "orderByStatus")
	customerName: String!
}

Both users and admin group users can read Orders and this gives them the ability to subscribe to their changes.
The generated code is the following:
export const onUpdateOrder = /* GraphQL */ `
	subscription OnUpdateOrder($owner: String) {
		onUpdateOrder(owner: $owner) {
			id
			product
			status
			customerName
			createdAt
			updatedAt
			owner
		}
	}

in my scenario, I want admin users to be able to subscribe to all Order changes, but owners can only read/subscribe to their own Orders. This is a problem since the generated code is hardcoded to expect an $owner of type String.
Note that this query will succeed in the AppSync console, but fail on the client because of the above requirement.
The error message is also really opaque:
Connection failed: {"errors":[{"message":"Validation error of type UndefinedVariable: variable not found"}]}
My solution was to create another subscription, onAnyUpdateOrder, that didn't require an owner.:
export const onAnyUpdateOrder = /* GraphQL */ `
	subscription OnUpdateOrder {
		onUpdateOrder {
			id
			product
			status
			customerName
			createdAt
			updatedAt
			owner
		}
	}
`

Expected behavior
I remember in a previous version of amplify, it was possible to turn off subscriptions for a particular auth rule (if memory serves me right). It would be great if that could come back.
Alternatively, if the codegen could be expanded to satisfy both owner and non-owner that would work well also and avoid having to create a separate file of modified queries.
Reproduction steps

amplify add auth
add cognito group
amplify add api
go though graphql steps
add schema above
amplify push -y
view issue.

GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

Additional information
No response

Hi @mtliendo - Thank you for raising this. We're working with AppSync to look at ways to break an implicit assumption that all subscription parameters are required.

authors: alharris-at mtliendo

repo: aws-amplify/amplify-codegen


text:
Update Hugo web framework to 0.58.x

Is your feature request related to a problem? Please describe.
Yes, unable to compile my web app on Amplify as the hugo web framework is on a older version.  Log below:
# Starting phase: build
# Executing command: hugo
2019-09-28T18:16:12.859Z [INFO]: ERROR 2019/09/28 18:16:12 HELLO-FRIEND theme does not support Hugo version 0.55.6. Minimum version required is 0.57

Describe the solution you'd like
Update Hugo version from 0.55.6 to 0.58.x or later release.
Additional context
None

You can set the version of Hugo the latest here: https://docs.aws.amazon.com/amplify/latest/userguide/custom-build-image.html#setup-live-updates
This should fix the issue.

Yup, setting that variable to latest fixed the issue.  Thanks!  Closing this issue.

repo: aws-amplify/amplify-console


text:
Frontend stucked on Provision after deployment

Before opening, please confirm:

[x] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
https://console.aws.amazon.com/amplify/home?region=us-east-1#/d1huifw3ka4zgk
Region
us-east-1
Amplify Console feature
Webhooks
Describe the bug
My apps is stucked on Provision after a build.
Expected behavior
the build used to take few minute only
Reproduction steps
Triggered a build by webhook
Build Settings
version: 1
frontend:
  phases:
    preBuild:
      commands:
        - yarn install
    build:
      commands:
        - npm run generate
  artifacts:
    # IMPORTANT - Please verify your build output directory
    baseDirectory: dist
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*

Additional information
No response

Resolved by unlink git and relinked it, but the problem is that the connected dns was lost and I had to link the dns again


text:
Nextjs build failed:  Type error: Cannot find module 'eslint' or its corresponding type declarations.

Before opening, please confirm:

[X] I have checked the custom domains troubleshooting guide.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
d6cg8pdc6mb4
Region
us-east-1
Step
Build front-end
Status
Failed
Issue or question
I have a website using Nextjs in  github
I have already setup build the app by aws amplify
In build step, it get the error
2023-07-26T02:12:31.147Z [INFO]: yarn run v1.22.0
2023-07-26T02:12:31.180Z [INFO]: $ next build
2023-07-26T02:12:31.595Z [INFO]: - warn No build cache found. Please configure build caching for faster rebuilds. Read more: https://nextjs.org/docs/messages/no-cache
2023-07-26T02:12:31.627Z [INFO]: Attention: Next.js now collects completely anonymous telemetry regarding usage.
2023-07-26T02:12:31.627Z [INFO]: This information is used to shape Next.js' roadmap and prioritize features.
                                 You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
                                 https://nextjs.org/telemetry
2023-07-26T02:12:31.715Z [INFO]: - info Linting and checking validity of types...
2023-07-26T02:12:31.834Z [WARNING]: - error ESLint must be installed in order to run during builds: yarn add --dev eslint
2023-07-26T02:12:49.814Z [WARNING]: Failed to compile.
2023-07-26T02:12:49.815Z [WARNING]: .eslintrc.cjs:1:19
                                    Type error: Cannot find module 'eslint' or its corresponding type declarations.
                                    > 1 | /** @type {import("eslint").Linter.Config} */
                                        |                   ^
                                      2 | const config = {
                                      3 |   overrides: [
                                      4 |     {
2023-07-26T02:12:49.865Z [WARNING]: error Command failed with exit code 1.
2023-07-26T02:12:49.866Z [INFO]: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
2023-07-26T02:12:49.873Z [ERROR]: !!! Build failed
2023-07-26T02:12:49.874Z [INFO]: Please check the supported SSR features to find if your build failure is related to an unsupported feature: https://docs.aws.amazon.com/amplify/latest/userguide/ssr-Amplify-support.html#supported-unsupported-features. You may also find this troubleshooting guide useful: https://docs.aws.amazon.com/amplify/latest/userguide/troubleshooting-ssr-deployment.html
2023-07-26T02:12:49.874Z [ERROR]: !!! Non-Zero Exit Code detected
2023-07-26T02:12:49.874Z [INFO]: # Starting environment caching...
2023-07-26T02:12:49.875Z [INFO]: # Environment caching completed
Terminating logging...

Error message
2023-07-26T02:12:31.595Z [INFO]: - warn No build cache found. Please configure build caching for faster rebuilds. Read more: https://nextjs.org/docs/messages/no-cache
2023-07-26T02:12:31.627Z [INFO]: Attention: Next.js now collects completely anonymous telemetry regarding usage.
2023-07-26T02:12:31.627Z [INFO]: This information is used to shape Next.js' roadmap and prioritize features.
                                 You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
                                 https://nextjs.org/telemetry
2023-07-26T02:12:31.715Z [INFO]: - info Linting and checking validity of types...
2023-07-26T02:12:31.834Z [WARNING]: - error ESLint must be installed in order to run during builds: yarn add --dev eslint
2023-07-26T02:12:49.814Z [WARNING]: Failed to compile.
2023-07-26T02:12:49.815Z [WARNING]: .eslintrc.cjs:1:19
                                    Type error: Cannot find module 'eslint' or its corresponding type declarations.
                                    > 1 | /** @type {import("eslint").Linter.Config} */
                                        |                   ^
                                      2 | const config = {
                                      3 |   overrides: [
                                      4 |     {
2023-07-26T02:12:49.865Z [WARNING]: error Command failed with exit code 1.
2023-07-26T02:12:49.866Z [INFO]: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
2023-07-26T02:12:49.873Z [ERROR]: !!! Build failed
2023-07-26T02:12:49.874Z [INFO]: Please check the supported SSR features to find if your build failure is related to an unsupported feature: https://docs.aws.amazon.com/amplify/latest/userguide/ssr-Amplify-support.html#supported-unsupported-features. You may also find this troubleshooting guide useful: https://docs.aws.amazon.com/amplify/latest/userguide/troubleshooting-ssr-deployment.html
2023-07-26T02:12:49.874Z [ERROR]: !!! Non-Zero Exit Code detected
2023-07-26T02:12:49.874Z [INFO]: # Starting environment caching...
2023-07-26T02:12:49.875Z [INFO]: # Environment caching completed
Terminating logging...

Additional information

Eslintrc.cjs

/** @type {import("eslint").Linter.Config} */
const config = {
  overrides: [
    {
      extends: [
        "plugin:@typescript-eslint/recommended-requiring-type-checking",
      ],
      files: ["*.ts", "*.tsx"],
      parserOptions: {
        project: "tsconfig.json",
      },
    },
  ],
  parser: "@typescript-eslint/parser",
  parserOptions: {
    project: "./tsconfig.json",
  },
  plugins: ["@typescript-eslint"],
  extends: ["next/core-web-vitals", "plugin:@typescript-eslint/recommended"],
  rules: {
    "@typescript-eslint/consistent-type-imports": [
      "warn",
      {
        prefer: "type-imports",
        fixStyle: "inline-type-imports",
      },
    ],
    "@typescript-eslint/no-unused-vars": ["warn", { argsIgnorePattern: "^_" }],
    "@typescript-eslint/no-unsafe-assignment": "warn",
  },
};

module.exports = config;

Env
"next": "^13.4.4"
"eslint": "^8.34.0",
No response

Hi @nvphung22 👋 , thanks for raising this!
It seems that the Amplify app d6cg8pdc6mb4 has been deleted and thus we wont be able to review the build logs for it from our end. If you are still running into this build error with a different Amplify app, I'll recommend you to build your app locally via npm run build to see if the issue is isolated outside the Amplify app environment.

repo: aws-amplify/amplify-hosting


text:
Autocomplete incorrectly shows in non-templates

CloudFormation format detection doesn't seem to work for Autocomplete suggestions. They show in all YAML files, not just CloudFormation YAML templates. This seems separate from the linter, which correctly doesn't run on non-templates.
Maybe there's a configuration option I'm missing?
Example from an OpenAPI YAML file:

It seems this issue is related to a different extension. Duh, and sorry!

It seems this issue is related to a different extension. Duh, and sorry!


text:
Fix Trail and EDS delta function

While running soak tests for cloudtrail-controller i came across an issue
where the controller doesn't properly compare tags field changes. More
specifically the delta function was expecting the tags array in the
desired and latest objects to have to same order.
This was not caught previously in the e2e tests because it's not
technically incorrect. Constatly returning that there is a diff for a
certain field causes the controller to attempt mutating the resource
state towards the desired state. Which is a correct reaction.
This patch fixes this issue by:

Ignore the part that uses reflect.DeepEqual for both EDS and Trail
Add missing preCompare hook for Trail resource.

No e2e tests needed.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/lgtm

/test cloudtrail-unit-test

/test cloudtrail-unit-test

/test cloudtrail-unit-test

/test cloudtrail-unit-test

authors: A-Hilaly jaypipes


text:
Allow major version upgrade by setting AllowMajorVersionUpgrade to true

Fixes aws-controllers-k8s/community#1265
Issue #, if available:
https://github.com/aws-controllers-k8s/community/issues/1265
Description of changes:
This PR is setting AllowMajorVersionUpgrade to true for both modify db instance and modify db cluster.
This flag was designed as protect flag to avoid accidentally engine version upgrade, however this is not necessary for controller side. whenever customer make change to engine version, ACK controller should take instance to target engine version.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/lgtm

authors: brucegucode jaypipes


text:
Build Rails app for production environment

Description
In our Soak Tests, we found out that a Rails app instrumented with OTel Ruby in development mode will use an unbounded amount of memory when receiving several requests.
CloudWatch showed a development Rails app using 11 GB of memory after just 2 hours:

We asked on the OTel Ruby CNCF Slack channel and got the great feedback that we should use a production environment.
This PR does that, and when we did that the Memory Usage was less than 1 GB after 5 hours:

However, to allow for a production environment, the rails app requires a "secret_base_key". Otherwise it will spam the log output with warnings which is really troublesome.
To solve this, we added dummy credentials which don't do anything. Because this is an example, we directly commit the security credentials in the Dockerfile but this is NOT GOOD PRACTICE FOR REAL PRODUCTION ENVIRONMENTS. We allow it to be like this because we want this demo example to work.
You can confirm the credentials work and view the encoded contents of by doing the following command:
$ cd sample-apps/manual-instrumentation/ruby-on-rails
$ RAILS_MASTER_KEY=<KEY_IN_SAMPLE-APP_DOCKERFILE> bin/rails credentials:edit

This will show the following contents:
# NOTE: DO NOT USE THIS IN PRODUCTION ENVIRONMENTS, WE ONLY SET THIS TO SIMULATE A REAL RAILS APP.

# Used as the base secret for all MessageVerifiers in Rails, including the one protecting cookies.
secret_key_base: DO_NOT_STORE_A_SECRET_THIS_IS_JUST_FOR_AN_EXAMPLE

Thanks for figuring this out and making it work!
Just out of curiosity, if the RAILS_MASTER_KEY is just a dummy credential, does it need to be in a certain format to work or can we simply replace it with something like "dummy_credential"?

@srprash Thanks for that prompt!!
I actually did test this with something like RAILS_MASTER_KEY=BOGUS_KEY but the tests immediately fail to start the app 😕:
app_1             | 2022-02-04 22:18:51 +0000 Rack app ("GET /outgoing-http-call" - (172.18.0.4)): #<ActiveSupport::MessageEncryptor::InvalidMessage: ActiveSupport::MessageEncryptor::InvalidMessage>

It's a good idea to post this in the README and PR description though so I've done that!

authors: NathanielRN srprash

repo: aws-observability/aws-otel-ruby


text:
Qos

Added missing documentation for new types.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Pushed directly to the QOS branch instead of making a new one....

repo: aws-robotics/rmw


text:
Overlaying videos on Android

When two videos are overlaid and the bottom video disables and then reactivates its tileId, the top video disappears.
Can you help me with this bug @hokyungh ? 🙏

Hi @yboyer can you see if the information on this issue can help you?
https://github.com/aws-samples/amazon-chime-react-native-demo/issues/23

It works ! Thanks a lot ! 🙏

authors: yboyer zhinang-amazon


text:
New use cases

Issue #, if available:
Description of changes:
-Small changes to naming/logic in existing functions
-New use cases added
a. ALLEVENTSREACTIVE
b. ALLEVENTSPROACTIVE
c. RECOMMENDATIONSANDANOMALIES
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Addition of 3 new use cases.
a. ALLEVENTSREACTIVE
b. ALLEVENTSPROACTIVE
c. RECOMMENDATIONSANDANOMALIES


text:
Fixed camera off screen

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

The camera off screen looks ok in the app, but the icon and text does not appear for me in the live stream. See the attached video. When the screen turns black, it should show the camera off screen that is visible in the app.
https://user-images.githubusercontent.com/68920478/155813483-5eba7bd8-0f24-48e5-8c01-38ae896a148d.mp4

Updated the SDK - try now - maybe that fixes it.
I couldn't reproduce it - for me the off image is shown everytime even when rotating, starting / stopping screenshare etc
So - if that still fails for you - then it must be an SDK issue and for that I'll need more info - like the device you have and maybe some logs. And it would be nice if I could communicate this with the SDK team, but yeah - I don't have access to twitch / justin anymore :)

Confirmed working for me now with the latest commit. The app functions as expected. Thanks for the update!

authors: egorbunovs slee-aws


text:
Update focus_acc computation to discards invalid examples from the average

Description of changes:
While working with the solution and delving into the details of how the focus_acc metric is computed for model validation, I realised that there are situations when examples do not contain any focus tokens, but are still "captured" in this metric.
Although these examples are excluded from the focus token sums (i.e. focus_acc_by_example - line 451 from ner.py), when the focus_acc_by_exampleis averaged intofocus_acc, the total number of validation examples is used (n_examples = probs_raw.shape[0]) instead of the n_focus_tokens_by_example` elements that are not 0.
By nature of the focus_acc, I understand that this metric only accounts for non-default labelled or predicted tokens, hence I concluded that it should not take into consideration examples where there are no such tokens. So I am proposing this change. @athewsey, I look forward to finding out your POV on this.
Additionally, the PR also introduces the n_focus_examples metric that will be captured in CloudWatch.
Testing done:
Solution execution with and without the change - analysis of the metrics via CloudWatch.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hi & thanks for this!
I agree the change makes sense, to make the metric more fairly comparable between datasets where the proportion of zero-entity examples is different.
Any div/0 risk would seem to require a user to provide a validation dataset with 0 examples of any entities - in which case things breaking would hopefully be obvious, and maybe even beneficial to help user notice the issue.
I also like surfacing the number of "focus" examples to the user via the extra metric, which may be useful in some cases for people trying to understand how accuracy is interacting with the propensity of the model to predict all-"other", to produce the final score.
Was going to ask why not n_focus_examples = (n_focus_tokens_by_example != 0).sum(), but from a quick timeit test on a small dummy array, seems like your slice-and-shape method is a fair bit faster? 🤯
So all looks good to me & happy to merge 😁

Excellent! Thanks for the feedback, @athewsey! Also, thanks for providing this super nice solution. I've learned a lot about the SageMaker & HuggingFace ecosystems thanks to it.

authors: athewsey vprecup


text:
bump terraform_version to v1.1.7

What does this PR do?
Update terraform_version in CI and tags. Fixes https://github.com/aws-ia/terraform-ssp-amazon-eks/issues/164
Motivation
Make sure the framework works with latest terraform version.
More

[X] Yes, I have tested the PR using my local account setup  (Provide any test evidence report under Additional Notes)
[ ] Yes, I have added a new example under examples to support my PR
[ ] Yes, I have created another PR for add-ons under add-ons repo (if applicable)
[X] Yes, I have updated the docs for this feature
[ ] Yes, I ran pre-commit run -a with this PR

Note: Not all the PRs required examples and docs except a new pattern or add-on added.
For Moderators

[X] E2E Test successfully complete before merge?

Additional Notes
I have been using 1.1.7 for a while now.

If it helps, I created https://github.com/clowdhaus/terraform-min-max to be able to use the projects provided version constraints for CI testing. We use the min check to ensure we are meeting the minimum required version we set on modules, and the max check is more of a "canary" - an advanced warning really since we never pin the major version, but it would let us know if we needed to react as soon as a Terraform core version starts to break our module.
If you changed the tests to run on a matrix, you could in theory not add any additional time since they are running in parallel. However, you'll have to ensure the cluster name is parameterized and different (didn't check if that is true here)

Closing this as its not urgent. Will reopen with pr workflow updated for testing min-max versions.


text:
Fix unclosed short codes.

Newer versions of Hugo will throw errors on hugo serve if there are
unclosed short codes. This commit fixes those unclosed tags.

@mariswa Can you review?