-
Notifications
You must be signed in to change notification settings - Fork 593
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
githubCreateIssue_fix #4151
githubCreateIssue_fix #4151
Conversation
/it-go |
1 similar comment
/it-go |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks neat! I noticed an issue though.
I have tested it with a test repository, but I think it can happen that the POST requests are made too fast after each other when the body is split up in chunks. When slowly stepping through the code it works well, but when running it normally, I saw it happening that multiple issues are opened with the chunks.
- name: chunkSize | ||
description: Defines size of the chunk. If content exceed chunk size it'll be sliced into chunks and stored in comments | ||
scope: | ||
- PARAMETERS | ||
- STAGES | ||
- STEPS | ||
type: int | ||
default: 65500 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should it be made clear what the maximum value is? Or what happens if you set chunkSize
above it?
Co-authored-by: Jordi van Liempt <[email protected]>
…y into githubCreateIssue-fix
/it-go |
* extend githubCreateIssue to handle long body Co-authored-by: Jordi van Liempt <[email protected]>
Changes
ghCreateIssue throws error when message body exceeds 65536 characters
For some cases body reaches the limit of issues body (65536 characters)
Possible solution: once body reaches the limit - split leftovers into the comments