I can't reproduce what you report.

Please confirm that in the "Debugging Target" dialog the upper radiobutton is set and the adjacent input field contains this:

##class( %SourceControl.UnitTest).Test()

And if you comment out the "D $ZF(..." line in the classmethod, then recompile it, does that resolve the problem. If not, then I think this proves that the problem isn't caused by the $ZF() call.

Also to say that if you need a response urgently you should contact InterSystems Support, a.k.a. WRC. This forum (Developer Community) is not a substitute for WRC.

By adding that repo I was able to upgrade to 1.0.255.

I guess that my original Atelier kit was built on Eclipse Mars, and that the developers recently moved up to Eclipse Neon but the upgrade mechanism didn't cope with this. Okay for a pre-release version of Atelier, but let's hope a similar thing doesn't happen once it's become a released and widely deployed tool.

I don't need it, but my experience is that InterSystems consistently maintains a very high standard of technical and professional competence among its staff, so knowing that the author of a post or a response is a member of ISC staff may be useful to readers.

Additionally, an ISC person may find it helpful in the event that someone whose name they do not recognize as being a colleague posts something that might benefit from follow-up through internal channels.

Think of it as equivalent to the way in which Global Summit badges usually give a discreet indication that the wearer is a company employee.

Glad to hear that System Defaults are working for them. My main gripe with that mechanism is how cumbersome Portal's UI is for making the setting in the right place. Added to that, it's just too easy for someone to adjust a setting directly, filing the new setting into the production class where it (a) overrides the System Default and (b) propagates when the class gets transferred.