Skip to content

Conversation

ilevkivskyi
Copy link
Member

A hot fix for a complicated crash due to a poisoned cache (discovered internally).

Copy link
Member

@gvanrossum gvanrossum left a comment

Choose a reason for hiding this comment

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

It's a pretty mysterious fix, I hope Jukka understands it.

'implicit',
'is_aliasing',
'alias_name',
'no_serialize'
Copy link
Member

Choose a reason for hiding this comment

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

Trailing comma. Also add a comment to the end of the docstring about it please.

Copy link
Member Author

Choose a reason for hiding this comment

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

Sorry, already merged before seeing your comment. Will fix this later.

@ilevkivskyi ilevkivskyi merged commit 61f7dd2 into master May 22, 2018
@ilevkivskyi ilevkivskyi deleted the child-crash branch May 22, 2018 20:01
ilevkivskyi added a commit that referenced this pull request May 22, 2018
…t_modules' (#5094)

A hot fix for a complicated crash due to a poisoned cache (discovered internally).
msullivan added a commit that referenced this pull request May 23, 2018
It looks like what happened is that since d.k.e doesn't exist, d.k.v
doesn't depend on d or d.k. However, it still performs parent patching
on them. Since there isn't a dependency, this can occur *before* d is
processed, which causes the parent patched symbol table entries to be
present when serialization occurs. This causes bogus cache entries to
be written.
msullivan added a commit that referenced this pull request May 24, 2018
It looks like what happened is that since d.k.e doesn't exist, d.k.v
doesn't depend on d or d.k. However, it still performs parent patching
on them. Since there isn't a dependency, this can occur *before* d is
processed, which causes the parent patched symbol table entries to be
present when serialization occurs. This causes bogus cache entries to
be written.
ilevkivskyi pushed a commit to ilevkivskyi/mypy that referenced this pull request May 24, 2018
gvanrossum pushed a commit that referenced this pull request May 24, 2018
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.

2 participants