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: limit expands that are too wide #1433

Merged
merged 1 commit into from
Sep 22, 2023
Merged

Conversation

hperl
Copy link
Collaborator

@hperl hperl commented Sep 21, 2023

Related issue(s)

Fixes https://github.com/ory-corp/cloud/issues/5344

Checklist

  • I have read the contributing guidelines.
  • I have referenced an issue containing the design document if my change
    introduces a new feature.
  • I am following the
    contributing code guidelines.
  • I have read the security policy.
  • I confirm that this pull request does not address a security
    vulnerability. If this pull request addresses a security vulnerability, I
    confirm that I got the approval (please contact
    security@ory.sh) from the maintainers to push
    the changes.
  • I have added tests that prove my fix is effective or that my feature
    works.
  • I have added or changed the documentation.

Further Comments

@hperl hperl requested a review from alnr September 21, 2023 17:40
@hperl hperl self-assigned this Sep 21, 2023
},
"max_read_width": {
"type": "integer",
"default": 100,
Copy link
Member

Choose a reason for hiding this comment

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

Is this 100 queries?

Copy link
Member

Choose a reason for hiding this comment

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

Yes basically. A single request could still have up to max_read_width ^ max_read_depth queries. The only way to significantly reduce these numbers is implementing caches.

},
"max_read_width": {
"type": "integer",
"default": 100,
Copy link
Member

Choose a reason for hiding this comment

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

Yes basically. A single request could still have up to max_read_width ^ max_read_depth queries. The only way to significantly reduce these numbers is implementing caches.

@zepatrik zepatrik merged commit f1317da into master Sep 22, 2023
24 checks passed
@zepatrik zepatrik deleted the hperl/fix-wide-expands branch September 22, 2023 12:17
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.

None yet

4 participants