[
https://issues.apache.org/jira/browse/AIRFLOW-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709011#comment-16709011
]
ASF GitHub Bot commented on AIRFLOW-3217:
-----------------------------------------
Eronarn opened a new pull request #4277: [AIRFLOW-3217] Airflow log view and
code view should wrap
URL: https://github.com/apache/incubator-airflow/pull/4277
### Jira
- [x] My PR addresses the following [Airflow
Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues:
https://issues.apache.org/jira/browse/AIRFLOW-3217
### Description
- [x] Here are some details about my PR, including screenshots of any UI
changes:
DAG code view before/after:
Log view before/after:
### Tests
- [x] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason: it's css
### Commits
- [x] 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"
----------------------------------------------------------------
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]
> Airflow log view and code view should wrap
> ------------------------------------------
>
> Key: AIRFLOW-3217
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3217
> Project: Apache Airflow
> Issue Type: Bug
> Components: logging
> Affects Versions: 1.10.0
> Reporter: James Meickle
> Priority: Minor
>
> Being able to look at logs and code in Airflow is great, but the Kubernetes
> operator in particular makes very long loglines. For example, a pod log might
> have something like this:
>
> `{{[2018-10-16 10:32:38,195] {{logging_mixin.py:95}} INFO - [2018-10-16
> 10:32:38,195] {{pod_launcher.py:95}} INFO - b'[2018-10-16 10:32:38.190104]
> INFO:`}}
>
> ...and that's before any log text! Since there is no wrapping or navigation
> on this screen, it's very challenging to make use of these logs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
