You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix#7852: avoid reading stale .tasty files from jars
Somehow, if we don't close the classloader used to read .tasty files
from jars, a subsequent compilation run might end up reading a stale
version of the .tasty file which does not exist on disk anymore. I don't
understand why this happens since we don't reuse the classloader itself,
but that's life sometimes ¯\_(ツ)_/¯
0 commit comments