I experienced this issue recently while syncing a database from an Acquia hosted dev environment to my local environment. This error led me to investigate the dump file which I found included global transaction identifier (GTID) sets. I was able to work around this issue by suppressing the GTID sets using the --set-gtid-purged=OFF option for the mysqldump command. Combining that option with the drush sql-sync command allows a successful sync.
A local Drupal environment can be created in many different ways. I recommend this approach for many reasons. Most of all, this method is used by many of the top professionals to develop enterprise Drupal sites. Additionally, it's automated, and easy enough for a beginner to get started, without worrying about all the technical details. At least, not to start (smirking).
The general idea is to edit the Pluggable Authentication Module (PAM) daemon sudo config file, and add the Touch ID module as the first type of authentication presented.
Create a script (preferred)
Several tutorials exist online explaining how to edit the PAM sudo file manually, which I also explain later in this post. However, I noticed after every time MacOS is updated, I need to reapply the fix. So, I decided to write a script to automate the process. This way, after updating MacOS, I simply execute my script.
I ran into an issue implementing reCaptcha on my website, after making several updates and changes to my architecture. The problem was the reCaptcha was always failing, even after every successful submission. In order to figure out the problem, I put the following code in the submit method of the Drupal7Post class.