[GitHub] [airflow] dossett commented on issue #5386: AIRFLOW-4748 Print stacktrace for dagbag process exceptions

2019-06-19 Thread GitBox
dossett commented on issue #5386: AIRFLOW-4748 Print stacktrace for dagbag 
process exceptions
URL: https://github.com/apache/airflow/pull/5386#issuecomment-503647953
 
 
   @ashb No, this particular error isn't that useful, but other errors have 
been especially very generic python error messages.  It does seem clunky in the 
UI like this, I admit, but finding it in a log file is super valuable.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [airflow] dossett commented on issue #5386: AIRFLOW-4748 Print stacktrace for dagbag process exceptions

2019-06-18 Thread GitBox
dossett commented on issue #5386: AIRFLOW-4748 Print stacktrace for dagbag 
process exceptions
URL: https://github.com/apache/airflow/pull/5386#issuecomment-503219352
 
 
   @ashb I stand corrected, I saw it the next time I opened Airflow, lol.
   
   
![image](https://user-images.githubusercontent.com/7207582/59703290-2eb67000-91bf-11e9-942e-a62e880c66a4.png)
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [airflow] dossett commented on issue #5386: AIRFLOW-4748 Print stacktrace for dagbag process exceptions

2019-06-18 Thread GitBox
dossett commented on issue #5386: AIRFLOW-4748 Print stacktrace for dagbag 
process exceptions
URL: https://github.com/apache/airflow/pull/5386#issuecomment-503217514
 
 
   @ashb The way we use Airflow I don't actually see this in the UI.  We have a 
service to submit the DAGs which calls into Airflow's code to parse the dag 
first (I don't recall the exact mechanism), so I only see this in an error log.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [airflow] dossett commented on issue #5386: AIRFLOW-4748 Print stacktrace for dagbag process exceptions

2019-06-17 Thread GitBox
dossett commented on issue #5386: AIRFLOW-4748 Print stacktrace for dagbag 
process exceptions
URL: https://github.com/apache/airflow/pull/5386#issuecomment-502859594
 
 
   @ashb Are you ok with this more limited change?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [airflow] dossett commented on issue #5386: AIRFLOW-4748 Print stacktrace for dagbag process exceptions

2019-06-13 Thread GitBox
dossett commented on issue #5386: AIRFLOW-4748 Print stacktrace for dagbag 
process exceptions
URL: https://github.com/apache/airflow/pull/5386#issuecomment-501862633
 
 
   @ashb That is an intriguing idea, but I don't have the bandwidth of a 
broader fix right now.  This is one of a few Airflow PRs I'm working as a 
result our 1.10.3 upgrade last week.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [airflow] dossett commented on issue #5386: AIRFLOW-4748 Print stacktrace for dagbag process exceptions

2019-06-11 Thread GitBox
dossett commented on issue #5386: AIRFLOW-4748 Print stacktrace for dagbag 
process exceptions
URL: https://github.com/apache/airflow/pull/5386#issuecomment-501097636
 
 
   Failing unit tests fixed.  Searching for `[fail]` in the travis output was 
the key.
   
   Thanks for the suggestion @milton0825 


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [airflow] dossett commented on issue #5386: AIRFLOW-4748 Print stacktrace for dagbag process exceptions

2019-06-08 Thread GitBox
dossett commented on issue #5386: AIRFLOW-4748 Print stacktrace for dagbag 
process exceptions
URL: https://github.com/apache/airflow/pull/5386#issuecomment-500177728
 
 
   One of the test suites passed, some others failed, I can't tell if the 
failures are connected to this change or not.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services