Controller upgrade to Juju 3.4.4 caused inconsistent charm state

Steps to reproduce

Bootstrap Juju 3.4.2 controller.
Deploy postgresql-k8s from 14/stable channel on revision 193 with 3 units.
Upgrade Juju controller version to 3.4.4.
Refresh postgresql-k8s charm to the latest revision 281 on stable channel.

Expected behavior
Postgresql-k8s charm units settle down as active units.
Actual behavior
Postgresql-k8s charm units are currently stuck with the following states:
Unit                                Workload     Agent       Address          Ports  Message
postgresql-k8s/0*                   maintenance  idle        <IP_ADDRESS>          reconfiguring cluster
postgresql-k8s/1                    active       allocating                          Primary
postgresql-k8s/2                    waiting      idle        <IP_ADDRESS>         awaiting for member to start

Versions

Operating system: Ubuntu 22.04.4 LTS

Juju CLI: 3.5.2-ubuntu-amd64

Juju agent: 3.4.4

Charm revision: 193/281

microk8s: N/A
Log output

Juju debug log:
unit-postgresql-k8s-2: 09:05:23 DEBUG unit.postgresql-k8s/2.juju-log ops 2.12.0 up and running.
unit-postgresql-k8s-2: 09:05:23 DEBUG unit.postgresql-k8s/2.juju-log Re-emitting deferred event <RelationChangedEvent via PostgresqlOperatorCharm/on/database_peers_relation_changed[73889]>.
unit-postgresql-k8s-2: 09:05:24 DEBUG unit.postgresql-k8s/2.juju-log Building PostgreSQL parameters for profile='production' and available_memory=33544642560
unit-postgresql-k8s-2: 09:05:24 INFO unit.postgresql-k8s/2.juju-log Updating Patroni config file
unit-postgresql-k8s-2: 09:05:24 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:24 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:24 DEBUG unit.postgresql-k8s/2.juju-log Early exit update_config: Patroni not started yet
unit-postgresql-k8s-2: 09:05:24 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:24 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:24 DEBUG unit.postgresql-k8s/2.juju-log Deferring on_peer_relation_changed: Waiting for member to start
unit-postgresql-k8s-2: 09:05:24 DEBUG unit.postgresql-k8s/2.juju-log Deferring <RelationChangedEvent via PostgresqlOperatorCharm/on/database_peers_relation_changed[73889]>.
unit-postgresql-k8s-2: 09:05:24 DEBUG unit.postgresql-k8s/2.juju-log Re-emitting deferred event <PebbleReadyEvent via PostgresqlOperatorCharm/on/postgresql_pebble_ready[97854]>.
unit-postgresql-k8s-2: 09:05:25 DEBUG unit.postgresql-k8s/2.juju-log Building PostgreSQL parameters for profile='production' and available_memory=33544642560
unit-postgresql-k8s-2: 09:05:25 INFO unit.postgresql-k8s/2.juju-log Updating Patroni config file
unit-postgresql-k8s-2: 09:05:25 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:25 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:25 DEBUG unit.postgresql-k8s/2.juju-log Early exit update_config: Patroni not started yet
unit-postgresql-k8s-2: 09:05:25 INFO unit.postgresql-k8s/2.juju-log Updated health checks
unit-postgresql-k8s-2: 09:05:25 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:25 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:25 DEBUG unit.postgresql-k8s/2.juju-log Deferring on_postgresql_pebble_ready: Waiting for cluster to start
unit-postgresql-k8s-2: 09:05:25 DEBUG unit.postgresql-k8s/2.juju-log Deferring <PebbleReadyEvent via PostgresqlOperatorCharm/on/postgresql_pebble_ready[97854]>.
unit-postgresql-k8s-2: 09:05:25 DEBUG unit.postgresql-k8s/2.juju-log Re-emitting deferred event <PebbleReadyEvent via PostgresqlOperatorCharm/on/postgresql_pebble_ready[97864]>.
unit-postgresql-k8s-2: 09:05:25 DEBUG unit.postgresql-k8s/2.juju-log Building PostgreSQL parameters for profile='production' and available_memory=33544642560
unit-postgresql-k8s-2: 09:05:25 INFO unit.postgresql-k8s/2.juju-log Updating Patroni config file
unit-postgresql-k8s-2: 09:05:26 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:26 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:26 DEBUG unit.postgresql-k8s/2.juju-log Early exit update_config: Patroni not started yet
unit-postgresql-k8s-2: 09:05:26 INFO unit.postgresql-k8s/2.juju-log Updated health checks
unit-postgresql-k8s-2: 09:05:26 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:26 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:26 DEBUG unit.postgresql-k8s/2.juju-log Deferring on_postgresql_pebble_ready: Waiting for cluster to start
unit-postgresql-k8s-2: 09:05:26 DEBUG unit.postgresql-k8s/2.juju-log Deferring <PebbleReadyEvent via PostgresqlOperatorCharm/on/postgresql_pebble_ready[97864]>.
unit-postgresql-k8s-2: 09:05:26 DEBUG unit.postgresql-k8s/2.juju-log Re-emitting deferred event <PebbleReadyEvent via PostgresqlOperatorCharm/on/postgresql_pebble_ready[118964]>.
unit-postgresql-k8s-2: 09:05:26 DEBUG unit.postgresql-k8s/2.juju-log Building PostgreSQL parameters for profile='production' and available_memory=33544642560
unit-postgresql-k8s-2: 09:05:26 INFO unit.postgresql-k8s/2.juju-log Updating Patroni config file
unit-postgresql-k8s-2: 09:05:26 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:26 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:26 DEBUG unit.postgresql-k8s/2.juju-log Early exit update_config: Patroni not started yet
unit-postgresql-k8s-2: 09:05:26 INFO unit.postgresql-k8s/2.juju-log Updated health checks
unit-postgresql-k8s-2: 09:05:26 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:26 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:26 DEBUG unit.postgresql-k8s/2.juju-log Deferring on_postgresql_pebble_ready: Waiting for cluster to start
unit-postgresql-k8s-2: 09:05:26 DEBUG unit.postgresql-k8s/2.juju-log Deferring <PebbleReadyEvent via PostgresqlOperatorCharm/on/postgresql_pebble_ready[118964]>.
unit-postgresql-k8s-2: 09:05:26 DEBUG unit.postgresql-k8s/2.juju-log Re-emitting deferred event <PebbleReadyEvent via PostgresqlOperatorCharm/on/postgresql_pebble_ready[142724]>.
unit-postgresql-k8s-2: 09:05:26 DEBUG unit.postgresql-k8s/2.juju-log Building PostgreSQL parameters for profile='production' and available_memory=33544642560
unit-postgresql-k8s-2: 09:05:26 INFO unit.postgresql-k8s/2.juju-log Updating Patroni config file
unit-postgresql-k8s-2: 09:05:27 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:27 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:27 DEBUG unit.postgresql-k8s/2.juju-log Early exit update_config: Patroni not started yet
unit-postgresql-k8s-2: 09:05:27 INFO unit.postgresql-k8s/2.juju-log Updated health checks
unit-postgresql-k8s-2: 09:05:27 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:27 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:27 DEBUG unit.postgresql-k8s/2.juju-log Deferring on_postgresql_pebble_ready: Waiting for cluster to start
unit-postgresql-k8s-2: 09:05:27 DEBUG unit.postgresql-k8s/2.juju-log Deferring <PebbleReadyEvent via PostgresqlOperatorCharm/on/postgresql_pebble_ready[142724]>.
unit-postgresql-k8s-2: 09:05:27 DEBUG unit.postgresql-k8s/2.juju-log Re-emitting deferred event <PebbleReadyEvent via PostgresqlOperatorCharm/on/postgresql_pebble_ready[145999]>.
unit-postgresql-k8s-2: 09:05:27 DEBUG unit.postgresql-k8s/2.juju-log Building PostgreSQL parameters for profile='production' and available_memory=33544642560
unit-postgresql-k8s-2: 09:05:27 INFO unit.postgresql-k8s/2.juju-log Updating Patroni config file
unit-postgresql-k8s-2: 09:05:27 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:27 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:27 DEBUG unit.postgresql-k8s/2.juju-log Early exit update_config: Patroni not started yet
unit-postgresql-k8s-2: 09:05:27 INFO unit.postgresql-k8s/2.juju-log Updated health checks
unit-postgresql-k8s-2: 09:05:27 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:27 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:27 DEBUG unit.postgresql-k8s/2.juju-log Deferring on_postgresql_pebble_ready: Waiting for cluster to start
unit-postgresql-k8s-2: 09:05:27 DEBUG unit.postgresql-k8s/2.juju-log Deferring <PebbleReadyEvent via PostgresqlOperatorCharm/on/postgresql_pebble_ready[145999]>.
unit-postgresql-k8s-2: 09:05:27 DEBUG unit.postgresql-k8s/2.juju-log Re-emitting deferred event <PebbleReadyEvent via PostgresqlOperatorCharm/on/postgresql_pebble_ready[146009]>.
unit-postgresql-k8s-2: 09:05:28 DEBUG unit.postgresql-k8s/2.juju-log Building PostgreSQL parameters for profile='production' and available_memory=33544642560
unit-postgresql-k8s-2: 09:05:28 INFO unit.postgresql-k8s/2.juju-log Updating Patroni config file
unit-postgresql-k8s-2: 09:05:28 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:28 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:28 DEBUG unit.postgresql-k8s/2.juju-log Early exit update_config: Patroni not started yet
unit-postgresql-k8s-2: 09:05:28 INFO unit.postgresql-k8s/2.juju-log Updated health checks
unit-postgresql-k8s-2: 09:05:28 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:28 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:28 DEBUG unit.postgresql-k8s/2.juju-log Deferring on_postgresql_pebble_ready: Waiting for cluster to start
unit-postgresql-k8s-2: 09:05:28 DEBUG unit.postgresql-k8s/2.juju-log Deferring <PebbleReadyEvent via PostgresqlOperatorCharm/on/postgresql_pebble_ready[146009]>.
unit-postgresql-k8s-0: 09:05:28 DEBUG unit.postgresql-k8s/0.juju-log Starting new HTTP connection (1): postgresql-k8s-0.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:28 DEBUG unit.postgresql-k8s/2.juju-log Re-emitting deferred event <PebbleReadyEvent via PostgresqlOperatorCharm/on/postgresql_pebble_ready[146096]>.
unit-postgresql-k8s-0: 09:05:28 DEBUG unit.postgresql-k8s/0.juju-log http://postgresql-k8s-0.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 200 None
unit-postgresql-k8s-0: 09:05:28 DEBUG unit.postgresql-k8s/0.juju-log Starting new HTTP connection (1): postgresql-k8s-0.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-0: 09:05:28 DEBUG unit.postgresql-k8s/0.juju-log http://postgresql-k8s-0.postgresql-k8s-endpoints:8008 "GET /cluster HTTP/1.1" 200 None
unit-postgresql-k8s-0: 09:05:28 DEBUG unit.postgresql-k8s/0.juju-log Re-emitting deferred event <RelationChangedEvent via PostgresqlOperatorCharm/on/database_peers_relation_changed[227933]>.
unit-postgresql-k8s-0: 09:05:28 DEBUG unit.postgresql-k8s/0.juju-log Starting new HTTP connection (1): postgresql-k8s-0.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-0: 09:05:28 DEBUG unit.postgresql-k8s/0.juju-log http://postgresql-k8s-0.postgresql-k8s-endpoints:8008 "GET /cluster HTTP/1.1" 200 None
unit-postgresql-k8s-0: 09:05:28 INFO unit.postgresql-k8s/0.juju-log Reconfiguring cluster
unit-postgresql-k8s-0: 09:05:28 DEBUG unit.postgresql-k8s/0.juju-log Starting new HTTP connection (1): postgresql-k8s-0.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-0: 09:05:28 DEBUG unit.postgresql-k8s/0.juju-log http://postgresql-k8s-0.postgresql-k8s-endpoints:8008 "GET /cluster HTTP/1.1" 200 None
unit-postgresql-k8s-0: 09:05:28 DEBUG unit.postgresql-k8s/0.juju-log Adding postgresql-k8s-2 to cluster
unit-postgresql-k8s-0: 09:05:28 DEBUG unit.postgresql-k8s/0.juju-log Starting new HTTP connection (1): postgresql-k8s-0.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-0: 09:05:28 DEBUG unit.postgresql-k8s/0.juju-log http://postgresql-k8s-0.postgresql-k8s-endpoints:8008 "GET /cluster HTTP/1.1" 200 None
unit-postgresql-k8s-0: 09:05:28 INFO unit.postgresql-k8s/0.juju-log not all members are ready
unit-postgresql-k8s-0: 09:05:28 INFO unit.postgresql-k8s/0.juju-log Deferring reconfigure: another member doing sync right now
unit-postgresql-k8s-0: 09:05:28 DEBUG unit.postgresql-k8s/0.juju-log Deferring <RelationChangedEvent via PostgresqlOperatorCharm/on/database_peers_relation_changed[227933]>.
unit-postgresql-k8s-0: 09:05:28 DEBUG unit.postgresql-k8s/0.juju-log Building PostgreSQL parameters for profile='production' and available_memory=33544642560
unit-postgresql-k8s-0: 09:05:28 INFO unit.postgresql-k8s/0.juju-log Updating Patroni config file
unit-postgresql-k8s-2: 09:05:28 DEBUG unit.postgresql-k8s/2.juju-log Building PostgreSQL parameters for profile='production' and available_memory=33544642560
unit-postgresql-k8s-0: 09:05:28 DEBUG unit.postgresql-k8s/0.juju-log Starting new HTTP connection (1): postgresql-k8s-0.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:28 INFO unit.postgresql-k8s/2.juju-log Updating Patroni config file
unit-postgresql-k8s-0: 09:05:28 DEBUG unit.postgresql-k8s/0.juju-log http://postgresql-k8s-0.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 200 None
unit-postgresql-k8s-2: 09:05:28 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:28 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:28 DEBUG unit.postgresql-k8s/2.juju-log Early exit update_config: Patroni not started yet
unit-postgresql-k8s-2: 09:05:28 INFO unit.postgresql-k8s/2.juju-log Updated health checks
unit-postgresql-k8s-2: 09:05:28 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:28 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:28 DEBUG unit.postgresql-k8s/2.juju-log Deferring on_postgresql_pebble_ready: Waiting for cluster to start
unit-postgresql-k8s-2: 09:05:28 DEBUG unit.postgresql-k8s/2.juju-log Deferring <PebbleReadyEvent via PostgresqlOperatorCharm/on/postgresql_pebble_ready[146096]>.
unit-postgresql-k8s-2: 09:05:28 DEBUG unit.postgresql-k8s/2.juju-log Re-emitting deferred event <RelationChangedEvent via PostgresqlOperatorCharm/on/database_peers_relation_changed[146100]>.
unit-postgresql-k8s-2: 09:05:28 DEBUG unit.postgresql-k8s/2.juju-log Building PostgreSQL parameters for profile='production' and available_memory=33544642560
unit-postgresql-k8s-2: 09:05:28 INFO unit.postgresql-k8s/2.juju-log Updating Patroni config file
unit-postgresql-k8s-0: 09:05:29 DEBUG unit.postgresql-k8s/0.juju-log Starting new HTTP connection (1): postgresql-k8s-0.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-0: 09:05:29 DEBUG unit.postgresql-k8s/0.juju-log http://postgresql-k8s-0.postgresql-k8s-endpoints:8008 "PATCH /config HTTP/1.1" 200 None
unit-postgresql-k8s-2: 09:05:29 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:29 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:29 DEBUG unit.postgresql-k8s/2.juju-log Early exit update_config: Patroni not started yet
unit-postgresql-k8s-2: 09:05:29 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:29 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-0: 09:05:29 DEBUG unit.postgresql-k8s/0.juju-log Starting new HTTP connection (1): postgresql-k8s-0.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:29 DEBUG unit.postgresql-k8s/2.juju-log Deferring on_peer_relation_changed: Waiting for member to start
unit-postgresql-k8s-0: 09:05:29 DEBUG unit.postgresql-k8s/0.juju-log http://postgresql-k8s-0.postgresql-k8s-endpoints:8008 "POST /reload HTTP/1.1" 202 None
unit-postgresql-k8s-2: 09:05:29 DEBUG unit.postgresql-k8s/2.juju-log Deferring <RelationChangedEvent via PostgresqlOperatorCharm/on/database_peers_relation_changed[146100]>.
unit-postgresql-k8s-2: 09:05:29 DEBUG unit.postgresql-k8s/2.juju-log Re-emitting deferred event <PebbleReadyEvent via PostgresqlOperatorCharm/on/postgresql_pebble_ready[150452]>.
unit-postgresql-k8s-2: 09:05:29 DEBUG unit.postgresql-k8s/2.juju-log Building PostgreSQL parameters for profile='production' and available_memory=33544642560
unit-postgresql-k8s-2: 09:05:29 INFO unit.postgresql-k8s/2.juju-log Updating Patroni config file
unit-postgresql-k8s-2: 09:05:29 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:29 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:29 DEBUG unit.postgresql-k8s/2.juju-log Early exit update_config: Patroni not started yet
unit-postgresql-k8s-2: 09:05:29 INFO unit.postgresql-k8s/2.juju-log Updated health checks
unit-postgresql-k8s-2: 09:05:29 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:29 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:29 DEBUG unit.postgresql-k8s/2.juju-log Deferring on_postgresql_pebble_ready: Waiting for cluster to start
unit-postgresql-k8s-2: 09:05:29 DEBUG unit.postgresql-k8s/2.juju-log Deferring <PebbleReadyEvent via PostgresqlOperatorCharm/on/postgresql_pebble_ready[150452]>.
unit-postgresql-k8s-2: 09:05:29 DEBUG unit.postgresql-k8s/2.juju-log Re-emitting deferred event <RelationChangedEvent via PostgresqlOperatorCharm/on/database_peers_relation_changed[150456]>.
unit-postgresql-k8s-2: 09:05:30 DEBUG unit.postgresql-k8s/2.juju-log Building PostgreSQL parameters for profile='production' and available_memory=33544642560
unit-postgresql-k8s-2: 09:05:30 INFO unit.postgresql-k8s/2.juju-log Updating Patroni config file
unit-postgresql-k8s-2: 09:05:30 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:30 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:30 DEBUG unit.postgresql-k8s/2.juju-log Early exit update_config: Patroni not started yet
unit-postgresql-k8s-2: 09:05:30 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:30 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:30 DEBUG unit.postgresql-k8s/2.juju-log Deferring on_peer_relation_changed: Waiting for member to start
unit-postgresql-k8s-2: 09:05:30 DEBUG unit.postgresql-k8s/2.juju-log Deferring <RelationChangedEvent via PostgresqlOperatorCharm/on/database_peers_relation_changed[150456]>.
unit-postgresql-k8s-2: 09:05:30 DEBUG unit.postgresql-k8s/2.juju-log Re-emitting deferred event <PebbleReadyEvent via PostgresqlOperatorCharm/on/postgresql_pebble_ready[150836]>.
unit-postgresql-k8s-2: 09:05:30 DEBUG unit.postgresql-k8s/2.juju-log Building PostgreSQL parameters for profile='production' and available_memory=33544642560
unit-postgresql-k8s-2: 09:05:30 INFO unit.postgresql-k8s/2.juju-log Updating Patroni config file
unit-postgresql-k8s-2: 09:05:30 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:30 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:30 DEBUG unit.postgresql-k8s/2.juju-log Early exit update_config: Patroni not started yet
unit-postgresql-k8s-2: 09:05:30 INFO unit.postgresql-k8s/2.juju-log Updated health checks
unit-postgresql-k8s-2: 09:05:30 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:30 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:30 DEBUG unit.postgresql-k8s/2.juju-log Deferring on_postgresql_pebble_ready: Waiting for cluster to start
unit-postgresql-k8s-2: 09:05:30 DEBUG unit.postgresql-k8s/2.juju-log Deferring <PebbleReadyEvent via PostgresqlOperatorCharm/on/postgresql_pebble_ready[150836]>.
unit-postgresql-k8s-2: 09:05:30 DEBUG unit.postgresql-k8s/2.juju-log Re-emitting deferred event <ConfigChangedEvent via PostgresqlOperatorCharm/on/config_changed[150840]>.
unit-postgresql-k8s-2: 09:05:30 DEBUG unit.postgresql-k8s/2.juju-log Defer on_config_changed: Cannot connect to database
unit-postgresql-k8s-2: 09:05:30 DEBUG unit.postgresql-k8s/2.juju-log Deferring <ConfigChangedEvent via PostgresqlOperatorCharm/on/config_changed[150840]>.
unit-postgresql-k8s-2: 09:05:30 DEBUG unit.postgresql-k8s/2.juju-log Re-emitting deferred event <RelationChangedEvent via PostgresqlOperatorCharm/on/database_peers_relation_changed[150844]>.
unit-postgresql-k8s-2: 09:05:31 DEBUG unit.postgresql-k8s/2.juju-log Building PostgreSQL parameters for profile='production' and available_memory=33544642560
unit-postgresql-k8s-2: 09:05:31 INFO unit.postgresql-k8s/2.juju-log Updating Patroni config file
unit-postgresql-k8s-2: 09:05:31 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:31 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:31 DEBUG unit.postgresql-k8s/2.juju-log Early exit update_config: Patroni not started yet
unit-postgresql-k8s-2: 09:05:31 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:31 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:31 DEBUG unit.postgresql-k8s/2.juju-log Deferring on_peer_relation_changed: Waiting for member to start
unit-postgresql-k8s-2: 09:05:31 DEBUG unit.postgresql-k8s/2.juju-log Deferring <RelationChangedEvent via PostgresqlOperatorCharm/on/database_peers_relation_changed[150844]>.
unit-postgresql-k8s-2: 09:05:31 DEBUG unit.postgresql-k8s/2.juju-log Re-emitting deferred event <RelationChangedEvent via PostgresqlOperatorCharm/on/database_peers_relation_changed[150856]>.
unit-postgresql-k8s-2: 09:05:31 DEBUG unit.postgresql-k8s/2.juju-log Building PostgreSQL parameters for profile='production' and available_memory=33544642560
unit-postgresql-k8s-2: 09:05:31 INFO unit.postgresql-k8s/2.juju-log Updating Patroni config file
unit-postgresql-k8s-2: 09:05:31 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:31 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:31 DEBUG unit.postgresql-k8s/2.juju-log Early exit update_config: Patroni not started yet
unit-postgresql-k8s-2: 09:05:31 DEBUG unit.postgresql-k8s/2.juju-log Starting new HTTP connection (1): postgresql-k8s-2.postgresql-k8s-endpoints:8008
unit-postgresql-k8s-2: 09:05:31 DEBUG unit.postgresql-k8s/2.juju-log http://postgresql-k8s-2.postgresql-k8s-endpoints:8008 "GET /health HTTP/1.1" 503 None
unit-postgresql-k8s-2: 09:05:31 DEBUG unit.postgresql-k8s/2.juju-log Deferring on_peer_relation_changed: Waiting for member to start
unit-postgresql-k8s-2: 09:05:31 DEBUG unit.postgresql-k8s/2.juju-log Deferring <RelationChangedEvent via PostgresqlOperatorCharm/on/database_peers_relation_changed[150856]>.
unit-postgresql-k8s-2: 09:05:31 DEBUG unit.postgresql-k8s/2.juju-log Emitting Juju event update_status.
unit-postgresql-k8s-2: 09:05:31 DEBUG unit.postgresql-k8s/2.juju-log on_update_status early exit: Unit is in Blocked/Waiting status
unit-postgresql-k8s-2: 09:05:31 INFO unit.postgresql-k8s/2.juju-log Kubernetes service 'postgresql-k8s' patched successfully
unit-postgresql-k8s-2: 09:05:32 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)

@marceloneppel please check this with priority.
@kelkawi-a , This charm has 2 CI upgrade tests:

upgrade from stable to edge
upgrade from edge to the new PR changes.

Both are solid on nightly GitHub tests (100% success rate for last 30 days).
We should add a test to upgrade between all stable revisions: 73->158->177->193->281 and run it weekly at least (running it nightly could be too expencive).
CC: @jeffreychang911 can solution QA add such stable revisions upgrade test to candidates testing procedure. Tnx!

Dear @kelkawi-a ,
I have executed the reported steps-to-reproduce, full trace here:
https://pastebin.canonical.com/p/HtMxXhHNSJ/
TL;DR:

successfully deployed PG rev 191 to Juju 3.4.2
successfully upgraded controller 3.4.2=>3.4.4
successfully upgraded model 3.4.2=>3.4.4
successfully upgraded PG 191=>281

There are (unnecessary?) all pods restart during both Juju controller and model upgrades.
PG cluster takes time to resurrect, but successfully resurected after the several update-status hooks circle.
Average downtime on my laptop was up to 10 minutes each time and we should with with Juju team to improve this.
Still, it either not a 100% reproducible or we have important bit missing in the current steps-to-reproduce.
Good ideas are welcome.

Hi, @kelkawi-a!
Do you have the specific Juju commands you used for the following steps?

Bootstrap Juju 3.4.2 controller.
Deploy postgresql-k8s from 14/stable channel on revision 193 with 3 units.
Upgrade Juju controller version to 3.4.4.
Refresh postgresql-k8s charm to the latest revision 281 on stable channel.

I did some different tests that would match with the above steps, but in all of them the charm started correctly after the last step (charm refresh).

Thanks for investigating! The controller is IS-owned so I don't have visibility on how it was bootstrapped nor upgraded. The charm was deployed using Juju's Terraform provider, and it was refreshed to the latest revision manually using juju refresh postgresql-k8s. It's also worth noting that the update-status-hook-interval model config is set to 1m. Since reporting, the charms on the staging environment I have access to have not settled yet.
Unit                                Workload     Agent       Address          Ports  Message
postgresql-k8s/0                    error        lost        <IP_ADDRESS>          crash loop backoff: back-off 5m0s restarting failed container=charm pod=postgresql-k8s-0_stg-temporal34(03aeb7a3-fd58...
postgresql-k8s/1                    active       allocating                          Primary
postgresql-k8s/2*                   waiting      idle        <IP_ADDRESS>         awaiting for cluster to start

re: ... and it was refreshed to the latest revision manually using 'juju refresh postgresql-k8s' ...
@kelkawi-a just to double check.
Did you follow official manual and execute juju run postgresql-k8s/leader pre-upgrade-check before juju refresh postgresql-k8s?

I can confirm that I did not run the pre-upgrade-check action prior to refreshing as I was not aware of it. Does this action also need to be run before performing a controller upgrade? Or just a charm upgrade?

I can confirm that I did not run the pre-upgrade-check action prior to refreshing as I was not aware of it. Does this action also need to be run before performing a controller upgrade? Or just a charm upgrade?

Just a charm upgrade. It makes sure the cluster in the safe state for the upgrade and prepares K8s StatefulSet. The lack of such preparation could make Juju bugs (linked above) more visible (assumption).
Can you please try to execute commands https://pastebin.canonical.com/p/HtMxXhHNSJ/ from your side to confirm the issue is not reproducible in your staging/lab.
P.S. Data team is currently working on upgrade v2 which will make pre-upgrade-check optional, however all stable Data charms requires it.

I can run these on my local machine but I'm not sure that will be useful. I do not have access on IS infra to perform controller upgrades. Perhaps @barryprice could assist with this.

The IS environment in question is still up, with postgres in the reported broken state, but we no longer have logs going back as far as the time of the failure.
Do please reach out if there's anything we can usefully run there to help diagnose - the pastebin above looks like a reproducer from scratch which can be run anywhere though.
One slight difference that I don't see mentioned above is the frequency of update-status hooks in the IS environment, which was reduced on request in that environment:
update-status-hook-interval                 model       1m
That should probably be included in any attempted reproducer for accuracy.
As far as I can see, the production environment was deployed with rev 193 of the postgresql-k8s charm, and has not been refreshed to/from any other revision.

As far as I can see, the production environment was deployed with rev 193 of the postgresql-k8s charm, and has not been refreshed to/from any other revision.

@barryprice, do you mean that the charm is still in rev 193?

@marceloneppel apologies, some confusion on my side.
The reported issue is from a staging environment managed by @kelkawi-a - but we'd previously seen similar in a production deploy, which is what I was describing above. I'd mistakenly assumed that's what was being tracked here.
In production, we deployed r193, upgraded the controllers, and wound up in a broken state. We have not upgraded from r193 since the service isn't in a fit state to do so.
In the staging environment, which is what we're actually tracking here, the charm was indeed upgraded.
I believe the model-config (hook interval) tweak I mentioned is present in both environments too though - @kelkawi-a should be able to confirm, in case that's relevant.

Hi, I have made mistake testing rev191 the first time.
Repeated one more time with rev193 and update-status-hook-interval=1m, no issues noticed.
This time upgrade has happened from 3.4.2 to 3.4.5 (due to the recent release of Juju).
We wish to reproduce this and fix in Lab t avoid production surprises in the future, but good ideas are necessary.

I suspect the random issue here is caused by multiple PG K8s pods restarts during the controller upgrade.
The amount of restart could be unpredictable (depends on the controller API downtime time).
In my tests, I had constantly two PT cluster restarts, which can be more for PG cluster upgrade in production and in theory can bring some unrecoverable states (which are unknown at the moment).
We have reported it as an bug to Juju team: https://bugs.launchpad.net/juju/+bug/2075139
IMHO, the K8s pods should be restarted during the model-upgrade only and should stay untouched on controller upgrade.

For the history: @maabujayyab has reported availability of the environment with the reproduced issue.
The investigation continues in https://warthogs.atlassian.net/browse/ISDB-1932?focusedCommentId=546892 and looks different. Requested extra debug information from IS.

The disk became full after multiple restarts due to the growing number of WAL files. It was a 1G disk only. Both the production and staging environments were fixed manually by removing the unnecessary WAL files in the production environment and redeploying the PostgreSQL charm in the staging environment (later restoring a backup of the pgdata directory).


New CHPL Endpoint Lists

Pull requests into this repository require the following checks to be completed by the submitter and reviewers.
Changes in this PR:
Create webscrapers for new CHPL endpoint lists including:

https://apidocs.onemedical.io/fhir/overview/
https://unify-developer.chbase.com/?page=FHIRAPI
https://www.trimedtech.com/Documentation/FHIRAPI/FHIRAPI.html
https://www.trimedtech.com/Documentation/FHIRAPI/V8FHIRAPI.html

The One Medical web scraper does not work locally due to a Zscalar security popup, but it has been tested on the Lantern AWS servers and the web scraper does work as expected. An email has been sent to Infosec to try to get access to the One Medical website. For now, if running locally press Control+C when it tries to access the One Medical website to cancel and move on to the next parsers.
Submitter:

[x] Administrative tasks are complete.

This pull request describes why these changes were made.
The JIRA ticket links to this PR.
The JIRA ticket for this PR is: Lantern 527 JIRA Ticket

[x] Tests are complete.

Tests are included and test edge cases.
Tests have been run locally and pass.

[x] Code review has been performed.

Code diff has been done and checked to ensure only expected code is being committed.
A linter for the language has been run.

Primary Reviewer:

[ ] Code works.

Code has been run locally and the basic functionality affected by the PR has been checked.
Edge cases have been checked to ensure behavior is as expected.

[x] Code review has been performed.

Code is maintainable, reusable, efficient, and correct.
Code accomplishes the tasks purpose.
Code follows style guidance appropriate for the language, including passing linter checks.
Code is well commented (which does not mean verbosely commented).

[x] Tests are complete.

Tests are included and test edge cases.
Tests have been run locally and pass.

Merger:
Prior to merging, ensure that all checks have been completed. Delete the branch after the merge
is complete.

Needs a rebase!


Hydrogen 2.3.1 installation fails due to file permission

Prerequisites

[X ] Have you checked the solutions in our troubleshooting guide for common problems ?
[ X] Have you checked that your issue isn't already filed ?

Description
Hydrogen fails to install or update, both from within atom and from cli. Tried the following:

Remove/re-install hydrogen.
Access with admin. privileges.
Clear npm cache.

Other packages install without issues.
Steps to Reproduce

Install atom 1.41.0
apm install hydrogen

Versions

OS version:
Windows 10 Enterprise 10.0.17663

atom --version

 Atom    : 1.41.0
Electron: 4.2.7
Chrome  : 69.0.3497.128
Node    : 10.11.0

apm --version

apm  2.4.3
npm  6.2.0
node 10.2.1 x64
atom 1.41.0
python
git
visual studio

Hydrogen version:

Plugins
Have you installed and activated any of the Hydrogen plugins below ?

[ ] hydrogen-python
[ ] Hydrogen Launcher
[ ] Data Explorer

Logs
6340 warn enoent ENOENT: no such file or directory, open 'C:\Users\USERNA~1\AppData\Local\Temp\apm-install-dir-119107-3408-vamrtf.nnz6\package.json'
6341 verbose enoent This is related to npm not being able to find a file.
6342 warn<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^15.0.0 but none is installed. You must install peer dependencies yourself.
6343 warn<EMAIL_ADDRESS>requires a peer of vega@* but none is installed. You must install peer dependencies yourself.
6344 warn<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^4.0.0 but none is installed. You must install peer dependencies yourself.
6345 warn apm-install-dir-119107-3408-vamrtf.nnz6 No description
6346 warn apm-install-dir-119107-3408-vamrtf.nnz6 No repository field.
6347 warn apm-install-dir-119107-3408-vamrtf.nnz6 No README data
6348 warn apm-install-dir-119107-3408-vamrtf.nnz6 No license field.
6349 verbose stack Error: EPERM: operation not permitted, rename 'C:\Users\USERNA~1\AppData\Local\Temp\apm-install-dir-119107-3408-vamrtf.nnz6\node_modules\Hydrogen' -> 'C:\Users\USERNA~1\AppData\Local\Temp\apm-install-dir-119107-3408-vamrtf.nnz6\node_modules\.Hydrogen.DELETE'
6350 verbose cwd C:\Users\USERNA~1\AppData\Local\Temp\apm-install-dir-119107-3408-vamrtf.nnz6
6351 verbose Windows_NT 10.0.17763
6352 verbose argv "C:\\Users\\username\\AppData\\Local\\atom\\app-1.41.0\\resources\\app\\apm\\bin\\node.exe" "C:\\Users\\username\\AppData\\Local\\atom\\app-1.41.0\\resources\\app\\apm\\node_modules\\npm\\bin\\npm-cli.js" "--globalconfig" "C:\\Users\\username\\.atom\\.apm\\.apmrc" "--userconfig" "C:\\Users\\username\\.atom\\.apmrc" "install" "https://www.atom.io/api/packages/hydrogen/versions/2.8.0/tarball" "--target=4.2.7" "--disturl=https://atom.io/download/electron" "--arch=x64" "--global-style"
6353 verbose node v10.2.1
6354 verbose npm  v6.2.0
6355 error path C:\Users\USERNA~1\AppData\Local\Temp\apm-install-dir-119107-3408-vamrtf.nnz6\node_modules\Hydrogen
6356 error code EPERM
6357 error errno -4048
6358 error syscall rename
6359 error Error: EPERM: operation not permitted, rename 'C:\Users\USERNA~1\AppData\Local\Temp\apm-install-dir-119107-3408-vamrtf.nnz6\node_modules\Hydrogen' -> 'C:\Users\USERNA~1\AppData\Local\Temp\apm-install-dir-119107-3408-vamrtf.nnz6\node_modules\.Hydrogen.DELETE'
6359 error  { [Error: EPERM: operation not permitted, rename 'C:\Users\USERNA~1\AppData\Local\Temp\apm-install-dir-119107-3408-vamrtf.nnz6\node_modules\Hydrogen' -> 'C:\Users\USERNA~1\AppData\Local\Temp\apm-install-dir-119107-3408-vamrtf.nnz6\node_modules\.Hydrogen.DELETE']
6359 error   cause:
6359 error    { Error: EPERM: operation not permitted, rename 'C:\Users\USERNA~1\AppData\Local\Temp\apm-install-dir-119107-3408-vamrtf.nnz6\node_modules\Hydrogen' -> 'C:\Users\USERNA~1\AppData\Local\Temp\apm-install-dir-119107-3408-vamrtf.nnz6\node_modules\.Hydrogen.DELETE'
6359 error      errno: -4048,
6359 error      code: 'EPERM',
6359 error      syscall: 'rename',
6359 error      path:
6359 error       'C:\\Users\\USERNA~1\\AppData\\Local\\Temp\\apm-install-dir-119107-3408-vamrtf.nnz6\\node_modules\\Hydrogen',
6359 error      dest:
6359 error       'C:\\Users\\USERNA~1\\AppData\\Local\\Temp\\apm-install-dir-119107-3408-vamrtf.nnz6\\node_modules\\.Hydrogen.DELETE' },
6359 error   stack:
6359 error    'Error: EPERM: operation not permitted, rename \'C:\\Users\\USERNA~1\\AppData\\Local\\Temp\\apm-install-dir-119107-3408-vamrtf.nnz6\\node_modules\\Hydrogen\' -> \'C:\\Users\\USERNA~1\\AppData\\Local\\Temp\\apm-install-dir-119107-3408-vamrtf.nnz6\\node_modules\\.Hydrogen.DELETE\'',
6359 error   errno: -4048,
6359 error   code: 'EPERM',
6359 error   syscall: 'rename',
6359 error   path:
6359 error    'C:\\Users\\USERNA~1\\AppData\\Local\\Temp\\apm-install-dir-119107-3408-vamrtf.nnz6\\node_modules\\Hydrogen',
6359 error   dest:
6359 error    'C:\\Users\\USERNA~1\\AppData\\Local\\Temp\\apm-install-dir-119107-3408-vamrtf.nnz6\\node_modules\\.Hydrogen.DELETE' }
6360 error The operation was rejected by your operating system.
6360 error It's possible that the file was already in use (by a text editor or antivirus),
6360 error or that you lack permissions to access it.
6360 error
6360 error If you believe this might be a permissions issue, please double-check the
6360 error permissions of the file and its containing directories, or try running
6360 error the command again as root/Administrator (though this is not recommended).

Expected behavior
Install hydrogen
Screenshots
[If applicable, add screenshots to help explain your problem.]
Additional context
[Add any other context about the problem here.]

Hydrogen can not control this issue. I would recommend following the logs advice.

6360 error The operation was rejected by your operating system.
6360 error It's possible that the file was already in use (by a text editor or antivirus),
6360 error or that you lack permissions to access it.
6360 error
6360 error If you believe this might be a permissions issue, please double-check the
6360 error permissions of the file and its containing directories, or try running
6360 error the command again as root/Administrator (though this is not recommended).

Close all text editors and disable antivirus, and then install via an elevated terminal using apm install hydrogen (ensure apm is in your system env vars). You may not have to do all 3. It's more likely just one of these is causing the block.
If that doesn't work, I can reopen the issue.


Add description for several missing members in product.rst

While it is not necessarily important, it should still be documented for the sake of clarity

Most could be verified.


add proxy from vscode terminal

If we can activate proxy from terminal and vscode understand that for applying it to extension installation that would be great.
for example, I go to vscode terminal and activate the proxy, but it seems like that the ssh local installation for terminal is not using that proxy.

Hmm...I'm not sure I fully understand. Maybe @code-asher does though?

How are you activating the proxy? Is it through the
HTTP_PROXY/HTTPS_PROXY environment variables or something else?
If you are using those environment variables when spawning code-server
it's possible they aren't getting inherited by the terminal.

@code-asher I am doing that in the terminal of vscode via module load proxy_activate
can you tell me how you mean I should do it? sorry I am a newbie so I need am not sure what you mean

Oh this is an Apache proxy? That won't affect the terminal, that only
affects web requests to your Apache webserver.

I am not actually what it is, I am sorry

No worries. If you are trying to use code-server to download extensions
through a proxy you could try this:
HTTPS_PROXY=https://<proxy-domain> code-server --install-extension <extension-id>

Thank you for trying to help me! that is actually what I am trying to do.
should I run this command in the vscode terminal? or in my linux terminal?
Also, how I can install code-server?
I am running
HTTPS_PROXY=http://MYPROXYADDRESSc ode-server  --install-extension ms-python.python-2021.8.1105858891.vsix

in the vscode terminal and im getting
bash: code-server: command not found

I'm sorry for the delayed response; I've been out of the office.
Ahhhhhhh it looks like you are using VS Code remote and not
code-server. You will probably have better luck looking for help
upstream!
https://github.com/microsoft/vscode/search?q=http_proxy&type=issues
I am not sure if VS Code supports HTTP_PROXY on the terminal.

@seyeeet since this is upstream, I'm going to label as so and we'll close the issue


Support OpenSearch suggestions

Supporting suggestions through the OpenSearch interface could help replace the Rust search browser extension.

I wrote a blog post to introduce how to enable opensearch in Firefox and Edge: https://query.rs/opensearch


upstream master 0618

Merging changes from release-candidate/master to dev.

Codecov Report

Merging #2611 into dev will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##              dev    #2611      +/-   ##
==========================================
+ Coverage   94.44%   94.46%   +0.01%
==========================================
  Files         160      160
  Lines       19523    19568      +45
==========================================
+ Hits        18439    18484      +45
  Misses       1084     1084

Impacted Files
Coverage Δ

qiita_db/util.py
96.81% <100%> (+0.12%)
:arrow_up:

qiita_db/metadata_template/util.py
91.21% <100%> (+0.12%)
:arrow_up:

qiita_db/metadata_template/test/test_util.py
99.57% <100%> (+0.03%)
:arrow_up:

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 90a88d9...d8aa5e1. Read the comment docs.


Feature Request: Coloring Coding of Email Accounts

I have a request.
Color coding of the different accounts added.
For instance, allow me to choose a color for my Gmail and another color for my IMAP mail. The color would appear on the side bar, but also in the email list to quickly show which account the email is coming from. Perhaps a thin vertical line on the left side in the message selection list and a thin horizontal banner across the top of the actual message.
Hope this makes sense.

Very similar to #1200

:+1: Yes Please. :)

This would be extremely helpful!

Airmail has this feature.

This feature of allowing to choose a color for all my Gmail accounts would be fantastic! :)

Any updates?

Really missing this feature as I consider switching from another mail app that has this. I have multiple mail accounts and really need to be able to distinguish the mail from each account in the centralised Inbox at a glance.

+1 for this


Ruby group capstone: set up your Kanban board

In this activity, my team and I we prepared a Kanban board with a GitHub project. We prepared an almost empty template that we needed to copy. All tasks are assigned to a member among us.

**** Below are the team in this project
Ayesha
Umair
Ibtisam
The link to kanban board below
Kanban

♻♻♻ STATUS: Changes Required  ♻♻♻

Hi Team   ✋🏼
Your project is excellent. You are almost done. However, there are some issues you should fix. Please fix them and your project will be approved.

♻ Request changes ♻

[ ]  Please make sure all tasks are assigned to someone in your team

Optional suggestions
_Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.
Cheers and Happy coding! 💻 👏

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

_As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

STATUS: APPROVED :green_circle: :clap:
Hello  @TEAM    ,
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉
HIGHLIGHTS:

Your project is professional
Your repo is professional
No linter errors

Now you can merge this branch and move on :1st_place_medal:
Happy Coding cheers 🥇 💯

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Add a cmd to create a schedule for cluster

based on https://github.com/stolostron/hibernate-cronjob
cm create clusters-schedule
cm delete clusters-schedule

Duplicate of #86


Immutable fixes 2.5.1

pulls latest temptifly that fixes these"
stolostron/backlog#21655
stolostron/backlog#22580
stolostron/backlog#23060
stolostron/backlog#23061
stolostron/backlog#22117
stolostron/backlog#22581
dark mode
temptifly commit: https://github.com/stolostron/temptifly/pull/199

/lgtm


[request] multiple hosts support

Hello, and thank you for your well maintained fork.
One benefit of using something like filebeat is that it can fall back to a backup logstash host when the first one defined is unavailable. Do you have any recommendations on how to add this type of feature here, allowing for multiple host/port combos to be specified for the same log handler?

@CameronNemo Not sure what your use case is but in case of logging on Linux or Windows, you might want to log to journald (https://github.com/systemd/python-systemd) or the event log respectively and then use journalbeat or winlogbeat.

Nak. Journalbeat has a lot of other issues, including missed messages due to buffering, lack of transparency across mount namespaces, log corruption, and a convoluted, type unaware structured log format.

@CameronNemo Thanks for your feedback. You are specifically talking about Journald and not journalbeat, is this correct?
In my tests logging to journald and then shipping them with journalbeat worked but I don’t have long-term experience with it yet as journalbeat is still new.

The primary intention of this implementation is to be resilient to network failures or a in some other way unreachable Logstash instance. This is achieved by retrying to transmit the events and persisting them until transferred successfully.
So in theory, it is not necessary to configure multiple Logstash instances as fallback.
In reality, this could still be useful to reduce overall transmission time.
I won't implement this myself but would accept a well written pull request.


Merge pull request #1 from mycoralhealth/master

update

what is this PR for? No files were changed.

closed PR - no details provided


HPE_INVALID_HEADER_TOKEN error on wordpress.org due to X-Olaf header since two days

when using request module to fetch content from http://wordpress.org/, I get error
{ [Error: Parse Error] bytesParsed: 228, code: 'HPE_INVALID_HEADER_TOKEN' }
since two days without having changed my node.js version (v.4.3.0 on ubuntu linux) nor having updated any node module.
returned http response headers (currently) are
HTTP/1.1 200 OK   Server: nginx   Date: Thu, 18 Feb 2016 08:49:25 GMT   Content-Type: text/html; charset=utf-8   Transfer-Encoding: chunked   Connection: keep-alive   Vary: Accept-Encoding   Strict-Transport-Security: max-age=360   X-Olaf: \342\233\204   X-Frame-Options: SAMEORIGIN   X-nc: EXPIRED lax 249
seems that the unnecessary and childish X-Olaf: \342\233\204 header's value cannot be parsed correctly due to some kind of encoding problems.
I do not have these problems on node.js v4.2.3 on windows.
I'm not sure if this is even the right issue tracker here for this problem, but maybe.
Can it be that this is somewhat related to #282 ?

error doesn't occur now anymore, without me having updated any component.

https://github.com/creationix/http-parser-js fixed the issue for me

https://github.com/creationix/http-parser-js fixed the issue for me


Cache OnAwsCloudEnvironmentCondition first result to avoid multiple http requests for every check

Prior to this commit every time @ConditionalOnAwsCloundEnvironment runs its check http request was performed.
With this commit first check result is cached and then returned for every next check.

Thanks @gschukin


Support GHC-8.2.2

When compiling with GHC 8.2.2-rc1:
src/Error.hs:25:17: error:
    Variable ‘r’ used as both a kind and a type
    Did you intend to use TypeInType?
   |
25 | error :: forall (r :: RuntimeRep) . forall (a :: TYPE r) . HasCallStack => Text -> a
   |                 ^^^^^^^^^^^^^^^^^

TypeInType should be enabled, see GHC issue 14121
https://ghc.haskell.org/trac/ghc/ticket/14121

Thanks, merged this and added support for 8.2.2 in the CI. :+1:


Error in device with WebGL2

Hi @xavierjs, me again :)
I am doing tests and I have encountered a special case. With the Samsung A5 from 2016 ... that has WebGl2 throw the following error:
ERROR in ContextFeedForward: Not enough capabilities
Why is it wrong? Is there any way to capture that error with a browser or device test?
Thanks!!

Hi,
I just tested on a Samsung A5  bought in early 2017 this demo with Chrome: https://jeeliz.com/demos/weboji/demos/threejs/raccoon/
And it works.
Are you sure you are using the latest Weboji version?
But the demo was too slow. Indeed the neural network model is quite heavier (heavier than the one used in Jeeliz FaceFilter for example). The weboji feature is more built for higher end mobile phones. It should work nicely with a Samsung S7, a Huawei P9, it works correctly on mine (a 4yo Sony Xperia Zperformance).

Hi, thanks for the quick response as always.
I am trying with your demo and I have the same error and I add this: ERROR: JEEFACETRANSFERAPI cannot be started. errCode = GL_INCOMPATIBLE.
This device has WebGl2.
Thanks!

Yes it's strange. I'll continue testing.
Thanks !!

Hi what's up about this error? Did you tried after updating Android, closing all apps and reboot your phone?

Hi, I don't have tried again with that device, As soon as I have it I will. Thanks for asking

Hi @sonidiaz
I have just pushed a new neural network model which is faster and lighter than the previous one (the accuracy is still the same).
On my medium end mobile phone it really makes a difference (4yo Sony Xperia Zperformance, same computing power than Iphone6).
Best,
Xavier

Hi @xavierjs,
it's great!!
As soon as i can i will do test with last release.
Best,
Nacho


Leaders and attendees of MyOnlineMeeting requirements

Adding information around the requirements for leaders and attendees.
The users to be added there have to be part of the organization or otherwise you'll get an error when submitting the data.
Fixed a typo as well

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

:warning: Validation status: warnings

File
Status
Preview URL
Details

Skype/UCWA/myOnlineMeetings_ref.md
:warning:Warning

Details

Skype/UCWA/myOnlineMeetings_ref.md

Line 359: [Warning] Invalid file link:(~/UCWA/OnlineMeetingResource_ref.md).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

More context for this Pull Request https://stackoverflow.com/questions/44709274/ucwa-myonlinemeeting-attendees-requirements-external-attendees/45060058

@baywet, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, Microsoft Pull Request Bot


Introduce static code control with ObjectScript quality

Thanks to your PR, we now have required Actions executed.
https://github.com/ELynx/i2b2-on-iris-raw-structure/actions/workflows/objectscript-quality.yml


[nrf-noup] cmake: remove check for including 'drivers'

Previously the build code in the 'drivers' folder included
some files which caused a compilation error for B0.
This problem has been fixed, and the folder can now
safely be included in the build.
This aligns with upstream code.
Signed-off-by: Håkon Øye Amundsen<EMAIL_ADDRESS>

tag is wrong, shouldn't be a hyphen in there

@SebastianBoe tag issue fixed


[MINOR] Remove confusing variable

:mag: Description
Issue References 🔗

This pull request fixes #
Describe Your Solution 🔧
fSession refers more to FlinkSessionImpl.fSession.
Types of changes :bookmark:

[ ] Bugfix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Test Plan 🧪
Behavior Without This Pull Request :coffin:
Behavior With This Pull Request :tada:
Related Unit Tests

Checklist 📝

[X] This patch was not authored or co-authored using Generative Tooling

Be nice. Be informative.

Thanks, merged to master/1.8


inaccurate and incomplete Device metadata

What were you trying to achieve?
Just fetch/view and utilise device metadata accordingly
What are the expected results?
complete and accurate metadata of all devices
What are the received results?
Some of the devices do have incomplete metadata
What are the steps to reproduce the issue?
Just check out devices details from Netmanager or from the APIs
In what environment did you encounter the issue?

Chrome
Postman

Additional context
N/A

This was addressed. And it is an ongoing task.


cv.face_detect isn't working

cv.face_detect is not working in windows as well as in linux.
Error: module 'cv2' has no attribute 'dnn'

Hello @varshith321 , May I know how did you install OpenCV Python bindings ?
Did you use pip install opencv-python ?
It should work fine on linux. I just tested it. Have a look at this notebook on Google Colab.

Hello @varshith321  , I have fixed the issue in the latest release.
Get the latest version using pip install --upgrade cvlib
Now it should work fine. Let me know if you face any issues. Have fun detecting faces with cvlib. Cheers.


Use steam api

Is there no way to use steam api without compiling the godot engine? Is it possible with the module compiled with gdnative?

I think you can compile the module for latest godot release (3.1.1 stable) so you don't need to compile the godot engine.

You can try to compile GDNative branch from here:
https://github.com/Gramps/GodotSteam/tree/gdnative
If you are using Godot 3.1.1, you can try to use compiled binaries from our game:
https://github.com/Antokolos/know-everything-os/tree/master/lib/godotsteam
I've used slightly modified gdnative branch when I did the compilation for Godot 3.1.1, you can find it here:
https://github.com/Antokolos/GodotSteam/tree/gdnative-1.1
You will need godot-cpp library in order to compile the GodotSteam. You can find it here:
https://github.com/GodotNativeTools/godot-cpp

Better way is to compile engine. It's worth it, not only because godotsteam, you can add any module, change other code to personalize your game. In the end, if you plan to release a game with godot, you will end compiling the engine. The earliest, the better.... You only need vstudio 2019, scons and python.

You need msvc, mingw, gcc or clang.

Better way is to compile engine.

Once you target multiple platforms, compiling engine for each of them becomes problematic.

All of these answers are true. @mthnzbk, as far as I know there is no way to use the Steam API without compiling the module or add it in with GDNative support.  Personally I find compiling the module easier but @Antokolos definitely provided a wealth of resources to get it working with GDNative.
If you really don't want to mess around with compiling or GDNative, you can always download pre-compiled version of the editor and template in the release section of the repo.  I update these with every major or important changed; granted my Linux versions are often a little behind and MacOS is basically non-existent.

I assume the question is answered?  If not, let me know and we can re-open it!  Thanks everyone for helping out!