wardend: fix query gas limit option

[Pitasi]

Same as cosmos/evm#641, we were ignoring the gas limit for queries, if set.

Closes ENG-713.

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

Adds a base application option to configure query gas limit at startup by wiring SetQueryGasLimit to FlagQueryGasLimit from sdkserver; adds a changelog entry documenting that app.toml's query-gas-limit was previously ignored. No other logic or error-handling changes.

Changes

Cohort / File(s)	Summary
Command root option wiring cmd/wardend/cmd/root.go	Add SetQueryGasLimit into baseappOptions, sourcing value from sdkserver's FlagQueryGasLimit so the app respects configured query gas limit at startup.
Changelog entry CHANGELOG.md	Add Unreleased bugfix note: app.toml's query-gas-limit was being ignored; document the fix.

Sequence Diagram(s)

sequenceDiagram
    autonumber
    participant CLI as CLI
    participant RootCmd as cmd/wardend/cmd/root.go
    participant SDKFlags as sdkserver (flags)
    participant BaseApp as BaseApp

    CLI->>RootCmd: start with flags
    RootCmd->>SDKFlags: read FlagQueryGasLimit
    SDKFlags-->>RootCmd: queryGasLimit
    RootCmd->>BaseApp: include SetQueryGasLimit(queryGasLimit) in baseappOptions
    RootCmd->>BaseApp: initialize application
    BaseApp-->>RootCmd: app ready (configured query gas limit)

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• wardend: fix query gas limit option #1727 — implements the same wiring of SetQueryGasLimit to FlagQueryGasLimit in cmd/wardend/cmd/root.go, directly related to respecting configured query gas limits.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title succinctly captures the main intent of the changeset by indicating that the query gas limit option in the wardend component is fixed, making it clear and specific without extraneous details. It references the relevant feature by name and conveys the core update so that team members scanning the history will immediately grasp its purpose. The phrasing is concise and avoids generic terms or unnecessary noise.
Description Check	✅ Passed	The description clearly relates to the changeset by explaining that the gas limit for queries was previously ignored and linking to the analogous upstream fix, and it specifies the associated issue being closed. It directly addresses the behavior change introduced by the pull request and ties it to a concrete ticket, demonstrating relevance without being off-topic or overly vague.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8946557 and c844076.

📒 Files selected for processing (2)

• CHANGELOG.md (1 hunks)
• cmd/wardend/cmd/root.go (1 hunks)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d8af5b2 and 06a7866.

📒 Files selected for processing (1)

• cmd/wardend/cmd/root.go (1 hunks)

⏰ 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: test
• GitHub Check: lint
• GitHub Check: Analyze (go)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
warden-help-center	Ignored	Preview		Oct 9, 2025 11:21am