Skip to content

fix: different response when blockbook is not responding #4967

fix: different response when blockbook is not responding

fix: different response when blockbook is not responding #4967

Triggered via push December 6, 2024 17:25
Status Success
Total duration 6m 7s
Artifacts

build.yml

on: push
checkout-and-build
5m 59s
checkout-and-build
Fit to window
Zoom out
Zoom in

Annotations

1 warning
SonarScanner
This action is deprecated and will be removed in a future release. Please use the sonarqube-scan-action action instead. The sonarqube-scan-action is a drop-in replacement for this action.