Skip to content

[pull] main from MetaMask:main#174

Merged
pull[bot] merged 3 commits into
dmrazzy:mainfrom
MetaMask:main
Apr 29, 2025
Merged

[pull] main from MetaMask:main#174
pull[bot] merged 3 commits into
dmrazzy:mainfrom
MetaMask:main

Conversation

@pull
Copy link
Copy Markdown

@pull pull Bot commented Apr 29, 2025

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.1)

Can you help keep this open source service alive? 💖 Please sponsor : )

mcmire and others added 3 commits April 29, 2025 15:06
)

Recently we added some new behavior to NetworkController which will
detect if an Infura RPC endpoint is down and allow for forwarding
traffic to Quicknode automatically. Because this behavior involves
integrating with backend services to enable Quicknode on failure, we are
unsure whether everything will work the way we want to on the first try,
so we want to be able to disable or enable the behavior using feature
flags. That is, when turned off, even if an RPC endpoint has been
configured with failover URLs, network traffic will not be forwarded to
the failovers if the primary is perceived to be down.

There are a couple of things to note about this commit:

- Usually we would have NetworkController listen to
RemoteFeatureFlagController to know when a feature flag was enabled or
disabled and then enable or disable the RPC failover behavior
accordingly. Because we don't intend to keep the feature flag forever,
however, we let the clients do that and we simply expose methods in
NetworkController that can be used manually by the clients.
- The way that the enabling/disabling works is a bit tricky. Naively, we
could create new versions of network client objects that have different
sets of RpcService objects, and replace the existing versions directly
in the network client registry (without updating their IDs). That's a
little weird, though, and it also means that if another controller
caches a network client at any point in time, the cached version would
not be updated. So instead, we take advantage of the fact that when
other controllers interact with a network client, it's really a proxy —
an AutoManagedNetworkClient — and so we can replace the underlying
object (a NetworkClient) without changing the proxy.
…ction (#5714)

## Explanation

Combinining `setAccountName` + `setSelectedAccount` to avoid having 2
update blocks.

## References

N/A

## Changelog

N/A

## Checklist

- [ ] I've updated the test suite for new or updated code as appropriate
- [ ] I've updated documentation (JSDoc, Markdown, etc.) for new or
updated code as appropriate
- [ ] I've communicated my changes to consumers by [updating changelogs
for packages I've
changed](https://github.com/MetaMask/core/tree/main/docs/contributing.md#updating-changelogs),
highlighting breaking changes as necessary
- [ ] I've prepared draft pull requests for clients and consumer
packages to resolve any breaking changes
Minor release of `@metamask/transaction-controller`.
@pull pull Bot added the ⤵️ pull label Apr 29, 2025
@pull pull Bot merged commit b0b9afb into dmrazzy:main Apr 29, 2025
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 29, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants