Skip to content

Conversation

@pombosilva
Copy link
Contributor

@pombosilva pombosilva commented Oct 13, 2025

Fixes WOR-957.

Some changes made to match production behaviors:

  • Limit of 1024 steps is now enforced
  • Don't free retry if the last attempt was due to internal errors
  • Step errors are now being properly thrown to the user

  • Tests
    • Tests included
    • Tests not necessary because: no tests needed, just a simple throw fix
  • Public documentation
    • Cloudflare docs PR(s):
    • Documentation not necessary because: no new features were added
  • Wrangler V3 Backport
    • Wrangler PR:
    • Not necessary because: Workflows were not GA in v3

@pombosilva pombosilva requested review from a team as code owners October 13, 2025 15:05
@changeset-bot
Copy link

changeset-bot bot commented Oct 13, 2025

🦋 Changeset detected

Latest commit: fbcfdaa

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

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

@github-project-automation github-project-automation bot moved this to Untriaged in workers-sdk Oct 13, 2025
@pombosilva pombosilva force-pushed the osilva/add-large-output-error branch from d864181 to a3889cc Compare October 13, 2025 15:06
@pkg-pr-new
Copy link

pkg-pr-new bot commented Oct 13, 2025

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@10966

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@10966

miniflare

npm i https://pkg.pr.new/miniflare@10966

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@10966

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@10966

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@10966

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@10966

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@10966

wrangler

npm i https://pkg.pr.new/wrangler@10966

commit: fbcfdaa

@pombosilva pombosilva changed the title [Workflows] Add correct step errors on local dev [Workflows] Enforce correct step limits and validations on local dev Oct 13, 2025
@pombosilva pombosilva force-pushed the osilva/add-large-output-error branch 4 times, most recently from d958e9d to 5e06f25 Compare October 20, 2025 10:26
@pombosilva pombosilva force-pushed the osilva/add-large-output-error branch from 5e06f25 to fbcfdaa Compare October 20, 2025 14:08
Comment on lines +160 to +162
await this.#engine.abort("Max steps reached");
error.isUserError = true;
throw error;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

abort is a no-op at the moment. From what I see, other usages of it don't throw the error to the caller. Imo you can remove the abort call here and just throw an error like: Aborting engine: Max steps reached. It diverges from production but at least the user is more likely to see the error (?)

Copy link
Contributor

@LuisDuarte1 LuisDuarte1 Oct 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think abort should be implemented for limits to work (otherwise how does one cancel engine execution?) - although we should probably try to hide all workerd noise that abort causes?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

abort is not "aborting" (aka throwing) anything atm. I can make it throw and check the consequences, and (if possible) hide workerd noise

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Untriaged

Development

Successfully merging this pull request may close these issues.

3 participants