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

From community slack: https://prefect-community.slack.com/archives/CL09KU1K7/p1599551263372600

From that slack comment:

_I am trying to run a DbtShellTask with a dynamic set of dbt_kwargs that are defined at run time. The task works when I define the dbt_kwargs in the task initialization, but not when they are provided at runtime.

Looks like the dbt_kwargs needs an em

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

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;

Is there any way to write the Historical and Online feature stores directly in the hdfs?

Summary

I would like to write the Historical and Online feature stores in two different hdfs paths, using the parquet format.
I've tried use the S3Config class to do it, but not works..