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

fix: always estimate relay gasLimit #4679

Merged
merged 1 commit into from
Dec 18, 2024
Merged

fix: always estimate relay gasLimit #4679

merged 1 commit into from
Dec 18, 2024

Conversation

iamacook
Copy link
Member

@iamacook iamacook commented Dec 17, 2024

What it solves

Resolves inconsistent relays on Arbitrum

How this PR fixes it

When relaying, a gasLimit can be optionally provided in the request. If provided, a 150k buffer is added to it for the Gelato execution overhead. If none is provided, Gelato estimates this on our behalf and no buffer is added.

This explicitly provides the gasLimit to relay requests (if present), otherwise manually estimates it if none is provided.

How to test it

Ensure relay attempts do not fail (particularly on Arbitrum) for the following cases, and that the gasLimit is present in each POST request to the /v1/chains/:chainId/relay:

  1. Safe creation/activation - uses estimation from UI
  2. Bulk execution - estimation occurs in the background

Checklist

  • I've tested the branch on mobile 📱
  • I've documented how it affects the analytics (if at all) 📊
  • I've written a unit/e2e test for it (if applicable) 🧑‍💻

@iamacook iamacook requested a review from tmjssz December 17, 2024 13:46
@iamacook iamacook self-assigned this Dec 17, 2024
Copy link

Arbitrum relay errors

Copy link

github-actions bot commented Dec 17, 2024

@iamacook iamacook marked this pull request as ready for review December 17, 2024 13:48
Copy link

📦 Next.js Bundle Analysis for safe-wallet-web

This analysis was generated by the Next.js Bundle Analysis action. 🤖

⚠️ Global Bundle Size Increased

Page Size (compressed)
global 1016.57 KB (🟡 +91 B)
Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

Two Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page Size (compressed) First Load
/new-safe/advanced-create 26.43 KB (🟡 +1 B) 1.02 MB
/new-safe/create 25.57 KB (🟡 +1 B) 1.02 MB
Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this.

Copy link

Coverage report

St.
Category Percentage Covered / Total
🟡 Statements
73.92% (+0.01% 🔼)
14408/19492
🔴 Branches
51.45% (+0.01% 🔼)
3438/6682
🔴 Functions
56.88% (+0.02% 🔼)
2046/3597
🟡 Lines
75.45% (+0.01% 🔼)
13068/17320
Show new covered files 🐣
St.
File Statements Branches Functions Lines
🟢
... / relaying.ts
100% 100% 100% 100%

Test suite run success

1715 tests passing in 233 suites.

Report generated by 🧪jest coverage report action from ffc3feb

@liliya-soroka
Copy link
Member

Verified

@iamacook iamacook merged commit 1e305f4 into dev Dec 18, 2024
16 checks passed
@iamacook iamacook deleted the relay-gas-limit branch December 18, 2024 10:00
@github-actions github-actions bot locked and limited conversation to collaborators Dec 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants