ionq-samples / Ion-Q-Thruster

UnitaryHACK2024 Challenge to create custom optimizer/transpiler for Qiskit to Native Gates.
MIT License
2 stars 4 forks source link

[Unitary Hack] Fix issue #2 #8

Closed huyenemma closed 3 months ago

huyenemma commented 3 months ago

3

Writing 4 transformation passes (rules written in Rewrite_templates.md) to reduce the depth and size of the circuit. All rules are based on the matrix multiplication of GPi, GPi2, and XX gates.

These passes can be plugged into the custom transpiler (when available). Currently, they optimize the IBM transpiled circuit.

gitguardian[bot] commented 3 months ago

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [-](https://dashboard.gitguardian.com/workspace/208229/incidents/secrets) | | Generic High Entropy Secret | 38daa6e06f782867c48c95da32525cdf42423fc3 | example.ipynb | [View secret](https://github.com/ionq-samples/Ion-Q-Thruster/commit/38daa6e06f782867c48c95da32525cdf42423fc3#diff-4dec3625bbb8a07a4757386fbc7ecd0a5289fa0008cd2f991f8d8d77ada92b6dR33) |
🛠 Guidelines to remediate hardcoded secrets
1. Understand the implications of revoking this secret by investigating where it is used in your code. 2. Replace and store your secret safely. [Learn here](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate this secret](https://docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/generics/generic_high_entropy_secret#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data. To avoid such incidents in the future consider - following these [best practices](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) to catch secret before it leaves your machine and ease remediation.

🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.