Skip to content
This repository has been archived by the owner on May 7, 2024. It is now read-only.

Feature/scripting client #4

Merged
merged 16 commits into from
Mar 27, 2017
Merged

Feature/scripting client #4

merged 16 commits into from
Mar 27, 2017

Conversation

MrMeemus
Copy link
Contributor

Submitting initial PR to get the show going.

There is one test issue when ran on mac regarding the way mac treats CRLF in a text file. Investigating a fix now.

ron added 11 commits March 15, 2017 07:44
…ered dictionary and we want to test against the contents in the input stream it was written to
…ountered, modified tests to reflect this change
…ql tools service side to finalize the event/parameter/response types
…s which would require another loop without invoking readchunk() which would block if there was no more data to read, leaving a message unprocessed in the buffer
@msftclas
Copy link

msftclas commented Mar 24, 2017

@MrMeemus,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot
#Closed

self.assertFalse(test_client.request_thread.isAlive())
self.assertFalse(test_client.response_thread.isAlive())
self.assertEqual(threading.active_count(), 1)

# Response thread should have reach EOF during test execution which should end the response thread.

Copy link
Member

@pensivebrian pensivebrian Mar 24, 2017

Choose a reason for hiding this comment

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

Missing an assert after the comment? #Resolved

Copy link
Contributor Author

Choose a reason for hiding this comment

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

comment was a mistake, fixed in next iteration.


In reply to: 107996156 [](ancestors = 107996156)


test_client.shutdown()
self.assertEqual(threading.active_count(), 1)
# Disabling this test in case this scenario is valid in the future
Copy link
Member

@pensivebrian pensivebrian Mar 24, 2017

Choose a reason for hiding this comment

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

Disabling this test in case this scenario is valid in the future [](start = 4, length = 66)

Can we enable the test as passing with the current behavior. Then, when the scenario is valid, it will fail and we can update the test? #Resolved

Copy link
Contributor Author

Choose a reason for hiding this comment

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

sure I'll add a skip tag to it


In reply to: 107996424 [](ancestors = 107996424)

@pensivebrian
Copy link
Member

Nice!


In reply to: 289101128 [](ancestors = 289101128)

@pensivebrian
Copy link
Member

:shipit:

@@ -2,3 +2,5 @@ enum34==1.1.6
future==0.16.0
pip==9.0.1
setuptools==30.4.0
coverage==4.3.4
Copy link
Member

@pensivebrian pensivebrian Mar 24, 2017

Choose a reason for hiding this comment

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

remove extra line above #Resolved

@MrMeemus MrMeemus merged commit f59a467 into dev Mar 27, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants