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

Expected Behavior

The __hash__ methods should not be implemented like this:

def __hash__(self) -> int:
    return hash((id(self), self.name))

Objects with the __hash__ method implemented in such a way are not being deduplicated correctly in e.g. sets and dicts.

Current Behavior

Steps to reproduce

Specifications

• Version:
• Platform:
• Subsystem:

sklearn.utils are meant to be used internally within the scikit-learn package. They are not guaranteed to be stable between versions of scikit-learn. So depending on this submodule may limit cleanlab compatibility across sklearn versions.

Would not be too much work to replace the few cleanlab functions currently being

On more advanced versions of LakeFS (probably > = v1.0.0), we would like to remove the logic that tries to fill the generation field in DB when loading old dumps. It means we will no longer support loading dump that made with a version lower than v0.61.0.

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

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.

Describe the bug
Currently, we have places in project where paged responses are returned with hardcoded hasNext and total properties. Need to fix this and return valid values to frontend. Frontend need to use these values instead of current solution

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