You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/09/09 17:30:00 UTC

[jira] [Commented] (AIRFLOW-3012) Email on sla miss is send only to first address on the list

    [ https://issues.apache.org/jira/browse/AIRFLOW-3012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16608514#comment-16608514 ] 

ASF GitHub Bot commented on AIRFLOW-3012:
-----------------------------------------

kaxil opened a new pull request #3869: [WIP][AIRFLOW-3012] Fix SLA Emails
URL: https://github.com/apache/incubator-airflow/pull/3869
 
 
   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 `git diff upstream/master -u -- "*.py" | flake8 --diff`
   

----------------------------------------------------------------
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:
users@infra.apache.org


> Email on sla miss is send only to first address on the list
> -----------------------------------------------------------
>
>                 Key: AIRFLOW-3012
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3012
>             Project: Apache Airflow
>          Issue Type: Bug
>    Affects Versions: 1.9.0
>            Reporter: Marek Kowal
>            Assignee: Kaxil Naik
>            Priority: Major
>
> Description:
> I store email recipients as a variable, test_recipient: test1@test.com, [test2@test.com|mailto:test2@test.com]
> With such dag definition:
> {code:java}
> email = Variable.get("test_recipients")
> args = {
>     'owner': 'airflow'
>     , 'depends_on_past': False
>     , 'start_date': datetime(2018, 8, 20, 0, 0)
>     , 'retries': 0
>     , 'email': email
>     , 'email_on_failure': True
>     , 'email_on_retry': True
>     , 'sla': timedelta(seconds=10)
> }{code}
> On sla miss email is send only to the first person on the list, in my example [test1@test.com|mailto:test1@test.com]
> to reproduce:
> create email list variable as string and wait for sla miss



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)