Skip to content

fix: different response when blockbook is not responding #4961

fix: different response when blockbook is not responding

fix: different response when blockbook is not responding #4961

Triggered via push December 6, 2024 15:28
Status Success
Total duration 8m 19s
Artifacts

build.yml

on: push
checkout-and-build
8m 11s
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.