New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUGFIX] Temporarily pin SqlAlchemy to < 1.4.0 #2547
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Shinnnyshinshin
commented
Mar 15, 2021
Comment on lines
-28
to
+29
Datasources use Batch Kwargs to specify instructions for how to access data from | ||
relevant sources such as an existing object from a DAG runner, a SQL database, S3 bucket, or local filesystem. | ||
Datasources use Batch Kwargs to specify instructions for how to access data from relevant sources such as an | ||
existing object from a DAG runner, a SQL database, S3 bucket, or local filesystem. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was just to trigger the full build
Shinnnyshinshin
changed the title
[WIP] pin sqlalchemy
Temporarily pin sqlalchemy to < Mar 15, 2021
1.4.0
for sqlalchemy dev requirements
Shinnnyshinshin
changed the title
Temporarily pin sqlalchemy to <
Temporarily Pin SqlAlchemy to < 1.4.0
Mar 15, 2021
1.4.0
for sqlalchemy dev requirements
Shinnnyshinshin
changed the title
Temporarily Pin SqlAlchemy to < 1.4.0
Temporarily pin SqlAlchemy to < 1.4.0
Mar 15, 2021
Shinnnyshinshin
changed the title
Temporarily pin SqlAlchemy to < 1.4.0
[WIP] Temporarily pin SqlAlchemy to < 1.4.0
Mar 15, 2021
Shinnnyshinshin
changed the title
[WIP] Temporarily pin SqlAlchemy to < 1.4.0
[BUGFIX] Temporarily pin SqlAlchemy to < 1.4.0
Mar 15, 2021
Shinnnyshinshin
requested review from
anthonyburdi,
alexsherstinsky,
Aylr,
eugmandel,
gilpasternak35,
spbail and
talagluck
March 15, 2021 23:41
Aylr
approved these changes
Mar 16, 2021
peterdhansen
pushed a commit
to peterdhansen/great_expectations
that referenced
this pull request
Mar 29, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes proposed in this pull request:
registry
issqlalchemy.dialects.registry
which isNone
becausesqlalchemy
isNone
)requirements-dev-sqlalchemy.txt
file. This will allow PRs that are currently blocked to move forward, as the "real" cause is either fixed or further investigated.