• Type: Bug
• Resolution: Fixed
• Priority: Medium
• Fix Version/s: 1.9.4
• Affects Version/s: 1.9.3
• Component/s: General
• Labels:

  None
• Environment:

  Mac OS 10.9.3

1. 

   tns_client__Git_.png

   560 kB

   31/May/2014 7:46 AM

[SRCTREE-2425] No files to be staged

Collapse comment: Steve Streeting (Inactive) added a comment - 04/Jun/2014 10:11 AM

Steve Streeting (Inactive) added a comment - 04/Jun/2014 10:11 AM

This was a bug which usually occurred when you switched between views (log and file status for commit usually) and there was some uninitialised state that was incorrectly used to sync the views up in transition. It's not related to the auto-refresh although when an auto-refresh occurred that would 'fix' the result.

Expand comment: Steve Streeting (Inactive) added a comment - 04/Jun/2014 10:11 AM

Steve Streeting (Inactive) added a comment - 04/Jun/2014 10:11 AM This was a bug which usually occurred when you switched between views (log and file status for commit usually) and there was some uninitialised state that was incorrectly used to sync the views up in transition. It's not related to the auto-refresh although when an auto-refresh occurred that would 'fix' the result.

Collapse comment: KieranA added a comment - 31/May/2014 5:16 PM

KieranA added a comment - 31/May/2014 5:16 PM

At the core of it, it all comes from the FSEvents API which is Apple's, based on that would it result in an eventual call to git status to determine the state of your repository.

Based on the current state of SourceTree from your screenshot it looks like there's a bug as no files are listed and yet a diff is shown. The diff should be shown based on a file selection.

Is there anything in Console.app to show SourceTree's doing something wrong, perhaps?

Cheers

Expand comment: KieranA added a comment - 31/May/2014 5:16 PM

KieranA added a comment - 31/May/2014 5:16 PM At the core of it, it all comes from the FSEvents API which is Apple's, based on that would it result in an eventual call to git status to determine the state of your repository. Based on the current state of SourceTree from your screenshot it looks like there's a bug as no files are listed and yet a diff is shown. The diff should be shown based on a file selection. Is there anything in Console.app to show SourceTree's doing something wrong, perhaps? Cheers

Collapse comment: Brendon McLean added a comment - 31/May/2014 7:54 AM

Brendon McLean added a comment - 31/May/2014 7:54 AM

I actually wonder if this is moderately related to the fact the fsnotify part of SourceTree doesn't seem to work either.

Expand comment: Brendon McLean added a comment - 31/May/2014 7:54 AM

Brendon McLean added a comment - 31/May/2014 7:54 AM I actually wonder if this is moderately related to the fact the fsnotify part of SourceTree doesn't seem to work either.