Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upBetter synchronization of runtime information with local client #44
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
ericmjonas
Feb 22, 2017
Collaborator
This actually shouldn't be that hard now that we have the runtime metadata and are validating it -- we could effectively replace the calls to preinstalled.
|
This actually shouldn't be that hard now that we have the runtime metadata and are validating it -- we could effectively replace the calls to preinstalled. |
ericmjonas
closed this
Feb 22, 2017
ericmjonas
reopened this
Feb 22, 2017
shivaram
added this to the v0.2 milestone
Mar 9, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
This is part of the serialization cleanup |
shivaram
self-assigned this
Mar 9, 2017
ericmjonas
added
the
serialization
label
Mar 19, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
shivaram
Mar 20, 2017
Collaborator
@ericmjonas Am I right in understanding that you are also addressing this in the serialization-bugs branch ?
|
@ericmjonas Am I right in understanding that you are also addressing this in the |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
ericmjonas
Mar 20, 2017
Collaborator
Yes because this requires changing the serialization infrastructure to take
in a more automatically-generated list of preinstalls from the runtime
`meta.json`
…On Mon, Mar 20, 2017 at 10:02 AM, Shivaram Venkataraman < ***@***.***> wrote:
@ericmjonas <https://github.com/ericmjonas> Am I right in understanding
that you are also addressing this in the serialization-bugs branch ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#44 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AACPEhtVeQfZ54UtkKgUEddalnpEiJ5pks5rnrEqgaJpZM4MHhvH>
.
|
Yes because this requires changing the serialization infrastructure to take
in a more automatically-generated list of preinstalls from the runtime
`meta.json`
…On Mon, Mar 20, 2017 at 10:02 AM, Shivaram Venkataraman < ***@***.***> wrote:
@ericmjonas <https://github.com/ericmjonas> Am I right in understanding
that you are also addressing this in the serialization-bugs branch ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#44 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AACPEhtVeQfZ54UtkKgUEddalnpEiJ5pks5rnrEqgaJpZM4MHhvH>
.
|
added a commit
that referenced
this issue
Mar 22, 2017
ericmjonas
closed this
Mar 22, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ericmjonas commentedFeb 21, 2017
Right now, what modules to not upload is hardcoded. We should be able to do better than that, especially due to conda env. This is mostly a placeholder to keep the issue alive.