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

Printing issues in Command Prompt #56

Open
varriaza opened this issue Oct 14, 2016 · 7 comments
Open

Printing issues in Command Prompt #56

varriaza opened this issue Oct 14, 2016 · 7 comments

Comments

@varriaza
Copy link
Collaborator

varriaza commented Oct 14, 2016

While working on the Adu5A and Adu5B I noticed that sometimes the console would attempt to print out two things at once which resulted in a garbled mess (see picture 1, the hello is also part of the weird print out). After updating to the current verison as of 10/14/2016 9:51 AM it got even worse (see picture 2). I also cannot connect to any databases either on my version or peng's Heroku.
Picture 1
command prompt printing problem

Picture 2
command prompt printing problem 2

@varriaza
Copy link
Collaborator Author

Also on an unrelated note, @sylarcp would you be able to tell me a database that has both adu5A and adu5B data at the same time because I have not found any?

@sylarcp
Copy link
Owner

sylarcp commented Oct 18, 2016

I found I could not connect to any database. Then I fixed it.
Now you can continue work on this issue.
And I confirmed that 128.175.112.58, anita_0104d contain both adu5 A and B data.

@varriaza
Copy link
Collaborator Author

It appears that in connect.py it prints out the "before conn", "conn" and "------ None" as seen above. It also prints out the error should the code find one however, it does not appear to be entering the exception in that file. Thus the problem appears to be elsewhere where errors are printed.

@sylarcp
Copy link
Owner

sylarcp commented Oct 18, 2016

Have you git pull?

On Oct 18, 2016, at 4:15 PM, varriaza notifications@github.com wrote:

It appears that in connect.py it prints out the "before conn", "conn" and "------ None" as seen above. It also prints out the error should the code find one however, it does not appear to be entering the exception in that file. Thus the problem appears to be elsewhere where errors are printed.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub #56 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/AOrTtCv-1ifWftVzQVPLUVwENxu4MgDuks5q1SjdgaJpZM4KXCOc.

@varriaza
Copy link
Collaborator Author

No, but I am now. I just wanted to test on what I had and write down what happens.

@sylarcp
Copy link
Owner

sylarcp commented Oct 18, 2016

OK, just pull and you can connect to the database. Thanks.

On Oct 18, 2016, at 4:17 PM, varriaza notifications@github.com wrote:

No, but I am now. I just wanted to test on what I had and write down what happens.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub #56 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/AOrTtCJx0Q8zKsGRSt6VdLMUNABrciF6ks5q1SlWgaJpZM4KXCOc.

@varriaza
Copy link
Collaborator Author

Connecting works. Thanks for fixing that.

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

No branches or pull requests

2 participants