fix(sdk): return undefined from parseFillLogs on empty logs

[devtechedge]

Summary

parseFillLogs currently builds blockData from logs[0] before checking whether any fill event is present. When callers pass an empty logs array (a valid "no fill found" case), that access throws a TypeError instead of returning undefined.

This change adds an early return for logs.length === 0, matching the existing no-match behavior for non-empty logs that do not contain a fill event.

Changes

• Guard parseFillLogs so an empty logs array returns undefined
• Add unit tests covering empty logs and unrelated non-fill logs

Test plan

• vitest run test/unit/actions/parseFillLogs.test.ts (empty array and non-fill logs both return undefined)
• Reviewers: confirm callers that already treat a missing fill as undefined continue to work as expected

Fixes #268

[vercel]

@devtechedge is attempting to deploy a commit to the UMA Team on Vercel.

A member of the Team first needs to authorize it.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 986fdc6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[devtechedge]

Hi - soft check-in on this one whenever you have a spare moment.

parseFillLogs was reading logs[0] before checking for a fill event, so an empty logs array (a valid "no fill found" case) threw a TypeError instead of returning undefined.

This adds an early logs.length === 0 return so empty input matches the existing no-match behavior, with unit coverage for empty arrays and unrelated non-fill logs (Fixes #268).

The diff stays small in waitForFillTx.ts plus the focused vitest file, and callers that already treat a missing fill as undefined should keep working the same way.

Happy to rebase, rename the guard, or add another case if that helps review - no rush from my side.