Open eladb opened 2 months ago
@Chriscbr we should discuss this BSOD behavior when some resources can't be resolved (e.g. Failed to start resources
). Off the top of my head, I'm not sure if I can change the behavior without altering the SDK or the simulator.
I tried this:
I also tried to use
containers.Workload
:This happened:
status: Success
,Container
node doesn't have any status indicatorIf I change to "verbose" log level I see:
When I used
containers.Workload
, the Console showed a blue screen:I expected this:
In both cases (
sim.Container
andcontainers.Workload
), I expected the error to show in the logs and theContainer
node to have a RED indicator.Is there a workaround?
No response
Anything else?
No response
Wing Version
No response
Node.js Version
No response
Platform(s)
No response
Community Notes