virtual_branches.toml with NUL characters in last line prevents GitButler from working after commit

[ollie-dev]

Using v.0.11.7 under latest Windows 11 patch.

Reproduce:

• Create some code changes
• manually write a commit message an commit
• click "push to remote"
• Errormessage:

"TOML parse error at line 24, column 1 | 24 |

| ^ invalid key"

• opening the virtual_branches.toml file, the last line looks like this in VS code:

Solution: Delete NUL characters an save - everything works again

[krlvi]

Hey, thanks for reporting that! We are gonna look into this.

@anaisbetts what do you think could be causing this?

[ollie-dev]

It happens as I do the commit. I had VS Code with the .toml-file open and could see changes being written in one second and in the next second the red NUL line appeared. Like a step after the first changes...

[anaisbetts]

@krlvi Nothing Windows specific on this one I can think of, feels like the app just wrote a buffer that was bigger than the content