-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add regtest entrypoint to mine blocks #6
Conversation
…pose test Co-Authored-By: Nico Krause <[email protected]>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
⚙️ Control Options:
|
…re tests Co-Authored-By: Nico Krause <[email protected]>
Co-Authored-By: Nico Krause <[email protected]>
Co-Authored-By: Nico Krause <[email protected]>
… sync timing Co-Authored-By: Nico Krause <[email protected]>
Co-Authored-By: Nico Krause <[email protected]>
Co-Authored-By: Nico Krause <[email protected]>
- Add Silk Road city nameOps creation in test setup - Enhance relay connectivity checks with retries - Add document structure validation - Improve error handling and logging - Add exponential backoff for DB sync Co-Authored-By: Nico Krause <[email protected]>
Co-Authored-By: Nico Krause <[email protected]>
Devin is currently unreachable - the session may have died. |
- Add service dependencies and readiness checks in docker-compose - Enhance regtest container with continuous block mining and error handling - Remove duplicate nameOp creation from tests and add proper waiting - Add comprehensive logging for better debugging Co-Authored-By: Nico Krause <[email protected]>
Co-Authored-By: Nico Krause <[email protected]>
Co-Authored-By: Nico Krause <[email protected]>
Co-Authored-By: Nico Krause <[email protected]>
- Add OrbitDB initialization retries and readiness checks - Enhance service readiness verification in entrypoint.sh - Add HTTP server initialization retries - Fix libp2p connectivity configuration - Add proper port configuration Co-Authored-By: Nico Krause <[email protected]>
- Add proper health checks for relay service - Fix double service start in entrypoint.sh - Improve doichaind readiness check - Add proper service dependency order Co-Authored-By: Nico Krause <[email protected]>
… service to use container DNS names - Fix test node connectivity with proper container addressing - Add proper health checks for libp2p port Co-Authored-By: Nico Krause <[email protected]>
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
14955053 | Triggered | Generic High Entropy Secret | 2a0b0cb | docker-compose-test.yml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. 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 for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit 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.
Co-Authored-By: Nico Krause <[email protected]>
- Update GitHub Actions workflow to use TEST_RELAY_PRIVATE_KEY secret - Enhance entrypoint.sh service readiness checks - Remove hardcoded private key references Co-Authored-By: Nico Krause <[email protected]>
Closing due to inactivity. |
This PR implements automated address generation and block mining for the regtest container. Fixes #5. Link to Devin run