fix: FunctionClauseError caused by blockTimestamp in reth v0.2.0-beta.6

[dirname]

Motivation

In reth v0.2.0-beta.6, the blockTimestamp was added to the meta information (see commit ca82ff5). This change leads to an error:

(FunctionClauseError) no function clause matching in EthereumJSONRPC.Log.entry_to_elixir/1
(ethereum_jsonrpc 6.5.0) lib/ethereum_jsonrpc/log.ex:165: EthereumJSONRPC.Log.entry_to_elixir({"blockTimestamp", "0x6647620b"})

This PR addresses and resolves the issue by ensuring proper handling of the blockTimestamp in the eth_getTransactionReceipt function.

Changelog

Enhancements

• Added handling for blockTimestamp in the eth_getTransactionReceipt function to prevent errors when parsing logs.

Bug Fixes

• Fixed the (FunctionClauseError) no function clause matching in EthereumJSONRPC.Log.entry_to_elixir/1 error caused by the inclusion of blockTimestamp in the meta information.

Incompatible Changes

• None

Upgrading

• No special upgrade steps are required.

Checklist for your Pull Request (PR)

• 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 checked whether I should update the docs and did so by submitting a PR to https://github.com/blockscout/docs
• If I added/changed/removed ENV var, I submitted a PR to https://github.com/blockscout/docs to update the list of env vars at https://github.com/blockscout/docs/blob/master/for-developers/information-and-settings/env-variables.md and I updated the version to master in the Version column. Changes will be reflected in this table: https://docs.blockscout.com/for-developers/information-and-settings/env-variables.
• 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.

[fedor-ivn]

Thank you for the PR! I left one suggestion, but overall LGTM.

[fedor-ivn]

@dirname I've run the CI/CD. Please check the job logs, seems like your fix caused some tests to fail, so they need some adjustments.

[dirname]

@dirname I've run the CI/CD. Please check the job logs, seems like your fix caused some tests to fail, so they need some adjustments.

Thank you for your meticulous attention to the code. I have taken the following steps to confirm with high probability that the CI failure is not related to the changes in this PR:

1. I downloaded the failed CI logs and did not find any calls related to the changes in this PR in the thrown stack.

2. Due to the extensive content of the logs, I used AI to assist in summarizing the errors, which are mainly due to:

3. I reviewed the CI records prior to this change and found similar errors to the ones seen in the current CI failure.

   • https://github.com/blockscout/blockscout/actions/runs/9126911987/job/25180167778

   • https://github.com/blockscout/blockscout/actions/runs/9129359751/job/25103752085

Please let me know if there's anything else need to explore or adjust.

[fedor-ivn]

@dirname, my apologies for the confusion. The test failures indeed don't seem to be related to your changes. They might be due to a flaky test. I'll investigate further and update you soon.