6b4f93c034
Updating multiple application settings panels through a single action causes the incorrect action to be shown when there are errors. Instead, make each panel action handle both updating and display.
24 lines
1.3 KiB
Text
24 lines
1.3 KiB
Text
= form_for @application_setting, url: preferences_admin_application_settings_path(anchor: 'js-gitaly-settings'), html: { class: 'fieldset-form' } do |f|
|
|
= form_errors(@application_setting)
|
|
|
|
%fieldset
|
|
.form-group
|
|
= f.label :gitaly_timeout_default, 'Default Timeout Period', class: 'label-bold'
|
|
= f.number_field :gitaly_timeout_default, class: 'form-control'
|
|
.form-text.text-muted
|
|
Timeout for Gitaly calls from the GitLab application (in seconds). This timeout is not enforced
|
|
for git fetch/push operations or Sidekiq jobs.
|
|
.form-group
|
|
= f.label :gitaly_timeout_fast, 'Fast Timeout Period', class: 'label-bold'
|
|
= f.number_field :gitaly_timeout_fast, class: 'form-control'
|
|
.form-text.text-muted
|
|
Fast operation timeout (in seconds). Some Gitaly operations are expected to be fast.
|
|
If they exceed this threshold, there may be a problem with a storage shard and 'failing fast'
|
|
can help maintain the stability of the GitLab instance.
|
|
.form-group
|
|
= f.label :gitaly_timeout_medium, 'Medium Timeout Period', class: 'label-bold'
|
|
= f.number_field :gitaly_timeout_medium, class: 'form-control'
|
|
.form-text.text-muted
|
|
Medium operation timeout (in seconds). This should be a value between the Fast and the Default timeout.
|
|
|
|
= f.submit 'Save changes', class: "btn btn-success"
|