kafka

This happens occasionally when shutting down the server:

Exception in thread "http-worker-15" java.lang.NullPointerException: null value in entry: exception=null
        at com.google.common.collect.CollectPreconditions.checkEntryNotNull(CollectPreconditions.java:32)
        at com.google.common.collect.ImmutableMap.entryOf(ImmutableMap.java:176)
        at com.google.common.collect.I

Description

1. The theme change toggle's placement is incorrect as it is being placed at the most important place i.e. top left, ideally it should be place in the top right as it's not the highlight of the product.

2. There

https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/servicebus/Azure.Messaging.ServiceBus/MigrationGuide.md

I have a use case where I need to create a new stream containing the bearing between two consecutive points in a pre-existing lat/lon stream. Normally bearing would be available in a standard lib but in a pinch can easily be implemented through sin, cos, and atan2 funcs, none of which are currently available in ksql.

Basic trig functions have a range of use cases in geometric and geographic co

Under the hood, Benthos csv input uses the standard encoding/csv packages's csv.Reader struct.

The current implementation of csv input doesn't allow setting the LazyQuotes field.

We have a use case where we need to set the LazyQuotes field in order to make things work correctly.

I have this implemented in a custom marshaler now but wondering if it makes sense to push back upstream - when we are integrating with legacy services we find it useful to use the correlation ID as the message ID when first brought into watermill - from there they get sent on headers to subsequent services and work normally.

Its a simple change if it would make sense for other users.

Version & Environment

Redpanda version: (use rpk version):

v21.11.2 (rev f58e69b)

What went wrong?

Accessing the admin API at hostname:9644/v1 fails. On the browser, the request hangs for several minutes (dev tools shows it as a in-progress, waiting for more bytes), before eventually failing (timing out).

wget shows some kind of read error 6.5K into the response:

~~