Add debug output to certificate viewing and fix stage script permissions
Some checks failed
Cross-Node Transaction Testing / transaction-test (push) Has been cancelled
Deploy to Testnet / deploy-testnet (push) Has been cancelled
Multi-Node Stress Testing / stress-test (push) Has been cancelled
Node Failover Simulation / failover-test (push) Has been cancelled
Some checks failed
Cross-Node Transaction Testing / transaction-test (push) Has been cancelled
Deploy to Testnet / deploy-testnet (push) Has been cancelled
Multi-Node Stress Testing / stress-test (push) Has been cancelled
Node Failover Simulation / failover-test (push) Has been cancelled
- Add debug output in view_certificates() to show certificate directory path - Display count of found certificate files - Show directory contents when no certificates found for troubleshooting - Make stage6_agent_development.sh executable - Make stage7_cross_node_training.sh executable
This commit is contained in:
@@ -360,6 +360,9 @@ view_certificates() {
|
||||
# Ensure directory exists
|
||||
mkdir -p "$CERT_DIR"
|
||||
|
||||
# Debug: Show CERT_DIR
|
||||
echo "Certificate directory: $CERT_DIR"
|
||||
|
||||
# Check for certificates
|
||||
local cert_files=()
|
||||
for cert_file in "$CERT_DIR"/stage*_certificate.json; do
|
||||
@@ -368,9 +371,13 @@ view_certificates() {
|
||||
fi
|
||||
done
|
||||
|
||||
echo "Found ${#cert_files[@]} certificate file(s)"
|
||||
|
||||
if [ ${#cert_files[@]} -eq 0 ]; then
|
||||
print_warning "No certificates found yet"
|
||||
echo "Complete stages to earn certificates"
|
||||
echo "Directory contents:"
|
||||
ls -la "$CERT_DIR" 2>/dev/null || echo "Directory not accessible"
|
||||
return 0
|
||||
fi
|
||||
|
||||
|
||||
0
scripts/training/stage6_agent_development.sh
Normal file → Executable file
0
scripts/training/stage6_agent_development.sh
Normal file → Executable file
0
scripts/training/stage7_cross_node_training.sh
Normal file → Executable file
0
scripts/training/stage7_cross_node_training.sh
Normal file → Executable file
Reference in New Issue
Block a user