Release v0.39.0

[rafal-ch]

Version v0.39.0

Added

• 2324: Added metrics for sync, async processor and for all GraphQL queries.
• 2320: Added new CLI flag graphql-max-resolver-recursive-depth to limit recursion within resolver. The default value it "1".

Fixed

• 2320: Prevent /health and /v1/health from being throttled by the concurrency limiter.
• 2322: Set the salt of genesis contracts to zero on execution.
• 2324: Ignore peer if we already are syncing transactions from it.

Breaking

• 2320: Reject queries that are recursive during the resolution of the query.

Changed

Breaking

• 2311: Changed the text of the error returned by the executor if gas overflows.

What's Changed

• chore(executor): instrument errors to be more meaningful by @rymnc in chore(executor): instrument errors to be more meaningful #2311
• fix(dummy_da_block_costs): remove dependency on polling_interval and use channel instead by @rymnc in fix(dummy_da_block_costs): remove dependency on polling_interval and use channel instead #2314
• fix(txpool): Error in GossipsubMessageAcceptance variant docstrings by @netrome in fix(txpool): Error in GossipsubMessageAcceptance variant docstrings #2316
• refactor: Eager returns in txpool_v2::service::Task::run by @netrome in refactor: Eager returns in txpool_v2::service::Task::run #2325
• fix(api_service): exclude health checks from throttling with ConcurrencyLimitLayer by @rymnc in fix(api_service): exclude health checks from throttling with ConcurrencyLimitLayer #2320
• Remove the normalize_rewards_and_costs() function by @rafal-ch in Remove the normalize_rewards_and_costs() function #2293
• fix(genesis): set salt of contract on execution of genesis state configuration by @rymnc in fix(genesis): set salt of contract on execution of genesis state configuration #2322
• Fixing the issue with duplicate transaction synchronization processes by @xgreenx in Fixing the issue with duplicate transaction synchronization processes #2324
• Reject queries that are recursive during the resolution by @xgreenx in Reject queries that are recursive during the resolution #2330

Full Changelog: v0.38.0...v0.39.0

[acerone85]

Question mostly for me to understand: do we update the genesis state transition version at every release? Or would there be cases when this does not need to be done (e.g. if we don't change the executor at all between two releases)?

[xgreenx]

We do this for each release, but yeah, it is a problem in the case when we need to update only off-chain logic.

It would be nice if all off-chain logic lived in another place, in this case we don't need to release fuel-core often itself