GitLabgitlab-org

cli

main
ply5 git calls30 ms96 KiB4 cachedprotocol v2
48 lines2.1 KiBRaw

Create a bug in the glab project

Any contributor can raise bugs against the glab CLI project. Use the appropriate issue template for your bug:

Add labels to your bug

The issue templates help set the correct labels for your bug. Add any of these labels that are also appropriate to your bug:

  • ~"bug::performance": For bugs about the response time of glab.
  • ~UX: For user experience problems.

Triage your bug

Use this guide to assign a severity label to your bug. A severity label helps the glab CLI project team prioritize fixes. This project uses the same severity guidelines as the wider GitLab organization. Use these glab-specific examples to help you assess the problem:

  • ~"severity::1": Blocker. A security vulnerability that requires an immediate fix.
  • ~"severity::2": Critical.
    • All glab commands fail, even when the target GitLab instance is working as expected.
    • A security vulnerability with a fix needed for next release.
  • ~"severity::3": Major.
    • A command fails with no workaround.
    • A command fails with an unexpected error.
    • The command output is incorrect.
    • The documentation is inaccurate.
  • ~"severity::4": Low.
    • A cosmetic bug.
    • The command output could be improved.
    • The command fails, but a suitable workaround exists.
    • A documentation improvement.

For full details, see Severity in the GitLab engineering handbook.

1---
2stage: AI Clients
3group: Developer Clients
4info: To determine the technical writer assigned to the Stage/Group associated with this page, see <https://handbook.gitlab.com/handbook/marketing/product-and-technical-marketing/technical-writing/#assignments>
5---
7# Create a bug in the glab project
9Any contributor can raise bugs against the `glab` CLI project. Use the appropriate
10issue template for your bug:
12- For potential security vulnerabilities, create an issue
13 [with the **Vulnerability Disclosure** template](https://gitlab.com/gitlab-org/cli/-/issues/new?issuable_template=Vulnerability%20Disclosure). This template creates a confidential issue.
14- For all other bugs, create an issue [with the **Bug** template](https://gitlab.com/gitlab-org/cli/-/issues/new?issuable_template=Bug).
16## Add labels to your bug
18The issue templates help set the correct labels for your bug. Add any of these
19labels that are also appropriate to your bug:
21- `~"bug::performance"`: For bugs about the response time of `glab`.
22- `~UX`: For user experience problems.
24## Triage your bug
26Use this guide to assign a severity label to your bug. A severity label helps the
27`glab` CLI project team prioritize fixes. This project uses the same severity
28guidelines as the wider GitLab organization. Use these `glab`-specific examples
29to help you assess the problem:
31- `~"severity::1"`: Blocker. A security vulnerability that requires an immediate fix.
32- `~"severity::2"`: Critical.
33 - All `glab` commands fail, even when the target GitLab instance is working as expected.
34 - A security vulnerability with a fix needed for next release.
35- `~"severity::3"`: Major.
36 - A command fails with no workaround.
37 - A command fails with an unexpected error.
38 - The command output is incorrect.
39 - The documentation is inaccurate.
40- `~"severity::4"`: Low.
41 - A cosmetic bug.
42 - The command output could be improved.
43 - The command fails, but a suitable workaround exists.
44 - A documentation improvement.
46For full details, see
47[Severity](https://handbook.gitlab.com/handbook/product-development/how-we-work/issue-triage/#severity)
48in the GitLab engineering handbook.
Diagnostics5 git calls · 30 ms
CallStatusSizeTime030 ms
discover200185 B3 ms
git.upload-pack discover
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=2
git.response.bytes=185
git.server.agent=git/2.56.g1891de4-Linux
git.server.object_format=sha1
git.server.caps=agent ls-refs fetch server-option object-format
git.server.fetch=shallow wait-for-done filter
git.protocol.version=2
git.pkt.frames=9
git.pkt.data=7
git.pkt.flush=2
git.pkt.delim=0
git.pkt.bytes=185
git.pkt.payload.max=35
ls-refs20058 KiB · hit2 ms
git.upload-pack ls-refs
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=2
git.response.bytes=59849
git.response.cache=HIT
git.response.duration_ms=2
git.protocol.version=2
git.pkt.frames=731
git.pkt.data=730
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=59849
git.pkt.payload.max=143
git.ls_refs.count=730
git.ls_refs.head=refs/heads/main
fetchtree:0 · deepen 1020032 KiB · hit2 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=3
git.response.bytes=32926
git.response.cache=HIT
git.response.duration_ms=2
git.fetch.filter=tree:0
git.fetch.wants=0dd7574dce9e385c5c30540e6c15657adc6bdce9
git.fetch.haves.count=0
git.fetch.deepen=10
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=22
git.pkt.data=20
git.pkt.flush=1
git.pkt.delim=1
git.pkt.bytes=32926
git.pkt.payload.max=32046
git.sideband.band1.bytes=32046
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0
git.pack.objects=80
git.pack.bytes=32046
git.pack.ofs_delta=36
git.pack.ref_delta=0
git.pack.chain.max=2
git.pack.trailer=cb0bad5d7ffc514895d8b21c4dd470327f90bc91
git.pack.full=44
Open pack map
fetchcombine:blob:none+tree:2 · deepen 12004.2 KiB · hit3 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=24
git.response.bytes=4273
git.response.cache=HIT
git.response.duration_ms=3
git.fetch.filter=combine:blob:none+tree:2
git.fetch.wants=0dd7574dce9e385c5c30540e6c15657adc6bdce9
git.fetch.haves.count=0
git.fetch.deepen=1
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=7
git.pkt.data=5
git.pkt.flush=1
git.pkt.delim=1
git.pkt.bytes=4273
git.pkt.payload.max=4173
git.sideband.band1.bytes=4173
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0
git.pack.objects=11
git.pack.bytes=4173
git.fetch.wide.objects=11
git.fetch.wide.extra_bytes=3930
git.fetch.wide.blobs=0
fetch2001.0 KiB · hit24 ms
git.upload-pack fetch
http.response.status_code=200
git.response.bytes=1026
git.response.cache=HIT
git.response.duration_ms=24
git.fetch.wants=a9d107d479488f739d66e77e87736becba7ddc04
git.fetch.haves.count=0
git.fetch.deepen=0
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=4
git.pkt.data=3
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=1026
git.pkt.payload.max=999
git.sideband.band1.bytes=999
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0

Each row is one HTTP round trip ply made to the git server for this page, on one timeline. discover asks what the server speaks, ls-refs lists branch tips, fetch brings objects by id. A hit was served by Workers Cache. Tap a row for its wire details.

Remote
https://gitlab.com/gitlab-org/cli
Ref
refs/heads/main
Commit
0dd7574dce9e385c5c30540e6c15657adc6bdce9
cf-ray
a5e1277059607fd8
Request
3018b0f6…
Protocol
v2 · sha1
Agent
git/2.56.g1891de4-Linux
Filter
advertised
Fetch
shallow wait-for-done filter
Capabilities
agent ls-refs fetch server-option object-format