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

Fix: RPC endpoints should default to proof=1 #4139

Merged
merged 1 commit into from
Dec 8, 2023
Merged

Conversation

kantai
Copy link
Member

@kantai kantai commented Dec 8, 2023

Description

HTTP changes in develop changed the default behavior of the proof query string. In master, it defaults to 1, but in develop it defaults to 0.

I'm open to changing this default, but this is why tests::integrations::integration_test_get_info broke, and the change would need to be mentioned specifically in the changelog. I think the right thing to do here is to return to the prior behavior, and if we want to change the default, we can do that in another PR that also updates the tests.

Copy link

codecov bot commented Dec 8, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (4ee724e) 72.27% compared to head (ce5faa3) 72.28%.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #4139   +/-   ##
========================================
  Coverage    72.27%   72.28%           
========================================
  Files          401      401           
  Lines       286381   286381           
========================================
+ Hits        206994   207012   +18     
+ Misses       79387    79369   -18     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@wileyj wileyj left a comment

Choose a reason for hiding this comment

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

confirmed test is now passing.
shipit

@blockstack-devops
Copy link
Contributor

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@stacks-network stacks-network locked as resolved and limited conversation to collaborators Nov 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants