warp.exe: <ERROR> delimiter must be a one-character string
kwit75 opened this issue · comments
just got this when running:
warp get --host=s3.us-west-002.xxx.com --access-key=XXXX --secret-key=XXXXX --tls=true --bucket=test-benchmark --autoterm --benchdata=./benchmark.csv
tried from Ubuntu (bin and docker) and Windows (bin/docker). Same issue.
This error stopped the benchmark data from being written FYI
It also happened when testing Backblaze B2. Perhaps they're missing part of the S3 API that causes this?
@austinpena-taloflow When you write "It also happened " does that mean it only happened on B2 or that it also happens on S3/MinIO servers?
I am pretty sure we only use / as delimiter.
the --secret parameter has '/' symbol inside of the password string. Could it be an issue? should I escape it somehow?
the --secret parameter has '/' symbol inside of the password string. Could it be an issue? should I escape it somehow?
This looks like an implementation issue perhaps some parsing issue with B2
@kwit75 @austinpena-taloflow Please provide useful information, what are you running (commandline), against which hosts, what is the exact output?
With just an error message that AFAICT doesn't come from warp itself, but from the remote host, there is nothing I can do.
@kwit75 Will shed more light on it, but the issue doesn't stop the benchmark from running, only the CSV from being produced.
When you write "It also happened " does that mean it only happened on B2 or that it also happens on S3/MinIO servers?
The benchmark ran without issues on B2. On S3 it works.
This looks like an implementation issue perhaps some parsing issue with B2
The test gets run, but the CSV had an issue. Can you expand on what happened with the CSV @kwit75?
Testing on Windows I don't see any issues with what you provide:
λ warp put --duration=10s --obj.size=1K --host=127.0.0.1:{9001...9002} --access-key=minio --secret-key=minio/123 --benchdata=./benchmark.csv
warp: Benchmark data written to "./benchmark.csv.csv.zst"
[...]
(yes, there is a slash in the secret key)
@klauspost this issue is B2 related unrelated to the tool - B2 is failing Listing() during cleanup.
@harshavardhana It is still a bit up in the air what the problem is
The benchmark ran without issues on B2. On S3 it works.
So still not sure what the issue it. The error does indicate a serverside problem.
So still not sure what the issue it. The error does indicate a serverside problem.
The error actually happens at the end of the run @klauspost mostly during cleanup. The error is an error returned by ListObjects when delimiter=two-characters
However this is not a requirement in AWS S3 to have delimiter=<more-than-one-character>
But we don't send 2 character delimiters. We don't even send one for the ListObjects call.
Either way, this is pointless without any info. Closing.