data-quality

Describe the bug
data docs columns shrink to 1 character width with long query

To Reproduce
Steps to reproduce the behavior:

1. make a batch from a long query string
2. run validation
3. render result to data docs
4. See screenshot
   <img width="1525" alt="Data_documentation_compiled_by_Great_Expectations" src="https://user-images.githubusercontent.com/928247/103230647-30eca500-4

Currently the X argument of CleanLearning.fit() does not seem to support non-array data.
Perhaps this is due to the sklearn function check_X_y() called inside CleanLearning, which we could replace.
Or perhaps it's due to how the cross-validation is currently being implemented.

However these are both easy to improve to rid the restriction that only array data are supported.
Seems e

Is your feature request related to a problem? Please describe.
The Pydantic errors can be very annoying to debug when the error messages are not explicit or (as often seen) completely missing. I provide two specific examples bellow but many more can be found throughout the codebase.

Describe the solution you'd like
Always include explicit error messages to all Pydating validation chec

webui/src/lib/api/index.js

Summary

There is a typo in the output here: https://github.com/whylabs/whylogs/blob/mainline/src/whylogs/cli/demo_cli.py#L113

Also we can update this to better align with our examples and suggested use, e.g. we can remove prompting for 'project' and 'pipeline' since these aren't required, and streamline the script to simplify the demo experience.

What type of re_data dbt macro you would like to add

• validate

What macro should be doing

Return true is string is a valid JSON and can be parsed to JSON

Currently the registry tags are a dictionary format like this:

{"description":"this is a test feature"}

but user could easily do something else like

{"description", "this is a test feature"}

and the object will not be serialized as it's not a valid python dict. We should add a type check for that to avoid those kind of errors.

What is the feature request? What problem does it solve?

As employees leave the organization/company or users change mails , eventually the notification list configured for the job would start containing a lot of invalid mails. This causes issues with SMTP relay (e.g postfix) which could be buffering all invalid requests until the queu is full, which cause all mails coming for all jobs to b