Skip to content
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

Notice in ./vendor/phpmyadmin/sql-parser/src/Parser.php#483 #413

Closed
liviuconcioiu opened this issue Jan 19, 2023 · 5 comments · Fixed by #414
Closed

Notice in ./vendor/phpmyadmin/sql-parser/src/Parser.php#483 #413

liviuconcioiu opened this issue Jan 19, 2023 · 5 comments · Fixed by #414
Assignees
Milestone

Comments

@liviuconcioiu
Copy link
Contributor

liviuconcioiu commented Jan 19, 2023

Steps to reproduce:

  1. Go to https://demo.phpmyadmin.net/QA_5_2/index.php?route=/database/sql&db=sakila
  2. Paste ANALYZE - only with this word it can be reproduced.
  3. Click on a database from the left side

Depending on settings, is either a warning or a notice. It happens on both QA_5_2 and master.

19.01.2023_20.26.01_REC.mp4
Notice in ./vendor/phpmyadmin/sql-parser/src/Parser.php#483
Trying to get property 'keyword' of non-object

Backtrace

Parser.php#377: PhpMyAdmin\SqlParser\Parser->parse()
Linter.php#126: PhpMyAdmin\SqlParser\Parser->__construct()
LintController.php#59: PhpMyAdmin\Linter::lint(string 'ANALYZE')
Routing.php#191: PhpMyAdmin\Controllers\LintController->__invoke(
,
array,
)
index.php#43: PhpMyAdmin\Routing::callControllerForRoute(
,
string '/lint',
,
,
)
Warning in ./vendor/phpmyadmin/sql-parser/src/Parser.php#483
Attempt to read property "keyword" on null

Backtrace

    Parser.php#377: PhpMyAdmin\SqlParser\Parser->parse()
    Linter.php#125: PhpMyAdmin\SqlParser\Parser->__construct()
    LintController.php#59: PhpMyAdmin\Linter::lint(string 'ANALYZE')
    Routing.php#167: PhpMyAdmin\Controllers\LintController->__invoke(
    ,
    array,
    )
    Common.php#325: PhpMyAdmin\Routing::callControllerForRoute(
    ,
    ,
    ,
    )
    index.php#32: PhpMyAdmin\Common::run()
@iifawzi
Copy link
Contributor

iifawzi commented Jan 19, 2023

Thank you for reporting this @liviuconcioiu, and thanks for the backtrace

@williamdes williamdes added this to the 5.7.0 milestone Jan 19, 2023
@williamdes williamdes self-assigned this Jan 19, 2023
@williamdes
Copy link
Member

Do you think @liviuconcioiu we should make a parser release or wait for phpMyAdmin to be released first and then do it as we had planned?

williamdes added a commit that referenced this issue Jan 19, 2023
Pull-request: #414

Signed-off-by: William Desportes <williamdes@wdes.fr>
@liviuconcioiu
Copy link
Contributor Author

Do you think @liviuconcioiu we should make a parser release or wait for phpMyAdmin to be released first and then do it as we had planned?

Depends how many people will use ANALYZE. I think a minor release should be done, before 5.2.1 is released.

@williamdes
Copy link
Member

Do you think @liviuconcioiu we should make a parser release or wait for phpMyAdmin to be released first and then do it as we had planned?

Depends how many people will use ANALYZE. I think a minor release should be done, before 5.2.1 is released.

Yeah we could do a minor with just this fix into it 🤔
Or release all the changes, most of the risk is released in the 5.6.0 version of the parser

@williamdes
Copy link
Member

Released as 5.7.0

Let's test the changes onto phpMyAdmin before it is released by the end of the month

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants