airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Iuliia Volkova (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-3326) High Sierra Complaining 'in progress in another thread when fork() was called'
Date Thu, 22 Nov 2018 07:29:00 GMT

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

Iuliia Volkova commented on AIRFLOW-3326:
-----------------------------------------

[~ryan.yuan] is this all code of plugin? 

from airflow.contrib.hooks.bigquery_hook import BigQueryHook

class BQHook(BigQueryHook):
    pass 

> High Sierra Complaining 'in progress in another thread when fork() was called'
> ------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-3326
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3326
>             Project: Apache Airflow
>          Issue Type: Bug
>    Affects Versions: 1.10.0
>         Environment: macOS High Sierra 10.13.6 (17G65)
>            Reporter: Ryan Yuan
>            Assignee: Ryan Yuan
>            Priority: Blocker
>
> Inside the plugins folder, I have a hook that is a child class of BigQueryHook. 
> {code:java}
> // code
> from airflow.contrib.hooks.bigquery_hook import BigQueryHook
> class BQHook(BigQueryHook):
>     pass{code}
> When I run the airflow server, it keeps throwing messages complaining 'in progress in
another thread when fork() was called', and I can't use the web server UI at all.
> {code:java}
> // messages from terminal
> objc[15098]: +[__NSPlaceholderDate initialize] may have been in progress in another thread
when fork() was called.
> objc[15098]: +[__NSPlaceholderDate initialize] may have been in progress in another thread
when fork() was called. We cannot safely call it or ignore it in the fork() child process.
Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
> [2018-11-12 14:03:40 +1100] [15102] [INFO] Booting worker with pid: 15102
> [2018-11-12 14:03:40,792] {__init__.py:51} INFO - Using executor SequentialExecutor
> [2018-11-12 14:03:40,851] {base_hook.py:83} INFO - Using connection to: https://custom-data-z00100-dev.appspot.com/
> objc[15099]: +[__NSPlaceholderDate initialize] may have been in progress in another thread
when fork() was called.
> objc[15099]: +[__NSPlaceholderDate initialize] may have been in progress in another thread
when fork() was called. We cannot safely call it or ignore it in the fork() child process.
Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
> [2018-11-12 14:03:40 +1100] [15103] [INFO] Booting worker with pid: 15103
> [2018-11-12 14:03:40,902] {base_hook.py:83} INFO - Using connection to: https://custom-data-z00100-dev.appspot.com/
> objc[15101]: +[__NSPlaceholderDate initialize] may have been in progress in another thread
when fork() was called.
> objc[15101]: +[__NSPlaceholderDate initialize] may have been in progress in another thread
when fork() was called. We cannot safely call it or ignore it in the fork() child process.
Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
> [2018-11-12 14:03:40 +1100] [15104] [INFO] Booting worker with pid: 15104
> [2018-11-12 14:03:40,948] {base_hook.py:83} INFO - Using connection to: https://custom-data-z00100-dev.appspot.com/
> objc[15100]: +[__NSPlaceholderDate initialize] may have been in progress in another thread
when fork() was called.
> objc[15100]: +[__NSPlaceholderDate initialize] may have been in progress in another thread
when fork() was called. We cannot safely call it or ignore it in the fork() child process.
Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
> {code}



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

Mime
View raw message