cockroachdb
cli/debug: narrow scope of --include-goroutine-stacks to just debug=2
It looks like your PR touches production code but doesn't add or edit any test code. Did you consider adding tests to your PR?
:owl: Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.
![blathers-crl[bot] avatar](https://avatars.githubusercontent.com/in/59700?v=4 "Published by a pub.dev verified publisher"){kind=small}
debug 3
Not yet: adding that is what had me in the neighborhood to notice this, but wanted to fix this one standalone in case it wants a backport later
@dhartunian How do you feel about backports to released branches in the interest of improving supportability (making --include-goroutine-stacks=false less costly in terms of debugging information lost and thus more viable as a latency-impact-reduction tool)?
Build succeeded:
- local_roachtest
- docker_image_amd64
- unit_tests
- linux_amd64_fips_build
- local_roachtest_fips
- examples_orms
- linux_amd64_build
- acceptance
- check_generated_code
- lint
![craig[bot] avatar](https://avatars.githubusercontent.com/in/10419?v=4 "Published by a pub.dev verified publisher"){kind=small}
Encountered an error creating backports. Some common things that can go wrong:
- The backport branch might have already existed.
- There was a merge conflict.
- The backport branch contained merge commits.
You might need to create your backport manually using the backport tool.
error creating backport branch refs/heads/blathers/backport-release-26.1-159253: POST https://api.github.com/repos/dt/cockroach/git/refs: 403 Resource not accessible by integration []
Backport to branch 26.1.x failed. See errors above.
:owl: Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.