Currently, we use Native filter on Superset version 1.2, but looks like The actual time range does not show correctly with SIP-15 (in the SIP-15 the time range must is [inclusive, exclusive) ). So that mean the actual time range and the tool tip must show label as: from_date <= col < to_date.

Expected results

![image](https://user-images.githubusercontent.com/37523968/130939207-7ff847a

Opened from the Prefect Public Slack Community

michael.ball: Hey there. I’ve been playing around with Docker storage today, trying to get all source code packaged together with the flows each time they are registered, and am using the files and env_vars attributes as outlined in the Docs. But it seems that my .dockerignore file (in the directory from whic

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

User request:

Can we open a ticket to add a recursive flag? It's not too hard to go through the S3 gateway but it requires setting up another profile for the AWS credentials, and people will have to install the AWS cli as well

https://lakefs.slack.com/archives/C016726JLJW/p1630673917035600?thread_ts=1630603335.022500&cid=C016726JLJW

if they are not class methods then the method would be invoked for every test and a session would be created for each of those tests.

`class PySparkTest(unittest.TestCase):
@classmethod
def suppress_py4j_logging(cls):
logger = logging.getLogger('py4j')
logger.setLevel(logging.WARN)

@classmethod
def create_testing_pyspark_session(cls):
    return Sp

Brief Description of Fix

When I see docs I found [get_features_targets page](https://pyjanitor-devs.github.io/pyjanitor/reference/janitor.functions/janitor.get_features_targe

If ploomber scaffold finds a pipeline.yaml if checks all tasks[*].sources and creates files for all tasks whose source is missing. e.g.,

tasks:
    - source: some_module.some_function
      product: output.csv

If some_module.py exists, ploomber scaffold adds a function definition there. However, if it doesn't, it fails.

Calling the command should create all neces

In the repository handler

• removeEntity tries to delete then if delete is not supported issues a purge, the purge method issues an audit log
• There are 2 callers to purgeRelationship only one of which audit logs

This is inconsistent.
I suggest we move the relationship audit log to the purge method, which means that both callers will audit log.