-
-
Notifications
You must be signed in to change notification settings - Fork 523
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
[Gitlab] Error while decorating the request #445
Labels
Comments
I'd need some more details to help replicate this:
|
sfaqer
added a commit
to sfaqer/sonarqube-community-branch-plugin
that referenced
this issue
Sep 16, 2021
Added encoding for entity sending to gitlab. Currently the Gitlab decorator does not set an encoding when sending the merge request decoration details to Gitlab, which results in some characters - such as the Cyrillic alphabet - being rendered incorrectly on Gitlab, or if that character found on old \ new path position occurs error in API. Explicitly specifying UTF-8 as the encoding overcome this.
Yes
Yes
no btw i found error and fix it in #446 =) |
mc1arke
added a commit
that referenced
this issue
Oct 9, 2021
When calling the Gitlab API with content that contains accented or cyrillic characters, the API returns an error response and fails to complete the decoration. Explicitly setting the encoding for all body content to UTF-8 on Gitlab API requests results in the content being encoded in a way for the Gitlab API handles correctly.
mc1arke
added a commit
that referenced
this issue
Oct 9, 2021
When calling the Gitlab API with content that contains accented or cyrillic characters, the API returns an error response and fails to complete the decoration. Explicitly setting the encoding for all body content to UTF-8 on Gitlab API requests results in the content being encoded in a way for the Gitlab API handles correctly.
mc1arke
added a commit
that referenced
this issue
Oct 9, 2021
When calling the Gitlab API with content that contains accented or cyrillic characters, the API returns an error response and fails to complete the decoration. Explicitly setting the encoding for all body content to UTF-8 on Gitlab API requests results in the content being encoded in a way for the Gitlab API handles correctly.
mc1arke
added
awaiting release
Merged but not currently in release version
backport candidate
This feature or fix should be included in another release branch
labels
Oct 9, 2021
Released in 1.10.0 of the plugin |
mc1arke
added a commit
that referenced
this issue
Jun 19, 2022
When calling the Gitlab API with content that contains accented or cyrillic characters, the API returns an error response and fails to complete the decoration. Explicitly setting the encoding for all body content to UTF-8 on Gitlab API requests results in the content being encoded in a way for the Gitlab API handles correctly.
mc1arke
added a commit
that referenced
this issue
Jun 19, 2022
When calling the Gitlab API with content that contains accented or cyrillic characters, the API returns an error response and fails to complete the decoration. Explicitly setting the encoding for all body content to UTF-8 on Gitlab API requests results in the content being encoded in a way for the Gitlab API handles correctly.
mc1arke
removed
the
backport candidate
This feature or fix should be included in another release branch
label
Jun 19, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe the bug
Found error in CE logs, MR not decorated
Expected behavior
MR successful decorated
Software Versions
Additional context
The text was updated successfully, but these errors were encountered: