在Git 2.37 (Q3 2022)中，引入了一个新的bug()和BUG_if_bug() API，以便更容易地统一记录“检测多个错误并最终中止”模式。

这将是trace2输出的一部分，用于调试git-shell相关的问题。

参见 Ævar Arnfjörð Bjarmason （avar） 的提交 6d40f0a、提交 07b1d8f、提交 5b2f5d9、提交 53ca569、提交 0cc05b0、提交 19d7594（2022 年 6 月 2 日）。 （由 Junio C Hamano -- gitster -- 合并于 提交 4da14b5，2022 年 6 月 10 日）

usage.c:添加一个非致命的bug()函数来配合bug() 署名:Ævar Arnfjörð Bjarmason

Add a bug() function to use in cases where we'd like to indicate a runtime BUG(), but would like to defer the BUG() call because we're possibly accumulating more bug() callers to exhaustively indicate what went wrong. We already have this sort of facility in various parts of the codebase, just in the form of ad-hoc re-inventions of the functionality that this new API provides. E.g. this will be used to replace optbug() in parse-options.c, and the 'error("BUG:[...]' we do in a loop in builtin/receive-pack.c. Unlike the code this replaces we'll log to trace2 with this new bug() function (as with other usage.c functions, including BUG()), we'll also be able to avoid calls to xstrfmt() in some cases, as the bug() function itself accepts variadic sprintf()-like arguments. Any caller to bug() can follow up such calls with BUG_if_bug(), which will BUG() out (i.e. abort()) if there were any preceding calls to bug(), callers can also decide not to call BUG_if_bug() and leave the resulting BUG() invocation until exit() time. There are currently no bug() API users that don't call BUG_if_bug() themselves after a for-loop, but allowing for not calling BUG_if_bug() keeps the API flexible. As the tests and documentation here show we'll catch missing BUG_if_bug() invocations in our exit() wrapper.

技术/api错误处理现在包括在它的手册页:

的BUG、BUG、死亡、使用、错误和警告报告错误

技术/api错误处理现在包括在它的手册页:

bug (lower-case, not BUG) is supposed to be used like BUG but prints a "BUG" message instead of calling abort(). A call to bug() will then result in a "real" call to the BUG() function, either explicitly by invoking BUG_if_bug() after call(s) to bug(), or implicitly at exit() time where we'll check if we encountered any outstanding bug() invocations. If there were no prior calls to bug() before invoking BUG_if_bug() the latter is a NOOP. The BUG_if_bug() function takes the same arguments as BUG() itself. Calling BUG_if_bug() explicitly isn't necessary, but ensures that we die as soon as possible. If you know you had prior calls to bug() then calling BUG() itself is equivalent to calling BUG_if_bug(), the latter being a wrapper calling BUG() if we've set a flag indicating that we've called bug().

Technical /api-trace2现在在它的手册页中包括:

当BUG()、BUG()、error()、 调用Die()、warning()或usage()函数。

使用Git 2.38 (Q3 2022)，您甚至可以打印命令在运行时使用的配置值。

您是否尝试在克隆时添加详细(-v)操作符?

Git克隆-v Git://git.kernel.org/pub/scm/.../linux-2.6 my2.6

试试这个:

GIT_TRACE=1 git pull origin master

如果是SSH，你可以使用以下命令:

对于更高的调试级别，类型-vv或-vvv分别用于调试级别2和3:

# Debug level 1
GIT_SSH_COMMAND="ssh -v" git clone <repositoryurl>

# Debug level 2
GIT_SSH_COMMAND="ssh -vv" git clone <repositoryurl>

# Debug level 3
GIT_SSH_COMMAND="ssh -vvv" git clone <repositoryurl>

这主要用于处理服务器的公钥和私钥问题。 你可以将此命令用于任何git命令，而不仅仅是'git clone'。

要获得更详细的输出，请使用以下方法:

GIT_CURL_VERBOSE=1 GIT_TRACE=1 git拉源主

Git 2.39 (Q4 2022)增加了两个新的跟踪功能，“计时器”和“计数器”:

参见Jeff Hostetler (Jeff-Hostetler)的commit 8107162, commit 8ad5756, commit 24a4c45, commit 3124793, commit a70839c, commit 8e8c5ad, commit 5bbb925, commit 545ddca(2022年10月24日)。 (由Taylor Blau—Taylor—在commit e5be3c6中合并，2022年10月30日)

Trace2:添加秒表计时器 署名:Jeff Hostetler

Timers are an alternative to Trace2 Regions. Regions are useful for measuring the time spent in various computation phases, such as the time to read the index, time to scan for unstaged files, time to scan for untracked files, and etc. However, regions are not appropriate in all places. For example, during a checkout, it would be very inefficient to use regions to measure the total time spent inflating objects from the ODB (Object DataBase) from across the entire lifetime of the process; a per-unzip() region would flood the output and significantly slow the command; and some form of post-processing would be required to compute the time spent in unzip(). Timers can be used to measure a series of timer intervals and emit a single summary event (at thread and/or process exit).

Technical /api-trace2现在在它的手册页中包括:

"th_timer" This event logs the amount of time that a stopwatch timer was running in the thread. This event is generated when a thread exits for timers that requested per-thread events. { "event":"th_timer", ... "category":"my_category", "name":"my_timer", "intervals":5, # number of time it was started/stopped "t_total":0.052741, # total time in seconds it was running "t_min":0.010061, # shortest interval "t_max":0.011648 # longest interval } "timer" This event logs the amount of time that a stopwatch timer was running aggregated across all threads. This event is generated when the process exits. { "event":"timer", ... "category":"my_category", "name":"my_timer", "intervals":5, # number of time it was started/stopped "t_total":0.052741, # total time in seconds it was running "t_min":0.010061, # shortest interval "t_max":0.011648 # longest interval }

Technical /api-trace2现在在它的手册页中包括:

Stopwatch Timer Events Measure the time spent in a function call or span of code that might be called from many places within the code throughout the life of the process. static void expensive_function(void) { trace2_timer_start(TRACE2_TIMER_ID_TEST1); ... sleep_millisec(1000); // Do something expensive ... trace2_timer_stop(TRACE2_TIMER_ID_TEST1); } static int ut_100timer(int argc, const char **argv) { ... expensive_function(); // Do something else 1... expensive_function(); // Do something else 2... expensive_function(); return 0; } In this example, we measure the total time spent in expensive_function() regardless of when it is called in the overall flow of the program. $ export GIT_TRACE2_PERF_BRIEF=1 $ export GIT_TRACE2_PERF=~/log.perf $ t/helper/test-tool trace2 100timer 3 1000 ... $ cat ~/log.perf d0 | main | version | | | | | ... d0 | main | start | | 0.001453 | | | t/helper/test-tool trace2 100timer 3 1000 d0 | main | cmd_name | | | | | trace2 (trace2) d0 | main | exit | | 3.003667 | | | code:0 d0 | main | timer | | | | test | name:test1 intervals:3 total:3.001686 min:1.000254 max:1.000929 d0 | main | atexit | | 3.003796 | | | code:0

并且，仍然使用Git 2.39:

Trace2:添加全局计数器机制 署名:Jeff Hostetler

Add global counters mechanism to Trace2. The Trace2 counters mechanism adds the ability to create a set of global counter variables and an API to increment them efficiently. Counters can optionally report per-thread usage in addition to the sum across all threads. Counter events are emitted to the Trace2 logs when a thread exits and at process exit. Counters are an alternative to data and data_json events. Counters are useful when you want to measure something across the life of the process, when you don't want per-measurement events for performance reasons, when the data does not fit conveniently within a region, or when your control flow does not easily let you write the final total. For example, you might use this to report the number of calls to unzip() or the number of de-delta steps during a checkout.

Technical /api-trace2现在在它的手册页中包括:

"th_counter" This event logs the value of a counter variable in a thread. This event is generated when a thread exits for counters that requested per-thread events. { "event":"th_counter", ... "category":"my_category", "name":"my_counter", "count":23 } "counter" This event logs the value of a counter variable across all threads. This event is generated when the process exits. The total value reported here is the sum across all threads. { "event":"counter", ... "category":"my_category", "name":"my_counter", "count":23 }