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

Clear Messages About The Process of Peer Creation #103

Open
Almansherov opened this issue May 29, 2018 · 11 comments
Open

Clear Messages About The Process of Peer Creation #103

Almansherov opened this issue May 29, 2018 · 11 comments

Comments

@Almansherov
Copy link
Member

During the peer creation process there are not very clear messages telling user how to behave or what to expect and we have to pay special attention to the messages.

@ibragim13kz
Copy link

ibragim13kz commented Jun 1, 2018

@dilshat @happyaron @liquuid We need to fix those errors. @jadilet @Almansherov FYI, guys.
screenshot from 2018-06-01 16-16-45

@ibragim13kz
Copy link

screenshot from 2018-06-01 16-58-48

@ibragim13kz
Copy link

And @jadilet will fix this one.
screenshot from 2018-06-01 17-03-01

@jadilet jadilet removed their assignment Jun 1, 2018
@ibragim13kz
Copy link

@efeefe Did you face some another error messages during peer creation or I mentioned all of them?

@happyaron
Copy link

happyaron commented Jun 3, 2018

About thisWARNING: apt does not have a stable CLI interface. Use with caution in scripts.

According to apt's man page:

The apt(8) commandline is designed as an end-user tool and it may change behavior between versions. While it tries not to break backward compatibility this is not guaranteed either if a change seems beneficial for interactive use.

All features of apt(8) are available in dedicated APT tools like apt-get(8) and apt-cache(8) as well.  apt(8) just changes the default value of some options (see apt.conf(5) and specifically the Binary scope). So you should prefer using these commands (potentially with some additional options enabled) in your scripts as they keep backward compatibility as much as possible.

So we should replace the usage of apt to apt-get and apt-cache where applicable.

@happyaron
Copy link

This PR (subutai-io/packer#74) is going to solve all the warnings except the rng-tools.service thing.

@efeefe
Copy link
Member

efeefe commented Jun 3, 2018

I've seen only those @ibragim13kz

@ibragim13kz
Copy link

ibragim13kz commented Jun 4, 2018

@jadilet Didn't you fix that?
screenshot from 2018-06-04 19-42-04

@happyaron
Copy link

@ibragim13kz This wasn't mentioned and it's not saying anything scary, is it considered as an error message as well?

@ibragim13kz
Copy link

@happyaron It was not mentioned because this message appeared in consequence of @jadilet changes.

@Almansherov
Copy link
Member Author

Almansherov commented Jun 7, 2018

@happyaron are the last two messages fixed? it is enough to change their colors. When user faces the red messages, she/he starts worrying.

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

No branches or pull requests

7 participants