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

owlbot hitting commit size limit #5066

Closed
chingor13 opened this issue May 24, 2023 · 1 comment · Fixed by #5067
Closed

owlbot hitting commit size limit #5066

chingor13 opened this issue May 24, 2023 · 1 comment · Fixed by #5067
Assignees
Labels
priority: p0 Highest priority. Critical issue. P0 implies highest priority. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@chingor13
Copy link
Contributor

Error: Command failed: git push -f origin owl-bot-copy-java-common-protos
Step #3: error: RPC failed; HTTP 408 curl 18 HTTP/2 stream 7 was reset
@chingor13 chingor13 added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p0 Highest priority. Critical issue. P0 implies highest priority. labels May 24, 2023
@chingor13
Copy link
Contributor Author

Possible workaround from: https://github.com/orgs/community/discussions/55820#discussioncomment-5946136

git config --global http.version HTTP/1.1
git config --global http.postBuffer 157286400

We can probably do this in the Dockerfile build as it's a global setting

chingor13 pushed a commit that referenced this issue May 24, 2023
Attempt the resolution documented
[here](https://github.com/orgs/community/discussions/55820) for ` RPC
failed; HTTP 408 curl 18 HTTP/2 stream 7 was reset`.

Fixes #5066
chingor13 added a commit that referenced this issue May 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p0 Highest priority. Critical issue. P0 implies highest priority. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
2 participants