sql-parser
sql-parser copied to clipboard
phpmyadmin
ContextMariaDb100133 does not exist
Suddenly when trying to use phpmyadmin, I am receiving the error below. Interestingly, I was in a debugging session debugging some php code. I went to use phpmyadmin and in the debugger context.php popped up. I closed out the debugger, tried to go to phpmyadmin and received this error. My database seems to be fine as I can get to it via the command line. I use phpmyadmin a lot so would like to get this working. How do I recover from it? Cheers, Michael
Fatal error: Uncaught PhpMyAdmin\SqlParser\Exceptions\LoaderException: Specified context ("\PhpMyAdmin\SqlParser\Contexts\ContextMariaDb100133") does not exist.
@williamdes Have a look at https://github.com/phpmyadmin/sql-parser/tree/master/src/Contexts; seems a file is missing. However I'm not sure as all filenames end with 00.
Hi William, When I first submitted that bug, I literally couldn't get into phpmyadmin. I had rebooted, the whole 9 yards. I didn't open anything else after rebooting, I just started the xampp stack tried to bring it up, and received that error. Now, I know this sounds strange, but it just seemed to clear itself. Not sure what did it. BUT.... I can reproduce this at will by having phpmyadmin up and debug my php app within Visual Code simultaneously. It just happened again. Attached is a screen shot of where the crash happens within Context.php. I then have to stop my debugging session, ensure phpmyadmin isn't running and resume my debug session. AND afterwards, I bring phpmyadmin up it is USUALLY fine. Obviously the workaround is don't have phpmyadmin open when debugging with Visual Code. However, there must be a certain case where it acts a bit more nefarious and doesn't clear itself straight away -- hence my bug submission. Up to that point, it happened a lot, but as I stated, I just learned to ensure phpmyadmin wasn't running. Then that one time happened. Seriously for a day, no matter what I did, I couldn't get phpmyadmin running, I kept receiving that error. Have no clue as to what fixed it. Cheers,Michael
@mrbrown2207 Thank you for the feedback, I will try to reproduce this as soon as possible. What you describe seems to be a php/Xdebug issue for me Needs some investigation ;)