In the OS X app, the menu items look like this:

• Catlight
  • Open Dashboard
  • Exit
• Edit
  • Add Connection to TFS or VSTS
  • Add Connection to AppVeyor
  • Add Connection to Jenkins
  • Add Connection to Travis CI
  • Settings
  • Cut
  • Copy
  • Paste
  • Select All
  • Start Dictation
  • Emoji & Symbols
• Help and Feedback
  • View Help
  • Provide a Suggestion
  • Report a Problem
  • About

This is not according to Apple's Human Interface Guidelines. Instead, I suggest the menus should look more like this:

• Catlight
  • About Catlight
  • Preferences...
  • Add Connection...
  • Quit Catlight
• Help
  • View Help
  • Provide a Suggestion
  • Report a Problem

This is more in line with

Hello,

I have been looking at using CatLight in our organisation and you guys have a fantastic tool!

I have one rather significant issue however. Cancelled builds seem to show up as failed. This makes my catlight red most of the time as we tend to let our pull request builds cancel mid way through as we dont have them as a required pass to complete the PR.

I have read 4 years ago a post from you guys that this is related to the fact that TFS cancels after a timeout. I believe it now errors at timeout if

Configuration Needed

Authentication needed. Error message: TF400813%3a+Resource+not+available+for+anonymous+access.+Client+authentication+required.

When I click the Configure link after it, it reconnects.

This is not desirable if I'm expecting notifications and can't tell that it is down unless I go to the dashboard.

We have found a problem with TFS API - it does not sort XAML builds properly. As a result, occasionally it will not provide a latest build information, but return older builds instead. We have submitted bug report to Microsoft and are looking for workarounds. 

This applies only to XAML builds. Other types of builds and other build systems should work fine.

I'm the DevOps guy and for me CatLight installed perfectly fine. But I asked my developers to install CatLight so they can see very quickly if/when their checkins break builds. For many of them upon opening setup.exe, the dashboard shows gears spinning indefinitely.

I had Catlight running initially and liked it a lot. But after installing some prerequisites for other software (including .NET 3.5) on my machine, I've started getting this error when running it:

 It keeps trying the same thing for a minute or two before giving up.

I've tried repairing some of the installed programs like .NET 4.5.2 and MVC 4 but to no avail. I also cleared everything in %APPDATA%\Catlight and reinstalled Catlight.

Any insight would be helpful, so I don't have to go looking for another program to keep me notified of my builds :)

I use the [GitHub Organization Folders](https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Organization+Folder+Plugin) connected to a GitHub Enterprise along with the new Pipeline goodness to do builds.

However, catlight only shows the top-level folders.  I expected it to show the nested builds underneath.

Here is an example:

• OrgOne
  • Uno
    • production
  • Eins
    • master
    • v2.x
    • experimental
  • Singular
    • master
• OrgTwo
  • Duo
    • master
  • Zwei
    • master
  • Doubled
    • master
    • PR-10
    • PR-11
    • PR-12

Only the leaf nodes are actual buildable jobs. Everything else is a folder.  The Jobs that have names like `PR-XX` are github pull requests are expected to be transient (depending on the life of the pull request) do not show that

I get a windows notification that my build has started. I click the dashboard and it still doesn't have the update. Even after a couple minutes the dashboard still does not update the information. My polling interval is set to 60 seconds.

Today CatLight prompted me to re-init my TFS connection which is for a Visual Studio Online account. When I click Save on the TFS connection settings screen, it opens a page in my browser to authorize CatLight. When I click Accept, I get this message (base URL obfuscated on purpose):

Connection problem There was a problem accessing your account: Response status code does not indicate success: 302 (Found). Please make sure that: Collection url is correct and accessible: https://xxxxxxx.visualstudio.com:443/defaultcollection User that is logged in this browser have access to https://xxxxxxx.visualstudio.com:443/defaultcollection You can close this window and return to CatLight app. If you

I've upgraded to the latest build (v 2.0.14 Beta), and tried to change the builds I monitor, after doing this I started seeing the message: Response status code does not indicate success:500 (Internal Server Error)

Looking at fiddler most of the projects being polled are fine except 1 which is returning the 500. However I am not subscribing to any builds associated with that project so I wouldn't expect this one failing to bring down the rest.

Hi,

I am unable to continue after SelectionBuilds screen.

- Server: on tfs 2015 sp1 on-premises

- Client: win10 updated (11/16).

- Catlight: v2.1.3 Beta

Process:

=> I go the config connection screen.

=> I access to all my projects and builds in the SelectionBuilds screen.

=> I select 0 or n projects.

=> Any case after, i have got error screen with: Offline "index was outside the bounds of the array"

I try the same action on an win8 with same user and connection string and it's work...

Thanks by advance.

Hi,

I am using CatLight on Windows 10 connected to TFS online. After a windows sleep catlight showed the status of TFS from 10 hours ago (i.e. before the sleep) and would not refresh. There was no sign or error, nothing. A manual refresh would have helped though ;)

Thanks and miaow for the nice tool!!!

François

Hi,

At the moment, CatLight cannot connect to teamcity if only NTLM is used. GitExtensions is having the same Issue currently. To workaround this issue it's possible to get an authentication cookie when ntlmlogin.html page is browsed. This authentication cookie can than be passed for further rest calls.

a powsershell sample can be found in the answer from mclayton on http://stackoverflow.com/questions/11020066/log-onto-teamcity-server-using-rest-api-without-passing-credentials-in-the-url

Br, Daniel

Then I open the Dashboard on my secondary monitor and then log onto that computer via RDP (with only one monitor) the dashboard is somehow hidden. Even after I restart CatLight it memorizes that it was on the other monitor and can't get it into view. 

Using Windows 10. CatLight v 2.3.1

If your CatLight cannot connect to Jenkins and shows 500 server error, please check your server version. It is displayed at the bottom of every Jenkins page.

We support Jenkins versions starting from 1.644 (released in early 2016) and 2.x 

Older version of Jenkins have bugs in the API that can result in server errors. If you have old version, consider upgrading your server.

Currently have CatLight connected to Jenkins version 2.46.2. CatLight will give notification when builds start/finish but will give the above error when I try to start a build through CatLight. Proper credentials are provided for Jenkins login. 

OS is MacOS 10.13 (high sierra)

When running catlight i get a blank screen and an error that localweb has crashed running localweb from terminal i get the following logs

Initializing logging. path: /Applications/Catlight.app/Contents/Resources/LocalWeb/wwwroot OS: 'Mac' AppData path: '/Users/oranshus' Initialized logging. Hosting environment: Production Content root path: /Applications/Catlight.app/Contents/Resources/LocalWeb Now listening on: http://localhost:5000 Application started. Press Ctrl+C to shut down. [1] 7218 segmentation fault ./LocalWeb

Recently we have seen problems with the "I will investigate" functionality. It has mainly 2 issues:

1. A person can "hang" as "investigating" on other persons' Catlight instance, while the person in question has a Catlight instance that says he/she is not currently investigating anything. - this one is critical, because we have errors that aren't looked into for a long while, until somebody asks the person why he/she hasn't fixed the error yet...!
2. "Investigating" isn't cleared after a green build, but must instead manually be cleared. This also leads to wrong behavior, because if a build breaks, a person investigates,

I get the above error message, when trying to click "Settings" on the TFS-server. I am using version 2.15.3

Hi,

since today I get the following error message "Invalid URI: The Uri scheme is too long.". And tried a little bit and found out that is because I choosed too many build definitions. If I deselect some of the definitions, everything works fine.

Cheers

Jan