Skip to content
#

trace

Here are 428 public repositories matching this topic...

基于 Gin 进行模块化设计的 API 框架,封装了常用功能,使用简单,致力于进行快速的业务研发。比如,支持 cors 跨域、jwt 签名验证、zap 日志收集、panic 异常捕获、trace 链路追踪、prometheus 监控指标、swagger 文档生成、viper 配置文件解析、gorm 数据库组件、gormgen 代码生成工具、graphql 查询语言、errno 统一定义错误码、gRPC 的使用 等等。

  • Updated Jul 10, 2021
  • Go
honggyukim
honggyukim commented Mar 17, 2021

We can reproduce the memory leak problem as follows.

$ make clean
$ make ASAN=1

$ ./uftrace record -L. --force uptime
 19:40:08 up 13 days,  1:55,  2 users,  load average: 3.61, 1.21, 0.43

=================================================================
==1188721==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 888 byte(s) in 1 object(s) allocated from:
    #0 0xffff
plajjan
plajjan commented Jul 2, 2021

It seems to me that UTC is selected for on the wire representation of time as well as in the database (jaegertracing/jaeger#712), which sort of makes sense, at least with a somewhat naive handling of timezones. However, I think that the Jaeger UI should support displaying times in the timezone local to the user, i.e. of the browser as to reduce the mental load when viewing

Improve this page

Add a description, image, and links to the trace topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the trace topic, visit your repo's landing page and select "manage topics."

Learn more