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

Sync MaxGitDiffLineCharacters with conf/app.ini #2779

Merged
merged 1 commit into from
Oct 25, 2017
Merged

Sync MaxGitDiffLineCharacters with conf/app.ini #2779

merged 1 commit into from
Oct 25, 2017

Conversation

michaelkuhn
Copy link
Contributor

MAX_GIT_DIFF_LINE_CHARACTERS was updated in #1845 but the corresponding default value of MaxGitDiffLineCharacters was not changed. This can lead to inconsistencies.

Specifically, with my bindata build, Gitea used the default of 500 instead of 5000 because MAX_GIT_DIFF_LINE_CHARACTERS is not set in my custom/conf/app.ini.

I found the bug with version 1.2 but it should also apply to master.

MAX_GIT_DIFF_LINE_CHARACTERS was updated in #1845 but the corresponding
default value of MaxGitDiffLineCharacters was not changed. This can lead
to inconsistencies.
@codecov-io
Copy link

Codecov Report

Merging #2779 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #2779   +/-   ##
=======================================
  Coverage   27.08%   27.08%           
=======================================
  Files          88       88           
  Lines       17264    17264           
=======================================
  Hits         4676     4676           
  Misses      11909    11909           
  Partials      679      679

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 178bd49...b7db6b8. Read the comment docs.

@tboerger tboerger added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Oct 25, 2017
@lafriks lafriks added the issue/regression Issue needs no code to be fixed, only a description on how to fix it yourself label Oct 25, 2017
@lafriks lafriks added this to the 1.3.0 milestone Oct 25, 2017
@lafriks
Copy link
Member

lafriks commented Oct 25, 2017

LGTM

@tboerger tboerger added lgtm/need 1 This PR needs approval from one additional maintainer to be merged. and removed lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels Oct 25, 2017
@lunny
Copy link
Member

lunny commented Oct 25, 2017

LGTM

@tboerger tboerger added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Oct 25, 2017
@lunny lunny merged commit 3af5b67 into go-gitea:master Oct 25, 2017
@lunny
Copy link
Member

lunny commented Oct 25, 2017

@michaelkuhn could you send a backport PR to branch release/v1.2 ?

@lafriks lafriks added the backport/done All backports for this PR have been created label Oct 25, 2017
lafriks pushed a commit that referenced this pull request Oct 25, 2017
MAX_GIT_DIFF_LINE_CHARACTERS was updated in #1845 but the corresponding
default value of MaxGitDiffLineCharacters was not changed. This can lead
to inconsistencies.
vdbt pushed a commit to vdbt/gitea that referenced this pull request Oct 27, 2017
MAX_GIT_DIFF_LINE_CHARACTERS was updated in go-gitea#1845 but the corresponding
default value of MaxGitDiffLineCharacters was not changed. This can lead
to inconsistencies.
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backport/done All backports for this PR have been created issue/regression Issue needs no code to be fixed, only a description on how to fix it yourself lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants