Skip to content

Bump sqlparse from 0.4.1 to 0.4.2#25

Open
dependabot[bot] wants to merge 65 commits intohackzurichfrom
dependabot/pip/sqlparse-0.4.2
Open

Bump sqlparse from 0.4.1 to 0.4.2#25
dependabot[bot] wants to merge 65 commits intohackzurichfrom
dependabot/pip/sqlparse-0.4.2

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot Bot commented on behalf of github Sep 10, 2021

Bumps sqlparse from 0.4.1 to 0.4.2.

Changelog

Sourced from sqlparse's changelog.

Release 0.4.2 (Sep 10, 2021)

Notable Changes

  • IMPORTANT: This release fixes a security vulnerability in the strip comments filter. In this filter a regular expression that was vulnerable to ReDOS (Regular Expression Denial of Service) was used. See the security advisory for details: GHSA-p5w8-wqhj-9hhf The vulnerability was discovered by @​erik-krogh and @​yoff from GitHub Security Lab (GHSL). Thanks for reporting!

Enhancements

  • Add ELSIF as keyword (issue584).
  • Add CONFLICT and ON_ERROR_STOP keywords (pr595, by j-martin).

Bug Fixes

  • Fix parsing of backticks (issue588).
  • Fix parsing of scientific number (issue399).
Commits
  • b1f76f6 Update changelog.
  • 3eec44e Update Changelog and bump version.
  • 8238a9e Optimize regular expression for identifying line breaks in comments.
  • e660467 Fix parsing of scientific numbers (fixes #399).
  • 23d2993 Update authors and changelog.
  • acc2810 keyword, add ON_ERROR_STOP
  • 282bcf1 keyword, add CONFLICT to postgres keywords
  • 63885dd Add ELSIF as keyword (fixes #584).
  • e575ae2 Fix parsing of backticks (fixes #588).
  • fe39072 Switch back to development mode.
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

…e now database to "hint" which columns should get used), we need to bring together how we use the database/values. Now we use the base data (database) for two things:

    * to put together a list of values from which the neural network later hase to pick the right one.
    * to get "hints" which column should get selected, based on if we find a value in this column.
All this is done in this merge, which should hopefully run again :-)
…gain - it does not make sense to check this in, as the guys from spider change data regularly.
…ized anymore. Now it's working again.

Also removed the value_encodings code as it is not used and will most probably also never.
…are anyway empty we don't wanna pay too much attention. The reason for the error is using the keyword "cast" as a column as far as I see.
…son" file. Also add values to the "ner_train.json"
…eparator token, as the model has been trained with exactly this tokens anyway. Keep in mind that we might soon skip this whole step, as averaging is not used right now - question token length is always 0.
… question is not equal to number of tokens. This is due to subword tokenzing.
…taoyds/test-suite-sql-eval). Copied code in (not yet adapted) and moved old evaluation scripts.
…l dbs) and to log failing queries, as well as logging final results to weights & biases.
…sql-eval). Also remove tensorboard logger as we anyway only use weights & biases by now.
…much more frequent than the epochs. We would have to log with a different X-Scale than number of epochs.
…sing) as it has a bug with python > 3.6 and is not maintained anymore. We use now Spacy and will in the future also remove all other lemmatization tools in pre-processing.

Also remove unused code in post-processing.
…PostgreSQL start to contain more and more logic it is necessary to share the common logic in a parent class. Also made shared logic parameterizable. New code is tested.
…ng/evaluation/inference) is not duplicated anymore. That way changes on the model need to be done only once.
…sformed to "nice" sql (see mongo_data_loader.py). We now need to manually adapt 40 of them as the spider project doesn't know "not exists" statements.
…gathered via Operator Tree Tool and now converted to Spider format.
…r from sql2SemQL.py.

Due to improvements on sql2SemQL.py this cleanup was necessary.
Re-run on Spider TRAIN/DEV to make sure it still works.
…r train_spider.json and train_others.json to one dataset)
brunnurs and others added 27 commits March 7, 2021 12:44
…-between tables as extra filters, which was simply not realistic (as they would not have been mentioned in the question - so how should the model have been able to learn them?).

Now we use the table graph together with the Dijkstra algorithm to get the in-between tables and only model table as joins which are not anyways in-between tables.
…roducible build

- Return score for each solution from beam search
- Small adaptions to the code due to python 3.8 update
…its to the database found in hack_zurich_database.dmp. The create_views.sql script is only necessary when building up the database from scratch again.
Bumps [sqlparse](https://github.com/andialbrecht/sqlparse) from 0.4.1 to 0.4.2.
- [Release notes](https://github.com/andialbrecht/sqlparse/releases)
- [Changelog](https://github.com/andialbrecht/sqlparse/blob/master/CHANGELOG)
- [Commits](andialbrecht/sqlparse@0.4.1...0.4.2)

---
updated-dependencies:
- dependency-name: sqlparse
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Sep 10, 2021
@dependabot @github
Copy link
Copy Markdown
Author

dependabot Bot commented on behalf of github Sep 17, 2021

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants