Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

internal/jsonrpc2: fix jsonrpc result no pending[id] blocking #155

Closed
wants to merge 2 commits into from

Conversation

a-wing
Copy link

@a-wing a-wing commented Sep 11, 2019

fix jsonrpc result no pending[id] always waits for a response

@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.


What to do if you already signed the CLA

Individual signers
Corporate signers

ℹ️ Googlers: Go here for more info.

@a-wing
Copy link
Author

a-wing commented Sep 11, 2019

@googlebot I signed it!

@googlebot
Copy link

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@gopherbot
Copy link
Contributor

This PR (HEAD: 87b3d0a) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/tools/+/194640 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
Within the next week or so, a maintainer will review your change and provide
feedback. See https://golang.org/doc/contribute.html#review for more info and
tips to get your patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.

During May-July and Nov-Jan the Go project is in a code freeze, during which
little code gets reviewed or merged. If a reviewer responds with a comment like
R=go1.11, it means that this CL will be reviewed as part of the next development
cycle. See https://golang.org/s/release for more details.


Please don’t reply on this GitHub thread. Visit golang.org/cl/194640.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Brad Fitzpatrick:

Patch Set 1:

Please add a test.


Please don’t reply on this GitHub thread. Visit golang.org/cl/194640.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Ian Cottrell:

Patch Set 1:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/194640.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from metal a-wing:

Patch Set 1:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/194640.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

This PR (HEAD: edbd8c9) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/tools/+/194640 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@gopherbot
Copy link
Contributor

Message from metal a-wing:

Patch Set 2:

Patch Set 1:

Please add a test.

Test added


Please don’t reply on this GitHub thread. Visit golang.org/cl/194640.
After addressing review feedback, remember to publish your drafts!

a-wing added a commit to sb-im/jsonrpc-lite that referenced this pull request Sep 17, 2019
@gopherbot
Copy link
Contributor

Message from Rebecca Stambler:

Patch Set 2: Run-TryBot+1

Ian, what do you think here?


Please don’t reply on this GitHub thread. Visit golang.org/cl/194640.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 2:

TryBots beginning. Status page: https://farmer.golang.org/try?commit=2925fb9a


Please don’t reply on this GitHub thread. Visit golang.org/cl/194640.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 2:

Build is still in progress...
This change failed on freebsd-amd64-12_0:
See https://storage.googleapis.com/go-build-log/97592b3c/freebsd-amd64-12_0_09a02495.log

Other builds still in progress; subsequent failure notices suppressed until final report. Consult https://build.golang.org/ to see whether they are new failures. Keep in mind that TryBots currently test exactly your git commit, without rebasing. If your commit's git parent is old, the failure might've already been fixed.


Please don’t reply on this GitHub thread. Visit golang.org/cl/194640.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 2: TryBot-Result-1

9 of 10 TryBots failed:
Failed on freebsd-amd64-12_0: https://storage.googleapis.com/go-build-log/97592b3c/freebsd-amd64-12_0_09a02495.log
Failed on linux-386: https://storage.googleapis.com/go-build-log/97592b3c/linux-386_a8de539d.log
Failed on linux-amd64 (Go 1.13.x): https://storage.googleapis.com/go-build-log/7ad8def9/linux-amd64_c1e6b312.log
Failed on linux-amd64: https://storage.googleapis.com/go-build-log/97592b3c/linux-amd64_56148861.log
Failed on windows-amd64-2016: https://storage.googleapis.com/go-build-log/97592b3c/windows-amd64-2016_b101dce7.log
Failed on openbsd-amd64-64: https://storage.googleapis.com/go-build-log/97592b3c/openbsd-amd64-64_86646ce6.log
Failed on linux-amd64-race: https://storage.googleapis.com/go-build-log/97592b3c/linux-amd64-race_b1ee31a6.log
Failed on windows-386-2008: https://storage.googleapis.com/go-build-log/97592b3c/windows-386-2008_c1b2ebaf.log
Failed on android-amd64-emu: https://storage.googleapis.com/go-build-log/97592b3c/android-amd64-emu_7761e0d4.log

Consult https://build.golang.org/ to see whether they are new failures. Keep in mind that TryBots currently test exactly your git commit, without rebasing. If your commit's git parent is old, the failure might've already been fixed.


Please don’t reply on this GitHub thread. Visit golang.org/cl/194640.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Rebecca Stambler:

Patch Set 3: Patch Set 2 was rebased


Please don’t reply on this GitHub thread. Visit golang.org/cl/194640.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Rebecca Stambler:

Patch Set 3: Run-TryBot+1


Please don’t reply on this GitHub thread. Visit golang.org/cl/194640.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 3:

TryBots beginning. Status page: https://farmer.golang.org/try?commit=68093fb3


Please don’t reply on this GitHub thread. Visit golang.org/cl/194640.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 3:

Build is still in progress...
This change failed on linux-amd64:
See https://storage.googleapis.com/go-build-log/ba0bab7b/linux-amd64_477344a6.log

Other builds still in progress; subsequent failure notices suppressed until final report. Consult https://build.golang.org/ to see whether they are new failures. Keep in mind that TryBots currently test exactly your git commit, without rebasing. If your commit's git parent is old, the failure might've already been fixed.


Please don’t reply on this GitHub thread. Visit golang.org/cl/194640.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 3: TryBot-Result-1

8 of 10 TryBots failed:
Failed on linux-amd64: https://storage.googleapis.com/go-build-log/ba0bab7b/linux-amd64_477344a6.log
Failed on linux-386: https://storage.googleapis.com/go-build-log/ba0bab7b/linux-386_109c3130.log
Failed on freebsd-amd64-12_0: https://storage.googleapis.com/go-build-log/ba0bab7b/freebsd-amd64-12_0_ab5c3f99.log
Failed on windows-amd64-2016: https://storage.googleapis.com/go-build-log/ba0bab7b/windows-amd64-2016_448d0fe0.log
Failed on windows-386-2008: https://storage.googleapis.com/go-build-log/ba0bab7b/windows-386-2008_ea465338.log
Failed on linux-amd64-race: https://storage.googleapis.com/go-build-log/ba0bab7b/linux-amd64-race_e77246d1.log
Failed on openbsd-amd64-64: https://storage.googleapis.com/go-build-log/ba0bab7b/openbsd-amd64-64_c388ba66.log
Failed on android-amd64-emu: https://storage.googleapis.com/go-build-log/ba0bab7b/android-amd64-emu_d3773ce4.log

Consult https://build.golang.org/ to see whether they are new failures. Keep in mind that TryBots currently test exactly your git commit, without rebasing. If your commit's git parent is old, the failure might've already been fixed.


Please don’t reply on this GitHub thread. Visit golang.org/cl/194640.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Rebecca Stambler:

Patch Set 3:

TryBot failures are unrelated - caused by golang/go#35226.


Please don’t reply on this GitHub thread. Visit golang.org/cl/194640.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Rebecca Stambler:

Patch Set 4: Patch Set 3 was rebased


Please don’t reply on this GitHub thread. Visit golang.org/cl/194640.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Rebecca Stambler:

Patch Set 4: Run-TryBot+1


Please don’t reply on this GitHub thread. Visit golang.org/cl/194640.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 4:

TryBots beginning. Status page: https://farmer.golang.org/try?commit=97388307


Please don’t reply on this GitHub thread. Visit golang.org/cl/194640.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 4: TryBot-Result+1

TryBots are happy.


Please don’t reply on this GitHub thread. Visit golang.org/cl/194640.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Ian Cottrell:

Patch Set 4:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/194640.
After addressing review feedback, remember to publish your drafts!

@maxhawkins
Copy link

I also ran into this bug.

If you cancel the context given to Call server-side and then the client sends a reply anyway it deadlocks the server.

@ianthehat

@maxhawkins
Copy link

I believe this issue is fixed by 88be013

@gopherbot
Copy link
Contributor

This PR is being closed because golang.org/cl/194640 has been abandoned.

See Ian's comment

@gopherbot gopherbot closed this Aug 8, 2020
bsponge added a commit to bsponge/tools that referenced this pull request Sep 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants