[Bug]: "ERROR: WAL archive check failed for server local: Expected empty archive" during recovery

Is there an existing issue already for this bug?

[x] I have searched for an existing issue, and could not find anything. I believe this is a new bug.

I have read the troubleshooting guide

[x] I have read the troubleshooting guide and I think this is a new bug.

I am running a supported version of CloudNativePG

[x] I have read the troubleshooting guide and I think this is a new bug.

Contact Details
<EMAIL_ADDRESS>Version
1.24 (latest patch)
What version of Kubernetes are you using?
1.31
What is your Kubernetes environment?
Other
How did you install the operator?
YAML manifest
What happened?
I am using Minikube and AWS s3. Tried this with 1.25.0 and 1.24.2 and 1.23.6.
I have created a backup of a cluster that was initialized with init db. Then I delete the cluster and this time i start it with recovery pointing to the backup i just made. I get an error during recovery, the error is "ERROR: WAL archive check failed for server local: Expected empty archive". And yes, the error is correct, there is no empty archive. But is this an error? Don't we need a non-empty archive to be able to recover from it?
I have run the following command:
barman-cloud-check-wal-archive --cloud-provider aws-s3 s3://metal-backup-eu/cnpg-backups/ local

and yes, I get the same error.
If I add the cnpg.io/skipEmptyWalArchiveCheck: enabled annotation then the recovery does work, however i do get some errors.
Please help!
Cluster resource
---
apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
  name: database
  # annotations:
  #   cnpg.io/skipEmptyWalArchiveCheck: enabled
spec:
  instances: 3
  storage:
    size: 5Gi
    storageClass: local
  # bootstrap:
  #   recovery:
  #     source: backup
  externalClusters:
    - name: backup
      barmanObjectStore:
        destinationPath: "s3://metal-backup-eu/cnpg-backups/"
        serverName: local
        s3Credentials:
          accessKeyId:
            name: aws
            key: AWS_ACCESS_KEY_ID
          secretAccessKey:
            name: aws
            key: AWS_SECRET_ACCESS_KEY
  backup:
    retentionPolicy: 7d
    target: prefer-standby
    barmanObjectStore:
      destinationPath: "s3://metal-backup-eu/cnpg-backups/"
      serverName: local
      s3Credentials:
        accessKeyId:
          name: aws
          key: AWS_ACCESS_KEY_ID
        secretAccessKey:
          name: aws
          key: AWS_SECRET_ACCESS_KEY

Relevant log output
Failing full-recovery pod:
{"level":"info","ts":"2024-12-28T04:57:25.512796992Z","msg":"barman-cloud-check-wal-archive checking the first wal","logging_pod":"database-1-full-recovery"}
{"level":"info","ts":"2024-12-28T04:57:26.914684215Z","logger":"barman-cloud-check-wal-archive","msg":"2024-12-28 04:57:26,914 [23] ERROR: WAL archive check failed for server local: Expected empty archive","pipe":"stderr","logging_pod":"database-1-full-recovery"}
{"level":"error","ts":"2024-12-28T04:57:26.942015656Z","msg":"Error invoking barman-cloud-check-wal-archive","logging_pod":"database-1-full-recovery","options":["--cloud-provider","aws-s3","s3://metal-backup-eu/cnpg-backups/","local"],"exitCode":-1,"error":"exit status 1","stacktrace":"github.com/cloudnative-pg/machinery/pkg/log.(*logger).Error\n\tpkg/mod/github.com/cloudnative-pg/machinery@v0.0.0-20241219102532-2807bc88310d/pkg/log/log.go:125\ngithub.com/cloudnative-pg/barman-cloud/pkg/walarchive.(*BarmanArchiver).CheckWalArchiveDestination\n\tpkg/mod/github.com/cloudnative-pg/barman-cloud@v0.0.0-20241218093921-134c7de4954a/pkg/walarchive/cmd.go:178\ngithub.com/cloudnative-pg/barman-cloud/pkg/archiver.(*WALArchiver).CheckWalArchiveDestination\n\tpkg/mod/github.com/cloudnative-pg/barman-cloud@v0.0.0-20241218093921-134c7de4954a/pkg/archiver/archiver.go:131\ngithub.com/cloudnative-pg/cloudnative-pg/pkg/management/postgres.(*InitInfo).checkBackupDestination\n\tpkg/management/postgres/restore.go:961\ngithub.com/cloudnative-pg/cloudnative-pg/pkg/management/postgres.InitInfo.Restore\n\tpkg/management/postgres/restore.go:253\ngithub.com/cloudnative-pg/cloudnative-pg/internal/cmd/manager/instance/restore.restoreSubCommand\n\tinternal/cmd/manager/instance/restore/cmd.go:91\ngithub.com/cloudnative-pg/cloudnative-pg/internal/cmd/manager/instance/restore.NewCmd.func2\n\tinternal/cmd/manager/instance/restore/cmd.go:63\ngithub.com/spf13/cobra.(*Command).execute\n\tpkg/mod/github.com/spf13/cobra@v1.8.1/command.go:985\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\tpkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1117\ngithub.com/spf13/cobra.(*Command).Execute\n\tpkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1041\nmain.main\n\tcmd/manager/main.go:68\nruntime.main\n\t/opt/hostedtoolcache/go/1.23.4/x64/src/runtime/proc.go:272"}
{"level":"error","ts":"2024-12-28T04:57:26.942116284Z","msg":"Error while restoring a backup","logging_pod":"database-1-full-recovery","error":"unexpected failure invoking barman-cloud-wal-archive: exit status 1","stacktrace":"github.com/cloudnative-pg/machinery/pkg/log.(*logger).Error\n\tpkg/mod/github.com/cloudnative-pg/machinery@v0.0.0-20241219102532-2807bc88310d/pkg/log/log.go:125\ngithub.com/cloudnative-pg/cloudnative-pg/internal/cmd/manager/instance/restore.restoreSubCommand\n\tinternal/cmd/manager/instance/restore/cmd.go:93\ngithub.com/cloudnative-pg/cloudnative-pg/internal/cmd/manager/instance/restore.NewCmd.func2\n\tinternal/cmd/manager/instance/restore/cmd.go:63\ngithub.com/spf13/cobra.(*Command).execute\n\tpkg/mod/github.com/spf13/cobra@v1.8.1/command.go:985\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\tpkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1117\ngithub.com/spf13/cobra.(*Command).Execute\n\tpkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1041\nmain.main\n\tcmd/manager/main.go:68\nruntime.main\n\t/opt/hostedtoolcache/go/1.23.4/x64/src/runtime/proc.go:272"}

Working full-recovery pod, with cnpg.io/skipEmptyWalArchiveCheck: enabled:
{"level":"info","ts":"2024-12-28T04:46:14.15134636Z","msg":"Recovering from external cluster","logging_pod":"database-1-full-recovery","sourceName":"backup"}
{"level":"info","ts":"2024-12-28T04:46:15.826826715Z","msg":"Target backup found","logging_pod":"database-1-full-recovery","backup":{"backup_name":"backup-20241228042528","backup_label":"'START WAL LOCATION: 0/5000028 (file<PHONE_NUMBER>00000000000005)\\nCHECKPOINT LOCATION: 0/5000080\\nBACKUP METHOD: streamed\\nBACKUP FROM: standby\\nSTART TIME: 2024-12-28 04:25:29 UTC\\nLABEL: Barman backup cloud 20241228T042529\\nSTART TIMELINE: 1\\n'","begin_time":"Sat Dec 28 04:25:29 2024","end_time":"Sat Dec 28 04:25:30 2024","begin_time_iso":"2024-12-28T04:25:29.596862+00:00","end_time_iso":"2024-12-28T04:25:30.186088+00:00","BeginTime":"2024-12-28T04:25:29.596862Z","EndTime":"2024-12-28T04:25:30.186088Z","begin_wal":"000000010000000000000005","end_wal":"000000010000000000000005","begin_xlog":"0/5000028","end_xlog":"0/50000F8","systemid":"7453313727789342749","backup_id":"20241228T042529","error":"","timeline":1}}
{"level":"info","ts":"2024-12-28T04:46:24.989700887Z","msg":"Starting barman-cloud-restore","logging_pod":"database-1-full-recovery","options":["s3://metal-backup-eu/cnpg-backups/","local","20241228T042529","--cloud-provider","aws-s3","/var/lib/postgresql/data/pgdata"]}
{"level":"info","ts":"2024-12-28T04:46:38.94339276Z","msg":"Restore completed","logging_pod":"database-1-full-recovery"}
{"level":"info","ts":"2024-12-28T04:46:38.943464664Z","msg":"Creating new data directory","logging_pod":"database-1-full-recovery","pgdata":"/controller/recovery/datadir_3920931494","initDbOptions":["--username","postgres","-D","/controller/recovery/datadir_3920931494","--no-sync"]}
{"level":"info","ts":"2024-12-28T04:46:39.220629704Z","logger":"initdb","msg":"The files belonging to this database system will be owned by user \"postgres\".\nThis user must also own the server process.\n\nThe database cluster will be initialized with locale \"en_US.utf8\".\nThe default database encoding has accordingly been set to \"UTF8\".\nThe default text search configuration will be set to \"english\".\n\nData page checksums are disabled.\n\nfixing permissions on existing directory /controller/recovery/datadir_3920931494 ... ok\ncreating subdirectories ... ok\nselecting dynamic shared memory implementation ... posix\nselecting default \"max_connections\" ... 100\nselecting default \"shared_buffers\" ... 128MB\nselecting default time zone ... Etc/UTC\ncreating configuration files ... ok\nrunning bootstrap script ... ok\nperforming post-bootstrap initialization ... ok\n\nSync to disk skipped.\nThe data directory might become corrupt if the operating system crashes.\n\n\nSuccess. You can now start the database server using:\n\n    pg_ctl -D /controller/recovery/datadir_3920931494 -l logfile start\n\n","pipe":"stdout","logging_pod":"database-1-full-recovery"}
{"level":"info","ts":"2024-12-28T04:46:39.220646214Z","logger":"initdb","msg":"initdb: warning: enabling \"trust\" authentication for local connections\ninitdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.\n","pipe":"stderr","logging_pod":"database-1-full-recovery"}
{"level":"info","ts":"2024-12-28T04:46:39.234522343Z","msg":"Installed configuration file","logging_pod":"database-1-full-recovery","pgdata":"/controller/recovery/datadir_3920931494","filename":"pg_hba.conf"}
{"level":"info","ts":"2024-12-28T04:46:39.241516115Z","msg":"Installed configuration file","logging_pod":"database-1-full-recovery","pgdata":"/controller/recovery/datadir_3920931494","filename":"pg_ident.conf"}
{"level":"info","ts":"2024-12-28T04:46:39.248187468Z","msg":"Installed configuration file","logging_pod":"database-1-full-recovery","pgdata":"/controller/recovery/datadir_3920931494","filename":"custom.conf"}
{"level":"info","ts":"2024-12-28T04:46:39.29573851Z","msg":"Generated recovery configuration","logging_pod":"database-1-full-recovery","configuration":"recovery_target_action = promote\nrestore_command = 'barman-cloud-wal-restore s3://metal-backup-eu/cnpg-backups/ local --cloud-provider aws-s3 %f %p'\n"}
{"level":"info","ts":"2024-12-28T04:46:39.30985154Z","msg":"Aligned PostgreSQL configuration to satisfy both pg_controldata and cluster spec","logging_pod":"database-1-full-recovery","enforcedParams":{"max_connections":"100","max_locks_per_transaction":"64","max_prepared_transactions":"0","max_wal_senders":"10","max_worker_processes":"32"},"controldataParams":{"max_connections":100,"max_locks_per_transaction":64,"max_prepared_transactions":0,"max_wal_senders":10,"max_worker_processes":32},"clusterParams":{"max_worker_processes":32}}
{"level":"info","ts":"2024-12-28T04:46:39.316538321Z","msg":"Starting up instance","logging_pod":"database-1-full-recovery","pgdata":"/var/lib/postgresql/data/pgdata","options":["start","-w","-D","/var/lib/postgresql/data/pgdata","-o","-c port=5432 -c unix_socket_directories=/controller/run","-t 40000000","-o","-c listen_addresses='<IP_ADDRESS>'"]}
{"level":"info","ts":"2024-12-28T04:46:39.362683474Z","logger":"pg_ctl","msg":"waiting for server to start....2024-12-28 04:46:39.362 UTC [41] LOG:  redirecting log output to logging collector process","pipe":"stdout","logging_pod":"database-1-full-recovery"}
{"level":"info","ts":"2024-12-28T04:46:39.362695881Z","logger":"pg_ctl","msg":"2024-12-28 04:46:39.362 UTC [41] HINT:  Future log output will appear in directory \"/controller/log\".","pipe":"stdout","logging_pod":"database-1-full-recovery"}
{"level":"info","ts":"2024-12-28T04:46:39.363151928Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:46:39.362 UTC","process_id":"41","session_id":"676f82af.29","session_line_num":"1","session_start_time":"2024-12-28 04:46:39 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"ending log output to stderr","hint":"Future log output will go to log destination \"csvlog\".","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:46:39.363251188Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:46:39.362 UTC","process_id":"41","session_id":"676f82af.29","session_line_num":"2","session_start_time":"2024-12-28 04:46:39 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"starting PostgreSQL 17.2 (Debian 17.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:46:39.363260716Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:46:39.362 UTC","process_id":"41","session_id":"676f82af.29","session_line_num":"3","session_start_time":"2024-12-28 04:46:39 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"listening on IPv4 address \"<IP_ADDRESS>\", port 5432","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:46:39.376567263Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:46:39.376 UTC","process_id":"41","session_id":"676f82af.29","session_line_num":"4","session_start_time":"2024-12-28 04:46:39 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"listening on Unix socket \"/controller/run/.s.PGSQL.5432\"","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:46:39.393488975Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:46:39.393 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"1","session_start_time":"2024-12-28 04:46:39 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"database system was interrupted while in recovery at log time 2024-12-28 04:24:30 UTC","hint":"If this has occurred more than once some data might be corrupted and you might need to choose an earlier recovery target.","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:46:39.393549577Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:46:39.393 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"2","session_start_time":"2024-12-28 04:46:39 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"creating missing WAL directory \"pg_wal/archive_status\"","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:46:39.393564712Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:46:39.393 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"3","session_start_time":"2024-12-28 04:46:39 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"creating missing WAL directory \"pg_wal/summaries\"","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:46:41.51323932Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:46:41.512 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"4","session_start_time":"2024-12-28 04:46:39 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"restored log file \"00000002.history\" from archive","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:46:42.939823762Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:46:42.939 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"5","session_start_time":"2024-12-28 04:46:39 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"starting backup recovery with redo LSN 0/5000028, checkpoint LSN 0/5000080, on timeline ID 1","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:46:44.569650927Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:46:44.569 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"6","session_start_time":"2024-12-28 04:46:39 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"restored log file \"00000002.history\" from archive","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:46:56.073824968Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:46:56.073 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"7","session_start_time":"2024-12-28 04:46:39 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"restored log file \"000000010000000000000005\" from archive","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:46:56.100269031Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:46:56.100 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"8","session_start_time":"2024-12-28 04:46:39 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"starting archive recovery","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:46:56.114524558Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:46:56.114 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"9","session_start_time":"2024-12-28 04:46:39 UTC","virtual_transaction_id":"148/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"redo starts at 0/5000028","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:47:03.506614009Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:47:03.506 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"10","session_start_time":"2024-12-28 04:46:39 UTC","virtual_transaction_id":"148/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"restored log file \"000000020000000000000006\" from archive","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:47:03.53131095Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:47:03.530 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"11","session_start_time":"2024-12-28 04:46:39 UTC","virtual_transaction_id":"148/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"completed backup recovery with redo LSN 0/5000028 and end LSN 0/50000F8","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:47:03.531363214Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:47:03.530 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"12","session_start_time":"2024-12-28 04:46:39 UTC","virtual_transaction_id":"148/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"consistent recovery state reached at 0/50000F8","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:47:03.531377311Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:47:03.531 UTC","process_id":"41","session_id":"676f82af.29","session_line_num":"5","session_start_time":"2024-12-28 04:46:39 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"database system is ready to accept read-only connections","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:47:03.593014195Z","logger":"pg_ctl","msg":"........................ done","pipe":"stdout","logging_pod":"database-1-full-recovery"}
{"level":"info","ts":"2024-12-28T04:47:03.593026986Z","logger":"pg_ctl","msg":"server started","pipe":"stdout","logging_pod":"database-1-full-recovery"}
{"level":"info","ts":"2024-12-28T04:47:03.700099724Z","msg":"Checking if the server is still in recovery","logging_pod":"database-1-full-recovery","recovery":true}
{"level":"info","ts":"2024-12-28T04:47:08.708786164Z","msg":"Checking if the server is still in recovery","logging_pod":"database-1-full-recovery","recovery":true}
{"level":"info","ts":"2024-12-28T04:47:10.611426304Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:47:10.611 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"13","session_start_time":"2024-12-28 04:46:39 UTC","virtual_transaction_id":"148/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"restored log file \"000000020000000000000007\" from archive","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:47:10.637881705Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:47:10.637 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"14","session_start_time":"2024-12-28 04:46:39 UTC","virtual_transaction_id":"148/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"redo in progress, elapsed time: 14.52 s, current LSN: 0/60000D8","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:47:13.718653979Z","msg":"Checking if the server is still in recovery","logging_pod":"database-1-full-recovery","recovery":true}
{"level":"info","ts":"2024-12-28T04:47:18.728270884Z","msg":"Checking if the server is still in recovery","logging_pod":"database-1-full-recovery","recovery":true}
{"level":"info","ts":"2024-12-28T04:47:19.065490499Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:47:19.065 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"15","session_start_time":"2024-12-28 04:46:39 UTC","virtual_transaction_id":"148/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"restored log file \"000000020000000000000008\" from archive","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:47:19.091913102Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:47:19.091 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"16","session_start_time":"2024-12-28 04:46:39 UTC","virtual_transaction_id":"148/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"redo in progress, elapsed time: 22.97 s, current LSN: 0/8000028","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:47:23.739155145Z","msg":"Checking if the server is still in recovery","logging_pod":"database-1-full-recovery","recovery":true}
{"level":"info","ts":"2024-12-28T04:47:26.498299977Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:47:26.497 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"17","session_start_time":"2024-12-28 04:46:39 UTC","virtual_transaction_id":"148/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"restored log file \"000000020000000000000009\" from archive","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:47:28.747098889Z","msg":"Checking if the server is still in recovery","logging_pod":"database-1-full-recovery","recovery":true}
{"level":"info","ts":"2024-12-28T04:47:33.753324788Z","msg":"Checking if the server is still in recovery","logging_pod":"database-1-full-recovery","recovery":true}
{"level":"info","ts":"2024-12-28T04:47:36.289349061Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:47:36.289 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"18","session_start_time":"2024-12-28 04:46:39 UTC","virtual_transaction_id":"148/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"restored log file \"00000002000000000000000A\" from archive","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:47:38.763404546Z","msg":"Checking if the server is still in recovery","logging_pod":"database-1-full-recovery","recovery":true}
{"level":"info","ts":"2024-12-28T04:47:43.771918929Z","msg":"Checking if the server is still in recovery","logging_pod":"database-1-full-recovery","recovery":true}
{"level":"info","ts":"2024-12-28T04:47:48.782649196Z","msg":"Checking if the server is still in recovery","logging_pod":"database-1-full-recovery","recovery":true}
{"level":"info","ts":"2024-12-28T04:47:48.970128069Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:47:48.969 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"19","session_start_time":"2024-12-28 04:46:39 UTC","virtual_transaction_id":"148/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"restored log file \"00000002000000000000000B\" from archive","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:47:50.418919962Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:47:50.418 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"20","session_start_time":"2024-12-28 04:46:39 UTC","virtual_transaction_id":"148/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"redo in progress, elapsed time: 54.30 s, current LSN: 0/80000E0","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:47:51.779129988Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:47:51.778 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"21","session_start_time":"2024-12-28 04:46:39 UTC","virtual_transaction_id":"148/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"redo done at 0/B000158 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 55.66 s","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:47:51.779151272Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:47:51.778 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"22","session_start_time":"2024-12-28 04:46:39 UTC","virtual_transaction_id":"148/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"last completed transaction was at log time 2024-12-28 04:43:39.16191+00","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:47:53.789651995Z","msg":"Checking if the server is still in recovery","logging_pod":"database-1-full-recovery","recovery":true}
{"level":"info","ts":"2024-12-28T04:47:58.798901414Z","msg":"Checking if the server is still in recovery","logging_pod":"database-1-full-recovery","recovery":true}
{"level":"info","ts":"2024-12-28T04:48:00.062275494Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:00.061 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"23","session_start_time":"2024-12-28 04:46:39 UTC","virtual_transaction_id":"148/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"restored log file \"00000002000000000000000B\" from archive","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:01.576666036Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:01.576 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"24","session_start_time":"2024-12-28 04:46:39 UTC","virtual_transaction_id":"148/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"selected new timeline ID: 3","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:03.139663347Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:03.139 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"25","session_start_time":"2024-12-28 04:46:39 UTC","virtual_transaction_id":"148/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"restored log file \"00000002.history\" from archive","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:03.161958687Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:03.161 UTC","process_id":"45","session_id":"676f82af.2d","session_line_num":"26","session_start_time":"2024-12-28 04:46:39 UTC","virtual_transaction_id":"148/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive recovery complete","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:03.168546821Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:03.168 UTC","process_id":"43","session_id":"676f82af.2b","session_line_num":"1","session_start_time":"2024-12-28 04:46:39 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"checkpoint starting: end-of-recovery immediate wait","backend_type":"checkpointer","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:03.224015053Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:03.223 UTC","process_id":"43","session_id":"676f82af.2b","session_line_num":"2","session_start_time":"2024-12-28 04:46:39 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"checkpoint complete: wrote 8 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.015 s, sync=0.011 s, total=0.062 s; sync files=5, longest=0.007 s, average=0.003 s; distance=114688 kB, estimate=114688 kB; lsn=0/C000028, redo lsn=0/C000028","backend_type":"checkpointer","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:03.235186725Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:03.234 UTC","process_id":"41","session_id":"676f82af.29","session_line_num":"6","session_start_time":"2024-12-28 04:46:39 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"database system is ready to accept connections","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:03.236843465Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:03.236 UTC","process_id":"90","session_id":"676f8303.5a","session_line_num":"1","session_start_time":"2024-12-28 04:48:03 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:03.806549237Z","msg":"Checking if the server is still in recovery","logging_pod":"database-1-full-recovery","recovery":false}
{"level":"info","ts":"2024-12-28T04:48:03.808337479Z","logger":"pg_ctl","msg":"pg_ctl: server is running (PID: 41)\n/usr/lib/postgresql/17/bin/postgres \"-D\" \"/var/lib/postgresql/data/pgdata\" \"-c\" \"port=5432\" \"-c\" \"unix_socket_directories=/controller/run\" \"-c\" \"listen_addresses=<IP_ADDRESS>\"\n","pipe":"stdout","logging_pod":"database-1-full-recovery"}
{"level":"info","ts":"2024-12-28T04:48:03.808357254Z","msg":"Shutting down instance","logging_pod":"database-1-full-recovery","pgdata":"/var/lib/postgresql/data/pgdata","mode":"fast","timeout":null}
{"level":"info","ts":"2024-12-28T04:48:03.810190412Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:03.809 UTC","process_id":"41","session_id":"676f82af.29","session_line_num":"7","session_start_time":"2024-12-28 04:46:39 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"received fast shutdown request","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:03.81683781Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:03.816 UTC","process_id":"41","session_id":"676f82af.29","session_line_num":"8","session_start_time":"2024-12-28 04:46:39 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"aborting any active transactions","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:03.818999366Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:03.818 UTC","process_id":"41","session_id":"676f82af.29","session_line_num":"9","session_start_time":"2024-12-28 04:46:39 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"background worker \"logical replication launcher\" (PID 91) exited with exit code 1","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:03.819441396Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:03.819 UTC","process_id":"43","session_id":"676f82af.2b","session_line_num":"3","session_start_time":"2024-12-28 04:46:39 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"shutting down","backend_type":"checkpointer","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:03.840518207Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:03.840 UTC","process_id":"43","session_id":"676f82af.2b","session_line_num":"4","session_start_time":"2024-12-28 04:46:39 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"checkpoint starting: shutdown immediate","backend_type":"checkpointer","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:03.892511342Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:03.892 UTC","process_id":"43","session_id":"676f82af.2b","session_line_num":"5","session_start_time":"2024-12-28 04:46:39 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.059 s; sync files=0, longest=0.000 s, average=0.000 s; distance=16384 kB, estimate=104857 kB; lsn=0/D000028, redo lsn=0/D000028","backend_type":"checkpointer","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:03.89755682Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:03.897 UTC","process_id":"90","session_id":"676f8303.5a","session_line_num":"2","session_start_time":"2024-12-28 04:48:03 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:04.89970283Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:04.899 UTC","process_id":"90","session_id":"676f8303.5a","session_line_num":"3","session_start_time":"2024-12-28 04:48:03 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:04.899764465Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:04.899 UTC","process_id":"90","session_id":"676f8303.5a","session_line_num":"4","session_start_time":"2024-12-28 04:48:03 UTC","transaction_id":"0","error_severity":"WARNING","sql_state_code":"01000","message":"archiving write-ahead log file \"00000003.history\" failed too many times, will try again later","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:04.901606369Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:04.901 UTC","process_id":"90","session_id":"676f8303.5a","session_line_num":"5","session_start_time":"2024-12-28 04:48:03 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:05.904846492Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:05.904 UTC","process_id":"90","session_id":"676f8303.5a","session_line_num":"6","session_start_time":"2024-12-28 04:48:03 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:06.907140711Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:06.906 UTC","process_id":"90","session_id":"676f8303.5a","session_line_num":"7","session_start_time":"2024-12-28 04:48:03 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:06.907214651Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:06.906 UTC","process_id":"90","session_id":"676f8303.5a","session_line_num":"8","session_start_time":"2024-12-28 04:48:03 UTC","transaction_id":"0","error_severity":"WARNING","sql_state_code":"01000","message":"archiving write-ahead log file \"00000003.history\" failed too many times, will try again later","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:06.9129308Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:06.912 UTC","process_id":"41","session_id":"676f82af.29","session_line_num":"10","session_start_time":"2024-12-28 04:46:39 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"database system is shut down","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:06.920239884Z","logger":"pg_ctl","msg":"waiting for server to shut down....... done","pipe":"stdout","logging_pod":"database-1-full-recovery"}
{"level":"info","ts":"2024-12-28T04:48:06.920260919Z","logger":"pg_ctl","msg":"server stopped","pipe":"stdout","logging_pod":"database-1-full-recovery"}
{"level":"info","ts":"2024-12-28T04:48:06.920514712Z","msg":"Exited log pipe","fileName":"/controller/log/postgres.csv","logging_pod":"database-1-full-recovery"}
{"level":"info","ts":"2024-12-28T04:48:06.93663136Z","msg":"Updated replication settings","logging_pod":"database-1-full-recovery","filename":"override.conf"}
{"level":"info","ts":"2024-12-28T04:48:06.936815857Z","msg":"Starting up instance","logging_pod":"database-1-full-recovery","pgdata":"/var/lib/postgresql/data/pgdata","options":["start","-w","-D","/var/lib/postgresql/data/pgdata","-o","-c port=5432 -c unix_socket_directories=/controller/run","-t 40000000","-o","-c listen_addresses='<IP_ADDRESS>'"]}
{"level":"info","ts":"2024-12-28T04:48:06.986291679Z","logger":"pg_ctl","msg":"waiting for server to start....2024-12-28 04:48:06.986 UTC [104] LOG:  redirecting log output to logging collector process","pipe":"stdout","logging_pod":"database-1-full-recovery"}
{"level":"info","ts":"2024-12-28T04:48:06.986322415Z","logger":"pg_ctl","msg":"2024-12-28 04:48:06.986 UTC [104] HINT:  Future log output will appear in directory \"/controller/log\".","pipe":"stdout","logging_pod":"database-1-full-recovery"}
{"level":"info","ts":"2024-12-28T04:48:06.98665156Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:06.986 UTC","process_id":"104","session_id":"676f8306.68","session_line_num":"1","session_start_time":"2024-12-28 04:48:06 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"ending log output to stderr","hint":"Future log output will go to log destination \"csvlog\".","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:06.986701826Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:06.986 UTC","process_id":"104","session_id":"676f8306.68","session_line_num":"2","session_start_time":"2024-12-28 04:48:06 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"starting PostgreSQL 17.2 (Debian 17.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:06.986711418Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:06.986 UTC","process_id":"104","session_id":"676f8306.68","session_line_num":"3","session_start_time":"2024-12-28 04:48:06 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"listening on IPv4 address \"<IP_ADDRESS>\", port 5432","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:06.99977053Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:06.999 UTC","process_id":"104","session_id":"676f8306.68","session_line_num":"4","session_start_time":"2024-12-28 04:48:06 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"listening on Unix socket \"/controller/run/.s.PGSQL.5432\"","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:07.016521333Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:07.016 UTC","process_id":"108","session_id":"676f8307.6c","session_line_num":"1","session_start_time":"2024-12-28 04:48:07 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"database system was shut down at 2024-12-28 04:48:03 UTC","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:07.029418173Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:07.029 UTC","process_id":"104","session_id":"676f8306.68","session_line_num":"5","session_start_time":"2024-12-28 04:48:06 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"database system is ready to accept connections","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:07.03090258Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:07.030 UTC","process_id":"111","session_id":"676f8307.6f","session_line_num":"1","session_start_time":"2024-12-28 04:48:07 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:07.053610542Z","logger":"pg_ctl","msg":" done","pipe":"stdout","logging_pod":"database-1-full-recovery"}
{"level":"info","ts":"2024-12-28T04:48:07.053643993Z","logger":"pg_ctl","msg":"server started","pipe":"stdout","logging_pod":"database-1-full-recovery"}
{"level":"info","ts":"2024-12-28T04:48:07.154816035Z","msg":"Configuring new PostgreSQL instance","logging_pod":"database-1-full-recovery"}
{"level":"info","ts":"2024-12-28T04:48:07.165998845Z","msg":"Executing post-init SQL instructions","logging_pod":"database-1-full-recovery"}
{"level":"info","ts":"2024-12-28T04:48:07.166111302Z","msg":"Executing post-init template SQL instructions","logging_pod":"database-1-full-recovery"}
{"level":"info","ts":"2024-12-28T04:48:07.172864394Z","logger":"pg_ctl","msg":"pg_ctl: server is running (PID: 104)\n/usr/lib/postgresql/17/bin/postgres \"-D\" \"/var/lib/postgresql/data/pgdata\" \"-c\" \"port=5432\" \"-c\" \"unix_socket_directories=/controller/run\" \"-c\" \"listen_addresses=<IP_ADDRESS>\"\n","pipe":"stdout","logging_pod":"database-1-full-recovery"}
{"level":"info","ts":"2024-12-28T04:48:07.172886995Z","msg":"Shutting down instance","logging_pod":"database-1-full-recovery","pgdata":"/var/lib/postgresql/data/pgdata","mode":"fast","timeout":null}
{"level":"info","ts":"2024-12-28T04:48:07.174400322Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:07.174 UTC","process_id":"104","session_id":"676f8306.68","session_line_num":"6","session_start_time":"2024-12-28 04:48:06 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"received fast shutdown request","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:07.190361653Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:07.190 UTC","process_id":"104","session_id":"676f8306.68","session_line_num":"7","session_start_time":"2024-12-28 04:48:06 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"aborting any active transactions","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:07.193572267Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:07.193 UTC","process_id":"104","session_id":"676f8306.68","session_line_num":"8","session_start_time":"2024-12-28 04:48:06 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"background worker \"logical replication launcher\" (PID 112) exited with exit code 1","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:07.194027502Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:07.193 UTC","process_id":"106","session_id":"676f8307.6a","session_line_num":"1","session_start_time":"2024-12-28 04:48:07 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"shutting down","backend_type":"checkpointer","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:07.216912469Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:07.216 UTC","process_id":"106","session_id":"676f8307.6a","session_line_num":"2","session_start_time":"2024-12-28 04:48:07 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"checkpoint starting: shutdown immediate","backend_type":"checkpointer","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:07.292042625Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:07.291 UTC","process_id":"106","session_id":"676f8307.6a","session_line_num":"3","session_start_time":"2024-12-28 04:48:07 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"checkpoint complete: wrote 4 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.015 s, sync=0.011 s, total=0.082 s; sync files=3, longest=0.007 s, average=0.004 s; distance=16384 kB, estimate=16384 kB; lsn=0/E000028, redo lsn=0/E000028","backend_type":"checkpointer","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:07.296817147Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:07.296 UTC","process_id":"111","session_id":"676f8307.6f","session_line_num":"2","session_start_time":"2024-12-28 04:48:07 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:08.300166891Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:08.299 UTC","process_id":"111","session_id":"676f8307.6f","session_line_num":"3","session_start_time":"2024-12-28 04:48:07 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:08.300251402Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:08.299 UTC","process_id":"111","session_id":"676f8307.6f","session_line_num":"4","session_start_time":"2024-12-28 04:48:07 UTC","transaction_id":"0","error_severity":"WARNING","sql_state_code":"01000","message":"archiving write-ahead log file \"00000003.history\" failed too many times, will try again later","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:08.302204781Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:08.301 UTC","process_id":"111","session_id":"676f8307.6f","session_line_num":"5","session_start_time":"2024-12-28 04:48:07 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:09.304737581Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:09.304 UTC","process_id":"111","session_id":"676f8307.6f","session_line_num":"6","session_start_time":"2024-12-28 04:48:07 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:10.307625617Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:10.307 UTC","process_id":"111","session_id":"676f8307.6f","session_line_num":"7","session_start_time":"2024-12-28 04:48:07 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:10.30770908Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:10.307 UTC","process_id":"111","session_id":"676f8307.6f","session_line_num":"8","session_start_time":"2024-12-28 04:48:07 UTC","transaction_id":"0","error_severity":"WARNING","sql_state_code":"01000","message":"archiving write-ahead log file \"00000003.history\" failed too many times, will try again later","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:10.313873613Z","logger":"postgres","msg":"record","logging_pod":"database-1-full-recovery","record":{"log_time":"2024-12-28 04:48:10.313 UTC","process_id":"104","session_id":"676f8306.68","session_line_num":"9","session_start_time":"2024-12-28 04:48:06 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"database system is shut down","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-12-28T04:48:10.385902589Z","logger":"pg_ctl","msg":"waiting for server to shut down....... done","pipe":"stdout","logging_pod":"database-1-full-recovery"}
{"level":"info","ts":"2024-12-28T04:48:10.386005917Z","logger":"pg_ctl","msg":"server stopped","pipe":"stdout","logging_pod":"database-1-full-recovery"}
{"level":"info","ts":"2024-12-28T04:48:10.386371354Z","msg":"Exited log pipe","fileName":"/controller/log/postgres.csv","logging_pod":"database-1-full-recovery"}

Code of Conduct

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

This is not a bug. It is explained here: https://cloudnative-pg.io/documentation/current/recovery/#restoring-into-a-cluster-with-a-backup-section
You are using the same bucket for both recovery and future backup, which might lead to problems (hence why we added that annotation).


Consequent enum of assignment detail

Also fix all sorting lists

requires rework of ListOfSpeakers to include PointOfOrder and pro contra


WIP: Add API to serialize imagestream

WIP for https://github.com/openshift/hypershift/issues/1767

Closing in favor of https://github.com/openshift/hypershift/pull/1773


Added Ryan Hall to AUTHORS. Refs #24554

In reference to original PR #4419

merged in 8f987323791181783d3f1ba847ffc0a938ddccdf, thanks!


error while running the script

ERROR:torch.distributed.elastic.multiprocessing.api:failed (exitcode: 2) local_rank: 0 (pid: 1199) of binary: /usr/bin/python3
Traceback (most recent call last):
File "/usr/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/usr/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/usr/local/lib/python3.7/dist-packages/torch/distributed/launch.py", line 193, in
main()
File "/usr/local/lib/python3.7/dist-packages/torch/distributed/launch.py", line 189, in main
launch(args)
File "/usr/local/lib/python3.7/dist-packages/torch/distributed/launch.py", line 174, in launch
run(args)
File "/usr/local/lib/python3.7/dist-packages/torch/distributed/run.py", line 755, in run
)(*cmd_args)
File "/usr/local/lib/python3.7/dist-packages/torch/distributed/launcher/api.py", line 131, in call
return launch_agent(self._config, self._entrypoint, list(args))
File "/usr/local/lib/python3.7/dist-packages/torch/distributed/launcher/api.py", line 247, in launch_agent
failures=result.failures,
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:

I am facing the above issue while running run_summarization script

Did you ever resolve this?


Schema compare Sql Proj as target shows differences for SqlView and StoredProcedures after apply

Azure Data Studio Version: ADS 1.38.0-rc1
OS Version: Win10

Steps to Reproduce:

Open SQl DB Proj extension and open SC on fresh SQL DB proj
Select DB as source (have some table/view/sp objects)
Select SQL DB Project as target
Compare and apply changes
Compare again after the changes applied to the sql proj
Should expect no differences, but is showing view/Sp in the diff window

Does this issue occur when all extensions are disabled?: Yes/No

The scripts for views, stored procedures, and schemas weren't getting recognized as part of the model because the GO was appended on the same line at the end of the script, not on a new line, like this;
CREATE VIEW [dbo].[View1]
  AS SELECT * FROM [dbo].[Table1]GO

This was caused by a recent change in DacFx that changed where the logic of where GO gets added to the script. This wasn't caught by the tests because there were only tests for tables and their child objects, which all have newline characters at the end of their scripts. The generate scripts for views and stored procedures don't have these new line characters at the end, which is why the GO was getting appended on the same line as the end of the script for these objects.

Left images are the first schema compare result and the right images are the result after applying the changes and doing a second schema compare
expected - no changes:

actual - there are objects not missing from the target project's model and a build failure:


ARROW-15672: [C++] Enable CSV writer to control the field delimiter

This PR modifies the WriteOptions for CSV to allow changing the default delimiter.

Thanks for doing this. We should also add unit tests (see https://github.com/apache/arrow/blob/master/cpp/src/arrow/csv/writer_test.cc and https://github.com/apache/arrow/blob/master/python/pyarrow/tests/test_csv.py) and you'll want to reformat the code here (see https://arrow.apache.org/docs/developers/cpp/development.html#code-style-linting-and-ci)

Adding the tests now,

Appveyor test failure looks related to this PR, needs be fixed.
https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow/builds/42659260/job/qk6x3kld8ffabyuu#L2758

Appveyor test failure looks related to this PR, needs be fixed. https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow/builds/42659260/job/qk6x3kld8ffabyuu#L2758

I checked the test logs. It shows an older piece of code which is failing now.
https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow/builds/42659260/job/qk6x3kld8ffabyuu#L2745
Here, the error log shows this
assert t == read_csv(buf, read_options=read_options)
while the updated code has this
       assert t == read_csv(buf, read_options=read_options,
                            parse_options=parse_options)

Odd. I kicked the build, let's see if it persists. If it still fails maybe we can rebase and try again.

Odd. I kicked the build, let's see if it persists. If it still fails maybe we can rebase and try again.

@lidavidm Rebased the branch.

The header is still using commas instead of the delimiter (see line 524 of writer.cc).  This is causing the write_csv.py test to fail.  A more interesting question is why the Linux CI jobs are passing but I'm pretty sure that is unrelated to your PR.

The header is still using commas instead of the delimiter (see line 524 of writer.cc). This is causing the write_csv.py test to fail. A more interesting question is why the Linux CI jobs are passing but I'm pretty sure that is unrelated to your PR.

Yes, sorry I missed that, and previously the parse_options was missing too. Corrected that. Thanks for help!

"R / rhub/debian-gcc-devel:latest" job failure is not related.


Use new MPI custom ops in mpi reduce

Follow-up to #2054

@vchuravy got it working!
Despite one single very strange error involving vectorization... see CI.


Wrong timezone offset for Asia/Almaty

Please provide a brief summary of the bug
Kazakhstan Almaty timezone was changed on 2024-03-01 to +05:00.
For more info see https://www.timeanddate.com/time/zone/kazakstan/almaty
See also OpenJDK bug report JDK-8325150
Did you test with the latest update version?
yes

Please provide steps to reproduce where possible
java.util.TimeZone.getTimeZone("Asia/Almaty").getRawOffset()/(10006060)
Expected Results
jshell> java.util.TimeZone.getTimeZone("Asia/Almaty").getRawOffset()/(10006060)
$1 ==> 5
Actual Results
jshell> java.util.TimeZone.getTimeZone("Asia/Almaty").getRawOffset()/(10006060)
$1 ==> 6
What Java Version are you using?
openjdk 17.0.10 2024-01-16 OpenJDK Runtime Environment Temurin-17.0.10+7 (build 17.0.10+7) OpenJDK 64-Bit Server VM Temurin-17.0.10+7 (build 17.0.10+7, mixed mode)
What is your operating system and platform?
macOS on M1
How did you install Java?
sdkman
Did it work before?
no

Did you test with other Java versions?
No response
Relevant log output
No response

This will be fixed with the 17.0.11 release in April.


No compilation error when concatenating function with string.

If you accidentally concatenate a ()=>string with a string, typescript does not give an error or warning, but I believe it should.
This is easily reproducible in the "Try Typescript" hello world greeter example.
originally I had some code that was akin to this:
meet() : string
{
	return this.greeting + ", sincerely George"
}

where I was concatenating a string property to another string.
Then, during a refactoring, I encapsulated the "greeting" part into a member function, greet().  I had intended to do something like this
meet() : string
{
	return this.greet() + ", sincerely George"
}

which would print "Hello World, sincerely George" when you click the button.
But I accidentally forgot the parentheses on greet:
meet() : string
{
	return this.greet + ", sincerely George"
}

which causes the alert button to print out the source code of the greet function, followed by "Sincerely George"
function () {
return "Hello, " + this.greeting;
}, sincerely George
One would think that TypeScript would warn you that you are concatenating a function's source code with  a string to make another string.
It does warn you if you simply try to return the function as a string
meet() : string
{
	return this.greet
}

saying "Type '() => string' is not assignable to type 'string'."
But it seems that as soon as you try to concatenate a ()=>string with another string it merrily goes on its way converting functions to strings, which seems rather dangerous to me.
Is there a good reason why implicitly casting a function to a string containing its source code should be allowed?

One would think that TypeScript would warn you that you are concatenating a function's source code with a string to make another string.

One would think so, but unfortunately it would warn users in the face of completely valid JavaScript.
function foo() {
    return 10;
}

// Prints out the text of the function.
// This is probably not what you wanted.
console.log("" + foo);

foo.toString = function() {
    return "Anything can happen in this language!";
}
// Prints 'Anything can happen in this language!'.
// Potentially desirable since 'toString' was overridden.
console.log("" + foo);

Using "" + is just a common idiom for invoking toString and I don't think we'd be able to appropriately dictate which uses are valid.

I would think concatenation of non-primitive types should be allowed only if they have a declared toString(): string member (as opposed to the implicit member inherited from Object). There should almost always be one in objects that someone would actually want to stringify implicitly.

I agree with Jeffrey here.  Certain, Daniel, you don't want to prevent people from legitimate use of the toString conversion.
But if toString is not overridden, it's hard to imagine a case where somewant would want to purposely implicitly concatenate their function source code with another string.  If they really want to do that, the TypeScript compiler should force an explicit call to toString, as it does
Likewise, if I really wanted the meet() function to return the source code of the greet() function, I could write
meet() : string
{
    return this.greet.toString()
}

and this tells TypeScript that "yes, I really do want to turn my function into a string".  But as I mentioned before, without the toString, TypeScript helpfully tells you that you have a type mismatch.  Which after all is the whole point of TypeScript.
It does not make sense to me that there is a double standard where you support dangerous implicit casts when concatenating strings, but not upon returning values.

There's a huge amount of code out there that does stuff like this:
console.log("Foo is " + x);

where x might be a function, undefined or null, in which case explicitly calling toString would be a bad idea. We made the decision that adding anything to a string is so often done that it is not ever an error.
If we absolutely had to add an error case to +, this would indeed probably be the first choice. but it doesn't meet the bar for introducing a breaking change in the language.

@RyanCavanaugh if this can be under a compiler flag, that would work for everyone. My colleague did run in the same scenario as described above, so it is a valid case. I get your point, this is how js is working,  so with a flag people who are interested in extra security could turn it on. Cases like
console.log("Foo is " + x);

can be refactored to
console.log("Foo is ", x);
//or
console.log("Foo is " + String(x));
//or
console.log("Foo is " + (x as string));

TSLint will soon (already?) have type-based rules so you can flag things like this at your discretion.
(x as string) is not a good workaround; this assertion essentially never succeeds in a useful way.


Multiple fields with the same parameter in a POST.

I am interacting with an API that allows for multiple fields of the same name to be included in a post request. The app is still under development and not available publicly.
HttpResponse<JsonNode> jsonResponse = Unirest.post(url)
                    .header("Authorization", "Token " + apikey)
                    .field("parameter", "value1")
                    .field("parameter", "value2")
                    .asJson();

The problem I am having is that when I have two fields with the same name, unirest only takes the second one and neglects the first one.

Sorry to reopen this old bug but I've stumbled upon it right now trying to use this library to access the Mailgun API service.
I disagree on this:

I am not sure it is REST compliant to have multiple fields with the same name but holding different values, basically you need to rethink the API design

REST is strongly based on HTTP and multiple fields with the same value is a common scenario with HTTP. Be it query strings or form data (body of a POST). The latter is the scenario of the OP.
As an example of an API that requires this usage is the same Mailgun service. To send a mail with multiple attachments you need this funcionality as you can't send them as query parameters.
I've tested this with the Jersey 2 client library and it works fine.


Formalize the invariants on allowed elimination sorts of inductives i…

…n PCUIC
Actually, I went and did much more, now a well-formed inductive declaration has:

A well-typed arity as a declared type
The corresponding sort is compared to the sorts of the arguments of constructors to check which eliminations should be allowed (in case of Prop-squashing), and to ensure that constructor types are smaller than the inductive type (in the predicative case).
For primitive projections, if there is any then the inductive must have a single constructor and all eliminations allowed.

This should be enough to let @yforster prove the necessary lemmas about extraction.
Still missing the universe check that the constructor's arguments types are <= the declared type (for consistency).

Ready when you are :)


Amazon-AWS-EC2-Security Issue

Added withExecutionLogs input.
Signed-off-by: Mihail-Cristian Tusa<EMAIL_ADDRESS>

@gituser173  Please review it!


Query applied indicator doesn't appear when entering to a dataset page and having a query applied

Steps to Reproduce
Please break down here below all the needed steps to reproduce the issue

Apply any valid/error'ed query to a dataset within the dataset view
Go back to dashboard
Enter the dataset view again

Current Result
Although a query is applied, the indicator doesn't show up so the data in the table can be missleading if the user doesn't remember that she applied a query.
Expected result
Query applied indicator should be shown.

This is not happening anymore 💃


MINIFICPP-2250 Do not strip core files in CI

Core files were getting stripped in some cases making them unusable:
https://github.com/lordgamez/nifi-minifi-cpp/actions/runs/6340288536
https://github.com/lordgamez/nifi-minifi-cpp/actions/runs/6340287277
https://github.com/lordgamez/nifi-minifi-cpp/actions/runs/6340278881
https://issues.apache.org/jira/browse/MINIFICPP-2250

Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically main)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file?
[ ] If applicable, have you updated the NOTICE file?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible.

How large are they? Do we have enough free disk space left on the runners?

The stripped core files I downloaded from the CI job were only 1.2MB, and when I tried to reproduce the issue locally I could make the test crash, but it only produced a 77MB core dump. I'm not sure why it was stripped as it should not exceed the current limit, but we recently added the step of removing the unneeded resources of the workers which frees up a few gigs that should be enough even if the crash dump is larger.


Speed is too fast, no way to configure it to be lower than +7 Speed

Mod you are referring to:
Sprint Sprint Sprint
Singleplayer or Multiplayer:
Both
Reproducible:
Fresh install of the mod and load for the first time.
Description:
Default speed in config.conf is 5, which, in-game is +12 speed! this is wayy to fast!!! If I lower the setting in the config to 0, it's still +7, which is faster than the advertised +5 speed! Is this a bug? I can set it to -1 and -2 etc, but it really glitches out and I go super fast lol.
Provide SMAPI Log:

Tried in both 1.0.3 and 1.0.4 where i left the speed default, and it's always +12 speed.... Sprint is the only mod installed, so there's no way its a conflict.

I will look into an option to disable that

just to let you know im now looking to add an option to disable the +7 speed when u have the Sprint key on leftshift. The reason being is that left shift is also the run key in vanilla game and since auto run is enabled by default, it slows the player down

I have fixed the issue, however I am planning to add more before a stable release build is released on Nexus. I have uploaded a prerelease build that has been tested on github instead so you don't have to wait any longer. Download SprintSprintSprint-1.0-beta.20190816 and run the game once to reset the config. In the config, set LeftShiftKeyExtraSpeed to something lower if you find the added speed too much.
https://github.com/JessebotX/StardewMods/releases/tag/Sprint
Release Notes - will be updated shortly

(i believe you can still leave comments here)


boot2docker appears to not have completed

I ran nanobox dev and it started setting things up. I noticed the boot2docker install seems to have stopped at 95%.
+> Installing nanobox/boot2docker...
   [**************************************    95%] 11.9M/s (0:00:01 remaining)   -
+> Creating a nanobox

Based on how much further the process went I'm guessing the progress bar was simply not updated at 100%

@sdomino Is this still happening?

As far as I know this is still an issue.


MGDOBR-1342: migrate to a dedicated istio api gateway (#1446) - Update kustomization images

This Pull request aims to update the kustomization images for the PR MGDOBR-1342: migrate to a dedicated istio api gateway (#1446)

/deploy dev

/deploy stable


AWS X-Ray Java Spring SDK | downstream API calls | Subsegments are nested inside each other

I'm trying to instrument a microservices java spring application with aws x-ray using aws-xray-recorder-sdk-spring 2.8.0 and I'm facing a problem when creating subsegments for the downstream http calls to microservices. We are using webflux's WebClient  for the downstream API calls and ExchangeFilterFunction implementation for the subsegment generation. Here is the gist of it:
public class XrayExchangeFilter implements ExchangeFilterFunction {
    @Override
    public Mono<ClientResponse> filter(ClientRequest request, ExchangeFunction next) {
        ...
        Subsegment subsegment = AWSXRay.getGlobalRecorder().beginSubsegment(segmentName);

        return next.exchange(request).doAfterSuccessOrError((response, ex) -> {
            if (ex != null) {
                subsegment.setFault(true);
                subsegment.addException(ex);
            } else {
                ...
            }

            AWSXRay.getGlobalRecorder().endSubsegment(subsegment);
        });
    }

A microservice makes several subsequent blocking downstream requests to other microservices and each subsegment gets added as a child of the previously generated subsegment instead of all the subsegments be added in a flat array under the main request that makes the sequential downstream calls. Is there a way to make it so that that nesting doesn't happen? Maybe I'm doing something wrong? I'm wondering if it is a bug or expected behavior as it seems counter-intuitive to me.
Here is what I'm getting in AWS X-Ray as segment document for the upstream call segment (instrumented using AWSXRayServletFilter) and mutated using the above filter:
       {
            "Id": "28f8dc008cd2db06",
            "Document": {
                "id": "28f8dc008cd2db06",
                "name": "gateway",
                "start_time":<PHONE_NUMBER>.211,
                "trace_id": "1-605ca473-7793c2a305c8425b7e5f9207",
                "end_time":<PHONE_NUMBER>.434,
                "http": {
                    "request": {
                        "url": "https://gateway/path",
                        "method": "POST",
                        "client_ip": "IP_ADDRESS",
                        "x_forwarded_for": true
                    },
                    "response": {
                        "status": 200,
                        "content_length": 1282
                    }
                },
                "aws": {
                    "xray": {
                        "rule_name": "backend-application",
                        "sdk_version": "2.8.0",
                        "sdk": "X-Ray for Java"
                    }
                },
                "service": {
                    "runtime": "OpenJDK 64-Bit Server VM",
                    "runtime_version": "11.0.6"
                },
                "subsegments": [
                    {
                        "id": "5367a2006ae6f9d0",
                        "name": "/downstream-call-1-path",
                        "start_time":<PHONE_NUMBER>.212,
                        "end_time":<PHONE_NUMBER>.293,
                        "http": {
                            "request": {
                                "url": "https://service-1/downstream-call-1-path",
                                "method": "GET"
                            },
                            "response": {
                                "status": 200
                            }
                        },
                        "namespace": "remote",
                        "subsegments": [
                            {
                                "id": "432fc2120ffb5669",
                                "name": "/downstream-call-2-path",
                                "start_time":<PHONE_NUMBER>.296,
                                "end_time":<PHONE_NUMBER>.318,
                                "http": {
                                    "request": {
                                        "url": "https://service-2/downstream-call-2-path",
                                        "method": "GET"
                                    },
                                    "response": {
                                        "status": 200
                                    }
                                },
                                "namespace": "remote",
                                "subsegments": [
                                    {
                                        "id": "41796b1bb6acdcf9",
                                        "name": "/downstream-call-3-path",
                                        "start_time":<PHONE_NUMBER>.319,
                                        "end_time":<PHONE_NUMBER>.33,
                                        "http": {
                                            "request": {
                                                "url": "https://service-1/downstream-call-3-path",
                                                "method": "POST"
                                            },
                                            "response": {
                                                "status": 200
                                            }
                                        },
                                        "namespace": "remote",
                                        "subsegments": [
                                            {
                                                "id": "300819e445ed2aed",
                                                "name": "/downstream-call-4-path",
                                                "start_time":<PHONE_NUMBER>.331,
                                                "end_time":<PHONE_NUMBER>.36,
                                                "http": {
                                                    "request": {
                                                        "url": "https://service-1/downstream-call-4-path",
                                                        "method": "POST"
                                                    },
                                                    "response": {
                                                        "status": 200
                                                    }
                                                },
                                                "namespace": "remote",
                                                "subsegments": [
                                                    {
                                                        "id": "29b6936aa9afe87d",
                                                        "name": "/downstream-call-5-path",
                                                        "start_time":<PHONE_NUMBER>.361,
                                                        "end_time":<PHONE_NUMBER>.395,
                                                        "http": {
                                                            "request": {
                                                                "url": "https://service-2/downstream-call-5-path",
                                                                "method": "POST"
                                                            },
                                                            "response": {
                                                                "status": 200
                                                            }
                                                        },
                                                        "namespace": "remote",
                                                        "subsegments": [
                                                            {
                                                                "id": "4ac504fd1e506663",
                                                                "name": "/downstream-call-6-path",
                                                                "start_time":<PHONE_NUMBER>.395,
                                                                "end_time":<PHONE_NUMBER>.433,
                                                                "http": {
                                                                    "request": {
                                                                        "url": "https://service-3/downstream-call-6-path",
                                                                        "method": "POST"
                                                                    },
                                                                    "response": {
                                                                        "status": 200
                                                                    }
                                                                },
                                                                "namespace": "remote"
                                                            }
                                                        ]
                                                    }
                                                ]
                                            }
                                        ]
                                    }
                                ]
                            }
                        ]
                    }
                ]
            }
        }

Hi @mentormate-georgikostadinov - we unfortunately don't officially support spring webflux. It looks like the main issue is that beginSubsegment actually makes that subsegment "active" - endSubsegment actually does not undo that so you would need to use something like clearEntity. However that means that the subsegments probably won't be connected to any parent. Propagating a segment in reactive frameworks isn't easy due to the crossing of asynchronous boundaries - in opentelemetry, our focus going forward for x-ray users, we have this somewhat complicated instrumentation
https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/instrumentation/spring/spring-webflux-5.0/library/src/main/java/io/opentelemetry/instrumentation/spring/webflux/client/WebClientTracingFilter.java#L68
Are you able to give opentelemetry a try by any chance? It supports many more, newer frameworks, such as webflux.


Fix PHPDocs for JSON resources

The resolve() method which is the client of the toArray() method expects array|Arrayable|JsonSerializable return type, not strictly array.
With the current PHPDoc problems arise when we extend the resource class, return something that is Arrayable|JsonSerializable and add a proper PHPDoc to the child class. Static analysis tools report a problem: we have weakened the postconditions of the overridden method.

Please fully qualify these.

Please fully qualify these.

Please see the updated code.


How to add "include" section of tsconfig to tsProject?

How to add "include" section of tsconfig to tsProject?

That is not yet supported by TypeScript, so it's not possible to use that at the moment.

TypeScript supports it. Because I use it already by tsc.

I did a quick test, and I'm pretty sure it isn't implemented yet. Do you have any reference that says that it was implemented? You can use files or exclude in a tsconfig file. If you really need a glob, you can use gulp.src('...') instead.

hmm, may be I'm wrong. I'm using
{
"compilerOptions": {
"module": "commonjs",
"target": "es5",
"inlineSourceMap": true
},
"include": [
"typings/tsd.d.ts"
],
"exclude": [
"node_modules"
]
}
Okay, how to give typescript info about "typings/tsd.d.ts"?
2016-04-07 19:40 GMT+03:00 Ivo Gabe de Wolff<EMAIL_ADDRESS>
I did a quick test, and I'm pretty sure it isn't implemented yet. Do you
have any reference that says that it was implemented? You can use files
or exclude in a tsconfig file. If you really need a glob, you can use
gulp.src('...') instead.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/ivogabe/gulp-typescript/issues/320#issuecomment-206986010

All TypeScript files that are in the (subdirectories of) the root directory (directory containing the tsconfig file) are passed to TypeScript, unless they were referenced in the exclude section. Thus, typings/tsd.d.ts will be passed to TypeScript.

var tsProject = ts.createProject(Object.assign({
    declaration: true,
    noExternalResolve: true
}, tsconfig.compilerOptions));

var tsStream = gulp.src(['src/*.ts', 'typings/tsd.d.ts'])
    .pipe(ts(tsProject));

return merge([
    tsStream.dts.pipe(gulp.dest('dist')),
    tsStream.js.pipe(gulp.dest('dist'))
])

This is my task and it gives me an error

For file resolution based on a tsconfig file, you must use tsProject = ts.createProject('tsconfig.json'); and tsProject.src() instead of gulp.src(...). Your config would also work if you removed noExternalResolve: true.

But tsc copy the whole file/directory structure. I've removed noExternalResolve: true. But has the same problem.

Can you try this:
var tsProject = ts.createProject('tsconfig.json', { declaration: true });

var tsStream = tsProject.src()
    .pipe(ts(tsProject));

return merge([
    tsStream.dts.pipe(gulp.dest('dist')),
    tsStream.js.pipe(gulp.dest('dist'))
])

Has this been solved?

Typescript already does support include but only @2.0. See release notes.
gulp-typescript still uses v.1.8 which is perfectly reasonable. The problem is that even if you customize the typescript version as below:
ts.createProject('tsconfig.json', {typescript: require('typescript')});
the new options are not passed to the compiler. By "new" I mean those which gain support in 2.0, specifically, include. Since, I'm using a project file, I would expect gulp-typescript to pass all of it to tsc, even if some parameters are not recognized or at least tell me that it is skips some of them. It sort of silences out the problem.
Obviously, executing $(npm bin)/tsc -p tsconfig.json directly gives expected results.
Is there some work being done regarding transition to ts 2.0? Is it easy to add new parameters?

I've wired up a quick implementation: see my fork.
Required changes are mostly in the project.ts file in how it handles the tsconfig.json. I didn't install TS 2.0 as a submodule and did not write tests though.
Let me know if this is useful.

As a side note: because of the way how project config options are handled in gulp-typescript, the include option can be supported without TypeScript 2.0 compiler. Files are searched for before they are passed to the compiler.

@pbalaga tsProject.src() does not use the TypeScript api indeed. It's no problem for me that it includes will be supported on TS1.8 too.
Your changes in your fork look good; can you create a pull request? A few comments: let files = [] should get a type annotation (since it is now typed as any[]); you wrote something like if (!includes) {} if (includes), you should replace that with an if-else; and you changed some formatting, can you revert those changes?

Fixed by @pbalaga in #402 🎉


Inconsistency in the ordering of buttons (should be positive action on right)

Re examples of groups of buttons shown throughout the Carbon website
Detailed description
In scenarios where there are two buttons presented to the user, one for the positive action (for example, Save, Print, Publish, etc.) and one to cancel without taking any action, I believe that IBM products follow the widely adopted convention of having the positive action on the right and the Cancel button on the left.
This is indeed the case with the vast majority of the examples given throughout the Carbon Design System website.
Some correct examples:
Correct example from the Modal component page:

Correct example from the Form component page:

Correct example from the Button component page:

All well and good 👍
Some incorrect examples:
However, I've spotted a few anomalies - specifically on the Button component page and the Form component page.
From the Button component page:

From the Form component page:

Note: both of these pages contain a few incorrect example images, not just the two I've shown here.
So I think these example images should be updated so that the Carbon Design Systems shows a consistent approach to scenarios with the user sees a primary action and a cancel button pairing.
It might also be worth explicitly adding some guidance about the ordering of such buttons.
For example, in the Carbon for IBM Products > Content guide, we have the following guidance for our designers:

Where there is more than one button (for example, a modal with both a Cancel and a Submit button), positive actions should be displayed on the right, negative actions on the left.

(Source: https://pages.github.ibm.com/cdai-design/pal/content/button-labels#grammar-and-structure)

Related issue: https://github.com/carbon-design-system/carbon-design-kit/issues/407

Hey team! Please add your planning poker estimate with ZenHub @laurenmrice @thyhmdo

Here's a Slack thread that seems to be pointing to the same inconsistency:
https://cognitive-app.slack.com/archives/C0M053VPT/p1652377862689979?thread_ts=1651849722.675849&cid=C0M053VPT
My team is interested in the outcome of this as well. For now, we are assuming Button page guidance, section Horizontally arranged groups, is the latest:

To sum up, a primary button will be left-aligned and positioned to the left of the secondary/tertiary button on full-page designs. The primary button will be right-aligned and appear to the right of the secondary/tertiary button within wizards and dialog windows.

At one point, the inconsistency was a conscious decision. It has been brought up several times with agreements for both directions. This should be reviewed again, perhaps in conjunction with the DSAG @jeanservaas @sstrubberg

@tomwaterton this was a conscious decision and the guidance is clear that the buttons do not always hold the same position depending on the context. Many design systems also follow this logic.

As a general rule, on full-page designs, the primary button is on the left side of the page. When the browser window is large and the user is scrolling to read, it’s best to have the primary button where the user’s attention has been focused all along. Whereas in wizards, where a user is progressing through a series of steps or dialog windows, the primary action traditionally sits at the bottom right. Buttons within components such as notifications, search fields, and data tables are also right-aligned.

I think the main problem here, is that the guidance changed (even though, I believe it was a while ago), and that the button guidance on Carbon is quite long.
Button is a component that people don't think to look back to unless they have a specific question I suspect. So that new approach probably isn't widely understood. I get the reasoning behind it, but only did after quite a lot of reading and thinking about it. And because it's quite far down a long page, someone might not get into it. That's one of the reasons I wanted to split more detailed guidance into different pieces on the PAL site, as we had the ability to build sub-pages, which I think the Carbon team aren't able to do (?).
I was planning to write two piece of guidance about button placement, and one about button groups with some more use cases / examples of when the primary would be on the left vs the right, but the group dispersed and wasn't able to put the work into it required.
Button groups got pretty close. Placement not so much. But maybe they could be combined and I could attempt to get it past the finish line if prioritised, and areas that need more clarification were identified.
Button groups:
https://ibm.box.com/s/w99iozey0m7aixee67rcxi361rg9v9jl

Thanks for the additional comments / information, everyone.
Although, @jeanservaas it seems like your latest comment is referring to the subject of whether a button / buttons are aligned to the left side of their containing element (such as in full-page scenarios) or to the right side of their containing element (such as in a wizard scenario). Just for clarity: My comments here weren't actually about the alignment of buttons relative to their containers. My question was rather about the order of primary/secondary buttons.
I thought (wrongly, it appears) that where there are two (or more) buttons, that the primary button always appeared on the right of any secondary/tertiary buttons (e.g. Cancel Save).
However, the piece of guidance that @shixiedesign has quoted in her comment teaches me that this is now not always the case.

I have to confess, I had not seen this before. (I don't  know whether this change has come in since I originally raised this issue?)
If this is the new guidance, then I think we just need to consider what we can do to help make it as prominent as we can so that more people spot this.

REF https://github.com/carbon-design-system/gatsby-theme-carbon/issues/1363


Using "exports" without defining it.

Not sure if the "exports" variable is a global within nodejs. I just installed this with Bower and I'm using it in the browser and it's not working. I mean "node" is in the title. But it would still be cool to use this library in the browser.

@reggi that is the CommonJS way of exporting a module (well syntactically that's not entirely correct as of ES6 - the newer Javascript revision). If you wish to use this module as-is, you would have to use a CommonJS module loader like Browserify. There are other module loaders based on different specifications other than CommonJS (such as AMD - most popularly implemented by RequireJS). You may see code like this in libraries:
(function () {
  // "this" context is now either a node global context or window context

  var libraryObject = { ...definitions... };

  if (typeof define === 'function' && define.amd) {
    // search for AMD loading context
    define('name-of-library', [], function () { return libraryObject; });
  } else {
    // export on the node "exports" object or "window" context
    (this.exports || this).libraryObject = libraryObject;
  }
}.call(this, window));

Check out browserify or webpack


Implement functions to clear or add a range of values

Java BitSet has clear(int, int) and set(int,int) functions. We should have the equivalent.

Yes. I'm looking with that.

This has been fully implemented. Closing.

Ok. Thanks for having merged my code !
Cheers!


Will log trail support 7.2.0 Kibana

Will log trail support 7.2.0 Kibana?

Here you go - https://github.com/sivasamyk/logtrail/releases/download/v0.1.31/logtrail-7.2.0-0.1.31.zip

Hi
After installing this plugin how can i see the in kibana UI