While we know that Mac is not a serious platform for production installations of Go, it is often the first system where Go is installed – to evaluate or try out things. Considering this, Go has always supported Mac. However, thanks to security changes made by Apple from OSX 10.7 (a.k.a Lion), Go installation broke on Mac. There was a workaround of course, but it is not the same.
The Go 12.3.1 app for Mac works on Lion and Mountain Lion. We believe this will help potential evaluators, anyone who wants to try out Go on their laptops.
UI improvements in Console and Custom tabs
One of the issues reported by multiple customers have been that the console log is truncated though there is space on the screen
This has been now fixed. Console log extends to the height of the screen and no longer has a separate scroll bar.
The same has been done for Custom tabs as well.
Another UI improvement is the introduction of a Top button to allow user to quickly navigate to the top of the page.
Logging LDAP failures
One of the challenges faced by enterprise customers is users being unable to login to Go and there is no information to indicate why. There is a way to get this information by enabling debug logs, but this is cumbersome.
We have improved the handling of this scenario by displaying a more informative user message on the screen for login failures. This also contains a link to the help document which details the possible reasons for login failure.
In addition, any LDAP failure is logged by default in the server logs for easy reference. An example entry from go-server.log
2012-10-07 16:22:57,070 INFO [1320529256@qtp-2063574763-15] CachedCruiseConfig:94 - Finished notifying all listeners
2012-10-07 16:23:02,249 ERROR [1862532266@qtp-2063574763-14] AuthenticationProcessingFilter:66 - org.springframework.security.AuthenticationServiceException: abcd.thoughtworks.com:389; nested exception is javax.naming.CommunicationException: abcd.thoughtworks.com:389 [Root exception is java.net.UnknownHostException: abcd.thoughtworks.com]; nested exception is org.springframework.ldap.CommunicationException: abcd.thoughtworks.com:389; nested exception is javax.naming.CommunicationException: abcd.thoughtworks.com:389 [Root exception is java.net.UnknownHostException: abcd.thoughtworks.com]
Filter agents by exact search
The number of agents in an enterprise installation can typically be 100 or more. A Go administrator is interested in filtering the agents by various criteria. Go supports this. One of the requests has been for filtering by exact search.
For instance, specifying resource:linux matches linux_old, linux new, anotherlinux and linuxnew.
But how do I filter only agents that match linux?
By specifying the search value in quotes, this can now be achieved. So, resource:”linux” now filters the agents only by linux.
Bug fix: null when triggering a pipeline on environments page
You will no longer see “null”.
Disclaimer: The statements and opinions expressed in this article are those of the author(s) and do not necessarily reflect the positions of Thoughtworks.
Thoughtworks acknowledges the Traditional Owners of the land where we work and live, and their continued connection to Country. We pay our respects to Elders past and present. Aboriginal and Torres Strait Islander peoples were the world's first scientists, technologists, engineers and mathematicians. We celebrate the stories, culture and traditions of Aboriginal and Torres Strait Islander Elders of all communities who also work and live on this land.
As a company, we invite Thoughtworkers to be actively engaged in advancing reconciliation and strengthen their solidarity with the First Peoples of Australia. Since 2019, we have been working with Reconciliation Australia to formalize our commitment and take meaningful action to advance reconciliation. We invite you to review our Reconciliation Action Plan.