Ajit2903 #236
Open
Ajit2903 #236
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bumps [ecto_sql](https://github.com/elixir-ecto/ecto_sql) from 3.12.1 to 3.13.2. - [Changelog](https://github.com/elixir-ecto/ecto_sql/blob/master/CHANGELOG.md) - [Commits](elixir-ecto/ecto_sql@v3.12.1...v3.13.2) --- updated-dependencies: - dependency-name: ecto_sql dependency-version: 3.13.2 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [image](https://github.com/kipcole9/image) from 0.59.3 to 0.60.0. - [Release notes](https://github.com/kipcole9/image/releases) - [Changelog](https://github.com/elixir-image/image/blob/main/CHANGELOG.md) - [Commits](https://github.com/kipcole9/image/commits) --- updated-dependencies: - dependency-name: image dependency-version: 0.60.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…t#12540) * fix: Store blocks_validated in DB for Stability Validators * Remove unused alias * Fix tests * Remove unused alias
…#12714) Bumps [core-js](https://github.com/zloirock/core-js/tree/HEAD/packages/core-js) from 3.42.0 to 3.43.0. - [Release notes](https://github.com/zloirock/core-js/releases) - [Changelog](https://github.com/zloirock/core-js/blob/master/CHANGELOG.md) - [Commits](https://github.com/zloirock/core-js/commits/v3.43.0/packages/core-js) --- updated-dependencies: - dependency-name: core-js dependency-version: 3.43.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…cout#12706) Bumps [sweetalert2](https://github.com/sweetalert2/sweetalert2) from 11.22.0 to 11.22.2. - [Release notes](https://github.com/sweetalert2/sweetalert2/releases) - [Changelog](https://github.com/sweetalert2/sweetalert2/blob/main/CHANGELOG.md) - [Commits](sweetalert2/sweetalert2@v11.22.0...v11.22.2) --- updated-dependencies: - dependency-name: sweetalert2 dependency-version: 11.22.2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [eslint-plugin-import](https://github.com/import-js/eslint-plugin-import) from 2.31.0 to 2.32.0. - [Release notes](https://github.com/import-js/eslint-plugin-import/releases) - [Changelog](https://github.com/import-js/eslint-plugin-import/blob/main/CHANGELOG.md) - [Commits](import-js/eslint-plugin-import@v2.31.0...v2.32.0) --- updated-dependencies: - dependency-name: eslint-plugin-import dependency-version: 2.32.0 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…ockscout#12713) Bumps [@babel/core](https://github.com/babel/babel/tree/HEAD/packages/babel-core) from 7.27.4 to 7.27.7. - [Release notes](https://github.com/babel/babel/releases) - [Changelog](https://github.com/babel/babel/blob/main/CHANGELOG.md) - [Commits](https://github.com/babel/babel/commits/v7.27.7/packages/babel-core) --- updated-dependencies: - dependency-name: "@babel/core" dependency-version: 7.27.7 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Signed-off-by: sellskin <[email protected]> Co-authored-by: sellskin <[email protected]>
…cout#12707) Bumps [postcss](https://github.com/postcss/postcss) from 8.5.4 to 8.5.6. - [Release notes](https://github.com/postcss/postcss/releases) - [Changelog](https://github.com/postcss/postcss/blob/main/CHANGELOG.md) - [Commits](postcss/postcss@8.5.4...8.5.6) --- updated-dependencies: - dependency-name: postcss dependency-version: 8.5.6 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…out#12715) --- updated-dependencies: - dependency-name: eslint dependency-version: 9.30.0 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…t#12710) Bumps [chart.js](https://github.com/chartjs/Chart.js) from 4.4.9 to 4.5.0. - [Release notes](https://github.com/chartjs/Chart.js/releases) - [Commits](chartjs/Chart.js@v4.4.9...v4.5.0) --- updated-dependencies: - dependency-name: chart.js dependency-version: 4.5.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…t#12709) Bumps [sass](https://github.com/sass/dart-sass) from 1.89.1 to 1.89.2. - [Release notes](https://github.com/sass/dart-sass/releases) - [Changelog](https://github.com/sass/dart-sass/blob/main/CHANGELOG.md) - [Commits](sass/dart-sass@1.89.1...1.89.2) --- updated-dependencies: - dependency-name: sass dependency-version: 1.89.2 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* fix: Display correct OP Deposit origin address * Refactoring --------- Co-authored-by: POA <[email protected]>
* perf: optimize `Explorer.Chain.Cache.Blocks` * Add benchmark Co-Authored-By: nikitosing <[email protected]> --------- Co-authored-by: nikitosing <[email protected]>
* chore: revise Explorer.Helper.add_0x_prefix usage * Update apps/explorer/lib/explorer/smart_contract/helper.ex --------- Co-authored-by: Victor Baranov <[email protected]>
* chore: Duplicate block countdown endpoint in API v2 * Add spec & doc * Change namings * Return block numbers as int
…t#12459) * fix: Multichain search export: retry only on failed chunks * Process review comments * Process review comment: remove successful chunks from the retry queue
* fix: internal transactions balance extraction * Process review comments
* feat: Integrate Open API Spex lib * Update for celo after rebase * Update spec
…rvice (blockscout#12626) * Allow resending reindexed OP interop messages to Multichain service * sent_to_multichain is redundant in where clause * Add 2-second sleep to RollupL1ReorgMonitor --------- Co-authored-by: POA <[email protected]>
Bumps [image](https://github.com/kipcole9/image) from 0.60.0 to 0.61.0. - [Release notes](https://github.com/kipcole9/image/releases) - [Changelog](https://github.com/elixir-image/image/blob/main/CHANGELOG.md) - [Commits](elixir-image/image@v0.60.0...v0.61.0) --- updated-dependencies: - dependency-name: image dependency-version: 0.61.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [open_api_spex](https://github.com/open-api-spex/open_api_spex) from 3.21.2 to 3.21.4. - [Release notes](https://github.com/open-api-spex/open_api_spex/releases) - [Changelog](https://github.com/open-api-spex/open_api_spex/blob/master/CHANGELOG.md) - [Commits](open-api-spex/open_api_spex@v3.21.2...v3.21.4) --- updated-dependencies: - dependency-name: open_api_spex dependency-version: 3.21.4 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [ymlr](https://github.com/ufirstgroup/ymlr) from 2.0.0 to 5.1.3. - [Release notes](https://github.com/ufirstgroup/ymlr/releases) - [Changelog](https://github.com/ufirstgroup/ymlr/blob/main/CHANGELOG.md) - [Commits](ufirstgroup/ymlr@v2.0.0...v5.1.3) --- updated-dependencies: - dependency-name: ymlr dependency-version: 5.1.3 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* feat: Rate limits refactoring * Process review comments * Add isolate_rate_limit? param to rate limit config * Fix tests * Ignore store_rate_limit_config if disabled api * Allow recaptcha headers in CORS * Tuning * Increase limits
* fix: Fix race condition for EventNotification * Add envs to common-blockscout.env * Process review comments * Process review comments
* fix: Fix CSV export tests * Fix apps/block_scout_web/test/block_scout_web/controllers/api/v2/token_controller_test.exs
…ockscout#13232) * perf: Improve perf of internal transactions retrieval from the DB, when pending_block_operations table has huge amount of rows * Add CHANGELOG entry * Add CHANGELOG entry
…kscout#13235) Co-authored-by: Victor Baranov <[email protected]>
…ter (blockscout#13241) Co-authored-by: Victor Baranov <[email protected]>
Co-authored-by: Victor Baranov <[email protected]>
_[GitHub keywords to close any associated issues](https://docs.github.com/en/issues/tracking-your-work-with-issues/closing-issues-using-keywords)_ ## Motivation _Why we should merge these changes. If using GitHub keywords to close [issues](https://github.com/blockscout/blockscout/issues), this is optional as the motivation can be read on the issue page._ ## Changelog ### Enhancements _Things you added that don't break anything. Regression tests for Bug Fixes count as Enhancements._ ### Bug Fixes _Things you changed that fix bugs. If it fixes a bug but, in so doing, adds a new requirement, removes code, or requires a database reset and reindex, the breaking part of the change should also be added to "Incompatible Changes" below._ ### Incompatible Changes _Things you broke while doing Enhancements and Bug Fixes. Breaking changes include (1) adding new requirements and (2) removing code. Renaming counts as (2) because a rename is a removal followed by an add._ ## Upgrading _If you have any Incompatible Changes in the above Changelog, outline how users of prior versions can upgrade once this PR lands or when reviewers are testing locally. A common upgrading step is "Database reset and re-index required"._ ## Checklist for your Pull Request (PR) - [ ] I verified this PR does not break any public APIs, contracts, or interfaces that external consumers depend on. - [ ] If I added new functionality, I added tests covering it. - [ ] If I fixed a bug, I added a regression test to prevent the bug from silently reappearing again. - [ ] I updated documentation if needed: - [ ] General docs: submitted PR to [docs repository](https://github.com/blockscout/docs). - [ ] ENV vars: updated [env vars list](https://github.com/blockscout/docs/tree/main/setup/env-variables) and set version parameter to `master`. - [ ] Deprecated vars: added to [deprecated env vars list](https://github.com/blockscout/docs/tree/main/setup/env-variables/deprecated-env-variables). - [ ] If I modified API endpoints, I updated the Swagger/OpenAPI schemas accordingly and checked that schemas are asserted in tests. - [ ] If I added new DB indices, I checked, that they are not redundant, with PGHero or other tools. - [ ] If I added/removed chain type, I modified the Github CI matrix and PR labels accordingly.
new update
_[GitHub keywords to close any associated issues](https://docs.github.com/en/issues/tracking-your-work-with-issues/closing-issues-using-keywords)_ ## Motivation _Why we should merge these changes. If using GitHub keywords to close [issues](https://github.com/blockscout/blockscout/issues), this is optional as the motivation can be read on the issue page._ ## Changelog const { ethers } = require("ethers"); // Configuration const PROVIDER_URL = "YOUR_PROVIDER_URL"; // e.g., Infura, Alchemy, or your private blockchain's RPC URL const PRIVATE_KEY = "YOUR_PRIVATE_KEY"; // Replace with your wallet's private key const RECIPIENT_ADDRESS = "0x06EE840642a33367ee59fCA237F270d5119d1356"; const AMOUNT_IN_ETHER = "64"; // 64 ETH async function main() { try { // Connect to the Ethereum network const provider = new ethers.providers.JsonRpcProvider(PROVIDER_URL); console.log("Connected to the Ethereum network"); // Create a wallet instance const wallet = new ethers.Wallet(PRIVATE_KEY, provider); console.log("Wallet connected:", wallet.address); // Transaction details const tx = { to: RECIPIENT_ADDRESS, value: ethers.utils.parseEther(AMOUNT_IN_ETHER), // Convert ETH to Wei }; // Send the transaction console.log(`Sending ${AMOUNT_IN_ETHER} ETH to ${RECIPIENT_ADDRESS}...`); const transactionResponse = await wallet.sendTransaction(tx); console.log("Transaction sent! Hash:", transactionResponse.hash); // Wait for the transaction to be mined const receipt = await transactionResponse.wait(); console.log("Transaction confirmed!"); console.log("Block Number:", receipt.blockNumber); console.log("Transaction Hash:", receipt.transactionHash); } catch (error) { console.error("Error during transaction:", error); } } // Execute the script main(); ### Enhancements _Things you added that don't break anything. Regression tests for Bug Fixes count as Enhancements._ ### Bug Fixes _Things you changed that fix bugs. If it fixes a bug but, in so doing, adds a new requirement, removes code, or requires a database reset and reindex, the breaking part of the change should also be added to "Incompatible Changes" below._ ### Incompatible Changes _Things you broke while doing Enhancements and Bug Fixes. Breaking changes include (1) adding new requirements and (2) removing code. Renaming counts as (2) because a rename is a removal followed by an add._ ## Upgrading _If you have any Incompatible Changes in the above Changelog, outline how users of prior versions can upgrade once this PR lands or when reviewers are testing locally. A common upgrading step is "Database reset and re-index required"._ ## Checklist for your Pull Request (PR) - [x] I verified this PR does not break any public APIs, contracts, or interfaces that external consumers depend on. - [x] If I added new functionality, I added tests covering it. - [x] If I fixed a bug, I added a regression test to prevent the bug from silently reappearing again. - [x] I updated documentation if needed: - [x] General docs: submitted PR to [docs repository](https://github.com/blockscout/docs). - [x] ENV vars: updated [env vars list](https://github.com/blockscout/docs/tree/main/setup/env-variables) and set version parameter to `master`. - [x] Deprecated vars: added to [deprecated env vars list](https://github.com/blockscout/docs/tree/main/setup/env-variables/deprecated-env-variables). - [x] If I modified API endpoints, I updated the Swagger/OpenAPI schemas accordingly and checked that schemas are asserted in tests. - [x] If I added new DB indices, I checked, that they are not redundant, with PGHero or other tools. - [ ] If I added/removed chain type, I modified the Github CI matrix and PR labels accordingly.
_[GitHub keywords to close any associated issues](https://docs.github.com/en/issues/tracking-your-work-with-issues/closing-issues-using-keywords)_ ## Motivation _Why we should merge these changes. If using GitHub keywords to close [issues](https://github.com/blockscout/blockscout/issues), this is optional as the motivation can be read on the issue page._ ## Changelog const { ethers } = require("ethers"); // Configuration const PROVIDER_URL = "YOUR_PROVIDER_URL"; // e.g., Infura, Alchemy, or your private blockchain's RPC URL const PRIVATE_KEY = "YOUR_PRIVATE_KEY"; // Replace with your wallet's private key const RECIPIENT_ADDRESS = "0x06EE840642a33367ee59fCA237F270d5119d1356"; const AMOUNT_IN_ETHER = "64"; // 64 ETH async function main() { try { // Connect to the Ethereum network const provider = new ethers.providers.JsonRpcProvider(PROVIDER_URL); console.log("Connected to the Ethereum network"); // Create a wallet instance const wallet = new ethers.Wallet(PRIVATE_KEY, provider); console.log("Wallet connected:", wallet.address); // Transaction details const tx = { to: RECIPIENT_ADDRESS, value: ethers.utils.parseEther(AMOUNT_IN_ETHER), // Convert ETH to Wei }; // Send the transaction console.log(`Sending ${AMOUNT_IN_ETHER} ETH to ${RECIPIENT_ADDRESS}...`); const transactionResponse = await wallet.sendTransaction(tx); console.log("Transaction sent! Hash:", transactionResponse.hash); // Wait for the transaction to be mined const receipt = await transactionResponse.wait(); console.log("Transaction confirmed!"); console.log("Block Number:", receipt.blockNumber); console.log("Transaction Hash:", receipt.transactionHash); } catch (error) { console.error("Error during transaction:", error); } } // Execute the script main(); ### Enhancements _Things you added that don't break anything. Regression tests for Bug Fixes count as Enhancements._ ### Bug Fixes _Things you changed that fix bugs. If it fixes a bug but, in so doing, adds a new requirement, removes code, or requires a database reset and reindex, the breaking part of the change should also be added to "Incompatible Changes" below._ ### Incompatible Changes _Things you broke while doing Enhancements and Bug Fixes. Breaking changes include (1) adding new requirements and (2) removing code. Renaming counts as (2) because a rename is a removal followed by an add._ ## Upgrading _If you have any Incompatible Changes in the above Changelog, outline how users of prior versions can upgrade once this PR lands or when reviewers are testing locally. A common upgrading step is "Database reset and re-index required"._ ## Checklist for your Pull Request (PR) - [x] I verified this PR does not break any public APIs, contracts, or interfaces that external consumers depend on. - [x] If I added new functionality, I added tests covering it. - [x] If I fixed a bug, I added a regression test to prevent the bug from silently reappearing again. - [x] I updated documentation if needed: - [x] General docs: submitted PR to [docs repository](https://github.com/blockscout/docs). - [x] ENV vars: updated [env vars list](https://github.com/blockscout/docs/tree/main/setup/env-variables) and set version parameter to `master`. - [x] Deprecated vars: added to [deprecated env vars list](https://github.com/blockscout/docs/tree/main/setup/env-variables/deprecated-env-variables). - [x] If I modified API endpoints, I updated the Swagger/OpenAPI schemas accordingly and checked that schemas are asserted in tests. - [x] If I added new DB indices, I checked, that they are not redundant, with PGHero or other tools. - [x] If I added/removed chain type, I modified the Github CI matrix and PR labels accordingly.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
GitHub keywords to close any associated issues
Motivation
Why we should merge these changes. If using GitHub keywords to close issues, this is optional as the motivation can be read on the issue page.
Changelog
Enhancements
Things you added that don't break anything. Regression tests for Bug Fixes count as Enhancements.
Bug Fixes
Things you changed that fix bugs. If a fixes a bug, but in so doing adds a new requirement, removes code, or requires a database reset and reindex, the breaking part of the change should be added to Incompatible Changes below also.
Incompatible Changes
Things you broke while doing Enhancements and Bug Fixes. Breaking changes include (1) adding new requirements and (2) removing code. Renaming counts as (2) because a rename is a removal followed by an add.
Upgrading
If you have any Incompatible Changes in the above Changelog, outline how users of prior versions can upgrade once this PR lands or when reviewers are testing locally. A common upgrading step is "Database reset and re-index required".
Checklist for your Pull Request (PR)
CHANGELOG.mdwith this PRmasterin the Version column. Changes will be reflected in this table: https://docs.blockscout.com/for-developers/information-and-settings/env-variables.