bazelbuild/bazel

Decorate profile spans with Workspace Events

Open

#22,086 opened on Apr 23, 2024

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Java (4,465 forks)batch import
P2help wantedteam-ExternalDepstype: feature request

Repository metrics

Stars
 (25,384 stars)
PR merge metrics
 (Avg merge 22d 20h) (77 merged PRs in 30d)

Description

Description of the feature request:

It would improve the user experience by quite a bit if the repository rules's profile spans are decorated with the same content currently printed to experimental_workspace_rules_log_file.

The log file by itself is not that interesting because the timing (start, finish, duration) is not included with the events.

Which category does this issue belong to?

External Dependency

What underlying problem are you trying to solve with this feature?

Improve repository rule troubleshooting experience.

Which operating system are you running Bazel on?

No response

What is the output of bazel info release?

No response

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse HEAD ?

No response

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response

Contributor guide

Research direction
Investigate how Bazel's profile tracing currently handles repository rule spans and workspace events. Look at the code around `experimental workspace rules log file` and the profile output to understand how to add workspace events to profile spans.
Tech stack
java
Domain
backendbuild systemdevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
BazelRepository rulesProfiling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30