aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/python/grpcio_tests
Commit message (Collapse)AuthorAge
* Merge pull request #17266 from lidizheng/python-channelzGravatar Lidi Zheng2018-11-29
|\ | | | | Channelz Python wrapper implementation
| * Update docstring of Channelz function && add default variable initializationGravatar Lidi Zheng2018-11-29
| |
| * Update comments && modify function nameGravatar Lidi Zheng2018-11-29
| |
| * Disable three subchannel unit tests for geventGravatar Lidi Zheng2018-11-28
| |
| * Remove the `del` hack and skip server related test casesGravatar Lidi Zheng2018-11-28
| |
| * Adopt reviewer's suggestionsGravatar Lidi Zheng2018-11-28
| | | | | | | | | | | | | | * Correct the StatusCode * Format code * Use @staticmethod * Fix typo
| * Channelz Python wrapper implementationGravatar Lidi Zheng2018-11-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Expose the C-Core API in Cython layer * Handle the object translation * Create a separate package for Channelz specifically * Handle nullptr and raise exception if seen one * Translate C++ Channelz unit tests * Adding 5 more invalid query unit tests Adding peripheral utility for grpcio-channelz package * Add to `pylint_code.sh` * Add to Python build script * Add to artifact build script * Add to Bazel * Add to Sphinx module list
* | Merge pull request #17281 from lidizheng/issue-16718Gravatar Lidi Zheng2018-11-26
|\ \ | | | | | | Raise the exception while credential initialization
| * | Raise the exception while credential initializationGravatar Lidi Zheng2018-11-26
| |/
* | Merge pull request #15640 from jtattermusch/slow_python_interop_buildGravatar Jan Tattermusch2018-11-26
|\ \ | | | | | | Run interop tests using python3.4 (and build interop with 3.4 only)
* | | Remove BUILD.bazel files from beta code elementsGravatar Mehrdad Afshari2018-11-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Beta code elements are going to get deprecated and Bazel support is much newer, so Bazel users are not supposed to accidentally depend on beta code elements. Preventing Bazel from building and including beta code elements makes our tests pass without depending on beta in grpcio target and helps avoid including that dependency accidentally if you are using Bazel.
* | | Removed unused import from grpc.beta in testsGravatar Mehrdad Afshari2018-11-21
| | |
| * | trailing "-bin" metadata is binaryGravatar Jan Tattermusch2018-11-21
| | |
| * | fix initial->trailingGravatar Jan Tattermusch2018-11-21
| | |
| * | make client_email loading python3 compatibleGravatar Jan Tattermusch2018-11-21
|/ /
* / python: close channels in _server_ssl_cert_config_testGravatar Eric Gribkoff2018-11-20
|/
* Regenerate projectsGravatar Muxi Yan2018-11-19
|
* Merge pull request #17143 from grpc/module-root-loggerGravatar Richard Belleville2018-11-12
|\ | | | | Only Add NullHandler to Module-Root Logger
* | Add missing transitive dependenciesGravatar Richard Belleville2018-11-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit resolves an interop test currently failing on master. Over the past couple of weeks, bazel-based tests have been introduced. The current setup does not appear to automatically handle transitive dependencies. Instead, transitive dependencies such as `requests` have been manually added to `requirements.bazel.txt`. It appears that the build server happened to have the dependencies of the `requests` library installed already, but later had a configuration wipe. This was compounded by the google-auth library erroneously reporting that the `requests` module itself was not installed. In fact, it was the transitive dependencies of `requests` that were not being installed by the build file. (third-order dependencies of our test) I consider this a quick fix to get the build passing. In the long run, we need to automatically resolve and install transitive dependencies in our bazel builds. Resolves: #17170
| * Use single NullHandler for whole libraryGravatar Richard Belleville2018-11-09
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I was trying to get a feel for what the rest of the python ecosystem does with its logging, so I looked into the top few libraries on pypi: urllib3 maintains a logger for not quite every module, but for each one that does heavy lifting. The logger name is `__name__`, and no handlers are registered for any module-level loggers, including NullHandler. Their documentation spells out how to configure logging for the library. They explicitly configure a library root-level logger called `urllib3` to which they attach a `NullHandler`. This addresses the "no handlers could be found" problem. Their tests explicitly configure handlers, just like ours do. scrapy is more hands-on. It provides a configuration module for its logging and a whole document on how to handle logging with scrapy. It looks like log.py's whole reason for existence is making sure that a handler is attached to to the scrapy handler at startup. I think the extra complexity here is because scrapy also offers a CLI, so there has to be some way to configure logging without resorting to writing python, so I felt we didn't need to resort to this added complexity. --- Based on all of the libraries I've looked at, I think our current approach is reasonable. The one change I would make is to explicitly configure a `grpc` logger and to only attach a `NullHandler` to it instead of putting the burden on the author of each new module to configure it there. With this change, I have - Configured a logger in each module that cares about logging - Removed all NullHandlers attached to module-level loggers - Explicitly configured a `grpc` logger with a `NullHandler` attached Resolves: #16572 Related: #17064
* Merge pull request #16995 from lidizheng/from-3.4-to-3.7Gravatar Lidi Zheng2018-11-07
|\ | | | | Migrate tests from Python 3.4 to Python 3.7
* \ Merge pull request #16919 from lidizheng/wait-for-readyGravatar Lidi Zheng2018-11-07
|\ \ | | | | | | Add wait-for-ready semantics
| * | Add wait-for-ready semanticsGravatar Lidi Zheng2018-11-06
| | | | | | | | | | | | | | | | | | * Include unit tests to test default behaviour, disable behaviour, enable behaviour of the wait-for-ready mechanism * Import flags constants from grpc_types.h * Use WaitGroup to wait for TRANSIENT_FAILURE state in unit test
| | * Migrate tests from Python 3.4 to Python 3.7Gravatar Lidi Zheng2018-11-06
| | |
* | | Merge pull request #16976 from benjaminp/remove-pkg_resourcesGravatar Lidi Zheng2018-11-05
|\ \ \ | | | | | | | | Replace pkg_resources with pkgutil.
* | | | Add support for utf-8 error messagesGravatar Lidi Zheng2018-11-05
| |/ / |/| | | | | | | | | | | * Both server and client should be fine with utf-8 error messages now * Adding an interop test: special status message
* | | Merge pull request #17081 from nathanielmanistaatgoogle/restore-python-bazelGravatar Srini Polavarapu2018-11-02
|\ \ \ | | | | | | | | Restore reverted Python Bazel work
| | * | Replace pkg_resources with pkgutil.Gravatar Benjamin Peterson2018-11-01
| | |/ | | | | | | | | | pkg_resources (part of setuptools) is overkill for reading resource files. The standard library module pkgutil can do that just fine.
* | | Use custom assertionsGravatar Richard Belleville2018-11-01
| | |
* | | Isolate logging in all test casesGravatar Richard Belleville2018-11-01
| | |
| * | Bazel rules for gRPC Python interop testsGravatar Naresh2018-11-01
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add interop tests for gRPC Python. py_proto_library rules are added to src/proto/grpc/testing/BUILD since grpc_proto_library is not compatible with py_* rules. 'requests' python module is added to requirements.bazel.txt as it is a dependency for google-auth. Previously, this was installed through tools/run_tests/helper_scripts/build_python.sh before running tests.
| * | Bazel rules for Python grpcio_reflectionGravatar Naresh2018-11-01
| |/
* | Appease the yapf godsGravatar Richard Belleville2018-10-31
| |
* | Add explicit test that user can configure their own handlerGravatar Richard Belleville2018-10-31
| |
* | Fix splatGravatar Richard Belleville2018-10-31
| |
* | Format codeGravatar Richard Belleville2018-10-31
| |
* | Pull out function to patch stderrGravatar Richard Belleville2018-10-31
| |
* | Add test for 'No handlers could be found' problemGravatar Richard Belleville2018-10-31
| |
* | Format codeGravatar Richard Belleville2018-10-31
| |
* | Add logging tests to tests.jsonGravatar Richard Belleville2018-10-31
| |
* | Fix various mind-numbing typosGravatar Richard Belleville2018-10-30
| |
* | Add basicConfig handler to grpcio_testingGravatar Richard Belleville2018-10-30
| |
* | Add basicConfig handler to unit testsGravatar Richard Belleville2018-10-30
| |
* | Add NullHandler to avoid warnings about no handlerGravatar Richard Belleville2018-10-30
| |
* | Revert "Configure module level loggers with basicConfig()"Gravatar Richard Belleville2018-10-30
| | | | | | | | This reverts commit a20e2073c1c53cbdd81a4fb750982a0b13e0c24e.
* | Add failing unit testGravatar Richard Belleville2018-10-30
|/
* Merge branch 'master' of https://github.com/grpc/grpc into channelzGravatar ncteisen2018-10-15
|\
* | Ban gevent testGravatar ncteisen2018-10-15
| |
| * Merge pull request #16864 from lidizheng/masterGravatar Lidi Zheng2018-10-15
|/| | | | | Fix Exception throw for invalid channel args
| * fix Exception throw for invalid channel argsGravatar Lidi Zheng2018-10-14
| | | | | | | | | | | | * unit test included * throw ValueError exception from Cython to Python * prevent the deconstruction method from failing when Channel initialization failed
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-05 04:15:57 +0000