Clicking "I will investigate" message generates a "Error: Request failed with status code 500" message and am unable to click the config icon (spanner) as disappears straight away.

This prevents you dismissing or selecting to stop investigating, which then prevents you seeing the estimated build completion time for a fresh build.

With dual monitors its sometimes hard to see when a notification pops up in the corner, I'm like a horse with blinds on sometimes and I would love to be able to have a bigger notification or be able to turn the entire screen red, for just a second or two when the build fails that way I can jump right on it instead of having to check the corner.

I have a task showing up twice in the list

This usually happens when the app cannot connect to the online service.

Please check your firewall, and make sure that CatLight.exe and LocalWeb.exe processes are allowed to connect to the Internet.

If you use a proxy server that requires manual configuration, you can go to Edit menu/Settings/Proxy and provide connection details.

For more information, you can check the application logs at %AppData%\CatLight\Logs\log.txt

Here is a sample error message, indicating a connection problem:

Bonjour , 

Pouvez-vous m'envoyer la facture relative à la commande [#2561-0780] ou m'expliquer la procédure afin de la télécharger ? 

Voici mon adresse mail : [email protected]

Bien à vous , 

Samuel Esposto 

Is this information stored at a CatLight server? Or do I have to provide a central location (database?) in my company to store and share this information for all clients?

I have just installed CatLight 2.10.3 on a Windows 10 machine, but it won't run. The gears spin for a minute or two, and then the screen says "cannot start the app".

I tried installing the CRT but the installer said that it wasn't applicable to my version of windows.

I have attached the log files.

When you have acknowledged a failing build (git branch) and the build turns green again it is still marked as acknowledged. You can right-click the green build and remove the "acknowledged check".

The "acknowledged status" should be resetted as soon as build turns green.

Not sure about the current side-effects but I would guess that you would not notice when build turns red again since it is still marked as acknowledged. Unfortunately this is not too easy to reproduce.

BR, Matthias

If allowable, please update with instructions to accomplish. Regards, Chris Wasem

When I add a VSTS connection, I'm properly prompted to Accept or Deny

I click on Accept, and I get redirected to localhost with an AccessToken in the URI, however the local server reports the following.

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

1. When giving Catlight it's own desktop to use in full screen dashboard view, the dashboard will move to it's own space after clicking on a toolbar notification.
2. Logging back into Macbook Pro from sleep mode, the full screen dashboard & Catlight in general freezes; It requires activity monitor manual forced exit to correct. I've tested just stretching the Catlight window til almost to full screen & no freezing.

In the dashboard, there are no difference between disabled build def's with last build broken, and active build def's with last build broken, which Means, we cannot distinguish between the failed builds to work on, and which to not work on.

We have about 10 out of 50 build definitions that are disabled due to old legacy-issues, and which we do not want to remove, because of future need to activate them.

We had a developer that broke a number of builds and kept trying (without investigating). Because they shouldn't have even created the CI builds directly, I removed them in the VSTS build page but now Catlight still shows them all as broken and attempts to refresh are not removing them. Seems Catlight should remove build status for builds that no longer exist.

CatLight works with GIT branches. It will show a separate build history for each branch and pull request.

 We divide branches in four categories:

• Primary - they will be always visible on the dashboard. They include branches like master, develop, trunk, etc.
• Short-lived - those are branches for pull requests. CatLight will show them for one day on the dashboard.
• Other - this is a category for feature, bugfix and release branches. They will be tracked while they are active, and had at least one build in the past week.
• Ignored - those branches will not be monitored. You can

Show them with a separate build record, like a branch

The jobs are listed correctly in the interface but when I click on a job link, I'm redirected to the slave URL instead.

Expected URL destination: http://master-server/jenkins/job/myjob/56 (using nginx reverse proxy)

I got instead: http://myslave-server:8080/job/myjob/56 which doesn't exist (error 404)

Thanks.

Hi Tim,

Since version 2.7.0 I cannot connect to our local TFS on prem anymore.

I keep seeing this error message:

Offline

Sequence contains no elements

Sometimes a restart of the app fixes it temporarily. But then all of a sudden, boom, same error again.

I was hoping this bug had been fixed in v 2.7.1 but unfortunately it isn't.

Hope you can fix this since we really rely on Catlight nowadays :) (And we're paid customers... ;)

It appears that i have the Master project in Jenkins twice, one that states that the build is broken and needs investigating, the other one states that no build has ever started on that project. This is regarding Jenkins.

I have attached a picture to see exactly what is happening.

Thanks.

When a Jenkins' build name contains "/", it is displayed as "%2F" 

 2017-03-13 20:51:39.1321 |  WARN |        SharedStateManager | 47 | Exception in SpaceUpdaterHandler System.Net.Http.HttpRequestException: Error while copying content to a stream. ---> System.IO.IOException: Unable to read data from the transport connection. The connection was closed before all data could be read. Expected 3898 bytes, read 0 bytes.