Go 1.9 Beta 1 finally released

Go1.9beta1 information
15 June 2017   1696

Great news for all Go enthusiasts, go1.9beta1, a beta version of Go 1.9 have been just released. It is piece from the master branch of the revision go1.9beta1.


Open source programming language developed by the members of Google team and contributors of open source community

At the moment, there are no known problems or issues.
Developers ask every Go coder to try running production load tests and unit tests with this new version. Report any problems using the issue tracker.

If you already have Go installed, the easiest way to try go1.9beta1 is by using this tool. Feel free to download all distributions from the usual place, here.

Gradual code repair while moving a type between packages is now supported in Go thanks to type aliases. List of all other changes in Go 1.9, can be found in the draft release notes.

Go 1.9 docs available here.

ClusterFuzz to be Open Source Now

Program's code is written in Python and Go, and distributed under the Apache 2.0 license
08 February 2019   232

Google has opened the source code for the ClusterFuzz platform, intended for fuzzing code testing using a server cluster. In addition to coordinating the execution of checks, ClusterFuzz also automates the execution of tasks such as sending a notification to developers, creating an application for a patch (issue), tracking a bug fix, and closing reports after a patch. The code is written in Python and Go, and distributed under the Apache 2.0 license. ClusterFuzz instances can run on Linux, macOS and Windows systems, as well as in various cloud environments.

Since 2011, ClusterFuzz has been used in the depths of Google to detect errors in the Chrome codebase and to ensure the operation of the OSS-Fuzz project, in the framework of which continuous fuzzing testing of open source software was organized. In total, ClusterFuzz has revealed more than 16 thousand errors in Chrome and more than 11 thousand errors in 160 open source projects participating in the OSS-Fuzz program. Due to the continuous process of checking the current code base, errors are usually caught within a few parts after the code is introduced and the changes causing them.