[jira] [Created] (AIRFLOW-3051) The cli tools for manipulating users should be symmetric with connections
William Pursell created AIRFLOW-3051: Summary: The cli tools for manipulating users should be symmetric with connections Key: AIRFLOW-3051 URL: https://issues.apache.org/jira/browse/AIRFLOW-3051 Project: Apache Airflow Issue Type: Wish Affects Versions: 1.10.0 Reporter: William Pursell The ability to manipulate users from the command line is a bit clunky. Currently 'airflow create_user' and 'airflow delete_user' and 'airflow list_users'. It seems that these ought to be made more like connections, so that it becomes 'airflow users list ...', 'airflow users delete ...' and 'airflow users create ...' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRFLOW-3090) INFO logs are *way* too verbose
William Pursell created AIRFLOW-3090: Summary: INFO logs are *way* too verbose Key: AIRFLOW-3090 URL: https://issues.apache.org/jira/browse/AIRFLOW-3090 Project: Apache Airflow Issue Type: Wish Reporter: William Pursell info logging is so verbose that it is very difficult to find info. Many of the INFO logs should probably be DEBUG instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRFLOW-3090) INFO logs are too verbose
[ https://issues.apache.org/jira/browse/AIRFLOW-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Pursell updated AIRFLOW-3090: - Summary: INFO logs are too verbose (was: INFO logs are *way* too verbose) > INFO logs are too verbose > - > > Key: AIRFLOW-3090 > URL: https://issues.apache.org/jira/browse/AIRFLOW-3090 > Project: Apache Airflow > Issue Type: Wish >Reporter: William Pursell >Priority: Minor > > info logging is so verbose that it is very difficult to find info. Many of > the INFO logs should probably be DEBUG instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRFLOW-1690) Error messages regarding gcs log commits are sparse
William Pursell created AIRFLOW-1690: Summary: Error messages regarding gcs log commits are sparse Key: AIRFLOW-1690 URL: https://issues.apache.org/jira/browse/AIRFLOW-1690 Project: Apache Airflow Issue Type: Bug Components: logging Affects Versions: 1.9.0 Reporter: William Pursell Assignee: William Pursell Priority: Minor Whether there is a local error creating a temporary file, or a connection error, the log message reads: "Could not write logs to %s" % remote_log_location This is not enough information to debug an error. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AIRFLOW-1714) "Separated" is misspelled in admin/connections tab
William Pursell created AIRFLOW-1714: Summary: "Separated" is misspelled in admin/connections tab Key: AIRFLOW-1714 URL: https://issues.apache.org/jira/browse/AIRFLOW-1714 Project: Apache Airflow Issue Type: Improvement Components: ui Affects Versions: Airflow 2.0 Reporter: William Pursell Assignee: William Pursell Priority: Trivial -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AIRFLOW-1745) BashOperator ignores SIGPIPE in subprocess
William Pursell created AIRFLOW-1745: Summary: BashOperator ignores SIGPIPE in subprocess Key: AIRFLOW-1745 URL: https://issues.apache.org/jira/browse/AIRFLOW-1745 Project: Apache Airflow Issue Type: Bug Components: DagRun Affects Versions: Airflow 1.8 Reporter: William Pursell Assignee: William Pursell In Python 2, subprocesses ignore SIGPIPE (https://bugs.python.org/issue1652). As a result, a simple bash operator with bash_command = 'yes | head' may never terminate (depending on the implementation of yes). Airflow should reset the signal disposition to default. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AIRFLOW-1745) BashOperator ignores SIGPIPE in subprocess
[ https://issues.apache.org/jira/browse/AIRFLOW-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16213742#comment-16213742 ] William Pursell commented on AIRFLOW-1745: -- Also, see https://stackoverflow.com/questions/22077881/yes-reporting-error-with-subprocess-communicate and https://stackoverflow.com/questions/23064636/python-subprocess-popen-blocks-with-shell-and-pipe/23089677#23089677 It's not clear to me if signals other than SIGPIPE need be reset. > BashOperator ignores SIGPIPE in subprocess > -- > > Key: AIRFLOW-1745 > URL: https://issues.apache.org/jira/browse/AIRFLOW-1745 > Project: Apache Airflow > Issue Type: Bug > Components: DagRun >Affects Versions: Airflow 1.8 >Reporter: William Pursell >Assignee: William Pursell > Original Estimate: 10m > Remaining Estimate: 10m > > In Python 2, subprocesses ignore SIGPIPE (https://bugs.python.org/issue1652). > As a result, a simple bash operator with bash_command = 'yes | head' may > never terminate (depending on the implementation of yes). Airflow should > reset the signal disposition to default. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AIRFLOW-873) Tests forcing availability of hive_metastore module
[ https://issues.apache.org/jira/browse/AIRFLOW-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16222573#comment-16222573 ] William Pursell commented on AIRFLOW-873: - +1 To Andy's comment. What is the resolution? How does one run run_unit_tests.sh? > Tests forcing availability of hive_metastore module > --- > > Key: AIRFLOW-873 > URL: https://issues.apache.org/jira/browse/AIRFLOW-873 > Project: Apache Airflow > Issue Type: Bug >Reporter: krishnabhupatiraju >Assignee: krishnabhupatiraju >Priority: Minor > > PR 2012 leads to an attempt to import hive_metastore any time unit tests are > run, even if these aren't the unit tests being run. hive_metastore is not a > required module for Airflow, but now any machine without it can't run any > local unit tests! I put the traceback I'm seeing below. > The unit test file causing this import needs to be guarded so it only runs in > if its dependencies are available (see hive_operator.py in the same tests > directory for one example, or the explicit skip guards in the postgres/mysql > tests that ensure they only run in the right travis environment). > == > ERROR: Failure: ImportError (No module named 'hive_metastore') > -- > Traceback (most recent call last): > File "/Users/jlowin/anaconda3/lib/python3.5/site-packages/nose/failure.py", > line 39, in runTest > raise self.exc_val.with_traceback(self.tb) > File "/Users/jlowin/anaconda3/lib/python3.5/site-packages/nose/loader.py", > line 418, in loadTestsFromName > addr.filename, addr.module) > File > "/Users/jlowin/anaconda3/lib/python3.5/site-packages/nose/importer.py", line > 47, in importFromPath > return self.importFromDir(dir_path, fqname) > File > "/Users/jlowin/anaconda3/lib/python3.5/site-packages/nose/importer.py", line > 94, in importFromDir > mod = load_module(part_fqname, fh, filename, desc) > File "/Users/jlowin/anaconda3/lib/python3.5/imp.py", line 244, in > load_module > return load_package(name, filename) > File "/Users/jlowin/anaconda3/lib/python3.5/imp.py", line 216, in > load_package > return _load(spec) > File "", line 693, in _load > File "", line 673, in _load_unlocked > File "", line 665, in exec_module > File "", line 222, in _call_with_frames_removed > File "/Users/jlowin/git/airflow/tests/__init__.py", line 24, in > from .operators import * > File "/Users/jlowin/git/airflow/tests/operators/__init__.py", line 20, in > > from .s3_to_hive_operator import * > File "/Users/jlowin/git/airflow/tests/operators/s3_to_hive_operator.py", > line 25, in > from airflow.operators.s3_to_hive_operator import S3ToHiveTransfer > File "/Users/jlowin/git/airflow/airflow/operators/s3_to_hive_operator.py", > line 27, in > from airflow.hooks.hive_hooks import HiveCliHook > File "/Users/jlowin/git/airflow/airflow/hooks/hive_hooks.py", line 28, in > > import hive_metastore > ImportError: No module named 'hive_metastore' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AIRFLOW-646) setup.py install fails
[
https://issues.apache.org/jira/browse/AIRFLOW-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Pursell reassigned AIRFLOW-646:
---
Assignee: William Pursell
> setup.py install fails
> --
>
> Key: AIRFLOW-646
> URL: https://issues.apache.org/jira/browse/AIRFLOW-646
> Project: Apache Airflow
> Issue Type: Bug
>Affects Versions: Airflow 1.7.1
> Environment: OS X
> Ubuntu 16.04
> Python 2.7
> Python 3.5
>Reporter: Nick Allen
>Assignee: William Pursell
>
> Running `python setup.py install` or listing airflow as a dependency in
> another setup.py install_requires section results in the following error:
> {quote}
> Running python-daemon-2.1.2/setup.py -q bdist_egg --dist-dir
> /tmp/easy_install-fibs2crb/python-daemon-2.1.2/egg-dist-tmp-hbg5xgc1
> Traceback (most recent call last):
> File "/usr/local/lib/python3.5/site-packages/setuptools/sandbox.py", line
> 154, in save_modules
> yield saved
> File "/usr/local/lib/python3.5/site-packages/setuptools/sandbox.py", line
> 195, in setup_context
> yield
> File "/usr/local/lib/python3.5/site-packages/setuptools/sandbox.py", line
> 243, in run_setup
> DirectorySandbox(setup_dir).run(runner)
> File "/usr/local/lib/python3.5/site-packages/setuptools/sandbox.py", line
> 273, in run
> return func()
> File "/usr/local/lib/python3.5/site-packages/setuptools/sandbox.py", line
> 242, in runner
> _execfile(setup_script, ns)
> File "/usr/local/lib/python3.5/site-packages/setuptools/sandbox.py", line
> 46, in _execfile
> exec(code, globals, locals)
> File "/tmp/easy_install-fibs2crb/python-daemon-2.1.2/setup.py", line 43, in
>
> sys.exit(errno)
> AttributeError: module 'version' has no attribute 'ChangelogAwareDistribution'
> During handling of the above exception, another exception occurred:
> Traceback (most recent call last):
> File "setup.py", line 281, in
> do_setup()
> File "setup.py", line 275, in do_setup
> 'extra_clean': CleanCommand,
> File "/usr/local/lib/python3.5/distutils/core.py", line 148, in setup
> dist.run_commands()
> File "/usr/local/lib/python3.5/distutils/dist.py", line 955, in run_commands
> self.run_command(cmd)
> File "/usr/local/lib/python3.5/distutils/dist.py", line 974, in run_command
> cmd_obj.run()
> File
> "/usr/local/lib/python3.5/site-packages/setuptools/command/install.py", line
> 67, in run
> self.do_egg_install()
> File
> "/usr/local/lib/python3.5/site-packages/setuptools/command/install.py", line
> 117, in do_egg_install
> cmd.run()
> File
> "/usr/local/lib/python3.5/site-packages/setuptools/command/easy_install.py",
> line 391, in run
> self.easy_install(spec, not self.no_deps)
> File
> "/usr/local/lib/python3.5/site-packages/setuptools/command/easy_install.py",
> line 621, in easy_install
> return self.install_item(None, spec, tmpdir, deps, True)
> File
> "/usr/local/lib/python3.5/site-packages/setuptools/command/easy_install.py",
> line 672, in install_item
> self.process_distribution(spec, dist, deps)
> File
> "/usr/local/lib/python3.5/site-packages/setuptools/command/easy_install.py",
> line 717, in process_distribution
> [requirement], self.local_index, self.easy_install
> File "/usr/local/lib/python3.5/site-packages/pkg_resources/__init__.py",
> line 826, in resolve
> dist = best[req.key] = env.best_match(req, ws, installer)
> File "/usr/local/lib/python3.5/site-packages/pkg_resources/__init__.py",
> line 1092, in best_match
> return self.obtain(req, installer)
> File "/usr/local/lib/python3.5/site-packages/pkg_resources/__init__.py",
> line 1104, in obtain
> return installer(requirement)
> File
> "/usr/local/lib/python3.5/site-packages/setuptools/command/easy_install.py",
> line 640, in easy_install
> return self.install_item(spec, dist.location, tmpdir, deps)
> File
> "/usr/local/lib/python3.5/site-packages/setuptools/command/easy_install.py",
> line 670, in install_item
> dists = self.install_eggs(spec, download, tmpdir)
> File
> "/usr/local/lib/python3.5/site-packages/setuptools/command/easy_install.py",
> line 850, in install_eggs
> return self.build_and_install(setup_script, setup_base)
> File
> "/usr/local/lib/python3.5/site-packages/setuptools/command/easy_install.py",
> line 1078, in build_and_install
> self.run_setup(setup_script, setup_base, args)
> File
> "/usr/local/lib/python3.5/site-packages/setuptools/command/easy_install.py",
> line 1064, in run_setup
> run_setup(setup_script, args)
> File "/usr/local/lib/python3.5/site-packages/setuptools/sandbox.py", line
> 246, in run_setup
> raise
> File "/usr/local/lib/python3.5/contextlib.py", line 77, in __exit__
> self.gen.throw(type, value, traceback)
> File "/usr/local/lib/python3.5/si
[jira] [Created] (AIRFLOW-1820) dagrun.dependency-check metric does not play nice with statsd
William Pursell created AIRFLOW-1820:
Summary: dagrun.dependency-check metric does not play nice with
statsd
Key: AIRFLOW-1820
URL: https://issues.apache.org/jira/browse/AIRFLOW-1820
Project: Apache Airflow
Issue Type: Bug
Components: core
Reporter: William Pursell
Assignee: William Pursell
Priority: Minor
The metric dagrun.dependency-check
(https://github.com/apache/incubator-airflow/blob/master/airflow/models.py#L4594)
is sent to statsd with spaces and colons in the metric name. This is not
ideal for statsd. (I'm not really sure I see the point of putting a timestamp
in a metric name at all!) We should either do something like
Stats.timing("dagrun.dependency-check.{}{:%Y%m%d_%H%M%S}". to use a nicer name,
or just drop the timestamp completely.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AIRFLOW-1869) Logging in gcs_task_handler discards too many error messages
William Pursell created AIRFLOW-1869: Summary: Logging in gcs_task_handler discards too many error messages Key: AIRFLOW-1869 URL: https://issues.apache.org/jira/browse/AIRFLOW-1869 Project: Apache Airflow Issue Type: Improvement Components: core Reporter: William Pursell Assignee: William Pursell Priority: Minor Fix For: Airflow 2.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AIRFLOW-1869) Logging in gcs_task_handler discards too many error messages
[ https://issues.apache.org/jira/browse/AIRFLOW-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Pursell updated AIRFLOW-1869: - Description: Many exceptions are caught and effectively discarded in the gcs task log reader. It makes debugging difficult. The logs should be more verbose and include the exception strings. > Logging in gcs_task_handler discards too many error messages > > > Key: AIRFLOW-1869 > URL: https://issues.apache.org/jira/browse/AIRFLOW-1869 > Project: Apache Airflow > Issue Type: Improvement > Components: core >Reporter: William Pursell >Assignee: William Pursell >Priority: Minor > Fix For: Airflow 2.0 > > > Many exceptions are caught and effectively discarded in the gcs task log > reader. It makes debugging difficult. The logs should be more verbose and > include the exception strings. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AIRFLOW-1876) Subtask logs are not easily distinguised
William Pursell created AIRFLOW-1876:
Summary: Subtask logs are not easily distinguised
Key: AIRFLOW-1876
URL: https://issues.apache.org/jira/browse/AIRFLOW-1876
Project: Apache Airflow
Issue Type: Improvement
Components: core
Reporter: William Pursell
Assignee: William Pursell
Priority: Minor
Currently, when the scheduler is outputting all subtask logs to the same
stream, it is not easy to distinguish which logs come from which task. It
would be nice if there were some convenient way to filter the logs from a given
task. For example, putting the task id after the word 'Subtask'
For example:
diff --git a/airflow/task_runner/base_task_runner.py
b/airflow/task_runner/base_task_runner.py
index bc0edcf3..e40f6ea9 100644
--- a/airflow/task_runner/base_task_runner.py
+++ b/airflow/task_runner/base_task_runner.py
@@ -95,7 +95,11 @@ class BaseTaskRunner(LoggingMixin):
line = line.decode('utf-8')
if len(line) == 0:
break
-self.log.info(u'Subtask %s: %s', self._task_instance,
line.rstrip('\n'))
+self.log.info(
+u'Subtask %d: %s',
+self._task_instance.job_id,
+line.rstrip('\n')
+)
def run_command(self, run_with, join_args=False):
"""
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AIRFLOW-1903) /admin/airflow should not be hardcoded
William Pursell created AIRFLOW-1903: Summary: /admin/airflow should not be hardcoded Key: AIRFLOW-1903 URL: https://issues.apache.org/jira/browse/AIRFLOW-1903 Project: Apache Airflow Issue Type: Improvement Components: core Reporter: William Pursell Assignee: William Pursell Priority: Minor Joy's new webserver (https://github.com/wepay/airflow-webserver) is changing some of the endpoints. Whether that package or some other is merged, we'll need some flexibility. In the short term, there needs to be a way to inject a different path to logs in the email alerts, and adding a config option seems easiest. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (AIRFLOW-1903) /admin/airflow should not be hardcoded
[ https://issues.apache.org/jira/browse/AIRFLOW-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Pursell closed AIRFLOW-1903. Resolution: Duplicate Duplicates https://issues.apache.org/jira/browse/AIRFLOW-1755 > /admin/airflow should not be hardcoded > -- > > Key: AIRFLOW-1903 > URL: https://issues.apache.org/jira/browse/AIRFLOW-1903 > Project: Apache Airflow > Issue Type: Improvement > Components: core >Reporter: William Pursell >Assignee: William Pursell >Priority: Minor > Original Estimate: 2h > Remaining Estimate: 2h > > Joy's new webserver (https://github.com/wepay/airflow-webserver) is changing > some of the endpoints. Whether that package or some other is merged, we'll > need some flexibility. In the short term, there needs to be a way to inject > a different path to logs in the email alerts, and adding a config option > seems easiest. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AIRFLOW-1915) flask-wtf version specification is too tight
William Pursell created AIRFLOW-1915: Summary: flask-wtf version specification is too tight Key: AIRFLOW-1915 URL: https://issues.apache.org/jira/browse/AIRFLOW-1915 Project: Apache Airflow Issue Type: Wish Components: core Reporter: William Pursell Assignee: William Pursell Priority: Minor airflow currently specifies flask-wtf 0.14. flask-application-builder requires 0.14.2. The discrepancy causes the version information to be unavailable from the web page when using the fab-based webserver. This seems unnecessary, and can be fixed by relaxing the version constraint in airflow. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AIRFLOW-1948) Errors on on_kill are suppressed
William Pursell created AIRFLOW-1948: Summary: Errors on on_kill are suppressed Key: AIRFLOW-1948 URL: https://issues.apache.org/jira/browse/AIRFLOW-1948 Project: Apache Airflow Issue Type: Improvement Components: core Reporter: William Pursell Assignee: William Pursell Priority: Minor BaseJob.kill eats diagnostic information which should make it into the log -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (AIRFLOW-1948) Errors on on_kill are suppressed
[ https://issues.apache.org/jira/browse/AIRFLOW-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AIRFLOW-1948 started by William Pursell. > Errors on on_kill are suppressed > > > Key: AIRFLOW-1948 > URL: https://issues.apache.org/jira/browse/AIRFLOW-1948 > Project: Apache Airflow > Issue Type: Improvement > Components: core >Reporter: William Pursell >Assignee: William Pursell >Priority: Minor > > BaseJob.kill eats diagnostic information which should make it into the log -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AIRFLOW-1948) Errors on on_kill are suppressed
[ https://issues.apache.org/jira/browse/AIRFLOW-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300803#comment-16300803 ] William Pursell commented on AIRFLOW-1948: -- https://github.com/apache/incubator-airflow/pull/2897 > Errors on on_kill are suppressed > > > Key: AIRFLOW-1948 > URL: https://issues.apache.org/jira/browse/AIRFLOW-1948 > Project: Apache Airflow > Issue Type: Improvement > Components: core >Reporter: William Pursell >Assignee: William Pursell >Priority: Minor > > BaseJob.kill eats diagnostic information which should make it into the log -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (AIRFLOW-1915) flask-wtf version specification is too tight
[ https://issues.apache.org/jira/browse/AIRFLOW-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AIRFLOW-1915 started by William Pursell. > flask-wtf version specification is too tight > > > Key: AIRFLOW-1915 > URL: https://issues.apache.org/jira/browse/AIRFLOW-1915 > Project: Apache Airflow > Issue Type: Wish > Components: core >Reporter: William Pursell >Assignee: William Pursell >Priority: Minor > Original Estimate: 0.25h > Remaining Estimate: 0.25h > > airflow currently specifies flask-wtf 0.14. flask-application-builder > requires 0.14.2. The discrepancy causes the version information to be > unavailable from the web page when using the fab-based webserver. This seems > unnecessary, and can be fixed by relaxing the version constraint in airflow. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AIRFLOW-1915) flask-wtf version specification is too tight
[ https://issues.apache.org/jira/browse/AIRFLOW-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300804#comment-16300804 ] William Pursell commented on AIRFLOW-1915: -- https://github.com/apache/incubator-airflow/pull/2876 > flask-wtf version specification is too tight > > > Key: AIRFLOW-1915 > URL: https://issues.apache.org/jira/browse/AIRFLOW-1915 > Project: Apache Airflow > Issue Type: Wish > Components: core >Reporter: William Pursell >Assignee: William Pursell >Priority: Minor > Original Estimate: 0.25h > Remaining Estimate: 0.25h > > airflow currently specifies flask-wtf 0.14. flask-application-builder > requires 0.14.2. The discrepancy causes the version information to be > unavailable from the web page when using the fab-based webserver. This seems > unnecessary, and can be fixed by relaxing the version constraint in airflow. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AIRFLOW-1955) Seeing errors "UnboundLocalError: local variable 'old_log' referenced before assignment" when using gcs logging
William Pursell created AIRFLOW-1955: Summary: Seeing errors "UnboundLocalError: local variable 'old_log' referenced before assignment" when using gcs logging Key: AIRFLOW-1955 URL: https://issues.apache.org/jira/browse/AIRFLOW-1955 Project: Apache Airflow Issue Type: Bug Reporter: William Pursell Assignee: William Pursell UnboundLocalError: local variable 'old_log' referenced before assignment This is a result of changes introduced in 75eef96af, which introduces a code path in which the variable is not set -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AIRFLOW-2938) Invalid 'extra' field in connection can raise an AttributeError when attempting to edit
William Pursell created AIRFLOW-2938: Summary: Invalid 'extra' field in connection can raise an AttributeError when attempting to edit Key: AIRFLOW-2938 URL: https://issues.apache.org/jira/browse/AIRFLOW-2938 Project: Apache Airflow Issue Type: Bug Reporter: William Pursell Assignee: William Pursell When the extra field of a connection is not an iterable json object, attempting to edit the connection can lead to a stack trace "Ooops": AttributeError: 'NoneType' object has no attribute 'get' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRFLOW-2083) Incorrect usage of "it's" appears throughout the documentation
William Pursell created AIRFLOW-2083: Summary: Incorrect usage of "it's" appears throughout the documentation Key: AIRFLOW-2083 URL: https://issues.apache.org/jira/browse/AIRFLOW-2083 Project: Apache Airflow Issue Type: Bug Reporter: William Pursell Assignee: William Pursell In several places, the word "it's" appears when it ought to be "its" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRFLOW-2142) Error messages are suppressed
William Pursell created AIRFLOW-2142: Summary: Error messages are suppressed Key: AIRFLOW-2142 URL: https://issues.apache.org/jira/browse/AIRFLOW-2142 Project: Apache Airflow Issue Type: Bug Reporter: William Pursell Assignee: William Pursell Many fatal exceptions are caught and the text of the exception is replaced with less specific information, leading to increased difficulty in diagnosing errors. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRFLOW-2370) Unable to script user account creation
William Pursell created AIRFLOW-2370: Summary: Unable to script user account creation Key: AIRFLOW-2370 URL: https://issues.apache.org/jira/browse/AIRFLOW-2370 Project: Apache Airflow Issue Type: Bug Components: core Affects Versions: 1.9.0 Reporter: William Pursell Assignee: William Pursell ariflow create_user invokes getpass.getpass to get a password. This makes it difficult to script the creation of users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
