Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[NBug] Index was outside the bounds of the array. #11678

Open
cforbin1 opened this issue Apr 10, 2024 · 1 comment
Open

[NBug] Index was outside the bounds of the array. #11678

cforbin1 opened this issue Apr 10, 2024 · 1 comment

Comments

@cforbin1
Copy link

Environment

  • Git Extensions 4.2.1.17611
  • Build b0c0b28
  • Git 2.44.0.windows.1
  • Microsoft Windows NT 10.0.19045.0
  • .NET 6.0.28
  • DPI 96dpi (no scaling)
  • Portable: False

Issue description

System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at GitUI.CommandsDialogs.FormCommit.FormatAllText(Int32 startLine)
   at GitUI.CommandsDialogs.FormCommit.Message_TextChanged(Object sender, EventArgs e) in C:\projects\gitextensions\GitUI\CommandsDialogs\FormCommit.cs:line 2785
   at GitUI.SpellChecker.EditNetSpell.TextBoxTextChanged(Object sender, EventArgs e) in C:\projects\gitextensions\GitUI\SpellChecker\EditNetSpell.cs:line 640
   at System.Windows.Forms.TextBoxBase.OnTextChanged(EventArgs e)
   at System.Windows.Forms.RichTextBox.WmReflectCommand(Message& m)
   at System.Windows.Forms.RichTextBox.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, WM msg, IntPtr wparam, IntPtr lparam)

Pressed standard Commit button instead of "Complete" merge, following successful conflict resolution of a merge from a commit that's "mid stream" on one branch, to the head of another branch.

Steps to reproduce

  1. Merge from a commit that's mid-stream on one branch, to the head of another branch.
  2. Ensure this merge will get at least one conflict to resolve.
  3. (For me, this was a big merge involving MANY files but few conflicts. No idea if this contributes to the error or not.)
  4. Resolve the conflicts.
  5. Shut down and re-start Git Extensions.
  6. Press the standard "Commit" button, NOT the "Continue" (merge) button.
  7. (Possible contributing factor: specified 30 previous commits to be added into the comment. It's a LONG comment that needs editing.)
  8. Get the Index out of Range exception.

Did this work in previous version of GitExtensions?

No response

Diagnostics

No response

Copy link

Potential duplicates:

  • #8607
  • #10219
  • #10493
  • #10501
  • #10563
  • #10779
  • #10788
  • #10822
  • #10844
  • #10898
  • #10900

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant