Setting PGUSER / PGPASSWORD breaks clustering on v2 postgres!

Create a development single-node cluster using fly pg create
Run fly secrets set --app=db-app-name PGUSER="postgres" PGPASSWORD="passwordhere" with the password shown in the first step.
Scale to a second machine in the cluster using fly machines list to note the first machine's ID and then fly machines clone machineid.

The problematic state is now in effect.
The new machine will not become healthy (however, at some point the fly machines clone command will terminate regardless).
fly logs --app=db-app-name will show the following:
2022-12-08T17:08:51Z app[148e466ce76189] ams [info]keeper   | pg_basebackup: error: connection to server at "fdaa:0:45b4:a7b:c207:ab67:1ee5:2", port 5433 failed: FATAL:  password authentication failed for user "repluser"
2022-12-08T17:08:51Z app[148e466ce76189] ams [info]keeper   | 2022-12-08T17:08:51.752Z	ERROR	cmd/keeper.go:1364	failed to resync from followed instance	{"error": "sync error: exit status 1"}
2022-12-08T17:08:51Z app[6e8293ea64d487] ams [info]keeper   | 2022-12-08 17:08:51.751 UTC [3249] DETAIL:  Connection matched pg_hba.conf line 6: "host replication repluser ::0/0 md5"
2022-12-08T17:08:56Z app[148e466ce76189] ams [info]keeper   | 2022-12-08T17:08:56.857Z	ERROR	cmd/keeper.go:1109	db failed to initialize or resync
2022-12-08T17:08:56Z app[6e8293ea64d487] ams [info]keeper   | 2022-12-08 17:08:56.931 UTC [3291] FATAL:  password authentication failed for user "repluser"

This error message will repeat every few seconds.
And obviously, the new machine is not part of the new cluster as can be seen using stolonctl status:
fly ssh console --app=db-app-name --select
? Select VM: ams: 32873d9b5de985 fdaa:0:45b4:a7b:c207:31c0:d315:2 aged-violet-1627
Connecting to fdaa:0:45b4:a7b:c207:31c0:d315:2... complete
root@32873d9b5de985:/# stolonctl status
=== Active sentinels ===

ID		LEADER
5a6b6323	true
b6ddd7a1	false

=== Active proxies ===

No active proxies

=== Keepers ===

UID		HEALTHY	PG LISTENADDRESS			PG HEALTHY	PG WANTEDGENERATION	PG CURRENTGENERATION
23c2dae83ff82	true	fdaa:0:45b4:a7b:23c2:dae8:3ff8:2:5433	false		1			0
c20731c0d3152	true	fdaa:0:45b4:a7b:c207:31c0:d315:2:5433	true	3	3

=== Cluster Info ===

Master Keeper: c20731c0d3152

===== Keepers/DB tree =====

c20731c0d3152 (master)
└─23c2dae83ff82

The reason for configuring PGUSER/PGPASSWORD is of course to enable wal-g for backups. (c.f. #71 and this forum topic )

@Qqwy can you try this workaround for now? When setting PGUSER and PGPASSWORD for wal-g set PGUSER to repluser and PGPASSWORD to the result of running echo $REPL_PASSWORD on one of your database machines.

Thank you. This workaround seems to work 👍 .

Site note: It does mean that for the time being, calling wal-g requires manually overriding these values:
Like e.g. when manually performing a backup:
PGUSER=postgres PGPASSWORD=$OPERATOR_PASSWORD wal-g backup-push /data/postgres

I have not tested yet whether the full backup+restore flow with wal-g works OK with the workaround in place. Hopefully will have time to do so tomorrow.

I finally had the time to revisit this.
Unfortunately, another error occurs during the initialization process of a restore later on.
The basis of a restore is a second cluster where OPERATOR_PASSWORD, SU_PASSWORD and REPL_PASSWORD are set to the same values as in the original cluster and also setting FLY_RESTORED_FROM to ensure stolonctl will apply these settings on cluster restart (otherwise you'll get authentication issues),
the following is what you should runto trigger the restore as per stolon's docs
export $(cat /data/.env | xargs)
stolonctl init '{ "initMode": "pitr", "pitrConfig": {"dataRestoreCommand": "wal-g backup-fetch %d LATEST" , "archiveRecoverySettings": { "restoreCommand": "wal-g wal-fetch \"%f\" \"%p\"" } } }'

But this will not succeed. Instead, the keeper will error with:
FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649

Ful logs
2023-01-25T16:03:19Z app[5683076c64248e] ams [info]keeper   | waiting for server to shut down....2023-01-25 16:03:19.038 UTC [651] LOG:  received fast shutdown request
2023-01-25T16:03:19Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:19.039 UTC [651] LOG:  aborting any active transactions
2023-01-25T16:03:19Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:19.039 UTC [711] FATAL:  terminating connection due to administrator command
2023-01-25T16:03:19Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:19.042 UTC [651] LOG:  background worker "logical replication launcher" (PID 660) exited with exit code 1
2023-01-25T16:03:19Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:19.042 UTC [654] LOG:  shutting down
2023-01-25T16:03:19Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:19.053 UTC [651] LOG:  database system is shut down
2023-01-25T16:03:19Z app[5683076c64248e] ams [info]keeper   |  done
2023-01-25T16:03:19Z app[5683076c64248e] ams [info]keeper   | server stopped
2023-01-25T16:03:19Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:19.193667 Selecting the latest backup...
2023-01-25T16:03:19Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:19.692009 LATEST backup is: 'base_000000010000000000000011'
2023-01-25T16:03:19Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:19.906784 AO files metadata was not found. Skipping the AO segments unpacking.
2023-01-25T16:03:19Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:19.962878 Finished extraction of part_003.tar.lz4
2023-01-25T16:03:20Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:20.615918 Finished extraction of part_001.tar.lz4
2023-01-25T16:03:20Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:20.644092 Finished extraction of pg_control.tar.lz4
2023-01-25T16:03:20Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:20.644229
2023-01-25T16:03:20Z app[5683076c64248e] ams [info]keeper   | Backup extraction complete.
2023-01-25T16:03:20Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:20.688 UTC [2899] LOG:  starting PostgreSQL 14.6 (Debian 14.6-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-01-25T16:03:20Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:20.688 UTC [2899] LOG:  listening on IPv6 address "fdaa:0:45b4:a7b:23c8:7dd3:f475:2", port 5433
2023-01-25T16:03:20Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:20.690 UTC [2899] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5433"
2023-01-25T16:03:20Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:20.692 UTC [2900] LOG:  database system was interrupted while in recovery at log time 2023-01-25 14:21:10 UTC
2023-01-25T16:03:20Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:20.692 UTC [2900] HINT:  If this has occurred more than once some data might be corrupted and you might need to choose an earlier recovery target.
2023-01-25T16:03:20Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:20.692 UTC [2900] LOG:  creating missing WAL directory "pg_wal/archive_status"
2023-01-25T16:03:20Z app[5683076c64248e] ams [info]sentinel | 2023-01-25T16:03:20.801Z	WARN	cmd/sentinel.go:287	received db state for unexpected db uid	{"receivedDB": "d253f8b8", "db": "90c1ed17", "keeper": "23c87dd3f4752"}
2023-01-25T16:03:21Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:21.251 UTC [2909] FATAL:  the database system is starting up
2023-01-25T16:03:21Z app[5683076c64248e] ams [info]keeper   | 2023-01-25T16:03:21.251Z	ERROR	cmd/keeper.go:719	cannot get configured pg parameters	{"error": "pq: the database system is starting up"}
2023-01-25T16:03:21Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:21.321620 Archive '00000002.history' does not exist.
2023-01-25T16:03:21Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:21.323 UTC [2900] LOG:  entering standby mode
2023-01-25T16:03:21Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:21.370 UTC [2918] FATAL:  the database system is starting up
2023-01-25T16:03:21Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:21.931 UTC [2900] LOG:  restored log file "000000010000000000000011" from archive
2023-01-25T16:03:21Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:21.941 UTC [2900] LOG:  redo starts at 0/11000028
2023-01-25T16:03:21Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:21.941 UTC [2900] LOG:  consistent recovery state reached at 0/11000100
2023-01-25T16:03:21Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:21.942 UTC [2899] LOG:  database system is ready to accept read-only connections
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:22.350785 WAL-prefetch file:<PHONE_NUMBER>00000000000012
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:22.361375 WAL-prefetch file:<PHONE_NUMBER>00000000000013
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:22.372025 WAL-prefetch file:<PHONE_NUMBER>00000000000014
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:22.383078 WAL-prefetch file:<PHONE_NUMBER>00000000000015
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:22.393465 WAL-prefetch file:<PHONE_NUMBER>00000000000016
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:22.403899 WAL-prefetch file:<PHONE_NUMBER>00000000000017
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:22.414554 WAL-prefetch file:<PHONE_NUMBER>00000000000018
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:22.425435 WAL-prefetch file:<PHONE_NUMBER>00000000000019
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:22.435498 WAL-prefetch file:<PHONE_NUMBER>0000000000001A
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:22.446848 WAL-prefetch file:<PHONE_NUMBER>0000000000001B
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:22.525 UTC [2900] LOG:  restored log file "000000010000000000000012" from archive
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:22.547953 Archive '000000010000000000000014' does not exist.
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   |
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:22.548332 Archive '000000010000000000000015' does not exist.
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   |
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:22.550749 Archive '000000010000000000000017' does not exist.
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   |
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:22.554112 Archive '000000010000000000000016' does not exist.
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   |
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:22.554881 Archive '000000010000000000000013' does not exist.
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   |
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:22.564293 Archive '000000010000000000000019' does not exist.
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   |
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:22.569117 Archive '00000001000000000000001B' does not exist.
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   |
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:22.579631 Archive '000000010000000000000018' does not exist.
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   |
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:22.579964 Archive '00000001000000000000001A' does not exist.
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   |
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:22.957149 WAL-prefetch file:<PHONE_NUMBER>00000000000013
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:22.967517 WAL-prefetch file:<PHONE_NUMBER>00000000000014
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:22.977624 WAL-prefetch file:<PHONE_NUMBER>00000000000015
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:22.988023 WAL-prefetch file:<PHONE_NUMBER>00000000000016
2023-01-25T16:03:22Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:22.999042 WAL-prefetch file:<PHONE_NUMBER>00000000000017
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:23.010185 WAL-prefetch file:<PHONE_NUMBER>00000000000018
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:23.020619 WAL-prefetch file:<PHONE_NUMBER>00000000000019
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:23.030686 WAL-prefetch file:<PHONE_NUMBER>0000000000001A
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:23.041314 WAL-prefetch file:<PHONE_NUMBER>0000000000001B
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:03:23.051664 WAL-prefetch file:<PHONE_NUMBER>0000000000001C
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:23.120065 Archive '000000010000000000000013' does not exist.
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   |
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:23.120491 Archive '000000010000000000000017' does not exist.
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   |
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:23.133325 Archive '000000010000000000000015' does not exist.
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   |
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:23.133604 Archive '000000010000000000000014' does not exist.
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   |
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:23.142447 Archive '000000010000000000000016' does not exist.
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   |
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:23.147363 Archive '00000001000000000000001A' does not exist.
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   |
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:23.153564 Archive '00000001000000000000001B' does not exist.
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   |
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:23.161895 Archive '00000001000000000000001C' does not exist.
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   |
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:23.169650 Archive '000000010000000000000019' does not exist.
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   |
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:23.187672 Archive '000000010000000000000018' does not exist.
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   |
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:23.271870 Archive '000000010000000000000013' does not exist.
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:23.288 UTC [2948] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:03:23Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:23.871153 Archive '00000002.history' does not exist.
2023-01-25T16:03:24Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:24.423471 Archive '000000010000000000000013' does not exist.
2023-01-25T16:03:24Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:24.442 UTC [2967] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:03:24Z app[5683076c64248e] ams [info]exporter | ERRO[0389] Error opening connection to database (postgresql://flypgadmin:PASSWORD_REMOVED@[fdaa:0:45b4:a7b:23c8:7dd3:f475:2]:5433/postgres?sslmode=disable): driver: bad connection  source="postgres_exporter.go:1658"
2023-01-25T16:03:25Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:25.001641 Archive '00000002.history' does not exist.
2023-01-25T16:03:28Z app[5683076c64248e] ams [info]proxy    | [WARNING] 024/160328 (597) : Backup Server bk_db/pg is DOWN, reason: Layer7 invalid response, info: "HTTP content check did not match", check duration: 7ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
2023-01-25T16:03:28Z app[5683076c64248e] ams [info]proxy    | [WARNING] 024/160328 (597) : Server bk_db/pg1 is DOWN, reason: Layer7 invalid response, info: "HTTP content check did not match", check duration: 9ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
2023-01-25T16:03:28Z app[5683076c64248e] ams [info]proxy    | [ALERT] 024/160328 (597) : backend 'bk_db' has no server available!
2023-01-25T16:03:29Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:29.492403 Archive '000000010000000000000013' does not exist.
2023-01-25T16:03:29Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:29.504 UTC [2997] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:03:30Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:30.077563 Archive '00000002.history' does not exist.
2023-01-25T16:03:34Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:34.476116 Archive '000000010000000000000013' does not exist.
2023-01-25T16:03:34Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:34.489 UTC [3027] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:03:35Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:35.076016 Archive '00000002.history' does not exist.
2023-01-25T16:03:38Z app[5683076c64248e] ams [info]exporter | INFO[0403] Established new database connection to "fdaa:0:45b4:a7b:23c8:7dd3:f475:2:5433".  source="postgres_exporter.go:970"
2023-01-25T16:03:38Z app[5683076c64248e] ams [info]exporter | INFO[0403] Semantic Version Changed on "fdaa:0:45b4:a7b:23c8:7dd3:f475:2:5433": 0.0.0 -> 14.6.0  source="postgres_exporter.go:1539"
2023-01-25T16:03:38Z app[5683076c64248e] ams [info]exporter | INFO[0403] Established new database connection to "fdaa:0:45b4:a7b:23c8:7dd3:f475:2:5433".  source="postgres_exporter.go:970"
2023-01-25T16:03:38Z app[5683076c64248e] ams [info]exporter | INFO[0403] Semantic Version Changed on "fdaa:0:45b4:a7b:23c8:7dd3:f475:2:5433": 0.0.0 -> 14.6.0  source="postgres_exporter.go:1539"
2023-01-25T16:03:39Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:39.434870 Archive '000000010000000000000013' does not exist.
2023-01-25T16:03:39Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:39.463 UTC [3063] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:03:40Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:40.033522 Archive '00000002.history' does not exist.
2023-01-25T16:03:44Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:44.475939 Archive '000000010000000000000013' does not exist.
2023-01-25T16:03:44Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:44.488 UTC [3096] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:03:45Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:45.067123 Archive '00000002.history' does not exist.
2023-01-25T16:03:49Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:49.431355 Archive '000000010000000000000013' does not exist.
2023-01-25T16:03:49Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:49.444 UTC [3130] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:03:50Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:50.090082 Archive '00000002.history' does not exist.
2023-01-25T16:03:54Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:54.535119 Archive '000000010000000000000013' does not exist.
2023-01-25T16:03:54Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:54.546 UTC [3161] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:03:55Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:55.140221 Archive '00000002.history' does not exist.
2023-01-25T16:03:59Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:03:59.566041 Archive '000000010000000000000013' does not exist.
2023-01-25T16:03:59Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:03:59.579 UTC [3198] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:04:00Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:00.190507 Archive '00000002.history' does not exist.
2023-01-25T16:04:04Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:04.560994 Archive '000000010000000000000013' does not exist.
2023-01-25T16:04:04Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:04.575 UTC [3228] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:04:05Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:05.171634 Archive '00000002.history' does not exist.
2023-01-25T16:04:09Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:09.489874 Archive '000000010000000000000013' does not exist.
2023-01-25T16:04:09Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:09.520 UTC [3262] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:04:10Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:10.095775 Archive '00000002.history' does not exist.
2023-01-25T16:04:14Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:14.488879 Archive '000000010000000000000013' does not exist.
2023-01-25T16:04:14Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:14.507 UTC [3295] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:04:15Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:15.111650 Archive '00000002.history' does not exist.
2023-01-25T16:04:19Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:19.483014 Archive '000000010000000000000013' does not exist.
2023-01-25T16:04:19Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:19.496 UTC [3332] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:04:20Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:20.083555 Archive '00000002.history' does not exist.
2023-01-25T16:04:24Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:24.504949 Archive '000000010000000000000013' does not exist.
2023-01-25T16:04:24Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:24.516 UTC [3362] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:04:25Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:25.090535 Archive '00000002.history' does not exist.
2023-01-25T16:04:27Z app[5683076c64248e] ams [info]keeper   | 2023-01-25T16:04:27.938Z	ERROR	cmd/keeper.go:1506	database cluster not initialized but requested role is master. This shouldn't happen!
2023-01-25T16:04:29Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:29.536742 Archive '000000010000000000000013' does not exist.
2023-01-25T16:04:29Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:29.549 UTC [3402] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:04:30Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:30.133647 Archive '00000002.history' does not exist.
2023-01-25T16:04:32Z app[5683076c64248e] ams [info]keeper   | 2023-01-25T16:04:32.950Z	ERROR	cmd/keeper.go:1109	db failed to initialize or resync
2023-01-25T16:04:32Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:04:32.990659 Selecting the latest backup...
2023-01-25T16:04:33Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:04:33.455259 LATEST backup is: 'base_000000010000000000000011'
2023-01-25T16:04:33Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:04:33.625594 AO files metadata was not found. Skipping the AO segments unpacking.
2023-01-25T16:04:33Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:04:33.649567 Finished extraction of part_003.tar.lz4
2023-01-25T16:04:34Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:04:34.353534 Finished extraction of part_001.tar.lz4
2023-01-25T16:04:34Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:04:34.371782 Finished extraction of pg_control.tar.lz4
2023-01-25T16:04:34Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:04:34.371878
2023-01-25T16:04:34Z app[5683076c64248e] ams [info]keeper   | Backup extraction complete.
2023-01-25T16:04:34Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:34.439 UTC [3443] LOG:  starting PostgreSQL 14.6 (Debian 14.6-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-01-25T16:04:34Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:34.439 UTC [3443] LOG:  could not bind IPv6 address "fdaa:0:45b4:a7b:23c8:7dd3:f475:2": Address already in use
2023-01-25T16:04:34Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:34.439 UTC [3443] HINT:  Is another postmaster already running on port 5433? If not, wait a few seconds and retry.
2023-01-25T16:04:34Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:34.439 UTC [3443] WARNING:  could not create listen socket for "fdaa:0:45b4:a7b:23c8:7dd3:f475:2"
2023-01-25T16:04:34Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:34.439 UTC [3443] FATAL:  could not create any TCP/IP sockets
2023-01-25T16:04:34Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:34.443 UTC [3443] LOG:  database system is shut down
2023-01-25T16:04:34Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:34.545374 Archive '000000010000000000000013' does not exist.
2023-01-25T16:04:34Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:34.562 UTC [3444] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:04:34Z app[5683076c64248e] ams [info]keeper   | 2023-01-25T16:04:34.589Z	ERROR	cmd/keeper.go:1258	failed to start instance	{"error": "postgres exited unexpectedly"}
2023-01-25T16:04:35Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:35.130687 Archive '00000002.history' does not exist.
2023-01-25T16:04:35Z app[5683076c64248e] ams [info]sentinel | 2023-01-25T16:04:35.644Z	ERROR	cmd/sentinel.go:1939	failed to update cluster data	{"error": "cannot choose initial master: no keepers registered"}
2023-01-25T16:04:39Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:39.515618 Archive '000000010000000000000013' does not exist.
2023-01-25T16:04:39Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:39.528 UTC [3478] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:04:40Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:40.108456 Archive '00000002.history' does not exist.
2023-01-25T16:04:40Z app[5683076c64248e] ams [info]sentinel | 2023-01-25T16:04:40.909Z	ERROR	cmd/sentinel.go:1939	failed to update cluster data	{"error": "cannot choose initial master: no keepers registered"}
2023-01-25T16:04:44Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:44.499745 Archive '000000010000000000000013' does not exist.
2023-01-25T16:04:44Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:44.515 UTC [3511] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:04:45Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:45.094840 Archive '00000002.history' does not exist.
2023-01-25T16:04:49Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:49.505755 Archive '000000010000000000000013' does not exist.
2023-01-25T16:04:49Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:49.517 UTC [3545] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:04:49Z app[5683076c64248e] ams [info]keeper   | 2023-01-25T16:04:49.715Z	ERROR	cmd/keeper.go:1109	db failed to initialize or resync
2023-01-25T16:04:49Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:04:49.803974 Selecting the latest backup...
2023-01-25T16:04:50Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:50.087285 Archive '00000002.history' does not exist.
2023-01-25T16:04:50Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:04:50.279906 LATEST backup is: 'base_000000010000000000000011'
2023-01-25T16:04:50Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:04:50.439055 AO files metadata was not found. Skipping the AO segments unpacking.
2023-01-25T16:04:50Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:04:50.463327 Finished extraction of part_003.tar.lz4
2023-01-25T16:04:51Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:04:51.107028 Finished extraction of part_001.tar.lz4
2023-01-25T16:04:51Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:04:51.129659 Finished extraction of pg_control.tar.lz4
2023-01-25T16:04:51Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:04:51.129786
2023-01-25T16:04:51Z app[5683076c64248e] ams [info]keeper   | Backup extraction complete.
2023-01-25T16:04:51Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:51.174 UTC [3570] LOG:  starting PostgreSQL 14.6 (Debian 14.6-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-01-25T16:04:51Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:51.175 UTC [3570] LOG:  could not bind IPv6 address "fdaa:0:45b4:a7b:23c8:7dd3:f475:2": Address already in use
2023-01-25T16:04:51Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:51.175 UTC [3570] HINT:  Is another postmaster already running on port 5433? If not, wait a few seconds and retry.
2023-01-25T16:04:51Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:51.175 UTC [3570] WARNING:  could not create listen socket for "fdaa:0:45b4:a7b:23c8:7dd3:f475:2"
2023-01-25T16:04:51Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:51.175 UTC [3570] FATAL:  could not create any TCP/IP sockets
2023-01-25T16:04:51Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:51.180 UTC [3570] LOG:  database system is shut down
2023-01-25T16:04:51Z app[5683076c64248e] ams [info]keeper   | 2023-01-25T16:04:51.342Z	ERROR	cmd/keeper.go:1258	failed to start instance	{"error": "postgres exited unexpectedly"}
2023-01-25T16:04:51Z app[5683076c64248e] ams [info]sentinel | 2023-01-25T16:04:51.472Z	WARN	cmd/sentinel.go:287	received db state for unexpected db uid	{"receivedDB": "90c1ed17", "db": "aaf1c095", "keeper": "23c87dd3f4752"}
2023-01-25T16:04:54Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:54.513472 Archive '000000010000000000000013' does not exist.
2023-01-25T16:04:54Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:54.529 UTC [3589] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:04:55Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:55.110797 Archive '00000002.history' does not exist.
2023-01-25T16:04:56Z app[5683076c64248e] ams [info]keeper   | 2023-01-25T16:04:56.364Z	ERROR	cmd/keeper.go:1109	db failed to initialize or resync
2023-01-25T16:04:56Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:04:56.454859 Selecting the latest backup...
2023-01-25T16:04:56Z app[5683076c64248e] ams [info]sentinel | 2023-01-25T16:04:56.839Z	WARN	cmd/sentinel.go:287	received db state for unexpected db uid	{"receivedDB": "90c1ed17", "db": "aaf1c095", "keeper": "23c87dd3f4752"}
2023-01-25T16:04:56Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:04:56.949833 LATEST backup is: 'base_000000010000000000000011'
2023-01-25T16:04:57Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:04:57.073700 AO files metadata was not found. Skipping the AO segments unpacking.
2023-01-25T16:04:57Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:04:57.097138 Finished extraction of part_003.tar.lz4
2023-01-25T16:04:57Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:04:57.628640 Finished extraction of part_001.tar.lz4
2023-01-25T16:04:57Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:04:57.648468 Finished extraction of pg_control.tar.lz4
2023-01-25T16:04:57Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:04:57.648498
2023-01-25T16:04:57Z app[5683076c64248e] ams [info]keeper   | Backup extraction complete.
2023-01-25T16:04:57Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:57.689 UTC [3622] LOG:  starting PostgreSQL 14.6 (Debian 14.6-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-01-25T16:04:57Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:57.689 UTC [3622] LOG:  could not bind IPv6 address "fdaa:0:45b4:a7b:23c8:7dd3:f475:2": Address already in use
2023-01-25T16:04:57Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:57.689 UTC [3622] HINT:  Is another postmaster already running on port 5433? If not, wait a few seconds and retry.
2023-01-25T16:04:57Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:57.689 UTC [3622] WARNING:  could not create listen socket for "fdaa:0:45b4:a7b:23c8:7dd3:f475:2"
2023-01-25T16:04:57Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:57.689 UTC [3622] FATAL:  could not create any TCP/IP sockets
2023-01-25T16:04:57Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:57.694 UTC [3622] LOG:  database system is shut down
2023-01-25T16:04:57Z app[5683076c64248e] ams [info]keeper   | 2023-01-25T16:04:57.862Z	ERROR	cmd/keeper.go:1258	failed to start instance	{"error": "postgres exited unexpectedly"}
2023-01-25T16:04:59Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:04:59.517739 Archive '000000010000000000000013' does not exist.
2023-01-25T16:04:59Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:04:59.530 UTC [3637] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:05:00Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:05:00.112102 Archive '00000002.history' does not exist.
2023-01-25T16:05:02Z app[5683076c64248e] ams [info]keeper   | 2023-01-25T16:05:02.897Z	ERROR	cmd/keeper.go:1109	db failed to initialize or resync
2023-01-25T16:05:02Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:05:02.966262 Selecting the latest backup...
2023-01-25T16:05:03Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:05:03.440917 LATEST backup is: 'base_000000010000000000000011'
2023-01-25T16:05:04Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:05:04.200744 AO files metadata was not found. Skipping the AO segments unpacking.
2023-01-25T16:05:04Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:05:04.240422 Finished extraction of part_003.tar.lz4
2023-01-25T16:05:04Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:05:04.523436 Archive '000000010000000000000013' does not exist.
2023-01-25T16:05:04Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:05:04.537 UTC [3676] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:05:04Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:05:04.853012 Finished extraction of part_001.tar.lz4
2023-01-25T16:05:04Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:05:04.912737 Finished extraction of pg_control.tar.lz4
2023-01-25T16:05:04Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:05:04.912769
2023-01-25T16:05:04Z app[5683076c64248e] ams [info]keeper   | Backup extraction complete.
2023-01-25T16:05:04Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:05:04.966 UTC [3686] LOG:  starting PostgreSQL 14.6 (Debian 14.6-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-01-25T16:05:04Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:05:04.966 UTC [3686] LOG:  could not bind IPv6 address "fdaa:0:45b4:a7b:23c8:7dd3:f475:2": Address already in use
2023-01-25T16:05:04Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:05:04.966 UTC [3686] HINT:  Is another postmaster already running on port 5433? If not, wait a few seconds and retry.
2023-01-25T16:05:04Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:05:04.966 UTC [3686] WARNING:  could not create listen socket for "fdaa:0:45b4:a7b:23c8:7dd3:f475:2"
2023-01-25T16:05:04Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:05:04.966 UTC [3686] FATAL:  could not create any TCP/IP sockets
2023-01-25T16:05:04Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:05:04.970 UTC [3686] LOG:  database system is shut down
2023-01-25T16:05:05Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:05:05.122972 Archive '00000002.history' does not exist.
2023-01-25T16:05:05Z app[5683076c64248e] ams [info]keeper   | 2023-01-25T16:05:05.126Z	ERROR	cmd/keeper.go:1258	failed to start instance	{"error": "postgres exited unexpectedly"}
2023-01-25T16:05:09Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:05:09.571929 Archive '000000010000000000000013' does not exist.
2023-01-25T16:05:09Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:05:09.587 UTC [3713] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:05:10Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:05:10.136527 Archive '00000002.history' does not exist.
2023-01-25T16:05:10Z app[5683076c64248e] ams [info]keeper   | 2023-01-25T16:05:10.181Z	ERROR	cmd/keeper.go:1109	db failed to initialize or resync
2023-01-25T16:05:10Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:05:10.256793 Selecting the latest backup...
2023-01-25T16:05:10Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:05:10.727394 LATEST backup is: 'base_000000010000000000000011'
2023-01-25T16:05:10Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:05:10.858197 AO files metadata was not found. Skipping the AO segments unpacking.
2023-01-25T16:05:10Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:05:10.884414 Finished extraction of part_003.tar.lz4
2023-01-25T16:05:11Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:05:11.520888 Finished extraction of part_001.tar.lz4
2023-01-25T16:05:11Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:05:11.541000 Finished extraction of pg_control.tar.lz4
2023-01-25T16:05:11Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:05:11.541021
2023-01-25T16:05:11Z app[5683076c64248e] ams [info]keeper   | Backup extraction complete.
2023-01-25T16:05:11Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:05:11.590 UTC [3740] LOG:  starting PostgreSQL 14.6 (Debian 14.6-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-01-25T16:05:11Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:05:11.590 UTC [3740] LOG:  could not bind IPv6 address "fdaa:0:45b4:a7b:23c8:7dd3:f475:2": Address already in use
2023-01-25T16:05:11Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:05:11.590 UTC [3740] HINT:  Is another postmaster already running on port 5433? If not, wait a few seconds and retry.
2023-01-25T16:05:11Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:05:11.590 UTC [3740] WARNING:  could not create listen socket for "fdaa:0:45b4:a7b:23c8:7dd3:f475:2"
2023-01-25T16:05:11Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:05:11.590 UTC [3740] FATAL:  could not create any TCP/IP sockets
2023-01-25T16:05:11Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:05:11.596 UTC [3740] LOG:  database system is shut down
2023-01-25T16:05:11Z app[5683076c64248e] ams [info]keeper   | 2023-01-25T16:05:11.754Z	ERROR	cmd/keeper.go:1258	failed to start instance	{"error": "postgres exited unexpectedly"}
2023-01-25T16:05:14Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:05:14.528757 Archive '000000010000000000000013' does not exist.
2023-01-25T16:05:14Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:05:14.543 UTC [3756] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:05:15Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:05:15.104948 Archive '00000002.history' does not exist.
2023-01-25T16:05:16Z app[5683076c64248e] ams [info]keeper   | 2023-01-25T16:05:16.769Z	ERROR	cmd/keeper.go:1109	db failed to initialize or resync
2023-01-25T16:05:16Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:05:16.855385 Selecting the latest backup...
2023-01-25T16:05:17Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:05:17.296092 LATEST backup is: 'base_000000010000000000000011'
2023-01-25T16:05:17Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:05:17.421906 AO files metadata was not found. Skipping the AO segments unpacking.
2023-01-25T16:05:17Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:05:17.447735 Finished extraction of part_003.tar.lz4
2023-01-25T16:05:17Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:05:17.995974 Finished extraction of part_001.tar.lz4
2023-01-25T16:05:18Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:05:18.018426 Finished extraction of pg_control.tar.lz4
2023-01-25T16:05:18Z app[5683076c64248e] ams [info]keeper   | INFO: 2023/01/25 16:05:18.018582
2023-01-25T16:05:18Z app[5683076c64248e] ams [info]keeper   | Backup extraction complete.
2023-01-25T16:05:18Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:05:18.055 UTC [3790] LOG:  starting PostgreSQL 14.6 (Debian 14.6-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-01-25T16:05:18Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:05:18.055 UTC [3790] LOG:  could not bind IPv6 address "fdaa:0:45b4:a7b:23c8:7dd3:f475:2": Address already in use
2023-01-25T16:05:18Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:05:18.055 UTC [3790] HINT:  Is another postmaster already running on port 5433? If not, wait a few seconds and retry.
2023-01-25T16:05:18Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:05:18.055 UTC [3790] WARNING:  could not create listen socket for "fdaa:0:45b4:a7b:23c8:7dd3:f475:2"
2023-01-25T16:05:18Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:05:18.055 UTC [3790] FATAL:  could not create any TCP/IP sockets
2023-01-25T16:05:18Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:05:18.060 UTC [3790] LOG:  database system is shut down
2023-01-25T16:05:18Z app[5683076c64248e] ams [info]keeper   | 2023-01-25T16:05:18.230Z	ERROR	cmd/keeper.go:1258	failed to start instance	{"error": "postgres exited unexpectedly"}
2023-01-25T16:05:19Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:05:19.502210 Archive '000000010000000000000013' does not exist.
2023-01-25T16:05:19Z app[5683076c64248e] ams [info]keeper   | 2023-01-25 16:05:19.516 UTC [3804] FATAL:  could not start WAL streaming: ERROR:  replication slot "stolon_1723880d" is active for PID 649
2023-01-25T16:05:20Z app[5683076c64248e] ams [info]keeper   | ERROR: 2023/01/25 16:05:20.097358 Archive '00000002.history' does not exist.
2023-01-25T16:05:21Z app[5683076c64248e] ams [info]keeper   | Process exited 0
2023-01-25T16:05:21Z app[5683076c64248e] ams [info]keeper   | restarting in 5s [attempt 1]

Actually, above issue was caused by something else: You need to make sure you do not enable wal-g on the restore until after you've restored. Makes sense in hindsight.
I'll close this issue now 👌 .


How can I add label ?

Some one told me this need repo permission.
1-Does that mean I need to apply to administrator of this project to add the label?
2-Who have the permission to add label to issue? Anyone or administrator?

Actually you need the write access permission: https://docs.github.com/en/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests
The author of the project and anyone with this permission (requires author assignment)


Porting PassProtect to Firefox

Hi there! It would be awesome to have this extension available to Firefox users. It should be fairly easy to port the Chrome version to Firefox. (There's a guide for porting Chrome extensions to Firefox on MDN.)
I'm the Add-ons Community Manager for Firefox and would be happy to help out with this if I can! Thanks so much.

I've already got it in progress! I ran into a few issues I haven't been able to resolve yet -- any chance I could get your email? Would love to figure it out =)

Absolutely! My email is cneiman [at] mozilla.com. You might also want to reach out to our developer mailing list at dev-addons [at] mozilla.org -- they'd be happy to help troubleshoot. :)

I wrote a port of this for Firefox. https://github.com/andymarch/passprotect-firefox
At the moment it's not signed for AMO

This would be amazing, has anyone made any progress on this in the last few years? @andymarch's looks great but having a signed one would be cool.


Feature request: Convert XML content for known escaped/encoded values.

hi,
When we convert XML to JSON, is it possible to add an option where in the content within XML is also converted to standard format? The content in XML may have been escaped to prevent XML error.
For example: XML could be A & gt ; B. But the converted JSON text can be A > B.  Currently this does not happen and > is retained. There will be many other such conversions applied to prevent the XML from becoming invalid. So if this can be added as an option feature, that would be great!
Below, is the sample that I use (C# .Net FW v4.5.2, running 10.3). So if overloaded method is made available for SerializeXNode to accept this option, that would be a good feature to have.
XDocument doc = XDocument.Parse(strXmlData);
string jsonText = JsonConvert.SerializeXNode(doc);

Thanks!
PS: Ignore the space between "& gt ;"

This already worked for me:
XElement e = new XElement("root", "A > B");

string json = JsonConvert.SerializeXNode(e);

Assert.AreEqual(@"{""root"":""A > B""}", json);


When saving a canvas on a HUAWEI Mate 20 Pro the image is not drawn.

Steps to Reproduce

Have a HUAWEI Mate 20 Pro
Have a canvas where you can draw and upload an image
Save the canvas

Logs
No Errors

Flutter Doctor -v
[√] Flutter (Channel master, v0.10.3-pre.90, on Microsoft Windows [Version 10.0.17134.345], locale nl-NL)
    • Flutter version 0.10.3-pre.90 at D:\flutter
    • Framework revision db9fe3f827 (2 days ago), 2018-11-04 03:20:44 +0100
    • Engine revision 88cb78cdf6
    • Dart version 2.1.0 (build 2.1.0-dev.8.0 bf26f760b1)

[√] Android toolchain - develop for Android devices (Android SDK 28.0.2)
    • Android SDK at D:\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.2
    • ANDROID_HOME = D:\Android\SDK
    • Java binary at: D:\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
    • All Android licenses accepted.

[√] Android Studio (version 3.2)
    • Android Studio at D:\Android\Android Studio
    • Flutter plugin version 29.1.1
    • Dart plugin version 181.5656
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)

[√] Connected device (1 available)
    • LYA L29                   • LHS7N18A04002770 • android-arm64 • Android 9 (API 28)

Issue
I have a HUAWEI Mate 20 Pro and when drawing on a canvas the image is shown. But when i save the canvas the image isn't drawn in the image. The lines i can draw in the canvas itself do show. On a AVD it does work running android 9.0 on both
Save the canvas code:
Future<ByteData> save() async {
    UI.PictureRecorder recorder = UI.PictureRecorder();
    Canvas canvas = Canvas(recorder);

    final UI.Rect rect = UI.Offset.zero & _canvasSize;
    final Size imageSize =
        Size(_image.width.toDouble(), _image.height.toDouble());
    FittedSizes sizes = applyBoxFit(BoxFit.contain, imageSize, _canvasSize);
    final Rect inputSubrect =
        Alignment.center.inscribe(sizes.source, Offset.zero & imageSize);
    final Rect outputSubrect =
        Alignment.center.inscribe(sizes.destination, rect);

    canvas.drawImageRect(_image, inputSubrect, outputSubrect, Paint());

    for (int i = 0; i < _points.length - 1; i++) {
      if (_points[i] != null && _points[i + 1] != null) {
        if (_points[i].paint.toString() == blurPaintSettings.toString()) {
          if (_blurStart == null) _blurStart = _points[i].offset;
          if (_points.length >= i + 3 && _points[i + 2] == null) {
            canvas.drawRect(Rect.fromPoints(_blurStart, _points[i + 1].offset),
                blurPaintSettings);
            _blurStart = null;
          }
        } else {
          canvas.drawLine(
              _points[i].offset, _points[i + 1].offset, _points[i].paint);
        }
      }
    }

    canvas.save();

    final image = recorder
        .endRecording()
        .toImage(_canvasSize.width.toInt(), _canvasSize.height.toInt());

    final imageBytes = await image.toByteData(format: UI.ImageByteFormat.png);

    return imageBytes;
}

Paint code:
@override
  void paint(Canvas canvas, Size size) {
    if (_image != null) {
      paintBackgroundImage(canvas, size);
    }

    for (int i = 0; i < _points.length - 1; i++) {
      if (_points[i] != null && _points[i + 1] != null) {
        if (_points[i].paint.toString() == blurPaintSettings.toString()) {
          if (_blurStart == null) _blurStart = _points[i].offset;
          if (_points.length >= i + 3 && _points[i + 2] == null) {
            canvas.drawRect(Rect.fromPoints(_blurStart, _points[i + 1].offset),
                blurPaintSettings);
            _blurStart = null;
          }
        } else {
          canvas.drawLine(
              _points[i].offset, _points[i + 1].offset, _points[i].paint);
        }
      }
    }

After some more testing this is not only a problem with the Huawei Mate 20 Pro but with every physical device. On the emulator everything works great but assoon as you take out the physical device it breaks.
Also no errors or excceptions. I debugged the image that is get and thats still there before and after the paint call

Dupe of #23621


RE2 (and likely the rest of REFramework) Has Issues Where PSVR2 Controllers Are Seemingly Non-Functional

Describe the bug
Using the PSVR2 SteamVR runs the controllers in Oculus Touch compatability mode (which is not a big deal, Half Life VR does the same and runs with PSVR2 flawlessly so the compatability layer is almost certainly not the problem) when you start the game with a fresh install of the mod the menu is navigable if slightly awkward.  The game can be loaded into without issue and you can walk, aim, bring up the inventory, and interact with interactables. However some of the binds are a bit awkward and R2 (right trigger) does not fire the gun, I have no way of knowing if reload works because I can't shoot. After attempting to smooth the bindings out by editing the bindings through steam VR in game (because you cannot change the bindings out of game like with Half Life VR mod) literally nothing works you can't even select no for HDR before the title screen. The only things that function are the joysticks. The in game bindings settings are just as useless because they think you're using a mouse and keyboard and all of the buttons do either nothing or show up as left click.
I have tried both nightly and current stable builds. OpenVR and OpenXR, I've also attempted to do it with the upscaler version. Nothing has worked.
Upload logs and any crash dumps
Uploaded logs from upscale OpenXR attempt and my binding json
If necessary I can run it in all 4 modes and get you more log files.
Identify the REFramework version
If the REFramework version or commit hash is known, submit this information.
To Reproduce
Steps to reproduce the behavior:

Start Game
Press cross/square. Nothing happens. This is after attempting to use steamVR to change bindings.
Start game (with default bindings)
Load into VR save file
Press R2. Gun does not fire. It is unknown whether the button for reloading works because I can't fire.

Expected behavior
I expect Right trigger to fire guns, and I expect square, cross, triangle, and circle to perform their assigned functions. (a,b,x,y (not respectively)) I also expect cross to perform the function of A and circle to perform the function of B in the menus (if i reassign the buttons to do so).
Crucially, it is possible to get the controllers to work as seen in this youtube video https://www.youtube.com/watch?v=In6bE8GzeWQ but I don't understand how they got it functioning.
Screenshots
If applicable, add screenshots to help explain your problem.
I don't think screenshots are applicable but if you're having issues recreating my issues I will record some videos
Desktop and VR (please complete the following information):

OS (e.g. Windows 11) - Windows 10
Graphics card - MSI Gaming X 3060 (the og one)
CPU - i7 - 10700

Virtual Reality (please complete the following information):

Headset model - PSVR2
Runtime (OpenVR or OpenXR) - Both. Switching between the 2 doesn't have any noticeable effect.

Additional context
re2_framework_log.txt
playstation_vr2_sense.json

Ensure you don't have any sort of extra conflicting software, like those for joysticks, joytokey, xpadder, etc...
If keyboard icons are showing up while using the controllers, that means something is conflciting and continuously sending keyboard input to the game. This could be because of conflicting software, or something like your mouse being extremely sensitive. Because the game doesn't exactly support dual input, the keyboard/mouse takes priority, and controller buttons generally get ignored.

I did a clean reinstall and did further testing and "fixed" the problem. However there are still several issues big enough to be worth mentioning;
1.) You cannot rebind any of the default bindings or everything breaks completely. This is probably because there is no distinction between left or right grips/triggers (just grip, trigger) and cross,square,triangle (just A,B) when you make custom bindings, however the automatically generated bindings bypass this in a way that I don't fully understand.
2.) Speaking of things I don't fully understand. You shoot by pressing Right Grip and Right Trigger. Nothing anywhere describes this behavior and I only found this out because i decided to push every non-menu-opening button at the same time and the gun went off.
3.) It is extremely unclear what the binds mean in the binding menu. The autobind just kind of makes it work in a way that the binding menu, clearly, doesn't reflect. I am pretty sure there isnt a way to bind the firing action to the controllers manually meaning the only way to add missing functionality, which includes opening the start menu and chanding ammo types, is by setting chords. Because if you de-mirror the controller everything stops working and the only available button on the left controller is the button that takes screenshots.
4.) I can give a detailed list of what each button does if you want to put it into the FAQ.


The first two frames of output in examples/vid2vid are wired

Below might improve the result:
- write_video(output, video_result[2:], fps=fps)
+ write_video(output, video_result[4:], fps=fps)

at https://github.com/cumulo-autumn/StreamDiffusion/blob/b74363e32c5f1f9035cf4fa8b0fd11ab8a3177de/examples/vid2vid/main.py#L99

how to handle this problem？
https://github.com/cumulo-autumn/StreamDiffusion/issues/31

Thanks for the report.
That part is being fixed by us.
Right now we have the initial 2 frames of the output video.
write_video(output, video_result[2:], fps=fps)
Try changing the slice of video_result[2:]  like video_result[4:]
This way you can eliminate some of the initial frames.


Modify saved response during replay

My app sets a non-deterministic request id which the response has to match so I need to update the tape to include the request id.
Can we add a new option that allows the outbound tape response to be edited bodyUpdater.
const opts = {
  host: "http://localhost:9001",
  port: 9000,
  bodyMatcher: (tape, req) => {  /** stripe out request id */},
  bodyUpdater: (tape, req) => { /** get new request id from req and replace old request id instances from the tape */}
}

@siderakis I just release v1.6.0 which includes a responseDecorator option which is very similar to your bodyUpdater proposal.
Thank for the suggestion.


Full working sample

Can anyone give an full working example for downloading, extracting und redirecting to the extracted content?

Yes here

It work's finde, but when i restart the app, the old local content appears.

Right. The plugin doesn't manage content for you. It just syncs content to stores it to some permanent location. There are different ways you can manage content and it's up to you how you want to do that.

How can I add a simple test routine to the app?

any idea?

@realn3rd what do you mean by simple test routine ?

A simple way to test on app start if content were already downloaded und redirect to this content.

Maybe something at device-ready-event?

Nice, but it doesn't work :/

What doesn't work ? Could you be more specific ?

The App shows only the local content, not the cached after restarting it.

@realn3rd did you set document.location=data.localpathin the complete callback ?

Yes
http://pastebin.com/hsRCNKzA

Any idea?

@realn3rd sorry for delay. You can try to use the following (on iOS 9+ and above) if you're using WKWebView:
ContentSync.loadUrl(YOUR_URL)
I've updated the sample in the repository to reflect this.


[SCHEDULE] Add factor_axis to rfactor

See https://github.com/dmlc/tvm/issues/851 We want to enhance rfactor so it contains an additional argument factor_axis, which takes list of axis in factored tensor, on which axis each factor corresponds to. This can enhance the ability to do vectorization and other things.

I take a look at the code. The additional argument is supposed to indicate the position of the new axis. But I don't know how to define the arg.

s.rfactor(tensorA, reduce_axis, pos). It is simple, but I think you would not prefer this way.
s.rfactor(tensorA, reduce_axis, factor_axis). The factor_axis is a list of axis refer to the generated factor_tensor, including the new axis. But it would suggest a reorder of axes, which could not be support.

Could you give me a simple example the explain how to design the api ? Then I could start to fix this.

@DengLLy Interested in pushing a patch?

supported by #895


Attribute name

https://github.com/akrava/software-engineering-methodology-practices/blob/fe840e69c81350029521012809f3327be4ba95f4/practice1/eurodiffusion/eurodiffusion.go#L82
IsCompleated -> IsCompleted

Thanks for finding this typo. I'll fix it

I've opened PR #9 in order to fix typo and merge changes.

Fixed in https://github.com/akrava/software-engineering-methodology-practices/commit/17cc50cbe718095aecafd952dc96ffc11b20f1f1. So issue is closed. Feel free to reopen if needed


Use wiki or external documentation site

Readme just isn't cutting it for the amount of options and combinations of things that could be in a code block

The homepage really needs some content but it's there https://github.com/nathonius/obsidian-github-link/wiki


Validation of Redirect_URI

Instead of using only String.starts_with, implement a strict validation mechanism that checks the full URL against the configured “white list” of URLs. Add more strict regular expression to legal_entity_create_request.json to implement the validation of the full length of provided URL

Return 401 response code instead of 422 in case of incorrect URI
{
    "meta": {
        "url": "http://api-svc.mithril/oauth/apps/authorize",
        "type": "object",
        "request_id": "2819c2aa-7583-44d5-afa8-1a25c2aeabc1#408",
        "code": 422
    },
    "error": {
        "type": "request_malformed",
        "message": "The redirection URI provided does not match a pre-registered value.",
        "invalid": [
            {
                "rules": [
                    {
                        "rule": "json"
                    }
                ],
                "entry_type": "request"
            }
        ]
    }
}

Done - Tested


[BEAM-2503] use static table name in BeamSql.simpleQuery

R: @takidau
As discussed in #3372, here's the part to use fixed table name PCOLLECTION in BeamSql.simpleQuery.

Changes Unknown when pulling 1f612049b83a67070d13aae790d61e0f71d79ca7 on XuMingmin:BEAM-2503 into ** on apache:DSL_SQL**.

Merged. Forgot to remove the commented out code. If it's not getting uncommented the next time you edit this file, let's please remove it then. Feel free to close this PR.

Thanks @takidau .
The commented lines are pending to fix in another task, would handle it in BEAM-2520.

For a feature branch I think that's probably okay, but I wouldn't want to leave commented-out code lying around on master. Thanks! Feel free to close.


Getting entity velocity crashes

I'm using the Netvar manager, doing this in the BaseEntity class:
Vector GetVelocity()
{
	static int m_vecVelocity = g_pNetvars->GetOffset("DT_BasePlayer", "m_vecVelocity[0]");
        return GetValue<Vector>(m_vecVelocity);
}

crashes the game when reading.

It's because the proper prop for vecVelocity is DT_BasePlayer->localdata->m_vecVelocity[0]


Animal sniffer

Hello @kohsuke.
Seeing as you recently set the compiler target back to 5, I wanted to help you maintain this compatibility.
There is still one unresolved issue:
--- animal-sniffer-maven-plugin:1.15:check (ensure-java-1.5-class-library) @ github-api ---
Checking unresolved references to org.codehaus.mojo.signature:java15:1.0
X:\Git\github\github-api\src\main\java\org\kohsuke\github\GHContent.java:81: Undefined reference: byte[] javax.xml.bind.DatatypeConverter.parseBase64Binary(String)
X:\Git\github\github-api\src\main\java\org\kohsuke\github\GHContent.java:182: Undefined reference: String javax.xml.bind.DatatypeConverter.printBase64Binary(byte[])
X:\Git\github\github-api\src\main\java\org\kohsuke\github\GHRepository.java:1165: Undefined reference: String javax.xml.bind.DatatypeConverter.printBase64Binary(byte[])

Hope that you can integrate this.

@KostyaSha Could you please voice your concern via comments?
The new reactions don't trigger notifications.
I am very interested in the obstacles.


Activate redux-devtools-extension (if available)

Hey thanks for the pull request! It looks like I've done a poor job documenting the enhancers extension point inside ember-redux that lets you opt in for dev tooling.
Here is an example of it
https://github.com/toranb/ember-redux-ddau-example/blob/master/app/enhancers/index.js
I prefer this to adding more complexity inside the redux service itself. That said, I think you've highlighted the missing pull request to the docs GH-pages site on "time travel/dev tooling"
You mind opening a pull request for the documentation so others see the idiomatic enhancer option mentioned above?
Sorry for the lack of docs about dev tooling this far!

I just overlooked http://www.ember-redux.com/configure/, so from my standpoint this is clear enough and needs no further doku.


Can not insert SharedMap into SharedObjectSequence

Describe the bug
I have the DataObject like this:
protected async initializingFirstTime() {
    const sequence = SharedObjectSequence.create(this.runtime);
    this.root.set("sequence", sequence.handle);
}

public async insertNode () {
    const children = await this.root.get<IFluidHandle<SharedObjectSequence<IFluidHandle<SharedMap>>>>("sequence").get();
    const map = SharedMap.create(this.runtime)
    children.insert(0, [map.handle as IFluidHandle<SharedMap>])
}

I definition insertNode method and try to insert children node when user typed some content.
But after init this data object and call insertNode(), I got the error: initialMessages called twice
I just wanner add SharedMap into SharedObjectSequence. Is any wrong for this case?

To Reproduce
I reappear this issue by draft-js example, here are commit code and insert-node-test branch

This looks like a duplicate of #3707


Fix ability cooldowns being triggered when GCD results in failure

Fixes #51 and fixes #71, I believe #48 is already addressed as well with CooldownState::set and ChargeState::set, but maybe an insert method would make it more clear, not too convinced either way.
doctests were failing due to a Debug bound in ActionLike, popped those on.
The most significant changes are these

Check ready prior to triggering cooldowns, this is the fix for # 71

Also added test for this

Added an OnGlobalCooldown error for when an ability fails due to the GCD.
Invert order of cooldown checks in ready so that an ability on cooldown returns an OnCooldown error before an OnGlobalCooldown error.

I can remove OnGlobalCooldown if its not a good addition, but I think it has merit for giving context on why an ability failed.

Good changes :) They need RELEASES.md notes though :) Start a new heading for 0.11 (unreleased) please.

Good changes :) They need RELEASES.md notes though :) Start a new heading for 0.11 (unreleased) please.

Updated RELEASES.md, thanks for the quick reply 😄!


ERROR: could not locate path that contains java

Describe the problem
Hi.
I'm trying to run a server on Java 19 but I'm getting an error.
All other versions of Java 8, 11, 17 work fine.
Container definition
Paste run command or compose file here

Container logs
[init] ERROR: your Docker provider has an annoying flaw where it
[init] tries to set PATH even though the container establishes
[init] a very specific value.
[init] ERROR: could not locate path that contains java

What is your Docker provider?

root@server:~# uname -a
Linux server 4.9.0-15-amd64 #1 SMP Debian 4.9.258-1 (2021-03-08) x86_64 GNU/Linux
root@server:~# cat /etc/issue
Debian GNU/Linux 9 \n \l

How do you run Docker?

docker container run -d -it -e UID=$(id -u s1) -e GID=$(id -u s1) -p 25565:25565 -v /home/servers/s1:/data -e TZ=Europe/Warsaw -e EULA=TRUE -e GUI=FALSE -e CUSTOM_SERVER=server.jar --name s1 itzg/minecraft-server:java19

The problem only occurs on Java 19.

Thanks for the additional context. I was suspecting a Portainer issue, but as you have found might be something about the java8 base image.

I don't use Portainer. Linux command line only. Do you know any solution that would help me get my server running on java 19?

Why do you need Java 19?
Otherwise, I am not able to look into this soon, so you will need to further investigate and a PR would be great.

What is the $PATH set to when it runs? You can test this in the container by tweaking the run command:
docker container run --rm -it -e UID=$(id -u s1) -e GID=$(id -u s1) -p 25565:25565 -v /home/servers/s1:/data -e TZ=Europe/Warsaw -e EULA=TRUE -e GUI=FALSE -e CUSTOM_SERVER=server.jar --name s1 --entrypoint /usr/bin/bash itzg/minecraft-server:java19

Once running you'll be at a bash prompt in the container.  Try some of the following command to get an idea of the state of the container:
echo $PATH
which java
command -v java

You can then exit the container by type exit

root@dd6d64b630ae:/data# echo $PATH
/opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
root@dd6d64b630ae:/data# which java
root@dd6d64b630ae:/data# command -v java
/opt/java/openjdk/bin/java
root@dd6d64b630ae:/data#

😕 It's confusing that which failed but command worked.  Instead of command java --version you should instead try just java --version  if that doesn't work (which it should), then try /opt/java/openjdk/bin/java --version

Oh, that command java --version should have worked (sorry about that).  That is odd.  Are you sure you have the latest image, maybe re-pull the image?

Reading through multiple issues on the error generated it seems that it could either be the base adoptium image the container is working with, or the version of docker installed.  Are you running the latest docker version?

root@7029f805e9e6:/data# command java --version
[0.007s][warning][os,thread] Failed to start thread "GC Thread#0" - pthread_create failed (EPERM) for attributes: stacksize: 1024k, guardsize: 4k, detached.
[0.008s][error  ][gc,task  ] Failed to create worker thread
root@7029f805e9e6:/data# /opt/java/openjdk/bin/java --version
[0.009s][warning][os,thread] Failed to start thread "GC Thread#0" - pthread_create failed (EPERM) for attributes: stacksize: 1024k, guardsize: 4k, detached.
[0.009s][error  ][gc,task  ] Failed to create worker thread
root@7029f805e9e6:/data# java --version
[0.008s][warning][os,thread] Failed to start thread "GC Thread#0" - pthread_create failed (EPERM) for attributes: stacksize: 1024k, guardsize: 4k, detached.
[0.011s][error  ][gc,task  ] Failed to create worker thread
root@7029f805e9e6:/data# command java --version
[0.009s][warning][os,thread] Failed to start thread "GC Thread#0" - pthread_create failed (EPERM) for attributes: stacksize: 1024k, guardsize: 4k, detached.
[0.009s][error  ][gc,task  ] Failed to create worker thread
root@7029f805e9e6:/data#

root@server:~# docker version
Client: Docker Engine - Community
 Version:           19.03.9
 API version:       1.40
 Go version:        go1.13.10
 Git commit:        9d988398e7
 Built:             Fri May 15 00:24:16 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.9
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.10
  Git commit:       9d988398e7
  Built:            Fri May 15 00:22:48 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.2
  GitCommit:<PHONE_NUMBER>f7fe2f4e74d43e2fc7ccd237edcbce
 runc:
  Version:          1.0.0-rc6+dev
  GitCommit:        09c8266bf2fcf9519a651b04ae54c967b9ab86ec
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

It looks like you're on an older Debian version (v9).  It looks like the latest Docker supports v10 and newer of Debian.  Do you know if you're able to update Docker to any newer version or if you're at the max of what's supported for your Debian version?

Something else you could try if you wanted to test something before a Docker/OS upgrade is if different images experience the same thing.  itzg/minecraft-server:java19 is based off eclipse-temurin:19-jre-jammy (if I'm following the code correctly).  You could try each one and see if you get a working java executable, java --version, in each of them substituting in the appropriate image:tag:
docker container run --rm -it image:tag
Using the following tags:

eclipse-temurin:19-jre-jammy
eclipse-temurin:19-jre-focal
eclipse-temurin:19-jre-alpine

After testing, it turns out that only 19-jre-jammy does not work.
19-jre-focal and 19-jre-alpine work fine.

Yeah, I figured that was going to happen becaus itzg/minecraft-server:java17 worked for you and that was based off of focal.  I think there's two solutions to this and that would be either upgrade your OS (at a minimum to v10) so that you can upgrade to the current Docker version (I looked and it seems you're on the latest/last version available for Debian v9), or change the base image for v19 to be focal based.  I'll leave that to be a discussion w/ you and @itzg. 😄

Yeah, I figured that was going to happen because itzg/minecraft-server:java17 worked for you and that was based off of focal. I think there's two solutions to this and that would be either upgrade your OS (at a minimum to v10) so that you can upgrade to the current Docker version (I looked and it seems you're on the latest/last version available for Debian v9), or change the base image for v19 to be focal based. I'll leave that to be a discussion w/ you and @itzg. 😄

Thank you very much for help.
@itzg Why is there focal in all Java versions and jammy in Java 19? Is it possible to set focal?

Meanwhile, found the issue that brought in Java 19 image and doesn't look like there was a requirement for jammy. Bumping down to focal makes the most sense all around.


NSFS | NC | Add Condition in authorize_request_policy

Explain the changes

Add Condition in authorize_request_policy in s3_rest.
To have the details of the account owner also return the owner_account in the function  read_bucket_sdk_policy_info.
In nsfs add the owner_account with mock value just to return a value like in the function read_bucket_sdk_policy_info.

Issues: Fixed (partial) #8080

Currently, after an account name is updated it results in failure in S3 request that the account tries to perform on the bucket (AccessDenied). It happens because the bucket_owner is with the previous name and the account_identifier is with the new name.

after this fix, the S3 request should not return an error, although there are still GAPS:

The buckets that the account owns still have the properties system_owner and bucket_owner with the previous name (in the bucket config).
Currently, the s3_policy is set in the bucket config files with the name of the account, and this will also not be updated, for example: Principal: { AWS: 'user10' }.

Testing Instructions:
Manual Test:
Before you start: Change the config.NSFS_CHECK_BUCKET_BOUNDARIES = false;

First, create the FS_ROOT and a directory for a bucket: mkdir -p /tmp/nsfs_root1/my-bucket and give permissions chmod 777 /tmp/nsfs_root1/ chmod 777 /tmp/nsfs_root1/my-bucket.
This will be the argument for:

new_buckets_path flag  /tmp/nsfs_root1 (that we will use in the account commands)
path in the buckets commands /tmp/nsfs_root1/my-bucket (that we will use in bucket commands).

Run the nsfs server: sudo node src/cmd/nsfs --debug 5
Create an account with an access key and secret key:
sudo node src/cmd/manage_nsfs account add --name shira-1003 --new_buckets_path /tmp/nsfs_root1 --access_key <access-key> --secret_key <secret-key> --uid 1003 --gid 1003
Create a bucket for the account
sudo node src/cmd/manage_nsfs bucket add --name shira-1003-bucket-1 --owner shira-1003 --path /tmp/nsfs_root1/my-bucket
Create the alias for sending the requests using AWS CLI (access key and secret key were omitted):
alias s3-nc-user-1='AWS_ACCESS_KEY_ID=<access-key>  AWS_SECRET_ACCESS_KEY=<secret-key> aws --no-verify-ssl --endpoint-url https://localhost:6443'
Send S3 requests, for example: s3-nc-user-1 s3api put-object --bucket shira-1003-bucket-1 --key hello.txt (should work).
Rename the account (account update):
sudo node src/cmd/manage_nsfs account update --name shira-1003 --new_name shira-1003-new
See that the owner of the bucket was not changed (still with the previous name shira-1003)
sudo node src/cmd/manage_nsfs bucket status --name shira-1003-bucket-1
Send S3 request, for example: s3-nc-user-1 s3api put-object --bucket shira-1003-bucket-1 --key hello.txt (should work after the fix, before that it throws an error). Please make sure that you send the request after the bucket_namespace_cache is clear, else you would not be able to reproduce the initial issue).

[ ] Doc added/updated
[ ] Tests added

LGTM

@shirady why did you do Before you start: Change the config.NSFS_CHECK_BUCKET_BOUNDARIES = false; ?
will this fix work without this change?

@romayalon I always change the config for running the s3 operation in NC NSFS, it should work the same.

@shirady Why are you doing that?

Thanks @shirady! please try to reproduce and open a bug if needed, we don't want to mask a bug by setting this config 👍🏻

Thanks @shirady! please try to reproduce and open a bug if needed, we don't want to mask a bug by setting this config 👍🏻

@romayalon I opened the issue #8177.


--label-file weird "unwanted" behavior ?

While refactoring, I stumbled upon a weird behavior : --label-file on docker run command behave exactly like --environment-file. This means, if there is a placeholder (i.e. a simple key, no = sign, no value), it will get the value from the environment variable.
$ cat labelfil
foo=bar
bar
$ env bar=baz docker run --name foo -d --label-file=labelfile busybox top
# […)
$ docker inspect --format="{{ .Config.Labels }}" foo
map[bar:baz foo:bar]

I'm not sure if this is a wanted feature or just happened to be that way because of the code.
/cc @docker/core-maintainers

I'm not aware of that being added as a feature, so that looks like a bug to me, possibly because it happened to use the same parsing logic.
ping @duglin ?

From looking at the docs for "docker run", I found this:
$ docker run -l my-label --label com.example.foo=bar ubuntu bash

The my-label key doesn’t specify a value so the label defaults to an empty string("").

so it looks like bar is supposed to be empty and if so then yea I agree, it sounds like a bug.  But we should probably get someone like @rhdan to weight-in since I think he had a hand in adding label support.

No those were only the SELinux labels, not these, so, yes, it's a bug


Project Summary: Recently Viewed Items

Opened Issue #131
Consolidated <ordering-panel>'s
Updated mockData for easier unit testing

@spadgett , @jeff-phillips-18 - All review issues addressed, thanks

Hi @spadgett, when you get a moment, this is waiting on your approval/merge.  -thanks


Added folder for static content - favicon.ico

I'm not sure why this is superior. static and public are synonyms in this context. Neither the system nor I really care where favicon.ico really lives since it's served by its own special middleware.
I could be talked into renaming static to public, but having both seems superfluous.
What do you think, @korczis?

@erikras, you are right we do not need both but I think it will be nice some folder for static/public content.
In my fork, I would like to add more static stuff from html5 boilerplate - https://html5boilerplate.com/

apple-touch-icon.png
browserconfig.xml
crossdomain.xml
tile-wide.png
tile.png
robots.txt
humans.txt

I'm fine with favicon living in static since it sort of belongs there, even if it is served differently (for reasons I do not entirely understand). This will also keep static in git for anyone to add their html5 boilerplate stuff. An acceptable compromise?

@erikras, this sounds perfect to me. I am for it.

btw, why you closed this issue without merging? Do you plan to implement it yourself?

I did already. It's linked above my last comment.

@erikras, perfect, thanks.


No topic provided by originator

Unless the issue is made clear, can we Close/Reject this ticket?

Original topic = code. Not related to DroidScript. Closing if no response by originator.
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
    <remote name="89886991208" fetch=".." review="https://android-review.googlesource.com/" />
    <default revision="master" remote="aosp" sync-j="4" />
    <project path="adk1/board" name="device/google/accessory/arduino" />
    <project path="adk1/app" name="device/google/accessory/demokit" />
    <project path="adk2012/app" name="device/google/accessory/adk2012" />
    <project path="adk2012/board" name="device/google/accessory/adk2012_demo" />
    <project path="external/ide" name="platform/external/arduino-ide" />
    <project path="external/toolchain" name="platform/external/codesourcery" />
</manifest>


Operand/shape error

Sending a query from Rasa to the action server generates the following error:
score = np.sum((self.standard_questions_encoder * query_vector), axis=1) / (self.standard_questions_encoder_len * (np.sum(query_vector * query_vector) ** 0.5)) ValueError: operands could not be broadcast together with shapes (1000,3072) (768,)
The very similar code from the bert-as-service example,
score = np.sum(query_vec * doc_vecs, axis=1) / np.linalg.norm(doc_vecs, axis=1)
works as expected.

@francisjervis Hey actually I also got the same shape error but soon find that I was using the wrong variable. I works like charm. Thanks to @nghuyong and contributors...😉


Unnecessary logging noise for non-authenticated GCS access

System information

Ubuntu 16.04
Python 3.6
TF 1.12

Describe the current behavior
Unnecessary access to GCP metadata endpoint, 10 retries, and lots of logging.
Describe the expected behavior
Should not be trying to access GCP metadata endpoint.
Code to reproduce the issue
$ python
>> tf.gfile.Exists("gs://tfds-data")  # this is a public bucket, doesn’t need any auth
2019-02-03 02:51:58.175696: I tensorflow/core/platform/cloud/retrying_utils.cc:73] The operation failed and will be automatically retried in 0.12376 seconds (attempt 1 out of 10), caused by: Unavailable: Error executing an HTTP request: libcurl code 6 meaning 'Couldn't resolve host name', error details: Couldn't resolve host 'metadata'

...(more of the same)

2019-02-03 02:52:05.330143: I tensorflow/core/platform/cloud/retrying_utils.cc:73] The operation failed and will be automatically retried in 1.29527 seconds (attempt 10 out of 10), caused by: Unavailable: Error executing an HTTP request: libcurl code 6 meaning 'Couldn't resolve host name', error details: Couldn't resolve host 'metadata'
2019-02-03 02:52:06.626410: W tensorflow/core/platform/cloud/google_auth_provider.cc:157] All attempts to get a Google authentication bearer token failed, returning an empty token. Retrieving token from files failed with "Not found: Could not locate the credentials file.". Retrieving token from GCE failed with "Aborted: All 10 retry attempts failed. The last failure: Unavailable: Error executing an HTTP request: libcurl code 6 meaning 'Couldn't resolve host name', error details: Couldn't resolve host 'metadata'".

(Linking issue tensorflow/datasets#38)

My fix in a252fe8 adds a hook to avoid the "unnecessary access" part of this bug; we still get noisier logs than I'd like. I'm going to repurpose this issue for "make logs less chatty for expected retries".

Hi There,
We are checking to see if you still need help on this, as you are using an older version of tensorflow which is officially considered end of life . We recommend that you upgrade to the latest 2.x version and let us know if the issue still persists in newer versions. Please open a new issue for any help you need against 2.x, and we will get you the right help.
This issue will be closed automatically 7 days from now. If you still need help with this issue, please provide us with more information.

@rsepassi Can you please confirm if the issue is being solved with the above comment.


add usage doc for kubeval

Sorry about taking multiple rounds of reviews on this small doc PR.
Hopefully all comments are addressed.

Sorry about taking multiple rounds of reviews on this small doc PR.
Hopefully all comments are addressed.

np. The first few docs sets the example and the bar for the rest of the catalog. It's very hard to overthink documentation given how important it is to usability.


fix: When serves both http&websocket,ws connection denied with "bad handshake".

When using package gorilla/websocket, calls Upgrader.Upgrade(w http.ResponseWriter, r *http.Request, responseHeader http.Header),it asserts the ResponseWriter to be a Hijacker implementation, if assertion fails ws connection will be denied.
Client error:  websocket: bad handshake
Server error:  websocket: response does not implement http.Hijacker
gorilla/websocket code details：server.go
173   	h, ok := w.(http.Hijacker)
174   	if !ok {
175  		return u.returnError(w, r, http.StatusInternalServerError, "websocket: response does not implement http.Hijacker")
176  	}

Please update the title and contents in English.

@nealwon I need to do another PR fix CI, please wait :)

Codecov Report

Merging #160 (11cb393) into master (6492c49) will decrease coverage by 0.11%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #160      +/-   ##
==========================================
- Coverage   64.64%   64.53%   -0.12%
==========================================
  Files          22       22
  Lines        1089     1094       +5
==========================================
+ Hits          704      706       +2
- Misses        330      334       +4
+ Partials       55       54       -1

Impacted Files
Coverage Δ

plugins/http/server.go
42.10% <0.00%> (-4.05%)
:arrow_down:

sampler.go
81.96% <0.00%> (+3.27%)
: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 6492c49...11cb393. Read the comment docs.

Could you share how this case happens?
gorilla/websocket seems a 3rd pary framework, rather than this one bundled with go core lib only.
If you plan to support this new library, you should land your codes to go2sky-plugins repository.

Yes，it's a popular 3rd-part lib.
In my project, I use this lib(gorilla/websocket) and want to try to use skywalking as performance monitoring.When i load go2sky lib, service start up normally,but all clients cannot connect to server due to "bad handshake".
Non-core libs not supported by go2sky,I can use fork to test skywalking.
Now i'll close this PR!

I mean this should be a plugin, not a core lib change.
You could create another client to inherit this and implement a new interface, which would be more nice.

OK, thx.


adjustments for latest version of SLURM

Hi James,  This problem resulted from a change in starting index for certain SLURM environment variables.  The latest pull request address this issue, I believe in a way that works for both old and new versions of SLURM.
On Thu, Sep 21, 2017 at 4:50 PM, R Modrak<EMAIL_ADDRESS>wrote:
Thanks for pointing this out.  I'm working on a fix now...

On Mon, Sep 18, 2017 at 6:50 AM, James A. Smith<EMAIL_ADDRESS>wrote:

    Hi Ryan,

    I have seisflows working with tigergpu_sm, but the taskid issue I brought up previously is an issue still and now affects tiger. If you run the Checkers3D example on tiger you should see that the index out of range error is happening because of the taskid.

    Anyway, it's not that important for me right now since I'm using the gpu small.

    James

Thanks, Ryan. I tried your fix and I still get the same error. I ran it using the devel version of seisflows. Let me know if I can help you with any more tests.
IOError: [Errno 2] No such file or directory:
Traceback (most recent call last):
File "/var/spool/slurmd/job3660559/slurm_script", line 41, in
func(**kwargs)
File "/tigress/jas11/packages/seisflows/seisflows/solver/specfem3d.py", line 106, in eval_func
super(specfem3d, self).eval_func(*args, **kwargs)
File "/tigress/jas11/packages/seisflows/seisflows/solver/base.py", line 193, in eval_func
unix.cd(self.cwd)
File "/tigress/jas11/packages/seisflows/seisflows/solver/base.py", line 585, in cwd
return join(PATH.SOLVER, self.source_name)
File "/tigress/jas11/packages/seisflows/seisflows/solver/base.py", line 580, in source_name
return self.source_names[self.taskid]
IndexError: list index out of range

From: Ryan Modrak<EMAIL_ADDRESS>Sent: Sunday, September 24, 2017 6:10 PM
To: rmodrak/seisflows
Cc: Subscribed
Subject: [rmodrak/seisflows] adjustments for latest version of SLURM (#78)
Hi James, This problem resulted from a change in starting index for certain SLURM environment variables. The latest pull request address this issue, I believe in a way that works for both old and new versions of SLURM.
On Thu, Sep 21, 2017 at 4:50 PM, R Modrak rmodrak<EMAIL_ADDRESS>wrote:
Thanks for pointing this out.  I'm working on a fix now...
On Mon, Sep 18, 2017 at 6:50 AM, James A. Smith<EMAIL_ADDRESS>wrote:
Hi Ryan,

I have seisflows working with tigergpu_sm, but the taskid issue I brought up previously is an issue still and now affects tiger. If you run the Checkers3D example on tiger you should see that the index out of range error is happening because of the taskid.

Anyway, it's not that important for me right now since I'm using the gpu small.

James

You can view, comment on, or merge this pull request online at:
https://github.com/rmodrak/seisflows/pull/78
Commit Summary

clarified comments
refactored postprocess.base
revised preprocessing, postprocesing docstrings
adjustments for latest version of SLURM
fix travis import errors

File Changes

M scripts/visualize/specfem2d/quickplothttps://github.com/rmodrak/seisflows/pull/78/files#diff-0 (5)
M seisflows/postprocess/base.pyhttps://github.com/rmodrak/seisflows/pull/78/files#diff-1 (24)
A seisflows/postprocess/default.pyhttps://github.com/rmodrak/seisflows/pull/78/files#diff-2 (17)
M seisflows/preprocess/base.pyhttps://github.com/rmodrak/seisflows/pull/78/files#diff-3 (3)
A seisflows/preprocess/default.pyhttps://github.com/rmodrak/seisflows/pull/78/files#diff-4 (18)
M seisflows/preprocess/double_difference.pyhttps://github.com/rmodrak/seisflows/pull/78/files#diff-5 (15)
M seisflows/system/slurm_lg.pyhttps://github.com/rmodrak/seisflows/pull/78/files#diff-6 (105)

Patch Links:

https://github.com/rmodrak/seisflows/pull/78.patch
https://github.com/rmodrak/seisflows/pull/78.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/rmodrak/seisflows/pull/78, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AE4EaIkZ92tenMn1zXjaFdumm-OQBQneks5sluFUgaJpZM4PiEEf.

Nevermind, I checked it and it worked for 2 sources. One source is not finishing this evening but it may just be the cluster.
James

From: James A. Smith
Sent: Sunday, September 24, 2017 8:39 PM
To: rmodrak/seisflows
Subject: RE: [rmodrak/seisflows] adjustments for latest version of SLURM (#78)
Thanks, Ryan. I tried your fix and I still get the same error. I ran it using the devel version of seisflows. Let me know if I can help you with any more tests.
IOError: [Errno 2] No such file or directory:
Traceback (most recent call last):
File "/var/spool/slurmd/job3660559/slurm_script", line 41, in
func(**kwargs)
File "/tigress/jas11/packages/seisflows/seisflows/solver/specfem3d.py", line 106, in eval_func
super(specfem3d, self).eval_func(*args, **kwargs)
File "/tigress/jas11/packages/seisflows/seisflows/solver/base.py", line 193, in eval_func
unix.cd(self.cwd)
File "/tigress/jas11/packages/seisflows/seisflows/solver/base.py", line 585, in cwd
return join(PATH.SOLVER, self.source_name)
File "/tigress/jas11/packages/seisflows/seisflows/solver/base.py", line 580, in source_name
return self.source_names[self.taskid]
IndexError: list index out of range

From: Ryan Modrak<EMAIL_ADDRESS>Sent: Sunday, September 24, 2017 6:10 PM
To: rmodrak/seisflows
Cc: Subscribed
Subject: [rmodrak/seisflows] adjustments for latest version of SLURM (#78)
Hi James, This problem resulted from a change in starting index for certain SLURM environment variables. The latest pull request address this issue, I believe in a way that works for both old and new versions of SLURM.
On Thu, Sep 21, 2017 at 4:50 PM, R Modrak rmodrak<EMAIL_ADDRESS>wrote:
Thanks for pointing this out.  I'm working on a fix now...
On Mon, Sep 18, 2017 at 6:50 AM, James A. Smith<EMAIL_ADDRESS>wrote:
Hi Ryan,

I have seisflows working with tigergpu_sm, but the taskid issue I brought up previously is an issue still and now affects tiger. If you run the Checkers3D example on tiger you should see that the index out of range error is happening because of the taskid.

Anyway, it's not that important for me right now since I'm using the gpu small.

James

You can view, comment on, or merge this pull request online at:
https://github.com/rmodrak/seisflows/pull/78
Commit Summary

clarified comments
refactored postprocess.base
revised preprocessing, postprocesing docstrings
adjustments for latest version of SLURM
fix travis import errors

File Changes

M scripts/visualize/specfem2d/quickplothttps://github.com/rmodrak/seisflows/pull/78/files#diff-0 (5)
M seisflows/postprocess/base.pyhttps://github.com/rmodrak/seisflows/pull/78/files#diff-1 (24)
A seisflows/postprocess/default.pyhttps://github.com/rmodrak/seisflows/pull/78/files#diff-2 (17)
M seisflows/preprocess/base.pyhttps://github.com/rmodrak/seisflows/pull/78/files#diff-3 (3)
A seisflows/preprocess/default.pyhttps://github.com/rmodrak/seisflows/pull/78/files#diff-4 (18)
M seisflows/preprocess/double_difference.pyhttps://github.com/rmodrak/seisflows/pull/78/files#diff-5 (15)
M seisflows/system/slurm_lg.pyhttps://github.com/rmodrak/seisflows/pull/78/files#diff-6 (105)

Patch Links:

https://github.com/rmodrak/seisflows/pull/78.patch
https://github.com/rmodrak/seisflows/pull/78.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/rmodrak/seisflows/pull/78, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AE4EaIkZ92tenMn1zXjaFdumm-OQBQneks5sluFUgaJpZM4PiEEf.

Hi James,
Thanks very much for your help testing.
Just tried two tests on tiger-- 1 source and 2 sources.  Both appeared to
pass.  I'll go ahead and accept the pull request.  Feel free to respond
back if there are future problems.
Ryan
On Sun, Sep 24, 2017 at 7:22 PM, James Smith<EMAIL_ADDRESS>wrote:

Nevermind, I checked it and it worked for 2 sources. One source is not
finishing this evening but it may just be the cluster.
James

From: James A. Smith
Sent: Sunday, September 24, 2017 8:39 PM
To: rmodrak/seisflows
Subject: RE: [rmodrak/seisflows] adjustments for latest version of SLURM
(#78)
Thanks, Ryan. I tried your fix and I still get the same error. I ran it
using the devel version of seisflows. Let me know if I can help you with
any more tests.
IOError: [Errno 2] No such file or directory:
Traceback (most recent call last):
File "/var/spool/slurmd/job3660559/slurm_script", line 41, in
func(**kwargs)
File "/tigress/jas11/packages/seisflows/seisflows/solver/specfem3d.py",
line 106, in eval_func
super(specfem3d, self).eval_func(*args, **kwargs)
File "/tigress/jas11/packages/seisflows/seisflows/solver/base.py", line
193, in eval_func
unix.cd(self.cwd)
File "/tigress/jas11/packages/seisflows/seisflows/solver/base.py", line
585, in cwd
return join(PATH.SOLVER, self.source_name)
File "/tigress/jas11/packages/seisflows/seisflows/solver/base.py", line
580, in source_name
return self.source_names[self.taskid]
IndexError: list index out of range

From: Ryan Modrak<EMAIL_ADDRESS>Sent: Sunday, September 24, 2017 6:10 PM
To: rmodrak/seisflows
Cc: Subscribed
Subject: [rmodrak/seisflows] adjustments for latest version of SLURM (#78)
Hi James, This problem resulted from a change in starting index for
certain SLURM environment variables. The latest pull request address this
issue, I believe in a way that works for both old and new versions of SLURM.
On Thu, Sep 21, 2017 at 4:50 PM, R Modrak rmodrak@gmail.com<mailto:rmodr
<EMAIL_ADDRESS>wrote:
Thanks for pointing this out. I'm working on a fix now...
On Mon, Sep 18, 2017 at 6:50 AM, James A. Smith<EMAIL_ADDRESS>wrote:
Hi Ryan,
I have seisflows working with tigergpu_sm, but the taskid issue I brought
up previously is an issue still and now affects tiger. If you run the
Checkers3D example on tiger you should see that the index out of range
error is happening because of the taskid.
Anyway, it's not that important for me right now since I'm using the gpu
small.
James

You can view, comment on, or merge this pull request online at:
https://github.com/rmodrak/seisflows/pull/78
Commit Summary

clarified comments
refactored postprocess.base
revised preprocessing, postprocesing docstrings
adjustments for latest version of SLURM
fix travis import errors

File Changes

M scripts/visualize/specfem2d/quickplot<https://github.com/
rmodrak/seisflows/pull/78/files#diff-0> (5)
M seisflows/postprocess/base.py<https://github.com/rmodrak/
seisflows/pull/78/files#diff-1> (24)
A seisflows/postprocess/default.py<https://github.com/rmodrak/
seisflows/pull/78/files#diff-2> (17)
M seisflows/preprocess/base.py<https://github.com/rmodrak/
seisflows/pull/78/files#diff-3> (3)
A seisflows/preprocess/default.py<https://github.com/rmodrak/
seisflows/pull/78/files#diff-4> (18)
M seisflows/preprocess/double_difference.py<https://github.
com/rmodrak/seisflows/pull/78/files#diff-5> (15)
M seisflows/system/slurm_lg.py<https://github.com/rmodrak/
seisflows/pull/78/files#diff-6> (105)

Patch Links:

https://github.com/rmodrak/seisflows/pull/78.patch
https://github.com/rmodrak/seisflows/pull/78.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://github.com/
rmodrak/seisflows/pull/78>, or mute the thread<https://github.com/
notifications/unsubscribe-auth/AE4EaIkZ92tenMn1zXjaFdumm-
OQBQneks5sluFUgaJpZM4PiEEf>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rmodrak/seisflows/pull/78#issuecomment-331767909, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AERpSntonAh8BUWA6j5L9PQ_G5Bq2PYFks5slxx9gaJpZM4PiEEf
.

Dear Dr Ryan,
I am trying to run the examples 2D at seisflow and i am not able to run.
My tests are sucesfuly done and i realise that woulb be impossible to run since the file legacy,py it is not at the package for download.
Also i found other package at  https://github.com/DmBorisov/SeisFlows_tunnel but it is also not working to run this examples.
Could you please help me?
I am very interest to use seisflow, thank you very much for your time.

Hi Kati,
Please see the following newly created issue:
#81
Thanks,
Ryan


Validate against the new bourbon schemas

Sorry, I've just saw this PR. This has already been taken care in: https://github.com/Adobe-Marketing-Cloud/reactor-validator/pull/4.