Confusing error message when default pickling for intermediate storage fails
See original GitHub issuerepro:
from dagster import (
DagsterInstance,
Output,
Nothing,
execute_pipeline,
pipeline,
reconstructable,
solid,
)
@solid
def nothing_solid(_):
yield Output(Nothing)
@pipeline
def repro():
nothing_solid()
if __name__ == "__main__":
execute_pipeline(
reconstructable(repro),
run_config={"execution": {"multiprocess": {}}, "storage": {"filesystem": {}}},
instance=DagsterInstance.get(),
)
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Unable to load files using pickle and multiple modules
The issue is that you're pickling objects defined in Settings by actually running the 'Settings' module, then you're trying to unpickle the objects...
Read more >PicklingError in pyspark (PicklingError: Can't pickle <class ...
Possible answer from here. The problem is that you're trying to pickle an object from the module where it's defined. If you move...
Read more >Classes - pybind11 documentation
Classes#. This section presents advanced binding code for classes and it is assumed that you are already familiar with the basics from Object-oriented...
Read more >Multiprocessing and Pickle, How to Easily fix that?
Steps to pickle ... 2. Save the file and run it through python process.py in the terminal. The test_pickle.pkl supposed to appear on...
Read more >Spark Programming Guide - Spark 2.1.0 Documentation
Users may also ask Spark to persist an RDD in memory, allowing it to be reused ... By default, when Spark runs a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
another user reported getting “OSError: [Errno 22] Invalid argument” from the same line as above stack trace since the user’s output was several GB. It was not clear that the resolution was to configure a different intermediate storage
Introduced a new error type
DagsterObjectStoreError
to capture errors during intermediate object store get and set.updated the error message to show more details: