Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Too big of runtime #105

Closed
ericmjonas opened this issue Mar 26, 2017 · 3 comments
Closed

Too big of runtime #105

ericmjonas opened this issue Mar 26, 2017 · 3 comments
Assignees
Labels
Milestone

Comments

@ericmjonas
Copy link
Collaborator

@ericmjonas ericmjonas commented Mar 26, 2017

If a user creates a runtime that unpacks to be too large, make sure we deliver sane errors to the user.

@ericmjonas
Copy link
Collaborator Author

@ericmjonas ericmjonas commented Mar 26, 2017

In particular the wrenhandler tries to download the pickled objects like data and the function before it deals with the handler. So this is a problem for multiple reasons

  • If func or data is too large, we will error
  • if there is left-over crap from a previous run, we will error
@ericmjonas
Copy link
Collaborator Author

@ericmjonas ericmjonas commented Mar 26, 2017

A reasonable workaround if the runtime ate up too much space on the last invocation can be to call map with use_cached_runtime=False

@shivaram shivaram added this to the v0.3 milestone Mar 29, 2017
@shivaram shivaram added the runtime label Mar 29, 2017
@ericmjonas
Copy link
Collaborator Author

@ericmjonas ericmjonas commented Aug 26, 2017

Closed by PR #172

@ericmjonas ericmjonas closed this Aug 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.