Conversation
Contributor
|
yay! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A little while back, we had issue with hiting the size limit for loading object in static TLS (thread local storage). A workaround was to preload those libraries. Newer versions of these libraries and their dependencies reduce the use of static TLS.
Removing the preloading of these libraries will make using
pip installand the like in kernels easier.I ran our test suite and the kernel reported by a user originally that was causing TLS issue and they all run: https://www.kaggle.com/kmader/library-overload
BUG=118388247