Dashboard: Fix NFT Collection creation error reported twice #7868
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
WalkthroughRemoved try/catch error handling from NFT deployment, minting, claim-condition, and admin flows in the NFT creation page. Deployment now sets a contractAddress ref and emits reportContractDeployed, then enqueues background association with the project; imports simplified and utilities unchanged. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant CreateNFTPage
participant Chain as Blockchain
participant Project as ProjectService
User->>CreateNFTPage: Deploy Contract (ERC721/1155)
CreateNFTPage->>Chain: deployContract(ercType, params)
Chain-->>CreateNFTPage: contractAddress
CreateNFTPage->>CreateNFTPage: contractAddressRef.set(address)
CreateNFTPage->>Project: addContractToProject.mutateAsync(address)
CreateNFTPage->>Project: reportContractDeployed({address, chainId, contractName, deploymentType, publisher})
User->>CreateNFTPage: Lazy Mint NFTs
CreateNFTPage->>Chain: mintLazy(address, metadata)
User->>CreateNFTPage: Set Claim Conditions
CreateNFTPage->>Chain: setClaimConditions(address, conditions)
User->>CreateNFTPage: Set Admins
CreateNFTPage->>Chain: setAdmins(address, admins)
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Warning Review ran into problems🔥 ProblemsErrors were encountered while retrieving linked issues. Errors (1)
✨ Finishing Touches
🧪 Generate unit tests
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has required the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
MananTank
changed the title
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #7868 +/- ##
==========================================
- Coverage 56.54% 56.54% -0.01%
==========================================
Files 904 904
Lines 58592 58592
Branches 4145 4144 -1
==========================================
- Hits 33131 33129 -2
- Misses 25355 25357 +2
Partials 106 106
🚀 New features to boost your workflow:
|
size-limit report 📦
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (4)
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/tokens/create/nft/create-nft-page.tsx (4)
95-131: Deployment flow refactor looks solid; consider lazy-loading deploy helpers to keep bundle leanThe deterministic branch for 721 vs 1155 and param mapping look correct. To reduce initial bundle size in this client component, consider dynamic-importing the deploy helpers inside this async path.
Example refactor (inside
handleContractDeploy):// at the start of the function const deploys = await import("thirdweb/deploys"); // then use: if (ercType === "erc721") { contractAddress = await deploys.deployERC721Contract({ /* ... */ }); } else { contractAddress = await deploys.deployERC1155Contract({ /* ... */ }); }This defers loading
thirdweb/deploysuntil the user actually deploys a contract.
133-142: Make analytics non-blocking and set the ref before reportingIf analytics throws (network/ad-blockers), it could interrupt the flow. Set the ref first and wrap reporting in a no-op try/catch to avoid blocking deployment UX.
Apply this diff:
- reportContractDeployed({ - address: contractAddress, - chainId: Number(collectionInfo.chain), - contractName: contractType, - deploymentType: "asset", - publisher: "deployer.thirdweb.eth", - }); - - contractAddressRef.current = contractAddress; + contractAddressRef.current = contractAddress; + try { + reportContractDeployed({ + address: contractAddress, + chainId: Number(collectionInfo.chain), + contractName: contractType, + deploymentType: "asset", + publisher: "deployer.thirdweb.eth", + }); + } catch { + // ignore analytics errors + }Please confirm
reportContractDeployedexpectscontractNameas the on-chain contract id (e.g., "DropERC721"/"DropERC1155") and not the generic "NFTCollection" used in someuseTrackcalls elsewhere.
336-339: Guard against empty admin updates to avoid a no-op multicallIf
adminsToAddis empty,encodedTxsis empty andmulticallmay be unnecessary or could throw depending on implementation. Skip sending the tx in that case.Apply this diff:
- await sendAndConfirmTransaction({ - account, - transaction: tx, - }); + if (encodedTxs.length > 0) { + await sendAndConfirmTransaction({ + account, + transaction: tx, + }); + }
143-151: Usemutate()for fire-and-forget to prevent unhandled promise rejectionsThe
mutateAsynccall returns a Promise that, when not handled, can result in uncaught errors in the console. Since this should run in the background, switch to the non-async version:- addContractToProject.mutateAsync({ + addContractToProject.mutate({ chainId: collectionInfo.chain, contractAddress: contractAddress, contractType: ercType === "erc721" ? "DropERC721" : "DropERC1155", deploymentType: "asset", projectId: props.projectId, teamId: props.teamId, });The hook’s
chainIdparameter is already typed as astring, so there’s no need to coerce it withNumber(...).
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (1)
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/tokens/create/nft/create-nft-page.tsx(6 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
**/*.{ts,tsx}
📄 CodeRabbit Inference Engine (CLAUDE.md)
**/*.{ts,tsx}: Write idiomatic TypeScript with explicit function declarations and return types
Limit each file to one stateless, single-responsibility function for clarity
Re-use shared types from@/typesor localtypes.tsbarrels
Prefer type aliases over interface except for nominal shapes
Avoidanyandunknownunless unavoidable; narrow generics when possible
Choose composition over inheritance; leverage utility types (Partial,Pick, etc.)
Comment only ambiguous logic; avoid restating TypeScript in prose
Files:
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/tokens/create/nft/create-nft-page.tsx
**/*.{ts,tsx,js,jsx}
📄 CodeRabbit Inference Engine (CLAUDE.md)
Load heavy dependencies inside async paths to keep initial bundle lean (lazy loading)
Files:
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/tokens/create/nft/create-nft-page.tsx
apps/{dashboard,playground-web}/**/*.{ts,tsx}
📄 CodeRabbit Inference Engine (CLAUDE.md)
apps/{dashboard,playground-web}/**/*.{ts,tsx}: Import UI primitives from@/components/ui/*(Button, Input, Select, Tabs, Card, Sidebar, Badge, Separator) in dashboard and playground apps
UseNavLinkfor internal navigation with automatic active states in dashboard and playground apps
Use Tailwind CSS only – no inline styles or CSS modules
Usecn()from@/lib/utilsfor conditional class logic
Use design system tokens (e.g.,bg-card,border-border,text-muted-foreground)
Server Components (Node edge): Start files withimport "server-only";
Client Components (browser): Begin files with'use client';
Always callgetAuthToken()to retrieve JWT from cookies on server side
UseAuthorization: Bearerheader – never embed tokens in URLs
Return typed results (e.g.,Project[],User[]) – avoidany
Wrap client-side data fetching calls in React Query (@tanstack/react-query)
Use descriptive, stablequeryKeysfor React Query cache hits
ConfigurestaleTime/cacheTimein React Query based on freshness (default ≥ 60s)
Keep tokens secret via internal API routes or server actions
Never importposthog-jsin server components
Files:
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/tokens/create/nft/create-nft-page.tsx
🧠 Learnings (4)
📚 Learning: 2025-06-10T00:50:20.795Z
Learnt from: MananTank
PR: thirdweb-dev/js#7315
File: apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/assets/create/nft/launch-nft.tsx:153-226
Timestamp: 2025-06-10T00:50:20.795Z
Learning: In apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/assets/create/nft/launch-nft.tsx, the updateStatus function correctly expects a complete MultiStepState["status"] object. For pending states, { type: "pending" } is the entire status object. For error states, { type: "error", message: React.ReactNode } is the entire status object. The current code incorrectly spreads the entire step object instead of passing just the status object.
Applied to files:
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/tokens/create/nft/create-nft-page.tsx
📚 Learning: 2025-06-24T21:38:03.155Z
Learnt from: MananTank
PR: thirdweb-dev/js#7434
File: apps/dashboard/src/app/(app)/team/~/~/contract/[chain]/[contractAddress]/components/project-selector.tsx:62-76
Timestamp: 2025-06-24T21:38:03.155Z
Learning: In the project-selector.tsx component for contract imports, the addToProject.mutate() call is intentionally not awaited (fire-and-forget pattern) to allow immediate navigation to the contract page while the import happens in the background. This is a deliberate design choice to prioritize user experience.
Applied to files:
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/tokens/create/nft/create-nft-page.tsx
📚 Learning: 2025-06-13T13:50:08.622Z
Learnt from: MananTank
PR: thirdweb-dev/js#7332
File: apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/public-pages/nft/overview/nft-drop-claim.tsx:170-178
Timestamp: 2025-06-13T13:50:08.622Z
Learning: In event-tracking (`useTrack`) calls across the dashboard, the team intentionally keeps `contractType` generic as `"NFTCollection"` even for ERC-721 drops; contract differentiation is handled via the `ercType` field instead.
Applied to files:
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/tokens/create/nft/create-nft-page.tsx
📚 Learning: 2025-06-10T00:46:00.514Z
Learnt from: MananTank
PR: thirdweb-dev/js#7315
File: apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/assets/create/nft/form.ts:25-42
Timestamp: 2025-06-10T00:46:00.514Z
Learning: In NFT creation functions, the setClaimConditions function signatures are intentionally different between ERC721 and ERC1155. ERC721 setClaimConditions accepts the full CreateNFTFormValues, while ERC1155 setClaimConditions accepts a custom object with nftCollectionInfo and nftBatch parameters because it processes batches differently than the entire form data.
Applied to files:
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/tokens/create/nft/create-nft-page.tsx
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
- GitHub Check: E2E Tests (pnpm, webpack)
- GitHub Check: Size
- GitHub Check: Lint Packages
- GitHub Check: Analyze (javascript)
🔇 Additional comments (4)
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/tokens/create/nft/create-nft-page.tsx (4)
26-26: LGTM: Analytics import matches PR goalKeeping only
reportContractDeployed(and removing error-tracking duplications elsewhere) aligns with the objective to avoid double error events.
180-183: Direct await is fine; ensure UI surfaces errorsRemoving try/catch here is fine if upstream UI handles promise rejections uniformly. Verify that
CreateNFTPageUIor its caller surfaces transaction errors to the user.Confirm that
CreateNFTPageUIwraps these calls with error handling (toast/dialog/state) so rejections are user-visible.
220-223: Same note as above for claim conditions (ERC721)Awaiting without local try/catch is fine if errors are handled upstream.
291-294: Same note as above for claim conditions (ERC1155 multicall)LGTM. The multicall encoding is correct; ensuring upstream error surfacing is enough.
Merge activity
|
<!--
## title your PR with this format: "[SDK/Dashboard/Portal] Feature/Fix: Concise title for the changes"
If you did not copy the branch name from Linear, paste the issue tag here (format is TEAM-0000):
## Notes for the reviewer
Anything important to call out? Be sure to also clarify these in your comments.
## How to test
Unit tests, playground, etc.
-->
<!-- start pr-codex -->
---
## PR-Codex overview
This PR focuses on refactoring the `CreateNFTPage` component in `create-nft-page.tsx` to streamline contract deployment processes and improve error handling by removing redundant code and optimizing the reporting of contract deployment.
### Detailed summary
- Removed the import of `reportAssetCreationFailed`.
- Simplified the contract deployment logic for `erc721` and `erc1155`.
- Moved the `reportContractDeployed` call directly after contract creation.
- Eliminated redundant error handling in several transaction functions.
- Updated calls to `sendAndConfirmTransaction` to remove try-catch blocks.
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit
- New Features
- None
- Refactor
- Streamlined NFT creation flows for a smoother experience: deterministic ERC721/ERC1155 deployment, simplified lazy minting, claim condition setup, and admin assignment.
- Contracts are automatically linked to the project in the background after deployment.
- Chores
- Improved post-deployment tracking by recording deployed contract details (address, chain, name, type, publisher) for better observability.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
graphite-app
bot
force-pushed
the
08-19-dashboard_fix_nft_collection_creation_error_tracked_twice
branch
from
980f97c to
e0ab3d5
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (3)
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/tokens/create/nft/create-nft-page.tsx (3)
106-107: Guard against invalid BigInt conversions for royalties.
BigInt(sales.royaltyBps)will throw ifroyaltyBpsis an empty string or otherwise invalid. Given form inputs can be blank or stringly-typed, consider a safe coerce with a default.Apply this diff in both ERC721 and ERC1155 branches:
- royaltyBps: BigInt(sales.royaltyBps), + royaltyBps: BigInt(sales.royaltyBps || 0),Also applies to: 123-124
141-151: Run project-association truly in the background and avoid unhandled rejections.
mutateAsyncreturns a Promise. As-is, a failure here will generate an unhandled promise rejection (noise, potential UI test flakiness). Also, you already computedcontractType; reuse it here.Apply this diff:
- addContractToProject.mutateAsync({ - chainId: collectionInfo.chain, - contractAddress: contractAddress, - contractType: ercType === "erc721" ? "DropERC721" : "DropERC1155", - deploymentType: "asset", - projectId: props.projectId, - teamId: props.teamId, - }); + void addContractToProject + .mutateAsync({ + // ensure number if hook expects numeric chainId; otherwise keep as-is + chainId: Number(collectionInfo.chain), + contractAddress, + contractType, // reuse computed value + deploymentType: "asset", + projectId: props.projectId, + teamId: props.teamId, + }) + .catch(() => { + // intentionally ignored (background task). Optionally log with a non-intrusive tracker. + });If
chainIdis meant to remain a string in this hook, keepcollectionInfo.chainand skip theNumber(...).
95-95: Add explicit return types per repo TS guideline.Minor nit to match the dashboard coding guidelines. Recommend adding explicit return types to these functions:
Example signatures:
async function handleContractDeploy(/* ... */): Promise<{ contractAddress: string }> { /* ... */ } async function handleLazyMintNFTs(/* ... */): Promise<void> { /* ... */ } async function handleSetClaimConditionsERC721(/* ... */): Promise<void> { /* ... */ } async function handleSetClaimConditionsERC1155(/* ... */): Promise<void> { /* ... */ } async function handleSetAdmins(/* ... */): Promise<void> { /* ... */ }
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (1)
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/tokens/create/nft/create-nft-page.tsx(6 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
**/*.{ts,tsx}
📄 CodeRabbit Inference Engine (CLAUDE.md)
**/*.{ts,tsx}: Write idiomatic TypeScript with explicit function declarations and return types
Limit each file to one stateless, single-responsibility function for clarity
Re-use shared types from@/typesor localtypes.tsbarrels
Prefer type aliases over interface except for nominal shapes
Avoidanyandunknownunless unavoidable; narrow generics when possible
Choose composition over inheritance; leverage utility types (Partial,Pick, etc.)
Comment only ambiguous logic; avoid restating TypeScript in prose
Files:
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/tokens/create/nft/create-nft-page.tsx
**/*.{ts,tsx,js,jsx}
📄 CodeRabbit Inference Engine (CLAUDE.md)
Load heavy dependencies inside async paths to keep initial bundle lean (lazy loading)
Files:
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/tokens/create/nft/create-nft-page.tsx
apps/{dashboard,playground-web}/**/*.{ts,tsx}
📄 CodeRabbit Inference Engine (CLAUDE.md)
apps/{dashboard,playground-web}/**/*.{ts,tsx}: Import UI primitives from@/components/ui/*(Button, Input, Select, Tabs, Card, Sidebar, Badge, Separator) in dashboard and playground apps
UseNavLinkfor internal navigation with automatic active states in dashboard and playground apps
Use Tailwind CSS only – no inline styles or CSS modules
Usecn()from@/lib/utilsfor conditional class logic
Use design system tokens (e.g.,bg-card,border-border,text-muted-foreground)
Server Components (Node edge): Start files withimport "server-only";
Client Components (browser): Begin files with'use client';
Always callgetAuthToken()to retrieve JWT from cookies on server side
UseAuthorization: Bearerheader – never embed tokens in URLs
Return typed results (e.g.,Project[],User[]) – avoidany
Wrap client-side data fetching calls in React Query (@tanstack/react-query)
Use descriptive, stablequeryKeysfor React Query cache hits
ConfigurestaleTime/cacheTimein React Query based on freshness (default ≥ 60s)
Keep tokens secret via internal API routes or server actions
Never importposthog-jsin server components
Files:
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/tokens/create/nft/create-nft-page.tsx
🧠 Learnings (3)
📚 Learning: 2025-06-10T00:50:20.795Z
Learnt from: MananTank
PR: thirdweb-dev/js#7315
File: apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/assets/create/nft/launch-nft.tsx:153-226
Timestamp: 2025-06-10T00:50:20.795Z
Learning: In apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/assets/create/nft/launch-nft.tsx, the updateStatus function correctly expects a complete MultiStepState["status"] object. For pending states, { type: "pending" } is the entire status object. For error states, { type: "error", message: React.ReactNode } is the entire status object. The current code incorrectly spreads the entire step object instead of passing just the status object.
Applied to files:
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/tokens/create/nft/create-nft-page.tsx
📚 Learning: 2025-06-13T13:50:08.622Z
Learnt from: MananTank
PR: thirdweb-dev/js#7332
File: apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/public-pages/nft/overview/nft-drop-claim.tsx:170-178
Timestamp: 2025-06-13T13:50:08.622Z
Learning: In event-tracking (`useTrack`) calls across the dashboard, the team intentionally keeps `contractType` generic as `"NFTCollection"` even for ERC-721 drops; contract differentiation is handled via the `ercType` field instead.
Applied to files:
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/tokens/create/nft/create-nft-page.tsx
📚 Learning: 2025-06-10T00:46:00.514Z
Learnt from: MananTank
PR: thirdweb-dev/js#7315
File: apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/assets/create/nft/form.ts:25-42
Timestamp: 2025-06-10T00:46:00.514Z
Learning: In NFT creation functions, the setClaimConditions function signatures are intentionally different between ERC721 and ERC1155. ERC721 setClaimConditions accepts the full CreateNFTFormValues, while ERC1155 setClaimConditions accepts a custom object with nftCollectionInfo and nftBatch parameters because it processes batches differently than the entire form data.
Applied to files:
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/tokens/create/nft/create-nft-page.tsx
🧬 Code Graph Analysis (1)
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/tokens/create/nft/create-nft-page.tsx (2)
apps/dashboard/src/@/analytics/report.ts (1)
reportContractDeployed(21-29)packages/thirdweb/src/exports/thirdweb.ts (1)
sendAndConfirmTransaction(155-155)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (8)
- GitHub Check: E2E Tests (pnpm, esbuild)
- GitHub Check: Size
- GitHub Check: E2E Tests (pnpm, vite)
- GitHub Check: E2E Tests (pnpm, webpack)
- GitHub Check: Unit Tests
- GitHub Check: Build Packages
- GitHub Check: Lint Packages
- GitHub Check: Analyze (javascript)
🔇 Additional comments (7)
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/tokens/create/nft/create-nft-page.tsx (7)
26-26: Good move: only keep success analytics (reportContractDeployed).This aligns with the PR goal to avoid double-reporting failures and limits tracking to successful deploys.
133-139: Analytics emitted only after successful deploy — correct placement.The payload matches
reportContractDeployed’s expected shape. This should prevent duplicate error reports while preserving success tracking.
153-155: Helpful return shape.Returning
{ contractAddress }keeps the UI step orchestration clear.
180-183: Lean path: let errors bubble to the UI.Removing local try/catch for
sendAndConfirmTransactionhere simplifies control flow and avoids duplicate error tracking.
220-223: Same here — simplified error flow.Awaiting and letting the caller handle errors is the right trade-off for consistent UX and telemetry.
291-294: Batch claim-conditions commit is clean.Multicall + single confirmation with centralized error handling looks good.
336-339: Admin role grants: centralized confirmation, no redundant try/catch.Looks good; transaction errors will be handled by the caller once.
graphite-app
bot
deleted the
08-19-dashboard_fix_nft_collection_creation_error_tracked_twice
branch
PR-Codex overview
This PR focuses on refactoring the
CreateNFTPagecomponent in thecreate-nft-page.tsxfile by removing redundant error handling, simplifying code structure, and retaining essential functionality related to NFT contract creation and deployment.Detailed summary
reportAssetCreationFailed.try-catchblocks.sendAndConfirmTransaction.Summary by CodeRabbit