High volume data generation on top of MongoDB

[MattG57]

The calendarClockServiceTests.ts file simulates a calendar-clock function that runs various data generation tasks on an hourly basis. It connects to a MongoDB database and performs the following tasks:

Survey Generation: Randomly generates surveys 20% of the time during weekdays (Monday to Friday) between 6 AM and 11 PM.
Seats Generation: Generates seat data for each member of the team every hour.
Metrics Generation: Generates metrics data daily at 11 PM.
The script loops through each hour within a specified date range, incrementing the datetime parameter each cycle, and calls the respective data generation functions. It also retrieves all team members from the database to use in the seats generation process.

[github-advanced-security]

ESLint found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.

[github-actions]

Dependency Review

The following issues were found:

• ❌ 1 vulnerable package(s)
• ✅ 0 package(s) with incompatible licenses
• ✅ 0 package(s) with invalid SPDX license definitions
• ✅ 0 package(s) with unknown licenses.
• ⚠️ 5 packages with OpenSSF Scorecard issues.

View full job summary

To fix the problem, we need to replace the use of Math.random() with a cryptographically secure random number generator. In Node.js, we can use the crypto module's randomInt function to generate secure random integers. This will ensure that the generated values are not predictable and enhance the security of the application.

We will:

1. Import the crypto module.
2. Replace all instances of Math.random() with crypto.randomInt.

To fix the problem, we need to ensure that the user input is interpreted as a literal value and not as a query object. This can be achieved by using the $eq operator in the MongoDB query. This approach ensures that the user input is treated as a literal value, preventing any potential NoSQL injection attacks.

To fix the problem, we need to ensure that the user input is properly sanitized before being used in the database query. We can use the $eq operator to ensure that the id is treated as a literal value and not as a query object. This will prevent any potential NoSQL injection attacks.

To fix the problem, we need to ensure that the user-provided data is properly sanitized before being used in a MongoDB query. We can use the $eq operator to ensure that the user input is interpreted as a literal value and not as a query object. This will prevent NoSQL injection attacks.

To fix the problem, we need to ensure that the user-provided data is properly sanitized or validated before being used in a database query. For MongoDB, we can use the $eq operator to ensure that the user input is interpreted as a literal value and not as a query object. This will prevent any potential NoSQL injection attacks.

We will modify the updateSurvey method in backend/src/services/survey.service.ts to use the $eq operator for the id field in the query.

[Copilot]

Copilot reviewed 60 out of 75 changed files in this pull request and generated 1 comment.

Files not reviewed (15)

• .vscode/tasks.json: Language not supported
• Dockerfile: Language not supported
• backend/github-manifest.json: Language not supported
• backend/package.json: Language not supported
• backend/src/tests/mock/metrics-gen/example.json: Language not supported
• backend/src/tests/mock/seats-gen/seatsExampleTest.json: Language not supported
• backend/src/tests/mock/survey-gen/exampleSurvey.json: Language not supported
• README.md: Evaluated as low risk
• backend/src/tests/mock/metrics-gen/runExampleMock.ts: Evaluated as low risk
• backend/jest.config.ts: Evaluated as low risk
• backend/src/tests/mock/metrics-gen/runMock.ts: Evaluated as low risk
• backend/src/tests/mock/metrics-gen/mockGenerator.ts: Evaluated as low risk
• backend/src/tests/mock/mock.mongo.ts: Evaluated as low risk
• backend/src/tests/mock/seats-gen/runSeatsGenerator.ts: Evaluated as low risk
• backend/src/tests/mock/seats-gen/mockSeatsGenerator.js: Evaluated as low risk

Comments suppressed due to low confidence (3)

backend/src/tests/mock/seats-gen/mockSeatsGenerator.ts:25

• The variable 'lastActivityAt' should have a specific type instead of 'any'. Consider using 'string' or 'Date'.

const lastActivityAt : any = seat.last_activity_at;

backend/src/tests/mock/seats-gen/mockSeatsGenerator.ts:55

• Use '===' instead of '==' for comparing dates.

if (newActivity == currentActivity ){

backend/src/tests/mock/seats-gen/mockSeatsGenerator.ts:74

• The property 'specificUser' is not defined in the 'SeatsMockConfig' type. Ensure it is part of the configuration.

seat.specificUser = this.config.specificUser;

Tip: If you use Visual Studio Code, you can request a review from Copilot before you push from the "Source Control" tab. Learn more

[Copilot]

The division by (1000 * 60 * 60 * 24) should be inside the Math.floor function to ensure the correct number of days is calculated. The corrected line should be: return addDays(this.config.startDate, Math.floor(Math.random() * ((this.config.endDate.getTime() - this.config.startDate.getTime()) / (1000 * 60 * 60 * 24))));

Suggested change

	return addDays(this.config.startDate, Math.floor(Math.random() * (this.config.endDate.getTime() - this.config.startDate.getTime()) / (1000 * 60 * 60 * 24)));
	return addDays(this.config.startDate, Math.floor(Math.random() * ((this.config.endDate.getTime() - this.config.startDate.getTime()) / (1000 * 60 * 60 * 24))));