fixing linting issues

Author: Azoam

dogfood/client/dogfood_client.go

@@ -73,10 +73,12 @@ func printAndLog(logLine string) {
 		if err != nil {
 			log.Fatal(err)
 		}
-		if err := f.Close(); err != nil {
+
+		if err = f.Close(); err != nil {
 			log.Fatal(err)
 		}
-		if _, err := os.Stat("/mnt/data/logging"); errors.Is(err, os.ErrNotExist) {
+
+		if _, err = os.Stat("/mnt/data/logging"); errors.Is(err, os.ErrNotExist) {
 			f, err = os.Create("/mnt/data/logging")
 			if err != nil {
 				log.Fatal(err)
@@ -92,6 +94,7 @@ func printAndLog(logLine string) {
 		if err != nil {
 			log.Fatal(err)
 		}
+
 		if err = f.Close(); err != nil {
 			log.Fatal(err)
 		}
@@ -149,7 +152,9 @@ func stringifyCatalogItems(items []*pb.CatalogItem) string {
 func main() {
 	// create and eventually close connection
 	printAndLog(fmt.Sprintf("connecting to %v...\n", serverAddr))
+
 	var opts []grpc.DialOption
+	
 	opts = append(opts, grpc.WithInsecure())
 	opts = append(opts, grpc.WithBlock())
 
@@ -166,7 +171,7 @@ func main() {
 
 	// generate and use client
 	client := pb.NewChaosDogfoodClient(conn)
-	
+
 	printAndLog("We successfully generated the client, getting ready to send requests")
 
 	sendsLotsOfRequests(client)

dogfood/tester/dogfood_tester.go

@@ -51,22 +51,19 @@ func handleRequests() {
 }
 
 func main() {
-	//TODO
+	// TODO
 	//1. Wait for a request to run a test
 	//4. Find out what relevant metrics would be (if only testing CPU, only CPU metrics matter)
-	//5. Get relevant metrics from datadog for the past 3 minutes
-	//6. Deploy the version to test
-	//7. Once the testing version is deployed and read, depending on the request, create individual disruptions
-	//8. For each disruption, let it bake for 3 minutes
-	//9. After baking, grab the last 3 minutes of data to compare to the stable 3 minutes of data
-	//10. If data looks rights, pass the test and move on to the next disruption and repeat starting from 8 until all
+	//5. Get relevant metrics from datadog for the past 3 minutes, stable metrics
+	//6. Depending on the request, create individual disruptions
+	//7. For each disruption, let it bake for 3 minutes
+	//8. After baking, grab the last 3 minutes of data to compare to the stable 3 minutes of data
+	//9. If data looks rights, pass the test and move on to the next disruption and repeat starting from 8 until all
 	//    disruptions are completed for the given request
 	//11. For each disruption removal, wait 2 minutes to make sure the state of world goes back to stable values measured
 	//    in the beginning
-	//12. Once the entire request is finished, do 1 of 2 things:
-	//    a. If queue is empty, return the chaos controller in the staging cluster back to latest:stable
-	//    b. If queue is not empty, take the next request
 	STATUS = "initializing"
 	logger = &zap.SugaredLogger{}
+
 	handleRequests()
 }