long tracebacks
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- stream-processing
Research direction
Start by reviewing the Stream usage shown in the issue and the proposed to_graph() and run(graph, input) entry points. The issue does not identify files, tests, an existing execution path, or acceptance criteria, so the desired traceback behavior and definition of done need to be established first.
Written by the indexing model from the issue text.
Description
I'm wondering if we can avoid long tracebacks:
In [1]: from streamz import Stream
In [2]: s = Stream()
In [3]: snext = s
...: for i in range(10):
...: snext = snext.map(lambda x : x)
...:
In [4]: def foo(x):
...: raise ValueError("Foo")
...:
In [5]: snext.sink(foo)
Out[5]: <sink: foo>
In [6]: s.emit(1)
.... Long error message
<ipython-input-4-9636b5287c3d> in foo(x)
1 def foo(x):
----> 2 raise ValueError("Foo")
ValueError: Foo
A way around this could be that the stream returns a graph which is executed one by one by an external function, like:
graph = s.to_graph()
run(graph, input)
where the run function would walk through each node in the graph in a top-down fashion and resolve the results.
Any other thoughts? Just an idea I figured I'd document somewhere. thanks!
- Dominant language
- Python
- Stars
- 1.3k
- Forks
- 149
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from python-streamz/streamz
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
python-streamz/streamz#481 · 4 comments ·
-
Combining the streamz.Stream.filenames() and streamz.Stream.from_textfile() using dask scatter? Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
python-streamz/streamz#480 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
python-streamz/streamz#479 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
python-streamz/streamz#478 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 10/100
python-streamz/streamz#476 · 17 comments · 2 reactions ·
All issues in python-streamz/streamz
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100