search

inngest / inngest-js

The developer platform for easily building reliable workflows with zero infrastructure for TypeScript & JavaScript
https://www.inngest.com/
GNU General Public License v3.0
414 stars 41 forks source link

[BUG] Local execution fails with StepRun does not belong to Opcode values after 3.12.0 upgrade #490

Closed gwax closed 7 months ago

gwax commented 7 months ago

Describe the bug After upgrading inngest-js to >=3.12.0, I can no longer run pipelines with inngest-cli. Doing so results in the error: Error: error reading generator opcode response: StepRun does not belong to Opcode values

To Reproduce Steps to reproduce the behavior:

  1. Take a working configuration with inngest-js <3.12.0 and inngest-cli 0.23.1
  2. Upgrade inngest-js to >=3.12.0
  3. Start inngest locally
  4. Execute a function

Expected behavior Local execution should work as before

Code snippets / Logs / Screenshots If applicable, add screenshots to help explain your problem.

System info (please complete the following information):

Additional context Add any other context about the problem here.

jpwilliams commented 7 months ago

Hi, @gwax!

Try it with inngest-cli@latest; we usually ship these changes as they move to Cloud, so expect SDKs to work with the latest version.

jpwilliams commented 7 months ago

Closing this as I'm expecting no change.

gwax commented 7 months ago

Yes, the issue turned out to be an unintentionally pinned older version of inngest-cli; thank you.