No description provided.
??? what does this mean?
Probably that when dispatch() (which is what runs a mojit) calls store.expandInstanceForEnv() (which is what calculates all the resources needed to run the mojit) and there is an error, that dispatch() doesn't return the error appropriately (or doesn't catch the exception), eventually leading to neither ac.done() nor ac.error() being called.
Reopened, since it is still a valid problem.
Fixed as part of 0.5.x, we now use the proper adapter.error when something happen within the dispatch workflow.