test: ntegration tests main rebase #266
Closed
Conversation
This file contains 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
# What ❔ Add transaction error reason transformer. ## Why ❔ To unsure error and reason are transformed correctly. ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [X] PR title corresponds to the body of PR (we generate changelog entries from PRs).
# What ❔ Add graceful shutdown timeout. ## Why ❔ To ensure that we can gracefully process all incoming HTTP requests before shutting down the service. ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [X] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [X] Tests for the changes have been added / updated.
# What ❔ Add filter by transfer type to the address transfers endpoint ## Why ❔ It is useful to be able to get a list of transfers of certain type for address. For example get list of withdrawals.
# What ❔ - add script to migrate address transfer type ## Why ❔ - standard migration would not be able to complete, script uses parallel connections and updates data in small chunks.
# What ❔ New goerli deprecation message with a specific deprecation date: <img width="1143" alt="image" src="https://github.com/matter-labs/block-explorer/assets/6553665/3bb8b99e-4998-40c4-8100-e4144fa8aa81"> ## Why ❔ To notify users when the deprecation is gonna happen. ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [X] PR title corresponds to the body of PR (we generate changelog entries from PRs).
# What ❔ 1. Log timestamp in ISO8601 format. 2. Internal retries for `DataFetcherService`. ## Why ❔ 1. To have timestamps properly processed so logs are in the correct order. 2. Otherwise in case of an error the whole batch is retried which is unnecessary. ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [X] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [X] Tests for the changes have been added / updated.
# What ❔ Get rid of the separate interceptor that transforms `BigNumber` to string, accomplish the same result overriding `BigNumber` `toJSON` function. ## Why ❔ Separate interceptor is not optimal especially for blocks with lots of related data, which we btw expect to see more often with higher TPS. There are blocks where all related info weights 2Mb+ and it takes ~200ms to transform the whole response object by the interceptor. Since after the transformation JSON serialisation happens anyway, we can just override `toJSON` for `BigNumber` and it will be picked up during JSON serialisation. I checked that with this change generated response is the same. Performance improvement for large payloads (2Mb+): 1. Serialisation with interceptor (interceptor + json serialiser): avg 290ms 2. Serialisation with overridden `toJSON` (json serialiser): avg 34ms But most important event loop is not blocked for a long time. ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [X] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [X] Tests for the changes have been added / updated.
# What ❔ Remove goerli network. ## Why ❔ Clean up the codebase since we stop supporting Goerli network. ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [X] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [X] Tests for the changes have been added / updated. - [X] Documentation comments have been added / updated.
# What ❔ Increase default timeout settings. ## Why ❔ To make sure explorer can handle large transactions. ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [X] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [X] Tests for the changes have been added / updated.
# What ❔ Rename root hash on the block screen to block hash. ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [X] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [X] Tests for the changes have been added / updated.
# What ❔ Fix docker compose by applying the same updates that were done in [local-setup](https://github.com/matter-labs/local-setup.) ## Why ❔ Old docker compose doesn't work with the latest `local-node` docker image. ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [X] PR title corresponds to the body of PR (we generate changelog entries from PRs).
# What ❔ Fix explorer so that a defined bridge address is not required. ## Why ❔ In-memory node doesn't have L1 network and bridge addresses defined. This fix make explorer work with the in-memory node. ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [X] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [X] Tests for the changes have been added / updated.
# What ❔ Migrate firebase jobs on self-hosted runners. ## Why ❔ For make contribution in frontend app from forks ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [x] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [x] Tests for the changes have been added / updated. - [x] Documentation comments have been added / updated.
|
Visit the preview URL for this PR: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What ❔
Why ❔
Checklist