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

Pages Bug fix attempt no.2. #191

Merged
merged 1 commit into from
Dec 4, 2023

Conversation

THOR300
Copy link
Contributor

@THOR300 THOR300 commented Dec 4, 2023

Description

Addition of a method to the SearchResponse class to increment that pages on the document passage matches.

Type of change

  • Bug fix
  • New feature
  • Breaking change

How Has This Been Tested?

Unit tests that assert the method works correctly.

Reviewer Checklist

  • The PR represents a single feature (small driveby fixes are also ok)
  • The PR includes tests that are sufficient for the level of risk
  • The code is sufficiently commented, particularly in hard-to-understand areas
  • Any required documentation updates have been made
  • Any TODOs added are captured in future tickets
  • No FIXMEs remain

@THOR300 THOR300 requested a review from katybaulch December 4, 2023 10:39
@THOR300 THOR300 marked this pull request as ready for review December 4, 2023 10:59
Copy link
Contributor

@katybaulch katybaulch left a comment

Choose a reason for hiding this comment

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

Nice one 👍

@THOR300 THOR300 merged commit 77f6698 into main Dec 4, 2023
2 checks passed
@THOR300 THOR300 deleted the bugfix/attempt-number-two-for-page-numbers branch December 4, 2023 11:16
@@ -76,7 +76,7 @@ def _search_request(
data_access_search_response,
limit=search_body.limit,
offset=search_body.offset,
)
).increment_pages()
Copy link
Contributor

Choose a reason for hiding this comment

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

I would argue that calling process_vespa_search_reposonse should also handle the page numbering. We are in a router here and this should not contain any search response logic. Having said that there are functions that exist at the bottom of the file with vespa logic in 😢 - probably a tech debt ticket

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes very open to that!

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