Fix bypass nodes slot check only works for precise types

[webfiltered]

Summary

• Follow-up on Fix execution breaks on multi/any-type slots #4864
• Fixes execution when bypassed nodes are directly connected to slots with non-exact type matches (e.g. list of types)

Changes

• Resolves logic issue from last-minute refactor in original design (find => findIndex).

Review Focus

Requires actual in-app testing with custom nodes before merge. May or may not do what it says on the tin.

• Fixes [Dev] ExecutableNodeDTO .#getBypassSlotIndex returns -1 instead of undefined. #5403

┆Issue is synchronized with this Notion page by Unito

[github-actions]

🎭 Playwright Test Results

✅ All tests passed across all browsers!

⏰ Completed at: 09/08/2025, 08:45:53 AM UTC

📊 Test Reports by Browser

---

🎉 Your tests are passing across all browsers!

[AustinMroz]

The fix is good. Here's a minimal, core only reproduction.

The indexing performed prior to the reported error uses Array.at which supports negative indexes. Consequentially, the error can only occur on a node which has no inputs. Virtual nodes generally don't add inputs corresponding to widgets. Since bypassing a subgraph currently also bypasses all inner nodes, any virtual nodes inside a bypassed subgraph (like primitives or a set node) will trigger this bug.

(Though this also suggests that the nodes inside a bypassed subgraph are being explored. This should not be the case, but is a seperate case I've not found a repro for.)