Report On: Fetch commits

Project Overview

The Bitcoin project is a highly active and continuously evolving initiative aimed at enhancing the functionality and security of Bitcoin Core, the software backbone of the Bitcoin network. The project is managed by a diverse group of contributors who work on improving the codebase, addressing issues, and implementing new features to ensure the robustness and efficiency of the network. The overall state of the project is healthy, with regular updates and a clear trajectory towards improving performance, security, and usability.

Recent Commits and Activities

Branch: master

0 days ago

• Commit: Merge bitcoin/bitcoin#30217: depends: Update Boost download link
• Author: Hennadii Stepanov (hebasto)
• Files Changed:
  • depends/packages/boost.mk (+1, -1)
• Collaborators: maflcko
• Summary: Updated Boost download link due to migration from boostorg.jfrog.io to archives.boost.io.

1 day ago

• Commit: Merge bitcoin/bitcoin#30215: doc: JSON-RPC request Content-Type is application/json
• Author: Luke Dashjr (luke-jr)
• Files Changed:
  • doc/JSON-RPC-interface.md (+2, -2)
  • src/rpc/util.cpp (+2, -2)
  • src/test/rpc_tests.cpp (+3, -3)
• Collaborators: laanwj, tdb3
• Summary: Specified JSON content type in RPC examples.

1 day ago

• Commit: Merge bitcoin/bitcoin#30134: fuzz: add more coverage for ScriptPubKeyMan
• Author: Bruno Garcia (brunoerg)
• Files Changed:
  • src/wallet/test/fuzz/scriptpubkeyman.cpp (+16, -0)
• Collaborators: marcofleon, murchandamus
• Summary: Added more coverage for ScriptPubKeyMan.

1 day ago

• Commit: Merge bitcoin/bitcoin#30216: build: Fix building fuzz binary on on SunOS / illumos
• Author: Hennadii Stepanov (hebasto)
• Files Changed:
  • src/Makefile.test.include (+1, -1)
• Collaborators: maflcko
• Summary: Fixed issue with building the fuzz binary on SunOS / illumos.

1 day ago

• Commit: Merge bitcoin/bitcoin#30167: doc, rpc: Release notes and follow-ups for #29612
• Author: Fabian Jahr (fjahr)
• Files Changed:
  • doc/release-notes-29612.md (added +8)
  • src/kernel/chainparams.cpp (+1, -1)
  • src/kernel/chainparams.h (+1, -1)
  • src/node/utxo_snapshot.h (+13, -5)
  • src/rpc/blockchain.cpp (+2, -2)
  • src/test/fuzz/deserialize.cpp (+2, -1)
  • src/test/fuzz/utxo_snapshot.cpp (+2, -1)
  • src/test/util/chainstate.h (+1, -1)
  • src/validation.cpp (+2, -2)
  • test/functional/feature_assumeutxo.py (+2, -1)
• Collaborators: maflcko, theStack
• Summary: Added release notes for #29612 and addressed post-merge review comments.

1 day ago

• Commit: Merge bitcoin/bitcoin#30192: build: remove --enable-lcov-branch-coverage
• Author: fanquake
• Files Changed:
  • configure.ac (+1, -9)
  • doc/developer-notes.md (+4, -0)
  • doc/release-notes-30192.md (added +6)
• Collaborators: theuni, hebasto
• Summary: Removed --enable-lcov-branch-coverage to support lcov 2.x.

1 day ago

• Commit: Merge bitcoin/bitcoin#30186: fuzz: increase txorphan harness stability
• Author: MarcoFalke (marcofleon)
• Files Changed:
  • src/txorphanage.cpp (+2, -3)
  • src/txorphanage.h (+3, -0)
• Collaborators: maflcko, dergoegge, glozow
• Summary: Improved stability of the txorphan fuzz harness by moving nNextSweep to be a member of the TxOrphanage class.

Developer Contributions

Hennadii Stepanov (hebasto)

Recent Activity:

• Authored commits related to updating Boost download link and fixing build issues on SunOS / illumos.

Patterns:

• Focused on maintaining dependencies and ensuring compatibility across different platforms.

Conclusion: Hennadii Stepanov's contributions are crucial for maintaining build stability and ensuring smooth dependency management.

Luke Dashjr (luke-jr)

Recent Activity:

• Specified JSON content type in RPC examples.

Patterns:

• Focused on improving documentation and ensuring compliance with standards.

Conclusion: Luke Dashjr's work helps improve clarity and standard compliance in documentation.

Bruno Garcia (brunoerg)

Recent Activity:

• Added more coverage for ScriptPubKeyMan.

Patterns:

• Focused on increasing test coverage for wallet-related components.

Conclusion: Bruno Garcia's contributions are essential for ensuring robust testing of wallet functionalities.

Conclusion

The recent activities within the Bitcoin project demonstrate a strong focus on refining the software through detailed documentation updates, rigorous testing improvements, and continuous integration enhancements. This ongoing development effort is crucial for maintaining Bitcoin Core's reliability as a cornerstone of the Bitcoin network. The team shows a collaborative approach with clear roles in dependency management (hebasto), documentation improvement (luke-jr), and test coverage enhancement (brunoerg).

Report On: Fetch issues

Analysis of Recent Activity

Summary of Recent Activity

Since the previous analysis, there has been a notable amount of activity in the project. This includes the creation of new issues, updates to existing issues, and the closure of several issues. Below is a detailed breakdown of the recent activity:

Open Issues

New Issues

1. #30221: "wallet: Ensure best block matches wallet scan state" - Implements changes to ensure m_last_block_processed and m_last_block_processed_height fields are in sync with the block locator stored in the wallet.
2. #30219: "Lint: Support running individual lint checks" - Adds support for running individual tests in the rust lint suite by passing --lint=LINT_TO_RUN to the lint runner.
3. #30218: "refactor: remove unused CKey::Negate method" - Removes an unused method that was introduced for an obsolete protocol.
4. #30214: "refactor: Improve assumeutxo state representation" - Refactors assumeutxo code to make it more maintainable and improve performance.
5. #30212: "rename TransactionErrors: MISSING_INPUTS and ALREADY_IN_CHAIN" - Renames transaction errors for better clarity.
6. #30211: "fuzz: Make FuzzedSock fuzz friendlier" - Improves the FuzzedSock class to make it more suitable for fuzzing.
7. #30210: "build: use UCRT runtime for Windows (release) binaries" - Proposes switching to the modern UCRT runtime for Windows builds.
8. #30209: "Make Transport independent of CNetMessage and CSerializedNetMsg" - Refactors Transport class to decouple it from specific message types.
9. #30207: "validation: Improve, document and test logic for chains building on invalid blocks" - Improves handling and documentation of chains building on invalid blocks.
10. #30206: "build: make macOS build Clang only" - Aims to make macOS builds use only Clang without requiring GCC.

Updated Issues

1. #30177: "show error 'could not sign any more inputs' when sign PSBT for multisig" - Reports an error encountered when signing a PSBT for a multisig wallet.
2. #30176: "Add 'maxuploadtargettimeframe' to change the timeframe considered by 'maxuploadtarget'" - Suggests adding a setting to change the timeframe for upload targets.
3. #30175: "Enable importprivkey, addmultisigaddress in descriptor wallets" - Proposes enabling legacy import commands in descriptor wallets.

Closed Issues

1. #30220: "Improve/simplify node sync for pruned nodes" - Closed after discussion about improving node sync for pruned nodes.
2. #30217: "depends: Update Boost download link" - Closed after updating Boost download link due to migration.
3. #30216: "build: Fix building fuzz binary on on SunOS / illumos" - Fixed build issues on SunOS/illumos platforms.
4. #30215: "doc: JSON-RPC request Content-Type is application/json" - Documentation update specifying JSON content type in RPC examples.
5. #30213: "net: have GetReceivedMessage() return bytes" - Closed after initial attempt to refactor Transport class.
6. #30208: "chore: fix some comments" - Minor comment fixes in the codebase.

Recommendations

1. Address stability and security-related issues such as memory leaks (#30094) promptly.
2. Review changes related to build configurations and dependencies to ensure compatibility across different platforms (#30099).
3. Monitor discussions around new features or changes, such as the proposal for integrating artificial intelligence with digital currencies (#30087), to assess their impact and feasibility.

Conclusion

The project has seen significant activity since the last report, with multiple new issues being created, updates made to existing issues, and several issues being closed. The focus remains on improving stability, security, and usability while carefully considering new proposals or features.

Overall, it is crucial to prioritize addressing critical bugs and ensuring compatibility across different environments while keeping an eye on innovative proposals that could enhance the project's functionality in the future.

This report highlights the recent activity in the project, focusing on new issues, updates, and closures since the previous analysis 7 days ago. The recommendations aim to guide future efforts towards maintaining stability and exploring new opportunities for improvement.

There have been no updates since the last report.

Report On: Fetch pull requests

Analysis of Progress Since Last Report

Summary

Since the previous analysis 7 days ago, there has been significant activity in the repository. Here are the key highlights:

New Pull Requests:

• PR #30221: wallet: Ensure best block matches wallet scan state
• PR #30219: Lint: Support running individual lint checks
• PR #30218: refactor: remove unused CKey::Negate method
• PR #30214: refactor: Improve assumeutxo state representation
• PR #30212: rename TransactionErrors: MISSING_INPUTS and ALREADY_IN_CHAIN
• PR #30211: fuzz: Make FuzzedSock fuzz friendlier
• PR #30207: validation: Improve, document and test logic for chains building on invalid blocks
• PR #30205: test: add mocked Sock that can read/write custom data and/or CNetMessages
• PR #30203: Enhance signet chain configuration in bitcoin.conf
• PR #30202: netbase: extend CreateSock() to support creating arbitrary sockets
• PR #30201: depends: remove FORCE_USE_SYSTEM_CLANG
• PR #30200: Introduce Miner interface
• PR #30197: fuzz: bound some miniscript operations to avoid fuzz timeouts
• PR #30195: test: Added test coverage to listsinceblock rpc
• PR #30194: refactor: use recommended type hiding on multi_index types
• PR #30193: ci: move ASAN job to GitHub Actions from Cirrus CI
• PR #30185: guix: show *_FLAGS variables in pre-build output

Closed Pull Requests:

• PR #30217 (Merged): depends: Update Boost download link.

  • This PR updated the Boost download link due to migration, improving download speed.

• PR #30216 (Merged): build: Fix building fuzz binary on SunOS / illumos.

  • This PR fixed an issue with building the fuzz binary on SunOS / illumos.

• PR #30215 (Merged): doc: JSON-RPC request Content-Type is application/json.

  • This PR specified JSON content type in RPC examples, improving documentation accuracy.

Notable Discussions and Changes:

1. wallet: Ensure best block matches wallet scan state (#30221):

   • This PR ensures that the wallet's last block fields are in sync with the record stored on disk, improving consistency and reducing confusion.

2. Lint Support for Individual Checks (#30219):

   • Adds support for running individual tests in the rust lint suite, enhancing flexibility and usability.

3. Improve assumeutxo state representation (#30214):

   • This PR aims to make assumeutxo code more maintainable and improve performance by not locking cs_main for a long time when connecting snapshot blocks.

4. validation logic for chains building on invalid blocks (#30207):

   • This PR improves documentation and testing for chains building on invalid blocks, enhancing robustness and reliability.

Potential Issues and Concerns:

1. Experimental IPv6 PCP Pinhole Testing (#30043):
   • Needs thorough evaluation in various real-world scenarios to ensure its effectiveness and safety.

Conclusion:

The past week has seen significant activity aimed at improving wallet consistency, enhancing linting capabilities, refining assumeutxo state representation, and improving validation logic for chains building on invalid blocks. These changes are crucial for the ongoing development and robustness of the Bitcoin network. Future reports will continue to monitor these developments and their impacts on the project.

Report On: Fetch PR 30221 For Assessment

PR #30221: wallet: Ensure best block matches wallet scan state

Summary

This pull request addresses a critical issue in the wallet's synchronization with the blockchain. It ensures that the best block matches the wallet scan state, which is crucial for accurate wallet operations and preventing potential inconsistencies. The changes include:

1. Combining Last Block Fields: The m_last_block_processed and m_last_block_processed_height fields are combined into a new BestBlock struct.
2. Backwards Compatibility: The block height is added to the BESTBLOCK_NOMERKLE record in a backwards-compatible manner.
3. Removing chainStateFlushed: The chainStateFlushed mechanism is removed entirely.
4. Updating Best Block: The best block fields are updated for each blockConnected and blockDisconnected event to ensure they represent the block to which the wallet is synced.
5. Serialization Code: The serialization code for the best block is included in the BestBlock struct.

Commits

• wallet: Update best block record after block dis/connect

• scripted-diff: Rename LastBlock to BestBlock

• wallet: Combine last block processed hash and height into a struct

• wallet: Replace chainStateFlushed in loading with WriteBestBlock

• wallet: Remove WriteBestBlock from chainStateFlushed

• wallet: Sync m_best_block with BESTBLOCK_NOMERKLE

• wallet: Load best block record in LoadWallet

• wallet: Use best block locator in migrate instead of re-reading it

• wallet: use SetBestBlock when saving progress during rescan

• wallet: Remove chainStateFlushed

Files Changed

The changes span across multiple files, including:

• src/qt/test/wallettests.cpp
• src/wallet/interfaces.cpp
• src/wallet/rpc/backup.cpp
• src/wallet/rpc/transactions.cpp
• src/wallet/rpc/util.cpp
• src/wallet/spend.cpp
• Various test files in src/wallet/test/
• Core wallet files like src/wallet/wallet.cpp, src/wallet/wallet.h, and src/wallet/walletdb.cpp

Code Quality Assessment

The changes are well-organized and follow good coding practices. Here are some observations:

1. Combining Fields into Struct:

   • The combination of related fields into a single struct (BestBlock) improves code readability and maintainability.
   • Serialization and deserialization methods are included within the struct, ensuring encapsulation.

2. Backwards Compatibility:

   • The changes ensure that older versions of the wallet can still read the new format by making the height optional during deserialization.

3. Removal of Redundant Mechanisms:

   • Removing chainStateFlushed simplifies the codebase and eliminates potential race conditions.

4. Consistent Updates:

   • Ensuring that the best block fields are updated consistently during both block connection and disconnection events helps maintain synchronization accuracy.

5. Test Coverage:

   • The changes include updates to various test files, ensuring that the new functionality is adequately tested.

6. Code Style:

   • The code adheres to the project's coding standards, including proper use of assertions, logging, and error handling.

Detailed Diff Analysis

The diff shows a comprehensive update across multiple components of the wallet system:

1. Renaming Methods:

   • Methods like SetLastBlockProcessed are renamed to SetBestBlock, reflecting their updated functionality.

2. Updating Best Block Logic:

   • The logic for setting and retrieving the best block has been updated throughout the codebase, ensuring consistency.

3. Test Updates:

   • Test cases have been updated to reflect changes in method names and functionality, ensuring that tests remain relevant and accurate.

4. Serialization Changes:

   • Serialization methods have been updated to handle the new BestBlock struct format.

Conclusion

Overall, this pull request significantly improves the synchronization mechanism between the wallet and blockchain by ensuring that the best block accurately reflects the wallet's scan state. The changes are well-thought-out, maintain backwards compatibility, and include comprehensive updates to tests and core logic. This should enhance both reliability and maintainability of the wallet system.

Report On: Fetch Files For Assessment

Source Code Assessment

depends/packages/boost.mk

Analysis

• Structure and Quality:

  • The file is concise and well-structured.
  • It uses Makefile syntax to define variables and commands for handling the Boost library dependency.
  • The use of variables like $(package)_version and $(package)_download_path makes it easy to update the Boost version or download path in the future.

• Changes Made:

  • The Boost download link was updated from https://boostorg.jfrog.io to https://archives.boost.io.
  • This change is crucial for ensuring that the dependency can be fetched correctly.

Recommendations

• None. The file is well-maintained and the recent change was necessary and correctly implemented.

doc/JSON-RPC-interface.md

Analysis

• Structure and Quality:

  • The document is comprehensive, detailing the JSON-RPC interface for Bitcoin Core.
  • It includes sections on endpoints, parameter passing, versioning, security, consistency guarantees, and limitations.
  • Examples are provided using curl commands, which are helpful for users.

• Changes Made:

  • The content type for JSON-RPC requests was specified as application/json.
  • This change ensures that clients send requests with the correct content type, which is important for proper request handling.

Recommendations

• None. The documentation is thorough and the recent update enhances clarity regarding content types.

src/rpc/util.cpp

Analysis

• Structure and Quality:

  • The file contains utility functions for the RPC interface.
  • It appears to be well-organized with clear function definitions and comments where necessary.

• Changes Made:

  • Updates were made to handle JSON content type.
  • This ensures that the RPC server correctly interprets requests with the specified content type.

Recommendations

• None. The changes improve robustness in handling JSON-RPC requests.

src/test/rpc_tests.cpp

Analysis

• Structure and Quality:

  • The file contains unit tests for the RPC interface.
  • It uses Boost's unit test framework, which is appropriate for C++ projects.

• Changes Made:

  • Tests were added to include checks for JSON content type.
  • This ensures that the new functionality related to content type handling is properly tested.

Recommendations

• None. The additional tests improve coverage and ensure reliability of new features.

src/wallet/test/fuzz/scriptpubkeyman.cpp

Analysis

• Structure and Quality:

  • The file contains fuzz tests for ScriptPubKeyMan.
  • It uses a structured approach to initialize test data and execute fuzzing operations.

• Changes Made:

  • More coverage was added to the fuzz tests.
  • This enhances the robustness of ScriptPubKeyMan by ensuring it can handle a wider range of inputs without crashing or producing incorrect results.

Recommendations

• None. The changes improve test coverage and reliability.

src/Makefile.test.include

Analysis

• Structure and Quality:

  • The makefile includes rules for building test binaries.
  • It is well-organized with conditional statements to handle different build configurations.

• Changes Made:

  • Fixes were made to build the fuzz binary on SunOS / illumos.
  • This ensures compatibility with these operating systems, broadening the range of supported environments.

Recommendations

• None. The changes enhance cross-platform compatibility.

doc/release-notes-29612.md

Analysis

• Structure and Quality:

  • The release notes are concise and clearly state the changes related to dumptxoutset RPC.
  • They provide necessary information about new formats and deprecations.

• Changes Made:

  • Notes were added about the new format for UTXO set dumps and deprecation of old formats.
  • This informs users about important changes they need to be aware of when upgrading.

Recommendations

• None. The release notes are clear and informative.

src/kernel/chainparams.cpp & src/kernel/chainparams.h

Analysis

• Structure and Quality:

  • These files define chain parameters used throughout Bitcoin Core.
  • They are well-organized with clear class structures and member definitions.

• Changes Made:

  • Updates were made as part of assumeutxo changes.
  • These updates likely involve modifications to support new UTXO snapshot functionality.

Recommendations

• Ensure thorough testing of assumeutxo-related changes as they impact core functionality related to blockchain state management.

src/node/utxo_snapshot.h

Analysis

• Structure and Quality:

  • This header file deals with UTXO snapshots.
  • It defines classes and functions related to snapshot metadata and handling.

• Changes Made:

  • Updates were made as part of assumeutxo changes.
  • These updates likely involve enhancements or fixes related to snapshot handling.

Recommendations

• Ensure comprehensive documentation within the codebase explaining any new structures or functions introduced as part of these changes.

src/rpc/blockchain.cpp

Analysis

• Structure and Quality:

  • This source file implements blockchain-related RPC commands.
  • It is lengthy but appears well-organized with functions logically grouped by functionality.

• Changes Made:

  • Updates were made as part of assumeutxo changes.
  • These updates likely involve modifications to support new RPC functionalities related to UTXO snapshots.

Recommendations

• Ensure extensive testing of new RPC functionalities introduced by these changes to maintain API stability.

src/test/fuzz/deserialize.cpp & src/test/fuzz/utxo_snapshot.cpp

Analysis

• Structure and Quality:

  • These files contain fuzz tests for deserialization and UTXO snapshots respectively.
  • They use structured approaches to generate test data and execute fuzzing operations.

• Changes Made:

  • Updates were made as part of assumeutxo changes.
  • These updates likely involve adding more test cases or enhancing existing ones to cover new functionalities or edge cases introduced by assumeutxo changes.

Recommendations

• Continuously monitor fuzz test results to identify any potential issues early in the development cycle.

src/test/util/chainstate.h

Analysis

• Structure and Quality:

  • This header file contains utility functions for chainstate tests.
  • It is well-organized with clear function definitions relevant to testing chainstate functionalities.

• Changes Made:

  • Updates were made as part of assumeutxo changes.
  • These updates likely involve adding utilities or modifying existing ones to support new chainstate functionalities introduced by assumeutxo changes.

Recommendations

• Ensure that all utility functions are thoroughly documented, especially those newly introduced or modified as part of these changes.

src/.clang-tidy

Analysis

• Structure and Quality: clang-tidy configuration file specifying checks for code quality improvement. It includes a comprehensive list of checks aimed at improving code quality, performance, readability, etc., while excluding certain checks that might not be relevant or could produce false positives in this codebase context. Warnings are treated as errors (WarningsAsErrors: '*'), ensuring strict adherence to coding standards during development.

Recommendations:

None. The configuration is robust, ensuring high code quality through extensive checks.

Overall Summary:

The reviewed files demonstrate good structure, quality, and adherence to coding standards. Recent updates across various files enhance functionality, compatibility, testing coverage, documentation clarity, etc., particularly concerning assumeutxo-related changes. No significant issues were identified in any reviewed files; thus no immediate recommendations are necessary beyond maintaining current practices ensuring thorough testing/documentation.

Aggregate for risks

Notable Risks

Inconsistent Wallet Synchronization

Severity: Medium (2/3)

Rationale

The recent pull request #30221 aims to ensure that the wallet's best block matches the wallet scan state, which is crucial for accurate wallet operations. However, this change introduces a new BestBlock struct and removes the chainStateFlushed mechanism, which could potentially lead to inconsistencies if not thoroughly tested.

• Evidence: The changes in PR #30221 include significant modifications to how the wallet tracks its synchronization state with the blockchain. This includes combining m_last_block_processed and m_last_block_processed_height into a new BestBlock struct and removing the chainStateFlushed mechanism.
• Reasoning: While these changes are intended to improve synchronization accuracy, they also introduce new code paths and logic that need extensive testing to ensure they do not introduce new bugs or inconsistencies.

Next Steps

• Conduct thorough testing, including edge cases, to ensure that the new synchronization logic works correctly.
• Monitor for any reports of synchronization issues from users after deploying these changes.
• Consider adding additional logging around the new synchronization points to aid in diagnosing any potential issues.

Multiple Refactors in a Short Period

Severity: Medium (2/3)

Rationale

Several refactor-related pull requests (#30218, #30214, #30212) have been merged recently, which could introduce instability if not carefully managed.

• Evidence: Recent PRs such as #30218 (removing unused CKey::Negate method), #30214 (improving assumeutxo state representation), and #30212 (renaming transaction errors) indicate multiple refactors within a short timeframe.
• Reasoning: While refactoring is essential for code maintainability and performance improvements, doing so in quick succession can lead to unforeseen issues if not adequately tested. This is especially true for critical components like wallet handling and transaction processing.

Next Steps

• Ensure comprehensive test coverage for all refactored components.
• Perform regression testing to verify that existing functionality remains unaffected by the changes.
• Stagger future refactorings to allow adequate time for testing and stabilization between changes.

Prolonged Open Issues Related to Build Configurations

Severity: Low (1/3)

Rationale

There are several open issues related to build configurations and dependencies (#30210, #30206), which could affect cross-platform compatibility if not resolved promptly.

• Evidence: Issues like #30210 (switching to UCRT runtime for Windows builds) and #30206 (making macOS builds Clang-only) indicate ongoing work on build configurations that have yet to be resolved.
• Reasoning: While these issues are not critical, they can lead to build failures or compatibility problems on specific platforms if left unresolved. Ensuring smooth build processes across all supported environments is essential for developer productivity and user experience.

Next Steps

• Prioritize resolving open build configuration issues to ensure cross-platform compatibility.
• Regularly review and update build scripts and dependencies to prevent similar issues in the future.
• Consider setting up automated builds for different platforms to catch configuration issues early.

Recent Trend of Multiple Bugs in Specific Areas

Severity: Low (1/3)

Rationale

There has been a recent trend of multiple bugs reported related to specific areas of the code (#30177, #30176), which may indicate underlying issues that need further investigation.

• Evidence: Issues like #30177 (error when signing PSBT for multisig) and #30176 (adding 'maxuploadtargettimeframe' setting) suggest recurring problems in wallet-related functionalities.
• Reasoning: While these individual bugs may not be critical, their recurrence in specific areas could point to deeper underlying problems that need addressing.

Next Steps

• Conduct a thorough review of the affected code areas to identify any common patterns or root causes.
• Implement additional tests or code reviews focused on these areas to catch similar issues early.
• Engage with contributors who reported these bugs to gather more context and insights into potential solutions.