Backup not continuous

Hi,
PGHoard created folder structure and uploaded base backup to S3. However it doesn't update anything there, despite me inserting new data to the table. As I'm writing this issue Postgresql is creating new WALs, but PGHoard is ignoring them and don't upload them to S3.
Also there is only "default/basebackup" directory in S3 bucket, there is no directory with WALs.
My Postgresql and PGHoard lives on the same machine and talk to each other using unix socket.
Here is my pghoard.conf:
{
  "backup_location": "/var/lib/pghoard",
  "log_level": "INFO",
  "backup_sites": {
    "default": {
      "nodes": [ "postgresql://" ],
      "object_storage": {
        "aws_access_key_id": "SECRET",
        "aws_secret_access_key": "SECRET",
        "bucket_name": "some-bucket",
        "region": "eu-west-1",
        "storage_type": "s3"
      },
      "active_backup_mode": "pg_receivexlog",
      "basebackup_count": 2,
      "basebackup_interval_hours": 24,
      "basebackup_mode": "local-tar",
      "pg_data_directory": "/var/lib/postgresql/9.6/main",
      "encryption_key_id": "default",
      "encryption_keys": {
        "default": {
          "public": "SECRET"
        }
      }
    }
  }
}

And my comments-stripped pg_hba.conf:
local   all             postgres                                peer
local   all             all                                     peer
local   replication     postgres

Am I doing something wrong, or is there a bug in PGHoard?

Please send a log file when this happens. (make sure log_level is set to DEBUG) Sounds like a configuration bug of some sort.

Here is the log:
Aug  3 14:39:53 staging pghoard[366]: pghoard MainThread DEBUG: Loading JSON config from: '/var/lib/pghoard/pghoard.json', signal: None
Aug  3 14:39:53 staging pghoard[366]: pghoard MainThread DEBUG: Loaded config: {'path_prefix': '', 'maintenance_mode_file': '/var/lib/pghoard/maintenance_mode_file', 'transfer': {'thread_count': 16}, 'alert_file_dir': '/var/lib/pghoard', 'http_address': '<IP_ADDRESS>', 'restore_prefetch': 15, 'backup_sites': {'default': {'pg_basebackup_path': '/usr/lib/postgresql/9.6/bin/pg_basebackup', 'pg_data_directory': '/var/lib/postgresql/9.6/main', 'basebackup_count': 2, 'pg_basebackup_version': 90603, 'active_backup_mode': 'pg_receivexlog', 'pg_xlog_directory': '/var/lib/postgresql/9.6/main/pg_xlog', 'basebackup_mode': 'local-tar', 'object_storage': {'aws_access_key_id': '1SJZGD4995TPNEJDB3R2', 'bucket_name': 'planujemywesele-production-pghoard', 'region': 'eu-west-1', 'aws_secret_access_key': 'T+CUC2TLvEFN4lvjmVn1z9LjjYwpWY3jZq22uyyf', 'storage_type': 's3'}, 'pg_data_directory_version': '9.6', 'encryption_key_id': None, 'pg_receivexlog_version': 90603, 'nodes': ['postgresql://'], 'active': True, 'pg_receivexlog_path': '/usr/lib/postgresql/9.6/bin/pg_receivexlog', 'basebackup_interval_hours': 24}}, 'log_level': 'DEBUG', 'json_state_file_path': '/var/lib/pghoard/pghoard_state.json', 'compression': {'algorithm': 'snappy', 'thread_count': 16, 'level': 0}, 'http_port': 16000, 'upload_retries_warning_limit': 3, 'backup_location': '/var/lib/pghoard'} from: '/var/lib/pghoard/pghoard.json'
Aug  3 14:39:53 staging pghoard[366]: PGHoardInotify MainThread DEBUG: InotifyWatcher initialized
Aug  3 14:39:53 staging pghoard[366]: WebServer MainThread DEBUG: WebServer initialized with address: '<IP_ADDRESS>' port: 16000
Aug  3 14:39:53 staging pghoard[366]: Compressor MainThread DEBUG: Compressor initialized
Aug  3 14:39:53 staging pghoard[366]: message repeated 15 times: [ Compressor MainThread DEBUG: Compressor initialized]
Aug  3 14:39:53 staging pghoard[366]: TransferAgent MainThread DEBUG: TransferAgent initialized
Aug  3 14:39:53 staging pghoard[366]: message repeated 15 times: [ TransferAgent MainThread DEBUG: TransferAgent initialized]
Aug  3 14:39:53 staging pghoard[366]: pghoard MainThread INFO: pghoard initialized, own_hostname: 'staging', cwd: '/var/lib/pghoard'
Aug  3 14:39:53 staging pghoard[366]: PGHoardInotify Thread-1 DEBUG: Starting InotifyWatcher
Aug  3 14:39:53 staging pghoard[366]: pghoard MainThread WARNING: Found invalid file '/var/lib/pghoard/default/xlog_incoming/00000001000000000000000B.partial' from incoming xlog directory
Aug  3 14:39:53 staging pghoard[366]: PGHoardInotify MainThread DEBUG: Added watch for path: '/var/lib/pghoard/default/xlog_incoming'
Aug  3 14:39:53 staging pghoard[366]: PGReceiveXLog MainThread DEBUG: Initialized PGReceiveXLog
Aug  3 14:39:53 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: Starting to run: ['/usr/lib/postgresql/9.6/bin/pg_receivexlog', '--status-interval', '1', '--verbose', '--directory', '/var/lib/pghoard/default/xlog_incoming', '--dbname', "dbname='replication' replication='true'"]
Aug  3 14:39:53 staging pghoard[366]: boto MainThread DEBUG: Using access key provided by client.
Aug  3 14:39:53 staging pghoard[366]: boto MainThread DEBUG: Using secret key provided by client.
Aug  3 14:39:53 staging pghoard[366]: boto MainThread DEBUG: path=/
Aug  3 14:39:53 staging pghoard[366]: boto MainThread DEBUG: auth_path=/planujemywesele-production-pghoard/
Aug  3 14:39:53 staging pghoard[366]: boto MainThread DEBUG: Method: HEAD
Aug  3 14:39:53 staging pghoard[366]: boto MainThread DEBUG: Path: /
Aug  3 14:39:53 staging pghoard[366]: boto MainThread DEBUG: Data:
Aug  3 14:39:53 staging pghoard[366]: boto MainThread DEBUG: Headers: {}
Aug  3 14:39:53 staging pghoard[366]: boto MainThread DEBUG: Host: planujemywesele-production-pghoard.s3-eu-west-1.amazonaws.com:443
Aug  3 14:39:53 staging pghoard[366]: boto MainThread DEBUG: Port: 443
Aug  3 14:39:53 staging pghoard[366]: boto MainThread DEBUG: Params: {}
Aug  3 14:39:53 staging pghoard[366]: PGReceiveXLog Thread-35 INFO: Started: ['/usr/lib/postgresql/9.6/bin/pg_receivexlog', '--status-interval', '1', '--verbose', '--directory', '/var/lib/pghoard/default/xlog_incoming', '--dbname', "dbname='replication' replication='true'"], running as PID: 414
Aug  3 14:39:53 staging pghoard[366]: boto MainThread DEBUG: establishing HTTPS connection: host=planujemywesele-production-pghoard.s3-eu-west-1.amazonaws.com, kwargs={'timeout': 70, 'port': 443}
Aug  3 14:39:53 staging pghoard[366]: boto MainThread DEBUG: Token: None
Aug  3 14:39:53 staging pghoard[366]: boto MainThread DEBUG: StringToSign:
Aug  3 14:39:53 staging pghoard[366]: HEAD
Aug  3 14:39:53 staging pghoard[366]: Thu, 03 Aug 2017 12:39:53 GMT
Aug  3 14:39:53 staging pghoard[366]: /planujemywesele-production-pghoard/
Aug  3 14:39:53 staging pghoard[366]: boto MainThread DEBUG: Signature:
Aug  3 14:39:53 staging pghoard[366]: AWS 1SJZGD4995TPNEJDB3R2:myeUKMkj336hxKANkoxQxagZTEY=
Aug  3 14:39:53 staging pghoard[366]: boto MainThread DEBUG: Final headers: {'Date': 'Thu, 03 Aug 2017 12:39:53 GMT', 'Content-Length': '0', 'User-Agent': 'Boto/2.40.0 Python/3.5.3 Linux/4.10.0-28-generic', 'Authorization': 'AWS 1SJZGD4995TPNEJDB3R2:myeUKMkj336hxKANkoxQxagZTEY='}
Aug  3 14:39:53 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:39:53 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'
Aug  3 14:39:54 staging pghoard[366]: boto MainThread DEBUG: Response headers: [('x-amz-id-2', '0g0tYhgae7htLm8o1PEodrgSOewatc1owcwLqy5ws58RcRkVB27v5QA79Q3ZOUs75OlR3lf+WWc='), ('x-amz-request-id', 'FF3DE419D870953F'), ('Date', 'Thu, 03 Aug 2017 12:39:55 GMT'), ('x-amz-bucket-region', 'eu-west-1'), ('Content-Type', 'application/xml'), ('Transfer-Encoding', 'chunked'), ('Server', 'AmazonS3')]
Aug  3 14:39:54 staging pghoard[366]: S3Transfer MainThread DEBUG: Found bucket: 'planujemywesele-production-pghoard'
Aug  3 14:39:54 staging pghoard[366]: S3Transfer MainThread DEBUG: S3Transfer initialized
Aug  3 14:39:54 staging pghoard[366]: S3Transfer MainThread DEBUG: Listing path 'default/basebackup/'
Aug  3 14:39:54 staging pghoard[366]: boto MainThread DEBUG: path=/
Aug  3 14:39:54 staging pghoard[366]: boto MainThread DEBUG: auth_path=/planujemywesele-production-pghoard/
Aug  3 14:39:54 staging pghoard[366]: boto MainThread DEBUG: path=/?delimiter=/&prefix=default/basebackup/
Aug  3 14:39:54 staging pghoard[366]: boto MainThread DEBUG: auth_path=/planujemywesele-production-pghoard/?delimiter=/&prefix=default/basebackup/
Aug  3 14:39:54 staging pghoard[366]: boto MainThread DEBUG: Method: GET
Aug  3 14:39:54 staging pghoard[366]: boto MainThread DEBUG: Path: /?delimiter=/&prefix=default/basebackup/
Aug  3 14:39:54 staging pghoard[366]: boto MainThread DEBUG: Data:
Aug  3 14:39:54 staging pghoard[366]: boto MainThread DEBUG: Headers: {}
Aug  3 14:39:54 staging pghoard[366]: boto MainThread DEBUG: Host: planujemywesele-production-pghoard.s3-eu-west-1.amazonaws.com:443
Aug  3 14:39:54 staging pghoard[366]: boto MainThread DEBUG: Port: 443
Aug  3 14:39:54 staging pghoard[366]: boto MainThread DEBUG: Params: {}
Aug  3 14:39:54 staging pghoard[366]: boto MainThread DEBUG: Token: None
Aug  3 14:39:54 staging pghoard[366]: boto MainThread DEBUG: StringToSign:
Aug  3 14:39:54 staging pghoard[366]: GET
Aug  3 14:39:54 staging pghoard[366]: Thu, 03 Aug 2017 12:39:54 GMT
Aug  3 14:39:54 staging pghoard[366]: /planujemywesele-production-pghoard/
Aug  3 14:39:54 staging pghoard[366]: boto MainThread DEBUG: Signature:
Aug  3 14:39:54 staging pghoard[366]: AWS 1SJZGD4995TPNEJDB3R2:MnaFC+l0vuC23MEMjT2hQKxFUkI=
Aug  3 14:39:54 staging pghoard[366]: boto MainThread DEBUG: Final headers: {'Date': 'Thu, 03 Aug 2017 12:39:54 GMT', 'Content-Length': '0', 'User-Agent': 'Boto/2.40.0 Python/3.5.3 Linux/4.10.0-28-generic', 'Authorization': 'AWS 1SJZGD4995TPNEJDB3R2:MnaFC+l0vuC23MEMjT2hQKxFUkI='}
Aug  3 14:39:54 staging pghoard[366]: boto MainThread DEBUG: Response headers: [('x-amz-id-2', 'bcFQRmS5QqYkVvc6xnr6oQcIv8y7XVtN4DvxSwN7FHcrYTrdFw1NEBL+VaM6LErwISwBU7eQ3Zw='), ('x-amz-request-id', '374086AA73744EAE'), ('Date', 'Thu, 03 Aug 2017 12:39:55 GMT'), ('x-amz-bucket-region', 'eu-west-1'), ('Content-Type', 'application/xml'), ('Transfer-Encoding', 'chunked'), ('Server', 'AmazonS3')]
Aug  3 14:39:54 staging pghoard[366]: boto MainThread DEBUG: b'<?xml version="1.0" encoding="UTF-8"?>\n<ListBucketResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Name>planujemywesele-production-pghoard</Name><Prefix>default/basebackup/</Prefix><Marker></Marker><MaxKeys>1000</MaxKeys><Delimiter>/</Delimiter><IsTruncated>false</IsTruncated></ListBucketResult>'
Aug  3 14:39:54 staging pghoard[366]: pghoard MainThread DEBUG: Found [] basebackups
Aug  3 14:39:54 staging pghoard[366]: pghoard MainThread INFO: Creating a new basebackup for 'default' because there are currently none
Aug  3 14:39:54 staging pghoard[366]: pghoard MainThread DEBUG: Writing JSON state file to '/var/lib/pghoard/pghoard_state.json'
Aug  3 14:39:54 staging pghoard[366]: PGBaseBackup Thread-36 DEBUG: Connecting to database to start backup process
Aug  3 14:39:54 staging pghoard[366]: pghoard MainThread DEBUG: Wrote JSON state file to disk, took 0.0178s
Aug  3 14:39:54 staging pghoard[366]: PGBaseBackup Thread-36 INFO: Starting to backup '/var/lib/postgresql/9.6/main' to '/var/lib/pghoard/default/basebackup/2017-08-03_3'
Aug  3 14:39:54 staging pghoard[366]: WebServer Thread-37 DEBUG: Request: PUT '/default/archive/00000003000000000000002E'
Aug  3 14:39:54 staging pghoard[366]: WebServer Thread-37 DEBUG: Got request to archive: 'default' 'xlog' '00000003000000000000002E', '/var/lib/postgresql/9.6/main/pg_xlog/00000003000000000000002E'
Aug  3 14:39:54 staging pghoard[366]: Compressor Thread-3 INFO: Compressed 16777216 byte open file '/var/lib/postgresql/9.6/main/pg_xlog/00000003000000000000002E' to 797365 bytes (5%), took: 0.048s
Aug  3 14:39:54 staging pghoard[366]: TransferAgent Thread-19 DEBUG: Starting to 'UPLOAD' '/var/lib/postgresql/9.6/main/pg_xlog/00000003000000000000002E', size: 797365
Aug  3 14:39:54 staging pghoard[366]: boto Thread-19 DEBUG: Using access key provided by client.
Aug  3 14:39:54 staging pghoard[366]: boto Thread-19 DEBUG: Using secret key provided by client.

Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: Using secret key provided by client.
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: path=/
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: auth_path=/planujemywesele-production-pghoard/
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: Method: HEAD
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: Path: /
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: Data:
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: Headers: {}
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: Host: planujemywesele-production-pghoard.s3-eu-west-1.amazonaws.com:443
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: Port: 443
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: Params: {}
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: establishing HTTPS connection: host=planujemywesele-production-pghoard.s3-eu-west-1.amazonaws.com, kwargs={'timeout': 70, 'port': 443}
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: Token: None
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: StringToSign:
Aug  3 14:39:55 staging pghoard[366]: HEAD
Aug  3 14:39:55 staging pghoard[366]: Thu, 03 Aug 2017 12:39:55 GMT
Aug  3 14:39:55 staging pghoard[366]: /planujemywesele-production-pghoard/
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: Signature:
Aug  3 14:39:55 staging pghoard[366]: AWS 1SJZGD4995TPNEJDB3R2:MzKsqu+OAMati9uZPn1FEOUek+8=
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: Final headers: {'Date': 'Thu, 03 Aug 2017 12:39:55 GMT', 'Content-Length': '0', 'User-Agent': 'Boto/2.40.0 Python/3.5.3 Linux/4.10.0-28-generic', 'Authorization': 'AWS 1SJZGD4995TPNEJDB3R2:MzKsqu+OAMati9uZPn1FEOUek+8='}
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: Response headers: [('x-amz-id-2', 'pGV39vRXDhKMdDFwBzNskvEbrfPAuyibMzI3c8j+/7qFQO3U7r2KXkQroJ5fwYaSKq3+Wv18dDY='), ('x-amz-request-id', '2A1F0574A7A2099A'), ('Date', 'Thu, 03 Aug 2017 12:39:56 GMT'), ('x-amz-bucket-region', 'eu-west-1'), ('Content-Type', 'application/xml'), ('Transfer-Encoding', 'chunked'), ('Server', 'AmazonS3')]
Aug  3 14:39:55 staging pghoard[366]: S3Transfer Thread-20 DEBUG: Found bucket: 'planujemywesele-production-pghoard'
Aug  3 14:39:55 staging pghoard[366]: S3Transfer Thread-20 DEBUG: S3Transfer initialized
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: path=/default/xlog/00000003000000000000002F
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: auth_path=/planujemywesele-production-pghoard/default/xlog/00000003000000000000002F
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: Method: PUT
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: Path: /default/xlog/00000003000000000000002F
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: Data:
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: Headers: {'Content-Type': 'application/octet-stream', 'x-amz-meta-original-file-size': '16777216', 'x-amz-meta-pg-version': '90603', 'Expect': '100-Continue', 'x-amz-meta-compression-algorithm': 'snappy', 'Content-MD5': 'fB0LHCnAP+k8aR7Cq/vE4w==', 'x-amz-meta-compression-level': '0', 'User-Agent': 'Boto/2.40.0 Python/3.5.3 Linux/4.10.0-28-generic', 'Content-Length': '797270'}
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: Host: planujemywesele-production-pghoard.s3-eu-west-1.amazonaws.com:443
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: Port: 443
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: Params: {}
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: Token: None
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: StringToSign:
Aug  3 14:39:55 staging pghoard[366]: PUT
Aug  3 14:39:55 staging pghoard[366]: fB0LHCnAP+k8aR7Cq/vE4w==
Aug  3 14:39:55 staging pghoard[366]: application/octet-stream
Aug  3 14:39:55 staging pghoard[366]: Thu, 03 Aug 2017 12:39:55 GMT
Aug  3 14:39:55 staging pghoard[366]: x-amz-meta-compression-algorithm:snappy
Aug  3 14:39:55 staging pghoard[366]: x-amz-meta-compression-level:0
Aug  3 14:39:55 staging pghoard[366]: x-amz-meta-original-file-size:16777216
Aug  3 14:39:55 staging pghoard[366]: x-amz-meta-pg-version:90603
Aug  3 14:39:55 staging pghoard[366]: /planujemywesele-production-pghoard/default/xlog/00000003000000000000002F
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: Signature:
Aug  3 14:39:55 staging pghoard[366]: AWS 1SJZGD4995TPNEJDB3R2:xHzD6se+eFYntcjjZ3nNtEKvFC4=
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: Final headers: {'Content-Type': 'application/octet-stream', 'x-amz-meta-original-file-size': '16777216', 'Authorization': 'AWS 1SJZGD4995TPNEJDB3R2:xHzD6se+eFYntcjjZ3nNtEKvFC4=', 'x-amz-meta-pg-version': '90603', 'Expect': '100-Continue', 'Date': 'Thu, 03 Aug 2017 12:39:55 GMT', 'x-amz-meta-compression-algorithm': 'snappy', 'Content-MD5': 'fB0LHCnAP+k8aR7Cq/vE4w==', 'x-amz-meta-compression-level': '0', 'User-Agent': 'Boto/2.40.0 Python/3.5.3 Linux/4.10.0-28-generic', 'Content-Length': '797270'}
Aug  3 14:39:55 staging pghoard[366]: boto Thread-20 DEBUG: Response headers: [('x-amz-id-2', 'kCFJffkiUBZ0lVaeObhTA8QU4Gs7XPIEsI+E4XyOvzMtLehcuIjA+wr5sjihvxeKQLmMWm9KS2c='), ('x-amz-request-id', 'A2A49B05D7B31758'), ('Date', 'Thu, 03 Aug 2017 12:39:56 GMT'), ('ETag', '"7c1d0b1c29c03fe93c691ec2abfbc4e3"'), ('Content-Length', '0'), ('Server', 'AmazonS3')]
Aug  3 14:39:55 staging pghoard[366]: TransferAgent Thread-20 INFO: 'UPLOAD' transfer of key: 'default/xlog/00000003000000000000002F', size: 797270, took 0.478s
Aug  3 14:39:55 staging pghoard[366]: WebServer Thread-38 DEBUG: Handled an archival request for: 'default' '/var/lib/postgresql/9.6/main/pg_xlog/00000003000000000000002F', took: 0.532s
Aug  3 14:39:55 staging pghoard[366]: WebServer Thread-38 DEBUG: HttpResponse 201
Aug  3 14:39:55 staging pghoard[366]: <IP_ADDRESS> - - [03/Aug/2017 14:39:55] "PUT /default/archive/00000003000000000000002F HTTP/1.1" 201 -
Aug  3 14:39:55 staging pghoard[366]: WebServer Thread-39 DEBUG: Request: PUT '/default/archive/000000030000000000000030'
Aug  3 14:39:55 staging pghoard[366]: WebServer Thread-39 DEBUG: Got request to archive: 'default' 'xlog' '000000030000000000000030', '/var/lib/postgresql/9.6/main/pg_xlog/000000030000000000000030'
Aug  3 14:39:56 staging pghoard[366]: Compressor Thread-3 INFO: Compressed 16777216 byte open file '/var/lib/postgresql/9.6/main/pg_xlog/000000030000000000000030' to 797271 bytes (5%), took: 0.049s
Aug  3 14:39:56 staging pghoard[366]: TransferAgent Thread-20 DEBUG: Starting to 'UPLOAD' '/var/lib/postgresql/9.6/main/pg_xlog/000000030000000000000030', size: 797271
Aug  3 14:39:56 staging pghoard[366]: boto Thread-20 DEBUG: path=/default/xlog/000000030000000000000030
Aug  3 14:39:56 staging pghoard[366]: boto Thread-20 DEBUG: auth_path=/planujemywesele-production-pghoard/default/xlog/000000030000000000000030
Aug  3 14:39:56 staging pghoard[366]: boto Thread-20 DEBUG: Method: PUT
Aug  3 14:39:56 staging pghoard[366]: boto Thread-20 DEBUG: Path: /default/xlog/000000030000000000000030
Aug  3 14:39:56 staging pghoard[366]: boto Thread-20 DEBUG: Data:
Aug  3 14:39:56 staging pghoard[366]: boto Thread-20 DEBUG: Headers: {'Content-Type': 'application/octet-stream', 'x-amz-meta-original-file-size': '16777216', 'x-amz-meta-pg-version': '90603', 'Expect': '100-Continue', 'x-amz-meta-compression-algorithm': 'snappy', 'Content-MD5': 'WAgzkrT7aOEPk/YYDFNfgw==', 'x-amz-meta-compression-level': '0', 'User-Agent': 'Boto/2.40.0 Python/3.5.3 Linux/4.10.0-28-generic', 'Content-Length': '797271'}
Aug  3 14:39:56 staging pghoard[366]: boto Thread-20 DEBUG: Host: planujemywesele-production-pghoard.s3-eu-west-1.amazonaws.com:443
Aug  3 14:39:56 staging pghoard[366]: boto Thread-20 DEBUG: Port: 443
Aug  3 14:39:56 staging pghoard[366]: boto Thread-20 DEBUG: Params: {}
Aug  3 14:39:56 staging pghoard[366]: boto Thread-20 DEBUG: Token: None
Aug  3 14:39:56 staging pghoard[366]: boto Thread-20 DEBUG: StringToSign:
Aug  3 14:39:56 staging pghoard[366]: PUT
Aug  3 14:39:56 staging pghoard[366]: WAgzkrT7aOEPk/YYDFNfgw==
Aug  3 14:39:56 staging pghoard[366]: application/octet-stream
Aug  3 14:39:56 staging pghoard[366]: Thu, 03 Aug 2017 12:39:56 GMT
Aug  3 14:39:56 staging pghoard[366]: x-amz-meta-compression-algorithm:snappy
Aug  3 14:39:56 staging pghoard[366]: x-amz-meta-compression-level:0
Aug  3 14:39:56 staging pghoard[366]: x-amz-meta-original-file-size:16777216
Aug  3 14:39:56 staging pghoard[366]: x-amz-meta-pg-version:90603
Aug  3 14:39:56 staging pghoard[366]: /planujemywesele-production-pghoard/default/xlog/000000030000000000000030
Aug  3 14:39:56 staging pghoard[366]: boto Thread-20 DEBUG: Signature:
Aug  3 14:39:56 staging pghoard[366]: AWS 1SJZGD4995TPNEJDB3R2:2bPe5RYVg+fQ40t2BWp76ptUbTI=
Aug  3 14:39:56 staging pghoard[366]: boto Thread-20 DEBUG: Final headers: {'Content-Type': 'application/octet-stream', 'x-amz-meta-original-file-size': '16777216', 'Authorization': 'AWS 1SJZGD4995TPNEJDB3R2:2bPe5RYVg+fQ40t2BWp76ptUbTI=', 'x-amz-meta-pg-version': '90603', 'Expect': '100-Continue', 'Date': 'Thu, 03 Aug 2017 12:39:56 GMT', 'x-amz-meta-compression-algorithm': 'snappy', 'Content-MD5': 'WAgzkrT7aOEPk/YYDFNfgw==', 'x-amz-meta-compression-level': '0', 'User-Agent': 'Boto/2.40.0 Python/3.5.3 Linux/4.10.0-28-generic', 'Content-Length': '797271'}
Aug  3 14:39:56 staging pghoard[366]: boto Thread-20 DEBUG: Response headers: [('x-amz-id-2', 'ha9VeloLAjePdQzO+gTydVFtOSkPmIdQ2BEBn4aQjiWDLgKnTrESOUE3vMogWRn13do493oTJuQ='), ('x-amz-request-id', '199646933BEB8CA3'), ('Date', 'Thu, 03 Aug 2017 12:39:57 GMT'), ('ETag', '"58083392b4fb68e10f93f6180c535f83"'), ('Content-Length', '0'), ('Server', 'AmazonS3')]
Aug  3 14:39:56 staging pghoard[366]: TransferAgent Thread-20 INFO: 'UPLOAD' transfer of key: 'default/xlog/000000030000000000000030', size: 797271, took 0.282s
Aug  3 14:39:56 staging pghoard[366]: WebServer Thread-39 DEBUG: Handled an archival request for: 'default' '/var/lib/postgresql/9.6/main/pg_xlog/000000030000000000000030', took: 0.331s
Aug  3 14:39:56 staging pghoard[366]: WebServer Thread-39 DEBUG: HttpResponse 201
Aug  3 14:39:56 staging pghoard[366]: <IP_ADDRESS> - - [03/Aug/2017 14:39:56] "PUT /default/archive/000000030000000000000030 HTTP/1.1" 201 -
Aug  3 14:39:56 staging pghoard[366]: WebServer Thread-40 DEBUG: Request: PUT '/default/archive/000000030000000000000031'
Aug  3 14:39:56 staging pghoard[366]: WebServer Thread-40 DEBUG: Got request to archive: 'default' 'xlog' '000000030000000000000031', '/var/lib/postgresql/9.6/main/pg_xlog/000000030000000000000031'
Aug  3 14:39:56 staging pghoard[366]: Compressor Thread-4 INFO: Compressed 16777216 byte open file '/var/lib/postgresql/9.6/main/pg_xlog/000000030000000000000031' to 797368 bytes (5%), took: 0.050s
Aug  3 14:39:56 staging pghoard[366]: TransferAgent Thread-21 DEBUG: Starting to 'UPLOAD' '/var/lib/postgresql/9.6/main/pg_xlog/000000030000000000000031', size: 797368
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: Using access key provided by client.
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: Using secret key provided by client.
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: path=/
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: auth_path=/planujemywesele-production-pghoard/
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: Method: HEAD
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: Path: /
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: Data:
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: Headers: {}
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: Host: planujemywesele-production-pghoard.s3-eu-west-1.amazonaws.com:443
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: Port: 443
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: Params: {}
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: establishing HTTPS connection: host=planujemywesele-production-pghoard.s3-eu-west-1.amazonaws.com, kwargs={'timeout': 70, 'port': 443}
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: Token: None
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: StringToSign:
Aug  3 14:39:56 staging pghoard[366]: HEAD
Aug  3 14:39:56 staging pghoard[366]: Thu, 03 Aug 2017 12:39:56 GMT
Aug  3 14:39:56 staging pghoard[366]: /planujemywesele-production-pghoard/
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: Signature:
Aug  3 14:39:56 staging pghoard[366]: AWS 1SJZGD4995TPNEJDB3R2:665x2vxauL++VcF5MNv4bi93FYQ=
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: Final headers: {'Date': 'Thu, 03 Aug 2017 12:39:56 GMT', 'Content-Length': '0', 'User-Agent': 'Boto/2.40.0 Python/3.5.3 Linux/4.10.0-28-generic', 'Authorization': 'AWS 1SJZGD4995TPNEJDB3R2:665x2vxauL++VcF5MNv4bi93FYQ='}
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: Response headers: [('x-amz-id-2', 'TJ1CjykkhkV1JVEdPdpY5ksnOqDmAD5MBXT9oSi5jzlb2aJNaiIV9sAn7pqiW7pUp/QHU5Z3UM0='), ('x-amz-request-id', '4599FEA9A56D1E89'), ('Date', 'Thu, 03 Aug 2017 12:39:57 GMT'), ('x-amz-bucket-region', 'eu-west-1'), ('Content-Type', 'application/xml'), ('Transfer-Encoding', 'chunked'), ('Server', 'AmazonS3')]
Aug  3 14:39:56 staging pghoard[366]: S3Transfer Thread-21 DEBUG: Found bucket: 'planujemywesele-production-pghoard'
Aug  3 14:39:56 staging pghoard[366]: S3Transfer Thread-21 DEBUG: S3Transfer initialized
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: path=/default/xlog/000000030000000000000031
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: auth_path=/planujemywesele-production-pghoard/default/xlog/000000030000000000000031
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: Method: PUT
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: Path: /default/xlog/000000030000000000000031
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: Data:
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: Headers: {'Content-Type': 'application/octet-stream', 'x-amz-meta-original-file-size': '16777216', 'x-amz-meta-pg-version': '90603', 'Expect': '100-Continue', 'x-amz-meta-compression-algorithm': 'snappy', 'Content-MD5': '+EPiSAFbFePUZjOWR2xsgg==', 'x-amz-meta-compression-level': '0', 'User-Agent': 'Boto/2.40.0 Python/3.5.3 Linux/4.10.0-28-generic', 'Content-Length': '797368'}
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: Host: planujemywesele-production-pghoard.s3-eu-west-1.amazonaws.com:443
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: Port: 443
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: Params: {}
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: Token: None
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: StringToSign:
Aug  3 14:39:56 staging pghoard[366]: PUT
Aug  3 14:39:56 staging pghoard[366]: +EPiSAFbFePUZjOWR2xsgg==
Aug  3 14:39:56 staging pghoard[366]: application/octet-stream
Aug  3 14:39:56 staging pghoard[366]: Thu, 03 Aug 2017 12:39:56 GMT
Aug  3 14:39:56 staging pghoard[366]: x-amz-meta-compression-algorithm:snappy
Aug  3 14:39:56 staging pghoard[366]: x-amz-meta-compression-level:0
Aug  3 14:39:56 staging pghoard[366]: x-amz-meta-original-file-size:16777216
Aug  3 14:39:56 staging pghoard[366]: x-amz-meta-pg-version:90603
Aug  3 14:39:56 staging pghoard[366]: /planujemywesele-production-pghoard/default/xlog/000000030000000000000031
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: Signature:
Aug  3 14:39:56 staging pghoard[366]: AWS 1SJZGD4995TPNEJDB3R2:NwNgAoFvwYUkie8imkadrBA+vj0=
Aug  3 14:39:56 staging pghoard[366]: boto Thread-21 DEBUG: Final headers: {'Content-Type': 'application/octet-stream', 'x-amz-meta-original-file-size': '16777216', 'Authorization': 'AWS 1SJZGD4995TPNEJDB3R2:NwNgAoFvwYUkie8imkadrBA+vj0=', 'x-amz-meta-pg-version': '90603', 'Expect': '100-Continue', 'Date': 'Thu, 03 Aug 2017 12:39:56 GMT', 'x-amz-meta-compression-algorithm': 'snappy', 'Content-MD5': '+EPiSAFbFePUZjOWR2xsgg==', 'x-amz-meta-compression-level': '0', 'User-Agent': 'Boto/2.40.0 Python/3.5.3 Linux/4.10.0-28-generic', 'Content-Length': '797368'}
Aug  3 14:39:57 staging pghoard[366]: boto Thread-21 DEBUG: Response headers: [('x-amz-id-2', '97YVL29mmEFWW5CfTG4O4CfDJxUIQXDsmUG3UEitagpN/W+WPS6BI8epOLkDRZFExYQFXxJ5qrQ='), ('x-amz-request-id', 'C82FDDEA1270937C'), ('Date', 'Thu, 03 Aug 2017 12:39:57 GMT'), ('ETag', '"f843e248015b15e3d4663396476c6c82"'), ('Content-Length', '0'), ('Server', 'AmazonS3')]
Aug  3 14:39:57 staging pghoard[366]: TransferAgent Thread-21 INFO: 'UPLOAD' transfer of key: 'default/xlog/000000030000000000000031', size: 797368, took 0.583s
Aug  3 14:39:57 staging pghoard[366]: WebServer Thread-40 DEBUG: Handled an archival request for: 'default' '/var/lib/postgresql/9.6/main/pg_xlog/000000030000000000000031', took: 0.634s
Aug  3 14:39:57 staging pghoard[366]: WebServer Thread-40 DEBUG: HttpResponse 201
Aug  3 14:39:57 staging pghoard[366]: <IP_ADDRESS> - - [03/Aug/2017 14:39:57] "PUT /default/archive/000000030000000000000031 HTTP/1.1" 201 -
Aug  3 14:39:57 staging pghoard[366]: PGBaseBackup Thread-36 INFO: Compressed 31959040 byte /var/lib/postgresql/9.6/main to 6674758 bytes (21%), took: 3.417s
Aug  3 14:39:58 staging pghoard[366]: WebServer Thread-37 DEBUG: Request: PUT '/default/archive/000000030000000000000032'
Aug  3 14:39:58 staging pghoard[366]: WebServer Thread-37 DEBUG: Got request to archive: 'default' 'xlog' '000000030000000000000032', '/var/lib/postgresql/9.6/main/pg_xlog/000000030000000000000032'
Aug  3 14:39:58 staging pghoard[366]: Compressor Thread-4 INFO: Compressed 16777216 byte open file '/var/lib/postgresql/9.6/main/pg_xlog/000000030000000000000032' to 797274 bytes (5%), took: 0.046s
Aug  3 14:39:58 staging pghoard[366]: TransferAgent Thread-20 DEBUG: Starting to 'UPLOAD' '/var/lib/postgresql/9.6/main/pg_xlog/000000030000000000000032', size: 797274
Aug  3 14:39:58 staging pghoard[366]: boto Thread-20 DEBUG: path=/default/xlog/000000030000000000000032
Aug  3 14:39:58 staging pghoard[366]: boto Thread-20 DEBUG: auth_path=/planujemywesele-production-pghoard/default/xlog/000000030000000000000032
Aug  3 14:39:58 staging pghoard[366]: boto Thread-20 DEBUG: Method: PUT
Aug  3 14:39:58 staging pghoard[366]: boto Thread-20 DEBUG: Path: /default/xlog/000000030000000000000032
Aug  3 14:39:58 staging pghoard[366]: boto Thread-20 DEBUG: Data:
Aug  3 14:39:58 staging pghoard[366]: boto Thread-20 DEBUG: Headers: {'Content-Type': 'application/octet-stream', 'x-amz-meta-original-file-size': '16777216', 'x-amz-meta-pg-version': '90603', 'Expect': '100-Continue', 'x-amz-meta-compression-algorithm': 'snappy', 'Content-MD5': '0AYq7+m4WgbbX8V++R2D8g==', 'x-amz-meta-compression-level': '0', 'User-Agent': 'Boto/2.40.0 Python/3.5.3 Linux/4.10.0-28-generic', 'Content-Length': '797274'}
Aug  3 14:39:58 staging pghoard[366]: boto Thread-20 DEBUG: Host: planujemywesele-production-pghoard.s3-eu-west-1.amazonaws.com:443
Aug  3 14:39:58 staging pghoard[366]: boto Thread-20 DEBUG: Port: 443
Aug  3 14:39:58 staging pghoard[366]: boto Thread-20 DEBUG: Params: {}
Aug  3 14:39:58 staging pghoard[366]: boto Thread-20 DEBUG: Token: None
Aug  3 14:39:58 staging pghoard[366]: boto Thread-20 DEBUG: StringToSign:
Aug  3 14:39:58 staging pghoard[366]: PUT
Aug  3 14:39:58 staging pghoard[366]: 0AYq7+m4WgbbX8V++R2D8g==
Aug  3 14:39:58 staging pghoard[366]: application/octet-stream
Aug  3 14:39:58 staging pghoard[366]: Thu, 03 Aug 2017 12:39:58 GMT
Aug  3 14:39:58 staging pghoard[366]: x-amz-meta-compression-algorithm:snappy
Aug  3 14:39:58 staging pghoard[366]: x-amz-meta-compression-level:0
Aug  3 14:39:58 staging pghoard[366]: x-amz-meta-original-file-size:16777216
Aug  3 14:39:58 staging pghoard[366]: x-amz-meta-pg-version:90603
Aug  3 14:39:58 staging pghoard[366]: /planujemywesele-production-pghoard/default/xlog/000000030000000000000032
Aug  3 14:39:58 staging pghoard[366]: boto Thread-20 DEBUG: Signature:
Aug  3 14:39:58 staging pghoard[366]: AWS 1SJZGD4995TPNEJDB3R2:ke/447MAdiu85qDEz5u1PIO6BQo=
Aug  3 14:39:58 staging pghoard[366]: boto Thread-20 DEBUG: Final headers: {'Content-Type': 'application/octet-stream', 'x-amz-meta-original-file-size': '16777216', 'Authorization': 'AWS 1SJZGD4995TPNEJDB3R2:ke/447MAdiu85qDEz5u1PIO6BQo=', 'x-amz-meta-pg-version': '90603', 'Expect': '100-Continue', 'Date': 'Thu, 03 Aug 2017 12:39:58 GMT', 'x-amz-meta-compression-algorithm': 'snappy', 'Content-MD5': '0AYq7+m4WgbbX8V++R2D8g==', 'x-amz-meta-compression-level': '0', 'User-Agent': 'Boto/2.40.0 Python/3.5.3 Linux/4.10.0-28-generic', 'Content-Length': '797274'}
Aug  3 14:39:58 staging pghoard[366]: boto Thread-20 DEBUG: Response headers: [('x-amz-id-2', 'wRRXpF91CBLnKXVsC3Z7m+PEJUREA04kD1nVS7JN33BnkKSAsKSKbSoKnGstC3HpgYmxD2Gr0dg='), ('x-amz-request-id', '6AA4B192F8515D6F'), ('Date', 'Thu, 03 Aug 2017 12:39:59 GMT'), ('ETag', '"d0062aefe9b85a06db5fc57ef91d83f2"'), ('Content-Length', '0'), ('Server', 'AmazonS3')]
Aug  3 14:39:58 staging pghoard[366]: TransferAgent Thread-20 INFO: 'UPLOAD' transfer of key: 'default/xlog/000000030000000000000032', size: 797274, took 0.371s
Aug  3 14:39:58 staging pghoard[366]: WebServer Thread-37 DEBUG: Handled an archival request for: 'default' '/var/lib/postgresql/9.6/main/pg_xlog/000000030000000000000032', took: 0.418s
Aug  3 14:39:58 staging pghoard[366]: WebServer Thread-37 DEBUG: HttpResponse 201
Aug  3 14:39:58 staging pghoard[366]: <IP_ADDRESS> - - [03/Aug/2017 14:39:58] "PUT /default/archive/000000030000000000000032 HTTP/1.1" 201 -
Aug  3 14:39:58 staging pghoard[366]: WebServer Thread-39 DEBUG: Request: PUT '/default/archive/000000030000000000000033'
Aug  3 14:39:58 staging pghoard[366]: WebServer Thread-39 DEBUG: Got request to archive: 'default' 'xlog' '000000030000000000000033', '/var/lib/postgresql/9.6/main/pg_xlog/000000030000000000000033'
Aug  3 14:39:58 staging pghoard[366]: Compressor Thread-5 INFO: Compressed 16777216 byte open file '/var/lib/postgresql/9.6/main/pg_xlog/000000030000000000000033' to 797353 bytes (5%), took: 0.048s
Aug  3 14:39:58 staging pghoard[366]: TransferAgent Thread-22 DEBUG: Starting to 'UPLOAD' '/var/lib/postgresql/9.6/main/pg_xlog/000000030000000000000033', size: 797353
Aug  3 14:39:58 staging pghoard[366]: boto Thread-22 DEBUG: Using access key provided by client.
Aug  3 14:39:58 staging pghoard[366]: boto Thread-22 DEBUG: Using secret key provided by client.

Aug  3 14:39:59 staging pghoard[366]: During handling of the above exception, another exception occurred:
Aug  3 14:39:59 staging pghoard[366]: Traceback (most recent call last):
Aug  3 14:39:59 staging pghoard[366]:   File "/usr/lib/python3/dist-packages/pghoard/basebackup.py", line 78, in run
Aug  3 14:39:59 staging pghoard[366]:     self.run_local_tar_basebackup()
Aug  3 14:39:59 staging pghoard[366]:   File "/usr/lib/python3/dist-packages/pghoard/basebackup.py", line 536, in run_local_tar_basebackup
Aug  3 14:39:59 staging pghoard[366]:     backup_end_time, backup_end_wal_segment = self.get_backup_end_time_and_segment(db_conn, backup_mode)
Aug  3 14:39:59 staging pghoard[366]: psycopg2.InterfaceError: connection already closed
Aug  3 14:39:59 staging pghoard[366]: pghoard MainThread DEBUG: Basebackup has finished for 'default': {'success': False}
Aug  3 14:39:59 staging pghoard[366]: S3Transfer MainThread DEBUG: Listing path 'default/basebackup/'
Aug  3 14:39:59 staging pghoard[366]: boto MainThread DEBUG: path=/
Aug  3 14:39:59 staging pghoard[366]: boto MainThread DEBUG: auth_path=/planujemywesele-production-pghoard/
Aug  3 14:39:59 staging pghoard[366]: boto MainThread DEBUG: path=/?delimiter=/&prefix=default/basebackup/
Aug  3 14:39:59 staging pghoard[366]: boto MainThread DEBUG: auth_path=/planujemywesele-production-pghoard/?delimiter=/&prefix=default/basebackup/
Aug  3 14:39:59 staging pghoard[366]: boto MainThread DEBUG: Method: GET
Aug  3 14:39:59 staging pghoard[366]: boto MainThread DEBUG: Path: /?delimiter=/&prefix=default/basebackup/
Aug  3 14:39:59 staging pghoard[366]: boto MainThread DEBUG: Data:
Aug  3 14:39:59 staging pghoard[366]: boto MainThread DEBUG: Headers: {}
Aug  3 14:39:59 staging pghoard[366]: boto MainThread DEBUG: Host: planujemywesele-production-pghoard.s3-eu-west-1.amazonaws.com:443
Aug  3 14:39:59 staging pghoard[366]: boto MainThread DEBUG: Port: 443
Aug  3 14:39:59 staging pghoard[366]: boto MainThread DEBUG: Params: {}
Aug  3 14:39:59 staging pghoard[366]: boto MainThread DEBUG: Token: None
Aug  3 14:39:59 staging pghoard[366]: boto MainThread DEBUG: StringToSign:
Aug  3 14:39:59 staging pghoard[366]: GET
Aug  3 14:39:59 staging pghoard[366]: Thu, 03 Aug 2017 12:39:59 GMT
Aug  3 14:39:59 staging pghoard[366]: /planujemywesele-production-pghoard/
Aug  3 14:39:59 staging pghoard[366]: boto MainThread DEBUG: Signature:
Aug  3 14:39:59 staging pghoard[366]: AWS 1SJZGD4995TPNEJDB3R2:JyPJFwsI8J0nMDXQ6/LOpjE6Xv0=
Aug  3 14:39:59 staging pghoard[366]: boto MainThread DEBUG: Final headers: {'Date': 'Thu, 03 Aug 2017 12:39:59 GMT', 'Content-Length': '0', 'User-Agent': 'Boto/2.40.0 Python/3.5.3 Linux/4.10.0-28-generic', 'Authorization': 'AWS 1SJZGD4995TPNEJDB3R2:JyPJFwsI8J0nMDXQ6/LOpjE6Xv0='}
Aug  3 14:39:59 staging pghoard[366]: boto MainThread DEBUG: Response headers: [('x-amz-id-2', 'KS7KNuK+xma2pAhbW5AiObv3DPLnybxj+BbiARry385qAICNv/xyiYVinInLD+yamSLAZxkxlDw='), ('x-amz-request-id', '3B9F5E72FCCF5AF6'), ('Date', 'Thu, 03 Aug 2017 12:40:00 GMT'), ('x-amz-bucket-region', 'eu-west-1'), ('Content-Type', 'application/xml'), ('Transfer-Encoding', 'chunked'), ('Server', 'AmazonS3')]
Aug  3 14:39:59 staging pghoard[366]: boto MainThread DEBUG: b'<?xml version="1.0" encoding="UTF-8"?>\n<ListBucketResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Name>planujemywesele-production-pghoard</Name><Prefix>default/basebackup/</Prefix><Marker></Marker><MaxKeys>1000</MaxKeys><Delimiter>/</Delimiter><IsTruncated>false</IsTruncated></ListBucketResult>'
Aug  3 14:39:59 staging pghoard[366]: pghoard MainThread DEBUG: Found [] basebackups
Aug  3 14:39:59 staging pghoard[366]: pghoard MainThread INFO: Creating a new basebackup for 'default' because there are currently none
Aug  3 14:39:59 staging pghoard[366]: pghoard MainThread WARNING: OperationalError (FATAL:  the database system is shutting down
Aug  3 14:39:59 staging pghoard[366]: ) connecting to DB at: "dbname='replication' replication='true'"
Aug  3 14:39:59 staging pghoard[366]: pghoard.common MainThread WARNING: Creating alert file: '/var/lib/pghoard/configuration_error'
Aug  3 14:39:59 staging pghoard[366]: pghoard MainThread DEBUG: Writing JSON state file to '/var/lib/pghoard/pghoard_state.json'
Aug  3 14:39:59 staging pghoard[366]: pghoard MainThread DEBUG: Wrote JSON state file to disk, took 0.0064s
Aug  3 14:39:59 staging pghoard[366]: boto Thread-22 DEBUG: Response headers: [('x-amz-id-2', 'V3B0+3UVZP5V7dWATgQL74DQiXEtKnbYIVbsI29gC0HR2Oh9lnk//6xb0faNRgTp0T24YmJgi1w='), ('x-amz-request-id', '9A4EA5686E2D542B'), ('Date', 'Thu, 03 Aug 2017 12:40:00 GMT'), ('ETag', '"4b0ab8af0d53c92f8fbdcfdcf8af8e4c"'), ('Content-Length', '0'), ('Server', 'AmazonS3')]
Aug  3 14:39:59 staging pghoard[366]: TransferAgent Thread-22 INFO: 'UPLOAD' transfer of key: 'default/xlog/000000030000000000000033', size: 797353, took 0.519s
Aug  3 14:39:59 staging pghoard[366]: WebServer Thread-39 DEBUG: Handled an archival request for: 'default' '/var/lib/postgresql/9.6/main/pg_xlog/000000030000000000000033', took: 0.568s
Aug  3 14:39:59 staging pghoard[366]: WebServer Thread-39 DEBUG: HttpResponse 201
Aug  3 14:40:03 staging pghoard[366]: <IP_ADDRESS> - - [03/Aug/2017 14:39:59] "PUT /default/archive/000000030000000000000033 HTTP/1.1" 201 -
Aug  3 14:40:03 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:40:03 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'
Aug  3 14:40:04 staging pghoard[366]: pghoard MainThread INFO: Creating a new basebackup for 'default' because there are currently none
Aug  3 14:40:04 staging pghoard[366]: pghoard MainThread DEBUG: Writing JSON state file to '/var/lib/pghoard/pghoard_state.json'
Aug  3 14:40:04 staging pghoard[366]: PGBaseBackup Thread-43 DEBUG: Connecting to database to start backup process
Aug  3 14:40:04 staging pghoard[366]: pghoard MainThread DEBUG: Wrote JSON state file to disk, took 0.0113s
Aug  3 14:40:04 staging pghoard[366]: PGBaseBackup Thread-43 INFO: Starting to backup '/var/lib/postgresql/9.6/main' to '/var/lib/pghoard/default/basebackup/2017-08-03_4'
Aug  3 14:40:04 staging pghoard[366]: PGBaseBackup Thread-43 INFO: Compressed 31846400 byte /var/lib/postgresql/9.6/main to 6652122 bytes (21%), took: 0.322s
Aug  3 14:40:04 staging pghoard[366]: PGBaseBackup Thread-43 DEBUG: Found: '000000030000000000000035' as starting wal segment, start_time: '2017-08-03T14:40:04+02:00'
Aug  3 14:40:04 staging pghoard[366]: TransferAgent Thread-19 DEBUG: Starting to 'UPLOAD' '/var/lib/pghoard/default/basebackup/2017-08-03_4', size: 6652122
Aug  3 14:40:04 staging pghoard[366]: boto Thread-19 DEBUG: path=/default/basebackup/2017-08-03_4
Aug  3 14:40:04 staging pghoard[366]: boto Thread-19 DEBUG: auth_path=/planujemywesele-production-pghoard/default/basebackup/2017-08-03_4
Aug  3 14:40:04 staging pghoard[366]: boto Thread-19 DEBUG: Method: PUT
Aug  3 14:40:04 staging pghoard[366]: boto Thread-19 DEBUG: Path: /default/basebackup/2017-08-03_4
Aug  3 14:40:04 staging pghoard[366]: boto Thread-19 DEBUG: Data:
Aug  3 14:40:04 staging pghoard[366]: boto Thread-19 DEBUG: Headers: {'x-amz-meta-end-time': '2017-08-03 14:40:04.762883+02:00', 'x-amz-meta-original-file-size': '31846400', 'Content-Type': 'application/octet-stream', 'x-amz-meta-pg-version': '90603', 'Expect': '100-Continue', 'x-amz-meta-start-time': '2017-08-03T14:40:04+02:00', 'x-amz-meta-format': 'pghoard-bb-v1', 'x-amz-meta-compression-algorithm': 'snappy', 'Content-MD5': 'mksykM2Uieh8DmmJ0/4bzA==', 'x-amz-meta-start-wal-segment': '000000030000000000000035', 'Content-Length': '6652122', 'User-Agent': 'Boto/2.40.0 Python/3.5.3 Linux/4.10.0-28-generic', 'x-amz-meta-end-wal-segment': '000000030000000000000035'}
Aug  3 14:40:04 staging pghoard[366]: boto Thread-19 DEBUG: Host: planujemywesele-production-pghoard.s3-eu-west-1.amazonaws.com:443
Aug  3 14:40:04 staging pghoard[366]: boto Thread-19 DEBUG: Port: 443
Aug  3 14:40:04 staging pghoard[366]: boto Thread-19 DEBUG: Params: {}
Aug  3 14:40:04 staging pghoard[366]: boto Thread-19 DEBUG: Token: None
Aug  3 14:40:04 staging pghoard[366]: boto Thread-19 DEBUG: StringToSign:
Aug  3 14:40:04 staging pghoard[366]: PUT
Aug  3 14:40:04 staging pghoard[366]: mksykM2Uieh8DmmJ0/4bzA==
Aug  3 14:40:04 staging pghoard[366]: application/octet-stream
Aug  3 14:40:04 staging pghoard[366]: Thu, 03 Aug 2017 12:40:04 GMT
Aug  3 14:40:04 staging pghoard[366]: x-amz-meta-compression-algorithm:snappy
Aug  3 14:40:04 staging pghoard[366]: x-amz-meta-end-time:2017-08-03 14:40:04.762883+02:00
Aug  3 14:40:04 staging pghoard[366]: x-amz-meta-end-wal-segment:000000030000000000000035
Aug  3 14:40:04 staging pghoard[366]: x-amz-meta-format:pghoard-bb-v1
Aug  3 14:40:04 staging pghoard[366]: x-amz-meta-original-file-size:31846400
Aug  3 14:40:04 staging pghoard[366]: x-amz-meta-pg-version:90603
Aug  3 14:40:04 staging pghoard[366]: x-amz-meta-start-time:2017-08-03T14:40:04+02:00
Aug  3 14:40:04 staging pghoard[366]: x-amz-meta-start-wal-segment:000000030000000000000035
Aug  3 14:40:04 staging pghoard[366]: /planujemywesele-production-pghoard/default/basebackup/2017-08-03_4
Aug  3 14:40:04 staging pghoard[366]: boto Thread-19 DEBUG: Signature:
Aug  3 14:40:04 staging pghoard[366]: AWS 1SJZGD4995TPNEJDB3R2:D2nD8EsQOZlLekLrjOeKOWpkHns=
Aug  3 14:40:04 staging pghoard[366]: boto Thread-19 DEBUG: Final headers: {'x-amz-meta-end-time': '2017-08-03 14:40:04.762883+02:00', 'x-amz-meta-original-file-size': '31846400', 'Content-Type': 'application/octet-stream', 'Date': 'Thu, 03 Aug 2017 12:40:04 GMT', 'x-amz-meta-pg-version': '90603', 'Expect': '100-Continue', 'x-amz-meta-start-time': '2017-08-03T14:40:04+02:00', 'Authorization': 'AWS 1SJZGD4995TPNEJDB3R2:D2nD8EsQOZlLekLrjOeKOWpkHns=', 'x-amz-meta-format': 'pghoard-bb-v1', 'x-amz-meta-compression-algorithm': 'snappy', 'Content-MD5': 'mksykM2Uieh8DmmJ0/4bzA==', 'x-amz-meta-start-wal-segment': '000000030000000000000035', 'Content-Length': '6652122', 'User-Agent': 'Boto/2.40.0 Python/3.5.3 Linux/4.10.0-28-generic', 'x-amz-meta-end-wal-segment': '000000030000000000000035'}
Aug  3 14:40:04 staging pghoard[366]: boto Thread-19 DEBUG: encountered BrokenPipeError exception, reconnecting
Aug  3 14:40:04 staging pghoard[366]: boto Thread-19 DEBUG: establishing HTTPS connection: host=planujemywesele-production-pghoard.s3-eu-west-1.amazonaws.com, kwargs={'timeout': 70, 'port': 443}
Aug  3 14:40:05 staging pghoard[366]: boto Thread-19 DEBUG: Token: None
Aug  3 14:40:05 staging pghoard[366]: boto Thread-19 DEBUG: StringToSign:
Aug  3 14:40:05 staging pghoard[366]: PUT
Aug  3 14:40:05 staging pghoard[366]: mksykM2Uieh8DmmJ0/4bzA==
Aug  3 14:40:05 staging pghoard[366]: application/octet-stream
Aug  3 14:40:05 staging pghoard[366]: Thu, 03 Aug 2017 12:40:04 GMT
Aug  3 14:40:05 staging pghoard[366]: x-amz-meta-compression-algorithm:snappy
Aug  3 14:40:05 staging pghoard[366]: x-amz-meta-end-time:2017-08-03 14:40:04.762883+02:00
Aug  3 14:40:05 staging pghoard[366]: x-amz-meta-end-wal-segment:000000030000000000000035
Aug  3 14:40:05 staging pghoard[366]: x-amz-meta-format:pghoard-bb-v1
Aug  3 14:40:05 staging pghoard[366]: x-amz-meta-original-file-size:31846400
Aug  3 14:40:05 staging pghoard[366]: x-amz-meta-pg-version:90603
Aug  3 14:40:05 staging pghoard[366]: x-amz-meta-start-time:2017-08-03T14:40:04+02:00
Aug  3 14:40:05 staging pghoard[366]: x-amz-meta-start-wal-segment:000000030000000000000035
Aug  3 14:40:05 staging pghoard[366]: /planujemywesele-production-pghoard/default/basebackup/2017-08-03_4
Aug  3 14:40:05 staging pghoard[366]: boto Thread-19 DEBUG: Signature:
Aug  3 14:40:05 staging pghoard[366]: AWS 1SJZGD4995TPNEJDB3R2:D2nD8EsQOZlLekLrjOeKOWpkHns=
Aug  3 14:40:05 staging pghoard[366]: boto Thread-19 DEBUG: Final headers: {'x-amz-meta-end-time': '2017-08-03 14:40:04.762883+02:00', 'x-amz-meta-original-file-size': '31846400', 'Content-Type': 'application/octet-stream', 'Date': 'Thu, 03 Aug 2017 12:40:04 GMT', 'x-amz-meta-pg-version': '90603', 'Expect': '100-Continue', 'x-amz-meta-start-time': '2017-08-03T14:40:04+02:00', 'Authorization': 'AWS 1SJZGD4995TPNEJDB3R2:D2nD8EsQOZlLekLrjOeKOWpkHns=', 'x-amz-meta-format': 'pghoard-bb-v1', 'x-amz-meta-compression-algorithm': 'snappy', 'Content-MD5': 'mksykM2Uieh8DmmJ0/4bzA==', 'x-amz-meta-start-wal-segment': '000000030000000000000035', 'Content-Length': '6652122', 'User-Agent': 'Boto/2.40.0 Python/3.5.3 Linux/4.10.0-28-generic', 'x-amz-meta-end-wal-segment': '000000030000000000000035'}
Aug  3 14:40:07 staging pghoard[366]: boto Thread-19 DEBUG: Response headers: [('x-amz-id-2', 'gMQBQ5c8kKidD0JniCJcs+ljxkbT7BobQKqh2KDQ7iybE35HRZx4opEVCvrpCJBA31m1BP0Bumk='), ('x-amz-request-id', 'BA9BCA96BEAFA912'), ('Date', 'Thu, 03 Aug 2017 12:40:07 GMT'), ('ETag', '"9a4b3290cd9489e87c0e6989d3fe1bcc"'), ('Content-Length', '0'), ('Server', 'AmazonS3')]
Aug  3 14:40:07 staging pghoard[366]: TransferAgent Thread-19 DEBUG: Deleting file: '/var/lib/pghoard/default/basebackup/2017-08-03_4' since it has been uploaded
Aug  3 14:40:07 staging pghoard[366]: TransferAgent Thread-19 INFO: 'UPLOAD' transfer of key: 'default/basebackup/2017-08-03_4', size: 6652122, took 2.443s
Aug  3 14:40:08 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:40:08 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'
Aug  3 14:40:09 staging pghoard[366]: pghoard MainThread DEBUG: Basebackup has finished for 'default': {'success': True, 'opaque': None}
Aug  3 14:40:09 staging pghoard[366]: S3Transfer MainThread DEBUG: Listing path 'default/basebackup/'
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: path=/
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: auth_path=/planujemywesele-production-pghoard/
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: path=/?delimiter=/&prefix=default/basebackup/
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: auth_path=/planujemywesele-production-pghoard/?delimiter=/&prefix=default/basebackup/
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Method: GET
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Path: /?delimiter=/&prefix=default/basebackup/
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Data:
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Headers: {}
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Host: planujemywesele-production-pghoard.s3-eu-west-1.amazonaws.com:443
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Port: 443
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Params: {}
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Token: None
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: StringToSign:
Aug  3 14:40:09 staging pghoard[366]: GET
Aug  3 14:40:09 staging pghoard[366]: Thu, 03 Aug 2017 12:40:09 GMT
Aug  3 14:40:09 staging pghoard[366]: /planujemywesele-production-pghoard/
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Signature:
Aug  3 14:40:09 staging pghoard[366]: AWS 1SJZGD4995TPNEJDB3R2:SScBwxVdUtVtAf5KzefuAKLE5Ko=
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Final headers: {'Date': 'Thu, 03 Aug 2017 12:40:09 GMT', 'Content-Length': '0', 'User-Agent': 'Boto/2.40.0 Python/3.5.3 Linux/4.10.0-28-generic', 'Authorization': 'AWS 1SJZGD4995TPNEJDB3R2:SScBwxVdUtVtAf5KzefuAKLE5Ko='}
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: encountered RemoteDisconnected exception, reconnecting
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: establishing HTTPS connection: host=planujemywesele-production-pghoard.s3-eu-west-1.amazonaws.com, kwargs={'timeout': 70, 'port': 443}
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Token: None
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: StringToSign:
Aug  3 14:40:09 staging pghoard[366]: GET
Aug  3 14:40:09 staging pghoard[366]: Thu, 03 Aug 2017 12:40:09 GMT
Aug  3 14:40:09 staging pghoard[366]: /planujemywesele-production-pghoard/
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Signature:
Aug  3 14:40:09 staging pghoard[366]: AWS 1SJZGD4995TPNEJDB3R2:SScBwxVdUtVtAf5KzefuAKLE5Ko=
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Final headers: {'Date': 'Thu, 03 Aug 2017 12:40:09 GMT', 'Content-Length': '0', 'User-Agent': 'Boto/2.40.0 Python/3.5.3 Linux/4.10.0-28-generic', 'Authorization': 'AWS 1SJZGD4995TPNEJDB3R2:SScBwxVdUtVtAf5KzefuAKLE5Ko='}
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Response headers: [('x-amz-id-2', 'fOGSstsu/z9wXKM+FMHHBtWaqYiNRYbxRfBvxNekqe2hRLP23UfFo+rnCP6OwHTNe8VQngCwcAE='), ('x-amz-request-id', 'E1B7955E9D5B0DB2'), ('Date', 'Thu, 03 Aug 2017 12:40:10 GMT'), ('x-amz-bucket-region', 'eu-west-1'), ('Content-Type', 'application/xml'), ('Transfer-Encoding', 'chunked'), ('Server', 'AmazonS3')]
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: b'<?xml version="1.0" encoding="UTF-8"?>\n<ListBucketResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Name>planujemywesele-production-pghoard</Name><Prefix>default/basebackup/</Prefix><Marker></Marker><MaxKeys>1000</MaxKeys><Delimiter>/</Delimiter><IsTruncated>false</IsTruncated><Contents><Key>default/basebackup/2017-08-03_4</Key><LastModified>2017-08-03T12:40:07.000Z</LastModified><ETag>"9a4b3290cd9489e87c0e6989d3fe1bcc"</ETag><Size>6652122</Size><Owner><ID>2eec8550b6fbe2d8f52628098ea13ef8f8f7440a221c1810321f524152226e62</ID><DisplayName>pawel3</DisplayName></Owner><StorageClass>STANDARD</StorageClass></Contents></ListBucketResult>'
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: path=/default/basebackup/2017-08-03_4
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: auth_path=/planujemywesele-production-pghoard/default/basebackup/2017-08-03_4
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Method: HEAD
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Path: /default/basebackup/2017-08-03_4
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Data:
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Headers: {}
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Host: planujemywesele-production-pghoard.s3-eu-west-1.amazonaws.com:443
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Port: 443
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Params: {}
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Token: None
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: StringToSign:
Aug  3 14:40:09 staging pghoard[366]: HEAD
Aug  3 14:40:09 staging pghoard[366]: Thu, 03 Aug 2017 12:40:09 GMT
Aug  3 14:40:09 staging pghoard[366]: /planujemywesele-production-pghoard/default/basebackup/2017-08-03_4
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Signature:
Aug  3 14:40:09 staging pghoard[366]: AWS 1SJZGD4995TPNEJDB3R2:C6V2jBtBhf/FULrERd+rdPVoCH4=
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Final headers: {'Date': 'Thu, 03 Aug 2017 12:40:09 GMT', 'Content-Length': '0', 'User-Agent': 'Boto/2.40.0 Python/3.5.3 Linux/4.10.0-28-generic', 'Authorization': 'AWS 1SJZGD4995TPNEJDB3R2:C6V2jBtBhf/FULrERd+rdPVoCH4='}
Aug  3 14:40:09 staging pghoard[366]: boto MainThread DEBUG: Response headers: [('x-amz-id-2', 'JKXU9KjCIVb0GGDulAtIx4X1HO2Bs4m5Joe73VVPhs51SnJSFzAZsyELgtqut38FCrYJvEIpzaA='), ('x-amz-request-id', 'E58538D3AB4E481F'), ('Date', 'Thu, 03 Aug 2017 12:40:10 GMT'), ('Last-Modified', 'Thu, 03 Aug 2017 12:40:07 GMT'), ('ETag', '"9a4b3290cd9489e87c0e6989d3fe1bcc"'), ('x-amz-meta-start-wal-segment', '000000030000000000000035'), ('x-amz-meta-pg-version', '90603'), ('x-amz-meta-compression-algorithm', 'snappy'), ('x-amz-meta-format', 'pghoard-bb-v1'), ('x-amz-meta-end-time', '2017-08-03 14:40:04.762883+02:00'), ('x-amz-meta-end-wal-segment', '000000030000000000000035'), ('x-amz-meta-original-file-size', '31846400'), ('x-amz-meta-start-time', '2017-08-03T14:40:04+02:00'), ('Accept-Ranges', 'bytes'), ('Content-Type', 'application/octet-stream'), ('Content-Length', '6652122'), ('Server', 'AmazonS3')]
Aug  3 14:40:09 staging pghoard[366]: pghoard MainThread DEBUG: Found [{'size': 6652122, 'metadata': {'original-file-size': '31846400', 'compression-algorithm': 'snappy', 'format': 'pghoard-bb-v1', 'end-time': '2017-08-03 14:40:04.762883+02:00', 'pg-version': '90603', 'start-time': datetime.datetime(2017, 8, 3, 14, 40, 4, tzinfo=tzoffset(None, 7200)), 'start-wal-segment': '000000030000000000000035', 'end-wal-segment': '000000030000000000000035'}, 'name': '2017-08-03_4', 'last_modified': datetime.datetime(2017, 8, 3, 12, 40, 7, tzinfo=tzutc())}] basebackups
Aug  3 14:40:09 staging pghoard[366]: pghoard MainThread DEBUG: Writing JSON state file to '/var/lib/pghoard/pghoard_state.json'
Aug  3 14:40:09 staging pghoard[366]: pghoard MainThread DEBUG: Wrote JSON state file to disk, took 0.0090s
Aug  3 14:40:13 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:40:13 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'
Aug  3 14:40:14 staging pghoard[366]: pghoard MainThread DEBUG: Writing JSON state file to '/var/lib/pghoard/pghoard_state.json'
Aug  3 14:40:14 staging pghoard[366]: pghoard MainThread DEBUG: Wrote JSON state file to disk, took 0.0095s
Aug  3 14:40:18 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:40:18 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'
Aug  3 14:40:19 staging pghoard[366]: pghoard MainThread DEBUG: Writing JSON state file to '/var/lib/pghoard/pghoard_state.json'
Aug  3 14:40:19 staging pghoard[366]: pghoard MainThread DEBUG: Wrote JSON state file to disk, took 0.0096s
Aug  3 14:40:23 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:40:23 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'
Aug  3 14:40:24 staging pghoard[366]: pghoard MainThread DEBUG: Writing JSON state file to '/var/lib/pghoard/pghoard_state.json'
Aug  3 14:40:24 staging pghoard[366]: pghoard MainThread DEBUG: Wrote JSON state file to disk, took 0.0094s
Aug  3 14:40:29 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:40:29 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'
Aug  3 14:40:29 staging pghoard[366]: pghoard MainThread DEBUG: Writing JSON state file to '/var/lib/pghoard/pghoard_state.json'
Aug  3 14:40:29 staging pghoard[366]: pghoard MainThread DEBUG: Wrote JSON state file to disk, took 0.0094s
Aug  3 14:40:34 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:40:34 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'
Aug  3 14:40:34 staging pghoard[366]: pghoard MainThread DEBUG: Writing JSON state file to '/var/lib/pghoard/pghoard_state.json'
Aug  3 14:40:34 staging pghoard[366]: pghoard MainThread DEBUG: Wrote JSON state file to disk, took 0.0093s
Aug  3 14:40:39 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:40:39 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'
Aug  3 14:40:39 staging pghoard[366]: pghoard MainThread DEBUG: Writing JSON state file to '/var/lib/pghoard/pghoard_state.json'
Aug  3 14:40:39 staging pghoard[366]: pghoard MainThread DEBUG: Wrote JSON state file to disk, took 0.0094s
Aug  3 14:40:44 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:40:44 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'
Aug  3 14:40:44 staging pghoard[366]: pghoard MainThread DEBUG: Writing JSON state file to '/var/lib/pghoard/pghoard_state.json'
Aug  3 14:40:44 staging pghoard[366]: pghoard MainThread DEBUG: Wrote JSON state file to disk, took 0.0093s
Aug  3 14:40:49 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:40:49 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'
Aug  3 14:40:49 staging pghoard[366]: pghoard MainThread DEBUG: Writing JSON state file to '/var/lib/pghoard/pghoard_state.json'
Aug  3 14:40:49 staging pghoard[366]: pghoard MainThread DEBUG: Wrote JSON state file to disk, took 0.0094s
Aug  3 14:40:54 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:40:54 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'
Aug  3 14:40:54 staging pghoard[366]: pghoard MainThread DEBUG: Writing JSON state file to '/var/lib/pghoard/pghoard_state.json'
Aug  3 14:40:54 staging pghoard[366]: pghoard MainThread DEBUG: Wrote JSON state file to disk, took 0.0099s
Aug  3 14:40:59 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:40:59 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'
Aug  3 14:40:59 staging pghoard[366]: pghoard MainThread DEBUG: Writing JSON state file to '/var/lib/pghoard/pghoard_state.json'
Aug  3 14:40:59 staging pghoard[366]: pghoard MainThread DEBUG: Wrote JSON state file to disk, took 0.0092s
Aug  3 14:41:04 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:41:04 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'
Aug  3 14:41:04 staging pghoard[366]: pghoard MainThread DEBUG: Writing JSON state file to '/var/lib/pghoard/pghoard_state.json'
Aug  3 14:41:04 staging pghoard[366]: pghoard MainThread DEBUG: Wrote JSON state file to disk, took 0.0094s
Aug  3 14:41:09 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:41:09 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'
Aug  3 14:41:09 staging pghoard[366]: pghoard MainThread DEBUG: Writing JSON state file to '/var/lib/pghoard/pghoard_state.json'
Aug  3 14:41:09 staging pghoard[366]: pghoard MainThread DEBUG: Wrote JSON state file to disk, took 0.0092s
Aug  3 14:41:14 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:41:14 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'
Aug  3 14:41:14 staging pghoard[366]: pghoard MainThread DEBUG: Writing JSON state file to '/var/lib/pghoard/pghoard_state.json'
Aug  3 14:41:14 staging pghoard[366]: pghoard MainThread DEBUG: Wrote JSON state file to disk, took 0.0100s
Aug  3 14:41:19 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:41:19 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'

Here is a problematic part of the log:
Aug  3 14:40:49 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:40:49 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'
Aug  3 14:40:49 staging pghoard[366]: pghoard MainThread DEBUG: Writing JSON state file to '/var/lib/pghoard/pghoard_state.json'
Aug  3 14:40:49 staging pghoard[366]: pghoard MainThread DEBUG: Wrote JSON state file to disk, took 0.0094s
Aug  3 14:40:54 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:40:54 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'
Aug  3 14:40:54 staging pghoard[366]: pghoard MainThread DEBUG: Writing JSON state file to '/var/lib/pghoard/pghoard_state.json'
Aug  3 14:40:54 staging pghoard[366]: pghoard MainThread DEBUG: Wrote JSON state file to disk, took 0.0099s
Aug  3 14:40:59 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:40:59 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'
Aug  3 14:40:59 staging pghoard[366]: pghoard MainThread DEBUG: Writing JSON state file to '/var/lib/pghoard/pghoard_state.json'
Aug  3 14:40:59 staging pghoard[366]: pghoard MainThread DEBUG: Wrote JSON state file to disk, took 0.0092s
Aug  3 14:41:04 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:41:04 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'
Aug  3 14:41:04 staging pghoard[366]: pghoard MainThread DEBUG: Writing JSON state file to '/var/lib/pghoard/pghoard_state.json'
Aug  3 14:41:04 staging pghoard[366]: pghoard MainThread DEBUG: Wrote JSON state file to disk, took 0.0094s
Aug  3 14:41:09 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:41:09 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'
Aug  3 14:41:09 staging pghoard[366]: pghoard MainThread DEBUG: Writing JSON state file to '/var/lib/pghoard/pghoard_state.json'
Aug  3 14:41:09 staging pghoard[366]: pghoard MainThread DEBUG: Wrote JSON state file to disk, took 0.0092s
Aug  3 14:41:14 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:41:14 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'
Aug  3 14:41:14 staging pghoard[366]: pghoard MainThread DEBUG: Writing JSON state file to '/var/lib/pghoard/pghoard_state.json'
Aug  3 14:41:14 staging pghoard[366]: pghoard MainThread DEBUG: Wrote JSON state file to disk, took 0.0100s
Aug  3 14:41:19 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)\n'
Aug  3 14:41:19 staging pghoard[366]: PGReceiveXLog Thread-35 DEBUG: b'pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again\n'

Any my postgresql.conf (without comments):
data_directory = '/var/lib/postgresql/9.6/main'
hba_file = '/etc/postgresql/9.6/main/pg_hba.conf'
ident_file = '/etc/postgresql/9.6/main/pg_ident.conf'
external_pid_file = '/var/run/postgresql/9.6-main.pid'
listen_addresses = ''
max_connections = 100
unix_socket_directories = '/var/run/postgresql'
shared_buffers = 8GB
dynamic_shared_memory_type = posix
wal_level = replica
max_wal_senders = 4
random_page_cost = 1.5
log_line_prefix = '%m [%p] %q%u@%d '
log_timezone = 'localtime'
cluster_name = '9.6/main'
stats_temp_directory = '/var/run/postgresql/9.6-main.pg_stat_tmp'
datestyle = 'iso, mdy'
timezone = 'localtime'
lc_messages = 'en_US.UTF-8'
lc_monetary = 'en_US.UTF-8'
lc_numeric = 'en_US.UTF-9'
lc_time = 'en_US.UTF-8'
default_text_search_config = 'pg_catalog.english'

You might want to take a look at your postgresql logs. It should be able to run that START_REPLICATION command, the log will probably tell you why it could not.

Here is Postgresql DEBUG5 log. Could you tell whye START_REPLICATION command doesn't work?  In your pghoard log you should be able to see the receivexlog command and the parameters that are used with it. If you run the same command by hand you should be able to reproduce the issue.

I've started pg_receivexlog manually passing the same arguments as PGHoard. Here is the output:
postgres@staging:/tmp$ /usr/lib/postgresql/9.6/bin/pg_receivexlog --status-interval 1 --verbose --directory /var/lib/pghoard/default/xlog_incoming --dbname dbname="'replication' replication='true'"
DEBUG:  CommitTransaction
DEBUG:  name: unnamed; blockState:       STARTED; state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
DEBUG:  received replication command: IDENTIFY_SYSTEM
DEBUG:  received replication command: IDENTIFY_SYSTEM
pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)
DEBUG:  received replication command: START_REPLICATION 0/B000000 TIMELINE 1
pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again
DEBUG:  CommitTransaction
DEBUG:  name: unnamed; blockState:       STARTED; state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
DEBUG:  received replication command: IDENTIFY_SYSTEM
pg_receivexlog: starting log streaming at 0/B000000 (timeline 1)
DEBUG:  received replication command: START_REPLICATION 0/B000000 TIMELINE 1
pg_receivexlog: could not send replication command "START_REPLICATION": pg_receivexlog: disconnected; waiting 5 seconds to try again

There are no OOM kills in dmesg. The server has 64GB of RAM and 8GB is used for Postgres shared_buffers. The database is almost empty.

After reinstalling entire host using ansible pg_receivexlog started to work correctly :)


WebviewView retainContextWhenHidden

I am working on an extension where I wish to retain the context of WebviewViews when they are hidden.  This would work just as the option retainContextWhenHidden does with WebviewPanels. getState and setState are not sufficient for our extension because we have some complex UI elements displayed through scripts.  I was wondering if there was anyway around this, or if this feature could be added.  Again, basically, I need retainContextWhenHidden, but for WebviewViews, not just WebviewPanels.

We have a great developer community over on slack where extension authors help each other. This is a great place for you to ask questions and find support.
Happy Coding!

I found that that was possible for WebviewPanels, but not for WebviewViews.  I am looking for the same type of functionality for webviews I display in the sidebar or bottom panel area.

The code I linked to is for webview views. You pass in retainContextWhenHidden for the call to registerWebviewViewProvider

Oh, my apologies, I see now.  Thank you so much.


Cannot use from wsl without a --host param (and probably directory too)

I have a modified version of tm-remote-build on my main machine and while setting things up again on my laptop re-found that I can't use it from WSL. The two args I added to make it work was host and directory.
The command I use is tm-remote-build load folder "$PLUGIN_FOLDER_NAME" --host <IP_ADDRESS> --port 30000 -v -d "$HOME/OpenplanetNext/"
I can share my modifications in a few weeks when I'm back in Australia.

Those additions make sense for wsl. I may be able to put something together for that sooner than a few weeks

As i suspected, adding the --host argument was very easy.
We dont need the Openplanet directory to make the plugin load so is that -d argument that you added just to help it find the Openplanet.log file? By default its using a filepath returned from Openplanet itself which would probably not end up being a valid path on WSL.
I can install WSL myself just to confirm. But anyway I think I'll add the -d argument to help with finding the log file and hopefully that will be what you need.

I think i should have it all working now but would love your feedback if you dont mind. Branch name is feature/configurable-host or you can look at #6.


Enhance arxiv scraper to include the new orchestrator methods

Integrated arxiv scraper methods into new orchestrator directory structure
New arxiv scraping from id's logic
orchestrator indexing with arxiv seems to work

@eloinoel
looks pretty good.


Is the SNS necessary in your design?

Hi there. I'm just wondering if the SNS as the "decoupling" mechanism is necessary and/or if there was a specific requirement or reasoning behind it.
Your flow of getting a response from a model is as follows:

front-end connects to a websocket  - which, under the hood, invokes the publisher Lambda - but it doesn't do much due to route_key being equal to $connect
then, front-end sends the user prompt to the open websocket (https://github.com/aws-samples/bedrock-claude-chat/blob/c2eec81489497e6ccabcd4d6009e64053b44a12d/frontend/src/hooks/usePostMessageStreaming.ts#L25) - it also triggers the same publisher Lambda. However, this time, it actually pushes the prompt forward to the SNS because the route_key is different.
now, the SNS invokes the websocket Lambda, which streams the response back to the websocket (https://github.com/aws-samples/bedrock-claude-chat/blob/main/backend/app/websocket.py#L77)

However, if (instead of being SNS consumer) your websocket Lambda was just a different route on the WS API gateway (lets call it /invoke), then the flow could look as follows:

front-end connects to a websocket  - which, under the hood, invokes the publisher Lambda - but it doesn't do much due to route_key being equal to $connect
front-end sends the user prompt to the open websocket as an action /invoke - it triggers the websocket Lambda

Voila, you no longer need the SNS and it still works the same way.
Am I missing something (could be totally wrong above of course)? Is the SNS here necessary? Does it provide any additional value over this alternative method that I've described which would simplify the design?
Other than that - great work. Thanks for providing this excellent blueprint!

Tomaz, check out the Readme under Architecture. I just happened to read this myself and was wondering the same thing. :-)
[Amazon SNS]: Used to decouple streaming calls between API Gateway and Bedrock because streaming responses can take over 30 seconds in total, exceeding the limitations of HTTP integration (See quota).

@tomaszdudek7
Thank you for your suggestion. We re-verified the behavior of http integration and confirmed that lambda can continue to send message to websocket connection after 30 sec passed although the message Endpoint request timed out sent. So I believe that we can simplify the architecture with front-end implementation which ignore the message saying timed out. We'll modify when we have time (PR is also welcome), thank you!

@ctodd Yes, but my point was that SNS is not even required here, as confirmed in the comment above.


immutable version tags for container images?

Description of the problem:
when browsing the list of available tags on https://hub.docker.com/r/gliderlabs/registrator/tags I see that 'master' and 'vendor' tags were last updated 7 months ago, but those names suggest they may point at a different version of the container image in the future (similar to 'latest'), this is fine if one wants to always consume the latest, but in a stable production environment unexpected changes do to a redeployment can be bad, and so it's useful to be able to pin the container version to something that won't change.  I see there are some older version tags (v7 being the latest) but nothing for the current master release.  Can we get a v8 tag, or just a build number type of tag or something that is more likely not to change?

v8 just hasn't been released yet.

@josegonzalez I understand that v8 hasn't been release yet but @bjornicus is asking if we can get at least an additional tag (like the git short commit id for example) that matches latest master (updated 8 months ago instead of v7 3years ago) that we can use to pin the registrator version in production environments.
Is is true that we could vendor the project but at what cost... all of us maintain an internal fork an sync and build it over and over .. on your side it is really something easy to do.. and I noticed that tons of people have already asked something like this... so this small change on your side could really benefit a lot of other people in the same situation.


test_complex_lock is not passing if python interpreter is not 2.7

When I run tests I have a problem with test_complex_lock. The reason is apscheduler package which for python 3> doesn't need funcsigs and futures dependency.
All other tests are working with python 3>

This test should always pass. It always passes on Linux. Funcsigs should always be in the lockfile, it should just have markers as a key as well. Are you running tests yourself? What os?

Yes, this test always passes but only if the version of intepreter is 2.7. Because if I use interpreter 3> for running of test , the test is downloading version apschedular which doesn't have funcsigs and futures (https://pypi.python.org/pypi/APScheduler ->  futures; python_version == "2.7"
funcsigs; python_version == "2.7" )
I don't know if somebody is running tests on python 3>, but after this changes all tests will be passed.
I have Archlinux, default python 3.6

Yes I understand that the test passes running python3 pipenv into a 2.7 environment. The test case was my idea.
The goal of pipenv is to have a resolver that when you run it on python 3, resolving a python 3 environment, it also includes optional packages that would only be installed on python 2. The goal of pipenv is not to arbitrarily force tests to pass
This is why I said before that these tests should always pass as-is. Not because I forgot that apscheduler resolves funcsigs for python 2, but because we rewrote the resolver specifically around this test case.
I am going to close this because this test exists for a reason

Ok, thanks for an explanation. So, I will look why these packages are not installed then.


simple update to include basic AAD information

simple update for basic AAD info provided by you.

@rdiazel : Thanks for your contribution! The author, @priyamohanram, has been notified to review your proposed change.

@rdiazel : Thanks for the PR. I have updated the documentation to include a table entry for Azure AD Basic. Hopefully this makes it clearer. Please feel free to open an issue if you have any further questions. Thank you!
#please-close


API reference refactor

API reference refactor

split up API reference docs into separate pages
reorganize endpoint structure into functionalities
replace main with index page
update redirects
removed Peon because chat should not be documented

### Peon

`GET /druid/worker/v1/chat/{taskId}/rowStats`

Retrieve a live row stats report from a Peon. See [task reports](../ingestion/tasks.md#task-reports) for more details.

`GET /druid/worker/v1/chat/{taskId}/unparseableEvents`

Retrieve an unparseable events report from a Peon. See [task reports](../ingestion/tasks.md#task-reports) for more details.

Preview: https://druid-puce.vercel.app/docs/api-reference/api-reference.html
This PR has:

[x] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[ ] added documentation for new or modified features or behaviors.
[ ] a release note entry in the PR description.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[ ] been tested in a test Druid cluster.

@vogievetsky PTAL

This is a really great cleanup. One small note: I would like to propose a better order for the HTTP API list
Instead of

How about:
Druid SQL
SQL-based ingestion
JSON querying
Tasks
Supervisors
Retention rules
Data management
Automatic compaction
Lookups
Service status
Dynamic configuration
Legacy metadata

Also note that I changed Supervisor => Supervisors to be consistent with Tasks


[fix issue #679]miss a situation in function get

if (is_null($redirectUri) && is_null($clientSecret))
@vinkla

Thanks for your contribution!
@lucadegasperi could you please check this. It is related to #679

why not make the redirectUri gettable in these situations?

Havn't checked yet?

Thanks for your pull request but this package should now be considered deprecated in favour of Laravel Passport.


DevDojo Auth breaks Jetstream's Teams support

Describe the bug
On a new Jetstream application (with "Teams" support enabled) registering a new User does not automatically create its own Team.
To Reproduce

Create a new Jetstream app (following Jetstreams docs)
1.1  Run composer create-project laravel/laravel example-app
1.2 Run cd example-app
1.3 Run composer require laravel/jetstream
1.4 Run php artisan jetstream:install livewire --teams

At this point, on the /register view, when a new User is registered, a new Team for the registered User is also created in the teams table.

Install Dev Dojo's Auth package for Jetstream app (following the docs)
2.1 Install the Auth Package
2.2 Publish the Fortify config
2.3 Enable the Name Field for Registration

Go through the Register user flow.

Expected behavior
After submitting the Register form in /register:

The user is redirected to the /login view.
User can login with their credentials, and land on the Dashboard which Displays their personal Team and User at the top right corner.

Actual behavior
After submitting the Register form in /register:

The user receives an Internal Server Error.

ErrorException
Attempt to read property "name" on null

This is due to the Team (teams table) not being created along with the User, then the navigation-menu tries to access the Team's Name and crashes the app.

Screenshots

System Details

OS: MacOS 14.5 (23F79)
Browser: Chrome 128.0.6559.0 (Official Build) dev (arm64)
Auth Version: "^1.0" (1.0.3)
PHP: 8.3

I think the current behavior is expected to not have any team. You can simply create the team by adding a new Listener to the Illuminate\Auth\Events\Registered Event.

Right, if we just do php artisan jetstream:install livewire then install DevDojo/Auth and register a new User all is good (there are no Teams involved here).
The part i'm not following is that installing php artisan jetstream:install livewire --teams automatically will create a Team for each new User. But if you install DevDojo/Auth then it interferes with the Team creation, only the User will be created.
Does that make sense?

When JetStream is installed with --teams, it uses an action to create each user, which automatically creates a "personal" team for them.
As such, JetStream assumes all users belong to at least one team.
You can either:

Make it so that DevDojo creates a personal team in a similar way; or,
Automate/instruct developers to make amendments to files (generated by JetStream stubs) so that they are able to support users with empty teams(), and with currentTeam being null.

I think it would be good to solve this by adding similar "switch" when installing DevDojo Auth, to enable Teams (or not).
This way, other features can be attached (in the future) to the Teams implementation that aren't useful to non-Teams e.g:

Customised creation of users (like above)
Customised authentication per Team
Inclusion of Middleware that can be used to protect Teams routes, e.g. for Corporate sign on rather than Social sign on.
etc

And most importantly, keeps non-Teams apps cruft-free.

I'm also facing this issue. It is better to add this to the installation guide with the Jetstream app. When users register it is always better to create a personal team.


It requires grad clip in original paper which seems to be ignored in this implementation.

I think the author used gradient penalty instead of gradient clip during implementation .

This is an improvred version of the original paper where clipping was required.


feat: add tap-next-press

This addresses the question I posed in https://github.com/kmonad/kmonad/discussions/656.
tap-next-press acts just like tap-next-release, except that it acts as hold on key presses rather than on key releases.
I suppose there could be one or two more functions added to fill out the matrix with hold and such, but I'd rather find out whether this has a decent chance of getting merged before I implement those, since I don't personally have a use for them.

Thanks @slotThe, I've added documentation

Great, thanks!


Crash with  java.lang.IllegalStateException: Error: Placement happened before lookahead.

Something is wrong:
this is my some code in Chat List:
@Composable
fun ClickableMessage(
    message: MessageEntity,
    isUserMe: Boolean,
    authorClicked: (String) -> Unit
) {
    MarkdownText(
        markdown = message.content,
        style = MaterialTheme.typography.bodyLarge.copy(color = LocalContentColor.current),
        modifier = Modifier.padding(16.dp),
        linkColor = MaterialTheme.colorScheme.onPrimary
    )
}

open the chat page，Crash immediately
this is log:
log.txt

hello

Hi @ak-ing
Could you help me sharing these info:

compose-markdown version
AGP version
Compose version
Android OS version

compose-markdown version：0.5.2
AGP version：8.3.2
Compose version：composeBom = "2024.05.00"
it is like androidx.compose.runtime:runtime-android:1.7.0-beta01
OS version：Android13


Res add will be included when evaluate Resnet's OPs ?

Hi, deer auther,
I wonder if thop will count residual connection's OPs (Add OP) when profiling resnet ?
Thanks

@hollyaoyaozi Try to use torch-operation-counter since it wrap the native pytorch operations (including add operation).


Test packages

Add unit tests to packages has always been very hard on concrete5.
What about adding support to this?
I think that it would require a bootstrap script that creates performs a clean installation of concrete5 (a kind of elemental_blank StartingPointPackage but without dashboard pages, gathering, themes, jobs, content...) in a brand new environment (that is, a new database, a new application directory).
That bootstrap script could be inspired by parts of the current core tests bootstrap file and the CLI install script.
Thoughts?

This is an interesting idea.

You can make this work today by using concrete5/core as a composer requirement and starting up a CLI runtime. The only thing it doesn't do is bootstrap an installation but IMO you should be able to fully unit test a package without installing concrete5.
That said, you're right that integration testing things like installing a package and singlepages and adding blocks and all that would be extremely useful. I think if we are going to do this, we should perhaps think about doing it in a separate composer package (since anyone doing this should be aware of composer and should be able to pull it down with a little bit of instructions).
That way we can have a fresh platform to build tests in a modern way without being held back by concrete5's default tests that are pretty old and slow. And we can learn a few things and bring them back to the main repo as well. I've seen a lot of testing suites lately that look a lot cleaner and more appealing than what we have in the core and I'd be pretty happy to get a chance to work on bringing that to our community.

I did some tests and indeed composer opens a whole new world of possibilities!
BTW we often need an installed instance of concrete5.


feat(node-v20): Bump deps: Node.js 20.x

call actions/setup-node@v4 with npm cache builtin, no need to call another caching layer;
resolves #3622

closed in #3717


Regr Test Repetition Visualization

Proposed changes:

...

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

/modeltest
num_repetitions: 5
include:
 - dataset: ["financial-demo"]
   config: ["Sparse + BERT + DIET(seq) + ResponseSelector(t2t)"]


Bundling edits

Adds

Builds for CommonJS, UMD, and ESModules.

ESModules: This will allow build systems to use the module: ... field in package.json (not well-documented as it's still an NPM proposal, but bundlers recognize it) to upgrade to ESModules. This allows for tree-shaking (dead code elimination) on imported modules (e.g. "I want to use APIClient in the front-end, but not Openlaw").
UMD: A umd build will be placed on https://unpkg.com/ on npm publish (unpkg.com/:package@:version/:file).
CommonJS: Basically for Node, and for old bundlers who will not upgrade to module: ... in package.json

Everything should remain functional.
Updates

sbt-scalajs -> 0.6.26
Changes the module format for client.js to export a modern esmodule
Package updates for babel
General package updates
Cleanup for config files where the settings did not apply to our build
Moves type Template into APIClient
Exports APIClient as esmodule
Updates entry point exports
Removes babel-polyfill in favor of a babel-runtime, so that there are no conflicts with consuming packages. We will need to put back babel-polyfill (or use Babel builtins) in areas of openlaw app where we have removed them so those bundles continue to work on older browsers

Removes

Dead code in config and APIClient.js
js/src/shared-types.js,  openlaw.webpack.config.js, libs.webpack.config.js

@Jdville03 I'll leave you to the version bump commit

@Jdville03 mentioned the esm build does not work with esmodules outright in the browser environment. I will fix that. Marking this as "[WIP]". If we can get that fixed, a user will have many ways to include our lib!

dist/
  cjs/
    openlaw.js // package.json "main: ...", for commonJS (node, webpack for browser if required)
  umd/
    openlaw.js // include in <script> via https://unpkg.com
  esm/
    index.esm.js // ALL files, include in <script> via https://unpkg.com
    apiclient.esm.js // include in <script> via https://unpkg.com
    openlaw.esm.js // include in <script> via https://unpkg.com

    // Babel-ified, minified files, but unbundled. They are meant to be used by bundlers
    lib/
      index.js // package.json "module: ...", Allows for tree-shaking (dead-code elimination) in bundlers.
      openlaw.js
      apiclient.js


Update data README.md to discuss NCDB

Currently there are no instructions for NCDB.

resolved by 7a7377b


QDK ver fix.

Addendum for #787.

@tcNickolas, I'm not sure. I updated for consistency, by example of the other repos.


Displays the number of items in the translation of a language

Just for information: have the number of items in the translation of a language displayed on the language map (page: list of languages)

I had a little trouble counting the total number of translations in one language, but finally it works. The total is displayed in the format of the translated language.

The problem is always there. R0.3 is currently undergoing refactoring and UTs on the api. I hope the problem will be fixed.


Bug: Navbar Inconsistency

What happened?
In Navbar when clicked on Home it remains purple when user is in home and when click on project its color is white similar to docs. It is In-Consistency. We can either make other section purple or make home section white when clicked. Sharing proofs
Add screenshots
Home Section [ See Navbar Color of Home ]

Project Section [ See Navbar Color of Project ]

Docs Section [ See Navbar Color of Docs ]

What browsers are you seeing the problem on?
No response
Record

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

@Harshu467 we need to add the active link purple. assigned

Hello, is this issue still open ?


Ansible lightspeed

Summary
When I press the ansible button to log on to my GitHub account a get an error "unable to parse decrypted password".
Currently using ansible 2.15.1

Extension version
Ansible
VS Code version
Version: 1.79.2
Ansible Version
ansible [core 2.15.1]
  config file = /Users/nadiofortunato/Desktop/Automation/playbooks/ansible.cfg
  configured module search path = ['/Users/nadiofortunato/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /opt/homebrew/lib/python3.11/site-packages/ansible
  ansible collection location = /Users/nadiofortunato/.ansible/collections:/usr/share/ansible/collections
  executable location = /opt/homebrew/bin/ansible
  python version = 3.11.1 (main, Dec 23 2022, 09:28:24) [Clang 14.0.0 (clang-14<IP_ADDRESS>)]<EMAIL_ADDRESS>  jinja version = 3.1.2
  libyaml = True

OS / Environment
Mac OS Ventura
Relevant log output
Unable to parse decrypted password

@nadiofortunato This is any issue in your environment. Open the keychain Access search and delete the vscode ansible related passwords. After that retry to login.


Trying to use "unstable-functions-support" and getting error "ReferenceError: fs is not defined"

Trying to get unstable functions support to work with Agility CMS's NextJS implementation for Preview mode and ISR.
This is the repo (trying to build a specific branch): https://github.com/agility/agility-nextjs-blog-ts/tree/animations
Latest deploy details:
https://app.netlify.com/sites/kind-perlman-97c6e9/deploys/606cb374152bea0008446d6a
Here's the deploy summary from netlify:
Plugin "@netlify/plugin-nextjs" internal error

ReferenceError: fs is not defined

In "onPostBuild" event in "@netlify/plugin-nextjs" from netlify.toml and package.json
at /opt/build/repo/node_modules/@netlify/plugin-nextjs/helpers/copyUnstableIncludedDirs.js:15:7
at Array.forEach ()
at copyUnstableIncludedDirs (/opt/build/repo/node_modules/@netlify/plugin-nextjs/helpers/copyUnstableIncludedDirs.js:14:17)
at onPostBuild (/opt/build/repo/node_modules/@netlify/plugin-nextjs/index.js:69:5)
at async Object.run (/opt/buildhome/.netlify-build-nvm/versions/node/v12.16.3/lib/node_modules/@netlify/build/src/plugins/child/run.js:18:3)
at async handleEvent (/opt/buildhome/.netlify-build-nvm/versions/node/v12.16.3/lib/node_modules/@netlify/build/src/plugins/child/main.js:36:38)
at async process. (/opt/buildhome/.netlify-build-nvm/versions/node/v12.16.3/lib/node_modules/@netlify/build/src/plugins/ipc.js:103:16)

If you're using file-based installation

netlify.toml:

[build]
  command   = "yarn build"
  publish = "out_publish"
  functions = "out_functions"

[[plugins]]
  package = "@netlify/plugin-nextjs"

next.config.js

module.exports = {
	target: "serverless",
	future: {
		webpack5: false,
	},
	unstableNetlifyFunctionsSupport: {
		'pages/[...slug].tsx': {
			includeDirs: ['./.next/cache/agility']
		},
		'pages/index.tsx': {
			includeDirs: ['./.next/cache/agility']
		}
	}
}

Let me know if you need any other details!

In case it helps, here's my package.json
{
  "name": "agility-nextjs-blog",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "predev": "agility-next sync",
    "dev": "next dev",
    "prebuild": "agility-next prebuild",
    "build": "next build",
    "export": "next export",
    "postbuild": "agility-next postbuild",
    "start": "next start",
    "cms-pull": "agility-next sync",
    "cms-clean": "agility-next clean"
  },
  "dependencies": {
    "@agility/content-sync": "^1.0.1",
    "@netlify/plugin-nextjs": "git://github.com/netlify/netlify-plugin-nextjs.git#unstable-functions-support",
    "framer-motion": "^4.0.0",
    "next": "^10.0.9",
    "react": "17.0.1",
    "react-dom": "17.0.1"
  },
  "devDependencies": {
    "@agility/nextjs": "^0.1.8",
    "@tailwindcss/jit": "^0.1.1",
    "@tailwindcss/typography": "^0.4.0",
    "@types/node": "^14.14.35",
    "@types/react": "^17.0.3",
    "autoprefixer": "^10.2.5",
    "postcss": "^8.2.8",
    "tailwindcss": "^2.0.3",
    "truncate-html": "^1.0.3",
    "typescript": "^4.2.3"
  }
}

@joelvarty hey! we just discussed this on twitter but for anyone reading through issues - this is due to a missing require in the branch and is currently in the process of being fixed along with a refactor. i'm going to close for now since the issue is resolved locally in the refactor and will be released soon when the temporary unstable solution gets merged into main. 🙏


Typescript build: Cannot find name 'Element'

Hi, I've installed both mixpanel and @types/mixpanel package but when I try to do my build with tsc I get these errors:
node_modules/@types/mixpanel/index.d.ts:629:27 - error TS2304: Cannot find name 'Element'.

629     type Query = string | Element | Element[];
                              ~~~~~~~

node_modules/@types/mixpanel/index.d.ts:629:37 - error TS2304: Cannot find name 'Element'.

629     type Query = string | Element | Element[];
                                        ~~~~~~~

This is the Mixpanel SDK for Node.js. The 3rd-party type definitions that you installed are for the Mixpanel browser SDK. If you're trying to use mixpanel-node, the type definitions are installed with the lib: https://github.com/mixpanel/mixpanel-node/blob/master/lib/mixpanel-node.d.ts


Drop Node6

When we were releasing in 2017, Node 6 was used by default on AWS and Google Cloud.
Node6 support doesn't come for free:

Since Puppeteer operates in two contexts - browser and node.js - common transpilers cannot handle Puppeteer transpilation. We implemented a custom one and maintain it occasionally.
Since our code is so different for Node6 wrt Node8, we have to maintain a separate CI for it
We ship both transpiled and non-transpiled versions of Puppeteer code to npm - more than doubling package size
There are occasional issues with Node6 here and there, e.g. https://github.com/GoogleChrome/puppeteer/issues/3455.
Certain features like "async stacks" don't work with Node6 at all.

Nowadays, both AWS and Google Cloud support Node 8, so Node 6 doesn't look like a must for us.
Node6 is getting end-of-lifed in April 2019, but I'm starting this thread to see if we can drop Node6 support earlier to cut on our overall complexity. Feel free to jump in and let us know what you think.

@ebidel, @JoelEinbinder: let me know what you guys think.

Since node moved to 10.x as LTS, I think supporting the last two LTS's is "enough".  Maybe just make a note on the troubleshooting page as to what the last version supporting node 6.x was.

I'm fine with dropping node 6 given most of the big providers offer node 8 options.
Good idea @jasonswearingen.

I’m fine with dropping it at 2.0.