At some point we moved from using mocha as a test runner to using jest, and jest out of the box started reporting much more warnings than mocha did.

No one went to clean up this output. In many cases it may just be about passing an extra prop in a component or setting a proper default value for a component's prop, or adding up to an existing fixture.

[optional] please roll out in chu

Current behavior

Currently Prefect provides no code examples on how to use the different Kubernetes Tasks.

Proposed behavior

Provide generic examples for the different Kubernetes Tasks for at least one kind of API.

Deployments

• CreateNamespacedDeployment
• DeleteNamespacedDeployment
• ListNamespacedDeployment
• PatchNamespacedDeployment
• ReadNamespacedDeployment
• R

We’ve been seeing a lot of great work to build and convey patterns for how to use Great Expectations across the primary cloud platforms, but we don’t currently have an implementation of the TupleStoreBackend for Microsoft Azure.

I believe an implementation of that backend would help many users, and would be directly analogous to the implementations of TupleGCSStoreBackend and `TupleS3StoreBa

Brief Description

Following up on #703, this issue seeks to introduce the ability to test whether in each column in a data frame the change between every two rows is within a user-defined range of values.

I would like to propose..

Example API

import pandas as pd
import numpy as np

# Create a random data frame
df = pd.DataFrame(data=[["2015-01-01 00:00:00", -0.76, 2, 2, 

In SubjectAreaRESTServicesInstance, it hard codes the default page size as 0, this is not correct

public static final String PAGE_SIZE_DEFAULT_VALUE = "0";
it should be changed to
public static final String PAGE_SIZE_DEFAULT_VALUE = "1000";

So it is consistent with OMAGServerConfig default
private static final int defaultMaxPageSize = 1000;