-
Notifications
You must be signed in to change notification settings - Fork 285
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
docs(examples): supply chain image boot goes silent for 10 minutes #780
Labels
Developer_Experience
documentation
Improvements or additions to documentation
enhancement
New feature or request
Milestone
Comments
petermetz
added
bug
Something isn't working
Developer_Experience
documentation
Improvements or additions to documentation
labels
Apr 9, 2021
I'm not sure this counts as a bug, but it would be a nice QoL fix. Thanks Peter! |
petermetz
added
enhancement
New feature or request
and removed
bug
Something isn't working
labels
Apr 9, 2021
petermetz
changed the title
fix(examples): supply chain image boot goes silent for 10 minutes
docs(examples): supply chain image boot goes silent for 10 minutes
Apr 9, 2021
Another thing: more documentation around what conditions, exactly, the demo needs to work would be great. This probably isn't the place to say this, but in the long run, a demo that business people could easily run on standard windows corporate laptops would be great. |
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Apr 15, 2021
Also adding a logger object so that the test ledger can be a little more chatty while starting up. Related to hyperledger-cacti#780 (but does not solve it completely) Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
that referenced
this issue
Apr 17, 2021
Also adding a logger object so that the test ledger can be a little more chatty while starting up. Related to #780 (but does not solve it completely) Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Jul 20, 2021
…ledger-cacti#780 Added logging to all 3 of the test ledger classes that are being used which are taking up most of the boot time. Now users can see the setup process as it chugs along step by step and in general be much more confident while waiting that things are indeed happening instead of the container just being in a zombie state. Also added an additional point in the README.md file claryfying that one needs to have a working installation of docker on their machine. Decided to not go into any more detail than that because the (linked) docker for desktop documentation is the best/most robust resrouces available there is and it would be hard to compete with it if we were to produce our own installation instructions. Fixes hyperledger-cacti#780 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
that referenced
this issue
Jul 22, 2021
Added logging to all 3 of the test ledger classes that are being used which are taking up most of the boot time. Now users can see the setup process as it chugs along step by step and in general be much more confident while waiting that things are indeed happening instead of the container just being in a zombie state. Also added an additional point in the README.md file claryfying that one needs to have a working installation of docker on their machine. Decided to not go into any more detail than that because the (linked) docker for desktop documentation is the best/most robust resrouces available there is and it would be hard to compete with it if we were to produce our own installation instructions. Fixes #780 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
hanxu12
pushed a commit
to hanxu12/cactus
that referenced
this issue
Jul 26, 2021
…ledger-cacti#780 Added logging to all 3 of the test ledger classes that are being used which are taking up most of the boot time. Now users can see the setup process as it chugs along step by step and in general be much more confident while waiting that things are indeed happening instead of the container just being in a zombie state. Also added an additional point in the README.md file claryfying that one needs to have a working installation of docker on their machine. Decided to not go into any more detail than that because the (linked) docker for desktop documentation is the best/most robust resrouces available there is and it would be hard to compete with it if we were to produce our own installation instructions. Fixes hyperledger-cacti#780 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> Signed-off-by: hxlaf <xuhan@lafayette.edu>
RafaelAPB
pushed a commit
to RafaelAPB/blockchain-integration-framework
that referenced
this issue
Mar 9, 2022
…ledger-cacti#780 Added logging to all 3 of the test ledger classes that are being used which are taking up most of the boot time. Now users can see the setup process as it chugs along step by step and in general be much more confident while waiting that things are indeed happening instead of the container just being in a zombie state. Also added an additional point in the README.md file claryfying that one needs to have a working installation of docker on their machine. Decided to not go into any more detail than that because the (linked) docker for desktop documentation is the best/most robust resrouces available there is and it would be hard to compete with it if we were to produce our own installation instructions. Fixes hyperledger-cacti#780 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Developer_Experience
documentation
Improvements or additions to documentation
enhancement
New feature or request
Describe the bug
The container appears as if it hung because it takes a long time to download the AIO images and it's not saying anything in the logs for that period of time.
To Reproduce
Launch the example container as instructed by the readme and watch how it appears to hang for about 10 minutes while it is actually hard at work setting everything up.
Expected behavior
Logs should show a little more liveness so people don't abandon the example assuming that it's broken.
The demo has an adequate amount of documentation around what conditions, exactly, it needs to work.
Logs/Stack traces
N/A
Screenshots
N/A
Cloud provider or hardware configuration:
Dev machine
Operating system name, version, build:
N/A
Hyperledger Cactus release version or commit (git rev-parse --short HEAD):
main
@ 0.4.1Hyperledger Cactus Plugins/Connectors Used
N/A
Additional context
N/A
cc: @takeutak @sfuji822 @hartm @jonathan-m-hamilton @AzaharaC @jordigiam @kikoncuo @jagpreetsinghsasan
The text was updated successfully, but these errors were encountered: