The panic resolves to this line, which seems to happen because we aren't checking for nil on ctpConf. Following activateContext, it appears to be possible that we're returning a nil for the configuration if the new context is deep equal to the current context. We should add a nil check to that variable and safely return.
How can we reproduce it?
I'm not even sure... @cwilhit found it and he isn't sure why either.
What happened?
The panic resolves to this line, which seems to happen because we aren't checking for nil on
ctpConf
. FollowingactivateContext
, it appears to be possible that we're returning a nil for the configuration if the new context is deep equal to the current context. We should add a nil check to that variable and safely return.How can we reproduce it?
I'm not even sure... @cwilhit found it and he isn't sure why either.
What environment did it happen in?