Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix false indeterminate function warning #757

Merged
merged 2 commits into from
Nov 25, 2024

Conversation

jpwilliams
Copy link
Member

@jpwilliams jpwilliams commented Nov 25, 2024

Summary

Fixes a false indeterminate function warning when using edited inputs in step state.

=================================================

⚠️  Function may be indeterminate

This is expected if a function is updated in the middle of a run, but may indicate a bug if not. We found new steps before seeing all previous steps, which may indicate that the function is non-deterministic. This may cause unexpected behaviour as Inngest executes your function.

=================================================

We show this warning when finding a brand new step that the Executor doesn't yet know about. If we've found this and there's a difference between the number of steps we've previously found and the amount of steps the Executor has given us, we display the warning.

The value we used for these counts was the fulfilled boolean, which tracks whether a step will resolve or reject based on Executor state. This, however, doesn't account for known steps when the Executor provides an input instead.

This PR adds a small hasStepState boolean to each found step, such that we know if the Executor has any knowledge of the step without scoping it down to just resolve/reject.

Checklist

  • Added a docs PR that references this PR N/A Bug fix
  • Added unit/integration tests N/A Warning log
  • Added changesets if applicable

Related

@jpwilliams jpwilliams added the Bug Something isn't working label Nov 25, 2024
@jpwilliams jpwilliams self-assigned this Nov 25, 2024
Copy link

changeset-bot bot commented Nov 25, 2024

🦋 Changeset detected

Latest commit: 0a680b4

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
inngest Patch

Not sure what this means? Click here to learn what changesets are.

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

@inngest-release-bot inngest-release-bot added the 📦 inngest Affects the `inngest` package label Nov 25, 2024
@jpwilliams jpwilliams merged commit 36b61f0 into main Nov 25, 2024
49 checks passed
@jpwilliams jpwilliams deleted the fix/false-indeterminate-warning branch November 25, 2024 13:37
jpwilliams pushed a commit that referenced this pull request Nov 25, 2024
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.


# Releases
## inngest@3.26.3

### Patch Changes

- [#758](#758)
[`8af4c25`](8af4c25)
Thanks [@jpwilliams](https://github.com/jpwilliams)! - Fix OpenAI
`tools` types - not properly scoped

- [#757](#757)
[`36b61f0`](36b61f0)
Thanks [@jpwilliams](https://github.com/jpwilliams)! - Fix false
indeterminate function warning

- [#756](#756)
[`7916c06`](7916c06)
Thanks [@jpwilliams](https://github.com/jpwilliams)! - Expose a type
that lists the `AiAdapter` for each format

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working 📦 inngest Affects the `inngest` package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants