fixed duplicate experiment name issue (#4210)

* fixed dupicate experiment name

Signed-off-by: Sarthak Jain <[email protected]>

* fixed text

Signed-off-by: Sarthak Jain <[email protected]>

* fixed text

Signed-off-by: Sarthak Jain <[email protected]>

---------

Signed-off-by: Sarthak Jain <[email protected]>
Co-authored-by: Saranya Jena <[email protected]>

Author: SarthakJain26

chaoscenter/graphql/server/pkg/chaos_experiment/handler/handler.go

@@ -106,7 +106,7 @@ func (c *ChaosExperimentHandler) SaveChaosExperiment(ctx context.Context, reques
 	if wfDetails.ExperimentID == request.ID {
 		logrus.WithFields(logFields).Info("request received to update k8s chaos experiment")
 		if wfDetails.Name != request.Name {
-			err = c.validateDuplicateExperimentName(ctx, request.ID, request.Name)
+			err = c.validateDuplicateExperimentName(ctx, projectID, request.Name)
 			if err != nil {
 				return "", err
 			}
@@ -120,15 +120,15 @@ func (c *ChaosExperimentHandler) SaveChaosExperiment(ctx context.Context, reques
 		return "experiment updated successfully", nil
 	}
 
-	err = c.validateDuplicateExperimentName(ctx, request.ID, request.Name)
+	err = c.validateDuplicateExperimentName(ctx, projectID, request.Name)
 	if err != nil {
 		return "", err
 	}
 
 	// Saving chaos experiment in the DB
 	logrus.WithFields(logFields).Info("request received to save k8s chaos experiment")
 
-	err = c.chaosExperimentService.ProcessExperimentCreation(context.TODO(), newRequest, username, projectID, wfType, revID, nil)
+	err = c.chaosExperimentService.ProcessExperimentCreation(ctx, newRequest, username, projectID, wfType, revID, nil)
 	if err != nil {
 		return "", err
 	}

chaoscenter/web/src/strings/strings.en.yaml

@@ -653,10 +653,7 @@ noKubernetesChaosInfrastructureFound: >-
 noLogs: Sorry, Logs are currently not available
 noMonitoredService: No monitoring services found for
 noProbeDescription: >-
-  Probes are pluggable checks that can be defined within the ChaosEngine for any
-  Chaos Fault. The experiment pods execute these checks based on the mode they
-  are defined in & factor their success as necessary conditions in
-  determining the verdict of the experiment
+  Probes are lightweight, self-contained scripts that can be run against Kubernetes applications to gather information about their behavior under stress and failure conditions.
 noProbeExecution: No Probe executions found
 noProbeExecutionDetails:
   subtitle: >-