skipping deployments for wf metadata that doesnt pass validation#21201
Open
patrickhuie19 wants to merge 1 commit intodevelopfrom
Open
skipping deployments for wf metadata that doesnt pass validation#21201patrickhuie19 wants to merge 1 commit intodevelopfrom
patrickhuie19 wants to merge 1 commit intodevelopfrom
Conversation
Contributor
|
👋 patrickhuie19, thanks for creating this pull request! To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team. Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks! |
Contributor
|
I see you updated files related to
|
|
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If you check workflow worker staging metrics, we're seeing a high volume of events with org ID missing in the staging env. A little log splunking shows its all from cases where the metadata is exhibiting a zero workflow owner address, a known bug that was fixed (and redeployed) for our prod wf registry contract.