Opened on 10/26/18 at 21:19:20
Closed on 08/17/22 at 06:08:55
#3571 closed defect (fixed)
Stream of Unicode Warnings from git hook on Commit
Reported by: | Joel Sherrill | Owned by: | Amar Takhar |
---|---|---|---|
Priority: | normal | Milestone: | 5.2 |
Component: | admin | Version: | 5 |
Severity: | critical | Keywords: | |
Cc: | Blocked By: | ||
Blocking: |
Description
When I pushed a commit this afternoon, I got so many of these that I can't scroll back to the git commit command:
remote: Code point 0x0000 is not Unicode, may not be portable at /data/support/git-support/hooks/hook_email.pl line 183.
remote: Malformed UTF-8 character (unexpected non-continuation byte 0x03, immediately after start byte 0xfd) in print at /data/support/git-support/hooks/hook_email.pl line 183.
remote: Code point 0x0000 is not Unicode, may not be portable at /data/support/git-support/hooks/hook_email.pl line 183.
remote: Malformed UTF-8 character (unexpected non-continuation byte 0xfe, immediately after start byte 0xf6) in print at /data/support/git-support/hooks/hook_email.pl line 183.
remote: Code point 0x0000 is not Unicode, may not be portable at /data/support/git-support/hooks/hook_email.pl line 183.
remote: Malformed UTF-8 character (unexpected non-continuation byte 0x04, immediately after start byte 0xfd) in print at /data/support/git-support/hooks/hook_email.pl line 183.
remote: Code point 0x0000 is not Unicode, may not be portable at /data/support/git-support/hooks/hook_email.pl linCKilled by signal 2.
Change History (4)
comment:1 Changed on 11/21/18 at 23:15:42 by Amar Takhar
comment:2 Changed on 12/05/18 at 03:35:26 by Amar Takhar
Any update on giving the hash that triggered this? Thanks.
comment:3 Changed on 02/13/19 at 20:03:19 by Amar Takhar
Milestone: | 5.1 → 5.2 |
---|
I haven't heard back on which hash triggered this. Moving to milestone:5.2
comment:4 Changed on 08/17/22 at 06:08:55 by Chris Johns
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
There has been no feedback so lets consider it closed.
Can you provide the rev hash that triggered this? Sorry I missed this ticket.