search

MrPutzi / design-ai-toolkit

Design + AI Toolkit
https://design-plus-ai-toolkit.vercel.app/
1 stars 0 forks source link

Fix photo generation and loading issues #11

Closed codeautopilot[bot] closed 4 months ago

codeautopilot[bot] commented 4 months ago

Resolves #10

This PR addresses the bug where generated photos are not displayed on the screen. It includes updates to the API endpoint for rate-limiting, error handling, and secure API key usage. Additionally, the front-end components are enhanced to handle the photo URL and various image loading states.

vercel[bot] commented 4 months ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
design-ai-toolkit ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 26, 2024 5:22pm
gitguardian[bot] commented 4 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 | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [10088641](https://dashboard.gitguardian.com/incidents/10088641?occurrence=127755256) | Triggered | Replicate user access token | 0fbf71fc674078de95f35614c9072bde245bd3ac | pages/api/generate.ts | [View secret](https://github.com/MrPutzi/design-ai-toolkit/commit/0fbf71fc674078de95f35614c9072bde245bd3ac#diff-8ae3f4d93885962d659b1c0b05b36d8b0912dc957d9fc08cf1e4ceb5ba19785eL49) |
🛠 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/specifics/replicate_user_access_token#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.

Our GitHub checks need improvements? Share your feedbacks!