clawbot
8b22ae8d42
check / check (push) Waiting to run
s3.part_size was loaded and defaulted but never reached the S3 client, whose uploader used a fixed 10MiB part. The client now takes the part size from the config, for storage_url and for the s3.* fields, and config load rejects a value below 5MiB or above 5GiB, an explicit 0 included. A blob too large for S3's limit of 10,000 parts at that size is uploaded in larger parts, since the uploader cannot learn the size of the reader it is given. The docs gave the default as 5MB, which the config file reads as 5,000,000 bytes, below the minimum; they now say 5MiB. Judgement call: the 5GiB maximum is enforced along with the 5MiB minimum the issue names. Model: opus-5-5
28 lines
709 B
YAML
28 lines
709 B
YAML
age_recipients:
|
|
- age1278m9q7dp3chsh2dcy82qk27v047zywyvtxwnj4cvt0z65jw6a7q5dqhfj # sneak's long term age key
|
|
- age1ezrjmfpwsc95svdg0y54mums3zevgzu0x0ecq2f7tp8a05gl0sjq9q9wjg # add additional recipients as needed
|
|
snapshots:
|
|
test:
|
|
paths:
|
|
- /tmp/vaultik-test-source
|
|
- /var/test/data
|
|
exclude:
|
|
- '*.log'
|
|
- '*.tmp'
|
|
- '.git'
|
|
- 'node_modules'
|
|
s3:
|
|
endpoint: https://s3.example.com
|
|
bucket: vaultik-test-bucket
|
|
prefix: test-host/
|
|
access_key_id: test-access-key
|
|
secret_access_key: test-secret-key
|
|
region: us-east-1
|
|
use_ssl: true
|
|
part_size: 5242880 # 5MiB
|
|
index_path: /tmp/vaultik-test.sqlite
|
|
chunk_size: 10MB
|
|
blob_size_limit: 10GB
|
|
compression_level: 3
|
|
hostname: test-host
|