[Dummy] Release/2.19.0 aptos #15642
Closed
[Dummy] Release/2.19.0 aptos #15642
Conversation
This file contains 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
* [Keystone] Disable remote calls to RegisterToWorkflow * Remove failing test --------- Co-authored-by: Cedric Cordenier <[email protected]>
Keystone hotfixes (2.19)
…n multinode state map [v2.19] (#15372) (cherry picked from commit 0cabe54) Co-authored-by: Brandon West <[email protected]>
* Consume latest changeset and update changelog * Update CHANGELOG.md
[KS-590] Auto-approval for workflow spec deletion
* bumping wsrpc (#15549) * Update go.mod * make gomodtidy --------- Co-authored-by: Patrick <[email protected]>
…anch Increase default timeout of remote Executable requests (#15587)
* isolate fix to mercury; more tests
…tfix [Keystone] Standard error message for remote execution errors (#15615)
Bump common to release/2.19.0-aptos branch
* wiring engine histogram buckets through to beholder Client * bumping common * Move metric views (#15515) * bumping common --------- Co-authored-by: Pavel <[email protected]>
* Adds metrics on workflow engine * Adds trigger event metric * Removes comment * metrics: execution duration histograms by status and removing now redundant instrumentation * adding step execution time histogram * fixing data race for global instruments * cleanup + fixing tests * renaming vars somehow fixes broken test * removing short circuit in workferForStepRequest if Vertex call fails * nil guard if Vertex errs * updating workflow.name to workflow.hexName and fixing err log --------- Co-authored-by: patrickhuie19 <[email protected]>
Hotfixes (histogram buckets + hex name + engine beholder metrics)
There was an issue raised [here](https://chainlink-core.slack.com/archives/C06NF17JK9N/p1733437678773739?thread_ts=1733412322.287769&cid=C06NF17JK9N) impacting the chain config dialog of the operator ui, because the chain id is no longer unique now that we work with multichain, we need to handle it better by considering the network and chain id together instead of just chainid. Context: smartcontractkit/operator-ui#97 JIRA: https://smartcontract-it.atlassian.net/browse/DPA-1384
fix(operator-ui): fix duplicate chain id in chain config dialog (#15585)
krebernisak
requested review from
pavel-raykov
and removed request for
a team
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR is used just to trigger CLL node builds and publish to ECR (build pipeline issues)