chore: Vendor supervisor_stdout extension#30252
Conversation
|
Warning Rate Limit Exceeded@sharat87 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 16 minutes and 26 seconds before requesting another review. 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. WalkthroughThe update involves modifying the Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
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 as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
|
/ok-to-test tags="@tag.Sanity" |
|
Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/7496825979. |
|
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/7496825979. |
We don't need these anymore, after changes from #30252.
Instead of downloading it from the github repo on every build (in
base.dockerfile), we vendor the supervisor extension so we can look to fix the buffer overflow problem in supervisor logs.After this is merged, after a day/two, we'll be removing
git,python3-pipand the supervisor-stdout extension frombase.dockerfile.Summary by CodeRabbit