-
```
Gridworks should fully support collaborative editing, including preventing
collisions and maintaining a full edit history.
A broker is being worked on to handle access to projects.
```
Original…
-
```
Gridworks should fully support collaborative editing, including preventing
collisions and maintaining a full edit history.
A broker is being worked on to handle access to projects.
```
Original…
-
```
Gridworks should fully support collaborative editing, including preventing
collisions and maintaining a full edit history.
A broker is being worked on to handle access to projects.
```
Original…
-
Read the FAQ first: https://github.com/confluentinc/librdkafka/wiki/FAQ
Do NOT create issues for questions, use the discussion forum: https://github.com/confluentinc/librdkafka/discussions
D…
-
Description
===========
The same SSL certificate provided to 'ssl.ca.pem' property as a verbatim string succeeds on MacOS and Windows but fails on Linux/Ubuntu to verify the Confluent Cloud kafka …
-
```
Gridworks should fully support collaborative editing, including preventing
collisions and maintaining a full edit history.
A broker is being worked on to handle access to projects.
```
Original…
-
```
Gridworks should fully support collaborative editing, including preventing
collisions and maintaining a full edit history.
A broker is being worked on to handle access to projects.
```
Original…
-
```
Gridworks should fully support collaborative editing, including preventing
collisions and maintaining a full edit history.
A broker is being worked on to handle access to projects.
```
Original…
-
```
Gridworks should fully support collaborative editing, including preventing
collisions and maintaining a full edit history.
A broker is being worked on to handle access to projects.
```
Original…
-
**Description**
#### After docker compose up
* ERROR broker=1 is storing logs in /tmp/kraft-combined-logs, Kafka expects to store log data in a persistent location (io.confluent.controlcenter.health…