  The following is the TASK that is throwing the error.  I was not able to get the entire output in the gist, but I put in the beginning and ending parts with "snip" in the middle.
Thanks

TASK [geerlingguy.php-mysql : Install PHP MySQL dependencies (Debian).] ********
fatal: [drupalvm]: FAILED! => {"cache_update_time":<PHONE_NUMBER>, "cache_updated": false, "changed": false, "msg": "'/usr/bin/apt-get -y -o \"Dpkg::Options::=--force-confdef\" -o \"Dpkg::Options::=--force-confold\"     install 'php7.2-mysql'' failed: E: Sub-process /usr/bin/dpkg returned an error code (1)\n", "rc": 100, "stderr": "E: Sub-process /usr/bin/dpkg returned an error code (1)\n", "stderr_lines": ["E: Sub-process /usr/bin/dpkg returned an error code (1)"], "stdout": "Reading package lists...\nBuilding dependency tree...\nReading state information...\nThe following NEW packages will be installed:\n  php7.2-mysql\n0 upgraded, 1 newly installed, 0 to remove and 228 not upgraded.\nNeed to get 118 kB of archives.\nAfter this operation, 454 kB of additional disk space will be used.\nGet:1 http://ppa.launchpad.net/ondrej/php/ubuntu xenial/main amd64 php7.2-mysql amd64 7.2.28-3+ubuntu16.04.1+deb.sury.org+1 [118 kB]\nFetched 118 kB in 0s (226 kB/s)\nSelecting previously unselected package php7.2-mysql.\r\n(Reading database ... \r(Reading database ... 5%\r(Reading database ... 10%\r(Reading database ... 15%\r(Reading database ... 20%\r(Reading database ... 25%\r(Reading database ... 30%\r(Reading database ... 35%\r(Reading database ... 40%\r(Reading database ... 45%\r(Reading database ... 50%\r(Reading database ... 55%\r(Reading database ... 60%\r(Reading database ... 65%\r(Reading database ... 70%\r(Reading database ... 75%\r(Reading database ... 80%\r(Reading database ... 85%\r(Reading database ... 90%\r(Reading database ... 95%\r(Reading database ... 100%\r(Reading database ... 72110 files and directories currently installed.)\r\nPreparing to unpack .../php7.2-mysql_7.2.28-3+ubuntu16.04.1+deb.sury.org+1_amd64.deb ...\r\nUnpacking php7.2-mysql (7.2.28-3+ubuntu16.04.1+deb.sury.org+1) ...\r\nProcessing triggers for php7.2-fpm (7.2.28-3+ubuntu16.04.1+deb.sury.org+1) ...\r\nJob for php7.2-fpm.service failed because the control process exited with error code. See \"systemctl status php7.2-fpm.service\" and \"journalctl -xe\" for details.\r\ninvoke-rc.d: initscript php7.2-fpm, action \"restart\" failed.\r\n\u001b[0;1;31m*\u001b[0m php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager\r\n   Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor preset: enabled)\r\n   Active: \u001b[0;1;31mfailed\u001b[0m (Result: exit-code) since Tue 2020-03-10 22:17:23 UTC; 5ms ago\r\n     Docs: man:php-fpm7.2(8)\r\n  Process: 1994 ExecStopPost=/usr/lib/php/php-fpm-socket-helper remove /run/php/php-fpm.sock /etc/php/7.2/fpm/pool.d/www.conf 72 \u001b[0;1;31m(code=exited, status=203/EXEC)\u001b[0m\r\n  Process: 1992 ExecStart=/usr/sbin/php-fpm7.2 --nodaemonize --fpm-config /etc/php/7.2/fpm/php-fpm.conf \u001b[0;1;31m(code=exited, status=78)\u001b[0m\r\n Main PID: 1992 (code=exited, status=78)\r\n\r\nMar 10 22:17:23 drupalvm systemd[1]: Starting The PHP 7.2 FastCGI Process M.....\r\nMar 10 22:17:23 drupalvm php-fpm7.2[1992]: [10-Mar-2020 22:17:23] ERROR: una...)\r\nMar 10 22:17:23 drupalvm php-fpm7.2[1992]: [10-Mar-2020 22:17:23] ERROR: FPM...d\r\nMar 10 22:17:23 drupalvm systemd[1]: \u001b[0;1;39mphp7.2-fpm.service: Main process exite.../a\u001b[0m\r\nMar 10 22:17:23 drupalvm systemd[1]: \u001b[0;1;31mFailed to start The PHP 7.2 FastCGI Pr...r.\u001b[0m\r\nMar 10 22:17:23 drupalvm systemd[1]: \u001b[0;1;39mphp7.2-fpm.service: Unit entered faile...e.\u001b[0m\r\nMar 10 22:17:23 drupalvm systemd[1]: \u001b[0;1;39mphp7.2-fpm.service: Failed with result...'.\u001b[0m\r\nHint: Some lines were ellipsized, use -l to show in full.\r\ndpkg: error processing package php7.2-fpm (--unpack):\r\n subprocess installed post-installation script returned error exit status 1\r\nErrors were encountered while processing:\r\n php7.2-fpm\r\n", "stdout_lines": ["Reading package lists...", "Building dependency tree...", "Reading state information...", "The following NEW packages will be installed:", "  php7.2-mysql", "0 upgraded, 1 newly installed, 0 to remove and 228 not upgraded.", "Need to get 118 kB of archives.", "After this operation, 454 kB of additional disk space will be used.", "Get:1 http://ppa.launchpad.net/ondrej/php/ubuntu xenial/main amd64 php7.2-mysql amd64 7.2.28-3+ubuntu16.04.1+deb.sury.org+1 [118 kB]", "Fetched 118 kB in 0s (226 kB/s)", "Selecting previously unselected package php7.2-mysql.", "(Reading database ... ", "(Reading database ... 5%", "(Reading database ... 10%", "(Reading database ... 15%", "(Reading database ... 20%", "(Reading database ... 25%", "(Reading database ... 30%", "(Reading database ... 35%", "(Reading database ... 40%", "(Reading database ... 45%", "(Reading database ... 50%", "(Reading database ... 55%", "(Reading database ... 60%", "(Reading database ... 65%", "(Reading database ... 70%", "(Reading database ... 75%", "(Reading database ... 80%", "(Reading database ... 85%", "(Reading database ... 90%", "(Reading database ... 95%", "(Reading database ... 100%", "(Reading database ... 72110 files and directories currently installed.)", "Preparing to unpack .../php7.2-mysql_7.2.28-3+ubuntu16.04.1+deb.sury.org+1_amd64.deb ...", "Unpacking php7.2-mysql (7.2.28-3+ubuntu16.04.1+deb.sury.org+1) ...", "Processing triggers for php7.2-fpm (7.2.28-3+ubuntu16.04.1+deb.sury.org+1) ...", "Job for php7.2-fpm.service failed because the control process exited with error code. See \"systemctl status php7.2-fpm.service\" and \"journalctl -xe\" for details.", "invoke-rc.d: initscript php7.2-fpm, action \"restart\" failed.", "\u001b[0;1;31m*\u001b[0m php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager", "   Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor preset: enabled)", "   Active: \u001b[0;1;31mfailed\u001b[0m (Result: exit-code) since Tue 2020-03-10 22:17:23 UTC; 5ms ago", "     Docs: man:php-fpm7.2(8)", "  Process: 1994 ExecStopPost=/usr/lib/php/php-fpm-socket-helper remove /run/php/php-fpm.sock /etc/php/7.2/fpm/pool.d/www.conf 72 \u001b[0;1;31m(code=exited, status=203/EXEC)\u001b[0m", "  Process: 1992 ExecStart=/usr/sbin/php-fpm7.2 --nodaemonize --fpm-config /etc/php/7.2/fpm/php-fpm.conf \u001b[0;1;31m(code=exited, status=78)\u001b[0m", " Main PID: 1992 (code=exited, status=78)", "", "Mar 10 22:17:23 drupalvm systemd[1]: Starting The PHP 7.2 FastCGI Process M.....", "Mar 10 22:17:23 drupalvm php-fpm7.2[1992]: [10-Mar-2020 22:17:23] ERROR: una...)", "Mar 10 22:17:23 drupalvm php-fpm7.2[1992]: [10-Mar-2020 22:17:23] ERROR: FPM...d", "Mar 10 22:17:23 drupalvm systemd[1]: \u001b[0;1;39mphp7.2-fpm.service: Main process exite.../a\u001b[0m", "Mar 10 22:17:23 drupalvm systemd[1]: \u001b[0;1;31mFailed to start The PHP 7.2 FastCGI Pr...r.\u001b[0m", "Mar 10 22:17:23 drupalvm systemd[1]: \u001b[0;1;39mphp7.2-fpm.service: Unit entered faile...e.\u001b[0m", "Mar 10 22:17:23 drupalvm systemd[1]: \u001b[0;1;39mphp7.2-fpm.service: Failed with result...'.\u001b[0m", "Hint: Some lines were ellipsized, use -l to show in full.", "dpkg: error processing package php7.2-fpm (--unpack):", " subprocess installed post-installation script returned error exit status 1", "Errors were encountered while processing:", " php7.2-fpm"]}

RUNNING HANDLER [geerlingguy.firewall : restart firewall] **********************

RUNNING HANDLER [geerlingguy.php : restart webserver] **************************

RUNNING HANDLER [geerlingguy.php : restart php-fpm] ****************************

RUNNING HANDLER [geerlingguy.mysql : restart mysql] ****************************
        to retry, use: --limit @/vagrant/provisioning/playbook.retry

PLAY RECAP *********************************************************************
drupalvm                   : ok=145  changed=13   unreachable=0    failed=1

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

Job for php7.2-fpm.service failed because the control process exited with error code. See \"systemctl status php7.2-fpm.service\" and \"journalctl -xe\" for details.

Can you run systemctl status php7.2-fpm.service and journalctl -xe inside the VM to see what it says? It seems like maybe something didn't install correctly, or there's a configuration error.

Thank you @geerlingguy, here's the output you asked for:
https://gist.github.com/cynicalgenxer/9d32514a21db9d879e1f288d80fe02c9
Had to do sudo to make journalctl -xe work.  I did a similar stripped down installation attempt on my Mac setup (with updated DrupalVM, Vagrant, VirtualBox) and got the same error as well.

On my Mac I got the same error:
https://gist.github.com/cynicalgenxer/c9dfe4ca5ecc1fa59d2eeec4e2c2b557
Here are the debugging command outputs:
vagrant@drupalvm:~$ systemctl status php7.2-fpm.service

php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager
Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2020-03-11 22:16:56 UTC; 6 days ago
Docs: man:php-fpm7.2(8)
Process: 2009 ExecStopPost=/usr/lib/php/php-fpm-socket-helper remove /run/php/php-fpm.sock /etc/php/7.2/fpm/pool.d/www.conf
Process: 2007 ExecStart=/usr/sbin/php-fpm7.2 --nodaemonize --fpm-config /etc/php/7.2/fpm/php-fpm.conf (code=exited, status=7
Main PID: 2007 (code=exited, status=78)

vagrant@drupalvm:~$ sudo journalctl -xe
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
-- Kernel start-up required KERNEL_USEC microseconds.
-- Initial RAM disk start-up required INITRD_USEC microseconds.
-- Userspace start-up required 23077 microseconds.
Mar 17 22:49:40 drupalvm systemd[1]: Started User Manager for UID 900.
-- Subject: Unit<EMAIL_ADDRESS>has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit<EMAIL_ADDRESS>has finished starting up.
-- The start-up result is done.
Mar 17 22:50:05 drupalvm mailhog[811]: [APIv1] KEEPALIVE /api/v1/events
Mar 17 22:51:05 drupalvm mailhog[811]: [APIv1] KEEPALIVE /api/v1/events
Mar 17 22:52:05 drupalvm mailhog[811]: [APIv1] KEEPALIVE /api/v1/events
Mar 17 22:53:05 drupalvm mailhog[811]: [APIv1] KEEPALIVE /api/v1/events
Mar 17 22:53:28 drupalvm sudo[27090]:  vagrant : TTY=pts/0 ; PWD=/home/vagrant ; USER=root ; COMMAND=/bin/journalctl -xe
Mar 17 22:53:28 drupalvm sudo[27090]: pam_unix(sudo:session): session opened for user root by vagrant(uid=0)

Weird, there's nothing about php-fpm in there. Can you also try sudo journalctl -xn --no-pager -u php7.2-fpm?

Thanks Jeff.
https://gist.github.com/cynicalgenxer/e6756d6fd6738c929a7710381c6d4b08

That's really weird, it seems that something else in the VM is already running on port 9000, maybe?
ERROR: unable to bind listening socket for address '<IP_ADDRESS>:9000': Address already in use (98)

It seems that php-fpm itself shut down cleanly, then tried starting (at Mar 11 22:16:56), but something was running on port 9000. Can you run: netstat -tulpn | grep 9000?

Thank you again, Jeff.
vagrant@drupalvm:~$ sudo netstat -tulpn | grep 9000
tcp        0      0 <IP_ADDRESS>:9000          <IP_ADDRESS>:*               LISTEN      863/php-fpm.conf)

I can't think of anything else. I'm assuming you've tried vagrant destroy -f and then vagrant up again? Also, what base box are you using? Could you share all the config.yml things you've overridden?

Thank you so much for your time @geerlingguy
I should have read the notice at the beginning of the vagrant up output closer.   On both of my machines I had an outdated box and after I ran vagrant box update things started working properly.  DrupalVM installations based on these boxes previously worked for me but stuff changes and I should have made sure all my components were up to date.  Thanks again!

@cynicalgenxer - Ah, that makes some sense—though typically older versions of the base box should still work with newer versions of Drupal VM. But it's best to always run the latest if you can!

I am having the same error in the last days - on windows+vagrant, but not when I let the playbook run inside a native server.
Everything is up-to-date, vagrant box (2.0.10), vagrant (2.2.9) and also VirtualBox (6.1.12).
Starting from a clean state - l even precautiously restarted windows and deleted packer-VMs.
I have seen the MySQL role had update, so I also tried checking out the 6.0.0 tag - with same result.
For the full story: I had vagrant box 2.0.9 with latest master before - worked fine for weeks. Then symlinking began going wrong - I think due to me booting the VM from virtualbox, instead of using vagrant command. Since the symlinking error strangely did not want to go away anymore (and I began even suspecting a windows update from last night as a part of the cause), I cleared everything, updated the vagrant box, updated VirtualBox and now am receiving this error.
I tried running the debug commands suggested - but I cannot report anything new.

@geerlingguy I'm also experiencing the same issue.  I have narrowed this down to specifically updating the box to 2.0.10. Everything else staying the same, updating to 2.0.10 causes this issue. Downgrading to 2.0.9 resolves the issue. Updating again causes the issue.
My setup is:
macOS Catalina
Vagrant 2.2.10
VirtualBox 6.1.12r139181
Ansible 2.9.12
PHP7.3-fpm
Let's have a look inside the VM.
$ vagrant ssh
vagrant@local:~$ systemctl status php7.3-fpm.service
* php7.3-fpm.service - The PHP 7.3 FastCGI Process Manager
   Loaded: loaded (/lib/systemd/system/php7.3-fpm.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2020-08-26 07:04:48 UTC; 2min 13s ago
     Docs: man:php-fpm7.3(8)
  Process: 20756 ExecStopPost=/usr/lib/php/php-fpm-socket-helper remove /run/php/php-fpm.sock /etc/php/7.3/fpm/p
  Process: 20755 ExecStart=/usr/sbin/php-fpm7.3 --nodaemonize --fpm-config /etc/php/7.3/fpm/php-fpm.conf (code=e
 Main PID: 20755 (code=exited, status=78)

vagrant@local:~$ sudo journalctl -xn --no-pager -u php7.3-fpm
-- Logs begin at Fri 2020-08-14 21:13:42 UTC, end at Wed 2020-08-26 07:07:20 UTC. --
Aug 26 06:57:24 local php-fpm7.3[19180]: [26-Aug-2020 06:57:24] ERROR: FPM initialization failed
Aug 26 06:57:24 local systemd[1]: php7.3-fpm.service: Main process exited, code=exited, status=78/n/a
Aug 26 06:57:24 local systemd[1]: php7.3-fpm.service: Failed with result 'exit-code'.
Aug 26 06:57:24 local systemd[1]: Failed to start The PHP 7.3 FastCGI Process Manager.
-- Subject: Unit php7.3-fpm.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit php7.3-fpm.service has failed.
--
-- The result is RESULT.
Aug 26 07:04:48 local systemd[1]: Starting The PHP 7.3 FastCGI Process Manager...

Aug 26 07:04:48 local php-fpm7.3[20755]: [26-Aug-2020 07:04:48] ERROR: unable to bind listening socket for address '<IP_ADDRESS>:9000': Address already in use (98)
Aug 26 07:04:48 local php-fpm7.3[20755]: [26-Aug-2020 07:04:48] ERROR: FPM initialization failed
Aug 26 07:04:48 local systemd[1]: php7.3-fpm.service: Main process exited, code=exited, status=78/n/a
Aug 26 07:04:48 local systemd[1]: php7.3-fpm.service: Failed with result 'exit-code'.
Aug 26 07:04:48 local systemd[1]: Failed to start The PHP 7.3 FastCGI Process Manager.
-- Subject: Unit php7.3-fpm.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit php7.3-fpm.service has failed.
--
-- The result is RESULT.

vagrant@local:~$ sudo netstat -tulpn | grep 9000
tcp        0      0 <IP_ADDRESS>:9000          <IP_ADDRESS>:*               LISTEN      16093/php-fpm: mast

Interestingly, I could not restart the php7.3-fpm service.
vagrant@local:~$ sudo systemctl restart php7.3-fpm
Job for php7.3-fpm.service failed because the control process exited with error code.
See "systemctl status php7.3-fpm.service" and "journalctl -xe" for details.

I had to first kill the process. Then, reinstall php7.3-fpm.
vagrant@local:~$ sudo pkill php-fpm
vagrant@local:~$ sudo apt-get install php7.3-fpm
Reading package lists... Done
Building dependency tree
Reading state information... Done
php7.3-fpm is already the newest version (7.3.21-1+ubuntu18.04.1+deb.sury.org+1).
The following packages were automatically installed and are no longer required:
  python-asn1crypto python-cffi-backend python-crypto python-cryptography python-enum34 python-httplib2 python-idna python-ipaddress python-jinja2 python-markupsafe
  python-paramiko python-pkg-resources python-pyasn1 python-setuptools python-six python-yaml sshpass
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 24 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
W: chown to _apt:root of directory /var/cache/apt/archives/partial failed - SetupAPTPartialDirectory (1: Operation not permitted)
Do you want to continue? [Y/n] y
Setting up php7.3-fpm (7.3.21-1+ubuntu18.04.1+deb.sury.org+1) ...
NOTICE: Not enabling PHP 7.3 FPM by default.
NOTICE: To enable PHP 7.3 FPM in Apache2 do:
NOTICE: a2enmod proxy_fcgi setenvif
NOTICE: a2enconf php7.3-fpm
NOTICE: You are seeing this message because you have apache2 package installed.
Processing triggers for php7.3-fpm (7.3.21-1+ubuntu18.04.1+deb.sury.org+1) ...
NOTICE: Not enabling PHP 7.3 FPM by default.
NOTICE: To enable PHP 7.3 FPM in Apache2 do:
NOTICE: a2enmod proxy_fcgi setenvif
NOTICE: a2enconf php7.3-fpm
NOTICE: You are seeing this message because you have apache2 package installed.
W: APT had planned for dpkg to do more than it reported back (0 vs 4).
   Affected packages: php7.3-fpm:amd64

Now, it's looking better.
vagrant@local:~$ systemctl status php7.3-fpm.service
* php7.3-fpm.service - The PHP 7.3 FastCGI Process Manager
   Loaded: loaded (/lib/systemd/system/php7.3-fpm.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2020-08-26 07:25:01 UTC; 13min ago
     Docs: man:php-fpm7.3(8)
  Process: 24391 ExecStopPost=/usr/lib/php/php-fpm-socket-helper remove /run/php/php-fpm.sock /etc/php/7.3/fpm/pool.d/www.conf 73 (code=exited, status=0/SUCCESS)
  Process: 24399 ExecStartPost=/usr/lib/php/php-fpm-socket-helper install /run/php/php-fpm.sock /etc/php/7.3/fpm/pool.d/www.conf 73 (code=exited, status=0/SUCCESS)
 Main PID: 24393 (php-fpm7.3)
   Status: "Processes active: 0, idle: 5, Requests: 0, slow: 0, Traffic: 0req/sec"
    Tasks: 6 (limit: 4662)
   CGroup: /system.slice/php7.3-fpm.service
           |-24393 php-fpm: master process (/etc/php/7.3/fpm/php-fpm.conf)
           |-24394 php-fpm: pool www
           |-24395 php-fpm: pool www
           |-24396 php-fpm: pool www
           |-24397 php-fpm: pool www
           `-24398 php-fpm: pool www

So, enable the php7.3-fpm conf in Apache2, and reload.
vagrant@local:~$ sudo a2enconf php7.3-fpm
Enabling conf php7.3-fpm.
To activate the new configuration, you need to run:
  systemctl reload apache2
vagrant@local:~$ sudo systemctl reload apache2

At this point php7.3-fpm is good, but something was wrong with the config. Provision the VM.
vagrant@local:~$ exit
$ vagrant provision

And encounter another issue.
blah blah blah... php7.4-fpm

Why is it trying to use PHP 7.4?
vagrant@local:/var/www/archbos$ php -v
PHP 7.4.9 (cli) (built: Aug  7 2020 14:29:36) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
    with Zend OPcache v7.4.9, Copyright (c), by Zend Technologies

What? Why? https://github.com/geerlingguy/drupal-vm/issues/2061 OH!
To confirm, I changed the php_version in my config.yml to 7.4. The VM provisioned without a problem. However, the application has issues. The first problem I noticed is an error in devel when trying to do a BLT sync.
  <em class="placeholder">Deprecated function</em>: Array and string offset a
  ccess syntax with curly braces is deprecated in <em class="placeholder">req
  uire()</em> (line <em class="placeholder">17</em> of <em class="placeholder
  ">/var/www/archbos/docroot/modules/contrib/devel/kint/kint/Kint.class.php</
  em>).

So, there are a few ways I can see to resolve this for the time being.

When the vagrant up fails with the error message in the title of this issue, stop and disable PHP 7.4, start and enable PHP 7.3, and change the PHP CLI version.
vagrant@local:~$ sudo systemctl stop php7.4-fpm
vagrant@local:~$ sudo systemctl disable  php7.4-fpm
Synchronizing state of php7.4-fpm.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable php7.4-fpm

vagrant@local:~$ sudo systemctl start  php7.3-fpm
vagrant@local:~$ sudo systemctl enable  php7.3-fpm
Synchronizing state of php7.3-fpm.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable php7.3-fpm

vagrant@local:~$ sudo update-alternatives --set php /usr/bin/php7.3
update-alternatives: using /usr/bin/php7.3 to provide /usr/bin/php (php) in manual mode

Locking the box at version 2.0.9 by putting the following in box/Vagrantfile.local
config.vm.box_version = "2.0.9"

Fix the code to read from the php_version config properly. Instead of using the default.

The same issue is happening for me as well - I was able to get the MySQL dependencies to install correctly using
vagrant@local:~$ sudo pkill php-fpm
vagrant@local:~$ sudo apt-get install php7.3-fpm

But after that, it again fails for other PHP packages and nodejs and others as well.
What I followed was:
vagrant@local:~$ sudo systemctl reload apache2
vagrant@local:~$ exit
$ vagrant provision

Thank you.

I can confirm, 2.0.9 works without problems.
I have helped myself with vagrant box remove geerlingguy/drupal-vm --box-version 2.0.10

I am facing exactly the same problem. My environment:

macOS Catalina 10.15.6
Vagrant 2.2.10
VirtualBox 6.1.12r139181
PHP7.3-fpm
ansible 2.9.13
config file = None
configured module search path = ['/Users/neeraj/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/lib/python3.8/site-packages/ansible
executable location = /usr/local/bin/ansible
python version = 3.8.5 (default, Jul 21 2020, 10:48:26) [Clang 11.0.3 (clang-1<IP_ADDRESS>)]

vagrant up output: https://gist.github.com/neeraj-ugam/0b8c8f0c3af8f1d907edc848a6aaea37
debugging command output: https://gist.github.com/neeraj-ugam/2277ae333ac0a21c764d213c9e60fa98

Same as https://github.com/geerlingguy/drupal-vm/issues/2076

I can confirm, 2.0.9 works without problems.
I have helped myself with vagrant box remove geerlingguy/drupal-vm --box-version 2.0.10

The only one works

I can confirm that using php 7.4 fixes this, although then xdebug will fail the build, which I momentarily fixed removing xdebug
TASK [geerlingguy.php-xdebug : Build Xdebug.] **********************************
changed: [bayer] => (item=phpize)
failed: [bayer] (item=./configure) => {"ansible_loop_var": "item", "changed": true, "cmd": ["./configure"], "delta": "0:00:00.652246", "end": "2020-10-19 10:14:07.692192", "item": "./configure", "msg": "non-zero return code", "rc": 1, "start": "2020-10-19 10:14:07.039946", "stderr": "configure: error: not supported. Need a PHP version >= 7.0.0 and < 7.4.0 (found 7.4.11)", "stderr_lines": ["configure: error: not supported. Need a PHP version >= 7.0.0 and < 7.4.0 (found 7.4.11)"], "stdout": "checking for grep that handles long lines and -e... /bin/grep\nchecking for egrep... /bin/grep -E\nchecking for a sed that does not truncate output... /bin/sed\nchecking for pkg-config... /usr/bin/pkg-config\nchecking pkg-config is at least version 0.9.0... yes\nchecking for cc... cc\nchecking whether the C compiler works... yes\nchecking for C compiler default output file name... a.out\nchecking for suffix of executables... \nchecking whether we are cross compiling... no\nchecking for suffix of object files... o\nchecking whether we are using the GNU C compiler... yes\nchecking whether cc accepts -g... yes\nchecking for cc option to accept ISO C89... none needed\nchecking how to run the C preprocessor... cc -E\nchecking for icc... no\nchecking for suncc... no\nchecking for system library directory... lib\nchecking if compiler supports -R... no\nchecking if compiler supports -Wl,-rpath,... yes\nchecking build system type... x86_64-pc-linux-gnu\nchecking host system type... x86_64-pc-linux-gnu\nchecking target system type... x86_64-pc-linux-gnu\nchecking for PHP prefix... /usr\nchecking for PHP includes... -I/usr/include/php/20190902 -I/usr/include/php/20190902/main -I/usr/include/php/20190902/TSRM -I/usr/include/php/20190902/Zend -I/usr/include/php/20190902/ext -I/usr/include/php/20190902/ext/date/lib\nchecking for PHP extension directory... /usr/lib/php/20190902\nchecking for PHP installed headers prefix... /usr/include/php/20190902\nchecking if debug is enabled... no\nchecking if zts is enabled... no\nchecking for gawk... no\nchecking for nawk... nawk\nchecking if nawk is broken... no\nchecking whether to enable Xdebug support... yes, shared\nchecking whether to enable Xdebug developer build flags... no\nchecking Check for supported PHP versions... ", "stdout_lines": ["checking for grep that handles long lines and -e... /bin/grep", "checking for egrep... /bin/grep -E", "checking for a sed that does not truncate output... /bin/sed", "checking for pkg-config... /usr/bin/pkg-config", "checking pkg-config is at least version 0.9.0... yes", "checking for cc... cc", "checking whether the C compiler works... yes", "checking for C compiler default output file name... a.out", "checking for suffix of executables... ", "checking whether we are cross compiling... no", "checking for suffix of object files... o", "checking whether we are using the GNU C compiler... yes", "checking whether cc accepts -g... yes", "checking for cc option to accept ISO C89... none needed", "checking how to run the C preprocessor... cc -E", "checking for icc... no", "checking for suncc... no", "checking for system library directory... lib", "checking if compiler supports -R... no", "checking if compiler supports -Wl,-rpath,... yes", "checking build system type... x86_64-pc-linux-gnu", "checking host system type... x86_64-pc-linux-gnu", "checking target system type... x86_64-pc-linux-gnu", "checking for PHP prefix... /usr", "checking for PHP includes... -I/usr/include/php/20190902 -I/usr/include/php/20190902/main -I/usr/include/php/20190902/TSRM -I/usr/include/php/20190902/Zend -I/usr/include/php/20190902/ext -I/usr/include/php/20190902/ext/date/lib", "checking for PHP extension directory... /usr/lib/php/20190902", "checking for PHP installed headers prefix... /usr/include/php/20190902", "checking if debug is enabled... no", "checking if zts is enabled... no", "checking for gawk... no", "checking for nawk... nawk", "checking if nawk is broken... no", "checking whether to enable Xdebug support... yes, shared", "checking whether to enable Xdebug developer build flags... no", "checking Check for supported PHP versions... "]}
failed: [bayer] (item=make) => {"ansible_loop_var": "item", "changed": true, "cmd": ["make"], "delta": "0:00:00.002610", "end": "2020-10-19 10:14:07.890971", "item": "make", "msg": "non-zero return code", "rc": 2, "start": "2020-10-19 10:14:07.888361", "stderr": "make: *** No targets specified and no makefile found.  Stop.", "stderr_lines": ["make: *** No targets specified and no makefile found.  Stop."], "stdout": "", "stdout_lines": []}

Can confirm that downgrading to 2.0.9 box fixed the issue for me
vagrant box remove geerlingguy/drupal-vm --box-version 2.0.10
vagrant box add geerlingguy/drupal-vm --box-version 2.0.9
I did not try upgrading to php 7.4 with the 2.0.10 box, as the production env. for the site in question is running 7.3 and I prefer to keep my local as similar as possible.
On a side note, you're a hero for building/maintaining this @geerlingguy, it's so much better than every other local dev setup I've used.

+1
I think this should be reopened because 2.0.10 is still the newest box version and using anything else than PHP 7.4 seems to break provision. At least in our case we are not yet ready to run PHP 7.4 in every project.
Locking to 2.0.9 is of course an option but would be nice to able to support the latest version available.

If there are still some problems, can someone please post a new issue so I can work on resolving it in a new release?

I had the same issue.
Vagrant up errors out at
TASK [geerlingguy.php-mysql : Install PHP MySQL \
\ dependencies (Debian).]

And sudo journalctl -xn --no-pager -u php7.3-fpm showed

ERROR: unable to bind listening socket for address '<IP_ADDRESS>:9000': Address already in use (98)

But adding php_version: "7.3" to config.yml fixed it.
I don't know how it is relevant but worked for me.
drupal_build_composer_project: false
drupal_install_site: false

#configure_drush_aliases: false
installed_extras:
  - adminer
  # - blackfire
  # - drupalconsole
  - drush
  # - elasticsearch
  # - java
  - mailhog
  #  - memcached
  # - newrelic
  - nodejs
  - pimpmylog
  # - redis
  # - ruby
  # - selenium
  # - solr
  #- tideways
  # - upload-progress
  # - varnish
  - xdebug
  #- xhprof # use `tideways` if you're installing PHP 7+

php_packages:
  - php7.3-common
  - php7.3-cli
  - php7.3-dev
  - php7.3-fpm
  - libpcre3-dev
  - php7.3-gd
  - php7.3-curl
  - php7.3-imap
  - php7.3-json
  - php7.3-opcache
  - php7.3-xml
  - php7.3-mbstring
  - php7.3-apcu
php_mysql_package: php7.3-mysql
php_fpm_daemon: php7.3-fpm
php_conf_paths:
  - /etc/php/7.3/fpm
  - /etc/php/7.3/apache2
  - /etc/php/7.3/cli
php_extension_conf_paths:
  - /etc/php/7.3/fpm/conf.d
  - /etc/php/7.3/apache2/conf.d
  - /etc/php/7.3/cli/conf.d
php_fpm_pool_conf_path: "/etc/php/7.3/fpm/pool.d/www.conf"


ES6 Module import

Hello.
I'm trying to import midnight.js into my file where i execute whole action.
I try
import 'midnight.js/midnight.jquery.js';
import 'midnight.js
etc...
I use webpack to bundle my code.
   new webpack.ProvidePlugin({       $: 'jquery',       jQuery: 'jquery'     }),
and getting error: $(...).midnight is not a function
node 6.11.5
yarn 1.0.1
midnight.js 1.1.1

@RobertoGonzalez As far as I can tell it does not work with jQuery or $ as global


Switch from SGE to LSF

Change the workflow so that it launches ipyparallel to run on LSF instead of SGE. Making this change because our work's cluster is changing over to LSF.
Note: Still need a Docker image that provides LSF to complete this change.

This is no longer necessary as we now use dask-drmaa to start up the cluster thanks to PR ( https://github.com/nanshe-org/nanshe_workflow/pull/160 ). The dask-drmaa strategy works equally well on SGE and LSF without such a change. Given this, am closing this PR out.


[ERROR] "embeddings.py: error: unrecognized arguments: -proc 4"

Decided to circle back to pLM to see if I can get it to run more efficiently on my HPC
Git cloned the repo today and am trying to verify behavior before I attempt a massive database build.
Running with 4 GPUs
Command:
# FASTA input python embeddings.py start database.fasta database -embedder pt --gpu -proc 4 -bs 0 --asdir
Produces:
$ python embeddings.py start database.fasta database -embedder pt --gpu -proc 4 -bs 0 --asdir usage: embeddings.py [-h] {start,resume} ... embeddings.py: error: unrecognized arguments: -proc 4
Note that I can run  embeddings.py  if I remove the -proc option

Wait. just the documentation is wrong.
Looks like the correct parameter should be -nproc

Fixed.


[NEXT] Component porting timeline

Are there any timelines set for component porting for @next?
I'm specifically interested in AutoComplete, "multiple select" Menu, and TextField Menu.

I believe menu is available ==> https://material-ui-1dab0.firebaseapp.com/component-demos/menus

@stunaz to clarify regarding "multiple select" Menu, current material-ui has a multiple property whereas material-ui@next does not

We don't have any ETA for porting components. They are ported by people requiring them in production. Anyone is encouraged to help us out. Notice that you can use both the latest and next release tag of npm at the same time on your projet. Material-UI versions do not conflict. Yarn makes it really easy by the way (npm don't make it easy).
Notice that porting the component you are describing is challenging as the implementation we have on the master is far from great (many many open issues). That's at least one week of work.

I have heard more feedback regarding those components. Same for me, soon or later I'm gonna need them for the project I'm working on. I'm wondering if we couldn't move from the alpha to the beta once we have them.


Add some Debug implementations

This covers a part of https://github.com/bluss/rust-itertools/issues/32
I looked for all structs and enums and added #[derive(Debug)] where possible. I added a Debug impl for KMerge, KMergeBy, MergeJoinBy using debug_fmt_fields, printing all fields except function callable objects.

Nice. I'd skip the ones that use a closure, or fix them to ignore the closure, otherwise those debug impls almost never have any use?

I agree. I skip the ones with a closure.
As a sidenote: I tried to implement Debug for MultiProduct and realized that debug_fmt_fields can currently not deal with it because it offers a single unnamed member (accessed by self.0) because debug_fmt_fields expects idents as field names.
Is there an easy way to extend debug_fmt_fields to support those members, too?

Maybe, it's a macro we can change as appopriate. We could also just use a struct with named fields.

Thanks a lot for this, we can address the rest later.


Server won’t create

error:
An error occurred while trying to connect to the remote node. Please check that the daemon is running and try again.
An error occurred trying to add a server. () []
Idk how to fix it

Wait, how did you fix it?

As we've mentioned in the past, the issues are meant for verifiable bugs. If you need support, please use the forums @ApertureDevelopment.

You: Shush. Noone replied on the forums, and I have every right to ask how he fixed the issue on a closed issue. https://community.pufferpanel.com/topic/773/can-t-create-new-server

@ApertureDevelopment You literally posted 17 minutes ago, to a forum topic, instead of opening your own. Please open your own topic, with as much information as possible, and someone can definitely help you. Patience is a virtue, and so is following the issue submission guidelines.

https://community.pufferpanel.com/topic/800/cannot-create-servers Already did, and since he had the same issue and never got a answere, despite 174 Views. Yeah definitely someone will help

If you have an issue using the panel, make a thread on the forum. Just because it's the same "error" doesn't mean it's the same issue.
Be patient when waiting for a response, especially when you bump a thread that's a year old.


Background color in a Tray messes up its border-radius

🐛 Bug Report
When the background-color attribute is set, the border-radius is no longer respected.
🤔 Expected Behavior
Corners of the Tray should be rounded

😯 Current Behavior
Corners of the Tray are not rounded

💁 Possible Solution
Adding overflow: hidden to the Tray component seems to fix this.
🔦 Context
When using a Popover, on small widths, the Tray component is used.

Closing and if it's still a problem or you provide additional information we can reopen.


Show path in NetConnectNotAllowedError

Just showing the hostname in the error is not descriptive enough. It's more useful to show the full path, so that the developer can easily determine which request is causing the error.

@mlolson thanks!
Landed on v1.2.0


tiles as props are slightly larger than their tile counterpart

The default scale of props in 'tiles as prop' causes them to be slightly larger than their regular tile counterparts

yes, the tiles as props are 1.25 times bigger then tiles because of my conversion
will be fixed in next release


Create lab-0-ptbr.ipynb

Create lab-0-ptbr.ipynb Brazilian Portuguese translation.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@GustavoPetronilo I added a button to link to the notebook on the challenge portal. Is "Português brasileiro" correct? If not please suggest a correct translation of "Brazilian Portuguese" in "Brazilian Portuguese" :D


Dbf5('file.dbf')  AssertionError  assert terminator == b'\r

Whenever I try to load a .dbf file I am getting an error.
>>> Dbf5('myfile.dbf')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\TARGET\WinPython-64bit-<IP_ADDRESS>\python-3.3.5.amd64\lib\site-packages\simpledbf\simpledbf.py", line 557, in __init__
    assert terminator == b'\r'
AssertionError
>>>

I am using
simpledbf-0.2.6.tar.gz

on
Python 3.3.5 (v3.3.5:62cf4e77f785, Mar  9 2014, 10:35:05) [MSC v.1600 64 bit (AMD64)] on win32

Thanks,
Andre Mikulec

I'm having the same problem.  Is there any plans on addressing this issue?

I too have this problem with a file edited with the DBF Explorer.

Any update on this?

Same here, but it happens on some dbf files, not others.  Debug tips greatly appreciated if anyone has a work around?

My guess is that the assertion errors are a result of incorrect DBF file versions. There is a section in the README that explains which DBF versions are acceptable.
Have a look at the table entitled "Database file header" on the dbf Wikipedia page. The very last byte of the header should be 0x0D, which is is a carriage return. If that is not true, then you might have a different file version. For example in DBF version 7, the header has a much different length, so this code will not process it correctly.
You can check the DBF version info from the first byte of your file as follows:
f = open('my.dbf', 'rb')
f.read(1)

Convert this hex value into binary. As per the DBF7 description, bits 0-2 tell you about the version number. For example, I downloaded the file "Health Indicator Attributes" from the HRSA website. When I checked the first byte, I got '\x03', which converts to 0000 0011 in binary. The first three bits (on the far right, i.e. 011) are equivalent to 3, which according the DBF7 notes linked above indicates a DBF version 5 file.
I hope this helps. If you'd like, you can use this code as a template to create a DBF version 7 reader using the format link that I've provided. I only deal with older DBF versions, so I won't have any bandwidth to make updates to this project.

same issue, updates?

is there any alternative for this library? As I can see there is no support

is there any alternative for this library? As I can see there is no support

same issues, still no updates on this?

Same issue!

Same problem here... Please any fix for this?

Same problem here... any fix for this?


Duration and video size preset configuration for iCloud video download

Hi, is there a way to change the duration and the quality of the avExportSession from requestExportSession?

@specc
duration : https://github.com/tilltue/TLPhotoPicker/issues/35
quality : https://developer.apple.com/documentation/photos/phvideorequestoptionsdeliverymode

For duration, if I have a 1:30 minute video, I want to export it as a 15 seconds video. How do I do that?
if I set maxVideoDuration to 15, it seems to now show video longer than 15 seconds.
For quality, I want to use AVAssetExportPreset960x540 to export my video to 960x540 resolution.


[azservicebus] context cancelled reattaching link

Bug Report
Related to #19506 #19465 #18517
I have multiple services consuming from the same service bus using different subscription names but some of them suddenly stop consuming without any error being thrown. The service just freezes on receiver.ReceiveMessages(...) method call.
I've enabled all logs for the service bus library that i'm attaching below. You can see that the context has been cancelled when trying to reattach the links.
% kubectl logs application-stats-updater-v2-746d7d9666-24bk4 --timestamps=true
2022-11-14T19:55:34.418532432Z Initializing consumption loop on topic dev-contracts
2022-11-14T19:55:34.418558232Z Receiving messages on topic dev-contracts
2022-11-14T19:55:34.418585133Z Initializing consumption loop on topic dev-transactions
2022-11-14T19:55:34.418591533Z Receiving messages on topic dev-transactions
2022-11-14T19:55:34.418597633Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater) refreshing claim
2022-11-14T19:55:34.418604533Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater) refreshing claim
2022-11-14T19:55:34.418609933Z [azsb.Conn] Creating new client, current rev: 0
2022-11-14T19:55:34.618364583Z [azsb.Conn] Client created, new rev: 1, took 199ms
2022-11-14T19:55:34.618386783Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater) negotiate claim, token expires on 2022-11-14T20:10:34Z
2022-11-14T19:55:34.618434683Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater) negotiate claim, token expires on 2022-11-14T20:10:34Z
2022-11-14T19:55:34.620871612Z [azsb.Auth] negotiating claim for audience amqps://sbnamespace.servicebus.windows.net/dev-contracts/Subscriptions/application-stats-updater with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-11-14T19:55:34.622238328Z [azsb.Auth] Response router has shut down
2022-11-14T19:55:34.625211863Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater/$management) refreshing claim
2022-11-14T19:55:34.625224463Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater/$management) negotiate claim, token expires on 2022-11-14T20:10:34Z
2022-11-14T19:55:34.625229063Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater) next refresh in 4m59.993128019s
2022-11-14T19:55:34.627743593Z [azsb.Auth] negotiating claim for audience amqps://sbnamespace.servicebus.windows.net/dev-transactions/Subscriptions/application-stats-updater with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-11-14T19:55:34.629098809Z [azsb.Auth] Response router has shut down
2022-11-14T19:55:34.631457837Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater/$management) refreshing claim
2022-11-14T19:55:34.631467137Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater/$management) negotiate claim, token expires on 2022-11-14T20:10:34Z
2022-11-14T19:55:34.631472537Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater) next refresh in 4m59.986949447s
2022-11-14T19:55:34.715507625Z [azsb.Auth] negotiating claim for audience amqps://sbnamespace.servicebus.windows.net/dev-contracts/Subscriptions/application-stats-updater/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-11-14T19:55:34.719919977Z [azsb.Auth] Response router has shut down
2022-11-14T19:55:34.721674498Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater/$management) next refresh in 4m59.903576465s
2022-11-14T19:55:34.724219328Z [azsb.Auth] negotiating claim for audience amqps://sbnamespace.servicebus.windows.net/dev-transactions/Subscriptions/application-stats-updater/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-11-14T19:55:34.725572044Z [azsb.Auth] Response router has shut down
2022-11-14T19:55:34.728026173Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater/$management) next refresh in 4m59.903480965s
2022-11-14T19:55:34.728788682Z [azsb.Receiver] Asking for 30 credits
2022-11-14T19:55:34.728805582Z [azsb.Receiver] Only need to issue 30 additional credits
2022-11-14T19:55:34.750598338Z [azsb.Receiver] Received 1/30 messages
2022-11-14T19:55:34.750626138Z [azsb.Receiver] [IO6PMxVPsUwi9sMHsm42IPtZcG6m6-w4Rhdk_L9vN2qJe0wOVe1p6g] Message releaser starting...
2022-11-14T19:55:34.750644739Z Got 1 messages on topic dev-contracts
2022-11-14T19:55:35.516623049Z [azsb.Receiver] Asking for 30 credits
2022-11-14T19:55:35.516645249Z [azsb.Receiver] Only need to issue 30 additional credits
2022-11-14T19:55:35.538452906Z [azsb.Receiver] Received 1/30 messages
2022-11-14T19:55:35.538473306Z Got 1 messages on topic dev-transactions
2022-11-14T19:55:35.538923411Z [azsb.Receiver] [WjP7829vX8d_cAq0m5cN55EyEkdDuY73fpSyuvfS3--oq1acBuhaKw] Message releaser starting...
2022-11-14T19:55:37.079155430Z Receiving messages on topic dev-contracts
2022-11-14T19:55:37.079197130Z [azsb.Receiver] [IO6PMxVPsUwi9sMHsm42IPtZcG6m6-w4Rhdk_L9vN2qJe0wOVe1p6g] Message releaser pausing. Released 0 messages
2022-11-14T19:55:37.079202530Z [azsb.Receiver] Asking for 30 credits
2022-11-14T19:55:37.079207530Z [azsb.Receiver] Only need to issue 1 additional credits
2022-11-14T19:55:37.290571817Z Receiving messages on topic dev-transactions
2022-11-14T19:55:37.290603217Z [azsb.Receiver] [WjP7829vX8d_cAq0m5cN55EyEkdDuY73fpSyuvfS3--oq1acBuhaKw] Message releaser pausing. Released 0 messages
2022-11-14T19:55:37.290618517Z [azsb.Receiver] Asking for 30 credits
2022-11-14T19:55:37.290625217Z [azsb.Receiver] Only need to issue 1 additional credits
2022-11-14T20:00:34.619455398Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater) refreshing claim
2022-11-14T20:00:34.619483799Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater) negotiate claim, token expires on 2022-11-14T20:15:34Z
2022-11-14T20:00:34.619490899Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater) refreshing claim
2022-11-14T20:00:34.619510199Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater) negotiate claim, token expires on 2022-11-14T20:15:34Z
2022-11-14T20:00:34.621943229Z [azsb.Auth] negotiating claim for audience amqps://sbnamespace.servicebus.windows.net/dev-transactions/Subscriptions/application-stats-updater with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-11-14T20:00:34.623151545Z [azsb.Auth] Response router has shut down
2022-11-14T20:00:34.624880266Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater) next refresh in 4m59.994560932s
2022-11-14T20:00:34.625461673Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater/$management) refreshing claim
2022-11-14T20:00:34.625515074Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater/$management) negotiate claim, token expires on 2022-11-14T20:15:34Z
2022-11-14T20:00:34.627282196Z [azsb.Auth] negotiating claim for audience amqps://sbnamespace.servicebus.windows.net/dev-contracts/Subscriptions/application-stats-updater with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-11-14T20:00:34.628892116Z [azsb.Auth] Response router has shut down
2022-11-14T20:00:34.631028443Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater) next refresh in 4m59.988451256s
2022-11-14T20:00:34.631658151Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater/$management) refreshing claim
2022-11-14T20:00:34.631675151Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater/$management) negotiate claim, token expires on 2022-11-14T20:15:34Z
2022-11-14T20:00:34.633257971Z [azsb.Auth] negotiating claim for audience amqps://sbnamespace.servicebus.windows.net/dev-contracts/Subscriptions/application-stats-updater/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-11-14T20:00:34.634782490Z [azsb.Auth] Response router has shut down
2022-11-14T20:00:34.636364110Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater/$management) next refresh in 4m59.989217865s
2022-11-14T20:00:34.638186433Z [azsb.Auth] negotiating claim for audience amqps://sbnamespace.servicebus.windows.net/dev-transactions/Subscriptions/application-stats-updater/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-11-14T20:00:34.640503662Z [azsb.Auth] Response router has shut down
2022-11-14T20:00:34.642907192Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater/$management) next refresh in 4m59.988785959s
2022-11-14T20:00:37.079479432Z [azsb.Receiver] Received 0/30 messages
2022-11-14T20:00:37.079516833Z [azsb.Conn] Closing links for error link was idle, detaching (will be reattached).
2022-11-14T20:00:37.083200094Z [azsb.Receiver] Failure when receiving messages: link was idle, detaching (will be reattached).
2022-11-14T20:00:37.083227694Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater) refreshing claim
2022-11-14T20:00:37.083233194Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater) negotiate claim, token expires on 2022-11-14T20:15:37Z
2022-11-14T20:00:37.085731035Z [azsb.Auth] negotiating claim for audience amqps://sbnamespace.servicebus.windows.net/dev-contracts/Subscriptions/application-stats-updater with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-11-14T20:00:37.094265677Z [azsb.Auth] Response router has shut down
2022-11-14T20:00:37.096148008Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater/$management) refreshing claim
2022-11-14T20:00:37.096165608Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater) next refresh in 4m59.987051486s
2022-11-14T20:00:37.096169408Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater/$management) negotiate claim, token expires on 2022-11-14T20:15:37Z
2022-11-14T20:00:37.099141157Z [azsb.Auth] negotiating claim for audience amqps://sbnamespace.servicebus.windows.net/dev-contracts/Subscriptions/application-stats-updater/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-11-14T20:00:37.101176191Z [azsb.Auth] Response router has shut down
2022-11-14T20:00:37.102829618Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater/$management) next refresh in 4m59.99334629s
2022-11-14T20:00:37.118006669Z [azsb.Receiver] Asking for 30 credits
2022-11-14T20:00:37.118027070Z [azsb.Receiver] Only need to issue 30 additional credits
2022-11-14T20:00:37.291819145Z [azsb.Receiver] Received 0/30 messages
2022-11-14T20:00:37.291845146Z [azsb.Conn] Closing links for error link was idle, detaching (will be reattached).
2022-11-14T20:00:37.296741227Z [azsb.Receiver] Failure when receiving messages: link was idle, detaching (will be reattached).
2022-11-14T20:00:37.296759327Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater) refreshing claim
2022-11-14T20:00:37.296764327Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater) negotiate claim, token expires on 2022-11-14T20:15:37Z
2022-11-14T20:00:37.299083766Z [azsb.Auth] negotiating claim for audience amqps://sbnamespace.servicebus.windows.net/dev-transactions/Subscriptions/application-stats-updater with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-11-14T20:00:37.300625091Z [azsb.Auth] Response router has shut down
2022-11-14T20:00:37.302429221Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater/$management) refreshing claim
2022-11-14T20:00:37.302445421Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater) next refresh in 4m59.994398207s
2022-11-14T20:00:37.302450421Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater/$management) negotiate claim, token expires on 2022-11-14T20:15:37Z
2022-11-14T20:00:37.305674575Z [azsb.Auth] negotiating claim for audience amqps://sbnamespace.servicebus.windows.net/dev-transactions/Subscriptions/application-stats-updater/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-11-14T20:00:37.307123599Z [azsb.Auth] Response router has shut down
2022-11-14T20:00:37.316223649Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater/$management) next refresh in 4m59.986201672s
2022-11-14T20:00:37.322774058Z [azsb.Receiver] Asking for 30 credits
2022-11-14T20:00:37.322791258Z [azsb.Receiver] Only need to issue 30 additional credits
2022-11-14T20:05:37.083778854Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater) refreshing claim
2022-11-14T20:05:37.083812155Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater) negotiate claim, token expires on 2022-11-14T20:20:37Z
2022-11-14T20:05:37.087050450Z [azsb.Auth] negotiating claim for audience amqps://sbnamespace.servicebus.windows.net/dev-contracts/Subscriptions/application-stats-updater with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-11-14T20:05:37.088385589Z [azsb.Auth] Response router has shut down
2022-11-14T20:05:37.090447850Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater) next refresh in 4m59.993320303s
2022-11-14T20:05:37.096696834Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater/$management) refreshing claim
2022-11-14T20:05:37.096719735Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater/$management) negotiate claim, token expires on 2022-11-14T20:20:37Z
2022-11-14T20:05:37.099727323Z [azsb.Auth] negotiating claim for audience amqps://sbnamespace.servicebus.windows.net/dev-contracts/Subscriptions/application-stats-updater/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-11-14T20:05:37.104013950Z [azsb.Auth] Response router has shut down
2022-11-14T20:05:37.108285064Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater/$management) next refresh in 4m59.98842037s
2022-11-14T20:05:37.118538064Z [azsb.Receiver] Received 0/30 messages
2022-11-14T20:05:37.118570164Z [azsb.Conn] Closing links for error link was idle, detaching (will be reattached).
2022-11-14T20:05:37.122408539Z [azsb.Receiver] Failure when receiving messages: link was idle, detaching (will be reattached).
2022-11-14T20:05:37.122432640Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater) refreshing claim
2022-11-14T20:05:37.122450740Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater) negotiate claim, token expires on 2022-11-14T20:20:37Z
2022-11-14T20:05:37.124758485Z [azsb.Auth] negotiating claim for audience amqps://sbnamespace.servicebus.windows.net/dev-contracts/Subscriptions/application-stats-updater with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-11-14T20:05:37.126007009Z [azsb.Auth] Response router has shut down
2022-11-14T20:05:37.127617641Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater/$management) refreshing claim
2022-11-14T20:05:37.127631441Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater/$management) negotiate claim, token expires on 2022-11-14T20:20:37Z
2022-11-14T20:05:37.127636241Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater) next refresh in 4m59.994804598s
2022-11-14T20:05:37.129652380Z [azsb.Auth] negotiating claim for audience amqps://sbnamespace.servicebus.windows.net/dev-contracts/Subscriptions/application-stats-updater/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-11-14T20:05:37.130868304Z [azsb.Auth] Response router has shut down
2022-11-14T20:05:37.132863443Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater/$management) next refresh in 4m59.994803799s
2022-11-14T20:05:37.139431371Z [azsb.Receiver] Asking for 30 credits
2022-11-14T20:05:37.139450772Z [azsb.Receiver] Only need to issue 30 additional credits
2022-11-14T20:05:37.298426973Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater) refreshing claim
2022-11-14T20:05:37.298463074Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater) negotiate claim, token expires on 2022-11-14T20:20:37Z
2022-11-14T20:05:37.315459205Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater/$management) refreshing claim
2022-11-14T20:05:37.315512407Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater/$management) negotiate claim, token expires on 2022-11-14T20:20:37Z
2022-11-14T20:05:37.415752162Z [azsb.Receiver] Received 0/30 messages
2022-11-14T20:05:37.416593079Z [azsb.Conn] Closing links for error link was idle, detaching (will be reattached).
2022-11-14T20:05:37.417557797Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater) negotiate claim, failed: context canceled
2022-11-14T20:05:37.417579098Z [azsb.Auth] (NegotiateClaimRefresh) Retry attempt 0 was cancelled, stopping: context canceled
2022-11-14T20:05:37.417595798Z [azsb.Auth] [dev-transactions/Subscriptions/application-stats-updater] fatal error, stopping token refresh loop: context canceled
2022-11-14T20:05:37.417601798Z [azsb.Auth] (dev-transactions/Subscriptions/application-stats-updater/$management) negotiate claim, failed: context canceled
2022-11-14T20:05:37.417607798Z [azsb.Auth] (NegotiateClaimRefresh) Retry attempt 0 was cancelled, stopping: context canceled
2022-11-14T20:05:37.417610998Z [azsb.Auth] [dev-transactions/Subscriptions/application-stats-updater/$management] fatal error, stopping token refresh loop: context canceled
2022-11-14T20:10:37.123273938Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater) refreshing claim
2022-11-14T20:10:37.123296738Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater) negotiate claim, token expires on 2022-11-14T20:25:37Z
2022-11-14T20:10:37.128474519Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater/$management) refreshing claim
2022-11-14T20:10:37.128507619Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater/$management) negotiate claim, token expires on 2022-11-14T20:25:37Z
2022-11-14T20:10:37.139644792Z [azsb.Receiver] Received 0/30 messages
2022-11-14T20:10:37.139669292Z [azsb.Conn] Closing links for error link was idle, detaching (will be reattached).
2022-11-14T20:10:37.139677893Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater) negotiate claim, failed: context canceled
2022-11-14T20:10:37.139682393Z [azsb.Auth] (NegotiateClaimRefresh) Retry attempt 0 was cancelled, stopping: context canceled
2022-11-14T20:10:37.139686493Z [azsb.Auth] [dev-contracts/Subscriptions/application-stats-updater] fatal error, stopping token refresh loop: context canceled
2022-11-14T20:10:37.139703693Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater/$management) negotiate claim, failed: context canceled
2022-11-14T20:10:37.139708293Z [azsb.Auth] (NegotiateClaimRefresh) Retry attempt 0 was cancelled, stopping: context canceled
2022-11-14T20:10:37.139711493Z [azsb.Auth] [dev-contracts/Subscriptions/application-stats-updater/$management] fatal error, stopping token refresh loop: context canceled

As I said, not all services are being affected, even though they are running the absolute same code, just using different subscription names/topics. This seems to be happening randomly, sometimes it stops just after 10 minutes, sometimes it takes 30 minutes...
This is happening on the latest version but I was having a similar bug to #18517 where services just stopped consuming after running for days on the previous version.
I'm available for more clarifications or tests if needed.
The code I'm running is similar to this:
func main() {
	client, err := azservicebus.NewClientFromConnectionString(connStr, nil)
	if err != nil {
		fmt.Println("Error", err)
		os.Exit(1)
	}

	rcv, err := client.NewReceiverForSubscription(context.TODO(), "test.sessionqueue", nil)
	for {
		messages, err := rcv.ReceiveMessages(context.TODO(), 1, nil)
		if err != nil {
			break
		}

		processMessages(messages)
	}
}

There isn't any example on how to create a service that acts as a daemon service, I mean, that just keeps on receiving messages. Is this correct way? Is it possible to include an example for that?

Hi @SpaWn2KiLl, taking a look at this. We added in a client-side idle check, which is why you see more link recreation.
From the log it looks like we're still hitting a period of time where no messages are coming in, despite having recreated and readded credits to the link.
From the log:
> 2022-11-14T19:55:34.728788682Z [azsb.Receiver] Asking for 30 credits
> 2022-11-14T19:55:34.728805582Z [azsb.Receiver] Only need to issue 30 additional credits
> 2022-11-14T19:55:34.750598338Z [azsb.Receiver] Received 1/30 messages

Things are working properly here, we only got 1 message but that's expected (I assume)
> 2022-11-14T19:55:37.290618517Z [azsb.Receiver] Asking for 30 credits
> 2022-11-14T19:55:37.290625217Z [azsb.Receiver] Only need to issue 1 additional credits
> 2022-11-14T20:00:37.079479432Z [azsb.Receiver] Received 0/30 messages
> 2022-11-14T20:00:37.079516833Z [azsb.Conn] Closing links for error link was idle, detaching (will be reattached).

Here's our first failure. ~19:55 is when we first asked for new messages and at ~20:00 our client-side idle timer fired off and closed the link due to idleness. This is a new feature, prior to this we wouldn't do anything until the service actually told us the link was timed out. We consider a link idle if no messages have arrived within 5 minutes.
From that point out we never seem to get any actual messages, but we do idle out and recreate the link several times. Here we start at 20:00:37, and (again) idle out at 20:05:37:
> 2022-11-14T20:00:37.322774058Z [azsb.Receiver] Asking for 30 credits
> 2022-11-14T20:00:37.322791258Z [azsb.Receiver] Only need to issue 30 additional credits
> 2022-11-14T20:05:37.118538064Z [azsb.Receiver] Received 0/30 messages
> 2022-11-14T20:05:37.118570164Z [azsb.Conn] Closing links for error link was idle, detaching (will be reattached).

This would seem to indicate there aren't any messages for that subscription but if there are messages there's no indicator on the client side - we haven't received anything.
I'm going to add the service team to this issue, to see if there's something I'm doing wrong in the client library or if there is something interesting on the service side. They should pop onto this issue after I add the appropriate label.
These are the cancellations below:
> 2022-11-14T20:10:37.139677893Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater) negotiate claim, failed: context canceled
> 2022-11-14T20:10:37.139682393Z [azsb.Auth] (NegotiateClaimRefresh) Retry attempt 0 was cancelled, stopping: context canceled
> 2022-11-14T20:10:37.139686493Z [azsb.Auth] [dev-contracts/Subscriptions/application-stats-updater] fatal error, stopping token refresh loop: context canceled
> 2022-11-14T20:10:37.139703693Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater/$management) negotiate claim, failed: context canceled
> 2022-11-14T20:10:37.139708293Z [azsb.Auth] (NegotiateClaimRefresh) Retry attempt 0 was cancelled, stopping: context canceled
> 2022-11-14T20:10:37.139711493Z [azsb.Auth] [dev-contracts/Subscriptions/application-stats-updater/$management] fatal error, stopping token refresh loop: context canceled

These should only happen if the user (ie, you) cancels the context passed to ReceiveMessages(). Was that the case? In the example you posted you're passing context.TODO, but I was curious if you do pass a real context there and if that cancels in some other part of your application.

There isn't any example on how to create a service that acts as a daemon service, I mean, that just keeps on receiving messages. Is this correct way? Is it possible to include an example for that?

What you have is basically it - you just loop continually, and block on ReceiveMessages(), letting it alert you when there are messages. If that's what you have in your app, that's all that's required. We only return if there's something useful (ie, a fatal error or actual messages).

Hello @richardpark-msft

These should only happen if the user (ie, you) cancels the context passed to ReceiveMessages(). Was that the case? In the example you posted you're passing context.TODO, but I was curious if you do pass a real context there and if that cancels in some other part of your application.

I added a log on the only specific scenario where the context being passed to ReceiveMessages() method call could be closed, and it was not showing up on the log dump I put here on the issue. This means I'm like 99% sure that the context I'm passing is not being closed on my end.
From what I understand, considering the SDK's logs, the "context canceled" error is being thrown here, but that context is being created here using a context.Background() as a parent. Then I'm not very sure in which scenarios can cancelRefreshCtx be called... Are you sure the only way to cancel refreshCtx is by canceling the context being passed to ReceiveMessages() method?

From what I understand, considering the SDK's logs, the "context canceled" error is being thrown here, but that context is being created here using a context.Background() as a parent. Then I'm not very sure in which scenarios can cancelRefreshCtx be called... Are you sure the only way to cancel refreshCtx is by canceling the context being passed to ReceiveMessages() method?

Let me check again, might be another path, just seemed the most likely one.

@SpaWn2KiLl, ah, you were right on the context:

2022-11-14T20:10:37.139669292Z [azsb.Conn] Closing links for error link was idle, detaching (will be reattached).
2022-11-14T20:10:37.139677893Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater) negotiate claim, failed: context canceled
2022-11-14T20:10:37.139682393Z [azsb.Auth] (NegotiateClaimRefresh) Retry attempt 0 was cancelled, stopping: context canceled

The refresh loop is being cancelled because of the first line - we're closing the old links out and one of the steps in there is to cancel the credential refresh loop for the previous link. This would be expected since we're closing out the old connection in favor of a new one. It's a bit of a timing issue if you see this or not - we'd have to be right in the middle of doing a negotiate claim but it's okay if it happens.
Do you see any more log messages after that indicating that we're recreating the link? You'd typically see more of these kinds of messages afterwards:

2022-11-14T20:05:37.122432640Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater) refreshing claim
2022-11-14T20:05:37.122450740Z [azsb.Auth] (dev-contracts/Subscriptions/application-stats-updater) negotiate claim, token expires on 2022-11-14T20:20:37Z
? 2022-11-14T20:05:37.124758485Z [azsb.Auth] negotiating claim for audience amqps://sbnamespace.servicebus.windows.net/dev-contracts/Subscriptions/application-stats-updater with token type servicebus.windows.net:sastoken and expiry of

Do you see any more log messages after that indicating that we're recreating the link?

No. The service is still running (it's been running for 25 hours now), still not consuming, and no more logs. Didn't restart the service since it is on a development environment and not a critical one.

Hi @SpaWn2KiLl, after looking at this more I think my keep-alive fix (combined with another fix to avoid cancellation on close) is just creating too many issues. I've rolled this back and released 1.1.3.

Hello @richardpark-msft. Thanks for your attention on this issue.
 Do you have any update about it?

Hi @SpaWn2KiLl, I'm starting to write out some tests and think about how to fix this one, but I don't have anything immediate. The rollback "addresses" this bug, at least, but the main issue where the receiver appears to hang is still something I'm working through.

Hi @hilariocoelho , sorry for going so silent on this. I believe we've made a few fixes that should help in this arena in the latest release: link
In particular:

go-amqp handles cancellation better - there were a few areas where it was possible to deadlock or put the library into an unstable state.
We added in some internal timeouts in case the network stack goes out to lunch, or if we get a large delay from the service responding to us when closing links.
There wase a service side bug that was fixed where you could ask for messages but not receive them, even if messages were available.

If you can, please try out the new release and let me know if you continue to see issues.


Typo error in Readme

in the bulk transfer sample "account_numberr" was used instead of "account_number"

Hello @Daemonicc 👋🏽,
Thank you for catching that. The typo has been corrected and the full ReadMe is undergoing an extensive review.
We would notify you and other members of our community as soon as this review is completed.
Please let us know how else we can improve your experience with the SDK.
You can join our Slack channel for more updates from the Engineering team.


bug: wrong event emit when lock

Plugin version:
1.1.4
Platform(s):
ios
Current behavior:
when listen to screenOrientationChange and then lock in landscape, i receive portrait-primary
Expected behavior:
when locking, i should receive the orientation locked
Steps to reproduce:
use the code below in your app to see it happen

Related code:
      ScreenOrientation.addListener('screenOrientationChange', async (res) => {
        const current = await ScreenOrientation.getCurrentOrientation()
        console.log('orientation', current, res)
      })
     ScreenOrientation.lock({ type: OrientationType.LANDSCAPE })

Other information:
Capacitor doctor:

💊   Capacitor Doctor  💊

Latest Dependencies:

  @capacitor/cli: 3.4.3
  @capacitor/core: 3.4.3
  @capacitor/android: 3.4.3
  @capacitor/ios: 3.4.3

Installed Dependencies:

  @capacitor/core: 3.4.3
  @capacitor/android: 3.4.3
  @capacitor/cli: 3.4.3
  @capacitor/ios: 3.4.3

[success] iOS looking great! 👌
[success] Android looking great! 👌

I was able to reproduce it. I will publish a fix.

@robingenz your reactivity is wonderful!
We should create an GitHub org with the best contributor like you and do open collective to pay the best contributor.
That something needed in the ecosystem to me, now the community plugin is failing is job and make the tech look week by the lack of reactivity...
i understand it, it needs a real tangible incentive to me

@robingenz thanks for the fix i tried today and seems the listener send the good value but not the function who get .

The codes who do this logging
      ScreenOrientation.addListener('screenOrientationChange', async (res) => {
        const current = await ScreenOrientation.getCurrentOrientation()
        console.log('orientation', current, res)
      })

@robingenz your reactivity is wonderful! We should create an GitHub org with the best contributor like you and do open collective to pay the best contributor. That something needed in the ecosystem to me, now the community plugin is failing is job and make the tech look week by the lack of reactivity... i understand it, it needs a real tangible incentive to me

Thank you for your kind words. I'll have to think about that. I have never come up with this idea. 😄
Okay, i will have a look again.

@riderx You can give it a try:
npm i<EMAIL_ADDRESS>

@robingenz i do it now !
What tool do you use to generate the version number ?

something is missing ^^

@robingenz oh ok thanks !
i will check then

@robingenz still getting the issue :/
at least i was able to release with the result of the listener screenOrientationChange but that weird getCurrentOrientation  still return the wrong one

Thanks for testing.
I will have my Mac back on Monday. Then I can test it myself and find a fix.

Okay, i fixed and tested it:
npm i<EMAIL_ADDRESS>
Does it work as you expect?


Add souvikrajsingh

thank you for this!
Made the necessary changes as asked in the README.md

i did make changes in the index.html please review my Commit! thank you!


pylance highlight doesn't work on *.ipynb file

Language Server version: 2020.9.0
OS and version: Windows 10
Python version (& distribution if applicable, e.g. Anaconda): python 3.8.3

Code highlight in .ipynb not work
this is highlight in .py file

this is highlight in .ipynb file

import numpy as np
import matplotlib.pyplot as plt

N = 50
x = np.random.rand(N)
y = np.random.rand(N)
c = np.random.rand(N)
s = np.pi*(np.random.rand(N) * 20) ** 2
plt.scatter(x, y, c=c, s=s, alpha=0.5)
plt.plot()

Thanks for the issue. This is something that requires the new notebook API that VS code is working on:
https://github.com/microsoft/vscode/issues/91987
Once that's complete, pylance will likely have to be updated to understand notebooks.


Fixed ViewShadow always disabled when configuring it manually

Fixed ViewShadow always disabled when configuring manually. Issue #43

Thank you :-)


Android Ad error: AdError 402: VAST media file loading reached a timeout of 15 seconds.

I am using video-js-5.4.6, videojs-ima-master-5.3, and videojs-contrib-ads-master-3.1.2. I'm having a problem on Sony Xperia Z2 (D6503) Android 5.1 and the Chrome 47.0.2526.83 and the adTagUrl: 'http://scads.starsite.com/www/delivery/fc.php?script=apVideo:vast2&zoneid=4' and I am getting the following error: Failed to execute 'play' on 'HTMLMediaElement': API can only be initiated by a user gesture. Ad error: AdError 402: VAST media file loading reached a timeout of 15 seconds. The ad window will appear with the ad text, but there will be no video or audio.
The video ads will play in Safari, Chrome, Firefox, and iPhone. The problem is when I am attempting to run this on Android.
Note: The advanced example will not work for me on the same device. I cannot play the video.

We've been having trouble lately with the standard samples on Android - can you try your tag in the iPhone sample? That works for me testing on a Nexus 5x. Thanks!

My video advertisements work under the iPhone example. I think I'm getting somewhere now. Thank you!

Was able to correct the video advertisements not loading, due to the first Android tap event not being captured. Implemented the jQuery mobile library to capture the tap event, and then called the initializeAdDisplayContainer function.


maxMines -10 instead of -9

If the number of black holes in a custom game is greater than the number of all fields minus 9, you win each game directly  -> change maxMines =_width*_height-10;

Closing this because auto-win is intended. thanks for the report!


exception when migrating pkg/vm_snapshot_analysis

$ cd pkg/vm_snapshot_analysis
$ dart pub upgrade
$ dart pub outdated --mode=null-safety
Showing dependencies that are currently not opted in to null-safety.
[✗] indicates versions without null safety support.
[✓] indicates versions opting in to null safety.

All your dependencies declare support for null-safety.
$ dart migrate
Migrating /Users/vegorov/src/dart/sdk/pkg/vm_snapshot_analysis

See https://dart.dev/go/null-safety-migration for a migration guide.

Analyzing project...
[-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------/]No analysis issues found.

Generating migration suggestions...
[-------------------------------------------------------------------------------------------------------|                                                                                ]Aborting migration due to an exception.  This most likely is due to a
bug in the migration tool.  Please consider filing a bug report at:

https://github.com/dart-lang/sdk/issues/new
Please include the SDK version (2.12.0) in your bug report.

To attempt to perform migration anyway, you may re-run with
--ignore-exceptions.

Exception details:

Never.substitute(Never | {T: void?(type argument 0 of supertype of CompareCommand (compare.dart:21:38))}) at offset 2583 in /Users/vegorov/src/dart/sdk/pkg/vm_snapshot_analysis/lib/src/commands/compare.dart (usageException('Need to provide path to old.json and new.json reports.'))

#0      DecoratedType._substitute (package:nnbd_migration/src/decorated_type.dart:467:5)
#1      DecoratedType._substituteFunctionAfterFormals (package:nnbd_migration/src/decorated_type.dart:495:24)
#2      DecoratedType._substitute (package:nnbd_migration/src/decorated_type.dart:446:14)
#3      DecoratedType.substitute (package:nnbd_migration/src/decorated_type.dart:327:12)
#4      EdgeBuilder.getOrComputeElementType (package:nnbd_migration/src/edge_builder.dart:304:32)
#5      EdgeBuilder.visitMethodInvocation (package:nnbd_migration/src/edge_builder.dart:1284:20)
#6      MethodInvocationImpl.accept (package:analyzer/src/dart/ast/ast.dart:7186:49)
#7      EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2207:24)
#8      EdgeBuilder.visitExpressionStatement (package:nnbd_migration/src/edge_builder.dart:801:25)
#9      ExpressionStatementImpl.accept (package:analyzer/src/dart/ast/ast.dart:3676:49)
#10     EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2207:24)
#11     EdgeBuilder.visitNode (package:nnbd_migration/src/edge_builder.dart:1340:9)
#12     GeneralizingAstVisitor.visitStatement (package:analyzer/dart/ast/visitor.dart:517:39)
#13     GeneralizingAstVisitor.visitBlock (package:analyzer/dart/ast/visitor.dart:165:31)
#14     BlockImpl.accept (package:analyzer/src/dart/ast/ast.dart:1083:49)
#15     EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2207:24)
#16     EdgeBuilder.visitIfStatement.<anonymous closure> (package:nnbd_migration/src/edge_builder.dart:1037:25)
#17     ScopedSet.doScoped (package:nnbd_migration/src/utilities/scoped_set.dart:44:13)
#18     EdgeBuilder.visitIfStatement (package:nnbd_migration/src/edge_builder.dart:1036:28)
#19     IfStatementImpl.accept (package:analyzer/src/dart/ast/ast.dart:5705:49)
#20     EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2207:24)
#21     EdgeBuilder.visitNode (package:nnbd_migration/src/edge_builder.dart:1340:9)
#22     GeneralizingAstVisitor.visitStatement (package:analyzer/dart/ast/visitor.dart:517:39)
#23     GeneralizingAstVisitor.visitBlock (package:analyzer/dart/ast/visitor.dart:165:31)
#24     BlockImpl.accept (package:analyzer/src/dart/ast/ast.dart:1083:49)
#25     EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2207:24)
#26     EdgeBuilder.visitNode (package:nnbd_migration/src/edge_builder.dart:1340:9)
#27     GeneralizingAstVisitor.visitFunctionBody (package:analyzer/dart/ast/visitor.dart:324:45)
#28     GeneralizingAstVisitor.visitBlockFunctionBody (package:analyzer/dart/ast/visitor.dart:168:55)
#29     BlockFunctionBodyImpl.accept (package:analyzer/src/dart/ast/ast.dart:1038:49)
#30     EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2207:24)
#31     EdgeBuilder._handleExecutableDeclaration (package:nnbd_migration/src/edge_builder.dart:2488:7)
#32     EdgeBuilder.visitMethodDeclaration (package:nnbd_migration/src/edge_builder.dart:1243:5)
#33     MethodDeclarationImpl.accept (package:analyzer/src/dart/ast/ast.dart:7033:49)
#34     EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2207:24)
#35     EdgeBuilder._dispatchList (package:nnbd_migration/src/edge_builder.dart:2229:7)
#36     EdgeBuilder.visitClassOrMixinOrExtensionDeclaration (package:nnbd_migration/src/edge_builder.dart:607:7)
#37     EdgeBuilder.visitClassDeclaration (package:nnbd_migration/src/edge_builder.dart:574:5)
#38     ClassDeclarationImpl.accept (package:analyzer/src/dart/ast/ast.dart:1536:49)
#39     EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2207:24)
#40     EdgeBuilder.visitNode (package:nnbd_migration/src/edge_builder.dart:1340:9)
#41     GeneralizingAstVisitor.visitCompilationUnit (package:analyzer/dart/ast/visitor.dart:202:51)
#42     CompletenessTracker.visitCompilationUnit.<anonymous closure> (package:nnbd_migration/src/utilities/completeness_tracker.dart:52:24)
#43     PermissiveModeVisitor.reportExceptionsIfPermissive (package:nnbd_migration/src/utilities/permissive_mode.dart:26:24)
#44     CompletenessTracker.visitCompilationUnit (package:nnbd_migration/src/utilities/completeness_tracker.dart:43:5)
#45     CompilationUnitImpl.accept (package:analyzer/src/dart/ast/ast.dart:2134:49)
#46     NullabilityMigrationImpl.processInput (package:nnbd_migration/src/nullability_migration_impl.dart:244:12)
#47     NonNullableFix.processUnit (package:nnbd_migration/src/front_end/non_nullable_fix.dart:164:15)
#48     _FixCodeProcessor.runLaterPhases.<anonymous closure> (package:nnbd_migration/migration_cli.dart:1154:19)
#49     _FixCodeProcessor.runLaterPhases.<anonymous closure> (package:nnbd_migration/migration_cli.dart:1152:28)
#50     _FixCodeProcessor.processResources (package:nnbd_migration/migration_cli.dart:1081:30)
<asynchronous suspension>
#51     _FixCodeProcessor.runLaterPhases (package:nnbd_migration/migration_cli.dart:1152:5)
<asynchronous suspension>
#52     MigrationCliRunner.run (package:nnbd_migration/migration_cli.dart:749:24)
<asynchronous suspension>
#53     MigrateCommand.run (package:nnbd_migration/migration_cli.dart:185:7)
<asynchronous suspension>
#54     CommandRunner.runCommand (package:args/command_runner.dart:196:13)
<asynchronous suspension>
#55     DartdevRunner.runCommand (package:dartdev/dartdev.dart:199:18)
<asynchronous suspension>
#56     runDartdev (package:dartdev/dartdev.dart:53:16)
<asynchronous suspension>
#57     main (file:///b/s/w/ir/cache/builder/sdk/pkg/dartdev/bin/dartdev.dart:11:3)
<asynchronous suspension>

Thanks for the bug report @mraleph!  Were you able to make progress with the migration by re-running with --ignore-exceptions?

I just migrated manually

I just migrated manually

Ok, thanks.

As of 1c7fe7196dd7a542f7f91cd6ea2ac81e1a13146c, the null safety migration tool has been removed from active development and retired. No further work on the tool is planned.
If you still need help, or you believe this issue has been closed in error, please feel free to reopen.


User can create user and set role even when not having edit roles permissions

Version information

Laravel: v8.0
Voyager: v1.4
PHP: 7.3
Database: [type] [version] (e.g. MySQL 8.0)

Description
User can create user and set role even when not having edit roles permissions
in views/users/edit-add.blade.php
line 64 should be
@can('edit', app('TCG\Voyager\Models\Role'))
instead of
@can('editRoles', $dataTypeContent)

editRoles is a custom policy stricter than edit_roles so that you cannot change your own role even if you can edit other users and change their roles, I never liked it but that's how it is.
Permission to edit roles has nothing to do with the permission of editing users or adding users.
Permission to edit roles means that you can change permissions for roles or change the name of the role.
If you want it to behave in a different way you can create a custom policy and override editRoles method.


[Docs] SQL Developer Guide

Background: https://airtable.com/tblD3oZPLJgGhCmch/viw1DKmbKhg2MIECH/rec3BeYWPmj5yce1x
Description: The docs section now includes a SQL Developer Guide that pulls out content on creating and updating data and other high-level topics with SQL development.
The reference section now only contains reference information.
Currently, the docs section is organized around SQL reference material. However, a lot of the material isn't really reference material. Instead, it is part of a SQL developer guide that could be lost as it is interleaved with reference material.
Team: Andrew Woods, Rafi Shamim, Richard Loveland
Github Tracking Issue:

Closing in favor of https://github.com/cockroachdb/docs/issues/5865.


Fix font size consistency initial

First step to address #527. Submitting PR against master so you can see changes, but as per @Golodhros may want to redo this against an RC branch.
Description

Tweaked line chart demo to show a yAxisLabel
Added getFontSize method to textHelpers
For line, stacked-area, mini-tooltip, and legend

Added font-size scss declarations
Removed font sizing from chart files
Tweaked sizing methodologies where appropriate to dynamically adjust for font size

Motivation and Context
#527.
How Has This Been Tested?

Added new test for font size getter
All tests passed
Visually inspected all charts confirming no unanticipated styling changes

Types of changes

[x] Refactor (changes the way we code something without changing its functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have read the CONTRIBUTING document.
[x] My code follows the code style guide of this project.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Thanks a lot @bratter!!
This is good to go!
I won't merge it into master though. I will try to figure out how to manage an RC branch with github, as this is something we haven't done yet. Then I will merge it into that RC branch.
Thanks a lot for this work, it is an improvement in consistency that was really needed!

Cool. When I get a chance over the next few weeks I may continue on pulling out duplicate code and extending the changes to the other chart types.

Great work! Thanks

Merged into release/3.0.0-rc1
Thanks a lot!


Removed unused resources

Resolved / Related Issues
Items resolved / related issues by this PR.

Closes #issue...
Related #issue...

Details of Changes
Add details of changes here.

Added...
Fixed...

Validation
How did you test these changes?

[x] Built and ran the app
[x] Tested the changes for accessibility

Screenshots (optional)
Add screenshots here.

Is it ok?


Create createSelected function

Pull Request Test Coverage Report for Build 72

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 82.27%

Totals

Change from base Build 71:
0.04%

Covered Lines:
239

Relevant Lines:
274

💛  - Coveralls


Trouble with electron-forge make while electron-forge start works

Hello,
I have been trying to convert an R Shiny app into an electron app for Mac. I tried using the instructions with R 4.1.0 in Mojave (10.14).
I stuck with npm 6.13.7 and node 13.9.0. I have installed, and unpacked the R folder using the get-r-mac.sh script (with minor edits to refer to the right files) and installed all the dependency R packages.
When I try electron-forge start, the app starts and works file. But, when I try to package it, I get the error
An unhandled rejection has occurred inside Forge:
ENOENT: no such file or directory, stat '/Users/mojave/.../r-mac/R.framework/Versions/4.1/R'
Error: ENOENT: no such file or directory, stat '/Users/mojave/.../r-mac/R.framework/Versions/4.1/R'

package.json
{
  "name": "ryabhatta",
  "productName": "ryabhatta",
  "version": "1.0.0",
  "description": "My Electron application description",
  "main": "src/index.js",
  "scripts": {
    "start": "electron-forge start",
    "package": "electron-forge package",
    "make": "electron-forge make",
    "publish": "electron-forge publish",
    "lint": "eslint src --color"
  },
  "keywords": [],
  "author": "mojave",
  "license": "MIT",
  "config": {
    "forge": {
      "packagerConfig": {},
      "makers": [
        {
          "name": "@electron-forge/maker-squirrel",
          "config": {
            "name": "ryabhatta"
          }
        },
        {
          "name": "@electron-forge/maker-zip",
          "platforms": [
            "darwin"
          ]
        },
        {
          "name": "@electron-forge/maker-deb",
          "config": {}
        },
        {
          "name": "@electron-forge/maker-rpm",
          "config": {}
        }
      ]
    }
  },
  "dependencies": {
    "axios": "^0.21.4",
    "electron-squirrel-startup": "^1.0.0",
    "esm": "^3.2.25",
    "execa": "^5.1.1"
  },
  "devDependencies": {
    "@babel/core": "^7.15.5",
    "@babel/plugin-transform-async-to-generator": "^7.14.5",
    "@babel/preset-env": "^7.15.6",
    "@babel/preset-react": "^7.14.5",
    "@electron-forge/cli": "^6.0.0-beta.61",
    "@electron-forge/maker-deb": "^6.0.0-beta.61",
    "@electron-forge/maker-rpm": "^6.0.0-beta.61",
    "@electron-forge/maker-squirrel": "^6.0.0-beta.61",
    "@electron-forge/maker-zip": "^6.0.0-beta.61",
    "electron": "14.0.1",
    "eslint": "^7.32.0",
    "eslint-config-airbnb": "^18.2.1",
    "eslint-plugin-import": "^2.24.2",
    "eslint-plugin-jsx-a11y": "^6.4.1",
    "eslint-plugin-react": "^7.25.1",
    "eslint-plugin-react-hooks": "^4.2.0",
    "fs-extra": "^10.0.0"
  }
}

Hi @SathiyaNManivannan, thank you for creating an issue in this repo! Unfortunately, I no longer have access to a Mac and cannot troubleshoot this issue for you. My apologies.

Thanks for responding @lawalter! With some changes to the packages.json, main.js and RScript, I was able to make the app. I will close this issue to keep things tidy for you.


[Change request to #51] Home page Who we are block

Home page Who we are block#51
Updated user story with corrections
As a Guest I want to see the fourth “Who we are” block (screen) of the home page and a footer so that I can find out the general information about Space2Study platform.
Acceptance criteria:
1.When a Guest scrolls down the home page, then he/she can see the fourth homepage bloc.
Mockup:

2.The “Who we are” home page bloc contains:

The title text “Who we are”
The description text “SpaceToStudy platform is a place where experts share their knowledge and students can learn from the best. Here you can find the proper training course, find a tutor, or find a student. SpaceToStude doesn’t receive any commission for classes between a tutor and a student, that’s why education with us becomes even closer and more financially available.”
video content

Replace the mockup.