You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(runtime): Improve error handling and stack trace tracking
Enhance error reporting by separating error messages and stack traces
in workflow runs and steps. This change allows for more detailed error
logging and better debugging capabilities by storing both the error
message and its full stack trace separately.
Key changes:
- Add `errorStack` field to workflow runs and steps
- Separate error message from stack trace during error processing
- Improve error logging with more context and detailed information
Copy file name to clipboardExpand all lines: CLAUDE.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -160,4 +160,5 @@ This project uses pnpm with workspace configuration. The required version is spe
160
160
- All changed packages should be included in the changeset. Never include unchanged packages.
161
161
- All changes should be marked as "patch". Never use "major" or "minor" modes.
162
162
- Remember to always build any packages that get changed before running downstream tests like e2e tests in the workbench
163
-
- Remember that changes made to one workbench should propogate to all other workbenches. The workflows should typically only be written once inside the example workbench and symlinked into all the other workbenches
163
+
- Remember that changes made to one workbench should propogate to all other workbenches. The workflows should typically only be written once inside the example workbench and symlinked into all the other workbenches
164
+
- When writing changeset, use the `pnpm changeset` command from the root of the repo. Keep the changesets terse (see existing changesets for examples). Try to amke chagnesets that are specific to each modified package so they are targeted. Ensure that any breaking changes are marked as "**BREAKING CHANGE**
0 commit comments