This issue tracks Superset's migration from JavaScript to TypeScript (as started in SIP-36). If you'd like to help with the migration, feel free to take an unchecked directory and convert the files within the immediate directory from JavaScript/JSX to TypeScript/TSX. #9162 and #9180 provide some tips for performing the migration. Once com

Description

I just run MySQLFetch task:

mysql = MySQLFetch(
        host="...",
        port=3306,
        db_name="...",
        user="...",
        password="...",
        query="SELECT * FROM ... LIMIT 1"
    )
mysql.run()

And I get this:

Traceback (most recent call last):
  File "/Users/danielnuriyev/simplisafe/scripts/lib/python3.8/site-packages/IPython/core/int

Describe the bug
This is basically one of the issues I called out in #1855:
When I run datasource new and exit the process at any point (e.g. ctrl+c), I still get a block for the credentials in config_variables.yml. However great_expectations.yml doesn't have the datasource entry. I would expect any kind of failure in the datasource creation process to not leave any artifacts.

**To Re

Brief Description of Fix

Currently, the docstrings for some functions are lacking a return description and (where applicable) a raises description.

I would like to propo

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

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;

Pivot missing categories breaks FeatureSet/AggregatedFeatureSet

Summary

When defining a feature set, it's expected that pivot will have all categories and, as a consequence, the resulting Source dataframe will be suitable to be transformed. When a different behavior happens, FeatureSet and AggregatedFeatureSet breaks.

Feature related:

Age: legacy