mirror of
https://github.com/invoke-ai/InvokeAI
synced 2024-08-30 20:32:17 +00:00
db4763a742
This addresses an edge case where: 1. the workflow references fields that are present on the workflow's nodes, but not on the invocation templates for those nodes and 2. The invocation template for that type does exist This should be a fairly obscure edge case, but could happen if a user fiddled around with the workflow manually. I ran into it as a result of two nodes having accidentally mixed up their invocation types, a problem introduced with a wonky merge commit.
Organization of the source tree: app -- Home of nodes invocations and services assets -- Images and other data files used by InvokeAI backend -- Non-user facing libraries, including the rendering core. configs -- Configuration files used at install and run times frontend -- User-facing scripts, including the CLI and the WebUI version -- Current InvokeAI version string, stored in version/invokeai_version.py