-
Notifications
You must be signed in to change notification settings - Fork 38
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
General code cleanup part #1 #29
Conversation
Move usage of coverage to run_tests
* spylon can already do this * It was broken looking for the python cell magic * It uses a metakernel.IPythonKernel instead of the active IPython kernel
* Show a reasonable error message when input is incomplete according to the interpreter * Only use one executors in the thread pool: we must do one thing at a time anyway
Going to do this separately after the general cleanup This reverts commit c8fa833.
Codecov Report
@@ Coverage Diff @@
## master #29 +/- ##
==========================================
- Coverage 85.48% 84.31% -1.18%
==========================================
Files 6 6
Lines 434 408 -26
==========================================
- Hits 371 344 -27
- Misses 63 64 +1 |
Whoops. Gotta put codecov back in. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for this
%%init_spark | ||
application_name = "My Fancy App" | ||
launcher.jars = ["file://some/jar.jar"] | ||
launcher.master = "local[4]" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What in the world is this local[4]
syntax?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Spark syntax for how many cores to use. local[4]
says "Please use 4 of my cores for the application master." local[*]
says "TAKE ALL MY CORES PLZ!"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add that as a comment in the code?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM? I know very little about this codebase but nothing is standing out to me
Going to merge what I've got, then carry on with documenting the other two modules in another PR. Thanks folks. |
Prelude to #28, 26, and #22 which will build atop this but that
I want to keep separate for easier review.