bazelbuild / bazelbuild/bazelisk

Add debug logging

Open
#744 2 comments 1 reaction 0 assignees View on GitHub
P2 type: feature request
Dominant language
Go
Stars
2.7k
Forks
424
PR merge metrics
No merged PRs in 30d

Description

https://github.com/bazelbuild/bazelisk/issues/743 is a recent example of when I needed to examine GCS requests, which usually means adding lots of print statements.

We should add debug logging via https://github.com/golang/glog so that similar problems can be debugged easier.

Contributor guide

Open the contributing guide

Research direction

Start by inspecting the Bazelisk code path that makes GCS requests and review the golang/glog integration described in the issue. Done means debug logging makes these requests easier to examine without adding print statements; the issue names no specific files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.