Bill Sorensen

One workaround is to use and mock the default axios instance; then calls to `request` can be mocked.

A coworker wondered what would happen if we sent two records, one good and one bad: --data '{"records":[{"key":"3984983","value":"Value 3984983"},{"value":"Value BAD"}]}' HTTP/1.1 200 OK {"offsets":[{"partition":null,"offset":null,"error_code":50003,"error":"Expiring 2 record(s) for topic-key-error-0:120001 ms has...

Even with multiple partitions and multiple records, it appears to be all-or-nothing: --data '{"records":[{"key":"B","value":"Value B2"},{"value":"Value BAD"}]}' HTTP/1.1 200 OK {"offsets":[{"partition":null,"offset":null,"error_code":50003,"error":"Expiring 2 record(s) for compact-multi-partition-0:120001 ms has passed since batch creation"},{"partition":null,"offset":null,"error_code":50003,"error":"Expiring...

@MarkC0x Thank you - we're in the process of moving off of the REST Proxy and we're no longer using compacted topics with it, so I no longer have a...

I likewise found this to be unexpected behavior. As those frequently come from query parameters (user input) when implementing pagination, this has security implementations. In the meantime, a workaround is:...

Just a +1 for adding a license. If you want to restrict commercial use, go with GPL or the more restrictive AGPL. If you don't, MIT is a popular choice....

We also see this, both in production and test environments. And it's not just Windows. Challenging to replicate though.

Thank you - I didn't find any examples currently, but I'll watch for them and grab that section of the YAML the next time it comes up.

We addressed the root cause, so these issues are rare now. When they do come up the pods are deleted before I have a chance to examine them. Here's an...

It happens some of the time, but relatively frequently. I just tried to replicate it with v1.8.1 and it was working fine for the first 2 loads and the third...