https://dagster.io/ logo
#announcements
Title
# announcements
f

Felix Yuan

11/18/2020, 10:34 AM
anybody knows why 'segmentation fault' occurs while running 'dagit -f hello_dagster.py'
n

Noah K

11/18/2020, 10:35 AM
What does your code look like?
f

Felix Yuan

11/18/2020, 11:05 AM
from dagster import execute_pipeline, pipeline, solid
@solid def get_name(_): return 'dagster' @solid def hello(context, name: str): context.log.info('Hello, {name}!'.format(name=name)) @pipeline def hello_pipeline(): hello(get_name())
exactly the first example in tutorial
n

Noah K

11/18/2020, 11:05 AM
What happens if you just run
python
f

Felix Yuan

11/18/2020, 11:06 AM
Python 3.7.2 (default, Feb 13 2019, 094728) [Clang 10.0.0 (clang-1000.11.45.5)] on darwin Type "help", "copyright", "credits" or "license" for more information.
n

Noah K

11/18/2020, 11:07 AM
Okay, so that works at least
f

Felix Yuan

11/18/2020, 11:07 AM
(dagster) ➜ dagster dagit -f hello_dagster.py /Users/yuany/envs/dagster/lib/python3.7/importlib/_bootstrap.py219 RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject return f(*args, **kwds) /Users/yuany/envs/dagster/lib/python3.7/importlib/_bootstrap.py219 RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject return f(*args, **kwds) /Users/yuany/envs/dagster/lib/python3.7/importlib/_bootstrap.py219 RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject return f(*args, **kwds) /Users/yuany/envs/dagster/lib/python3.7/importlib/_bootstrap.py219 RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject return f(*args, **kwds) /Users/yuany/envs/dagster/lib/python3.7/importlib/_bootstrap.py219 RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject return f(*args, **kwds) /Users/yuany/envs/dagster/lib/python3.7/importlib/_bootstrap.py219 RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject return f(*args, **kwds) /Users/yuany/envs/dagster/lib/python3.7/site-packages/dagster/core/instance/config.py29 UserWarning: The dagster instance configuration file (dagster.yaml) is not present at /var/folders/ky/8vpv512d043f06lsw_5jtfbh0000gn/T/tmpy3yox77i. Dagster uses this file to know where and how to store local artifacts, information about past runs, and structured events. If nothing is specified, Dagster will store this information in the local filesystem in the /var/folders/ky/8vpv512d043f06lsw_5jtfbh0000gn/T/tmpy3yox77i directory. ).format(config_filename=config_filename, base_dir=base_dir) Loading repository... Serving on http://127.0.0.1:3000 in process 60564 [1] 60564 segmentation fault dagit -f hello_dagster.py
This is the full log
n

Noah K

11/18/2020, 11:09 AM
Did you maybe upgrade python after installing dagster?
f

Felix Yuan

11/18/2020, 11:09 AM
no, I didn't upgrade python
This is my first time to try dagster, I followed the tutorial step by step. It is OK to run with dagster (rather than dagit) .
n

Noah K

11/18/2020, 11:11 AM
Are you familiar with gdb? You could try and get a stack trace out of it.
f

Felix Yuan

11/18/2020, 11:14 AM
ok, I will try gdb, may be tomorrow, I will give you feedback
This is the list of pip freeze
(dagster) ➜ dagster cat requirements.txt alembic==1.4.3 aniso8601==7.0.0 attrs==20.3.0 bleach==3.2.1 certifi==2020.11.8 chardet==3.0.4 click==7.1.2 coloredlogs==14.0 contextlib2==0.6.0.post1 croniter==0.3.36 dagit==0.9.19 dagster==0.9.19 dagster-graphql==0.9.19 defusedxml==0.6.0 docstring-parser==0.7.1 entrypoints==0.3 Flask==1.1.2 Flask-Cors==3.0.9 Flask-GraphQL==2.0.1 Flask-Sockets==0.2.1 funcsigs==1.0.2 future==0.18.2 gevent==20.9.0 gevent-websocket==0.10.1 graphene==2.1.8 graphql-core==2.3.2 graphql-relay==2.0.1 graphql-server-core==1.2.0 graphql-ws==0.3.1 greenlet==0.4.17 grpcio==1.33.2 grpcio-health-checking==1.33.2 humanfriendly==8.2 idna==2.10 importlib-metadata==2.0.0 ipython-genutils==0.2.0 itsdangerous==1.1.0 Jinja2==2.11.2 jsonschema==3.2.0 jupyter-core==4.7.0 Mako==1.1.3 MarkupSafe==1.1.1 mistune==0.8.4 natsort==7.0.1 nbconvert==5.6.1 nbformat==5.0.8 packaging==20.4 pandocfilters==1.4.3 pathtools==0.1.2 pendulum==1.4.4 promise==2.3 protobuf==3.14.0 Pygments==2.7.2 pyparsing==2.4.7 pyrsistent==0.17.3 python-dateutil==2.8.1 python-editor==1.0.4 pytz==2020.4 pytzdata==2020.1 PyYAML==5.3.1 requests==2.25.0 Rx==1.6.1 six==1.15.0 SQLAlchemy==1.3.20 tabulate==0.8.7 testpath==0.4.4 toposort==1.5 tqdm==4.52.0 traitlets==5.0.5 tzlocal==1.5.1 urllib3==1.26.2 watchdog==0.10.3 webencodings==0.5.1 Werkzeug==1.0.1 zipp==3.4.0 zope.event==4.5.0 zope.interface==5.2.0
a

alex

11/18/2020, 3:48 PM
wild - have not seen anything like this reported before
the python 3.7 version we test against is
3.7.8
n

Noah K

11/18/2020, 7:47 PM
It's almost certainly a bad compiled module in the local setup
👍 1
Just hard to trace which without a stack
f

Felix Yuan

11/19/2020, 2:06 AM
I downgrade my greenlet to 0.4.14, it works now.
4 Views