Failure to install plugin

$ vagrant plugin install vagrant-vbguest

Installing the 'vagrant-vbguest' plugin. This can take a few minutes...
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

conflicting dependencies fog-core (~> 1.43.0) and fog-core (= 2.1.0)
  Activated fog-core-2.1.0
  which does not match conflicting dependency (~> 1.43.0)

  Conflicting dependency chains:
    fog-core (= 2.1.0), 2.1.0 activated

  versus:
    vagrant-libvirt (> 0), 0.0.41 activated, depends on
    fog-core (~> 1.43.0)

Platform/Version Info
$ uname -r
5.3.0-7625-generic

$ cat /etc/*release*
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=19.10
DISTRIB_CODENAME=eoan
DISTRIB_DESCRIPTION="Pop!_OS 19.10"
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=19.10
DISTRIB_CODENAME=eoan
DISTRIB_DESCRIPTION="Ubuntu 19.10"
NAME="Pop!_OS"
VERSION="19.10"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 19.10"
VERSION_ID="19.10"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=eoan
UBUNTU_CODENAME=eoan
LOGO=distributor-logo-pop-os
NAME="Pop!_OS"
VERSION="19.10"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 19.10"
VERSION_ID="19.10"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=eoan
UBUNTU_CODENAME=eoan
LOGO=distributor-logo-pop-os

Full DEBUG output:
$ VAGRANT_LOG=debug vagrant plugin install --verbose vagrant-vbguest

 INFO global: Vagrant version: 2.2.3
 INFO global: Ruby version: 2.5.5
 INFO global: RubyGems version: <IP_ADDRESS>
 INFO global: VAGRANT_LOG="debug"
 INFO global: VAGRANT_NO_PLUGINS="1"
 INFO global: VAGRANT_DISABLE_PLUGIN_INIT="1"
 WARN global: resolv replacement has not been enabled!
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/providers/hyperv/plugin.rb
 INFO manager: Registered plugin: Hyper-V provider
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/providers/docker/plugin.rb
 INFO manager: Registered plugin: docker-provider
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/providers/virtualbox/plugin.rb
 INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/kali/plugin.rb
 INFO manager: Registered plugin: Kali guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/bsd/plugin.rb
 INFO manager: Registered plugin: BSD-based guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/gentoo/plugin.rb
 INFO manager: Registered plugin: Gentoo guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/esxi/plugin.rb
 INFO manager: Registered plugin: ESXi guest.
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/freebsd/plugin.rb
 INFO manager: Registered plugin: FreeBSD guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/dragonflybsd/plugin.rb
 INFO manager: Registered plugin: DragonFly BSD guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/linux/plugin.rb
 INFO manager: Registered plugin: Linux guest.
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/trisquel/plugin.rb
 INFO manager: Registered plugin: Trisquel guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/tinycore/plugin.rb
 INFO manager: Registered plugin: TinyCore Linux guest.
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/solaris/plugin.rb
 INFO manager: Registered plugin: Solaris guest.
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/alt/plugin.rb
 INFO manager: Registered plugin: ALT Platform guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/windows/plugin.rb
 INFO manager: Registered plugin: Windows guest.
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/darwin/plugin.rb
 INFO manager: Registered plugin: Darwin guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/funtoo/plugin.rb
 INFO manager: Registered plugin: Funtoo guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/solaris11/plugin.rb
 INFO manager: Registered plugin: Solaris 11 guest.
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/slackware/plugin.rb
 INFO manager: Registered plugin: Slackware guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/photon/plugin.rb
 INFO manager: Registered plugin: VMware Photon guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/haiku/plugin.rb
 INFO manager: Registered plugin: Haiku guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/elementary/plugin.rb
 INFO manager: Registered plugin: Elementary guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/amazon/plugin.rb
 INFO manager: Registered plugin: Amazon Linux guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/suse/plugin.rb
 INFO manager: Registered plugin: SUSE guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/debian/plugin.rb
 INFO manager: Registered plugin: Debian guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/arch/plugin.rb
 INFO manager: Registered plugin: Arch guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/redhat/plugin.rb
 INFO manager: Registered plugin: Red Hat Enterprise Linux guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/netbsd/plugin.rb
 INFO manager: Registered plugin: NetBSD guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/atomic/plugin.rb
 INFO manager: Registered plugin: Atomic Host guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/smartos/plugin.rb
 INFO manager: Registered plugin: SmartOS guest.
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/coreos/plugin.rb
 INFO manager: Registered plugin: CoreOS guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/nixos/plugin.rb
 INFO manager: Registered plugin: NixOS guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/pld/plugin.rb
 INFO manager: Registered plugin: PLD Linux guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/openbsd/plugin.rb
 INFO manager: Registered plugin: OpenBSD guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/omnios/plugin.rb
 INFO manager: Registered plugin: OmniOS guest.
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/mint/plugin.rb
 INFO manager: Registered plugin: Mint guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/fedora/plugin.rb
 INFO manager: Registered plugin: Fedora guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/guests/ubuntu/plugin.rb
 INFO manager: Registered plugin: Ubuntu guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/hosts/bsd/plugin.rb
 INFO manager: Registered plugin: BSD host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/hosts/gentoo/plugin.rb
 INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/hosts/freebsd/plugin.rb
 INFO manager: Registered plugin: FreeBSD host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/hosts/linux/plugin.rb
 INFO manager: Registered plugin: Linux host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/hosts/alt/plugin.rb
 INFO manager: Registered plugin: ALT Platform host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/hosts/windows/plugin.rb
 INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/hosts/darwin/plugin.rb
 INFO manager: Registered plugin: Mac OS X host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/hosts/slackware/plugin.rb
 INFO manager: Registered plugin: Slackware host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/hosts/suse/plugin.rb
 INFO manager: Registered plugin: SUSE host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/hosts/arch/plugin.rb
 INFO manager: Registered plugin: Arch host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/hosts/redhat/plugin.rb
 INFO manager: Registered plugin: Red Hat Enterprise Linux host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/hosts/void/plugin.rb
 INFO manager: Registered plugin: Void host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/hosts/null/plugin.rb
 INFO manager: Registered plugin: null host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/provisioners/cfengine/plugin.rb
 INFO manager: Registered plugin: CFEngine Provisioner
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/provisioners/docker/plugin.rb
 INFO manager: Registered plugin: docker
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/provisioners/file/plugin.rb
 INFO manager: Registered plugin: file
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/provisioners/puppet/plugin.rb
 INFO manager: Registered plugin: puppet
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/provisioners/ansible/plugin.rb
 INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/provisioners/salt/plugin.rb
 INFO manager: Registered plugin: salt
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/provisioners/chef/plugin.rb
 INFO manager: Registered plugin: chef
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/provisioners/shell/plugin.rb
 INFO manager: Registered plugin: shell
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/pushes/local-exec/plugin.rb
 INFO manager: Registered plugin: local-exec
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/pushes/atlas/plugin.rb
 INFO manager: Registered plugin: atlas
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/pushes/noop/plugin.rb
 INFO manager: Registered plugin: noop
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/pushes/heroku/plugin.rb
 INFO manager: Registered plugin: heroku
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/pushes/ftp/plugin.rb
 INFO manager: Registered plugin: ftp
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/synced_folders/smb/plugin.rb
 INFO manager: Registered plugin: SMB synced folders
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/synced_folders/rsync/plugin.rb
 INFO manager: Registered plugin: RSync synced folders
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/synced_folders/nfs/plugin.rb
 INFO manager: Registered plugin: NFS synced folders
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/kernel_v1/plugin.rb
 INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/communicators/ssh/plugin.rb
 INFO manager: Registered plugin: ssh communicator
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/communicators/winrm/plugin.rb
 INFO manager: Registered plugin: winrm communicator
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/communicators/winssh/plugin.rb
 INFO manager: Registered plugin: windows ssh communicator
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/version/plugin.rb
 INFO manager: Registered plugin: version command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/reload/plugin.rb
 INFO manager: Registered plugin: reload command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/ssh/plugin.rb
 INFO manager: Registered plugin: ssh command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/winrm/plugin.rb
 INFO manager: Registered plugin: winrm command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/snapshot/plugin.rb
 INFO manager: Registered plugin: snapshot command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/plugin/plugin.rb
 INFO manager: Registered plugin: plugin command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/provider/plugin.rb
 INFO manager: Registered plugin: provider command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/port/plugin.rb
 INFO manager: Registered plugin: port command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/help/plugin.rb
 INFO manager: Registered plugin: help command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/status/plugin.rb
 INFO manager: Registered plugin: status command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/powershell/plugin.rb
 INFO manager: Registered plugin: powershell command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/package/plugin.rb
 INFO manager: Registered plugin: package command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/rdp/plugin.rb
 INFO manager: Registered plugin: rdp command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/suspend/plugin.rb
 INFO manager: Registered plugin: suspend command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/ssh_config/plugin.rb
 INFO manager: Registered plugin: ssh-config command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/halt/plugin.rb
 INFO manager: Registered plugin: halt command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/provision/plugin.rb
 INFO manager: Registered plugin: provision command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/validate/plugin.rb
 INFO manager: Registered plugin: validate command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/winrm_config/plugin.rb
 INFO manager: Registered plugin: winrm-config command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/destroy/plugin.rb
 INFO manager: Registered plugin: destroy command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/list-commands/plugin.rb
 INFO manager: Registered plugin: list-commands command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/up/plugin.rb
 INFO manager: Registered plugin: up command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/global-status/plugin.rb
 INFO manager: Registered plugin: global-status command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/box/plugin.rb
 INFO manager: Registered plugin: box command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/cap/plugin.rb
 INFO manager: Registered plugin: cap command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/resume/plugin.rb
 INFO manager: Registered plugin: resume command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/upload/plugin.rb
 INFO manager: Registered plugin: upload command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/push/plugin.rb
 INFO manager: Registered plugin: push command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/init/plugin.rb
 INFO manager: Registered plugin: init command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/login/plugin.rb
 INFO manager: Registered plugin: vagrant-login
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/cloud/plugin.rb
 INFO manager: Registered plugin: vagrant-cloud
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/kernel_v2/plugin.rb
 INFO manager: Registered plugin: kernel
 INFO vagrant: `vagrant` invoked: ["plugin", "install", "--verbose", "vagrant-vbguest"]
DEBUG vagrant: Creating Vagrant environment
 INFO environment: Environment initialized (#<Vagrant::Environment:0x000055ecc6f62288>)
 INFO environment:   - cwd: /redacted/packer
 INFO environment: Home path: /home/redacted/.vagrant.d
DEBUG environment: Effective local data path:
 WARN environment: No local data path is set. Local data cannot be stored.
 WARN manager: Plugin loading is disabled
DEBUG manager: Enabling globalized plugins
 WARN manager: Plugin initialization is disabled
 WARN manager: Plugin loading is disabled
 INFO loader: Loading configuration in order: [:home, :root]
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG push: finalizing
 INFO environment: Running hook: environment_plugins_loaded
 INFO runner: Preparing hooks for middleware sequence...
 INFO runner: 1 hooks defined.
 INFO runner: Running action: environment_plugins_loaded #<Vagrant::Action::Builder:0x000055ecc770f440>
 INFO environment: Running hook: environment_load
 INFO runner: Preparing hooks for middleware sequence...
 INFO runner: 1 hooks defined.
 INFO runner: Running action: environment_load #<Vagrant::Action::Builder:0x000055ecc763e8b8>
 WARN checkpoint_client: checkpoint library not found. disabling.
 INFO cli: CLI: [] "plugin" ["install", "--verbose", "vagrant-vbguest"]
DEBUG cli: Invoking command class: VagrantPlugins::CommandPlugin::Command::Root ["install", "--verbose", "vagrant-vbguest"]
DEBUG checkpoint_client: waiting for checkpoint to complete...
DEBUG checkpoint_client: no information received from checkpoint
DEBUG root: Invoking command class: VagrantPlugins::CommandPlugin::Command::Install ["--verbose", "vagrant-vbguest"]
 INFO host: Autodetecting host type for [#<Vagrant::Environment: /redacted/packer>]
DEBUG host: Trying: gentoo
DEBUG host: Trying: freebsd
DEBUG host: Trying: alt
DEBUG host: Trying: darwin
DEBUG host: Trying: slackware
DEBUG host: Trying: suse
DEBUG host: Trying: arch
DEBUG host: Trying: redhat
DEBUG host: Trying: void
DEBUG host: Trying: bsd
DEBUG host: Trying: linux
 INFO host: Detected: linux!
 INFO runner: Preparing hooks for middleware sequence...
 INFO runner: 1 hooks defined.
 INFO runner: Running action:  #<Vagrant::Action::Builder:0x000055ecc69d18c8>
 INFO warden: Calling IN action: #<VagrantPlugins::CommandPlugin::Action::InstallGem:0x000055ecc6c55018>
 INFO interface: info: Installing the 'vagrant-vbguest' plugin. This can take a few minutes...
DEBUG bundler: Enabling strict dependency enforcement
DEBUG bundler: Dependency list for installation:
 - vagrant-libvirt > 0
 - vagrant-vbguest > 0
 - bcrypt_pbkdf = 1.0.1
 - bigdecimal = 1.3.4
 - blankslate = 3.1.3
 - builder = 3.2.3
 - childprocess = 0.9.0
 - cmath = 1.0.0
 - concurrent-ruby = 1.0.5
 - csv = 1.0.0
 - date = 1.0.0
 - dbm = 1.0.0
 - did_you_mean = 1.2.1
 - domain_name = 0.5.20160216
 - ed25519 = 1.2.4
 - erubis = 2.7.0
 - etc = 1.0.0
 - excon = 0.60.0
 - fcntl = 1.0.0
 - ffi = 1.9.10
 - fiddle = 1.0.0
 - fileutils = 1.0.2
 - fog-core = 2.1.0
 - fog-json = 1.2.0
 - fog-libvirt = 0.6.0
 - fog-xml = 0.1.1
 - formatador = 0.2.5
 - gdbm = 2.0.0
 - http-cookie = 1.0.3
 - i18n = 0.7.0
 - io-console = 0.4.6
 - ipaddr = 1.2.0
 - json = 2.1.0
 - listen = 3.1.5
 - log4r = 1.1.10
 - mime-types = 3.2.2
 - mime-types-data = 3.2015.1120
 - minitest = 5.11.3
 - multi_json = 1.12.1
 - net-scp = 2.0.0
 - net-sftp = 2.1.2
 - net-ssh = 5.2.0
 - net-telnet = 0.1.1
 - netrc = 0.11.0
 - nokogiri = 1.10.3
 - oj = 3.8.1
 - openssl = 2.1.2
 - pkg-config = 1.3.8
 - power_assert = 1.1.1
 - psych = 3.0.2
 - rake = 12.3.1
 - rb-inotify = 0.9.10
 - rdoc = 6.0.1
 - rest-client = 2.0.2
 - ruby-libvirt = 0.7.1
 - rubyzip = 1.2.2
 - scanf = 1.0.0
 - sdbm = 1.0.0
 - sqlite3 = 1.3.13
 - stringio = 0.0.1
 - strscan = 1.0.0
 - test-unit = 3.2.8
 - unf = 0.1.4
 - unf_ext = <IP_ADDRESS>
 - vagrant = 2.2.3
 - vagrant_cloud = 2.0.2
 - webrick = 1.4.2
 - xmlrpc = 0.3.0
 - zlib = 1.0.0
DEBUG bundler: Enabling user defined remote RubyGems sources
DEBUG bundler: Enabling default remote RubyGems sources
DEBUG bundler: Adding source - https://gems.hashicorp.com/
DEBUG bundler: Adding source - https://rubygems.org/
DEBUG bundler: Current source list for install: ["https://gems.hashicorp.com/", "https://rubygems.org/"]
DEBUG bundler: Generating new builtin set instance.
DEBUG bundler: Generating new plugin set instance. Skip gems - []
DEBUG bundler: Generating solution set for installation.
ERROR warden: Error occurred: Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

conflicting dependencies fog-core (~> 1.43.0) and fog-core (= 2.1.0)
  Activated fog-core-2.1.0
  which does not match conflicting dependency (~> 1.43.0)

  Conflicting dependency chains:
    fog-core (= 2.1.0), 2.1.0 activated

  versus:
    vagrant-libvirt (> 0), 0.0.41 activated, depends on
    fog-core (~> 1.43.0)

 INFO warden: Beginning recovery process...
 INFO warden: Calling recover: #<VagrantPlugins::CommandPlugin::Action::InstallGem:0x000055ecc6c55018>
 INFO warden: Recovery complete.
 INFO environment: Running hook: environment_unload
 INFO runner: Preparing hooks for middleware sequence...
 INFO runner: 1 hooks defined.
 INFO runner: Running action: environment_unload #<Vagrant::Action::Builder:0x000055eccdb594a0>
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::BundlerError: Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

conflicting dependencies fog-core (~> 1.43.0) and fog-core (= 2.1.0)
  Activated fog-core-2.1.0
  which does not match conflicting dependency (~> 1.43.0)

  Conflicting dependency chains:
    fog-core (= 2.1.0), 2.1.0 activated

  versus:
    vagrant-libvirt (> 0), 0.0.41 activated, depends on
    fog-core (~> 1.43.0)

>
ERROR vagrant: Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

conflicting dependencies fog-core (~> 1.43.0) and fog-core (= 2.1.0)
  Activated fog-core-2.1.0
  which does not match conflicting dependency (~> 1.43.0)

  Conflicting dependency chains:
    fog-core (= 2.1.0), 2.1.0 activated

  versus:
    vagrant-libvirt (> 0), 0.0.41 activated, depends on
    fog-core (~> 1.43.0)

ERROR vagrant: /usr/share/rubygems-integration/all/gems/vagrant-2.2.3/lib/vagrant/plugin/manager.rb:172:in `rescue in install_plugin'
/usr/share/rubygems-integration/all/gems/vagrant-2.2.3/lib/vagrant/plugin/manager.rb:116:in `install_plugin'
/usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/plugin/action/install_gem.rb:30:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.2.3/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.2.3/lib/vagrant/action/builder.rb:116:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.2.3/lib/vagrant/action/runner.rb:66:in `block in run'
/usr/share/rubygems-integration/all/gems/vagrant-2.2.3/lib/vagrant/util/busy.rb:19:in `busy'
/usr/share/rubygems-integration/all/gems/vagrant-2.2.3/lib/vagrant/action/runner.rb:66:in `run'
/usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/plugin/command/base.rb:14:in `action'
/usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/plugin/command/install.rb:70:in `block in execute'
/usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/plugin/command/install.rb:69:in `each'
/usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/plugin/command/install.rb:69:in `execute'
/usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/commands/plugin/command/root.rb:66:in `execute'
/usr/share/rubygems-integration/all/gems/vagrant-2.2.3/lib/vagrant/cli.rb:58:in `execute'
/usr/share/rubygems-integration/all/gems/vagrant-2.2.3/lib/vagrant/environment.rb:291:in `cli'
/usr/share/rubygems-integration/all/gems/vagrant-2.2.3/bin/vagrant:177:in `<top (required)>'
/usr/bin/vagrant:23:in `load'
/usr/bin/vagrant:23:in `<main>'
 INFO interface: error: Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

conflicting dependencies fog-core (~> 1.43.0) and fog-core (= 2.1.0)
  Activated fog-core-2.1.0
  which does not match conflicting dependency (~> 1.43.0)

  Conflicting dependency chains:
    fog-core (= 2.1.0), 2.1.0 activated

  versus:
    vagrant-libvirt (> 0), 0.0.41 activated, depends on
    fog-core (~> 1.43.0)

Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

conflicting dependencies fog-core (~> 1.43.0) and fog-core (= 2.1.0)
  Activated fog-core-2.1.0
  which does not match conflicting dependency (~> 1.43.0)

  Conflicting dependency chains:
    fog-core (= 2.1.0), 2.1.0 activated

  versus:
    vagrant-libvirt (> 0), 0.0.41 activated, depends on
    fog-core (~> 1.43.0)

 INFO interface: Machine: error-exit ["Vagrant::Errors::BundlerError", "Bundler, the underlying system Vagrant uses to install plugins,\nreported an error. The error is shown below. These errors are usually\ncaused by misconfigured plugin installations or transient network\nissues. The error from Bundler is:\n\nconflicting dependencies fog-core (~> 1.43.0) and fog-core (= 2.1.0)\n  Activated fog-core-2.1.0\n  which does not match conflicting dependency (~> 1.43.0)\n\n  Conflicting dependency chains:\n    fog-core (= 2.1.0), 2.1.0 activated\n\n  versus:\n    vagrant-libvirt (> 0), 0.0.41 activated, depends on\n    fog-core (~> 1.43.0)\n\n"]

Thanks for the details report, but this is not a vbguest issue. vbguest has no dependencies which cause this conflict.
Try cleaning up your plugins (repair / uninstall / expunge) or deleting the entire  ~/.vagrant.d/gems directory and reinstall them.


Tidy up the code of events

Objective

The code in events.rs was a bit messy. There was lots of duplication between EventReader and ManualEventReader, and the state management code is not needed.

Solution

Clean it up.

Future work
Should we remove the type parameter from ManualEventReader?
It doesn't have any meaning outside of its source Events. But there's no real reason why it needs to have a type parameter - it's just plain data. I didn't remove it yet to keep the type safety in some of the users of it (primarily related to &mut World usage)

I would also suggest moving the impl EventReader block closer to the struct declaration. It's the only one in the file that doesn't follow this pattern and it feels a bit weird.

bors r+


Windows file manager tab system

Description of the new feature / enhancement
easy copy and move
Scenario when this would be used?
faster working Experience and no additional app is used
Supporting information
No response

/dup https://github.com/microsoft/PowerToys/issues/10


Info banner on cluster repo list page does not close when prompted

Rancher version:
Rancher 2.6.1

Browser type & version:
Firefox 78.13.0esr

Describe the bug
On the Cluster Repo List page the banner at the top does not close when prompted.
Also errors in the console point to the issue of the handler for the close event isn't defined.
To Reproduce

Navigate to cluster => Apps & Marketplace => Repositories
Try to close info banner above the list

Result
The banner does not close
Expected Result
The banner should close
Screenshots
https://user-images.githubusercontent.com/40806497/136951676-4de4d22c-706f-4d5a-8984-5eaff631553f.mp4
(Errors in console)

My checks PASSED
Reproduction Steps
Not required.

Validation Environment

Component
Type / Version

Rancher version:
v2.6-931a0f09d0f85ade0dcaa8fbe9d6e0c58ae52bbc-head

Rancher cluster type
Single Node Docker Install

Docker version
20.10.7, build 20.10.7-0ubuntu1~20.04.2

Helm version
v2.16.8-rancher1

Downstream cluster type
Custom RKE Linode

Downstream K8s version
v1.21.5-rancher1-1

Cloud credentials
Linode API Token setup prior to steps

Browser Type
Google Chrome

Browser Version
95.0.4638.69 (Official Build) (x86_64)

Validation steps

Starting from the default Rancher homepage /dashboard/home
Click hamburger menu -> Under EXPLORE CLUSTER click local -> Apps & Marketplace -> Repositories
Now click the X on the info banner that's displaying this message:

A chart repository is a Helm repository or Rancher git based application catalog. It provides the list of available charts in the cluster. Cluster Templates are deployed via Helm charts.

The message now closes successfully :rocket:


Fix typos

Fix typos
Fix typos
Checklist

[no] Unit tests written
[no] Manually tested
[no] Prettier & ESLint were run
[no] New dependencies are included in package-lock.json

Deployed to: http://staging.quran.com:32839

Salam Alykom, the link is broken!


Fix favourites process list

Summary
The 'Star'-ing of processes used to work, however, the latest refactor of the process list seems to have reverted it back to the nonfunctional display.
It now works again.

Details

[ ] TODO: Once #250 is merged, the sorter function of the Favourite-Column needs to be wrapped with the Folder-Aware wrapper.

#283 was merged now.


aurora color scheme html

I am using aurora colorscheme and I want to get rid of the extremely bright yellow color as shown in the picture. I tried tweaking aroudn with my common sense but didn't get desired results. Can anyone tell how do I achieve it?

see what this highlight is called and correct that highlight to your desired color. that setting might be something like
vim.cmd('set highlightname=#COLOR')

or similar i'm not totally sure but it should work.

see what this highlight is called and correct that highlight to your desired color. that setting might be something like
vim.cmd('set highlightname=#COLOR')

or similar i'm not totally sure but it should work.

thanks for helping, but this doesn't work either.


Increase time to timeout on azure

Increasing the timeout time from 60 minutes to 120 minutes on azure pipeline per

https://docs.microsoft.com/en-us/azure/devops/pipelines/process/phases?view=azure-devops&tabs=yaml#timeouts

This should be plenty, but according to the documentation, the timeoutInMinutes can be increased to 360 minutes for public projects:
For 360 minutes (6 hours) on Microsoft-hosted agents with a public project and public repository

Only 33% of the azure builds have succeeded in the last 7 days and 38% have succeeded in the last 30 days. I haven't checked, but I suspect many of those failures were related to timing out.

@rgommers what do you think?

I would merge both as I've had more than one build timeout over the last day due to other azure jobs than the prerelease_deps_coverage_64bit_blas one. It was the main issue, but after #16122 I've been seeing other azure pipeline jobs timing out.


Allow multiple edge type creation

Hi Sebastian,
To allow multiple edge type creation in association classes of config file, I did some changes in BioCypher script.
Right now one can create multiple edge types using this type of structure in config file:
protein to cellular component association:
  represented_as: edge
  label_as_edge: [located_in, part_of, is_active_in]
  preferred_id: id
  source: protein
  target: cellular component
  label_in_input: [protein_located_in_cellular_component, protein_part_of_cellular_component, protein_is_active_in_cellular_component]
  properties:
    reference: str
    evidence_code: str

Instead of this:
protein to cellular component association loc:
  represented_as: edge
  label_as_edge: protein_located_in_cellular_component
  preferred_id: id
  source: protein
  target: cellular component
  label_in_input: protein_located_in_cellular_component
  properties:
    reference: str
    evidence_code: str

protein to cellular component association part:
  represented_as: edge
  label_as_edge: protein_part_of_cellular_component
  preferred_id: id
  source: protein
  target: cellular component
  label_in_input: protein_part_of_cellular_component
  properties:
    reference: str
    evidence_code: str

protein to cellular component association active:
  represented_as: edge
  label_as_edge: protein_is_active_in_cellular_component
  preferred_id: id
  source: protein
  target: cellular component
  label_in_input: protein_is_active_in_cellular_component
  properties:
    reference: str
    evidence_code: str

In my opinion, this option was crowding config file and was error prone.
In my changes, I used label_in_input field to map BioCypher's ontological backbone. So, it should be unique among all label_in_input edge types. And I used label_as_edge field to display edge label of corresponding label_in_input field in graph db. In addition to that, PR's script create csv files for each association class for edges (e.g., ProteinToCellularComponentAssociation-header.csv, ProteinToCellularComponentAssociation-part000.csv). If I continue with previous csv file creation approach, it would have caused issues. For example, Protein-Go and Protein Domain-Go edges may have same edge labels (label_as_edge) but not the same properties. This may create inconsistency in csv creation. Also, this may create csv file abundance if someone wants create multiple edge types for many association classes.
I tested these functionalities in fairly complex data that is composed of Protein-Go, Go-Go, Domain-Go edges. It looks like it works fine. Still, there is a possibility that I may have made mistakes and there is also room for improvement. So, I would appreciate it if you could review and check my PR.

Hi Bünyamin,
many thanks for the PR; I'll review it ASAP. :)

@bnymnsen could you please add specific tests for the functionality you added (and update existing tests if necessary)?

Hi again, after a long time 😢
Finally, I finished the tests for for write.py, translate.py and create.py scripts. I updated test scripts for  write.py and translate.py. Except the write.py, other two works fine. In write.py, tests run fine except for the tests related to BioCypherRelasNode functionality. Since I broke this functionality, I need to a bit of time figure out how to solve this. However, I want to ask, currently my PR is outdated, does this create any problem? If you want, I can update this PR for current version of BioCypher.

Hi @bnymnsen,
don't worry; I was planning to do some additional refactoring looking at the work @deeenes has done on dev, which also overlaps with your proposal. I think I will take the code of both and combine it in a separate feature branch once there is time (probably after resubmission of the manuscript). You can use your time better on the CROssBAR implementation. :)

Closing since this has been implemented in the course of the refactoring. Thanks again for the PR, and sorry for not being able to merge.


[FEATURE] Add an "echo" endpoint to the default app that responds with the details of the request

CDNs often have quirks in terms of how they forward requests to origins.
When customers stack a CDN on MRT, we often debug request forwarding issues To debug issues with forwarding, we often suggest customers add an "echo" endpoint to ssr.js to their apps:
// ssr.js
app.all('/reflect', function echoHandler({method, path, headers, body}, res) {
  return res.send({method, path, headers, body})
})

It would be nice if we included this endpoint by default in apps with an environment variable toggle so folks could enable it without a code change.
This would simplify debugging many of these issues!

Hi @johnboxall  👋
Sounds like a good idea. I'm wondering is something like this might be a little more future-proof.
// ssr.js

import {devMiddleware} from `pwa-kit-react-sdk`

...

if (!env.isProduction || env.enableServerDevEnpoint) {
    app.use(devMiddleware())
}

Here we can add your suggested reflect endpoint under a common /__dev path. This would allow use to add more end-points with out worrying about coming up with pathnams that might collide with user defined ones. Another idea might be /__dev/info that would give the user and us details about the version of sdk/node/etc they are using.

@bendvc – your suggestion about not conflicting with is a good one.
Instead of introducing a new path, we could extend the current convention of /mobify/ping and friends with /mobify/reflect. Alternatively, we could even extend ping to provide this information.
One key part of my suggestion is that ideally this endpoint is available across all environments (including production ones!) and can be enabled without a code change – so I'm imagining something that is default off, but can be enabled using an MRT environment variable (eg. MRT_REFLECT_ENABLED=$TRUTHY)


How to modify loadResult when grouping

Hi,
I need to modify loadResult data to set some fields after filtering (for ex.: I need to get Product with it's actual and previous price. So, I need to get all products, call Load() to filter data and then find the previous price). Of cource, I can set data before calling Load method, but what if I need just 10 Products, but I need to set previouse price for all products, which cause some perfomance issues.
As I can see, I can modify LoadResult.data when there is no grouping, but how to modify result with grouping?

if I need just 10 Products, but I need to set previouse price for all products, which cause some perfomance issues.

Is is possible to add a lazy-evaluated computed property?
[NotMapped]
public decimal PrevPrice {
    get { return FigureOutPrevPrice(...); }
}

As I can see, I can modify LoadResult.data when there is no grouping, but how to modify result with grouping?

What is the exact problem you have encountered?

Is is possible to add a lazy-evaluated computed property?

Unfortunately, no, because this prtopery is calculated with recursive function

As I can see, I can modify LoadResult.data when there is no grouping, but how to modify result with grouping?

What is the exact problem you have encountered?
As I can see, LoadRuslt data property can be dyncamic, expando object or collection of type Group. So, when the dxDataGrid was grouped by some field it makes 2 request, on the second requests data where I can modify data property after call Load method.

The real issue is export data to excel, it makes only 1 request and Result data type is collection of  Group and I don't see the actual Product objects. Remote paging and grouping are enabled.

@AlekseyMartynov, sorry, closed by mistake

Ended up with this recusrsive method:
private List<Product> GetData(object data, List<Product> objects)
        {
            if (objects == null)
                objects = new List<Product>();

            var collection = data as IEnumerable<object>;

            if (collection != null)
            {
                foreach (var item in collection)
                {
                    var r = item as Product;

                    if (r != null)
                        objects.Add(r);
                    else
                    {
                        var group = item as Group;
                        if (group != null && group.items != null)
                        {
                            foreach (var it in group.items)
                            {
                                var f = it as Product;
                                if (f != null)
                                    objects.Add(f);
                                else
                                {
                                    if (it is Group)
                                    {
                                        var g = it as Group;
                                        return GetModels(g, objects);
                                    }
                                }
                            }
                        }
                    }
                }
            }

            return objects;
        }

I have a generic method that may help here. I use it like this in my controllers specifically for my projections as described in https://github.com/DevExpress/DevExtreme.AspNet.Data/issues/367#issuecomment-573893506.
The translator is any method accepting a List of the projected type, and returning the same. Should be pretty easy to modify for any other purpose.
    public async Task<IActionResult> GetEntitiesForProjectAsync<TDto>(DataSourceLoadOptions loadOptions, Func<List<TDto>, Task<List<TDto>>> translator) where TDto : class
    {
        var ProjectEntities = await GetLoadResultForProjectAsync<TDto>(loadOptions);//<=just a call to DataSourceLoader.LoadDtoAsync - refer https://github.com/DevExpress/DevExtreme.AspNet.Data/issues/367#issuecomment-573893506
        if (ProjectEntities is LoadResult lr && lr.data is IEnumerable data)
        {
            lr.data = await TranslateLoadResultDataAsync<TDto>(data, translator);
            return Ok(lr);
        }
        return new OkObjectResult(ProjectEntities);
    }

The method
public async Task<IList> TranslateLoadResultDataAsync<TDto>(IEnumerable lstData, Func<List<TDto>, Task<List<TDto>>> translator)
    {
        if (lstData == null) return null;
        if (lstData is IEnumerable<T> lstBaseTypeData)
        {
            lstData = _mapper.Map<List<T>, List<TDto>>(lstBaseTypeData.ToList());
        }
        if (lstData is IEnumerable<TDto> lstDtoTypeData)
        {
            var lst = lstDtoTypeData.ToList();
            return await translator(lst);
        }
        if (lstData is IEnumerable<Group> lstGroupData)
        {
            var lst = lstGroupData.ToList();
            foreach (Group group in lst)
            {
                group.items = (await TranslateLoadResultDataAsync<TDto>(group.items, translator));
            }
            return lst;
        }
        //any other case
        var lstObject = new List<object>();
        foreach (object o in lstData)
        {
            lstObject.Add(o);
        }
        return lstObject;
    }

@statler The code snippets above, aren't complete. Can you please revise?

@krptodr
Please be more specific about what you think is missing. I am pretty sure everything is there, or referenced as described by the comment to #367 for GetLoadResultForProjectAsync

@statler I can’t piece the two tickets together. I think that function is missing. Do you have an example you can provide in DevExpress example format? I’d really appreciate leveraging you’re idea from ticket #367 and here for the grouping.

If someone can give me a clean working basic webapi asp.net core 2 project (no asp.net views - just the webapi) for the northwind db with entity framework .core 2, I will have a chop at it. The devex examples are not .Net Core, and not really relevant to this.


k8s nodes and NAT

I have a cluster made up of ubuntu nodes <IP_ADDRESS>("ai") <IP_ADDRESS> ("i")
I am trying to add a k8s node ("<IP_ADDRESS>")  that is behind a NAT gateway.
The k8s node is translated as "<IP_ADDRESS>" in the "192.168.1.x" network.
Is this supported? What configuration changes do I need to make to get this to work?

Have you tried it and found it to be a problem?  With things like this it
is sometimes difficult to predict what will or won't work.  If it is a
1-to-1 NAT I suspect it will be transparent to us, as long as you add the
Node with the NAT IP and not the native IP.
On Wed, Jul 15, 2015 at 8:34 PM, shankeriyer<EMAIL_ADDRESS>wrote:

I have a cluster made up of ubuntu nodes <IP_ADDRESS>("ai") <IP_ADDRESS>
("i")
I am trying to add a k8s node ("<IP_ADDRESS>") that is behind a NAT gateway.
The k8s node is translated as "<IP_ADDRESS>" in the "192.168.1.x" network.
Is this supported? What configuration changes do I need to make to get
this to work?
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/11359.

I have tried 2 scenarios
(a) with kube_up i configure my cluster to have a k8s node with an IP of <IP_ADDRESS>.
I find that the k8s nodes tries to bind to the <IP_ADDRESS> address and there are errors in the log
(b) Next I want to try a kubeup without the "<IP_ADDRESS>" node and try to add the node after the cluster is up with the local nodes. Here I need to modify the /etc/default/kubelet  /etc/default/etcd on the "<IP_ADDRESS>" node to ensure that it binds to its local internal address for the services it exposes but then the masters tries to talk back to it on "<IP_ADDRESS>" which is not possible

It sounds like there's some work to be done to make this work then, sorry.  It doesn't sound like a very common case, so we didn't cover it automatically.

Wonder if etcd needs a combinations of the right set of parameters to get this working
viz. --initial-advertise-peer-urls => should have the translated so that the rest of the networks can access
--listen-peer-urls should have the local ip's
and the infra should have the correct IP addresses depending on the location of the peers
Will try it out and update this thread

@shankeriyer , I decided to deploy one etcd instance per node to get a high availabilty.You can just run one etcd on master, this would be simpler for your case I assume.But I'm not sure behind a nat, a k8s master can find node or not...You can give it a shot.

Not sure whether you can configure it or not , I will give you a help link use docker to deploy k8s.  https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/getting-started-guides/docker-multinode/master.md. Hope it helps

It just use one etcd instance and avoid etcd trick settings

+cc @cjcullen

This seems like a very niche use case - I am not sure we want to go out of our way to make this better, unless such changes are good overall for other reasons.

to run K8s in a IoT/m2m use case this would be a typical scenario where you have just one "Gateway" node. Once you can reach this gateway Node K8s could create some kind of policy managed overlay network for the applications. But the external etcd should be available I assume.
BTW: IPv6 could be a option to once deployed more widely. How ist the IPv6 support these days?


no option for terminationGracePeriodSeconds

In a call w/ posit they told me that there is a issue where kubernetes might kill a pod before it can finish deactivating the license. To prevent that I should let the pod run for two minutes before killing it. I'm presuming to do that I would set terminationGracePeriodSeconds. However, there is no option to pass that into the helm values, and I don't use kustomize. Can that option be added in please?

Howdy @Almenon ! Yes, this sounds like a great option to add, thanks for sending this across!


Adding some more icons for filenames and extensions

Hello, I hope you all are doing well. I committed to this repository a little over a year ago, when I made a pull request like this one, suggesting ideas for icons. Many of these icon -> extension associations were taken from eza, because that project has many icons that this project does not have yet. I have a pull request pending on that repo, too. Please look over my changed file, but to save you some time here's the summary of what I've done:

Found a better (larger and clearer) Rust icon, so I changed that (\u{e68b})
Set emacs config files (config.el, packages.el etc.) to use the actual Emacs icon instead of GNU head for Emacs files (\u{e632})
Perl language extensions (.pl, .pm, .pod, .plx) now use the camel instead of the... circle (\u{e67e})
Added OCAML extensions (.ml, .mli, .mll)
Added many Go and Gradle filenames
Added separate key icons for public keys (extensions) and private keys (filenames)
Added a kitty cat for Yarn configuration files
Switched all the Bash, Zsh, and Csh filenames to use a shebang icon, instead of the command prompt

You will notice I changed many of the existing icons in place for standard folder/directory name matches, such as in the home directory ("Pictures", "Music", "Downloads" now are actual folder icons) and in the root directory ("bin", "src"). These are in a separate commit, so if you aren't feeling those particular icons, we can roll it back to how those icons were before.
Thank you very much for your time. I welcome any and all feedback, and I will make more commits if necessary.
For reference

Codecov Report

Merging #929 (b17e9cd) into master (ae1a2cd) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@           Coverage Diff           @@
##           master     #929   +/-   ##
=======================================
  Coverage   85.74%   85.74%
=======================================
  Files          51       51
  Lines        5003     5003
=======================================
  Hits         4290     4290
  Misses        713      713

Files
Coverage Δ

src/theme/icon.rs
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Hello, I have fixed the CI tests.

hi @Babkock, thanks for contributing, but I would prefer to keep the origin icons if there is no strong reasons to change

hi @Babkock, thanks for contributing, but I would prefer to keep the origin icons if there are no strong reasons to change them, it may break the existed users

Which original icons, specifically? I think the Rust, subtitle, and Emacs icon changes should stay; are you talking about those, or the ones for Music, Downloads, Pictures, etc.?

Hi @Babkock, thanks so much for contributing, all the icons look great but the src, the new icon seems to be less expressive than the origin one.
and we could also change the sbin folder to the icon bin used here https://github.com/lsd-rs/lsd/pull/929/files#diff-5e5b98f7f3576b07a63f44e581ef0ddfa6829569af86bac0231b330cca0a357eL290

Hi @Babkock, thanks so much for contributing, all the icons look great but the src, the new icon seems to be less expressive than the origin one.
and we could also change the sbin folder to the icon bin used here https://github.com/lsd-rs/lsd/pull/929/files#diff-5e5b98f7f3576b07a63f44e581ef0ddfa6829569af86bac0231b330cca0a357eL290

I think I wanted the src directory to have a folder icon that matches the others, i.e. one that looks like a folder. The little wrench matches the wrench for the other files meson.build and configure. I can change it back to the generic XML icon </> aka \u{f121} if that is what you want. I am not sure what you are referencing with the sbin? sbin and bin both have the same icon, the gear folder \u{e5fc}, at least in my fork they do.
I have pushed some fixes, and added a couple icons that were missing.

to have a folder icon that matches the others

I agree with you on this one,

The little wrench matches the wrench for the other files

but not this one.
I also seek for a better one but failed.

for the sbin icon, I refer to this line you added https://github.com/lsd-rs/lsd/pull/929/files#diff-5e5b98f7f3576b07a63f44e581ef0ddfa6829569af86bac0231b330cca0a357eR428 ("bin", "\u{eae8}"), // "" the eae8 with 0101 seem great for bin and sbin, but like the previous comment, it also does not have a folder sign

for the sbin icon, I refer to this line you added https://github.com/lsd-rs/lsd/pull/929/files#diff-5e5b98f7f3576b07a63f44e581ef0ddfa6829569af86bac0231b330cca0a357eR428 ("bin", "\u{eae8}"), // "" the eae8 with 0101 seem great for bin and sbin, but like the previous comment, it also does not have a folder sign

Ohh, okay. So that bin icon (the eae8 0101) is with the extensions, so that icon is only supposed to go with filenames like bootloader.bin or kernel.bin, stuff like that. But for exact filename matches, bin and sbin both have the gear folder icon e5fc. I do not believe sbin should be with the file extensions.
I apologize for any confusion. Are we on the same page? Did I address your concern? Is there anything you would like me to change?


Animation support for switching views

Is your feature request related to a problem? Please describe.
The switch between views is very abrupt.
Describe the solution you'd like
It would be nice to have the possibility to animate the transition.
A solution similar to the one that the Vaadin Router (Section "Animated Route Transition") provides would be awesome.
That way one could simply implement the CSS transition he wants.
Describe alternatives you've considered
None

Doesn't the UI::navigate actually use the Vaadin Router? If so, is there currently an API to do as you described?

Thank you for the hint, I asked in the Vaadin Forums if it is possible using flow: Thread. If this would work out of the box it would be very nice of course.

Possibly can be solved by using the compani addon


selinux: Use events in the selinux controller

What would you like to be added:
decorate the selinux policy controller with events.
Why is this needed:
It was suggested in PR#214 that the selinux controller should use events so that admins are aware of what has happened.

/assign

/assign

@naveensrinivasan are you still planning on working on this issue?

Sorry I am not planning to. Thanks

/assign


Improve share sensors dropdown

Description:
Looks like when checking share sensors dropdown list with iOS Safari and scrolling on page makes the list jump. Maybe this can be improved.

QA passed


Distributed cleanup

Salvage dask.distributed commits from #180

Errors in this PR are due to a pandas 0.16.1 change https://github.com/pydata/pandas/issues/10106


Fix code generation for rt-template siblings.

Taken from wix/react-templates#164.

Going to do this in a separate branch since my fork has diverged significantly from upstream.


Problem finding Path

My Environment

[X ] Windows 10

My issue is related to (check only those which apply):

[X] settings.txt

Expected Behavior
Change node version
Actual Behavior
Cannot find the path correctly
Steps to reproduce the problem:
use the command nvm use 6.10.3
C:\Users\Denis Policastro>nvm use 6.10.3
exit status 1: 'C:\Users\Denis' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
I think there is a problem in the settings.txt, when the nvm doesn't recognize my path cause it have a space in my <USER>

I also have this issue.
exit status 1: 'C:\Users\Ben' is not recognized as an internal or external command, operable program or batch file.

I'm currently facing the same issue using nvm use 8.0.0 command line after having installed Node v8.0.0 with Cmder (cmd.exe with admin privileges) in Microsoft Windows 10.

Duplicate #41 - also see https://github.com/coreybutler/nvm-windows/wiki/Common-Issues#spaces-in-pathnamesinstallation-root


"No game found" if you try to download icons from SteamGridDB

If I try to download updated icons for installed applications (both Better xCloud shortcuts and Android games), a 'No game found' alert is displayed
https://github.com/likeich/console-launcher/assets/19996309/ebd3aee0-1ed9-4776-9f80-5a0673f75d49
Problem encountered with the latest v112.0.0-alpha8 release. Previously used the Play Store stable and it worked regularly.

Fixed in the latest update (alpha 9)


Question about tileset attributes

Here's something I found while doing the rewrite:
https://github.com/mapeditor/rs-tiled/blob/0bb711466908e6f282b9f01039f372e79b44c497/assets/tiled_flipped.tmx#L3
Is this valid TMX? It has no name, tilewidth, etc attributes. How come this isn't triggering the tests?

Nevermind. This is a reference, not an external tileset. My bad.


DDF-1180: Add XML format to OWASP configuration

Updated OWASP configuration to generate XML report so it can be used by the Jenkins plug-in.

@shaundmorris: Please take a look when you have a chance. The only thing that's changed is the  element in the . Everything else should have already been merged.

@shaundmorris: I just rebased my local branch and pushed it back. Let me know if there's anything else I need to do on my end for you to merge this to master.


GitHub class conflict

Why are we getting Class conflicts when Pull, and how do we resolve so we can get the code.

Dillan showed me how how to Reset, but took several steps.  You may need to check with him.

Steps:
• Commit all changes
• Reset from the desired branch under the            remote folder.
On Feb 2, 2017 00:26, "pzcode"<EMAIL_ADDRESS>wrote:

Dillan showed me how how to Reset, but took several steps. You may need to
check with him.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/FRC2832/Robot_2017/issues/4#issuecomment-276871753,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APTwrmlJtMGOOywZeQ0U5bZHTnyBZ2jhks5rYWj6gaJpZM4LwmlC
.

Setup your User Library paths as described in this file - Variable Library
Load 3rd party libraries following these instructions


⚠ Bofrost.es has degraded performance

In 4481a52, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1510 ms

Resolved: Bofrost.es performance has improved in 59bdbe1.


chrry-pick sqoop task in dev to 1.3.4

What is the purpose of the pull request
Merge sqoop optimization and bug fix in dev-branch to 1.3.4
Brief change log

sqoop task optimization

Verify this pull request
This change added tests and can be verified as follows:

verified this pr using SqoopTaskTest

which issues does this pr refer to ?

which issues does this pr refer to ?

linked issue: #2917 #4034 #4104 #4135


Fix typo

Uneeded comma when calling the MobileServiceClient constructor

Hi @japf, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

@japf : Thanks for your contribution to the Azure documentation! The author, @adrianhall, has been notified to review your proposed change.

#sign-off


Update About Pages

About Pages need to include the following paragraphs under the top section "About the Northern Australia Map".
WHY NORTHERN AUSTRALIA
Northern Australia is a big region – covering all of the Northern Territory and north of the Tropic Capricorn in Queensland and Western Australia.
It accounts for more than 40 per cent of Australia’s land mass and contains up to 17 million hectares of arable soil, around 60 per cent of the water that falls in Australia and 90 per cent of Australia’s gas reserves.
Northern Australia has world-class and growing strengths in agriculture, energy and resources, tourism and hospitality, tropical health and medical research and education.
Opportunities for expansion and growth exist across all these sectors - and in the services, infrastructure, logistics, training, innovation, and the research and development that cluster around them.
ABOUT AUSTRADE
The Australian Trade and Investment Commission – Austrade – is the Australian Government agency that promotes trade, investment and education, and develops tourism policy and research. For foreign investment, Austrade works in partnership with Australian state and territory governments to provide investors with information and the right industry and government contacts needed to establish or expand a business in Australia.

Done.


Cannot install httpie via pip in Ubuntu 14.04 LTS

Installing httpie via sudo pip install --upgrade httpie leads to:
    $ http
Traceback (most recent call last):
  File "/usr/local/bin/http", line 7, in <module>
    from httpie.__main__ import main
  File "/usr/local/lib/python2.7/dist-packages/httpie/__main__.py", line 6, in <module>
    from .core import main
  File "/usr/local/lib/python2.7/dist-packages/httpie/core.py", line 22, in <module>
    from httpie.client import get_response
  File "/usr/local/lib/python2.7/dist-packages/httpie/client.py", line 6, in <module>
    from requests.packages import urllib3
ImportError: No module named packages

Intalling it via apt-get install httpie at least gets version 0.8 working.

Update requests and Pygments then try updating httpie.

I got this error recently. It was actually working prior to me installing pip and then installing awscli. I installed it from easy_install.
Traceback (most recent call last):
  File "/usr/local/bin/http", line 9, in <module>
    load_entry_point('httpie==0.9.2', 'console_scripts', 'http')()
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 351, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2363, in load_entry_point
    return ep.load()
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2088, in load
    entry = __import__(self.module_name, globals(),globals(), ['__name__'])
  File "/usr/local/lib/python2.7/dist-packages/httpie/__main__.py", line 6, in <module>
    from .core import main
  File "/usr/local/lib/python2.7/dist-packages/httpie/core.py", line 22, in <module>
    from httpie.client import get_response
  File "/usr/local/lib/python2.7/dist-packages/httpie/client.py", line 6, in <module>
    from requests.packages import urllib3
ImportError: No module named packages

Even after updating requests and pygments, it still fails.

Same here: same error, ubuntu 14.04 too, latest version of httpie. In my case I'm on a almost fresh install of ubuntu, and I tried to install instead of update.
pigments, urllib3, requests are fully updated using pip.

Hmm "pip install --upgrage httpie" worked for me in Ubuntu 14.04 in a fresh virtualenv:
"Installing collected packages: requests, Pygments, httpie
Successfully installed Pygments-2.0.2 httpie-0.9.2 requests-2.7.0"

Still breaking for me.
@imacleod What do you mean by fresh a virtualenv? Could you please elaborate on how you got it working?

@k0pernikus By a fresh virtualenv I meant creating a new virtualenv, activating it, and installing httpie inside of it. I just did this again with a new virtualenv to confirm that it worked and it did. I used these steps:
virtualenv testenv
cd testenv
source bin/activate
pip install --upgrade httpie

I've got the same error.
But after installing Pygments and Requests I got the the following error :

httpie error: TypeError: str returned non-string (type Error)

It's ok with a :

--verify=no

I've tested both apt-get install httpie and pip install httpie on a fresh Ubuntu 14.04.2 instance but haven't been able to reproduce this issue.

running pip install --upgrade requests fixed this issue for me.

Make sure you have installed requests by means of pip:
sudo apt-get remove python-requests python3-requests


Reset windows fix

Reset popup not seen clear. I made its container bigger. Fix issue #18

This is just a palliative solution - better would be a pop out to full window screen - showing the options page


Thumbnails to gimp resources

Hi David,
is possible to use this schema to do thumbnails of gimp resources on gnome?

Hi Americo,
This thumbnailer can only extract a *.png thumbnail ( created by the application at the moment of saving ) inside an archive. That's how *.kra and *.ora files are designed ( open document, as open office files ).
I don't think brush tip, gradients, palette ( gimp resources ) use this format.


README.md

Add OCF, The Open Connectivity Foundation, standards.

Hi, Thanks for the contribution!
OCF is replacing OIC (Open Interconnect) which is in the Alliances section. I think that it would be better to remove the OIC entry from this section first. and let OCF in the Standards section. I think it would be better to make this change in this pull request, since this is basically a replacement.

Ok, shall I make those updates and submit a new PR?

Yes that would be really nice 😉. Thank you.

OCF has been added in PR #15.


Autocomplete doesn't always work on .js files

The autocomplete feature is a little buggy on standard .js files (it works fine on .jsx though). It didn't work when I first installed the plugin but it worked when I restarted atom and then it stopped working a while later. It works again if I disable/enable the plugin. I haven't changed any settings, everything is the default.

I seem to be having this issue as well. What information can I provide to help troubleshoot this?


Azure IoT Edge - Build Modules

I'm unable to get this to work with Azure IoT Edge - Build Modules from with in the Azure DevOps Pipeline; any guidance no how to configure the pipeline for this use case?

Have you tried to use the NuGet Authenticate task? https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/package/nuget-authenticate?view=azure-devops


Problematic namespace for runtime shader map internal

Common modules that are included in runtime using the maven shader plugin are exposed as internal. However, may other modules need to use these modules. We should consider a new name or not moving them in the shade process.

Code Generator and Tuple shall be exposed, MapStream shall not be exposed.

injector, tupe and logger are moved to the public API


feat: collapse every section

This allows setting .Site.Params.GeekdocCollapseAllSections which then
behaves as if you would have set .Page.Params.geekdocCollapseSection
in all sections.
It is a hard positive switch, so you can not override it per section
once enabled.

Thanks for your contribution!

Thanks again.


bring PR #1101 to polkadot-v0.9.42 release branch

make https://github.com/paritytech/frontier/pull/1101 available to polkadot-v0.9.42release branch

@sorpaas https://github.com/paritytech/frontier/pull/1093 had the same CI issue: https://github.com/paritytech/frontier/actions/runs/5400985798/jobs/9810176023


Update AutoMockable.stencil

Fix inconsistent naming of Invocation variable and call on it which has been cause of build errors.

          1 Error

:no_entry_sign:
Any changes to library code need a summary in the Changelog.

  Generated by :no_entry_sign: Danger

thanks for contributing!
could you add the changelog entry?


Defining the "Basic Usage"

So we can work towards a common goal I'd like to discuss how exactly the Json Schema Builder should be used / called / included.
I created a small "Basic Usage" example based on the Angular Schema Form Example.
As I see it, it should be enough to just have a $scope.schema and a $scope.form (and an optional $scope.options) object for passing & receiving data, right?
Here's what I think it could look like (from my fork)
First, expose your (existing) schema and form to the $scope.
angular.module('myModule', ['schemaFormBuilder'])
       .controller('FormBuilderController', function($scope) {
  // JSON Schema
  // add an existing schema to edit it
  // or leave blank to create a new form
  $scope.schema = {};

  // Schema Form Defintion
  // add an existing form definition for editing
  // or leave blank to create a new form
  $scope.form = [];

});

Then load them into the Schema Form Builder using the sfbSchema and sfbForm directives.

</form>

Thoughts?

Well, yeah, something like that would be the usage, I suppose.
As close as the normal ASF usage as possible.
Have you looked closer to see if it easy to break out a directive from the application?

Took a quick look, and the code seems really nice, it should be pretty easy to break that out.

I'm currently working on that. There's some functionality in there that does not belong into the library IMHO, like saving forms or notifying the user of changes (locker, growl).
But the code is well-structured, so it's certainly possible. I'll have to read up on some angular convetions & best practices first, though.

Please do, it would be a killer feature if you could get that done.

I'm gonna need this for my masters thesis, so eventually I'll have to ;-)

Good choice. :-)

I'm partial to: https://github.com/johnpapa/angular-styleguide
The material repo also has a jscs file that follows Google code guide with minor differences, but I haven't looked into the builder enough to know how appropriate that is, however it would be nice to follow the same guides across all js implementations within the org. That's my 2c :)

Thanks, I'll give it a look and try to abide by it.


Generic support for dense arrays in VHLO

Request description
Array types are used sparingly in StableHLO, mostly in the form of DenseI64ArrayAttr, altough there are also uses of DenseBoolArrayAttr and ArrayAttr. Support for array types in serialization/deserialization is limited.
ArrayAttr is handled in a generic manner, i.e. both registered and unregistered array attributes will round trip through VHLO.
However, DenseI64ArrayAttr and DenseBoolArrayAttr are supported in a specific way. They are serialized using vhlo::TensorV1Attr, which means that they have to be converted back to arrays when they are deserialized. This is handled with op type switches, so there is no generic support: arrays that occur outside of the specific list of handled attributes will deserialize into tensors rather than arrays:
$ stablehlo-translate --serialize --target=current <<<"func.func @foo() {
  stablehlo.custom_call @foo() {foo = array<i64: 1, 2, 3>} : () -> ()
  func.return
}" | stablehlo-translate --deserialize
func.func @foo() {
  stablehlo.custom_call @foo() {foo = dense<[1, 2, 3]> : tensor<3xi64>} : () -> ()
  return
}

These are other kinds of array attributes, such as DenseI32ArrayAttr, which are currently not supported:
$ stablehlo-translate --serialize --target=current <<<"func.func @foo() {
  stablehlo.custom_call @foo() {foo = array<i32: 1, 2, 3>} : () -> ()
  func.return
}" | stablehlo-translate --deserialize
...
Failed to convert: array<i32: 1, 2, 3>
<stdin>:2:3: error: failed to legalize operation 'stablehlo.custom_call' that was explicitly marked illegal
  stablehlo.custom_call @foo() {foo = array<i32: 1, 2, 3>} : () -> ()
  ^

We should consider implementing generic handling of dense array attributes so that all such attributes can round trip through VHLO.
This feature request was originally motivated by a report in the stablehlo Discord channel: https://discordapp.com/channels/999073994483433573/999074539138990131/1219706845443129426

Let's add array + symbolref support together

I wanted to check in on this issue because this just came up in JAX: https://github.com/jax-ml/jax/issues/24160
We rely on array attributes in the XLA foreign function interface for accepting vector inputs, but this doesn't currently work via the plugin interface (i.e. any open source users of JAX on GPU) because of this round tripping issue. I'm going to look into being more flexible on the FFI side, but wanted to add a +1 here to say that having support for round tripping array attributes would be useful for us!


Make it clearer that you can manage roles for multiple users

From slack:

mogul [6:04 PM]
Hi Stratospherians, I have a question about user management… Say I want to edit the roles of the two people I’ve selected in this screenshot… How do I go about doing that? I don’t see any control to proceed.
And yet I can use the overflow menu on each line to edit people individually.
Am I misunderstanding, and there is no ability to edit roles for multiple people at the same time? Could have sworn I saw that previously… :thinking_face:
One of the early observations of user behavior on our existing dashboard was that they get very confused about what to do when the user they’re looking to add to their org/space isn’t listed… In our situation, we need them to go invite that user, at which point (even while the invite is pending) the user will appear and they can assign roles. Can this be an extension point somehow? Eg, if we configure a “Want to see more people here?” URL, maybe Stratos could present that somewhere?

(The point about inviting users, and providing a configured URL to draw users to that is separate... I'll make another issue about it so you can ignore it here; feel free to edit it out of the post above.)
From Slack:

You need to click on the double user icon on the top right of the header. I can see why that's not obvious now that I look at it. Once you select a user the icon, very sneaky, replaces the refresh icon that was there before and because of this, there is no clear visual cue that anything has changed. I also am beginning to wonder if our reliance on just icons for actions is compounding these kind of issues.

This is another information hierarchy issue!

If you relocate the action out of the blue top area in the header into any location within the white/gray are where the data is, it would be very clear what actions are available.

Having re-read my slack comment, I wanted to clarify that the "top right of the header" that I was talking about what actually the top right of the table header. Either way this issue still stands.
We've identified quite a few hierarchy issues that we're going to rectify moving into the new year. A lot of the fixes are going to revolve around moving actions from the top right of the page header into the relevant table headers. An example of this would be to move the "+" (add organization) on the CF summary page to the organization tab.
The general assertion we will be using when deciding which actions to move will be "this action directly affects the named entity", if this is not the case then we will find a better place for it.


Bump Iceberg to 1.7.0

:mag: Description
Issue References 🔗

Apache Iceberg 1.7.0 release https://github.com/apache/iceberg/releases/tag/apache-iceberg-1.7.0
Describe Your Solution 🔧
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Types of changes :bookmark:

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Test Plan 🧪
Behavior Without This Pull Request :coffin:
Behavior With This Pull Request :tada:
Related Unit Tests

Checklist 📝

[x] This patch was not authored or co-authored using Generative Tooling

Be nice. Be informative.

Iceberg 1.7.0 has dropped the support for Java 8. Let's see whether it's passing the CI tests.

Oh, it drops Java 8 ...

Oops ... it failed. How about bumping Iceberg to 1.7.0 for all except for the java-8 profile ?

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

Project coverage is 0.00%. Comparing base (dddb037) to head (eba16ae).

Additional details and impacted files
@@          Coverage Diff           @@
##           master   #6804   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files         687     687
  Lines       42442   42442
  Branches     5793    5793
======================================
  Misses      42442   42442

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

Oops ... it failed. How about bumping Iceberg to 1.7.0 for all except for the java-8 profile ?
It sounded good, I tried it.

LGTM if tests pass, thanks for your contribution!

Tests look like they've passed .


Add new source controls properties

This PR Adds new properties for Source Controls APIs

Can we update examples as well

@msyyc @tadelesh @qiaozha ,please help review sdk breaking changes, thanks

@kazrael2119 Hi, can we get approval please? The examples have been added

/azp run

/azp run

/azp run

@sanchitmehta ,please fix ModelValidation error

@kazrael2119 realized the example was wrong and I fixed it

/azp run


alpha4: tcp vs sctp performance

I made a micro benchmark based on current echo examples
tcp: /src/main/java/io/netty/example/echo
sctp: /src/main/java/io/netty/example/sctp
the tcp is x5 times faster then sctp, single channel;
can some one else please reproduce this independently?

Lets just close this for now


Extension causes high cpu load

Hello. When using the extension in Vscode, the following message appeared:

Issue Type: Performance
Extension Name: html-css-class-completion
Extension Version: 1.18.0
OS Version: Linux x64 4.15.0-45-generic
VSCode version: 1.31.1

Thank you
Zignd.html-css-class-completion-unresponsive.cpuprofile.txt

Duplicate of #155


Template boolean fields not persistent when binding type is property

Describe the Bug
In #1933, @MaxTru asked me to open a new issue concerning the behaviour of checkboxes/property attributes in camunda modeller templates. When a value of type: Boolean with binding type property is defined in a template, a checkbox will be added to the property window but it's not possible to change the value as it always resets when the element loses the scope.
As far as I understood the remarks in #1933 however, boolean support is limited. Consequentially, I am not certain this is an actual bug worth fixing.
Steps to Reproduce

Create a template file <x>/.camunda/element-templates/templates.json, containing this:

{
    "name": "Mail Task",
    "id": "com.camunda.example.MailTask",
    "appliesTo": [
        "bpmn:ServiceTask"
    ],
    "properties": [
        {
            "label": "Receivers",
            "type": "Boolean",
            "binding": {
                "type": "property",
                "name": "receivers"
            }
        }
    ]
}

Create and save an empty BPMN file in <x>.
Load BPMN file
Create a Service Task and assign the Element Template MailTask
Under Custom Fields, there will be a receiver checkbox which can be checked and unchecked but always resets when the ServiceTask is deselected.

Demo
(open in new tab for full hd resolution)

Expected Behavior
Changes of receiver are persistent.
Environment

OS: Windows 10 Version 2004
Camunda Modeler Version: 4.2.0

Dear @aleneum,
thanks for reporting and the detailed description.
In the example you gave you used a property named receivers. But receivers is not a valid property for a serviceTask BPMN XML element. The Camunda modeler is a BPMN 2.0 editor built upon domain specific modeling rules (see design principles). Therefore Element Templates do not support to set a property with an invalid name according to BPMN Moddle.
BPMN-moddle defines the BPMN meta-model, ie. what elements are valid in the context of BPMN 2.0.
If you would use for instance the following element template you will find out that the property binding with type = Boolean does work as expected (since camunda:asyncBefore is a valid Camunda BPMN 2.0 XML element, see here).
{
    "name": "Buggy Task",
    "id": "com.camunda.example.BuggyTask",
    "appliesTo": [
        "bpmn:ServiceTask"
    ],
    "properties": [
        {
            "label": "Async Before",
            "type": "Boolean",
            "binding": {
                "type": "property",
                "name": "camunda:asyncBefore"
            }
        }
    ]
}

May I ask what you want to achieve? We can then support you better in finding a solution for your use case.
For now I will close this ticket. Please also note that we are planning to implement and include a json validation of provided element template configurations to explicitly detect and highlight invalid element template configs to the user (see here).
Please don't hesitate to reach out (e.g., via forum.bpmn.io or creating another issue) in case of any more problems.

Hi @MaxTru,
thank you for that detailled explanation

May I ask what you want to achieve? We can then support you better in finding a solution for your use case.

oh, personally I was just interested in camunda:inputParameter and camunda:outputParameter which I use to communicate values to and from (Python) Service Tasks. I only tested the other binding types in #1933 for the sake of completeness. I can deal with passing everything as strings but I was looking for a way to reduce potential sources of error while creating models. Some type checking/restrictions in the modeller (String, Boolean, Int, Float, JSON, Enum: Can be done with Dropdown) could prevent spelling issue such as passing "treu" instead of "true" o "2O.1" instead of "20.1". But I am quite certain that I just scratched the surface of BPMN XML and Camunda. I still have to figure out how to do such things properly I guess.

Please also note that we are planning to implement and include a json validation of provided element template configurations to explicitly detect and highlight invalid element template configs to the user (see

that sounds neat

Please don't hesitate to reach out (e.g., via forum.bpmn.io or creating another issue) in case of any more problems.

will do. thanks for the support!

Hi @aleneum ,
understand - have you looked at constraints? https://github.com/camunda/camunda-modeler/tree/master/docs/element-templates#Constraints
By defining a regexp using a constraints configuration you could add some validation to the user inputs.
Best
Max


Editor panels messed up, 2D viewport inoperable

Godot version:

43e358205831fbcc5d6d7e8aade5131168d83651 Mono
OS/device including version:

Linux
Issue description:

According to @Calinou , appears to be a regression caused by https://github.com/godotengine/godot/commit/f2e54057aec3a4e4fbb9f9da5729915deb2f4648

2D viewport does not scroll or update anymore.  The editor will also darken, as if to show information, but instead shows nothing.

I can't reproduce on d403b408 with a non-Mono build, on Mageia 7 x86_64.

@akien-mga I cleared out my .config/godot, various .mono folders, recloned, rebuilt, and everything seems to be OK now.

@somnivore so should this be closed? Unless you can reproduce the error.

I'll assume it was just to do with differences in config files between previous Godot builds, as the problems don't seem to be coming back.


Can this support semicircles or other arc angles?

It has no support for that right now but you may customize rendering function to draw any shape. Here are few examples of customization:

thin "empty" circle
"start dot"
multiple circles
triangle

I meant something like this:

Yes, I understand your idea. The answer is: it's possible to do, though not so easy.
My lib is designed for circles only, not other shapes. However, I may create a snippet for you (like I did before, for examples above) :)

I don't know if @hmaidasani is still looking for this but i had to do a semi-circle as well, and i was able to override drawEmptyArc and drawArc and played a little with the math and got the semicircle working. Im gonna leave the code here just in cause is useful for anyone.
Thanks for this awesome library by the way @kottenator
Code for half-circle
               drawArc: function (v) {
                    var ctx = this.ctx,
                        r = this.radius,
                        t = this.getThickness(),
                        a = this.startAngle;

                    ctx.save();
                    ctx.beginPath();

                    if (!this.reverse) {
                        ctx.arc(r, r, r - t / 2, a, a + Math.PI * v);
                    } else {
                        ctx.arc(r, r, r - t / 2, a - Math.PI * v, a);
                    }

                    ctx.lineWidth = t;
                    ctx.lineCap = this.lineCap;
                    ctx.strokeStyle = this.arcFill;
                    ctx.stroke();
                    ctx.restore();
                },
                drawEmptyArc: function (v) {
                    var ctx = this.ctx,
                    r = this.radius,
                    t = this.getThickness(),
                    a = this.startAngle;

                    if (v < 1) {
                        ctx.save();
                        ctx.beginPath();

                        if (v <= 0) {
                            ctx.arc(r, r, r - t / 2, 0, Math.PI * 2);
                        } else {
                            if (!this.reverse) {
                                ctx.arc(r, r, r - t / 2, 0, a + Math.PI * v, a);
                            } else {
                                ctx.arc(r, r, r - t / 2, 0, a - Math.PI * v);
                            }
                        }

                        ctx.lineWidth = t;
                        ctx.strokeStyle = this.emptyFill;
                        ctx.stroke();
                        ctx.restore();
                    }
                },

gterat work, @juliansantaana!
I have re-worked your code a bit and made a [demo of arc layout].
I guess this task is resolved.

awesome @kottenator , introducing that new arcCoef attr is a great idea. Im gonna use your code since is obviusly more polished.
Are you thinking on merging this to the master?

Unfortunately, I can't merge it into master because it's not a circle anymore, it's an arc.
I already have made demos for arc layout, triangle layout, "thin empty circle", "start point", embed circles - all of them are custom layouts, that are not so popular, so they should not be included into the "core".
I don't know how what to do with it. Maybe some kind of plug-ins?

May I suggest branching some of these out into separate plugins? I too needed a semi circle and this worked perfectly. Not many devs will go so far to make the solution and since it's pretty much 'the' solution, it would be cool to have these as little gist plugins or something.
I did add ctx.lineCap = this.lineCap; to drawEmptyArc so the caps of the empty arc also have the same cap style.
Thanks again!

Yes, I'm thinking of plugin architecture - #111.


[sil-combine] Fix a stack_alloc peephole.

What's in this pull request?

Resolved bug number: (SR-)

Before merging this pull request to apple/swift repository:

[x] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    OS X platform               | @swift-ci Please test OS X platform
    Linux platform              | @swift-ci Please test Linux platform

Note: Only members of the Apple organization can trigger swift-ci.

Fix a bug in the stack_alloc peephole, which was producing a code using opened archetypes before they were actually defined.
rdar://26309488

@swift-ci Please test and merge


styled css/tailwind for error page.

could not get the bg image to show. could get to work only for some images. unsure why. image isn't too big for the spilled-wine. i got the wine pairing image to show just fine. all else is good.

CORRECTION: was able to see the image after restarting my dev. no issues with bg image.

Also added css styling to the cellarpage when not logged in.


Ds models

@FinnStutzenstein @emanuelschuetze
DataStore and Models should be done so far.
Since auto update is directly dependent on both web sockets, data store and Models creation I added this here (also, it's nice for testing)
I gonna evaluate pull/3775 once I finished the open tasks for OS3 Milestone1
Please review and merge soon.


Dark theme: Database navigator - Table size graph color has very bad visibility

Description
Dark theme In Database Navigator, statistics info > table size graph color has very bad visibility.

DBeaver Version
Community 24.0
Operating System
Windows
Database and driver
No response
Steps to reproduce
No response
Additional context
No response

Thanks for the report @Progress1


try xcode 8.3

Codecov Report

Merging #217 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #217   +/-   ##
======================================
  Coverage    85.1%   85.1%
======================================
  Files         257     257
  Lines       17481   17481
======================================
  Hits        14877   14877
  Misses       2604    2604

Flag
Coverage Δ

#data_tests
79.23% <ø> (ø)
:arrow_up:

#examples
36.45% <ø> (ø)
:arrow_up:

#unit_tests
88.22% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3e9fb8a...dd12ddc. Read the comment docs.


Add binary problem for Standard ML

There is now an example program binary.sml and test program test_binary.sml for the binary problem.

Sorry, habit from being a Perl programmer :) I removed the trailing comma and squashed my two commits.

Sweet, thanks!


Add dropout test

Create a tensor of shape (100,000,) and add a dropout with rate=0.01. We can then count the number of zeros in this tensor and expect it to be around 100,000 * 0.01 = 1000 with some tolerance.

I’m not sure why the unit tests failed ._. From the log, it seems like non_zeros are completely off.

I added .cpu() and the test case would pass for both CPU and GPU - sorry for being a noob earlier!


⚠ Quirk Club Argentina (Payment Gateway) has degraded performance

In 100077b, Quirk Club Argentina (Payment Gateway) (https://us-central1-quirkclub-dev.cloudfunctions.net/api/check/payment-gateway-ml) experienced degraded performance:

HTTP code: 200
Response time: 7106 ms

Resolved: Quirk Club Argentina (Payment Gateway) performance has improved in 95dc44e after 18 minutes.


UI: Fix issue where 1st tab shows the close icon...

When there are multiple tabs open using the file explorer. This happens because the mouse_pos is initialized to Point::ZERO which technically resides inside the rect of the first tab.
Signed-off-by: Hanif Bin Ariffin<EMAIL_ADDRESS>
[ ] Added an entry to CHANGELOG.md if this change could be valuable to users

Edit: Do you want to include this to CHANGELOG.md?

Codecov Report

Merging #1483 (7864ebb) into master (3396279) will increase coverage by 0.04%.
The diff coverage is 0.00%.

 Learn more

Yes please for the changelog. You might want to rebase master first.


.NET 6

Hey,
Thanks for the tool, much appreciated.
Saw your comments regarding .Net 6 not being included in Windows which caused you to fallback to older .Net Framework versions and use slower code (i.e. not FindPattern_SIMD).
If the concern is that an average used would not be able to "just run" a release from this repo, .Net 6 (probably even 5 or 3.1) allows publishing a self-contained exe. I.e. end-users would not have to install anything. Soo... JFYI
See here: https://docs.microsoft.com/en-us/dotnet/core/deploying/#publish-self-contained

Hello, unfortunately self-contained apps do not fully support WPF (missing trimming support) yet so you end up with a huge number of additional dlls and config files that will be bundled into your exe. In my initial test the output was ~100MiB. That is ridiculous for such a small app.

I don't think this is feasible either. Microsoft will not start shipping .NET 6 with Windows in the foreseeable future and plaguing every user with a 150mb executable instead of a 300kb one is not a great idea.
At best we could release two versions (self-contained and framework dependent), but even then the framework dependent version would be significantly larger than one targeting .NET Framework.

Fair enough, 150 megs for a small tool is indeed quite a bit.
It seems that the only feasible way to create cross-platform GUI apps that don't take so much HDD space is something like Blazor. Blazor apps should be trimmable.
Depending on how strong the benefits of .Net 6 are in this case (I suppose it is mostly about cross-platform builds here and not so much about the performance), it might be worth considering.

Rather pointless for a Windows-only application. The only benefit would be C# 10 and speed, the latter of which is irrelevant.


[Event Request] Table 39 - Purchase Line - OnValidateNoOnBeforeCheckReceiptNo

Dear ALAppExtensions team,
through this issue we would like to request adding event publisher OnValidateNoOnBeforeCheckReceiptNo in Table 39 Purchase Line with the following signature:
[IntegrationEvent(false, false)]
local procedure OnValidateNoOnBeforeCheckReceiptNo(var PurchaseLine: Record "Purchase Line"; var xPurchaseLine: Record "Purchase Line"; var IsHandled: Boolean)
begin
end;

which would be called as follows in the OnValidate trigger of field 6 - No.:
trigger OnValidate()
var
    TempPurchLine: Record "Purchase Line" temporary;
    IsHandled: Boolean;
    l_ReceiptGLAccount: Boolean;
begin
    IsHandled := false;
    OnBeforeValidateNo(Rec, xRec, CurrFieldNo, IsHandled);
    if IsHandled then
        exit;
    GetPurchSetup();
    "No." := FindOrCreateRecordByNo("No.");
    TestStatusOpen();
    TestField("Qty. Rcd. Not Invoiced", 0);
    TestField("Quantity Received", 0);
    // >>>> New >>>>>>>>>>>>>>>>
    IsHandled := false;
    OnValidateNoOnBeforeCheckReceiptNo(Rec, xRec, IsHandled);
    if not IsHandled then
        TestField("Receipt No.", '');
    // <<<< New <<<<<<<<<<<<<<<<
    ...
end;

Thanks in advance!

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 47054.