Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2023-02-02Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2022-09-23Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2022-08-25Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2022-03-24Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2022-03-22Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2021-09-06Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2021-07-23Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2021-05-06Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-09-10Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-03-09Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-07-10Add a rubocop for Rails.loggerMayra Cabrera
Suggests to use a JSON structured log instead Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/54102
2019-04-01Allow streaming io objects into GitalyBob Van Landuyt
This allows us to set the encoding of an IO passed without reading it into memory. This is useful if we want to stream files into Gitaly. Like we do when uploading a new file to the repository.
2018-10-22Enable frozen string for lib/gitlab/*.rbgfyoung
2018-08-29Fix Error 500s due to encoding issues when Wiki hooks fireStan Hu
Saved Wiki content goes through the GitalyClient::WikiService, which calls StringIO#set_encoding on the input stream. The problem is that this call mutates the encoding of the given string object to ASCII-88BIT, which causes problems for models expecting the data to still be in UTF-8. Freezing the input disables this behavior: https://github.com/ruby/ruby/blob/v2_4_4/ext/stringio/stringio.c#L1583 Closes #50590
2018-07-09Resolve Naming/UncommunicativeMethodLin Jen-Shin
2018-07-09Updates from `rubocop -a`Lin Jen-Shin
2018-03-22Fix EncodingHelper#clean blowing up on UTF-16BE stringsAhmad Sherif
Closes gitaly#1101
2018-02-10Return a warning string if we try to encode to unsupported encodingAhmad Sherif
Fixes gitlab-development-kit#321
2018-01-05Fix a bug where charlock_holmes was used needlessly to encode stringsAlejandro Rodríguez
2017-12-28Move encoding methods to the more general EncodingHelperAlejandro Rodríguez
2017-11-23Fix encoding bugs in Gitlab::Git::UserJacob Vosmaer (GitLab)
2017-10-19Avoind unnecesary `force_encoding` operationsAlejandro Rodríguez
They're costly. This will also avoid some edge cases where charlock_holmes assigns a weird encoding to a perfectly valid UTF-8 string.
2017-09-06remove useless commentmicael.bergeron
2017-09-06renames ambiguous methods and add specmicael.bergeron
2017-09-06fix refactoring error with Blob.binary?micael.bergeron
remove some lint
2017-09-06revert to using a simple representationmicael.bergeron
2017-09-06wip: fake its a binary diffmicael.bergeron
2017-08-08Raise encoding confidence threshold to 50Lin Jen-Shin
It is recommended that we set this to 50: https://gitlab.com/gitlab-org/gitlab-ce/issues/35098#note_35036746 In this particular issue, the confidence was 42 for Shift JIS, but in fact that's encoded in UTF-8 just with a single bad character. In this case, we shouldn't try to treat it as Shift JIS, but just treat it as UTF-8 and remove invalid bytes. Treating it like Shift JIS would corrupt the whole data. Unfortunately, the diff which would cause this could not be disclosed therefore we can't use it as a test example.
2017-06-06Fix binary encoding error on MR diffsJames Lopez
2017-06-02Rename `Gitlab::Git::EncodingHelper` to `Gitlab::EncodingHelper`Bob Van Landuyt