"OSH eval error while looking for sub-exec"

[abathur]

I encountered a case of resholve falling over when OSH hit during resholve's new nested-resolution routine. resholve should now ~handle this and just print a warning, but I don't have a very good sense of

• how common this warning will be
• what kind of syntax will trigger it
• whether there will be anything smarter resholve should do

I'm hoping to collect some more real reports of this to help figure out if we can just silently ignore these or if it's going to need additional handling.