Misattributed import failed bug

It seems if you have a broken custom node directory, you can cause other completely working nodes to appear as failed imports in the "installed" node list in the manager UI. This could make debugging a problem harder for users.

This issue can be reproduced by creating a new folder with an empty set of nodes. If the NODE_CLASS_MAPPINGS are not present in the init file in that folder, the error will be displayed correctly in the initial ComfyUI terminal output, but the subsequent node in that list (despite functioning perfectly) will be highlighted in red in the manager UI presumably by a mismatch from a created offset.

Reproduce the issue with a custom node folder whose init file lacks NODE_CLASS_MAPPINGS, then compare the terminal output with the manager UI's installed-node status sequence. Trace how import failures are associated with nodes and verify that a working node after the broken one is no longer highlighted as failed.

Written by the indexing model from the issue text.