assertion failed: !absl::exchange(g_registered, true) #30640
Assignees
Labels
Comments
|
Thanks for reporting! I'm glad to see our prereleases are catching issues! |
|
Thanks for pointing this out! I'll have a fix for this shortly, and we'll put out an rc2 release afterwards. |
drfloob
added a commit
that referenced
this issue
Aug 19, 2022
This fixes a bug that could occur on repeated grpc initialization (after a complete shutdown) Fixes #30640
drfloob
added a commit
to drfloob/grpc
that referenced
this issue
Aug 19, 2022
This fixes a bug that could occur on repeated grpc initialization (after a complete shutdown) Fixes grpc#30640
This was referenced Aug 19, 2022
Merged
drfloob
added a commit
that referenced
this issue
Aug 19, 2022
This was referenced Aug 22, 2022
docs(samples): Add prebuilt telecom agent webhook code in python
googleapis/python-dialogflow-cx#434
Merged
Merged
Merged
This was referenced Aug 23, 2022
This was referenced Aug 23, 2022
gcf-merge-on-green bot
pushed a commit
to googleapis/python-storage
that referenced
this issue
Aug 23, 2022
Unblock ci/cd by excluding pre-release version in question `1.49.0rc1` Update: grpc/grpc#30642 fixes issue grpc/grpc#30651 and grpc/grpc#30640 Restore noxfile once the merged fix is released
This was referenced Aug 24, 2022
Merged
veblush
added a commit
that referenced
this issue
Sep 20, 2022
* Bump 1.49.x branch to 1.49.0.pre1 (#30615) * bump version to 1.49.0-pre1 * regenerate projects * [backport][v1.49.x] forkable fixes (#30646) * Fix forkable globals (#30608) * Fix forkable repeated registration (#30642) This fixes a bug that could occur on repeated grpc initialization (after a complete shutdown) Fixes #30640 * Drop support for ruby 2.5 (#30699) (#30762) * Drop ruby 2.5 support * Backport: "stabilize the C2P resolver URI scheme" to v1.49.x (#30654) * stabilize the C2P resolver URI scheme * Bump 1.49 branch to 1.49.0.pre2 (#30786) * bump version to 1.49.0-pre2 * regenerate projects * Update protobuf on ancillary packages (#30795) (#30805) * Bump release version on 1.49 to 1.49.0.pre3 (#30814) * bump version to 1.49.0-pre3 * regenerate projects * xDS interop: enable pod log collection in the buildscripts (#30735) (#30856) - Enables pod log collection in all PSM interop jobs implemented in #30594. - Associate test suite runs with their own log file, so it's displayed on "Target Log" tab * xDS interop: buildscripts: fix run_test return status (#30768) (#30875) To capture the return status of the test in run_test the last command must be the call to the test itself. This removes `set +x`, which makes the run_test always return success, and not propagate the test status. I can't find it, but this exact error bit us before. Looks like it leaked to other scripts. The good thing is if the test was executed, it's failure would still be picked up from the result xml. However, if the test framework didn't start in the first place, the result will be false positive. Example: https://source.cloud.google.com/results/invocations/98d3e679-ec8a-40bd-9f36-88179747b0d6/targets ``` /home/kbuilder/.pyenv/versions/k8s_xds_test_runner/bin/python3: Error while finding module specification for 'tests.authz_test' (ModuleNotFoundError: No module named 'tests') + set +x Failed test suites: 0 [ID: 3548168] Command finished after 625 secs, exit value: 0 ``` * client_channel: fix crash when cancelling a watch after SHUTDOWN (#30885) (#30928) * Support Python 3.11 (#30818) (#30944) * Support Python 3.11 * Update build images for 3.11 * Whoopsie * The architecture of this thing is garbage * Silence ownership warning * Account for change in git behavior * Fix directory * I am in great pain * Update Windows and arm linux * Agh * Clean up * Bump 1.49 branch to 1.49.0 (#30974) * bump version to 1.49.0 * regenerate projects * Update protobuf to v21.6 on 1.49.x (#31028) * Update third_party/protobuf * run tools/distrib/python/make_grpcio_tools.py * update build_handwritten.yaml * regenerate projects * Bump v1.49.x to v1.49.1 (#31037) * bump version to 1.49.1 * regenerate projects * Automated change: Fix sanity tests Co-authored-by: gnossen <gnossen@users.noreply.github.com> * Fix ruby windows ucrt build (#31053) Co-authored-by: apolcyn <apolcyn@google.com> Co-authored-by: AJ Heller <hork@google.com> Co-authored-by: Richard Belleville <rbellevi@google.com> Co-authored-by: Sergii Tkachenko <sergiitk@google.com> Co-authored-by: Mark D. Roth <roth@google.com> Co-authored-by: Richard Belleville <gnossen@gmail.com> Co-authored-by: gnossen <gnossen@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of gRPC and what language are you using?
Here are the installed python packages, no idea which version of grpc runs underneath.
What operating system (Linux, Windows,...) and version?
What runtime / compiler are you using (e.g. python version or version of gcc)
What did you do?
This is not very minimal, but I couldn't find any other way to reproduce it so far.
What did you expect to see?
The test suite should work.
What did you see instead?
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
See TROUBLESHOOTING.md for how to diagnose problems better.
Anything else we should know about your project / environment?
The testing environment uses some multi-threading and asyncio.
The text was updated successfully, but these errors were encountered: