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

Epicea does not log super class changes #4869

Open
demarey opened this issue Oct 9, 2019 · 5 comments

Comments

@demarey
Copy link
Contributor

commented Oct 9, 2019

After an image crash, I noticed that some events are not logged / lost by Epicea.
For example, I had A subclass: #Foo that I changed to B subclass: #Foo

This change does not appear in the session log.

@demarey demarey added this to the 8.0.0 milestone Oct 9, 2019
@demarey

This comment has been minimized.

Copy link
Contributor Author

commented Oct 10, 2019

@tinchodias

This comment has been minimized.

Copy link
Contributor

commented Oct 14, 2019

Hi @demarey this is in Pharo 7, right? did you try in 8?

@tinchodias

This comment has been minimized.

Copy link
Contributor

commented Oct 14, 2019

Ah, now I see you tagged as 8 milestone. But I don't delete my answer because I still suspect it happens in 7 and that it would be fixed by backporting #2959

@demarey

This comment has been minimized.

Copy link
Contributor Author

commented Oct 14, 2019

Hi @tinchodias

Yes, it happens in Pharo 7. Did not try on Pharo 8

@tinchodias

This comment has been minimized.

Copy link
Contributor

commented Oct 14, 2019

Then it should be fixed via #4908

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.