Details
Description
Issue Summary
Upon viewing the 'blame' for one or more files in a repository can produce a warning in the UI with a message "An error occurred while executing an external process: null"
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Import a repository
- Create a couple of commits in the repository
- For one of the commits, add the commit message similar to '10 11 02200' (3 numbers, separated by a single space)
- click on blame
Expected Results
The proper output for blame is displayed.
Actual Results
A dialog box apprears with error "An error occurred while executing an external process: null"
The below exception is thrown in the atlassian-bitbucket.log file, once debug logging is enabled.
2022-04-29 16:04:50,746 DEBUG [http-nio-7990-exec-6] username @1FY8PZSx964x12296927x2 1xbbwxk 192.168.1.1,0:0:0:0:0:0:0:1 "GET /rest/api/latest/projects/PRJ/repos/REP/browse/sample/test.yaml HTTP/1.1" c.a.b.i.p.nu.NioNuProcessHandler 23387: Dropping [/bin/git blame --incremental -L 1,+1535 refs/heads/production -- sample/test.yaml] callback invocation (Canceled: false; Timed out: false) java.lang.NumberFormatException: null at java.lang.Long.parseLong(Unknown Source) at java.lang.Long.parseLong(Unknown Source)
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available