| Commit message (Collapse) | Author | Age |
|\
| |
| |
| |
| |
| | |
Conflicts:
src/core/security/google_default_credentials.c
test/core/security/verify_jwt.c
|
| | |
|
| |\
| | |
| | | |
Testing port server
|
| | | |
|
| | |
| | |
| | |
| | | |
... also fix things that were broken :)
|
| |\ \
| |/ /
|/| |
| | | |
server_creds_auth_md_processor
|
| | |\
| |_|/
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
run_tests.py will start a server (if it's not running, or if the running
port server mismatches the 'current' one) that serves ports to use for
tests. The server is left running after run_tests.py finishes, so that
in environments such as Mac and Windows where tests run unshielded from
each other, we don't start jumping on already used ports.
|
| |\ \
| | |/
| |/|
| | | |
complain-with-both-passion-and-meaning
|
|\| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Currently, if two threads call grpc_completion_queue_pluck on the same
completion queue for different tags, there is a 50% chance that we
deliver the completion wakeup to the wrong poller - forcing the correct
poller to wait until its polling times out before it can return an event
up to the application.
This change tweaks our polling interfaces so that we can indeed wake a
specific poller.
Nothing has been performance tuned yet. It's definitely sub-optimal in a
number of places. Wakeup file-descriptors should be recycled. We should
have a path that avoids calling poll() followed by epoll(). We can
probably live without it right at the second though.
This code will fail on Windows at least (I'll do that port when I'm in the office and have a Windows
machine).
|
|/ / |
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Right now it is a global function: would be better to have this per
(secure) port.
- Changed the interface of the auth_context slightly to make it more
friendly.
- Positive tests pass. Still need some work on error case (have a
negative case as well).
- Fixing cpp auth context tests so that they use the shiny new C API.
|
| | | |
|
| |/
|/| |
|
|/
|
|
|
| |
Use it to validate that arithmetic on time types makes even some vague
kind of sense.
|
|\ |
|
| |\ |
|
| | |\ |
|
| | | |\ |
|
| | | | | |
|
| |\ \ \ \
| | | |_|/
| | |/| | |
|
| | |\ \ \
| |_|/ / /
|/| | | | |
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
Base64 decode improvements
|
| | |\ \ \
| |_|/ / /
|/| | | | |
|
| |_|/ /
|/| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Handle the case where we recreate an auth context.
Add (opt-in) debugging for refcounts on auth contexts.
|
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | | |
Still missing:
- Caching of the already checked JWTs (although it could be done at an
upper layer).
- Caching of the jwks_uri to avoid 2 roundtrips for each verification.
|
| |/
|/| |
|
|/
|
|
|
| |
- Allow ablity to specify the length for decoding.
- Allow for non-padded encodings to be decoded properly.
|
|\ |
|
| |
| |
| |
| |
| | |
The issue remains that we don't test our tools, but at least we test
that they compile.
|
| | |
|
| | |
|
| |\
| |/
|/| |
|
| | |
|
| |\
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
Makefile
src/core/iomgr/pollset_posix.c
src/core/surface/call.c
src/core/surface/channel.c
src/core/surface/server.c
src/python/src/grpc/_adapter/_low_test.py
tools/doxygen/Doxyfile.core.internal
|
|\ \
| | |
| | |
| | |
| | |
| | | |
Conflicts:
src/core/iomgr/fd_posix.h
src/core/iomgr/iomgr.c
|
| | |\
| |_|/
|/| | |
|
| | | |
|
|/ /
| |
| |
| |
| | |
This allows a list of them to be dumped to isolate where memory leaks
are occuring.
|
| | |
|
| |\
| |/
|/| |
|
| |
| |
| |
| | |
Fixes #1843
|
| |\
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
Makefile
build.json
src/core/security/credentials.c
src/core/security/credentials.h
src/core/surface/call.c
test/core/end2end/tests/request_response_with_payload_and_call_creds.c
tools/doxygen/Doxyfile.c++
tools/doxygen/Doxyfile.core
|
|\ \ |
|
| | | |
|