Presto DB is checked several times but it also means that
it is added several times to DISABLED_INTEGRATIONS in case
it is not enabled. This commit fixes it.
Seems that postgres is really stable when it comes to upgrades,
so we take the assumption that if we test 9.6 and 13, and they
work, all the versions between will also work.
This PR changes Postgres 10 to 13 in tests and updates documentation
with all the versions in between.
Example:
```python
{paused_dag_id for paused_dag_id, in paused_dag_ids}
```
Instead of
```python
set(paused_dag_id for paused_dag_id, in paused_dag_ids)
```
Missing a commit means that the the row level lock was not released
before `executor.heartbeat()` was called. This was only a problem for
the SequentialExecutor, as all the other executors would continue
running the scheduler code so the lock would be released shortly after
tasks are sent to the executor anyway. (Where as SequentialExecutor
doesn't return control until tasks have run!)
Resolves#11563. With the hover event triggering the tooltips, the tooltip was triggering a mouse-out event when the cursor was at the top of the circle (where the tooltip is presented). This was causing the fluttering behavior due to the looping off these events.
No functional changes, just visual enhancement of the variable import
form. This simply refactors the markup slightly to better utilize some Bootstrap
styling and add an icon to the button.
If you used context from git repo, the .piprc file was missing and
COPY in Dockerfile is not conditional.
This change copies the .pypirc conditionally from the
docker-context-files folder instead.
Also it was needlessly copied in the main image where it is not
needed and it was even dangerous to do so.
The packages lacked setup.py and they could not be installed.
This change automatically generates setup.py for the packages and
adds them to the packages.
Fixes: #11546
This is a follow up after #11659. Thanks to this one, it will
be immediately visible in CI which types of tests are run.
This change has been lost during one of the rebases, so it is
brought back now.
It was possible to "block" the scheduler such that it would not
schedule or queue tasks for a dag if you triggered a DAG run when the
DAG was already at the max active runs.
This approach works around the problem for now, but a better longer term
fix for this would be to introduce a "queued" state for DagRuns, and
then when manually creating dag runs (or clearing) set it to queued, and
only have the scheduler set DagRuns to running, nothing else -- this
would mean we wouldn't need to examine active runs in the TI part of the
scheduler loop, only in DagRun creation part.
Fixes#11582
..so that whenever the Airflow server restarts, it does not leave rogue ECS Tasks. Instead the operator will seek for any running instance and attach to it.
We've implemented the capability of running the tests in smaller
chunks and selective running only some of those, but this
capability have been disabled by mistake by default setting of
TEST_TYPE to "All" and not removing it when TEST_TYPES are set
to the sets of tests that should be run.
This should speed up many of our tests and also hopefully
lower the chance of EXIT 137 errors.
Jarek Potiuk
yangrong688
John Bampton
Ephraim Anierobi
Kamil Breguła
Kaxil Naik
Jed Cunningham
Ash Berlin-Taylor
Marian Cepok
Martijn Pieters
Ryan Hamilton
Darwin Yip