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.

Sign up for GitHub

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

Jump to bottom

[UX] Fix peer.py client #24

Closed
5 tasks done
mo3rfan opened this issue Dec 8, 2017 · 0 comments
Closed
5 tasks done

[UX] Fix peer.py client #24

mo3rfan opened this issue Dec 8, 2017 · 0 comments
Milestone
Optimal release

Comments

@mo3rfan
Copy link

mo3rfan commented Dec 8, 2017 •
edited
Loading

Right after a call is made to another peer in peer.py, there might be some delay before the "====GOT DC===" message prints out. During this period, the script can get into an error state if something goes into stdin. fix this.

  • Block the stdin during "connecting..." state
  • Route the stdin right after GOT DC to SendString()
  • Fix the aforementioned issue.
  • First message send doesn't occur.
  • Remove unwanted print messages
@mo3rfan mo3rfan added this to the Optimal release milestone Dec 8, 2017
@mo3rfan mo3rfan changed the title [UX] Ensure CLI client doesn't throw errors while in connecting state [UX] Fix peer.py client Dec 8, 2017
@mo3rfan mo3rfan mentioned this issue Dec 8, 2017
Closed
@mo3rfan mo3rfan closed this as completed Dec 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Optimal release
Development

No branches or pull requests
1 participant
@mo3rfan