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

Partial Response : "Use Partial Response" enabled by default #6977

Merged
merged 1 commit into from
Dec 27, 2023

Conversation

Vanshikav123
Copy link
Contributor

@Vanshikav123 Vanshikav123 commented Dec 13, 2023

  • I added CHANGELOG entry for this change.
  • Change is not relevant to the end user.

Changes

I have made relevant changes in the codebase such that #6270 issue is resolved and Use Partial Response checkbox is enabled by default.

Copy link
Member

@saswatamcode saswatamcode left a comment

Choose a reason for hiding this comment

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

Thanks! Generally looks good, but I wonder if you came across the issue mentioned in comment: #6270 (comment)

@@ -272,6 +276,7 @@ const PanelList: FC<RouteComponentProps & PathPrefixProps> = ({ pathPrefix = ''
defaultStep={defaultStep}
defaultEngine={defaultEngine}
queryHistoryEnabled={enableQueryHistory}
usePartialResponse={usePartialResponse === 'true'}
Copy link
Member

Choose a reason for hiding this comment

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

Do we need the equality check here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yaa actually i used it to resolve a error which ensure it's always a boolean.

Copy link
Contributor

Choose a reason for hiding this comment

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

Isn't this done in the js/ts world by doing a double negation, like !!usePartialResponse? I see it often where people want to convert something to boolean.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thank you @douglascamata made changes suggested by you its working ! can review now

@Vanshikav123
Copy link
Contributor Author

Thanks! Generally looks good, but I wonder if you came across the issue mentioned in comment: #6270 (comment)

Hello @saswatamcode worked on the comment you suggested tested it on my local machine you can review it again !

Copy link
Contributor

@MichaHoffmann MichaHoffmann left a comment

Choose a reason for hiding this comment

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

lgtm

Copy link
Contributor

@yeya24 yeya24 left a comment

Choose a reason for hiding this comment

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

Thanks. LGTM.
I am not expert on the UI part but the code looks ok.

@yeya24
Copy link
Contributor

yeya24 commented Dec 27, 2023

@Vanshikav123 Please sign off DCO

@Vanshikav123
Copy link
Contributor Author

@Vanshikav123 Please sign off DCO

Done !

@MichaHoffmann MichaHoffmann merged commit 61040a5 into thanos-io:main Dec 27, 2023
20 checks passed
@Vanshikav123 Vanshikav123 deleted the patch-partialResponse branch December 30, 2023 13:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants