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

Rullzer prevent inf loop #146

Closed
wants to merge 3 commits into from
Closed

Conversation

DeepDiver1975
Copy link
Member

@DeepDiver1975 DeepDiver1975 commented Sep 25, 2018

Follow up of #70

screenshot from 2018-09-25 15-41-42

@DeepDiver1975 DeepDiver1975 force-pushed the rullzer-prevent_inf_loop branch 2 times, most recently from 10a081f to f652b5d Compare September 25, 2018 14:00
rullzer and others added 2 commits September 25, 2018 16:03
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
@staabm
Copy link
Member

staabm commented Sep 25, 2018

Did you check the test will fail without the patch?
(Feel free to merge the PR of you did)

@rullzer
Copy link

rullzer commented Sep 25, 2018

Thanks for taking over @DeepDiver1975

@DeepDiver1975
Copy link
Member Author

This unit test is not hitting the code in question - I need to have a second look ....

@@ -155,6 +155,25 @@ function testExpectStream() {
);
}

function testEmptyProps() {
Copy link
Member Author

Choose a reason for hiding this comment

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

@rullzer this test should now reflect your description. But this does not trigger the infinite loop. Can I ask you to have a look what's missing? THX

Copy link

Choose a reason for hiding this comment

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

I took a look but it indeed does not seem to be triggered anymore. Maybe there was a different bug. Anyway good it is fixed.

Copy link
Member Author

Choose a reason for hiding this comment

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

Maybe related to an older version. Let's close this for now - let us know if the issue pops up again. THX

@DeepDiver1975
Copy link
Member Author

@rullzer after having another look I can now confirm the bug - here is the fix: #158

Maybe you find the time for some testing? THX

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

Successfully merging this pull request may close these issues.

None yet

3 participants