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

(fix) - avoid stale closurses #2005

Merged
merged 4 commits into from
Oct 15, 2019
Merged

(fix) - avoid stale closurses #2005

merged 4 commits into from
Oct 15, 2019

Conversation

JoviDeCroock
Copy link
Member

@JoviDeCroock JoviDeCroock commented Oct 12, 2019

Problem here being I can't seem to reproduce this in a test :/

Fixes: #1998

Edit:
Shaves -9B

@coveralls
Copy link

coveralls commented Oct 12, 2019

Coverage Status

Coverage increased (+0.1%) to 99.767% when pulling a315e22 on fix/contextHijack into b46885c on master.

Copy link
Member

@cristianbote cristianbote left a comment

Choose a reason for hiding this comment

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

👍 thanks @JoviDeCroock!

Copy link
Member

@marvinhagemeister marvinhagemeister left a comment

Choose a reason for hiding this comment

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

That's a good one! Amazing work 👍💯

@marvinhagemeister
Copy link
Member

@JoviDeCroock is the comment about not being able to reproduce the issue in tests still relevant?

@JoviDeCroock
Copy link
Member Author

@marvinhagemeister yes it is. I'm probably making a mistake somewhere ^^

@AlmeroSteyn
Copy link

Thank you for working on this! The effort and the tool is much appreciated.

@cristianbote
Copy link
Member

Test case added -- it was a tricky one for sure

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.

Context being hijacked by second instance of application
5 participants