[
https://issues.apache.org/jira/browse/AIRFLOW-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16659408#comment-16659408
]
ASF GitHub Bot commented on AIRFLOW-3234:
-----------------------------------------
ajbosco opened a new pull request #4078: [AIRFLOW-3234] add
dagbag_import_failure_handler
URL: https://github.com/apache/incubator-airflow/pull/4078
Make sure you have checked _all_ steps below.
### Jira
- [ ] My PR addresses the following [Airflow
Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references
them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
- https://issues.apache.org/jira/browse/AIRFLOW-XXX
- In case you are fixing a typo in the documentation you can prepend your
commit with \[AIRFLOW-XXX\], code changes always need a Jira issue.
### Description
- [ ] Here are some details about my PR, including screenshots of any UI
changes:
### Tests
- [ ] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
### Commits
- [ ] My commits all reference Jira issues in their subject lines, and I
have squashed multiple commits if they address the same issue. In addition, my
commits follow the guidelines from "[How to write a good git commit
message](http://chris.beams.io/posts/git-commit/)":
1. Subject is separated from body by a blank line
1. Subject is limited to 50 characters (not including Jira issue reference)
1. Subject does not end with a period
1. Subject uses the imperative mood ("add", not "adding")
1. Body wraps at 72 characters
1. Body explains "what" and "why", not "how"
### Documentation
- [ ] In case of new functionality, my PR adds documentation that describes
how to use it.
- When adding new operators/hooks/sensors, the autoclass documentation
generation needs to be added.
### Code Quality
- [ ] Passes `flake8`
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Enable alerting for dagbag import errors
> ----------------------------------------
>
> Key: AIRFLOW-3234
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3234
> Project: Apache Airflow
> Issue Type: Improvement
> Reporter: Adam Boscarino
> Assignee: Adam Boscarino
> Priority: Minor
>
> If a task fails due to being unable to load the DagBag it is set to `failed`
> without being able to use callbacks or retries. This creates the possibility
> for "silent" failures. We should have the ability to handle these failures
> with some other functionality (similar to the SLA callbacks).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
