Adding lock to avoid concurrent access

[b-gopalswami]

---

Below is a summarization created by an LLM (gpt-4-0125-preview). Be mindful of hallucinations and verify accuracy.

Why

The changes aim to enhance thread safety and maintainability in the fake record component by introducing a mutex for protecting concurrent access to shared data and making minor adjustments to maintain consistency.

What

• framework/components/fake/record.go
  • Added sync.Mutex to the imports. This change enables the use of mutexes for thread-safe operations.
  • Introduced a mutex mu at the package level. This mutex is used to protect the concurrent access to the shared Records structure, ensuring thread safety.
  • Wrapped the update to the Records data structure inside a lock and defer unlock pattern using the newly introduced mutex. This modification ensures that concurrent writes to the Records data structure are safely serialized, preventing data races or corruption.

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube