Skip to content

GitLab pushes fail on pre-receive hook server error for commit messages with '\r' and '\n'

Summary

Pushing fails. Error message indicates it is a server error and to contact the administrator.

Steps to reproduce

Push a commit with \n and \r in a commit message, and see the error message.

What is the current bug behavior?

Can't push.

What is the expected correct behavior?

Can push.

Relevant logs and/or screenshots

$ git push
Counting objects: 51, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (36/36), done.
Writing objects: 100% (51/51), 31.03 KiB | 2.39 MiB/s, done.
Total 51 (delta 16), reused 0 (delta 0)
remote: GL-HOOK-ERR: Unable to validate commit, server error encountered.
remote:
remote: Please contact the administrator, and retry the commit at a later time.
remote:
To https://gitlab.eclipse.org/eclipse/escet/escet.git
 ! [remote rejected]     715-js-html-codegen-print-decls-fix-and-improve -> 715-js-html-codegen-print-decls-fix-and-improve (pre-receive hook declined)
error: failed to push some refs to 'https://gitlab.eclipse.org/eclipse/escet/escet.git'

Priority

  • Urgent
  • High
  • Medium
  • Low

Severity

  • Blocker
  • Major
  • Normal
  • Low

Impact

Workaround is to change the commit message and push it then with the changed message. The error is highly confusing though.

Edited by Dennis Hendriks