* Dockerfile to 3.9
* Python version
* More python updates
* 3.9 on GitHub actions and lint updates
* Test out 3.9.11 on GitHub actions
* install python with an action
* formatting: newline
* Also has python code
* only check first level for changed modules
Previous example (source-google-search-console/credentials)
* Test failure: there is no logger.trace
* Added RDS base performance tests for source-postgres, source-mssql and source-mysql
* updated perfomance test with cpu and memory limit
Co-authored-by: andriikorotkov <andrii.h.korotkov@globallogic.com>
* upgrade to gradle 7.2
* get build working with gradle 7.2
* fix build
* fix connector build?
* EXCLUDE distTar and switch includes to excludes
* switch back to includes
* temporarily try to adjust properties
* don't know why this was modified
* revert spotless upgrade
* upgrade gradle node (better arm support it says)
* add back in Xss since we are getting StackOverflowError without it
* revert bad spotless fmt
* fix acceptance tests duplicates strategy
* add zip for jdbc includes
* check if this helps for java connectors
* remove accidental commit
* remove redundant
* fix warning explosion
* oops
* override gradle.properties
* remove set-env
This is what the plugin's maintainer suggested: xvik/gradle-use-python-plugin#19.
I ran the build 10 times in a row without any checkPython error so this does seem to have fixed it.
* working except for too much logging and bad success case
* succeeds on passing case
* completes successfully
* just doesn't kill the main
* working zombie killing
* cleanup
* more cleanup
* use correct path
* fmt
* cleanups, bugfixes, integration tests
* run worker integration tests as part of ci
* delete tester class
* fix hanging checkpoint container problem
* fix name of command
* replace todo with clarifying comment
Completely test the OAuth module and streams/core.py file.
Add pytest-mock as well as a convenience wrapper to run the type checker and the test together when developing.
Also configure pytest to pick up loggers at the INFO level and above, and pick up standard out for easier debugging.
Some of the script bits are unpolished - will improve them as we go along.
Upgrade to Pip 21.1 in preparation to upgrade DBT 19.
The latest Pip has
- a stricter resolver
- access to more up to date Python wheels (e.g. #2267 is solved since as any version after Pip 21 has access to ready-compiled Python wheels, see https://issues.apache.org/jira/browse/ARROW-11835).
- in theory faster pip installs (https://github.com/pypa/pip/issues/9187#issuecomment-826037738 makes me think the current Pip version is stable enough be consumed)
Also relax the constraint for `requests` and `backoff` since both were actually specifying incompatible versions that the old Pip resolver was silently swallowing.
Test this locally first by running git clean -dfx to remove all the existing venv files. The two different Pip versions do not work well.
