I cannot initialize a new vm with ansible installed via git as normal user (with root it works).

Issue Type

Bug Report / Support Request

Your Environment
Vagrant 2.0.2
VirtualBox 5.1.30_Ubuntur118389
ansible 2.4.4 (stable-2.4 92cea82a4e) last updated 2018/02/28 20:16:43 (GMT +200)
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/home/david/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /opt/ansible/lib/ansible
  executable location = /opt/ansible/bin/ansible
  python version = 2.7.14 (default, Sep 23 2017, 22:06:14) [GCC 7.2.0]

Your OS

Linux (Ubuntu 17.10)

Full console output
vagrant up --debug
 INFO global: Vagrant version: 1.9.8
 INFO global: Ruby version: 2.3.4
 INFO global: RubyGems version: 2.5.2
 INFO global: VAGRANT_OLD_ENV_XDG_SESSION_DESKTOP="KDE"
 INFO global: VAGRANT_OLD_ENV_SHELL="/bin/bash"
 INFO global: VAGRANT_OLD_ENV_WINDOWID="83886086"
 INFO global: VAGRANT_OLD_ENV_PATH="/opt/ansible/bin:/opt/ansible/test/runner:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin"
 INFO global: VAGRANT_OLD_ENV_LC_TIME="es_ES.UTF-8"
 INFO global: VAGRANT_EXECUTABLE="/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/bin/vagrant"
 INFO global: VAGRANT_OLD_ENV_DISPLAY=":0"
 INFO global: VAGRANT_OLD_ENV_LC_ADDRESS="es_ES.UTF-8"
 INFO global: VAGRANT_OLD_ENV_SESSION_MANAGER="local/bree:@/tmp/.ICE-unix/1794,unix/bree:/tmp/.ICE-unix/1794"
 INFO global: VAGRANT_OLD_ENV_OLDPWD="/home/david/vagrant/blt-test/blt"
 INFO global: VAGRANT_OLD_ENV_MANPATH="/opt/ansible/docs/man:"
 INFO global: VAGRANT_OLD_ENV_LC_IDENTIFICATION="es_ES.UTF-8"
 INFO global: VAGRANT_OLD_ENV_MANDATORY_PATH="/usr/share/gconf//usr/share/xsessions/plasma.mandatory.path"
 INFO global: VAGRANT_OLD_ENV_USER="david"
 INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/opt/vagrant/embedded"
 INFO global: VAGRANT_OLD_ENV_LANG="en_US.UTF-8"
 INFO global: VAGRANT_OLD_ENV_SSH_AUTH_SOCK="/tmp/ssh-sHJL627f3bcu/agent.1660"
 INFO global: VAGRANT_OLD_ENV_DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-Eyp7JhvAO9,guid=510a69e100b2d57befefb29f5aa0e25f"
 INFO global: VAGRANT_OLD_ENV_QT_QUICK_CONTROLS_STYLE="org.kde.desktop"
 INFO global: VAGRANT_OLD_ENV_KONSOLE_PROFILE_NAME="Profile 1"
 INFO global: VAGRANT_OLD_ENV_LC_MEASUREMENT="es_ES.UTF-8"
 INFO global: VAGRANT_OLD_ENV_LANGUAGE=""
 INFO global: VAGRANT_OLD_ENV_XDG_CONFIG_DIRS="/etc/xdg/xdg-/usr/share/xsessions/plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings"
 INFO global: VAGRANT_OLD_ENV_LC_PAPER="es_ES.UTF-8"
 INFO global: VAGRANT_OLD_ENV_ANSIBLE_HOME="/opt/ansible"
 INFO global: VAGRANT_OLD_ENV_PYTHONPATH="/opt/ansible/lib:"
 INFO global: VAGRANT_OLD_ENV_KONSOLE_DBUS_SESSION="/Sessions/9"
 INFO global: VAGRANT_INSTALLER_VERSION="2"
 INFO global: VAGRANT_OLD_ENV_DESKTOP_SESSION="/usr/share/xsessions/plasma"
 INFO global: VAGRANT_OLD_ENV_LC_MONETARY="es_ES.UTF-8"
 INFO global: VAGRANT_OLD_ENV_LC_NUMERIC="es_ES.UTF-8"
 INFO global: VAGRANT_OLD_ENV_XDG_CURRENT_DESKTOP="KDE"
 INFO global: VAGRANT_OLD_ENV_XDG_RUNTIME_DIR="/run/user/1000"
 INFO global: VAGRANT_OLD_ENV_PWD="/home/david/vagrant/blt-test"
 INFO global: VAGRANT_OLD_ENV_XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0"
 INFO global: VAGRANT_OLD_ENV_XDG_DATA_DIRS="/usr/share//usr/share/xsessions/plasma:/usr/local/share:/usr/share:/var/lib/snapd/desktop"
 INFO global: VAGRANT_OLD_ENV_XDG_SESSION_CLASS="user"
 INFO global: VAGRANT_OLD_ENV_XDG_SESSION_PATH="/org/freedesktop/DisplayManager/Session1"
 INFO global: VAGRANT_OLD_ENV_KDE_SESSION_UID="1000"
 INFO global: VAGRANT_OLD_ENV_LS_COLORS="rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:"
 INFO global: VAGRANT_OLD_ENV_LC_NAME="es_ES.UTF-8"
 INFO global: VAGRANT_OLD_ENV_QT_AUTO_SCREEN_SCALE_FACTOR="0"
 INFO global: VAGRANT_OLD_ENV_KDE_FULL_SESSION="true"
 INFO global: VAGRANT_OLD_ENV_SHELL_SESSION_ID="46c76dc985594c05a5f8148117d87df5"
 INFO global: VAGRANT_OLD_ENV_XDG_VTNR="7"
 INFO global: VAGRANT_OLD_ENV__="/opt/vagrant/bin/vagrant"
 INFO global: VAGRANT_OLD_ENV_PROFILEHOME=""
 INFO global: VAGRANT_OLD_ENV_SSH_AGENT_PID="1735"
 INFO global: VAGRANT_OLD_ENV_TERM="xterm-256color"
 INFO global: VAGRANT_OLD_ENV_COLORFGBG="15;0"
 INFO global: VAGRANT_INSTALLER_ENV="1"
 INFO global: VAGRANT_OLD_ENV_GS_LIB="/home/david/.fonts"
 INFO global: VAGRANT_OLD_ENV_DEFAULTS_PATH="/usr/share/gconf//usr/share/xsessions/plasma.default.path"
 INFO global: VAGRANT_OLD_ENV_HOME="/home/david"
 INFO global: VAGRANT_OLD_ENV_XDG_SESSION_TYPE="x11"
 INFO global: VAGRANT_OLD_ENV_KONSOLE_DBUS_WINDOW="/Windows/1"
 INFO global: VAGRANT_OLD_ENV_KONSOLE_DBUS_SERVICE=":1.64"
 INFO global: VAGRANT_OLD_ENV_COLORTERM="truecolor"
 INFO global: VAGRANT_OLD_ENV_PAM_KWALLET5_LOGIN="/run/user/1000/kwallet5.socket"
 INFO global: VAGRANT_OLD_ENV_XAUTHORITY="/home/david/.Xauthority"
 INFO global: VAGRANT_OLD_ENV_SHLVL="2"
 INFO global: VAGRANT_OLD_ENV_XDG_SEAT="seat0"
 INFO global: VAGRANT_OLD_ENV_PAM_KWALLET_LOGIN="/run/user/1000/kwallet.socket"
 INFO global: VAGRANT_OLD_ENV_XCURSOR_THEME="breeze_cursors"
 INFO global: VAGRANT_OLD_ENV_LC_TELEPHONE="es_ES.UTF-8"
 INFO global: VAGRANT_OLD_ENV_KDE_SESSION_VERSION="5"
 INFO global: VAGRANT_OLD_ENV_LOGNAME="david"
 INFO global: VAGRANT_OLD_ENV_XDG_SESSION_ID="4"
 INFO global: VAGRANT_OLD_ENV_QT_ACCESSIBILITY="1"
 INFO global: VAGRANT_LOG="debug"
 INFO global: Plugins:
 INFO global:   - vagrant-hostsupdater = [installed: 1.0.2 constraint: > 0]
 INFO global:   - vagrant-rsync-back = [installed: 0.0.1 constraint: > 0]
 INFO global:   - vagrant-share = [installed: undefined constraint: > 0]
 INFO global:   - vagrant-vbguest = [installed: 0.15.1 constraint: > 0]
DEBUG bundler: Current generated plugin dependency list: [<Gem::Dependency type=:runtime name="vagrant-hostsupdater" requirements="> 0">, <Gem::Dependency type=:runtime name="vagrant-rsync-back" requirements="> 0">, <Gem::Dependency type=:runtime name="vagrant-share" requirements="> 0">, <Gem::Dependency type=:runtime name="vagrant-vbguest" requirements="> 0">]
DEBUG bundler: Generating new builtin set instance.
DEBUG bundler: Generating new plugin set instance. Skip gems - []
DEBUG bundler: Activating solution set: ["vagrant-hostsupdater-1.0.2", "vagrant-rsync-back-0.0.1", "ruby_dep-1.3.1", "erubis-2.7.0", "builder-3.2.3", "gyoku-1.3.1", "nori-2.6.0", "multi_json-1.12.1", "little-plugger-1.1.4", "logging-2.2.2", "rubyntlm-0.6.2", "httpclient-2.8.3", "ffi-1.9.18", "gssapi-1.2.0", "winrm-2.2.3", "rubyzip-1.2.1", "winrm-fs-1.0.1", "winrm-elevated-1.1.0", "wdm-0.1.1", "netrc-0.11.0", "mime-types-data-3.2016.0521", "mime-types-3.1", "unf_ext-<IP_ADDRESS>", "unf-0.1.4", "domain_name-0.5.20170404", "http-cookie-1.0.3", "rest-client-2.0.2", "rb-kqueue-0.2.5", "net-ssh-4.1.0", "net-scp-1.2.1", "net-sftp-2.1.2", "log4r-1.1.10", "hashicorp-checkpoint-0.1.4", "rb-inotify-0.9.10", "rb-fsevent-0.10.2", "listen-3.1.5", "i18n-0.8.0", "childprocess-0.6.3", "vagrant-1.9.8", "vagrant-share-1.1.9", "micromachine-2.0.0", "vagrant-vbguest-0.15.1"]
DEBUG bundler: Activating gem vagrant-hostsupdater-1.0.2
DEBUG bundler: Activating gem vagrant-rsync-back-0.0.1
DEBUG bundler: Activating gem vagrant-share-1.1.9
DEBUG bundler: Activating gem micromachine-2.0.0
DEBUG bundler: Activating gem vagrant-vbguest-0.15.1
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/communicators/ssh/plugin.rb
 INFO manager: Registered plugin: ssh communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/communicators/winrm/plugin.rb
 INFO manager: Registered plugin: winrm communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/communicators/winssh/plugin.rb
 INFO manager: Registered plugin: windows ssh communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/hosts/slackware/plugin.rb
 INFO manager: Registered plugin: Slackware host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/hosts/bsd/plugin.rb
 INFO manager: Registered plugin: BSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/hosts/redhat/plugin.rb
 INFO manager: Registered plugin: Red Hat Enterprise Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/hosts/suse/plugin.rb
 INFO manager: Registered plugin: SUSE host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/hosts/windows/plugin.rb
 INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/hosts/gentoo/plugin.rb
 INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/hosts/freebsd/plugin.rb
 INFO manager: Registered plugin: FreeBSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/hosts/arch/plugin.rb
 INFO manager: Registered plugin: Arch host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/hosts/linux/plugin.rb
 INFO manager: Registered plugin: Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/hosts/darwin/plugin.rb
 INFO manager: Registered plugin: Mac OS X host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/hosts/null/plugin.rb
 INFO manager: Registered plugin: null host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/elementary/plugin.rb
 INFO manager: Registered plugin: Elementary guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/mint/plugin.rb
 INFO manager: Registered plugin: Mint guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/slackware/plugin.rb
 INFO manager: Registered plugin: Slackware guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/solaris11/plugin.rb
 INFO manager: Registered plugin: Solaris 11 guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/debian/plugin.rb
 INFO manager: Registered plugin: Debian guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/bsd/plugin.rb
 INFO manager: Registered plugin: BSD-based guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/trisquel/plugin.rb
 INFO manager: Registered plugin: Trisquel guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/redhat/plugin.rb
 INFO manager: Registered plugin: Red Hat Enterprise Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/suse/plugin.rb
 INFO manager: Registered plugin: SUSE guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/funtoo/plugin.rb
 INFO manager: Registered plugin: Funtoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/solaris/plugin.rb
 INFO manager: Registered plugin: Solaris guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/esxi/plugin.rb
 INFO manager: Registered plugin: ESXi guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/windows/plugin.rb
 INFO manager: Registered plugin: Windows guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/kali/plugin.rb
 INFO manager: Registered plugin: Kali guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/fedora/plugin.rb
 INFO manager: Registered plugin: Fedora guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/openbsd/plugin.rb
 INFO manager: Registered plugin: OpenBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/smartos/plugin.rb
 INFO manager: Registered plugin: SmartOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/pld/plugin.rb
 INFO manager: Registered plugin: PLD Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/gentoo/plugin.rb
 INFO manager: Registered plugin: Gentoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/freebsd/plugin.rb
 INFO manager: Registered plugin: FreeBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/arch/plugin.rb
 INFO manager: Registered plugin: Arch guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/linux/plugin.rb
 INFO manager: Registered plugin: Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/dragonflybsd/plugin.rb
 INFO manager: Registered plugin: DragonFly BSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/darwin/plugin.rb
 INFO manager: Registered plugin: Darwin guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/photon/plugin.rb
 INFO manager: Registered plugin: VMware Photon guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/tinycore/plugin.rb
 INFO manager: Registered plugin: TinyCore Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/netbsd/plugin.rb
 INFO manager: Registered plugin: NetBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/nixos/plugin.rb
 INFO manager: Registered plugin: NixOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/amazon/plugin.rb
 INFO manager: Registered plugin: Amazon Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/atomic/plugin.rb
 INFO manager: Registered plugin: Atomic Host guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/coreos/plugin.rb
 INFO manager: Registered plugin: CoreOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/omnios/plugin.rb
 INFO manager: Registered plugin: OmniOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/guests/ubuntu/plugin.rb
 INFO manager: Registered plugin: Ubuntu guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/providers/virtualbox/plugin.rb
 INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/providers/docker/plugin.rb
 INFO manager: Registered plugin: docker-provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/providers/hyperv/plugin.rb
 INFO manager: Registered plugin: Hyper-V provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/pushes/local-exec/plugin.rb
 INFO manager: Registered plugin: local-exec
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/pushes/atlas/plugin.rb
 INFO manager: Registered plugin: atlas
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/pushes/heroku/plugin.rb
 INFO manager: Registered plugin: heroku
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/pushes/ftp/plugin.rb
 INFO manager: Registered plugin: ftp
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/pushes/noop/plugin.rb
 INFO manager: Registered plugin: noop
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/kernel_v1/plugin.rb
 INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/list-commands/plugin.rb
 INFO manager: Registered plugin: list-commands command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/port/plugin.rb
 INFO manager: Registered plugin: port command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/push/plugin.rb
 INFO manager: Registered plugin: push command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/status/plugin.rb
 INFO manager: Registered plugin: status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/resume/plugin.rb
 INFO manager: Registered plugin: resume command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/halt/plugin.rb
 INFO manager: Registered plugin: halt command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/suspend/plugin.rb
 INFO manager: Registered plugin: suspend command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/version/plugin.rb
 INFO manager: Registered plugin: version command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/provision/plugin.rb
 INFO manager: Registered plugin: provision command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/powershell/plugin.rb
 INFO manager: Registered plugin: powershell command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/init/plugin.rb
 INFO manager: Registered plugin: init command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/box/plugin.rb
 INFO manager: Registered plugin: box command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/ssh/plugin.rb
 INFO manager: Registered plugin: ssh command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/reload/plugin.rb
 INFO manager: Registered plugin: reload command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/rdp/plugin.rb
 INFO manager: Registered plugin: rdp command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/package/plugin.rb
 INFO manager: Registered plugin: package command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/snapshot/plugin.rb
 INFO manager: Registered plugin: snapshot command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/cap/plugin.rb
 INFO manager: Registered plugin: cap command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/provider/plugin.rb
 INFO manager: Registered plugin: provider command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/login/plugin.rb
 INFO manager: Registered plugin: vagrant-login
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/ssh_config/plugin.rb
 INFO manager: Registered plugin: ssh-config command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/global-status/plugin.rb
 INFO manager: Registered plugin: global-status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/up/plugin.rb
 INFO manager: Registered plugin: up command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/help/plugin.rb
 INFO manager: Registered plugin: help command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/plugin/plugin.rb
 INFO manager: Registered plugin: plugin command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/destroy/plugin.rb
 INFO manager: Registered plugin: destroy command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/validate/plugin.rb
 INFO manager: Registered plugin: validate command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/provisioners/puppet/plugin.rb
 INFO manager: Registered plugin: puppet
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/provisioners/cfengine/plugin.rb
 INFO manager: Registered plugin: CFEngine Provisioner
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/provisioners/docker/plugin.rb
 INFO manager: Registered plugin: docker
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/provisioners/shell/plugin.rb
 INFO manager: Registered plugin: shell
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/provisioners/ansible/plugin.rb
 INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/provisioners/salt/plugin.rb
 INFO manager: Registered plugin: salt
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/provisioners/file/plugin.rb
 INFO manager: Registered plugin: file
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/provisioners/chef/plugin.rb
 INFO manager: Registered plugin: chef
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/kernel_v2/plugin.rb
 INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/synced_folders/nfs/plugin.rb
 INFO manager: Registered plugin: NFS synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/synced_folders/rsync/plugin.rb
 INFO manager: Registered plugin: RSync synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/synced_folders/smb/plugin.rb
 INFO manager: Registered plugin: SMB synced folders
 INFO global: Loading plugins!
DEBUG global: Loading plugin `vagrant-hostsupdater` with default require: `vagrant-hostsupdater`
 INFO manager: Registered plugin: HostsUpdater
DEBUG global: Successfully loaded plugin `vagrant-hostsupdater`.
DEBUG global: Loading plugin `vagrant-rsync-back` with default require: `vagrant-rsync-back`
 INFO manager: Registered plugin: Rsync Back
DEBUG global: Successfully loaded plugin `vagrant-rsync-back`.
DEBUG global: Loading plugin `vagrant-share` with default require: `vagrant-share`
 INFO manager: Registered plugin: vagrant-share
DEBUG global: Successfully loaded plugin `vagrant-share`.
DEBUG global: Loading plugin `vagrant-vbguest` with default require: `vagrant-vbguest`
 INFO manager: Registered plugin: vagrant-vbguest
DEBUG global: Successfully loaded plugin `vagrant-vbguest`.
 INFO vagrant: `vagrant` invoked: ["up", "--debug"]
DEBUG vagrant: Creating Vagrant environment
 INFO environment: Environment initialized (#<Vagrant::Environment:0x00000001bc1a50>)
 INFO environment:   - cwd: /home/david/vagrant/blt-test
 INFO environment: Home path: /home/david/.vagrant.d
DEBUG environment: Effective local data path: /home/david/vagrant/blt-test/.vagrant
 INFO environment: Local data path: /home/david/vagrant/blt-test/.vagrant
DEBUG environment: Creating: /home/david/vagrant/blt-test/.vagrant
 INFO environment: Running hook: environment_plugins_loaded
 INFO runner: Preparing hooks for middleware sequence...
 INFO runner: 2 hooks defined.
 INFO runner: Running action: environment_plugins_loaded #<Vagrant::Action::Builder:0x0000000265a958>
 INFO environment: Running hook: environment_load
 INFO runner: Preparing hooks for middleware sequence...
 INFO runner: 2 hooks defined.
 INFO runner: Running action: environment_load #<Vagrant::Action::Builder:0x000000024545f0>
 INFO cli: CLI: [] "up" []
DEBUG cli: Invoking command class: VagrantPlugins::CommandUp::Command []
DEBUG command: 'Up' each target VM...
 INFO loader: Set :root = ["#<Pathname:/home/david/vagrant/blt-test/Vagrantfile>"]
DEBUG loader: Populating proc cache for #<Pathname:/home/david/vagrant/blt-test/Vagrantfile>
DEBUG loader: Load procs for pathname: /home/david/vagrant/blt-test/Vagrantfile
ERROR loader: Vagrantfile load error: Malformed version number string 2.4.4 (stable-2.4 92cea82a4e) last updated 2018/02/28 20:16:43 (GMT +200)
ERROR loader: /opt/vagrant/embedded/lib/ruby/2.3.0/rubygems/version.rb:207:in `initialize'
/opt/vagrant/embedded/lib/ruby/2.3.0/rubygems/version.rb:199:in `new'
/opt/vagrant/embedded/lib/ruby/2.3.0/rubygems/version.rb:199:in `new'
/home/david/vagrant/blt-test/vendor/geerlingguy/drupal-vm/lib/drupalvm/vagrant.rb:62:in `require_ansible_version'
/home/david/vagrant/blt-test/vendor/geerlingguy/drupal-vm/Vagrantfile:40:in `<top (required)>'
/home/david/vagrant/blt-test/Vagrantfile:13:in `load'
/home/david/vagrant/blt-test/Vagrantfile:13:in `<top (required)>'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/config/loader.rb:219:in `load'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/config/loader.rb:219:in `block in procs_for_path'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/config.rb:53:in `block in capture_configures'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/config.rb:48:in `synchronize'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/config.rb:48:in `capture_configures'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/config/loader.rb:217:in `procs_for_path'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/config/loader.rb:203:in `procs_for_source'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/config/loader.rb:67:in `block in set'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/config/loader.rb:61:in `each'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/config/loader.rb:61:in `set'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/environment.rb:505:in `config_loader'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/environment.rb:810:in `vagrantfile'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/up/command.rb:67:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/cli.rb:42:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/environment.rb:308:in `cli'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/bin/vagrant:138:in `<main>'
 INFO environment: Running hook: environment_unload
 INFO loader: Loading configuration in order: [:home, :root]
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG push: finalizing
 INFO host: Autodetecting host type for [#<Vagrant::Environment: /home/david/vagrant/blt-test>]
DEBUG host: Trying: slackware
DEBUG host: Trying: redhat
DEBUG host: Trying: suse
DEBUG host: Trying: gentoo
DEBUG host: Trying: freebsd
DEBUG host: Trying: arch
DEBUG host: Trying: darwin
DEBUG host: Trying: bsd
DEBUG host: Trying: windows
DEBUG host: Trying: linux
 INFO host: Detected: linux!
 INFO runner: Preparing hooks for middleware sequence...
 INFO runner: 2 hooks defined.
 INFO runner: Running action: environment_unload #<Vagrant::Action::Builder:0x000000025fcb00>
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::VagrantfileLoadError: There was an error loading a Vagrantfile. The file being loaded
and the error message are shown below. This is usually caused by
a syntax error.

Path: /home/david/vagrant/blt-test/Vagrantfile
Line number: 0
Message: ArgumentError: Malformed version number string 2.4.4 (stable-2.4 92cea82a4e) last updated 2018/02/28 20:16:43 (GMT +200)>
ERROR vagrant: There was an error loading a Vagrantfile. The file being loaded
and the error message are shown below. This is usually caused by
a syntax error.

Path: /home/david/vagrant/blt-test/Vagrantfile
Line number: 0
Message: ArgumentError: Malformed version number string 2.4.4 (stable-2.4 92cea82a4e) last updated 2018/02/28 20:16:43 (GMT +200)
ERROR vagrant: /opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/config/loader.rb:245:in `rescue in block in procs_for_path'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/config/loader.rb:218:in `block in procs_for_path'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/config.rb:53:in `block in capture_configures'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/config.rb:48:in `synchronize'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/config.rb:48:in `capture_configures'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/config/loader.rb:217:in `procs_for_path'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/config/loader.rb:203:in `procs_for_source'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/config/loader.rb:67:in `block in set'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/config/loader.rb:61:in `each'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/config/loader.rb:61:in `set'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/environment.rb:505:in `config_loader'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/environment.rb:810:in `vagrantfile'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/plugins/commands/up/command.rb:67:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/cli.rb:42:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/environment.rb:308:in `cli'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.8/bin/vagrant:138:in `<main>'
 INFO interface: error: There was an error loading a Vagrantfile. The file being loaded
and the error message are shown below. This is usually caused by
a syntax error.

Path: /home/david/vagrant/blt-test/Vagrantfile
Line number: 0
Message: ArgumentError: Malformed version number string 2.4.4 (stable-2.4 92cea82a4e) last updated 2018/02/28 20:16:43 (GMT +200)
There was an error loading a Vagrantfile. The file being loaded
and the error message are shown below. This is usually caused by
a syntax error.

Path: /home/david/vagrant/blt-test/Vagrantfile
Line number: 0
Message: ArgumentError: Malformed version number string 2.4.4 (stable-2.4 92cea82a4e) last updated 2018/02/28 20:16:43 (GMT +200)
 INFO interface: Machine: error-exit ["Vagrant::Errors::VagrantfileLoadError", "There was an error loading a Vagrantfile. The file being loaded\nand the error message are shown below. This is usually caused by\na syntax error.\n\nPath: /home/david/vagrant/blt-test/Vagrantfile\nLine number: 0\nMessage: ArgumentError: Malformed version number string 2.4.4 (stable-2.4 92cea82a4e) last updated 2018/02/28 20:16:43 (GMT +200)"]

Summary
I get this error when try to start a virtual machine, with ansible installed via git. The problem seens to be related with the fact that drupalvm is not able to process the output of ansible --version command.

Related original issue on acquia/blt https://github.com/acquia/blt/issues/2610

@dlopez-akalam why not install ansible with brew or through system package manager?
If ansible only works from the sources only with root then you haven't set the right permissions to the build files.
Personally I'd say that this would be out of scope relating drupal vm as it requires functional ansible, vagrant and virtualbox. And your ansible wont run without elevated privileges so I'm not sure is this the right place to ask help.

Thought i did a quick snoop trough This is the part that gets the version number:
https://github.com/geerlingguy/drupal-vm/blob/789266c848a7681d5dd7916cafc8e23b04d1b4f6/lib/drupalvm/vagrant.rb#L53-L56
And this is probably failing:
https://github.com/geerlingguy/drupal-vm/blob/789266c848a7681d5dd7916cafc8e23b04d1b4f6/lib/drupalvm/vagrant.rb#L62
so I'd presume Gem::Version.new cant handle some of the extra strings that the source build ansible is adding to the version line of ansible --version
But is that something to fix on drupalvms files vagrant rb file is the interesting bit > I'd say no unless ansibles builds start to output some more info on the version part

I think this is a Drupal VM bug as long as it's unable to parse the Ansible version. I've created a PR that changes the regexp to ignore part in parenthesis, see https://github.com/geerlingguy/drupal-vm/pull/1726

This is fixed in @rsanzante's PR #1726 - thanks!
(It's currently in Drupal VM dev/master only, I have not yet created a release with this fix).

Sorry, I don't think this has fixed the issue. Or it may have created a different issue? I had some problems setting up a new DrupalVM box this morning from a master branch version of DrupalVM. I eventually tied it down to this change. Reverting the change appeared to fix this issue.
Here is the error I was seeing. It looks like the whole ansible version output is being included as the version number.
`There was an error loading a Vagrantfile. The file being loaded
and the error message are shown below. This is usually caused by
a syntax error.
Path: /Users/someone/Sites/project/Vagrantfile
Line number: 0
Message: ArgumentError: Malformed version number string <IP_ADDRESS>
config file = None
configured module search path = [u'/Users/someone/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /Library/Python/2.7/site-packages/ansible
executable location = /usr/local/bin/ansible-playbook
python version = 2.7.10`
Here is the output of my ansible --version
→ ansible --version ansible <IP_ADDRESS>   config file = None   configured module search path = [u'/Users/someone/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']   ansible python module location = /Library/Python/2.7/site-packages/ansible   executable location = /usr/local/bin/ansible   python version = 2.7.10 (default, Feb  7 2017, 00:08:15) [GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.34)]
If you need any more information then let me know.

@philipnorton42 What OS are you using?

I guess it's matching the trailing whitespace:
/^[^\s]+ ([^\(]+).*$/

should be
/^[^\s]+ ([^\(\s]+).*$/

I asked for the OS because a colleague with MacOS today reported an error with this regular expression.
The problem is the last number, for example, the '0' in <IP_ADDRESS>. In OSX this triggers an error while in Linux it doesn't.
He solved using this regexp:
/^[^\s]+ ((?:\d\.){2}\d).*$/
See it in action in this link:
http://rubular.com/r/J4TBshh16b
@oxyc Those expression matches the last number as well so I guess they don't solve the issue.
I'm going to create a new PR.

PR done! I can't reopen this issue, should I create a new issue!
Sorry for the first regexp :-1:

I wanted to chime in I had the exact same error with the same version of Ansible, except on Ubuntu 16.04 LTS, Linux <IP_ADDRESS>-112-generic kernel.
Though I haven't tested the new regex yet, I thought it might be useful to at least confirm the issue is present on more than one OS.

@rsanzante For what it's worth I am running osx Sierra. Thanks for the update though, I will test the regex in the morning (UK time).

Alternative way for matching: https://stackoverflow.com/questions/8955657/regex-pattern-to-extract-version-number-from-string eg.
\d+(\.\d+)+

That would drop out any strings also if they added something more to the version number like 5.0.0-alpha .

@FinBoWa That expression would match <IP_ADDRESS> instead of 2.4.1, so the error would still be present. Proposed regexp in https://github.com/geerlingguy/drupal-vm/issues/1725#issuecomment-374749602 would match 5.0.0 from "ansible 5.0.0-alpha", see http://rubular.com/r/J4TBshh16b.

@oxyc, no because it parsed <IP_ADDRESS> instead of 2.4.1. Semver only has three numbers, not four, see https://semver.org/.
I guess the code that drupal vm depending on OS enforces the three numbers and triggers an error if it receives four numbers.

But this has been working fine since it was introduced in https://github.com/geerlingguy/drupal-vm/commit/ae4c8031d7ff6f8e362595bbca2acdc7e2594167 so I don't think the 4th digit can be the cause.

ansible_version = "2.3.1-patch1"
req = Gem::Requirement.new(">2.4")

if req.satisfied_by?(Gem::Version.new(ansible_version))
   puts "yes"
else
   puts "no"
end

That works but if you put something else there you get a similar error
ansible_version = "2.3.1-patch1 blaaah"
req = Gem::Requirement.new(">2.4")

if req.satisfied_by?(Gem::Version.new(ansible_version))
   puts "yes"
else
   puts "no"
end

So the amount of should not be the cause of the error and event the -patch . So the rexgp is getting something more than just the actual version, maybe a cr char or something?

@oxyc I don't have an answer for that. It strange because old regexp from https://github.com/geerlingguy/drupal-vm/pull/1726 matches the same as regexp from https://github.com/geerlingguy/drupal-vm/commit/410e8788a719777f4f23fd93b46c1b5b5d422091.
Anyway, I think version detection should stick to Semver, just 3 numbers. That's what new PR does (https://github.com/geerlingguy/drupal-vm/pull/1739).
See the three regexs in action

'Old' regexp: http://rubular.com/r/DfzD7bFzzN
Regexp from merged PR: http://rubular.com/r/fUNRdT9cJ2
Regexp from new PR: http://rubular.com/r/DaUdEJVgiW

@FinBoWa I don't see any garbage chars in the matches from rubular.com. Maybe their engine is not so similar to Ruby's engine?

I'm just pointing out that you are dropping version information on the wrong premises that the fourth digit was the cause of the issue and at least for me it doesn't seem that way as the ruby Gem::Version.new(ansible_version) is cabable of handling it > somethign else is probably causing the issues.
Anyways: personally im not happy dropping the fourth as its just mere forcing a string to be "semver" if it wasnt that already the string is still valid version with any number of digits.

But im not part of the drupal vm team so these are just my point of view so take them as that way :D

@philipnorton42 which ruby and gem versions do you have?
ruby --version
gem --version

I can confirm I get the same error on macOS with:
drupal-vm-test master*: ruby --version
ruby 2.5.0p0 (2017-12-25 revision 61468) [x86_64-darwin17]

drupal-vm-test master*: gem --version
2.7.4

Ensuring the trailing whitespace isn't in the match fixes it for me:
# Return the ansible version parsed from running the executable path provided.
def ansible_version
  /^[^\s]+ ([^\s]+)$/.match(`#{ansible_bin} --version`) { |match| return match[1] }
end

@rsanzante any chance you and your colleague could test the alternative PR i opened at #1740? If you can confirm it works it's always nicer to be able to lock the full Ansible version :) As I couldn't find the exact cause for the bug I'm still not entirely confident so would appreciate if you could give it a try.

I have the same issue as @philipnorton42. Either of patch #1739 or #1740 fixes the issue for me.


WIP: Prepare for release

Miscellaneous jobs required to do a release.

Update the README to mention nightly
Switch licence from Apache-2.0 to a MIT/Apache-2.0 dual license

@Centril, are you okay with this?

Update Cargo.toml metadata
Enable travis to make sure breaking nightly changes are detected early

@Centril, it doesn't look like I can enable travis because I'm not the repo owner. Would you be able to enable it and set up "cron job" so it rebuilds master every week or so?

@Centril, are you okay with this?

Certainly!

@Centril, it doesn't look like I can enable travis because I'm not the repo owner. Would you be able to enable it and set up "cron job" so it rebuilds master every week or so?

Enabled travis and setup a weekly cron job. :)

Released! :tada:

🎉 🎈 🍾
Thanks a lot for driving this!


wg-stories Meeting 2022-02-25

Meeting date/time (UTC)
2022-02-25 18:00
Instructions for joining the meeting
https://meet.google.com/mdz-axok-ndz?authuser=0&hs=122
Agenda
Note: Add a comment on this issue to propose items for the agenda.

Updates
Jon Newmuis:
Launch for Dev preview - shopping functionality within stories.
APIs are mostly final. Fully available functionality.
Ask questions to the slido:
https://app.sli.do/event/vUumXTAJenbxGEqLax7zpA
Philip Bell:
Shopping dev preview links:
https://github.com/ampproject/amphtml/issues/37570
https://wsdemos.uc.r.appspot.com/shopping
Caleb Cordry:
Going to work on auto-advancing ads.
Reports that current ad experiences.
Decreases bounce rate (seeing the number of users that see the ads).
Affects All ads everywhere.
Short stories are harder to monetize:
if we change the ways the ads are places,
We roll the dice for the short stories.
Caleb has more insight and can post a link to more details to how that algorithm works.
Shihua Zheng:
Moving the ad badges to the bottom of the page.
https://github.com/ampproject/amphtml/issues/37774
Jon:
Developer preview email list.
Can add some shoppable elements of the story.
Philip:
Need to make sure to opt in to the nightly build as shopping features are relatively new at this point.
https://cdn.ampproject.org/experiments.html
Jon:
Describes shopping config, full specification that outlines the shopping tags, PDP, and PLP.
Want to make sure that something is relatively small scope and launchable!
Pratik Ghela:
Doesn't work even after turning on nightly mode
Philip:
What device Pratik?
Pratik:
Macbook Pro
Jon:
Prefetching is previously undefined behavior:
Edouard Short:
Change of visibility states, buttons and an iframe.
When playing the story, you can’t pre-render the assets.
Want to find out what a better workflow is.
Jon:
Set visibility state to pre-render, using the fragment parameter initially.
At the point that you want to render the story, you can use the amp viewer api to set the visibility to visible.
Edouard:
When I set it to visible, it plays the story. Would like to show the assets without playing the story.
Jon:
Protect user privacy, do in only cases when there is a n amp cache, which are trusted sources.
Jon:
Reach out to third party vendors like amazon and shopify to invest in stories/shopping. There’s a whole world in which we can go shopping. This is just the beginning.
Edouard:
Keep in mind that digital projects have distribution advantages over physical projects
Jon:
We want to hear feedback from the shopping experience.


cli: enable invoice for UDA

Currently via CLI it's not possible to create an invoice to receive a UDA.
@crisdut could you please take care of this?

@crisdut could you please take care of this?

Yes!

@crisdut any news on this?

I'm having a hard time finding the time to do this, but give me a few days and I'll do it.

The last three commits in https://github.com/RGB-WG/rgb/pull/248 are now do the NFT (and all other forms) of invoicing, closing this issue.
I first tried to do it as a dedicated PR, but it was not possible since I needed a lot of stuff I did in the develop branch already, so I just added those things on top.


Cleanup user directories if state was leftover from previous run

We are seeing failures in our CI relating to state not being cleaned
up in a previous run:
  1) Chef::Provider::User::Useradd action :create when the user already exists and home directory is updated and manage_home is enabled moves the home directory to the new location
     Failure/Error: user_resource.run_action(:create)
     Mixlib::ShellOut::ShellCommandFailed:
       user[TEST USER RESOURCE] (dynamically defined) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '12'
       ---- Begin output of ["usermod", "-d", "/home/bar", "-m", "cf-test"] ----
       STDOUT:
       STDERR: usermod: directory /home/bar exists
       ---- End output of ["usermod", "-d", "/home/bar", "-m", "cf-test"] ----
       Ran ["usermod", "-d", "/home/bar", "-m", "cf-test"] returned 12
     # ./lib/chef/mixin/shell_out.rb:56:in `shell_out!'
     # ./lib/chef/provider/user/useradd.rb:42:in `manage_user'
     # ./lib/chef/provider/user.rb:137:in `block in action_create'
     # ./lib/chef/mixin/why_run.rb:52:in `call'
     # ./lib/chef/mixin/why_run.rb:52:in `add_action'
     # ./lib/chef/provider.rb:180:in `converge_by'
     # ./lib/chef/provider/user.rb:136:in `action_create'
     # ./lib/chef/provider.rb:145:in `run_action'
     # ./lib/chef/resource.rb:561:in `run_action'
     # ./spec/functional/resource/user/useradd_spec.rb:336:in `block (4 levels) in <top (required)>'

:+1:

:+1:

:+1:


added target = _blank so as to open link in new tab for resource table

Description of PR
Type of PR

[x] Bugfix
[ ] New feature

Relevant Issues
Fixes #...
Checklist

[x] Compiles and passes lint tests
[x] Properly formatted
[x] Tested on desktop
[x] Tested on phone

Screenshots

duplicate #920


Dynamic routes along with manually created?

Hello. I am trying to use manually created pages/routes along with dynamically generated, but seems like it is not working.
Is there any option to use Nuxt like this:

wtf route doesn't work on articles/wtf/ endpoint. Only the routes that comes from API in _section is working.
Since I can't find proper way to insert components in dynamic routes (that fetch data and then v-html it from API), I want to have an opportunity sometimes create manually rich pages, where I can use components etc, and not being dependent on v-for and v-html schemes.
How to achieve that?

 Then only create a wtf.vue page for it. Or place an index.vue inside the folder so the route is generated.

@vuchl no, I expect wtf to be a section! Where I can manually put other pages.

Nothing from this is working

https://github.com/vuchl/static-and-dynamic-routes - I have the same code. It doesn't work in real setup.

Looks like I needed to restart Nuxt. Now it's working. Strange, never saw this before, usually Nuxt don't need restart.


When Czml.DataSource.precess is called, the view will appear

初始加载2000个卫星,后续从websocket中持续读取数据通过Czml.DataSource.process方法往position属性中加入对应的坐标,这种情况下process方法 每调用一次,视图和currentTime会出现卡顿,卡顿的时长与播放速度有关

@JimmingSong does the issue only appear if you have 2000 satellites loaded?
Do you mean that the browser window itself freezes, or just that the timeline stops progressing? Are you able to reproduce this issue in Sandcastle (https://cesiumjs.org/Cesium/Apps/Sandcastle/index.html) ? Can you provide a code example of what you're doing?


homepage log in button issue (front end)

Need to update homepage so that log in button navigate & changes to account page (not just navigate)

Issue with log in button navigating to account page but not changing actual page (stays on home page and have to click to different page to reset)

Updated previously, now reroutes to the account page.


🔄 synced file(s) with klaasnicolaas/github-config

synced local file(s) with klaasnicolaas/github-config.

Changed files

synced local directory .github/ with remote directory github/

This PR was created automatically by the repo-file-sync-action workflow run #8546033207

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (672e745) to head (c3b21ff).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #376   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines          165       165
  Branches        31        31
=========================================
  Hits           165       165

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Include deployment of CHproxy?

See https://github.com/Vertamedia/chproxy

Yes, we plan to have it supported.

@alex-zaitsev any update on this feature ?


SQLite composite key not working

I see that entity having composite key for a SQLite database does not work.
There is a exception throw in the code.
Can you let me know how can I test my code with the SQLite and if there is a better alternative to do this
https://github.com/MoonStorm/Dapper.FastCRUD/blob/fb37c4a4796bc4482661b7feb9dd5802c955af79/Dapper.FastCrud/SqlBuilders/SqLiteBuilder.cs#L16

At a first glance, that restriction shouldn't exist. Thanks for bringing this issue to our attention.


“confirms to” should be “conforms to”

Throughout the source and generated diagrams, the relationship between a protocol and a type that conforms to the protocol is written as “confirms to”. This is a typo.
Excerpt from https://docs.swift.org/swift-book/LanguageGuide/Protocols.html:

Any type that satisfies the requirements of a protocol is said to conform to that protocol.

Until I created a patch you can use the following workaround: set a custom text for that relationship type in your .swiftplantuml.yml configuration file.
relationships:
  realize:
    label: "conforms to"

Fix is available in 0.7.3

Thank you!


Test with mltap

Include jmakeig/mltap as a dependency
Update test scripts
Likely, fix mltap bugs
Profit!

Fixed by series of commits ending with 4fea876655a6cfdf001234b5f0516415c0e4540b.


GPO error

I added the GPO as suggested from this page under 'Use Group Policy to control the installation of Microsoft Teams' in our environment and now we receive an error "The processing of Group Policy failed. Windows attempted to read the file \xxxxx.net\SysVol\xxxxx.net\Policies{456B5A1A-BFF7-4370-965C-AD50A0549696}\gpt.ini from a domain controller and was not successful. "  Powershell inquiry shows the newly added Teams - Excluded GPO.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7936ca5e-c658-4956-b174-99eaf1eb67d4
Version Independent ID: 9ecc0b61-a941-f5e1-96c3-d32fae59eacd
Content: Deploy Microsoft Teams with Microsoft 365 Apps
Content Source: DeployOffice/teams-install.md
Service: o365-proplus-itpro
GitHub Login: @DHB-MSFT
Microsoft Alias: danbrown

@jwatt130 . Did you updated  latest admx adml templates in your  domain computer.
Which policy settings did you enabled in GPO


Login function

Login function to the heroku backend

@yochannah the requested changes for these were fixed in the last commit. It should be good to go. I'm working on solving the other issues in readiness for deployment


Release notes for Delegate HF releae 82505

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screenshot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65f80646a4d56541596a2ecc--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65f815e69a02ab4ee11c97b1--harness-developer.netlify.app


fix: set dashboard mine tab to created_by filter

SUMMARY
This pr fixes an issue where the old mine tab filter in the dashboard table would filter by owners where it should be set to created_by.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
https://user-images.githubusercontent.com/17326228/129641943-98cba82a-602d-4ca7-b2c3-cc98e78c39a1.mov
TESTING INSTRUCTIONS
go to. home page dashboard table and make sure mine tab loads same user objects on page load and clicking mine tab.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up

🏷 2021.31


[BUG] Delete node is not required on longhorn UI

Describe the bug
The option delete node/remove node is not required on the longhorn node page after https://github.com/longhorn/longhorn-manager/pull/692
To Reproduce
Steps to reproduce the behavior:

Go to the Longhorn node page, the delete node button and remove node option should be removed.

Environment:

Longhorn version: Longhorn-master

Agree. It seems the manual node deletion is meaningless now.

Verified with longhorn-master - bb53c5f
Validation - Pass
The delete node button is not present on the node page.


policy: Move exported Lookup to EndpointPolicy

Move the exported Lookup function to EndpointPolicy, so that it can actually be used from other packages.

/test

rebased to pick up CI fix from main.

/test


[FEATURE REQUEST] A BLOG ON THE IMPORTANCE OF MINDFULNESS

I have a very informative and interactive idea in mind to mention about the importance of mind over matter and how can we live in the present with the strength of this mind
Could you please give met he opportunity to contribute here @akshitagupta15june

you can create the blog, share the google doc in the moksh discord group, and if it gets accepted we will publish it with credit.


PolicyRecordingBot and Whiteboards

We are currently able to record audio, video and screen shares. Is Whiteboard stream somehow also available? If yes, could you please let us know what changes are needed to record whiteboards shared during a teams meeting?

No, the whiteboard stream is not available to the bot.

Thanks


Multi GPU training is stuck

🐛 Bug

To Reproduce
I am experienceing the same problem.
Except that it does not work in 'dp' setting as well as in 'ddp' setting'
I ran the cifar-10 example with multiple gpus
import os

import torch
import torch.nn as nn
import torch.nn.functional as F
import torchvision
from pl_bolts.datamodules import CIFAR10DataModule
from pl_bolts.transforms.dataset_normalizations import cifar10_normalization
from pytorch_lightning import LightningModule, seed_everything, Trainer
from pytorch_lightning.callbacks import LearningRateMonitor
from pytorch_lightning.loggers import TensorBoardLogger
from torch.optim.lr_scheduler import OneCycleLR
from torch.optim.swa_utils import AveragedModel, update_bn
from torchmetrics.functional import accuracy

seed_everything(7)

PATH_DATASETS = os.environ.get('PATH_DATASETS', '.')
AVAIL_GPUS = torch.cuda.device_count()
BATCH_SIZE = 256 if AVAIL_GPUS else 64
NUM_WORKERS = int(os.cpu_count() / 2)

train_transforms = torchvision.transforms.Compose([
    torchvision.transforms.RandomCrop(32, padding=4),
    torchvision.transforms.RandomHorizontalFlip(),
    torchvision.transforms.ToTensor(),
    cifar10_normalization(),
])

test_transforms = torchvision.transforms.Compose([
    torchvision.transforms.ToTensor(),
    cifar10_normalization(),
])

cifar10_dm = CIFAR10DataModule(
    data_dir=PATH_DATASETS,
    batch_size=BATCH_SIZE,
    num_workers=NUM_WORKERS,
    train_transforms=train_transforms,
    test_transforms=test_transforms,
    val_transforms=test_transforms,
)

def create_model():
    model = torchvision.models.resnet18(pretrained=False, num_classes=10)
    model.conv1 = nn.Conv2d(3, 64, kernel_size=(3, 3), stride=(1, 1), padding=(1, 1), bias=False)
    model.maxpool = nn.Identity()
    return model

class LitResnet(LightningModule):

    def __init__(self, lr=0.05):
        super().__init__()

        self.save_hyperparameters()
        self.model = create_model()

    def forward(self, x):
        out = self.model(x)
        return F.log_softmax(out, dim=1)

    def training_step(self, batch, batch_idx):
        x, y = batch
        logits = self(x)
        loss = F.nll_loss(logits, y)
        self.log('train_loss', loss)
        return loss

    def evaluate(self, batch, stage=None):
        x, y = batch
        logits = self(x)
        loss = F.nll_loss(logits, y)
        preds = torch.argmax(logits, dim=1)
        acc = accuracy(preds, y)

        if stage:
            self.log(f'{stage}_loss', loss, prog_bar=True)
            self.log(f'{stage}_acc', acc, prog_bar=True)

    def validation_step(self, batch, batch_idx):
        self.evaluate(batch, 'val')

    def test_step(self, batch, batch_idx):
        self.evaluate(batch, 'test')

    def configure_optimizers(self):
        optimizer = torch.optim.SGD(
            self.parameters(),
            lr=self.hparams.lr,
            momentum=0.9,
            weight_decay=5e-4,
        )
        steps_per_epoch = 45000 // BATCH_SIZE
        scheduler_dict = {
            'scheduler': OneCycleLR(
                optimizer,
                0.1,
                epochs=self.trainer.max_epochs,
                steps_per_epoch=steps_per_epoch,
            ),
            'interval': 'step',
        }
        return {'optimizer': optimizer, 'lr_scheduler': scheduler_dict}

model = LitResnet(lr=0.05)
model.datamodule = cifar10_dm

trainer = Trainer(
    progress_bar_refresh_rate=10,
    max_epochs=30,
    gpus=AVAIL_GPUS,
   accelerator='dp',
    logger=TensorBoardLogger('lightning_logs/', name='resnet'),
    callbacks=[LearningRateMonitor(logging_interval='step')],
)

trainer.fit(model, cifar10_dm)
trainer.test(model, datamodule=cifar10_dm)

The output is hanged after working for just one step of training_step(one batch for each gpu).
Also, even if I press Ctrl+C multiple times, it does not halt. So I had to kill the process by looking up in htop.
I also tried the "boring mode" so it does not seems to be a general pytorch/pytorch-lightining problem but rather a problem with multi-gpus.
-->
Environment

CUDA:
- GPU:
- Tesla V100-SXM2-32GB
- Tesla V100-SXM2-32GB
- Tesla V100-SXM2-32GB
- Tesla V100-SXM2-32GB
- available:         True
- version:           11.1
Packages:
- numpy:             1.21.2
- pyTorch_debug:     False
- pyTorch_version:   1.8.1+cu111
- pytorch-lightning: 1.4.4
- tqdm:              4.62.2
System:
- OS:                Linux
- architecture:
- 64bit
-
- processor:         x86_64
- python:            3.8.10
- version:           #146-Ubuntu SMP Tue Apr 13 01:11:19 UTC 2021

Additional context
Also, If I run the boring model with multi gpus, NCCL_DEBUG=INFO, it gives the message like this
PU available: True, used: True
TPU available: False, using: 0 TPU cores
IPU available: False, using: 0 IPUs
LOCAL_RANK: 0 - CUDA_VISIBLE_DEVICES: [0,1,2,3]
/home/jovyan/user/jinwon/simsiam_mixup/lib/python3.8/site-packages/pytorch_lightning/trainer/data_loading.py:105: UserWarning: The dataloader, train dataloader, does not have many workers which may be a bottleneck. Consider increasing the value of the num_workers argument(try 48 which is the number of cpus on this machine) in theDataLoaderinit to improve performance.   rank_zero_warn( /home/jovyan/user/jinwon/simsiam_mixup/lib/python3.8/site-packages/pytorch_lightning/trainer/data_loading.py:322: UserWarning: The number of training samples (1) is smaller than the logging interval Trainer(log_every_n_steps=50). Set a lower value for log_every_n_steps if you want to see logs for the training epoch.   rank_zero_warn( /home/jovyan/user/jinwon/simsiam_mixup/lib/python3.8/site-packages/pytorch_lightning/trainer/data_loading.py:105: UserWarning: The dataloader, val dataloader 0, does not have many workers which may be a bottleneck. Consider increasing the value of thenum_workers argument (try 48 which is the number of cpus on this machine) in the DataLoader init to improve performance.
rank_zero_warn(
Epoch 0:   0%|                                                                                | 0/2 [00:00<00:00, 5077.85it/s]
sait3-0:30577:30633 [0] NCCL INFO Bootstrap : Using [0]eth0:<IP_ADDRESS><0>
sait3-0:30577:30633 [0] NCCL INFO NET/Plugin : No plugin found (libnccl-net.so), using internal implementation
sait3-0:30577:30633 [0] misc/ibvwrap.cc:63 NCCL WARN Failed to open libibverbs.so[.1]
sait3-0:30577:30633 [0] NCCL INFO NET/Socket : Using [0]eth0:<IP_ADDRESS><0>
sait3-0:30577:30633 [0] NCCL INFO Using network Socket
NCCL version 2.7.8+cuda11.1
And it gets stuck after this. Also, Ctrl+C does not work and I have to kill it manually.

I'm also running into similar issues with similar code

Thanks @saitjinwon, @ia-davidpichler,
Thanks for reporting the bug, I am investigating it right now :)
Best,
T.C

I copy/pasted your code and it seems to work fine for me.
  rank_zero_deprecation(
Epoch 1:  51%|███████████████████████████████████████                                      | 100/197 [00:21<00:20,  4.70it/s, loss=1.32, v_num=0, val_loss=1.590, val_acc=0.440]

Would you mind trying out master: pip install git+https://github.com/PyTorchLightning/pytorch-lightning.git

Currently experiencing this. Updating helped me solve the issue!

Same with me. It's not working on Multiple GPU's. And moreover try ur luck with nn.BCE as loss function for multi-label classification

I'm still getting this intermittently. I think my issues are only present when I log metrics and sync them.

Dear @pratikchhapolika @ia-davidpichler @aleSuglia,
Would you mind provide the exact script causing the hang. The script above works fine for me.
Best,
T.C

Closing for now. @saitjinwon if you come back to this issue (sorry for the delay on this) have a look at #9242 (comment).


feat: Add merge query results functionality to rest_api_query

Summary of Changes
Adding this functionality in support of moving Move Dashboard Extractors to discovery API.
Based on discovery api documents, space discovery api has dashboard_group_id, dashboard_group_name, and dashboard_group_description, while report discovery api has dashboard_id, dashboard_name, dashboard_group_id, and dashboard_description etc.  If we want to extract DashboardMetadata that has all these information in one record, we have to join them based on dashboard_group_id. The purpose of this PR is to address this.
There are some other use cases that we need to merge results as well, for example, total_views_count that lives in report stats discovery api, which we have to merge into the response of report discovery api
Tests
Unit test for QueryMerger
CheckList
Make sure you have checked all steps below to ensure a timely review.

[x] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[x] PR includes a summary of changes.
[x] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[x] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

@feng-tao @dorianj @allisonsuarez @dkunitsk ^^ Let me know if you have any question

@youngyjd could you fix the CI? i could take a look at the PR tonight.

lgtm, any remaining MODE apis are still on legacy?

@feng-tao yeah.
this one https://github.com/amundsen-io/amundsen/blob/ade49021c0ea8a9ff8fa150e89754eb7718db038/databuilder/databuilder/extractor/dashboard/mode_analytics/mode_dashboard_executions_extractor.py#L83. Discovery api only has last execution state but no last execution timestamp. Mode team is addressing it.
and this one https://github.com/amundsen-io/amundsen/blob/ade49021c0ea8a9ff8fa150e89754eb7718db038/databuilder/databuilder/extractor/dashboard/mode_analytics/mode_dashboard_user_extractor.py#L87. Username is missing from mode's discovery api. They are working on it too.


large category number

Apologies if I am not posting this in the correct place, but I'm looking for some help with using datashader for plotting points clustered using DBSCAN. Each cluster has an ID and I would like to colourise each cluster according to its ID. The data is in a Pandas DataFrame and ID column has dtype set to 'category'. Each cluster has a modest number of points but there are typically >500 clusters (the total number of points can be around 1e6) which means >500 different categories.
I am trying to use Holoviews to produce and interactive plot and the bit of code that does the plotting is:
points = hv.Points(clusters, kdims=['x', 'y'], vdims=['cluster_id'])

dynspread(datashade(points, aggregator=ds.count_cat('cluster_id')).opts(width=400, height=400))

This works when the number of clusters is small but fails when I try the full data set:
ValueError: Insufficient colors provided (22) for the categorical fields available (573)
I have tried making a color_key but the datashader colours all seem to have length 256. I tried to interpolate a Matplotlib colour map over all 500 cluster_ids and the code above runs but each point is black (or grey when I zoom).
I'm sure I've missed (or misunderstood) something in the docs so sorry to waste your time if there is a trivial solution.
Thanks!
Dan.

Colorcet.pyviz.org offers 256-color categorical colormaps, and if you need more, you can always concatenate them: import colorcet as cc ; long_key = list(set(cc.glasbey_cool +  cc.glasbey_warm + cc.glasbey_dark)); datashade(..., color_key=long_key). You can also use the glasbey python package to make sets of colors of any length. Either way, you'll get a plot where every category has a different color, but humans are not good at discriminating between so many similar colors, so I would recommend trying to add some hierarchical structure to the categories and then use colors per category in separate plots, or some other way to make the data actually understandable.


How to decode itunes:episode tags

How would one go about decoding a tag with a colon in it, for example:
itunes:episode544</itunes:episode>
Thanks

Hi @RichardAtDP, the colon in the name denotes the presence of the itunes namespace. You could strip it with the shouldProcessNamespaces property on XMLDecoder, as described in README.md. Does that answer your question?

Thanks @MaxDesiatov - I'm wondering how to integrate that option in a Combine pipeline?

Did you check the existing section about Combine? The decoding operator takes a decoder instance as an argument, you can pass your own with shouldProcessNamespaces set as needed.

Got it! Thanks for your help.
For reference
`let decoder = XMLDecoder()
decoder.shouldProcessNamespaces = true
       self.cancellable = URLSession.shared.dataTaskPublisher(for: url)
        .map {  $0.data }
        .decode(type: Response.self, decoder: decoder )
        .catch { err in
            return Just( Response(info:info), error: "\(err)") )
        }
       .replaceError(with: Response(info:info), error: "\(err)") )
       .receive(on: DispatchQueue.main)
       .eraseToAnyPublisher()
       .assign(to: \.response, on: self)`


SAA-1404: Add case note to prisoner profile during de-allocation

Codecov Report
Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (32918d6) 86.93% compared to head (ea7ccaa) 86.94%.
Report is 2 commits behind head on main.

Files
Patch %
Lines

...activitiesmanagementapi/entity/ActivitySchedule.kt
50.00%
0 Missing and 1 partial :warning:

...esmanagementapi/service/ActivityScheduleService.kt
93.33%
0 Missing and 1 partial :warning:

...tivitiesmanagementapi/service/CandidatesService.kt
0.00%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #748      +/-   ##
============================================
+ Coverage     86.93%   86.94%   +0.01%
- Complexity     3430     3435       +5
============================================
  Files           357      358       +1
  Lines         11876    11898      +22
  Branches        998     1000       +2
============================================
+ Hits          10324    10345      +21
  Misses         1084     1084
- Partials        468      469       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


adding input control purpose section

Thanks @htmlandbacon - could you just bump the minor version in the package.json and on the homepage to reflect the change and I'll merge.

will remember for next time!


open-isns: 0.100 -> 0.101

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
Out of tree test used: https://github.com/markuskowa/nix-system/blob/master/tests/isns.nix
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@ofborg eval

@SuperSandro2000 galene on master is still broken

@SuperSandro2000 galene on master is still broken

Going to fix that...

It's rolling again, thanks.


add SetExtraData to CodecParameters to set extradata

For publishing an rtmp stream extradata needs to be set (PPS, SPS h264).

done =)

When pushing a h264 rtmp stream you need to set the H264 SPS/PPS as extra data, its like meta data, so that decoder knows how it can decode it correctly.  =)

Thanks for the PR! ❤
Let me know whether you need a tag 👍

When pushing a h264 rtmp stream you need to set the H264 SPS/PPS as extra data, its like meta data, so that decoder knows how it can decode it correctly. In my case a I got a h264 bytestream from a IP-Camera the first frame is an IDR Frame, this includes the SPS,PPS.

Ha you mean that you're using the Packet.FromData() method and therefore need to manually set the stream's codec parameters extradata whereas when using a FormatContext, it gets filled automatically?

Ha you mean that you're using the Packet.FromData() method and therefore need to manually set the stream's codec parameters extradata whereas when using a FormatContext, it gets filled automatically?

correct =)

Let me know whether you need a tag 👍
thanks no tag needed =)


Replication support for 9.4, with integration tests

This PR introduces a new API for administering replication via a read-write "leader" and read-only "follower." Specifically, the standardized workflow for promoting an existing standalone database to a leader, and creating a new follower database, is:

Activate leader: Run a container with --activate-leader LEADER_URL, also mounting the data volumes of the leader container. This allows for enabling replication either remotely (by the LEADER_URL), or by directly accessing the leader's filesystem. This operation should print all necessary configuration variables to be loaded in (via ENV) to initialize the follower in the next step.
Initialize follower: Run a container with --initialize-follower, in the same way you'd run --initialize on a standalone database. Mount a new set of data volumes for this container, and include all ENV variables printed by --activate-leader in the previous step.
Start follower: Run a container with no arguments, mounting the data volumes of the follower created in the previous step.

On PostgreSQL, these operations are implemented as follows:

Activate leader: Create a new replication-only user, and print its connection URL as REPLICATION_URL.
Initialize follower: Run pg_basebackup and create a recovery.conf file.
Start follower: No special implementation. A PostgreSQL database "knows" whether it is a leader or follower.

A note on the standardized API for replication: it's possible that other database technologies (I'm thinking of MongoDB) will require a fourth step, something like --add-follower, run against the leader, either before or after starting the follower. It would possibly require configuration values printed during the --initialize-follower step, and would register the new follower with the leader.
I'm leaving that detail out of this PR, since it's not a necessary step in the PostgreSQL replication process. I'll take my next stab at MongoDB, and if MongoDB proves that the API needs to be changed, I'll backport any new necessary commands to PostgreSQL (implemented as no-ops).

@aaw and @blakepettersson for comments/suggestions.

Looks great and the bats test is awesome.
Have you thought about the procedure for moving a leader to another instance? It might make sense to make --activate-leader re-runnable with the same user to support that (i.e., running an ALTER ROLE $USERNAME WITH PASSWORD '$PASSPHRASE' with a newly generated passphrase if the user already exists, then dumping the new REPLICATION_URL). Then to move instances, we could mount the data volume on a new instance, re-run --activate-leader on the new leader and then re-run --initialize-follower on each follower with the output of --activate-leader again (assuming pg_basebackup will do the right thing and realize that it should point to a new leader that has a superset of the data the old leader had).

@aaw: Really good points. I have thought a bit about making --activate-leader re-runnable. I definitely think that should be supported.
I'd like to do some further R&D on three open questions, before I give a coherent reply to you:

Test whether a follower will continue to successfully replicate against a leader in the current implementation, if the leader's IP changes (but its hostname remains the same)
Investigate how we can implement promotion of followers to leaders in a PostgreSQL cluster
Implement these subcommands for MongoDB, which has a different, more convoluted clustering model, to see how well the pattern applies to other databases

@krallin: Closing this one out. LMK if you want to adapt it to the --initialize-from API and the DRY, templatized build structure of aptible/docker-redis#10 ad aptible/docker-mysql#15 — or whether you want me to.


Add ncbigene pipeline with new source

[ ] Needs 24GB + memory
[ ] @sabrinatoro to test

Note: I do not have enough memory to run the import refresh. I tried with 16, 20, 25, and 30 GB

@sabrinatoro  Are these the steps you are following: https://mondo.readthedocs.io/en/stable/editors-guide/import-terms-for-logical-axioms/#import-terms-into-mondo-for-use-in-logical-axioms
Let me know if you want me to try since I have more memory available on this laptop.

@sabrinatoro I agree with @twhetzel thats probably for the best for now. I think I can reduce the memory foot print, I have reached out for some help.
In the meantime, I have updated the import so this PR is ready to go.

@sabrinatoro If you like you can try it again, I reduce the memory footprint a bit and it should work withMEMORY_GB=24. But you can also just merge it, let Trish do import refresh in the meantime via SOP and punt making this less memory intensive moving forward.

@twhetzel could you please try running the import, and confirm that it works (ie that we have the non-human genes in Mondo; the list is in the manual_seed.txt which was updated in the PR).
If it works, then merge this PR.

@matentzn I refreshed the imports following this Mondo Docs using this ncbigene-import-full feature branch.
This is the summary of changes:
src/ontology/imports/go_terms.txt        |   2 +
src/ontology/imports/hp_terms.txt        |   1 +
src/ontology/imports/merged_import.owl   | 308 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
src/ontology/imports/ncbitaxon_terms.txt |  14 +++++
I wasn't expecting additional changes since you ran and committed these files. Is this^^ expected?

@matentzn sure, I just pushed those changed files to this PR.

@twhetzel thanmk you, the changes are all expected! Awesome. Ready to merge!


[BUG] nested variable substitution fails

Is there an existing issue for this?

[ ] I have searched the existing issues

Expected Behavior
For the default docker-compose.yml file to work without any modifications
Current Behavior
Nested variable substitution doesn't work for my version of Docker Compose version v2.2.3
So the original config:
environment:
  API_QUERY_URL: "${API_QUERY_URL:-http://localhost:${NB_API_PORT_HOST:-8000}/}"

Needs to be:
environment:
  API_QUERY_URL: "${API_QUERY_URL:-http://localhost:8000/}"

Error message
invalid interpolation format for services.query.environment.API_QUERY_URL: "http://localhost:${NB_API_PORT_HOST:-8000". You may need to escape any $ with another $.
Environment

OS:
Python/Node version:

How to reproduce
No response
Anything else?
No response

This also currently fails on our Arbutus cloud server for Docker Compose version v.2.17.2.
See also https://github.com/docker/compose/pull/5268#issuecomment-1666792510


Removing base62 rust crate

The base62 Rust crate depended on the failure Rust crate, which has a known vulnerability.

Does this need a release note?

Does this need a release note?

@nguerrera Good point. Just added the release notes, and updated the version.


New eval command

It resolves the promise and inspects it with depth 0 (ideal for objects).

I'll make something better, ETA in a moment or tomorrow

Uh sure


Send service check as metric

What does this PR do?
Send the service check as a metric as well: 1 for up status, 0 for others
Motivation
FR
Review checklist

[ ] PR has a meaningful title or PR has the no-changelog label attached
[ ] Feature or bugfix has tests
[ ] Git history is clean
[ ] If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo

Additional Notes
Also 🔥 some ruby leftovers

Codecov Report

Merging #2509 into master will decrease coverage by 8.26%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2509      +/-   ##
==========================================
- Coverage   84.57%   76.31%   -8.27%
==========================================
  Files         631        4     -627
  Lines       35398      114   -35284
  Branches     4302        9    -4293
==========================================
- Hits        29939       87   -29852
+ Misses       4168       22    -4146
+ Partials     1291        5    -1286


Delete extensions directory

@JonathanTylerCombs Can you please explain what your PR is trying to do? Please describe the issue you are trying to fix.

Closing as this doesn't appear to be a real PR.


Some linux subpackages dont have a cuda- prefix

I want to install [libcublas-dev] which doesn't have a cuda- prefix. See here.
Could the action be changed to not always include the cuda- prefix on windows?

you mean on linux?
@Jimver yes please change this.

Yeah on linux, the windows subpackages have sometimes have different names.

Thx for the report! Should be fixed in v0.2.11 by using the non-cuda-sub-packages  argument.

I cannot seem to be able to install a drivers package, e.g. cuda-drivers_520.61.05-1_amd64.deb, there is always a cuda version appended to the end.


Swedish localization

I request Swedish localization.

Localization story is still being worked on

@rustd Can you take a look?

Identity 3 will be localized in the same set of languages ASP.NET 5 will be localized in. I am closing this specific issue as this is tracked all up in general.


docs: fix link to specs

Part of https://github.com/celestiaorg/go-square/issues/15

Pinging @cmwaters @evan-forbes @Wondertan for review.


Ship Stabilization

This may be an issue with the ether compressors, or possibly just a problem with compressors placed on different planes than each other. I find that some of my bigger ships tend to bounce up and down violently with only the compressors acting upon them. It will shoot up to the height it is set to, and then it will fail and fall back down to the ground and repeat. No idea what it is. Perhaps its the strength of the compressors or the weight of the ship itself, but it's pretty irritating to keep the ship controlled

Old issue, closed. This is fixed in the latest jenkins builds.


Logo added

#56
Added logo

@shreyad2806 You messed up the login and signup pages, and this logo isn’t suitable for adding to the website.

@shreyad2806 If you cannot create a decent logo, please close this issue. Otherwise, this logo needs improvement.


How to set 'dis_thr ' correctly?

Hi ,
When I use 'ct.tl.spatial_communication', I noticed that your description of ‘dis_thr’ in the tutorial is 'The threshold of spatial distance of signaling.', but I don't understand what the units of this number are, is it the number of cells? Or um?
And how do I set an appropriate distance for my organization? According to the max area?

Hi, the distance threshold takes the same unit as the spatial coordinates stored in adata.obsm['spatial'].


retrieval of .txt file

Thank you very much for keeping your excellent service! Please let me ask whether I'm using your service incorrectly, or I found a bug.
I'm making a JavaScript tool loading some JSON files (via Fetch API), like:
https://gl.githack.com/mpsuzuki/mj-shrink-map/raw/dd777/index.html

If I fetch JSON files, there is no problem.
But if I load a .TXT file, it fails, like this:
https://gl.githack.com/mpsuzuki/mj-shrink-map/raw/0ee0b/index.html

Following errors were issued in console.

What's wrong? Is there any difference between the handling of .JSON file and .TXT file?

I note: both of ivd-20220913.txt and ivd-20220913.json exist in the repository.
https://gitlab.com/mpsuzuki/mj-shrink-map/-/tree/0ee0b

Hey. That's because of CORS error. All non-supported file types are being redirected to the upstream and thus do not have permissive CORS headers.

I've added support for .txt files in 60b7854, please let me know if it works for you. I myself verified and it works now, just do not forget to clear your browser cache.

Thanks! I've confirmed that now .txt file is properly fetch-able.
Thank you very much for your prompt fix!!


[Speedtest] Update interface to include streaming quality - 12232

Description
The issue - 12232

The interface has been updated to incorporate streaming quality.
It now displays the available quality for both voice/video calls and streaming.
Additionally, in the event of a poor internet connection, a corresponding icon will be displayed.

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Looks good to me. One thing confuse me. Why are all files in the bandwidth folder prefix again with bandwidth? Seems like redundant to me.
Btw: I can not the the runtime behavior for now

Hi there. Thank you for the review.
It makes sense to drop duplicated words. Updated filenames.


Simple operations will report errors. eg "log    ${${0.2}-${1}}"

20211227 15:15:39.701 :  FAIL : Resolving variable '${0.2-1}' failed: SyntaxError: invalid syntax (<string>, line 1)

You are using the extended variable syntax and it is resolved like this:
1.Try to find variable with name 0.2-1. Not found.
2. Find base name for a possible variable that is used with the extended syntax. Base name cannot contain special characters. In this case the base name is 0.
3. Try to find variable with the base name. ${0} exists and is equal to zero.
4. Evaluate expression in Python so that the base name is replaced with a variable containing the value got earlier. This causes a syntax error also in Python:
>>> var = 0
>>> var.2 - 1
  File "<stdin>", line 1
    var.2 - 1
       ^
SyntaxError: invalid syntax

In other words, the problem here is the . character. You could restructure the variable to ${2 / 10 - 1} to avoid it. Alternatively you could use the newish inline Python evaluation syntax and use ${{0.2 -1}}. In this case the expression is evaluated directly in Python.


Correctly handle AR glass in calculateIrradianceThroughCoverDeSoto

This pull request updates the calculateIrradianceThroughCoverDeSoto function to properly handle anti-reflective coated glass. Previously, the function didn't include the AR coating in the calculation of transmittance at normal angles, but it did in calculation of transmittance at angle of incidence. This caused calculated incidence angle modifiers for beam irradiance to be >1. The only model impacted by this change previously was pvwattsv7 because it used that function with an AR glass assumption, but it had a check to make sure that transmitted poa wasn't greater than incident poa, so effects are minimal. However, with the as-yet unreleased switch to assuming AR glass throughout pvwattsv8 and pvsamv1, this bug became very apparent.
This fix adds the effect of AR glass into the transmittance at normal incidence, and also adds checks to make sure that no component IAM is calculated to be > 1. Many tests were updated accordingly. In the process of finding the bug, I also slightly reorganized and updated comments in incidence angle modifier code, removed the unused zenith angle input from the calculateIrradianceThroughCoverDeSoto function, and fixed a bug where using POA irradiance directly never reported reflection losses.
Fixes #669 and fixes #674
I will make a PR for SAM to update test results after this is approved.

Correct, no UI changes, just assumptions in SSC. The CEC database doesn't give us information on whether or not a module is AR coated.


Add PointLight shadow fallback to spot shadow

Comments fixed, still a bit of validation and fixes to do

Validation tests look good final check for @deltakosh and should be good to go.


How runned MZmine3 on computer cluster ?

Basic information
Thank you to all developers for these optimizations.
I have previously run mzMine2on computer cluster, just running ./startMZmine_Linux.sh followed by batch file.
Now, I How to use mzMine3.0.21-beta Linux version batch mode under computer cluster for large sample panel analysis? I have already optimized my parameters on small subsets of data.

My operating system: Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz  2.21 GHz, 16.0 GB (15.8 GB usable)
My MZmine version: MZmine3.0.21-beta

What happened
I have no idea how to install it on a cluster of computers, knowing that I am not an administrator of this computer cluster (just a user). Please do you have any directions/advice/tricks, on how to install it and how to run it?
Thank you

Hey great that you are running MZmine 3. More memory is always nice... But you should be able to run a couple of hundred samples on your machine.
There is a small part in the documentation that might need to be updated. But here is an example how to set the temp folder and run a batch file
"C:\Program Files\MZmine\MZmine.exe" -batch "D:\batch\my_batch_file.xml" -memory none -temp "D:\tmpmzmine"


about dataset

Thanks for sharing the benchmark.
I have submitted the form, I hope you can quickly pass the audit.

Some common issues when filling out the dataset request form:

did not submit the request via your working email
did not specify your employer (or university)
did not provide a meaningful motivation of using the dataset


Remove Ubuntu version pin in check jobs

I guess we're going to have leave the Ubuntu 20.04 pin in place to retain Python 3.6 support.


Folder issues on Windows for test command

Error is thrown for test command when parameter dataset-path contains folder(s) level on Windows:

Are there blanks in the path?
What happens if you put the full path in single quotes?


[Truffle support] Compilation errors

Taken from feedback: https://github.com/nomiclabs/hardhat-vscode-feedback/issues/4
Currently, we only show compilation errors for Hardhat projects. Different tools can compile the same codebase differently, leading to different compilation errors. For example, they may choose to use a different version of solc for a certain source file.
We need to detect when a project is using Truffle and get the compilation errors based on its compilation pipeline, ideally without reimplementing its logic.

We have added an adapter structure that allows other projects (other than hardhat) to be used from the language server.
Support for truffle consists of providing an implementation for this adapter that matches the truffle project structures.


Should we enable discussions on this repo ?

I wonder if we should bother to enable discussions on this repo, as swapping issues and discussions is pretty easy, and would allow to discuss ideas before moving them to real issues.
That would generate an extra forum like for LibreTime, duplicating discourse and I don't know if we have a use for this. I'm not using discourse a lot though, it feels more like we could use a dedicated place to discuss financial/organizational topics without newcomers asking for help (hope this doesn't sound mean towards newcomers).
Or maybe I didn't find any dedicated place were such discussion can happen appart from the (closed source) admin team panel, and the dev topic category on discourse.

My thought is probably not. We can create several new categories in discourse for things that aren't funding requests and issues in this repo for the requests. Even if there is some discussion on the request in the issue, that is fine.


Add Known Environment Canada Open Source Software

Environment Canada Developed a Wiki Entry showing what OSS it had available.
https://www.gcpedia.gc.ca/wiki/Environment_Canada_Use_of_Open_Source_Software

My understanding is that web URL is only be available to internal to GoC users.
I would suggest a general policy of avoiding links on github (and other public source code management platforms) that point to internal-only GoC resources.


chore: add geth metrics

Motivation
We want to compare lodestar's execution engine call duration with geth's metric
Description
Add geth metrics to Execution Engine dashboard

cc @dapplion

@tuyennhv why the huge diff?

@dapplion I don't know how github shows this huge diff, here's in my VsCode

main change is from line 1476 to 1934

updated the Dashboard following #5525 thanks @dapplion 🚀

:tada: This PR is included in v1.9.0 :tada:


Infer functions fail to typecheck (functions don't exist)

Consider the following minimal example (or see the repo):
defmodule InferTypecheckIssue do
  def get(binary), do: Infer.get(binary)
  def get_from_path(path), do: Infer.get_from_path(path)
end

When running dialyzer (via dialyxir v1.4.2), it fails with errors:
$ mix dialyzer
[...snip...]
Total errors: 2, Skipped: 0, Unnecessary Skips: 0
done in 0m0.69s
lib/infer_typecheck_issue.ex:2:unknown_function
Function Infer.get/1 does not exist.
________________________________________________________________________________
lib/infer_typecheck_issue.ex:3:unknown_function
Function Infer.get_from_path/1 does not exist.
________________________________________________________________________________
done (warnings were emitted)
Halting VM with exit status 2

I must admit I have no idea why it happens. I thought that it has something to do with the infer's project config, so I looked at mix.exs but didn't find anything suspicious.

Upon further inspection, seems like this line is the culprit: https://github.com/daskycodes/infer/blob/65beb8673273708718606431706bc9e2d50f7ffb/lib/infer.ex#L14
It breaks dialyzer's analysis:
:dialyzer.run error: Analysis failed with error:
Unable to find type 'fun'/1

This breakage in turn results in dialyzer not finding any function (or callback info for builtin and 3rd-party library behaviours); here's is excerpt of dialyzer's output from our application:
Total errors: 3082, Skipped: 69, Unnecessary Skips: 0
done in 0m7.0s
deps/mox/lib/mox.ex:476:unknown_function
Function Mox.__dispatch__/4 does not exist.
________________________________________________________________________________
lib/application.ex:17:unknown_function
Function :telemetry.attach/4 does not exist.
________________________________________________________________________________
lib/binomo/application.ex:14:unknown_function
Function Logger.__do_log__/4 does not exist.
________________________________________________________________________________
lib/binomo/application.ex:14:unknown_function
Function Logger.__should_log__/2 does not exist.
________________________________________________________________________________
lib/binomo/application.ex:25:unknown_function
Function :telemetry.attach_many/4 does not exist.
________________________________________________________________________________
lib/oban/worker.ex:1:callback_info_missing
Callback info about the Oban.Worker behaviour is not available.
________________________________________________________________________________
lib/phoenix/endpoint.ex:1:callback_info_missing
Callback info about the Plug behaviour is not available.
________________________________________________________________________________
lib/phoenix/endpoint.ex:1:callback_info_missing
Callback info about the Phoenix.Endpoint behaviour is not available.
________________________________________________________________________________
[...snip...]

Success typing should be:
@type matcher_fun() :: (binary() -> boolean())

@smaximov thank you for looking into this. I will prepare a PR and merge it ASAP! 🤝

Closed in https://github.com/daskycodes/infer/pull/12


[Docs] Fix broken links

This patch updates broken links in contributing guide.
Signed-off-by: Juyeong Lee<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #963. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

INFO: You can read if there are misspelled characters at our misspelling check report. Please read http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/963-202102260257120.15884494781494-2b1b305b8cf2c54e4c67bb6cc90dff4658b9684f/report/misspelling_result.txt.

INFO: You can read if there are misspelled characters at our misspelling check report. Please read http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/963-202103021832510.081855058670044-18f260ddcf4749909e6fbb13c6dcb7cab72c170b/report/misspelling_result.txt.


dashboard/config: disable LOCKDEP temporary

We have a number of top crashes related to LOCKDEP:
https://syzkaller.appspot.com/bug?id=a588183ac34c1437fc0785e8f220e88282e5a29f
https://syzkaller.appspot.com/bug?id=63fc8d0501c39609dd2f268e4190ec9a72619563
https://syzkaller.appspot.com/bug?id=8a18efe79140782a88dcd098808d6ab20ed740cc
https://syzkaller.appspot.com/bug?id=3d97ba93fb3566000c1c59691ea427370d33ea1b
https://syzkaller.appspot.com/bug?id=381cb436fe60dc03d7fd2a092b46d7f09542a72a
These are issues related to LOCKDEP itself, rather than LOCKDEP detecting bugs in kernel code.
Currently it stalls fuzzing almost completely, it's the only issues we detect:
2020/09/27 10:48:01 vm-29: crash: WARNING in print_bfs_bug
2020/09/27 10:48:04 vm-23: crash: WARNING in print_bfs_bug
2020/09/27 10:48:08 vm-17: crash: WARNING in print_bfs_bug
2020/09/27 10:48:11 VMs 30, executed 259149, corpus cover 302451, corpus signal 722669, max signal 729949, crashes 139, repro 0
2020/09/27 10:48:22 VMs 30, executed 259619, corpus cover 302469, corpus signal 722905, max signal 730088, crashes 139, repro 0
2020/09/27 10:48:23 vm-16: crash: WARNING in print_bfs_bug
2020/09/27 10:48:32 VMs 30, executed 261726, corpus cover 302847, corpus signal 724972, max signal 732135, crashes 141, repro 0
2020/09/27 10:48:33 vm-30: crash: WARNING in print_bfs_bug
2020/09/27 10:48:40 vm-27: crash: WARNING in print_bfs_bug
2020/09/27 10:48:41 vm-5: crash: WARNING in print_bfs_bug
2020/09/27 10:48:42 VMs 27, executed 263261, corpus cover 303012, corpus signal 726278, max signal 733644, crashes 143, repro 0
2020/09/27 10:48:46 vm-25: crash: WARNING in print_bfs_bug
2020/09/27 10:48:52 vm-19: crash: WARNING in print_bfs_bug
2020/09/27 10:48:52 VMs 27, executed 264768, corpus cover 303215, corpus signal 727455, max signal 734667, crashes 145, repro 0
2020/09/27 10:48:57 vm-34: crash: WARNING in print_bfs_bug
2020/09/27 10:49:01 vm-10: crash: WARNING in perf_group_attach
2020/09/27 10:49:02 VMs 27, executed 265904, corpus cover 303386, corpus signal 728265, max signal 735537, crashes 148, repro 0
2020/09/27 10:49:11 vm-33: crash: WARNING in print_bfs_bug

I think we should disable LOCKDEP for some time until these issues are resolved so that we can find other bugs.

"WARNING in print_bfs_bug" was fixed:
https://syzkaller.appspot.com/bug?extid=62ebe501c1ce9a91f68c
And now we have config parameters to tune lockdep capacity.