Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Security Alerts - simulation: internal error: cannot unmarshal string into Go value of type state.StateDB, data: None #30463

Closed
seaona opened this issue Feb 20, 2025 · 2 comments
Assignees
Labels
regression-prod-12.12.0 Regression bug that was found in production in release 12.12.0 Sev2-normal Normal severity; minor loss of service or inconvenience. team-confirmations Push issues to confirmations team type-bug Something isn't working

Comments

@seaona
Copy link
Contributor

seaona commented Feb 20, 2025

Describe the bug

Whenever I trigger a transaction in Optimism, I get the Security Alert error in the API response simulation: internal error: cannot unmarshal string into Go value of type state.StateDB, data: None

Expected behavior

No response

Screenshots/Recordings

cannot-unmarshal-security-alerts.mp4

Steps to reproduce

  1. Select Optimism network
  2. Trigger a tx
  3. See background error and API returns 500 with error

Error messages or log output

Detection stage

In production (default)

Version

12.12.0

Build type

None

Browser

Chrome

Operating system

Linux

Hardware wallet

No response

Additional context

No response

Severity

No response

@seaona seaona added Sev2-normal Normal severity; minor loss of service or inconvenience. team-confirmations Push issues to confirmations team type-bug Something isn't working labels Feb 20, 2025
@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by team Feb 20, 2025
@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by severity Feb 20, 2025
@metamaskbot metamaskbot added the regression-prod-12.12.0 Regression bug that was found in production in release 12.12.0 label Feb 20, 2025
@vinistevam
Copy link
Contributor

vinistevam commented Feb 21, 2025

After some testing, @cryptotavares and I identified that the issue is on the API side, specifically with the Priority Connect RPC used for this chain. The RPC is provided by Infura, and we've already shared the error details with their team. I'll update the ticket once we hear back from them.

@vinistevam
Copy link
Contributor

Infure created an incident https://consensys.slack.com/archives/C08E29KDCBH and after a fix, the RPCs started to work and validate the requests.

@github-project-automation github-project-automation bot moved this from To be fixed to Fixed in Bugs by team Feb 25, 2025
@github-project-automation github-project-automation bot moved this from To be fixed to Fixed in Bugs by severity Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
regression-prod-12.12.0 Regression bug that was found in production in release 12.12.0 Sev2-normal Normal severity; minor loss of service or inconvenience. team-confirmations Push issues to confirmations team type-bug Something isn't working
Projects
Archived in project
Status: Fixed
Development

No branches or pull requests

3 participants