Uploaded image for project: 'Sourcetree for Windows'
  1. Sourcetree for Windows
  2. SRCTREEWIN-6674

SpellChecker Error

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • None
    • 1.9.9.20, 1.9.10.0
    • None

    • Operating System: Windows 10

    • Severity 2 - Major

      Everytime I open SourceTree I get this error message:

      SpellChecker Error

      SourceTree detected the following invalid Dictionary file references.
      These are known to cause performance issues.

      Do you want to remove these invalid dictionaries?

      [ Yes ] [ No ]

       Pressing "Yes" open SourceTree normally but the error appears the next time I open SourceTree.

      How to solve it?

        1. 2016-12-13 10_26_53-.png
          2016-12-13 10_26_53-.png
          7 kB

            [SRCTREEWIN-6674] SpellChecker Error

            Vipin Yadav (Inactive) made changes -
            Assignee New: Vipin Yadav [ e85ff1f4514c ]
            Oleksandr Naumenko (Inactive) made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Long Term Backlog [ 12073 ] New: Closed [ 6 ]

            Oleksandr Naumenko (Inactive) added a comment - - edited

            These changes will appear in the 3.4.6 release

            Oleksandr Naumenko (Inactive) added a comment - - edited These changes will appear in the 3.4.6 release

            Steve Sobol added a comment -

            Guys,

            I stopped using SourceTree back in 2018, when you started requiring Bitbucket accounts (God only knows why; I had an Atlassian account, and I can't figure out why that wasn't good enough).

            But I do use other Atlassian products (Jira Cloud and Jira Service Management).

            This bug, marked as severity 2 and high priority, has now remained open and unresolved  for FIVE YEARS.

            And as an Atlassian customer, I find that alarming.

            What's the problem here? Did you guys just decide you didn't want to fix the problem?

            Steve Sobol added a comment - Guys, I stopped using SourceTree back in 2018, when you started requiring Bitbucket accounts (God only knows why; I had an Atlassian account, and I can't figure out why that wasn't good enough). But I do use other Atlassian products (Jira Cloud and Jira Service Management). This bug, marked as  severity 2 and  high priority , has now remained open and unresolved  for  FIVE YEARS. And as an Atlassian customer, I find that alarming. What's the problem here? Did you guys just decide you didn't want to fix the problem?
            Apoorv Singhal (Inactive) made changes -
            Labels Original: spellchecker New: DevTriaged spellchecker
            Apoorv Singhal (Inactive) made changes -
            Status Original: Needs Triage [ 10030 ] New: Long Term Backlog [ 12073 ]
            Apoorv Singhal (Inactive) made changes -
            Status Original: Gathering Impact [ 12072 ] New: Needs Triage [ 10030 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: JAC Bug Workflow v3 [ 3446865 ] New: SRCTREE JAC Bug Workflow [ 3741119 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: SourceTree Bug Workflow [ 1629474 ] New: JAC Bug Workflow v3 [ 3446865 ]
            Status Original: Verified [ 10005 ] New: Gathering Impact [ 12072 ]

            Steve Sobol added a comment -

            Deleting my Microsoft Office custom dictionary worked, but I was only willing to do it because the dictionary had a handful of entries. And I did something today, I think, that caused the custom dictionary to be created again, so I'm getting the message again.

            Why? – WHY IS THIS HAPPENING when I have the "spell-check commit messages" feature DISABLED?

            Steve Sobol added a comment - Deleting my Microsoft Office custom dictionary worked, but I was only willing to do it because the dictionary had a handful of entries. And I did something today, I think, that caused the custom dictionary to be created again, so I'm getting the message again. Why? –  WHY IS THIS HAPPENING when I have the "spell-check commit messages" feature DISABLED?

              e85ff1f4514c Vipin Yadav (Inactive)
              eb792aac5398 Benjamin Fernandez
              Affected customers:
              17 This affects my team
              Watchers:
              20 Start watching this issue

                Created:
                Updated:
                Resolved: