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

oldProtocol often nil in ClassDescription>>#notifyRepackage:method:oldProtocol:newProtocol: #13796

Closed
MarcusDenker opened this issue May 24, 2023 · 1 comment · Fixed by #13798 or #13801

Comments

@MarcusDenker
Copy link
Member

Bug description
On the CI we see a lot

 EpMonitor could not log a change. You can enable debugging with "EpMonitor current debugMode: true".

If I do that, I see a lot of teste failing when e.g. running the Newtools debugger tests

For these cases, oldProtocol nil in ClassDescription>>#notifyRepackage:method:oldProtocol:newProtocol: and we get a DNU for #name.

If EpMonitor debugMode is off, the tests are green

@MarcusDenker
Copy link
Member Author

It is strange that EpMonitor does what it thinks is local error handling:

EpMonitor>>#handleError:
	self debugMode
		ifTrue: [ error pass ]
		ifFalse: [ 'EpMonitor could not log a change. You can enable debugging with "EpMonitor current debugMode: true".' traceCr ]

Yet is silences the error not just for Epiciea?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant