When trying to display the diff of a (long) file in a commit, I get "The diff for this file is too large to render." instead of the diff.
- What is the upper limit of the file size that Stash is still willing to display?
- Is there a way to increase this limit?
Balasz,
Stash applies two limits to diff rendering to limit memory usage:
# Maximum length for any line returned from a given file when viewing source. This value truncates long lines. There is no mechanism for retrieving the truncated part short of downloading the entire file.
page.max.source.length=5000
# Maximum number of segment lines (of any type, total) which may be returned for a single diff. Unlike other page limits, this is a hard limit; subsequent pages cannot be requested when a diff exceeds this size.
page.max.diff.lines=10000
Does anyone know where this setting is for Bitbucket server 4.1? That file doesn't seem to exist (also checked replacing the stash with bitbucket)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's now called bitbucket.properties and should be created in BITBUCKET_HOME/shared/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Does anyone have a good feel for the impact on system performance if we increase the defaults by a factor of 10?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It depends quite much on how many users are doing what exactly. If large diffs are relatively rare compared to all the other things the server does, it will not have a significant performance impact. Try for an hour or a day and keep track of the performance indicators of the server.
(I did increase this by a factor of 10 to to 50k. We have so many users, and so few huge diffs that it did not really make a difference in the performance.)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Balazs,
Could this help you out?
https://confluence.atlassian.com/display/STASHKB/Pull+request+is+too+large+to+render
Best regards,
Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I found this myself as well. That question is about the number of files in a pull request, i have a problem with the number of lines in one file. So I guess it doesn't solve my problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That won't work; that settings defines the limit of the number of changes (path elements) that's renderable in a pull request.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.