Go Implementation For Apache Dubbo .
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 58%
Response Time: 17h
First Timer Success: 69%
apache/dubbo-go has a recorded first-timer success rate of 68.8%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in apache/dubbo-go respond to incoming external pull requests in approximately 17.5 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 59.9 places apache/dubbo-go in the A tier.
The external contributor pull request merge rate for apache/dubbo-go is 58.5%, based on public PR activity from non-core contributors.
apache/dubbo-go currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in apache/dubbo-go. Prompt code reviews with positive guidance for new contributors.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/apache/dubbo-go?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~11 hours (73% approval). Large PRs (>500 lines) take ~84 hours (26% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Go.
A multi-hypervisor VM runtime for OCI images, supporting Cloud Hypervisor, Firecracker, QEMU, and Apple Virtualization.framework.
The AWS Provider enables Terraform to manage AWS resources.
LLM Swiss Army Knife for your Terminal
What happened? https://github.com/apache/dubbo-go/actions/runs/32698171775/job/97344210257 2026-08-24T06:47:10.018Z WARN accesslog/filter.go:331 [Filter][AccessLog] can not open the access log file, accessLog=/tmp/TestGetOrOpenLogFileClosesCachedFileOnOpenError3476862592/001/access.log err=open /tmp/TestGetOrOpenLogFileClosesCachedFileOnOpenError3476862592/001/access.log: is a directory 2026-08-24T06:47:10.018Z WARN accesslog/filter.go:130 [Filter][AccessLog] the channel is full and the access logIntoChannel data will be dropped --- FAIL: TestAccessLogFilterGoroutineShutdown (0.20s) memory_leak_test.go:64: Error Trace: /home/runner/work/dubbo-go/dubbo-go/filter/accesslog/memory_leak_test.go:64 Error: "3" is not greater than "3" Test: TestAccessLogFilterGoroutineShutdown FAIL coverage: 83.8% of statements FAIL dubbo.apache.org/dubbo-go/v3/filter/accesslog 0.363s How can we reproduce it? (optional) No response Environment No response
背景 dubbo-go 当前依赖图中仍有多项较旧版本，部分来自 gost 的 go.mod，部分直接存在于 dubbo-go/go.mod。需要做一次有边界的依赖升级，优先处理官方 SDK、旧版本和安全/兼容性风险。 本 issue 只处理依赖更新和回归验证，不负责把 API 迁移到标准库。 升级清单 以下版本以 issue 创建时的依赖检查结果为基线，最终版本应通过 go list -m -u 和兼容性验证确认。 重点依赖 当前 建议 go.etcd.io/etcd/api/v3 v3.5.7 与 client/v3 一起升级到稳定且兼容的版本 go.etcd.io/etcd/client/v3 v3.5.7 优先评估 v3.5.x/v3.6.x，随后评估 v3.7.x；保持 api/client 版本一致 github.com/nacos-group/nacos-sdk-go/v2 v2.2.5 升级到当前 v2.3.x 稳定版本 go.yaml.in/yaml/v4 v4.0.0-rc.6 跟进 v4 稳定版本；同时清理不必要的 gopkg.in/yaml.v2 间接依赖 go.uber.org/zap v1.21.0 升级到当前 v1.28.x github.com/sirupsen/logrus v1.9.4 升级到当前
背景 这批任务面向 OSPP 新人，目标是通过小 PR 补齐 Dubbo-Go 中面向用户的导出注释，并补充对应模块的单测覆盖。 需要在评论区里面评论【认领 + 任务序号】 未认领的 PR 不予接受 AI 生成的 PR 不予接受 对 OSPP 感兴趣的同学一定要通过 README 里面的方式加群沟通 please note that a complete AI PR is not welcome. 目标仓库： dubbo-go https://github.com/apache/dubbo-go 提交 PR 的时候 @Alanxtl，我到时候会去看。 任务总览 序号 任务名称 负责人 任务链接 1 补齐 Metrics Options / Error Classifier 注释与单测覆盖 @tangerineyu #3665 2 补齐 Metrics Probe 注释与单测覆盖 待认领 查看任务 3 补齐 Registry Options 注释与单测覆盖 @641-git641 #3653 4 补齐 Service Discovery Metadata Customizer 注释与单测覆盖 待认领 查看任务 5 补齐 Service Discovery Instance Customizer 注释与单测覆盖 待认领 查看任务 6 补齐 Meta
Problem Dubbo-go already supports passing request attachments through context.WithValue(ctx, constant.AttachmentKey, ...). The dubbo-go-samples/context sample covers this direction: consumer request attachment -> provider ctx.Value(constant.AttachmentKey) -> business response body However, this does not cover the opposite direction: provider result attachments -> Triple response trailers -> consumer reads response attachments For Triple unary calls, provider-side result attachments can be propagated as response trailers. The missing piece is that generic invocations do not currently expose a consumer-side API for reading those response trailers. Current limitation filter/generic.GenericService currently defines Invoke as a function field without per-call options: type GenericService struct { Invoke func(ctx context.Context, methodName string, types []string, args []hessian.Object) (any, error) `dubbo:"$invoke"` } The normal Triple generated unary client path can capture response
背景 dubbo-go 现在已经有一套自适应限流能力，主要包括： provider 侧的 filter/adaptivesvc consumer 侧的 cluster/adaptivesvc p2c load balance consumer 本地 metrics Hill Climbing 自适应并发控制算法 这套能力可以在 provider 侧根据实时请求情况动态调整并发上限，同时让 consumer 根据 provider 返回的剩余容量选择更合适的节点。 下一步我们希望对这块能力做一次系统梳理，并考虑把它迁移到 dubbo-go-extensions，让 dubbo-go 主仓库更加轻量。 要做的事情 检查 dubbo-go 当前自适应限流能力 需要先梳理当前已有能力，包括： provider 侧自适应限流 filter method 级别 limiter Hill Climbing 算法 consumer 侧 adaptiveService cluster P2C 如何使用 provider 返回的 remaining 信息 当前配置入口和使用方式 已知限制和潜在问题 做压力测试，看看能力上限 需要补一组压测，验证当前实现的实际效果，比如： 高
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to apache/dubbo-go, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of apache/dubbo-go acknowledge new external contributions in approximately 17 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 58.5% were successfully merged into the primary branch.
apache/dubbo-go has a recorded first-timer success rate of 68.8%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~17 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 59.9 places apache/dubbo-go in the Welcoming tier.
The external pull request merge rate is 58.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, apache/dubbo-go currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for apache/dubbo-go are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.