You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Getting that error message "error: spawn ENAMETOOLONG" whenever the plugin tries to commit a backup. It's been working fine until looks like four days ago (15 May) was the last successful commit.
Relevant errors (if available)
No response
Steps to reproduce
When Obsidian Git tries to send a back up, "error: spawn ENAMETOOLONG" appears and it won't back up.
Expected Behavior
No response
Addition context
No response
Operating system
Windows
Plugin version
1.25.3
The text was updated successfully, but these errors were encountered:
As stated in this comment, it may be a too long argument. Do you have any file, which filename is very long or is the amount of changed files very high. E.g. when you enabled the option to list all changed files in the commit body.
On Thu, May 19, 2022 at 10:56 AM Vinzent ***@***.***> wrote:
As stated in this comment <steveukx/git-js#461>,
it may be a too long argument. Do you have any file, which filename is very
long or is the amount of changed files very high. E.g. when you enabled the
option to list all changed files in the commit body.
—
Reply to this email directly, view it on GitHub
<#238 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEDBJPC5WVORTCQ7FUEXCG3VKZQCBANCNFSM5WLQNQ4A>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
Describe the bug
Getting that error message "error: spawn ENAMETOOLONG" whenever the plugin tries to commit a backup. It's been working fine until looks like four days ago (15 May) was the last successful commit.
Relevant errors (if available)
No response
Steps to reproduce
When Obsidian Git tries to send a back up, "error: spawn ENAMETOOLONG" appears and it won't back up.
Expected Behavior
No response
Addition context
No response
Operating system
Windows
Plugin version
1.25.3
The text was updated successfully, but these errors were encountered: