Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tests, workspace: Add Taproot soft fork status to getblockchaininfo test and VS Code workspace configuration #254

Merged
merged 2 commits into from
Dec 16, 2024

Conversation

gto90
Copy link
Member

@gto90 gto90 commented Dec 16, 2024

Purpose

This pull request includes updates to the getblockchaininfo test to include the Taproot soft fork status and adds a new Visual Studio Code workspace configuration file to the repository.

Changes Made

  • Commit 0bda8ec:

    • Added Taproot soft fork details to the expected softforks field in the getblockchaininfo test.
    • Ensured the test checks for the correct status, start time, timeout, and activation state of the Taproot soft fork.
    • This update ensures that the getblockchaininfo RPC call accurately reflects the status of the Taproot soft fork, which is crucial for testing and validation purposes.
    • Refs Activate Taproot #244
  • Commit 698a43a:

    • Added a new digibyte.code-workspace file to configure the Visual Studio Code workspace settings for the DigiByte Core project.
      The digibyte.code-workspace file includes the project's folder settings, file associations for proper syntax highlighting, and GitHub Copilot advanced settings.
    • This addition aims to improve the development experience for contributors using Visual Studio Code by providing a pre-configured workspace setup.

Related Issues

Refs #244

Additional Information

This PR addresses the need for accurate reporting of the Taproot soft fork status in the getblockchaininfo RPC call and enhances the development environment for contributors using Visual Studio Code.

This commit updates the `rpc_blockchain.py` functional test to include the Taproot soft fork status in the `getblockchaininfo` RPC call. The Taproot soft fork is defined using the BIP9 activation mechanism with specific start and timeout times. The test verifies that the Taproot soft fork is correctly reported as "defined" and not yet active.

Changes include:
- Adding Taproot soft fork details to the expected `softforks` field in the `getblockchaininfo` test.
- Ensuring the test checks for the correct status, start time, timeout, and activation state of the Taproot soft fork.

This update ensures that the `getblockchaininfo` RPC call accurately reflects the status of the Taproot soft fork, which is crucial for testing and validation purposes.

Refs #244
This commit adds a new `digibyte.code-workspace` file to the repository. This file is used to configure the Visual Studio Code workspace settings for the DigiByte Core project.

The `digibyte.code-workspace` file includes:
- Folder settings for the project.
- File associations to ensure proper syntax highlighting for various C++ standard library headers.
- GitHub Copilot advanced settings to specify project directories.

This addition aims to improve the development experience for contributors using Visual Studio Code by providing a pre-configured workspace setup.
Copy link

@JaredTate JaredTate left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK. Tested with "test/functional/test_runner.py rpc_blockchain.py" and passes. I am also making this review from withing VS Code on my mac for the first time. Pretty cool and eays.

@JaredTate
Copy link

Screenshot 2024-12-16 at 2 16 53 PM
Looks like I still have to be in the web GUI to upload a photo with my review.

Copy link
Member

@ycagel ycagel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cACK. Great work @gto90!

@ycagel ycagel merged commit c336e5d into develop Dec 16, 2024
0 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants