-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[Bug]: Linea Send
transactions remain in a Pending
state indefinitely unless they are sped up.
#31176
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
Comments
Send
transactions remain in a Pending
state indefinitely unless they are sped up.Send
transactions remain in a Pending
state indefinitely unless they are sped up.
Removing the regression label here. From Slack conversations with Linea team, this is an effect of market conditions rather than tied to a release version. |
…oller` config (#31476) <!-- Please submit this PR as a draft initially. Do not mark it as "Ready for review" until the template has been completely filled out, and PR status checks have passed at least once. --> ## **Description** <!-- Write a short description of the changes included in this pull request, also include relevant motivation and context. Have in mind the following questions: 1. What is the reason for the change? 2. What is the improvement/solution? --> This PR aims to enable update of `txParams` gas updates on every `GasFeeController` update. [](https://codespaces.new/MetaMask/metamask-extension/pull/31476?quickstart=1) ## **Related issues** Fixes: MetaMask/MetaMask-planning#4519 Might be related: #31176 ## **Manual testing steps** N/A ## **Screenshots/Recordings** <!-- If applicable, add screenshots and/or recordings to visualize the before and after of your change. --> ### **Before** <!-- [screenshots/recordings] --> ### **After** <!-- [screenshots/recordings] --> ## **Pre-merge author checklist** - [X] I've followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Extension Coding Standards](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [X] I've completed the PR template to the best of my ability - [X] I’ve included tests if applicable - [X] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [X] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.
@OGPoyraz ![]() Interesting that I see the same behavior in the RC, may be it makes sense to wait for the higher Linea gas? |
I want to summarise what happens in background. We have a special gas fee flow on Linea. Basically what we do is that asking gas estimations via Even if you select I am adding a recording that it succesfully Screen.Recording.2025-04-02.at.09.26.43.movBut I am not sure why we see the error above, because it's an RPC error and I wonder in what circumstances they throw it. If you find consistent way to get this error, please open another task so we can investigate further with Linea team. For this issue - I am considering that it's done as recording shows that it works as expected, again feel free to re-open if it consistently stays on |
Describe the bug
Linea
Send
transactions remain in aPending
state indefinitely unless they are sped up.Some transactions can be confirmed, but other will stuck
Pending
.(STX are not available on Linea)
Gas API response:
https://gas.api.cx.metamask.io/networks/59144/suggestedGasFees
No errors in the network tab:
Expected behavior
Transactions are processed in a timely manner without requiring them to be sped up
Screenshots/Recordings
Screen.Recording.2025-03-20.at.17.03.25.mov
Steps to reproduce
Send
transactionError messages or log output
Detection stage
In production (default)
Version
12.14.1
Build type
None
Browser
Chrome
Operating system
MacOS
Hardware wallet
No response
Additional context
No response
Severity
No response
The text was updated successfully, but these errors were encountered: