The java implementation of Apache Dubbo. An RPC and microservice framework.
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 25%
Response Time: <1h
First Timer Success: 20%
apache/dubbo has a recorded first-timer success rate of 20.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in apache/dubbo respond to incoming external pull requests in approximately 0.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 56.6 places apache/dubbo in the A tier.
The external contributor pull request merge rate for apache/dubbo is 25.3%, based on public PR activity from non-core contributors.
apache/dubbo currently has 23 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (66% critical review signals). Ensure PRs strictly follow guidelines before requesting review in apache/dubbo.
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?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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (32% approval). Large PRs (>500 lines) take ~2 hours (15% approval). Keep your diff compact for rapid review.
Pre-check I am sure that all the content I provide is in English. Search before asking I had searched in the issues and found no similar issues. Apache Dubbo Component Java SDK (apache/dubbo) Dubbo Version dubbo-rpc-triple:3.3.6 Netty:4.2.9 use direct memory jdk:17.0.17 windowns Steps to reproduce this issue @DubboReference( version = "1.0.0", url = "tri://${dubbo.directUrl}", protocol = "tri", check = false, timeout = 100, // Set a shorter timeout to simulate a rpc timeout connections = 5, actives = 5 ) public void setTripleService(TripleExternalService tripleService) { this.tripleService = tripleService; } note : add jvm property -Dio.netty.leakDetectionLevel=PARANOID If you keep calling a certain method of this interface for a while, it will appear, and the smaller the timeout, the easier it is to reproduce. output： io.netty.buffer.AdvancedLeakAwareByteBuf.readByte(AdvancedLeakAwareByteBuf.java:401) io.netty.handler.codec.http2.DefaultHttp2FrameReader.preProcessFrame(Defa
Pre-check I am sure that all the content I provide is in English. Search before asking I had searched in the issues and found no similar issues. Apache Dubbo Component Java SDK (apache/dubbo) Dubbo Version Apache Dubbo：3.3.6 JDK：17 Steps to reproduce this issue Start a Triple provider in one JVM with a client-streaming RPC: rpc Upload(stream UploadFrame) returns (UploadResult); Start a new consumer JVM and immediately invoke Upload: send the metadata frame first, then send one or more file-content frames. The first call after the consumer restart may fail. Subsequent calls usually succeed without restarting either side. The issue is reproducible with both: a single Dubbo port with ext-protocol: tri native tri protocol The payload can be very small (for example, 16 KB); it is not dependent on a large gRPC frame. Actual result The consumer receives: org.apache.dubbo.rpc.StatusRpcException: UNKNOWN : gRPC frame header malformed: reserved bits not zero at org.ap
Pre-check I am sure that all the content I provide is in English. Search before asking I had searched in the issues and found no similar issues. Apache Dubbo Component Java SDK (apache/dubbo) Dubbo Version Dubbo: 3.3.7-SNAPSHOT Branch: 3.3 Commit: 3a30432 JDK: Eclipse Temurin 17.0.17 Operating system: Windows 11 x86_64 Netty: 4.2.15.Final Steps to reproduce this issue Add the following test to the existing RestProtocolTest.groovy: import org.apache.dubbo.remoting.http12.HttpUtils import io.netty.handler.codec.http.multipart.DefaultHttpDataFactory def "completed form request should release post data"() { given: HttpUtils.DATA_FACTORY.cleanAllHttpData() def request = new TestRequest( path: '/argTest', contentType: MediaType.APPLICATION_FROM_URLENCODED, body: 'name=Sam&age=8' ) expect: runner.post(request) == 'Sam is 8 years old' trackedPostRequests() == 0 cleanup: HttpUtils.DATA_FACTOR
Pre-check I am sure that all the content I provide is in English. Search before asking I had searched in the issues and found no similar issues. Apache Dubbo Component Java SDK (apache/dubbo) Dubbo Version Dubbo 3.3.6, Triple protocol (dubbo.protocol.name=tri), instance mode , JDK 8. Steps to reproduce this issue Graceful shutdown tears down the Triple PathResolver mapping before in-flight requests have drained. A request that has already been accepted by the server, but has not yet resolved its invoker, will fail with UNIMPLEMENTED once afterUnExport runs. The race can be reproduced deterministically with two breakpoints on the provider side — no timing luck required. Use a thread-level (suspend-thread, not suspend-all) breakpoint so the shutdown thread and the request thread can be released independently. Provider service (anything works, the body is irrelevant): @DubboService public class DemoServiceImpl implements DemoService { @Override public String sayHello(Strin
Pre-check I am sure that all the content I provide is in English. Search before asking I had searched in the issues and found no similar issues. Apache Dubbo Component Java SDK (apache/dubbo) Dubbo Version Dubbo: 3.2.19 in production, reproduced against apache/3.3 HEAD Registry: Nacos 2.x (gRPC client, application-level discovery) Discovery mode: APPLICATION_FIRST Steps to reproduce this issue The bug is deterministic and can be reproduced without a Nacos server, using only a failing unit test that captures the race. Clone apache/dubbo at the 3.3 branch: git clone https://github.com/apache/dubbo.git cd dubbo git checkout 3.3 Add my fork as a remote and fetch the branch: git remote add hnpkso https://github.com/hnpkso/dubbo.git git fetch hnpkso fix/subscribe-push-loss Check out just the test commit (source stays as unmodified 3.3): git checkout f9755db2 Run the tests: mvn -pl dubbo-registry/dubbo-registry-api test \ -Dtest=ServiceDiscoveryRegistryTest Observe 3
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, 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 acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 25.3% were successfully merged into the primary branch.
apache/dubbo has a recorded first-timer success rate of 20.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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 56.6 places apache/dubbo in the Welcoming tier.
The external pull request merge rate is 25.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, apache/dubbo currently has 23 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for apache/dubbo 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.