Hi, I have debian stretch installed, and I tried to install Catlight 2.15.4, I saw that it needs libicu52 which it does not exist on stretch, so I used jessie repo to get it, then install Catlight-2.15.4.deb with dpkg, it started but with empty content, it has only menu, but it does not work if I try to sign in, or add a connection, but it can redirect me through the browser if I click on "Report a Problem".
I attached a screenshot for it.
I get the above error message, when trying to click "Settings" on the TFS-server. I am using version 2.15.3
I just stumbled onto an issue.
I was wondering why the build investigation feature was not showing up, although I added my credentials for the jenkins build server.
It turns out that the feature only works when you provide base url for the jenkins server:
if you provide a link to a filtered view like
the jobs will show show up in catlight, like they are specified in the jenkins view, but the build investigation feature will not work.
This is not a big problem and can be avoided easily. But I thought you might want
Unfortunately CatLight does not seem to be working.
I seem to be able to successfully authenticate with my domain account and select the Builds, Releases and Workitems, however, I then get a 400 error.
Could you please advise what my issue may be?
Please refer to attached log files and screenshot.
I get a blue screen suggesting the below:
Cannot start the app
Please make sure that you have KB2533623 and Universal CRT installed.
Application logs are at %APPDATA%\Catlight\Logs
You can send the logs to email@example.com and we will try to fix this.
CatLight likes to update itself in the background, without me knowing about that. Anyway, when it updates itself, it always creates a shortcut on my desktop. I don't like this behavior because I have to delete the shortcut everytime. I see no point of having a shortcut on my desktop when CatLight is always available via the tray and is set to start with Windows.
Please do not re-create the shortcut after user deletes it.
On Windows PC trying to log in to the app to active the licens I get this error: an error occurred while sending the request - we have a http proxy but as far as we can see it allows the http/https traffic to *.catlight.io to pass through. Is it possible to active some verbose logging in catlight app to investigate further? Regards Morten
Not able to add third email to 3 user subscription. Website just hangs
The connection logs in as an admin to our Jenkins server. "All builds" is checked for "Show build notifications". All options are checked for "Show notifications". Dashboard is showing old, failed build when build has passed (CatLight v2.11.10; Jenkins 2.60.1). Why are later builds not showing up?
"I will investigate" shows error when clicked (and hides estimated build time) and spanner disappears before can be clicked
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.
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:
- 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.
- 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.
Not difference between disabled build def's with last build broken, and active build def's with last build broken
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.
I am trying to connect for on-premise TFS, and alwais get the same error:
"Unexpected character encountered while parsing value: <. Path '', line 0, position 0."
and my Project Collection Url, user and password (domain\user) are correct.
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
Getting the "Something Broke Down"error when trying to add a TFS connection.
Log file shows the following:
[2017-02-01 15:51:10.817] [DEBUG] main - LocalWebService started [2017-02-01 15:51:10.819] [DEBUG] main - ApplicationManager start complete [2017-02-01 15:51:10.819] [DEBUG] main - Opening dashboard [2017-02-01 15:51:12.831] [DEBUG] main - App state changed. User signed in: false [2017-02-01 15:51:13.828] [DEBUG] main - Opened dashboard on start: http://127.0.0.1:60295/?onStart=true [2017-02-01 15:51:13.829] [DEBUG] main - Tray app initialization complete [2017-02-01 15:51:15.950] [INFO] console - Tray icon status: [object Object]. [2017-02-01 15:51:38.799] [INFO] console - web stdout: fail [2017-02-01 15:51:38.799] [INFO] console - web stdout: : Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware An unhandled