gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2021-09-20	Add latest changes from gitlab-org/gitlab@14-3-stable-eev14.3.0-rc42	GitLab Bot

2021-08-19	Add latest changes from gitlab-org/gitlab@14-2-stable-eev14.2.0-rc42	GitLab Bot

2021-05-19	Add latest changes from gitlab-org/gitlab@13-12-stable-eev13.12.0-rc42	GitLab Bot

2020-08-20	Add latest changes from gitlab-org/gitlab@13-3-stable-ee	GitLab Bot

2020-07-20	Add latest changes from gitlab-org/gitlab@13-2-stable-ee	GitLab Bot

2020-03-09	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2019-09-18	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2019-09-17	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2019-07-26	Fix cannot modify frozen string	Thong Kuah
	Note that Performance/UnfreezeString recommends unary plus over "".dup, but unary plus has lower precedence so we have to use parenthesis
2019-07-26	Add frozen_string_literal to spec/lib (part 1)	Thong Kuah
	Using the sed script from https://gitlab.com/gitlab-org/gitlab-ce/issues/59758
2019-04-01	Allow streaming io objects into Gitaly	Bob 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-12-18	Update specs to exclude possible false positive pass	blackst0ne

2018-08-29	Fix Error 500s due to encoding issues when Wiki hooks fire	Stan 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-03-22	Fix EncodingHelper#clean blowing up on UTF-16BE strings	Ahmad Sherif
	Closes gitaly#1101
2018-02-10	Return a warning string if we try to encode to unsupported encoding	Ahmad Sherif
	Fixes gitlab-development-kit#321
2018-01-05	Fix a bug where charlock_holmes was used needlessly to encode strings	Alejandro Rodríguez

2017-12-28	Move encoding methods to the more general EncodingHelper	Alejandro Rodríguez

2017-11-23	Fix encoding bugs in Gitlab::Git::User	Jacob Vosmaer (GitLab)

2017-10-19	Avoind unnecesary `force_encoding` operations	Alejandro 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-08-08	Make sure that we have author and committer	Lin Jen-Shin
	In case we don't have it setup in ~/.gitconfig
2017-08-08	Add a test to show that threshold 40 would corrupt	Lin Jen-Shin
	If we set `ENCODING_CONFIDENCE_THRESHOLD` to 40, this test case would not pass. If we raise to 50, this would pass. Note that if in the future rugged didn't return corrupt data, this would be less relevant. But still icu recommend the threshold to be 50, we should just stick with 50.
2017-06-02	Rename `Gitlab::Git::EncodingHelper` to `Gitlab::EncodingHelper`	Bob Van Landuyt