karapace

karapace copied to clipboard

# What happened? ``` POST to https://karapace/topics/mytopic { "key_schema": "{\"type\":\"string\"}, "value_schema": "{\"fields\":[{\"name\":\"updated\",\"type\":{\"logicalType\":\"timestamp-millis\",\"type\":\"long\"}}],\"name\":\"x\",\"type\":\"record\"}", "records": [ { "key": "14535018", "value": { "updated": 166445827700 } } ] } ``` gives the error ```...

perj

Check compatibility API does not support verbose mode

1

# What happened? The check compatibility of a schema API does not support verbose mode. When using the Confluent Schema Registry client against Karapace, this makes the call to the...

charlescd

Add a dev target to Dockerfile, add a dev compose file

7

# About this change - What it does - Add a dev target to Dockerfile which will install dev and static-check dependencies - Set up a volume that syncs local...

gpkc

When a user sends a bad schema, we return a 500 even though the error is handled. Here we return a 422 instead.

gpkc

# About this change - What it does References: #xxxxx # Why this way

matyaskuti

Bumps [pytest](https://github.com/pytest-dev/pytest) from 7.4.4 to 8.0.2. Release notes Sourced from pytest's releases. 8.0.2 pytest 8.0.2 (2024-02-24) Bug Fixes #11895: Fix collection on Windows where initial paths contain the short version...

dependabot[bot]

# About this change - What it does Run tests in a random order. Reproduce rest consumer failure in random order: `--random-order-bucket=global --random-order-seed=472073` (with process number 2) Reproduce unittest failure...

matyaskuti

Prometheus client metrics support

10

This code provides the option to use Prometheus for collecting statistics in Karapace. The branch is based on karapace-metrics branch.

libretto

fix: harden the order of keys that needs to be serialized

1

# Why this way Previously we were relying on the fact that the `.keys()` order and the `json.dumps()` order are always sync. This enforces by the `OrderedDict` a fixed order....

eliax1996

Error and connection reset by peer when trying to run against RedPanda

1

Running both redpanda and karapace (registry) in docker, I get this in the logs and the schema registry always returns "reset by peer": ``` 023-12-27 11:06:34 karapace.schema_reader schema-reader ERROR Unexpected...

genzgd