Conversation
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. Comment |
gontzess
changed the title
gontzess
force-pushed
the
task-sdk-upgrade-batch-5
branch
2 times, most recently
from
5cac6ef to
7370e36
Compare
gontzess
force-pushed
the
task-sdk-upgrade-batch-5
branch
from
7370e36 to
2d7753d
Compare
- Add pkg/config with field definitions and go generate directive - Remove old cmd/baton-retool/config.go (moved to pkg/config) - Update Makefile with GENERATED_CONF, BUILD_TAGS, and generate target - Update main.go to use generated config struct instead of viper Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add connectorrunner.WithDefaultCapabilitiesConnectorBuilder to enable automatic capability detection from connector interface implementation.
|
|
||
| args = append(args, limit+1) | ||
| _, _ = sb.WriteString(fmt.Sprintf("LIMIT $%d ", len(args))) | ||
| fmt.Fprintf(sb, "LIMIT $%d ", len(args)) |
There was a problem hiding this comment.
I'm guessing linting. All these upgrades come with a big lint version bump too and more stringent rules
There was a problem hiding this comment.
Ah yes the PR description includes this: Fix lint issue: use fmt.Fprintf instead of WriteString(fmt.Sprintf())
There was a problem hiding this comment.
Ah yes the PR description includes this: Fix lint issue: use fmt.Fprintf instead of WriteString(fmt.Sprintf())
3 participants
Summary
go generatefollowing baton-datadog patternCI Status
🤖 Generated with Claude Code