Skip to content

Make ivar references safer #3555

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

Merged
merged 1 commit into from
Aug 12, 2019
Merged

Make ivar references safer #3555

merged 1 commit into from
Aug 12, 2019

Conversation

mikehaney24
Copy link
Contributor

Fixes 3547, in theory. This code all goes away/changes with the sqlite refactor, so making it safe is probably sufficient for now. No one was able to reproduce locally, most likely because this is a lifecycle issue.

Fixes 3547, in theory. This code all goes away/changes with the sqlite refactor, so making it safe is probably sufficient for now. No one was able to reproduce locally, most likely because this is a lifecycle issue.
Copy link
Contributor

@maksymmalyhin maksymmalyhin left a comment

Choose a reason for hiding this comment

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

LGTM

@mikehaney24 mikehaney24 merged commit 23e4a63 into master Aug 12, 2019
@mikehaney24 mikehaney24 deleted the mph-fixcrash branch August 12, 2019 18:41
mikehaney24 added a commit that referenced this pull request Aug 12, 2019
Fixes 3547, in theory. This code all goes away/changes with the sqlite refactor, so making it safe is probably sufficient for now. No one was able to reproduce locally, most likely because this is a lifecycle issue.
paulb777 pushed a commit that referenced this pull request Aug 12, 2019
* Make ivar references safer (#3555)

Fixes 3547, in theory. This code all goes away/changes with the sqlite refactor, so making it safe is probably sufficient for now. No one was able to reproduce locally, most likely because this is a lifecycle issue.

* Increment GDT to v1.1.1

GDTCCT has a dep on ~> 1.1, so this incremented version should get picked up.

* Actually use the strongified variables I made
@firebase firebase locked and limited conversation to collaborators Oct 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants