[
https://issues.apache.org/jira/browse/AIRFLOW-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16698276#comment-16698276
]
ASF GitHub Bot commented on AIRFLOW-1823:
-----------------------------------------
xnuinside opened a new pull request #4237: [AIRFLOW-1823] added possibility to
send execution date with millisec…
URL: https://github.com/apache/incubator-airflow/pull/4237
…onds to task_instance_info REST API endpoint
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-1823\] My Airflow PR"
- https://issues.apache.org/jira/browse/AIRFLOW-1823
- 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:
added compatibility with UI triggered DAGs
checked:
<img width="910" alt="screen shot 2018-11-25 at 23 19 59"
src="https://user-images.githubusercontent.com/15959809/48984139-260a2980-f109-11e8-95cb-31b8bc1998d1.png";>
### 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]
> API get_task_info is incompatible with manual runs created by UI
> ----------------------------------------------------------------
>
> Key: AIRFLOW-1823
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1823
> Project: Apache Airflow
> Issue Type: Bug
> Components: api
> Affects Versions: 2.0.0
> Environment: ubuntu
> Airflow 1.9rc02
> commit:
> https://github.com/apache/incubator-airflow/blob/master/airflow/www/api/experimental/endpoints.py#L126
> Reporter: Jeremy Lewi
> Assignee: Iuliia Volkova
> Priority: Minor
>
> The API method
> [task_instance_info|https://github.com/apache/incubator-airflow/blob/master/airflow/www/api/experimental/endpoints.py#L126]
> doesn't work with manual runs created by the UI.
> The UI creates dag runs with ids with sub second precision in the name. An
> example of a run created by the UI is
> 2017-11-16T20:23:32.045330
> The endpoint for
> [task_instance_info|https://github.com/apache/incubator-airflow/blob/master/airflow/www/api/experimental/endpoints.py#L126]
> however assumes the dag run id is of the form '%Y-%m-%dT%H:%M:%S'.
> Runs triggered via the CLI generate run ids with the form expected by the API.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
![https://user-images.githubusercontent.com/15959809/48984139-260a2980-f109-11e8-95cb-31b8bc1998d1.png"](https://user-images.githubusercontent.com/15959809/48984139-260a2980-f109-11e8-95cb-31b8bc1998d1.png"){kind=link}