Skip to content

chore: supply GraphQLResponse info in resolve benchmark#1227

Merged
ysmolski merged 4 commits intomasterfrom
yury/eng-7534-engine-fix-benchmarks-in-v2pkgengineresolve
Jul 16, 2025
Merged

chore: supply GraphQLResponse info in resolve benchmark#1227
ysmolski merged 4 commits intomasterfrom
yury/eng-7534-engine-fix-benchmarks-in-v2pkgengineresolve

Conversation

@ysmolski
Copy link
Copy Markdown
Contributor

@ysmolski ysmolski commented Jul 11, 2025

Two benchmarks were panicing because GraphQLResponse.Info is expected to be non-nil in the ResolveGraphQLResponse method.

This fixes resolve benchmarks.

Summary by CodeRabbit

  • Tests
    • Improved benchmark tests for nested batching scenarios with enhanced response data initialization.
  • Documentation
    • Updated performance section in README with corrected benchmark command path.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jul 11, 2025

Walkthrough

The update explicitly initializes the Info field in the GraphQLResponse struct within two benchmark functions by assigning it a pointer to a GraphQLResponseInfo struct with OperationType set to ast.OperationTypeQuery. Additionally, the README.md file was updated to correct the directory path in a shell command example under the Performance section.

Changes

File(s) Change Summary
v2/pkg/engine/resolve/resolve_test.go Added explicit initialization of the Info field in GraphQLResponse within two benchmark functions.
README.md Updated shell command example path from v2/pkg/engine to v2/pkg/engine/resolve in Performance section.

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1601cc4 and fa26a99.

📒 Files selected for processing (1)
  • README.md (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • README.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: Build and test (go 1.23 / windows-latest)
  • GitHub Check: Build and test (go 1.23 / windows-latest)

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
v2/pkg/engine/resolve/resolve_test.go (1)

6571-6573: Consider de-duplicating repeated plan boilerplate

You added an identical Info stanza to the second benchmark. While harmless, the same three-line snippet now appears in multiple benchmark plans. A tiny helper (e.g. withQueryInfo(plan *GraphQLResponse)) would reduce copy-paste across future benches.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1166a10 and 78525f9.

📒 Files selected for processing (1)
  • v2/pkg/engine/resolve/resolve_test.go (2 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: SkArchon
PR: wundergraph/graphql-go-tools#1203
File: v2/pkg/engine/resolve/loader.go:63-67
Timestamp: 2025-07-02T15:28:02.122Z
Learning: In the graphql-go-tools codebase, result structs are consistently initialized with non-nil bytes.Buffer instances, making additional nil checks for res.out unnecessary defensive programming.
v2/pkg/engine/resolve/resolve_test.go (1)

undefined

<retrieved_learning>
Learnt from: SkArchon
PR: #1203
File: v2/pkg/engine/resolve/loader.go:63-67
Timestamp: 2025-07-02T15:28:02.122Z
Learning: In the graphql-go-tools codebase, result structs are consistently initialized with non-nil bytes.Buffer instances, making additional nil checks for res.out unnecessary defensive programming.
</retrieved_learning>

🧬 Code Graph Analysis (1)
v2/pkg/engine/resolve/resolve_test.go (3)
v2/pkg/engine/resolve/response.go (1)
  • GraphQLResponseInfo (34-36)
pkg/graphql/request.go (2)
  • OperationType (21-21)
  • OperationTypeQuery (25-25)
v2/pkg/ast/ast_operation_definition.go (2)
  • OperationType (11-11)
  • OperationTypeQuery (15-15)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: Build and test (go 1.23 / windows-latest)
  • GitHub Check: Build and test (go 1.23 / ubuntu-latest)
  • GitHub Check: Build and test (go 1.23 / windows-latest)
🔇 Additional comments (1)
v2/pkg/engine/resolve/resolve_test.go (1)

6261-6263: Nil-panic fixed – initialization looks good

Supplying Info with OperationTypeQuery prevents the ResolveGraphQLResponse helper from panicking in this benchmark.
No further issues spotted.

Two benchmarks were panicing because GraphQLResponse.Info is expected to
be non-nil in the ResolveGraphQLResponse method.

This fixes resolve benchmarks.
@ysmolski ysmolski force-pushed the yury/eng-7534-engine-fix-benchmarks-in-v2pkgengineresolve branch from 78525f9 to 1601cc4 Compare July 11, 2025 09:37
@ysmolski ysmolski requested a review from a team as a code owner July 11, 2025 09:41
@devsergiy devsergiy changed the title fix: supply Info with the GraphQLResponse struct chore: supply GraphQLResponse info in resolve benchmark Jul 15, 2025
@ysmolski ysmolski merged commit 4e09496 into master Jul 16, 2025
10 checks passed
@ysmolski ysmolski deleted the yury/eng-7534-engine-fix-benchmarks-in-v2pkgengineresolve branch July 16, 2025 08:29
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.

2 participants