-
Updated
Feb 9, 2022 - Java
scheduler
Here are 1,978 public repositories matching this topic...
-
Updated
Feb 24, 2022 - Java
-
Updated
Feb 23, 2022 - JavaScript
-
Updated
Feb 11, 2022 - Python
-
Updated
Feb 12, 2022 - C#
-
Updated
Feb 24, 2022 - Groovy
Right now, we've got this chunk of code:
def _columns_to_markdown(columns: Mapping[str, Any]) -> str:
return (
textwrap.dedent(
"""
| Name | Description |
| - | - |
"""
)
+ "\n".join([f"| {name} | {metadata['description']}" for name, metadata in columns.items()])
)
Instead of representing them with markdown, we
-
Updated
Jan 27, 2022 - Shell
-
Updated
May 16, 2021 - Ruby
-
Updated
Feb 24, 2022 - PHP
Is there a way to make a job re-occur N milliseconds after it finished previous time?
-
Updated
Feb 24, 2022 - TypeScript
-
Updated
Aug 23, 2021 - Java
-
Updated
Feb 24, 2022 - Ruby
-
Updated
Jan 21, 2022 - TypeScript
The tests fail sometimes due to millisecond based timing on some of the tests. I over optimized for local testing and it's causing tests to fail in CI occasionally. The CI pipeline is running in docker with limited resources, so not able to handle quite as precise time as my local machine.
-
Updated
Feb 24, 2022 - JavaScript
-
Updated
Feb 23, 2022 - Ruby
Improve this page
Add a description, image, and links to the scheduler topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the scheduler topic, visit your repo's landing page and select "manage topics."
Apache Airflow version
2.2.4 (latest released)
What happened
When triggering this dag below it runs when it should fail. A set is being passed to default_args instead of what should be a dictionary yet the dag still succeeds.
What you expected to happen
I expected the dag to fail as the default_args parameter should only be a dictionary.
How to reproduce