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

Datasets not initally available when starting from scratch #46

Closed
hjwilli opened this issue Jun 20, 2018 · 2 comments
Closed

Datasets not initally available when starting from scratch #46

hjwilli opened this issue Jun 20, 2018 · 2 comments
Assignees
Labels

Comments

@hjwilli
Copy link
Collaborator

hjwilli commented Jun 20, 2018

When starting pennai completely from scratch, the only datasets initially available via the web interface are
(Adults, Breast Cancer, Gametes, Hypothyroid, Mushrooms, Readmissions); the initial datasets defined in pennai\lab\examples\Users\Users.json. It seems that after some time if the containers are restarted all of the datasets are available.

The cause may be that the process that does the initial loading of the datasets takes a while to run, and does so silently.

@hjwilli hjwilli added the bug label Jun 20, 2018
hjwilli added a commit that referenced this issue Jun 20, 2018
make lab node_modules unzipping verbose again; making it silent doesn't
seem to impact speed too much and it seems better to have feedback as to
what is happening

make machine verbose as well

references #46
@hjwilli hjwilli self-assigned this Jun 20, 2018
hjwilli added a commit that referenced this issue Jun 20, 2018
Updated the machine start script to run 'npm install' if it sees a
machine/node_modules/.staging directory.

References #46
@hjwilli
Copy link
Collaborator Author

hjwilli commented Jun 20, 2018

Discovered an issue... the 'npm install' command had only partially completed on machine (because I force exited the container during the initial build... whoops), meaning there was a machine/node_modules directory which was incomplete and the machine process was not starting correctly.

Updated the machine start script to run 'npm install' if it sees a machine/node_modules/.staging directory.

hjwilli added a commit that referenced this issue Jul 6, 2018
References #40
References #46
@hjwilli
Copy link
Collaborator Author

hjwilli commented Jul 11, 2018

This seems to be stable as of fc25144.

Datasets are loaded during the startup process of machine instances, which register the datasets located in machine/datasets using the lab api (/api/v1/datasets/). Inconsistent behavior was caused by machine and lab starting at different times, machine instances now wait for lab to be up before attempting to register.

@hjwilli hjwilli closed this as completed Jul 11, 2018
hjwilli added a commit that referenced this issue Aug 1, 2018
Remove dataset configuration from lab\examples\Users\Users.json

References #46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant