diff options
| author | Stan Hu <stanhu@gmail.com> | 2019-05-06 14:42:21 -0700 |
|---|---|---|
| committer | Stan Hu <stanhu@gmail.com> | 2019-05-06 21:21:56 -0700 |
| commit | b7b852c250a95648d5954e0ead6c37b5ff8b35d9 (patch) | |
| tree | b022cb42e2a902d09b5874469412cab53893c041 /scripts | |
| parent | e1aa7f5074aab8190d16a6f25121d33b99a07238 (diff) | |
| download | gitlab-ce-sh-fix-activerecord-patch-mark2.tar.gz | |
Additional fix to handle NULL lock_versionsh-fix-activerecord-patch-mark2
If the UI sends a string value for lock_version (e.g. "0"), then the
previous monkey patch did not properly handle that properly. This
commit casts the value to an integer to determine whether to look for
NULL lock_versions.
For merge requests, GitLab sends a POST request to
`namespace/project/merge_requests/:iid` with the
`merge_request[lock_version]` parameter with a string `0`. The string
value comes from the form field, which explains why
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/28145 wasn't
sufficient.
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions