chore: Bumping fastapi + starlette#3938
Conversation
Bumps [fastapi](https://github.com/tiangolo/fastapi) from 0.99.1 to 0.109.1. - [Release notes](https://github.com/tiangolo/fastapi/releases) - [Commits](fastapi/fastapi@0.99.1...0.109.1) --- updated-dependencies: - dependency-name: fastapi dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
012dbd2 to
bcebc63
Compare
February 7, 2024 02:55
Signed-off-by: Chester Ong <chester.ong.ch@gmail.com>
bcebc63 to
b9b8b26
Compare
February 7, 2024 02:56
Sorry, something went wrong.
|
Considering upgrading mypy too? 👀 |
Sorry, something went wrong.
|
I'm looking to pin the mypy version to 1.4.1 but like the #3942 there are quite a number of linting failures. Let me see if I can do one with minimum changes. |
Sorry, something went wrong.
Signed-off-by: Chester Ong <chester.ong.ch@gmail.com>
Signed-off-by: Chester Ong <chester.ong.ch@gmail.com>
…tedError Signed-off-by: Chester Ong <chester.ong.ch@gmail.com>
Signed-off-by: Chester Ong <chester.ong.ch@gmail.com>
0ef5334 to
d9ddf13
Compare
February 8, 2024 07:34
|
I'm of the opinion to skip tests mypy type errors till a later PR. Seems like alot of classes in sdk/python/tests/integration/feature_repos/universal/**/* have classes that do not confirm to the BaseClass abstract method definition. For example: subclass: |
Sorry, something went wrong.
Signed-off-by: Chester Ong <chester.ong.ch@gmail.com>
Signed-off-by: Chester Ong <chester.ong.ch@gmail.com>
Signed-off-by: Chester Ong <chester.ong.ch@gmail.com>
Signed-off-by: Chester Ong <chester.ong.ch@gmail.com>
Signed-off-by: Chester Ong <chester.ong.ch@gmail.com>
Signed-off-by: Chester Ong <chester.ong.ch@gmail.com>
|
@sudohainguyen could you rerun the tests. Linting should pass now |
Sorry, something went wrong.
|
great! re-running |
Sorry, something went wrong.
e1ac385 to
94ced34
Compare
February 8, 2024 16:33
Signed-off-by: Chester Ong <chester.ong.ch@gmail.com>
Sorry, something went wrong.
|
great, now unit tests 😓 |
Sorry, something went wrong.
…concrete Signed-off-by: Chester Ong <chester.ong.ch@gmail.com>
|
@sudohainguyen my bad, please try again. Hopefully I can get this in before lunar new year |
Sorry, something went wrong.
|
Perfect! All checks passed |
Sorry, something went wrong.
sudohainguyen
left a comment
There was a problem hiding this comment.
great work! all problem solved
lgtm
is there any issue in terms of performance we should know? @bushwhackr
Sorry, something went wrong.
None at all, all changes are to fix linting issues. |
Sorry, something went wrong.
|
to revert to the old mypy settings: |
Sorry, something went wrong.
|
alright, let's get rid of it in another PR |
Sorry, something went wrong.
|
any blockers? |
Sorry, something went wrong.


What this PR does / why we need it:
Bumping vuln fastapi version. https://nvd.nist.gov/vuln/detail/CVE-2024-24762
Changes
sdk/python/feastdirectoryWhich issue(s) this PR fixes:
Fixes #3931 #3930