schema

The title might seem a bit vague but I don't know how to describe it any better tbh :-)

Anyway this is what happened: I got some 500 responses from the schema registry and all I could see in the logs was :

[2020-04-02 16:03:35,048] INFO 100.96.14.58 - - [02/Apr/2020:16:03:34 +0000] "PUT /config/some-topic-value HTTP/1.1" 500 69  502 (io.confluent.rest-utils.requests)

The logs di

Describe the bug
pa.errors.SchemaErrors.failure_cases only returns the first 10 failure_cases

• I have checked that this issue has not already been reported.
• I have confirmed this bug exists on the latest version of pandera. 0.6.5
• (optional) I have confirmed this bug exists on the master branch of pandera.

Note: Please read [this guide](https://matthewrocklin.c

Here is an example of current error message:

The 'email_address' field must not be empty.

Is there a way to pass field label into schema so the error message is displayed like so:

The 'Email Address' field must not be empty.

I know we can use custom messages for each field but curious if there's a lazier approach here :)

Looks like it should be "Not all child routes satisfy compojure.api.routes/Routing."

Maybe a fix could use (str ::Routing) or some derivative

-Victor

We have a small number of e2e tests for kpt live (outside of the bash-based approach). They currently run in serial and requires that a new cluster is created for several of the tests. This causes them to be very slow.

We should improve this by:

• Reduce the number of times we need to create a new kind cluster, as this takes ~1 minute. Tests should clean up after themselves and we can handle

Add some validation checks for mongo operators that can't be done by SimpleSchema. See longshotlabs/meteor-simple-schema#9.

• $rename (make sure existing values for the renamed key validate for the new key name)
• $inc (check min/max and allowed values)
• $addToSet (check maxCount)
• $push (check maxCount)
• $pull (check minCount)
• $pullAll (check minCount)
• $pop (check min