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

docs: update Dev env docs #6633

Closed
wants to merge 1 commit into from

Conversation

KiranShahdadpuri
Copy link
Collaborator

Added more errors and it's solutions which may likely to happen during zulip dev set up.

SSL read: error:00000000:lib(0):func(0):reason(0), errno 104
```

It means that either your network connection is unstable or speed
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A more succinct way to convey this: "It means your internet connection is either unstable or slow. To resolve this, run vagrant up until it works."

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@KiranShahdadpuri why do you prefer to state it as "speed is very less"? 'less' needs another object to be compared to.

==> default: E:Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
```

It means that your local apt repository has got corrupted, which can be resolved by executing the command:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"has been corrupted"

@KiranShahdadpuri
Copy link
Collaborator Author

@rht did the changes as you said. Please, review it.

@@ -711,7 +711,30 @@ This is equivalent of running a halt followed by an up (aka rebooting
the guest). After this, you can do `vagrant provision` and `vagrant
ssh`.

#### ssh connection closed by remote host
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@KiranShahdadpuri It appears that you accidentally removed this line: "#### ssh connection closed by remote host", am I correct?

SSL read: error:00000000:lib(0):func(0):reason(0), errno 104
```

It means that either your internet connection is unstable or speed
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"or slow" is still better, I think.

@rht
Copy link
Collaborator

rht commented Oct 8, 2017

@KiranShahdadpuri thanks for writing this up, for the purpose of preventing other developer's frustration when they run vagrant !

@KiranShahdadpuri
Copy link
Collaborator Author

yes, sorry I had accidentally removed that. I updated it now.

@rht
Copy link
Collaborator

rht commented Oct 10, 2017

@KiranShahdadpuri Hmm??? you had just removed your edits, and duplicated the ssh section. Did some error happen while you was doing a rebase?

@KiranShahdadpuri
Copy link
Collaborator Author

KiranShahdadpuri commented Oct 11, 2017 via email

@KiranShahdadpuri
Copy link
Collaborator Author

updated.

@rht
Copy link
Collaborator

rht commented Oct 12, 2017

@KiranShahdadpuri can you squash all the commits into 1 commit. The steps are:

  1. git rebase -i HEAD~4. This will open up a text editor showing the most recent 4 commits
  2. From the second line to the fourth line, replace pick with fixup.
  3. Save and exit the text editor

@rht
Copy link
Collaborator

rht commented Oct 12, 2017

Any guide to recover that commit?

Lol, how did you do this? There is always git reflog tho.

@KiranShahdadpuri
Copy link
Collaborator Author

Lol, how did you do this? There is always git reflog tho.
Was unaware. Had got that googling.
Updated the changes.

@zulipbot
Copy link
Member

Heads up @KiranShahdadpuri, we just merged some commits that conflict with the changes your made in this pull request! You can review this repository's recent commits to see where the conflicts occur. Please rebase your feature branch against the upstream/master branch and resolve your pull request's merge conflicts accordingly.

@timabbott
Copy link
Sponsor Member

Sorry for the slow review @KiranShahdadpuri! I reviewed and merged this, after a few small tweaks to the language. Thanks for doing this !

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

Successfully merging this pull request may close these issues.

None yet

4 participants