Fixing5902

[ChaitraTM]

Resolves #5919 .

Description

What is the purpose of this pull request?

This pull request:

• Refactored random number generation in the following benchmark files to use random/base/uniform instead of randu(), aligning with other packages and benchmarks.
• Updated test messages in stdlib/lib/node_modules/@stdlib/stats/base/dists/levy/median/test/test.native.js
• Changed test assertion messages from "returns NaN" to "returns expected value" to improve clarity and consistency with other tests.

Related Issues

Does this pull request have any related issues?

This pull request:

• resolves Address commit comments (commit b790b70) #5902

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

---

@stdlib-js/reviewers

[kgryte]

This shouldn't be here. You need to revisit your Git configuration.

[kgryte]

@ChaitraTM A few comments:

1. It is not clear which issue this PR is supposed to address. You mention two issues in your OP, one of which is a closed pull request.
2. Your Git configuration is off. You consistently commit a Git submodule which is not desired.
3. You need to spend more time studying project conventions. A number of your proposed changes do not match our conventions.

Based on the above, I'm going to go ahead and close this PR.

[stdlib-bot]

Thank you for working on this pull request. However, we cannot accept your contribution as this pull request does not follow project conventions.

We place a high value on consistency throughout the stdlib codebase, and this pull request was found to significantly deviate from stdlib conventions. We encourage you to closely examine other packages in stdlib and attempt to emulate the practices and conventions found therein.

• If you are attempting to contribute a new package, sometimes the best approach is to simply copy the contents of an existing package and then modify the minimum amount necessary to implement the feature (e.g., changing descriptions, parameter names, and implementation).
• If you are contributing tests, find a package implementing a similar feature and emulate the tests of that package.
• If you are updating documentation, examine several similar packages and emulate the content, style, and prose of those packages.

In short, the more effort you put in to ensure that your contribution looks and feels like stdlib—including variables names, bracket spacing, line breaks, etc—the more likely that your contribution will be reviewed and ultimately accepted. We encourage you to closely study the codebase before continuing to work on this pull request.

Thank you again for your interest in stdlib, and we look forward to reviewing your future contributions.