Serverspec Test

I mention having an issue running the Serverspec test in my PR #168. I got around to setting up Cygwin on my machine to see if running Serverspec tests works in Cygwin since I am having an issue running them from PowerShell.
Running make test-virtualbox/eval-win10x86-enterprise from Cygwin gets me the following error:
==> default: Running provisioner: serverspec...
F

Failures:

  1) windows box should have a vagrant user
     Failure/Error: expect(user 'vagrant').to exist
     NoMethodError:
       undefined method `[]' for nil:NilClass

     # C:/Users/Matthew Winfield/.vagrant.d/gems/2.4.4/gems/specinfra-2.75.0/lib/specinfra/backend/ssh.rb:179:in `sudo?'
     # C:/Users/Matthew Winfield/.vagrant.d/gems/2.4.4/gems/specinfra-2.75.0/lib/specinfra/backend/ssh.rb:42:in `build_command'
     # C:/Users/Matthew Winfield/.vagrant.d/gems/2.4.4/gems/specinfra-2.75.0/lib/specinfra/backend/ssh.rb:10:in `run_command'
     # C:/Users/Matthew Winfield/.vagrant.d/gems/2.4.4/gems/specinfra-2.75.0/lib/specinfra/runner.rb:27:in `run'
     # C:/Users/Matthew Winfield/.vagrant.d/gems/2.4.4/gems/specinfra-2.75.0/lib/specinfra/runner.rb:19:in `method_missing'
     # C:/Users/Matthew Winfield/.vagrant.d/gems/2.4.4/gems/serverspec-2.41.3/lib/serverspec/type/user.rb:4:in `exists?'
     # C:/git/boxcutter-windows/test/windows_spec.rb:5:in `block (2 levels) in <top (required)>'
     # C:/Users/Matthew Winfield/.vagrant.d/gems/2.4.4/gems/vagrant-serverspec-1.3/lib/vagrant-serverspec/provisioner.rb:93:in `provision'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/provision.rb:138:in `run_provisioner'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:95:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builder.rb:116:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `block in run'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/util/busy.rb:19:in `busy'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `run'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/environment.rb:510:in `hook'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/provision.rb:126:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/provision.rb:126:in `block in call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/provision.rb:103:in `each'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/provision.rb:103:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/clear_forwarded_ports.rb:15:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/set_name.rb:50:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/clean_machine_folder.rb:17:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/check_accessible.rb:18:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builder.rb:116:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `block in run'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/util/busy.rb:19:in `busy'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `run'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/call.rb:53:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builder.rb:116:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `block in run'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/util/busy.rb:19:in `busy'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `run'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/call.rb:53:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builder.rb:116:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `block in run'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/util/busy.rb:19:in `busy'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `run'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/call.rb:53:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/box_check_outdated.rb:36:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/check_virtualbox.rb:26:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/match_mac_address.rb:19:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/discard_state.rb:15:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/import.rb:74:in `import'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/import.rb:13:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/prepare_clone_snapshot.rb:17:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/prepare_clone.rb:15:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/customize.rb:40:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/check_accessible.rb:18:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builder.rb:116:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `block in run'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/util/busy.rb:19:in `busy'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `run'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/call.rb:53:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builder.rb:116:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `block in run'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/util/busy.rb:19:in `busy'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `run'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/call.rb:53:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/check_virtualbox.rb:26:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builder.rb:116:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `block in run'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/util/busy.rb:19:in `busy'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `run'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/machine.rb:239:in `action_raw'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/machine.rb:208:in `block in action'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/environment.rb:598:in `lock'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/machine.rb:194:in `call'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/machine.rb:194:in `action'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
     # C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/logging-2.2.2/lib/logging/diagnostic_context.rb:474:in `block in create_with_logging_context'

Finished in 0.09076 seconds (files took 0.3728 seconds to load)
1 example, 1 failure

Failed examples:

rspec C:/git/boxcutter-windows/test/windows_spec.rb:4 # windows box should have a vagrant user

ERROR warden: Error occurred: ServerSpec failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
ERROR warden: Error occurred: ServerSpec failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
ERROR warden: Error occurred: ServerSpec failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
ERROR warden: Error occurred: ServerSpec failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
ERROR warden: Error occurred: ServerSpec failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
ERROR warden: Error occurred: ServerSpec failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
ERROR warden: Error occurred: ServerSpec failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
ERROR warden: Error occurred: ServerSpec failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
ERROR warden: Error occurred: ServerSpec failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
ERROR warden: Error occurred: ServerSpec failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
ERROR warden: Error occurred: ServerSpec failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
ERROR warden: Error occurred: ServerSpec failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::ServerSpecFailed: ServerSpec failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.>
ERROR vagrant: ServerSpec failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
ERROR vagrant: C:/Users/Matthew Winfield/.vagrant.d/gems/2.4.4/gems/vagrant-serverspec-1.3/lib/vagrant-serverspec/provisioner.rb:94:in `provision'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/provision.rb:138:in `run_provisioner'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:95:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builder.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/util/busy.rb:19:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/environment.rb:510:in `hook'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/provision.rb:126:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/provision.rb:126:in `block in call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/provision.rb:103:in `each'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/provision.rb:103:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/clear_forwarded_ports.rb:15:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/set_name.rb:50:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/clean_machine_folder.rb:17:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/check_accessible.rb:18:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builder.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/util/busy.rb:19:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/call.rb:53:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builder.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/util/busy.rb:19:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/call.rb:53:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builder.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/util/busy.rb:19:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/call.rb:53:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/box_check_outdated.rb:36:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/check_virtualbox.rb:26:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/match_mac_address.rb:19:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/discard_state.rb:15:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/import.rb:74:in `import'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/import.rb:13:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/prepare_clone_snapshot.rb:17:in `call' C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/prepare_clone.rb:15:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/customize.rb:40:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/check_accessible.rb:18:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builder.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/util/busy.rb:19:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/call.rb:53:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builder.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/util/busy.rb:19:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/call.rb:53:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/check_virtualbox.rb:26:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builder.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/util/busy.rb:19:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/machine.rb:239:in `action_raw'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/machine.rb:208:in `block in action'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/environment.rb:598:in `lock'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/machine.rb:194:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/machine.rb:194:in `action'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/logging-2.2.2/lib/logging/diagnostic_context.rb:474:in `block in create_with_logging_context'
ServerSpec failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
make: *** [test-box/virtualbox/eval-win10x86-enterprise-nocm-1.0.4.box] Error 1

I get a different error running from PowerShell. From PowerShell I get the following error:
==> box: Successfully added box 'eval-win10x86-enterprise-nocm-1.0.4' (v0) for 'virtualbox'!
+ mkdir -p /tmp/boxtest
+ pushd /tmp/boxtest
/tmp/boxtest /c/git/boxcutter-windows
+ create_vagrantfile_linux
+ vagrant plugin list
+ grep vagrant-serverspec
vagrant-serverspec (1.3)
+ echo 'vagrant-serverspec installed'
vagrant-serverspec installed
+ cat
+ VAGRANT_LOG=warn
+ vagrant up --provider virtualbox
 WARN global: resolv replacement has not been enabled!
Bringing machine 'default' up with 'virtualbox' provider...
ERROR warden: Error occurred: There are errors in the configuration of this machine. Please fix
the following errors and try again:

serverspec provisioner:
* You must list at least one spec file

ERROR warden: Error occurred: There are errors in the configuration of this machine. Please fix
the following errors and try again:

serverspec provisioner:
* You must list at least one spec file

ERROR warden: Error occurred: There are errors in the configuration of this machine. Please fix
the following errors and try again:

serverspec provisioner:
* You must list at least one spec file

ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::ConfigInvalid: There are errors in the configuration of this machine. Please fix
the following errors and try again:

serverspec provisioner:
* You must list at least one spec file

>
ERROR vagrant: There are errors in the configuration of this machine. Please fix
the following errors and try again:

serverspec provisioner:
* You must list at least one spec file

ERROR vagrant: C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/config_validate.rb:18:in `call' C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builder.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/util/busy.rb:19:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builtin/call.rb:53:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/plugins/providers/virtualbox/action/check_virtualbox.rb:26:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/builder.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/util/busy.rb:19:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/action/runner.rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/machine.rb:239:in `action_raw'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/machine.rb:208:in `block in action'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/environment.rb:598:in `lock'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/machine.rb:194:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/machine.rb:194:in `action'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/logging-2.2.2/lib/logging/diagnostic_context.rb:474:in `block in create_with_logging_context'
There are errors in the configuration of this machine. Please fix
the following errors and try again:

serverspec provisioner:
* You must list at least one spec file

Like I've said previously, I am not sure if this is an issue in the boxcutter/windows project or if this is a problem with my environment. The documentation in the readme makes it sound like this doesn't require any special setup. Any guidance or help with this is appreciated!

Hey @mwinfie, does this issue still exist? Are you still interested in trying to resolve it?

Marking this issue as stale as it hasn't been responded to in a long time. If there's still no interaction, this issue will be closed in a month. If you feel this is a mistake and should not be closed, please let me know.

Closing this issue as it has gone stale due to a lack of interaction that has extended to almost a year. If you feel this is in error, please let me know and I will re-open.


make saved more visible

make a small hint that a PCM has been saved (maybe something smaller than an alert)

Now, the "save" button change its icon when saving.
However, the icon is not always changed back to normal when a modification occured on the table.

Fully implemented in bfcd47eba1812f745ee10bb3d5e33a2956d962e3


filter train set gt labels

hello，
I want to remove the extension lines in intersection that are not in the current direction in the -ls.json file. How should the logic of judgment be?
Thanks.

Hi, maybe you can utilize the direction and topology of the centerlines? The order of points represents the direction of centerlines.

You can also use the key is_intersection_or_connector to filter the lane segments within the intersection.

You can also use the key is_intersection_or_connector to filter the lane segments within the intersection.

but I need to keep the centerlines that the current car might travel on.

Hi, maybe you can utilize the direction and topology of the centerlines? The order of points represents the direction of centerlines.

just  the vector from startpoint to endpoint？But when the car rotates, the angle between the vector and the car coordinate system changes.

You can also use the key is_intersection_or_connector to filter the lane segments within the intersection.

but I need to keep the centerlines that the current car might travel on.

The coordinate of the ego car is (0, 0) on the ground plane. This property may be used to filter the lane on which the ego car is driving. Then, the topology relationship on lane can be used to calculate lanes on which ego car might travel.


Active terminal causes :wall to fail with E676: No matching autocommands for acwrite buffer

Steps to reproduce:

vim -u NONE
:term
<C-W>:wall<CR>

What happens:

E676: No matching autocommands for acwrite buffer flashes briefly

What I expect

no confusing error message

Note that if the terminal is no longer active (e.g you exit the shell), :wall doesn't complain.

On 13:18 Thu 05 Oct     , Marius Gedminas wrote:

Steps to reproduce:

vim -u NONE
:term
<C-W>:wall<CR>

What happens:

E676: No matching autocommands for acwrite buffer flashes briefly

What I expect

no confusing error message

Note that if the terminal is no longer active (e.g you exit the shell), :wall doesn't complain.

I see this regularly, when using vim-fugitive :Gcommit command.
Regards,
Marcin

This also happens to me all the time when I have a terminal open and try to use fzf for opening a buffer.
I think this should be fixed in vim itself although I am uncertain of the implementation details, but in the meantime I use the following workaround in my vimrc:
fun! s:workaroundIssue2190()
    " see https://github.com/vim/vim/issues/2190
    if &buftype=='terminal' && !exists('b:workaround_issue_2190')
        autocmd BufWriteCmd <buffer> echo 'workaround 2190'
        let b:workaround_issue_2190=1
    endif
endfun
aug workaroundIssue2190
    autocmd! BufWinEnter * call s:workaroundIssue2190()
aug END

Or add ignoring for write if buftype is nowrite or terminal.
diff --git a/src/ex_cmds.c b/src/ex_cmds.c
index b4351b23d..79dc01314 100644
--- a/src/ex_cmds.c
+++ b/src/ex_cmds.c
@@ -3414,6 +3414,12 @@ do_wqall(exarg_T *eap)
 		++error;
 		break;
 	    }
+
+	    if (bt_dontwrite(buf))
+	    {
+		continue;
+	    }
+
 #ifdef FEAT_BROWSE
 	    /* ":browse wall": ask for file name if there isn't one */
 	    if (buf->b_ffname == NULL && cmdmod.browse)

+1 for the patch  ignoring not-writable buffers.


Move:  python solutions to python 3

#4

@navyakanu , I have added contributing guidelines in the repository. Request you to go through it and create new PR as per the guidelines. Closing This PR for now.

@sagarchoudhary96 I have updated the PR, changed the commit name, kindly review and let me know if there are any comments which needs amends

@navyakanu there is merge conflict with your PR, resolve the conflict and Update the PR. you can resolve by syncing your forked repo with this repository. you can read about it by searching for sync forked repo with main repo on google search.

Also, at max only send PR for only 4 solutions.

@navyakanu , the solution for Day2 is already completed. check the issue first comment to see opened questions. Closing the PR.


Both original and translated routes exist: Duplicate Content

Hello,
when I use your plugin, both the original and the translated routes exist. This is a problem because it creates duplicate content, which is bad for SEO.
Is it possible to have only the translated routes, and remove the original routes, when the locale is set to a language other than the default?
Thanks!

I had the same problem - but it can be solved easily with a redirect call. Redirect all stuff to the new place. You can use parameters in rails redirects, so you can redirect all contents easily.

The issue is not really solved with a redirect. It works for users, but when pages are indexed by search engines, this can destroy your ranking (think "duplicate content"). Pages which don't exist or contain duplicate content should return 404.
How did you solve this?

I see your point. What is the perfect solution to this?

This is simple: When adding translated routes, remove the original routes from the routing table.
However, I do not know how to do this in i18n-routing ... :)


Add HttpToS3Loader

This new class is useful to download a file from the internet and
upload it to an s3 bucket. Existing file with an expected hash
should not be overwritten.
Resolves #3

lgtm


Make link buttons behave like buttons

What
Add role, draggable, and data-module attributes to links styled as buttons.
Why
As they're styled as buttons they should also behave like buttons, so as not to confuse the user.
Link to Trello card (if applicable): https://trello.com/c/SLDfWeAe

can't review at the mo as it wont run locally and theres no deploy


CommitsSinceVersionSource and PreReleaseNumber as Integer

What You Are Seeing?
The GitVersion properties CommitsSinceVersionSource and PreReleaseNumber are currently of type string. The JSON file from the CLI of GitVersion returns both values as int (that make sense for me).
MacBook-er-osx:AddPhoto er$ mono tools/GitVersion.CommandLine/tools/GitVersion.exe
{
  "Major":0,
  "Minor":2,
  "Patch":0,
  "PreReleaseTag":"alpha.59",
  "PreReleaseTagWithDash":"-alpha.59",
  "PreReleaseLabel":"alpha",
  "PreReleaseNumber":59,
  "BuildMetaData":"",
  "BuildMetaDataPadded":"",
  "FullBuildMetaData":"Branch.feature/40_FAKE_to_CAKE.Sha.279a1141bfb8ba2ea31227eae5ee47badeeef71b",
  "MajorMinorPatch":"0.2.0",
  "SemVer":"0.2.0-alpha.59",
  "LegacySemVer":"0.2.0-alpha59",
  "LegacySemVerPadded":"0.2.0-alpha0059",
  "AssemblySemVer":"<IP_ADDRESS>",
  "FullSemVer":"0.2.0-alpha.59",
  "InformationalVersion":"0.2.0-alpha.59+Branch.feature/40_FAKE_to_CAKE.Sha.279a1141bfb8ba2ea31227eae5ee47badeeef71b",
  "BranchName":"feature/40_FAKE_to_CAKE",
  "Sha":"279a1141bfb8ba2ea31227eae5ee47badeeef71b",
  "NuGetVersionV2":"0.2.0-alpha0059",
  "NuGetVersion":"0.2.0-alpha0059",
  "CommitsSinceVersionSource":59,
  "CommitsSinceVersionSourcePadded":"0059",
  "CommitDate":"2017-05-05"
}

What is Expected?

Both properties should be of type int.

What version of Cake are you using?

0.19.5

Are you running on a 32 or 64 bit system?
What environment are you running on?  Windows? Linux? Mac?

Win 10
macOS

Are you running on a CI Server?  If so, which one?

GitLab CI (9.1)

How Did You Get This To Happen? (Steps to Reproduce)
I wanted to use the version parts for calculation (android version code), but failed in first approach with PreReleaseNumber is not a number.

@WebDucer can you confirm what version of GitVersion you are using?  Just want to make sure that this isn't a change in the output between versions of GitVersion.

@gep13 I use the current version 3.6.5.

@WebDucer In which case, I agree.  This is something that we should fix.  Are you in a position to submit a PR to correct this?

@gep13 Yes, I can do that on weekend. But this change would cause a breaking change for all that uses this properties as strings.

@WebDucer Yes, you are right.
@devlead any ideas about a "graceful" way to handle this?


feat(primitives): added enum utilities

This PR was created by branching off a feat branch and not from master.


App breaking randomly - Android

The app is breaking randomly on an Android device. (PocoF1) Screenshot attached.

Is that the production or dev build? I know the Flame devs are aware of that issue (updated pubspec to latest version just in case it may fix it)

@impulse , this was a production build. The pubspec update seems to have fixed it.

Alright. This issue is Flame related, so if you keep running into this bug check out their repo for issues / solutions.


Use existing stacks in the home directory

I tried setting up dockge with my existing docker-compose stacks, which are located in my home directory: ~/docker/….
Here's how I mapped the volumens:
    volumes:
    …
      - /home/einmaulwurf/docker:/home/einmaulwurf/docker
    environment:
      - DOCKGE_STACKS_DIR=/home/einmaulwurf/docker

But there seems to be some problem with that. I can see all my containers in the dockge UI, but the compose files are shown as empty. Is it possible to use dockge in this setup, or do I have to move my compose files to /opt/stacks?

My bad, I did not rename my compose files from docker-compose.yaml to compose.yaml. Now it works.
I would suggest, that either docker-compose.yaml files are recognized as well, or that the user can set an environment variable to change the filename.


[TF2.0] Loading a Saved Model failed with AttributeError: '_UserObject' object has no attribute '_create_or_restore_slot_variable'

I am using the latest TF2.0 pip package.
Consider the following code:
import tensorflow as tf
import numpy as np

class ToyModel(tf.keras.Model):
    """A simple linear model."""

    def __init__(self):
        super().__init__()
        self.l1 = tf.keras.layers.Dense(5)

    @tf.function(input_signature=[tf.TensorSpec([None, 1], tf.float32, name="input_func")])
    def call(self, x):
        return self.l1(x)

def toy_dataset():
    inputs = tf.range(10.)[:, None]
    outputs = inputs * 5. + tf.range(5.)[None, :]
    # TODO: switch `tuple` to `dict`.
    dataset = tf.data.Dataset.from_tensor_slices((inputs, outputs))
    return dataset.repeat(10).batch(2).shuffle(buffer_size=5)

dataset = toy_dataset()
optimizer = tf.keras.optimizers.Adam(0.1)

model = ToyModel()
model.compile(loss='mean_squared_error', optimizer=optimizer, metrics=['accuracy'])
history = model.fit(dataset, epochs=5)

# Inference works
inputs = np.array([[0, 5]], dtype=np.float32).T
print(model(inputs))

# Export to Saved Model
model_path = "/tmp/saved_model"
tf.saved_model.save(model, model_path)

# Load model
saved_model = tf.saved_model.load(model_path)

# Inference from Saved Model
#inputs = np.array([[0, 5]], dtype=np.float32).T
#saved_model(inputs)

It fails with:
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-2-4a1364881187> in <module>
     37
     38 # Load model
---> 39 saved_model = tf.saved_model.load(model_path)
     40
     41 # Inference from Saved Model

~/local/conda/envs/tf/lib/python3.7/site-packages/tensorflow/python/saved_model/load.py in load(export_dir, tags)
    322       loader = _Loader(object_graph_proto,
    323                        saved_model_proto,
--> 324                        export_dir)
    325       root = loader.get(0)
    326   else:

~/local/conda/envs/tf/lib/python3.7/site-packages/tensorflow/python/saved_model/load.py in __init__(self, object_graph_proto, saved_model_proto, export_dir)
     62     self._setup_functions_structures()
     63     self._setup_functions_captures()
---> 64     self._restore_checkpoint()
     65
     66     for node in self._nodes:

~/local/conda/envs/tf/lib/python3.7/site-packages/tensorflow/python/saved_model/load.py in _restore_checkpoint(self)
    151     saver = util.TrackableSaver(graph_view.ObjectGraphView(self.get(0)))
    152     saver._file_prefix_placeholder = constant_op.constant(variables_path)
--> 153     load_status = saver.restore(variables_path)
    154     load_status.assert_existing_objects_matched()
    155     checkpoint = load_status._checkpoint

~/local/conda/envs/tf/lib/python3.7/site-packages/tensorflow/python/training/tracking/util.py in restore(self, save_path)
   1094         graph_view=self._graph_view)
   1095     base.CheckpointPosition(checkpoint=checkpoint, proto_id=0).restore(
-> 1096         self._graph_view.root)
   1097     load_status = CheckpointLoadStatus(
   1098         checkpoint,

~/local/conda/envs/tf/lib/python3.7/site-packages/tensorflow/python/training/tracking/base.py in restore(self, trackable)
    207         # This object's correspondence with a checkpointed object is new, so
    208         # process deferred restorations for it and its dependencies.
--> 209         restore_ops = trackable._restore_from_checkpoint_position(self)  # pylint: disable=protected-access
    210         if restore_ops:
    211           self._checkpoint.new_restore_ops(restore_ops)

~/local/conda/envs/tf/lib/python3.7/site-packages/tensorflow/python/training/tracking/base.py in _restore_from_checkpoint_position(self, checkpoint_position)
    777           ._single_restoration_from_checkpoint_position(
    778               checkpoint_position=current_position,
--> 779               visit_queue=visit_queue)))
    780     return restore_ops
    781

~/local/conda/envs/tf/lib/python3.7/site-packages/tensorflow/python/training/tracking/base.py in _single_restoration_from_checkpoint_position(self, checkpoint_position, visit_queue)
    804             child_position)
    805       else:
--> 806         if child_position.bind_object(trackable=local_object):
    807           # This object's correspondence is new, so dependencies need to be
    808           # visited. Delay doing it so that we get a breadth-first dependency

~/local/conda/envs/tf/lib/python3.7/site-packages/tensorflow/python/training/tracking/base.py in bind_object(self, trackable)
    249                       slot_name=slot_restoration.slot_name))
    250         else:
--> 251           optimizer_object._create_or_restore_slot_variable(  # pylint: disable=protected-access
    252               slot_variable_position=CheckpointPosition(
    253                   checkpoint=checkpoint,

AttributeError: '_UserObject' object has no attribute '_create_or_restore_slot_variable'

Maybe related to https://github.com/tensorflow/tensorflow/issues/25235 ?

Sorry you ran into this; should be fixed by https://github.com/tensorflow/tensorflow/commit/147e6777068ea569cbecbd270b8b07c648bae09b
I checked with 2.0.0-dev20190318 and the save and load works. "call" isn't there with that name; we should make subclassed Models export any explicitly-decorated methods. This method just needs to be modified to include something like AutoTrackable's search for attributes containing decorated functions. We could have Layer inherit from AutoTrackable and call super().

Or we could just add a copy of the traced function under "call" instead of just "_default_save_signature".

I confirm 2.0.0.dev20190318 fix the issue.

I let you close since you want to address something with call.

Yep, leaving open to track the call issue. Thanks for confirming.

Models export all their methods now (example). So well and truly fixed now.

use tf.keras.models.load_model(path) instead.

I am having a similar issue. I recently installed anaconda 2020.02 on my Windows 10 laptop which comes with Spyder 4.0.1. .... then installed Tensorflow 2.1.0
import tensorflow as tf trained_model = tf.saved_model.load(export_dir='model_CNN_Dataset_pitch_tempo_envs1024xbatch_20xepochs_4') trained_model.summary() trained_model.layers
it fails with:

AttributeError: '_UserObject' object has no attribute 'summary'

Any suggestions please?

@LatinAmericanProgramer if summary is from a Keras Model, I'd use the Keras save/load wrappers (tf.keras.Model.save(..., save_format='tf'), tf.keras.load_model). That will revive Models as Models rather than just an object with traced tf.functions. Otherwise pure Python methods are not saved with the SavedModel.

Thank you @allenlavoie ... I fix it uninstalling Tensorflow 2.1.0 and installing the version 2.2.0-dev20200327 using pip install tf-nightly-gpu . This fixed the problem for me.
Thank you

I believe I have a similar problem...
Python 3.7.6
TensorFlow 2.0.0
I am trying to save NN model ('Policy') with tf.keras.models.save_model and it raises AttributeError: 'Policy' object has no attribute 'built'.
Should I save it using another method?
Thanks!


issue #1: GKE cluster using Terraform (first iteration)

Closes #1
Closes https://github.com/ai-cfia/github-workflows/issues/58
Closes https://github.com/ai-cfia/github-workflows/issues/50
Closes https://github.com/ai-cfia/nachet-backend/issues/45
Closes https://github.com/ai-cfia/finesse-backend/issues/24

Finesse URL: https://finesse.ninebasetwo.xyz/health
Nachet backend URL: https://nachir.ninebasetwo.xyz/health

Previously made a number of comments on this PR but I don't see replies or acknowlegement to them. Can you address the comments @ThomasCardin so I can close those conversation threads?

Done

I'll revisit once the changes are implemented

Do you have time to review. Every requested changes are done

Linting error from the kubernetes/system/* will be fixed in another issue


[2.1.1] Flakey test: StreamDoesNotStartIfTokenAlreadyCanceled

Consider taking https://github.com/aspnet/SignalR/issues/2310 for 2.1.1

This fix reduces spurious additional logging of errors that occur when a client has disconnected while the server is trying to send data to it (which fails, since the client connection is no longer active).

Declined for 2.1.1

Shiproom considered this issue but I mis-explained it as #2343 - This is actually a duplicate of #2341 which was approved.


[bug] After adding a device or healing the network, the graph is wrong

Version
Checklist:

[x] I am not using HomeAssistant. Or: a developer has told me to come here.
[x] I have checked the troubleshooting section and my problem is not described there.
[x] I have read the changelog problem was not mentioned there.

Build/Run method

[x] Docker
[ ] PKG
[ ] Snap package
[ ] Manually built (git clone - yarn install - yarn run build )

zwavejs2mqtt version: 4.2.1
zwave-js version: 7.4.0
Describe the bug
After adding a new device to the network or healing the network with changed routes, the network graph is not updated. The neighbor information in the log is correct, but the graph is out of sync. A full page reload is required to make it work.
To Reproduce
Steps to reproduce the behavior:

A network with at least one node disconnected
Visualize the graph, notice a disconnected device
Heal the network
Visualize the graph, still notice a disconnected device

OR
I've also seen this after adding a new device.
Expected behavior
At 4. the device should be connected.
Additional context
I'm using Firefox on Arch Linux.
After a network heal, my network graph looks like this:

Reloading the entire page leads to the updated graph:

This is a follow-up to #739

@andyboeh Could you try to change graph options to see if it is updated correctly then? An option change triggers a refresh of the graph. Try to change grouping or else and let me know


update mapzen ui

Lgtm, please merge.
Doesn't require any release.

On Nov 4, 2016, at 08:55, Peter Richardson<EMAIL_ADDRESS>wrote:
You can view, comment on, or merge this pull request online at:
https://github.com/tangrams/zinc-style-no-labels/pull/2
Commit Summary
update mapzen ui
File Changes
M index.html (2)
Patch Links:
https://github.com/tangrams/zinc-style-no-labels/pull/2.patch
https://github.com/tangrams/zinc-style-no-labels/pull/2.diff
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Adding dedicated file for STF test results.

The results of each test task will be written to that file as PASS or FAIL.
The file will be placed on undercloud machine and could be viewable from Jenkins job tree.

The output of the test results file looks like this:
controller-2 collectd container status: PASS
controller-1 collectd container status: PASS
controller-0 collectd container status: PASS
compute-0 collectd container status: PASS
compute-1 collectd container status: PASS
ceph-0 collectd container status: PASS
controller-0 collectd metrics status: PASS
controller-2 collectd metrics status: PASS
controller-1 collectd metrics status: PASS
compute-0 collectd metrics status: PASS
compute-1 collectd metrics status: PASS
ceph-0 collectd metrics status: PASS
controller-0 collectd metrics value status: PASS
controller-2 collectd metrics value status: PASS
controller-1 collectd metrics value status: PASS
compute-0 collectd metrics value status: PASS
compute-1 collectd metrics value status: PASS
ceph-0 collectd metrics value status: PASS
controller-0 metrics_qdr  container status: PASS
controller-1 metrics_qdr  container status: PASS
controller-2 metrics_qdr  container status: PASS
compute-1 metrics_qdr  container status: PASS
compute-0 metrics_qdr  container status: PASS
ceph-0 metrics_qdr  container status: PASS
controller-0 metrics_qdr number of messages: PASS
controller-2 metrics_qdr number of messages: PASS
controller-1 metrics_qdr number of messages: PASS
compute-0 metrics_qdr number of messages: PASS
compute-1 metrics_qdr number of messages: PASS
ceph-0 metrics_qdr number of messages: PASS
PASS: 30
FAIL: 0


About test code

Hello,
It seems that there is only the training code.
Can you provide the test code used for the evaluation in the paper?

I have added the test code for the result generation.
Thank you.

ok，message received.
I will run and test the code.
Thanks!
Best regards,
Python II chapter master,
JQY
发自我的iPhone
------------------ Original ------------------
From: zzh-tech<EMAIL_ADDRESS>Date: Mon,Sep 21,2020 2:51 PM
To: zzh-tech/ESTRNN<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [zzh-tech/ESTRNN] About test code (#1)
I have added the test code for the result generation.
Thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I have added the test code for the result generation.
Thank you.

Thank you for uploading the test code.
However, I have still some issues with training and test codes.
Please comment on these issues.

Test accuracy is much lower than valid accuracy during training. Visual results are also not sharp.
For a single GPU model, the test PSNR is 29.83dB while the best validation PSNR is 30.73dB.
I trained the model with the old source code.

Model performance (validation accuracies) seems to depends on the number of GPUs used in training. (used ddp mode)

Example logs)

1 GPU used
2020/09/17, 15:37:23 - [Epoch 500 / lr 2.50e-05]
[train] epoch time: 401.73s, average batch time: 0.84s
[train] 1MSE : 65.95 (best 62.06), PSNR : 31.84 (best 32.14)
[valid] epoch time: 93.00s, average batch time: 0.37s
[valid] 1MSE : 89.95 (best 80.37), PSNR : 30.22 (best 30.73)

2 GPUs used
2020/09/19, 18:02:29 - [Epoch 500 / lr 2.50e-05]
[train] epoch time: 179.98s, average batch time: 0.75s
[train] 1MSE : 71.04 (best 68.76), PSNR : 31.23 (best 31.40)
[valid] epoch time: 36.07s, average batch time: 0.28s
[valid] 1MSE : 95.21 (best 88.25), PSNR : 29.76 (best 30.21)

4 GPUs used
2020/09/18, 05:00:53 - [Epoch 500 / lr 2.50e-05]
[train] epoch time: 103.80s, average batch time: 0.86s
[train] 1MSE : 95.22 (best 85.12), PSNR : 30.19 (best 30.54)
[valid] epoch time: 22.33s, average batch time: 0.35s
[valid] 1MSE : 110.71 (best 99.94), PSNR : 29.06 (best 29.52)

As for issue #1:
The PSNR values for our model and other models are all calculated through one round of random cropped (256x256) test dataloader (Not on full resolution video). What we want to compare is the deblurring efficiency of each model under same experimental conditions. Actually, if you want to get sharper results, you could increase the training epochs since the model is not converged at 500 epochs. And you can use larger model configuration, e.g., increasing "n_blocks" and "n_feats" as we did in the paper.
As for issue #2:
If you use ddp mode, the real batch size is "num_gpus*batch_size", which means each process (GPU) will use the batch size you set in "para". Batch size will affect the performance of the model. In general, small batch size is better with the same training epochs, but I believe the effect of hyper-paramter "frames" is coupled to batch size. This also applies to other model like IFIRNN.
Thank you.

For issue #2, I see your reply.
However, for issue #1, the my training setting is same as the model (B9C80) in the paper, which is trained for 500 epoch and shows the PSNR 30.79 dB.
Validation accuracy is similar to the paper's value although its accuracy is calculated from random crops.
My test accuracy is much lower than the paper's value.
I think that there may be a problem in the test code.
Could you provide the pretrained model or check again that the current test code is valid?

I didn't write the code in the test function to calculate PSNR since the validation and test in GOPRO is same.
Could you please send me your code to calculate PSNR and your (B9C80) checkpoint?
My email<EMAIL_ADDRESS>Thank you

You mean that PSNR values in Table. 1 in the paper are validation accuracies, calculated from random crops?
Thank you

Yes, it may seem strange.
But, at 500 epochs, all the models are not converged, I have to choose one value to compare.
So I chose the best one of each model.
I run all the other models in the same way, from this perspective the comparison is fair.
And when you run enough epochs (over 500), the current valid PSNR will be very close to best one.
Sorry to confuse you.

OK I see, my question is settled.
Thank you.
I will close this issue.


Show some error message when the given passphrase is wrong

Currently the underline expect script always return 0, and we can not tell whether the unlocking process is succeed or not.
From expect document: Manpage of EXPECT

status (or 0 if not specified) is returned as the exit status of Expect. exit is implicitly executed if the end of the script is reached.

We can check the return value of gpg process and show some helpful message to users.

The following expect script may help, which use Tcl command substitution on expect command wait.
set result [lindex [wait] 3]
exit $result

The forth return value of the wait command is the return value of the spawned process or errno set by the operating system.

Tcl Built-In Commands - Tcl manual page
Manpage of EXPECT

Fixed in #3


DBSUpload in infinite loop due to wrong datatier

If a wrong output module is defined in the workflow configuration, the DBSUpload is not able to insert it  and it gets into an infinite loop trying to do so. Restarting the component doesn't help, so everything that is running on the agent won't be registered in the DBS.

Closing it since AFAIK a new datatier gets created if it's not available.


Opening a WSL tab really quickly upon sign in does not add Windows Paths to PATH variable

Environment
Windows build number: 18972

Any other software?: WSL installed

Steps to reproduce

Sign out of Windows
Sign back in
Start Terminal really quickly and open up a WSL instance
The WSL instance does not have Windows file paths connected to it (e.g: typing in cmd.exe fails)

Expected behavior

Even if you open up WSL quickly it should add Windows paths correctly.

Actual behavior

Opening WSL quickly from Windows Terminal upon signing in does not add in Windows file paths correctly

Additional notes
We (the WSL team) don't think this is a WSL specific issue since we use environment variables to add the Windows path. If you open up a CMD window and run wsl very quickly upon startup you still get the correct Windows paths added. This seems to be an issue with how Windows Terminal treats environment variables.

Windows Terminal doesn't treat environment variables in any particular way. Perhaps this is #1125?

Unless WSL is somehow loading the user's PATH from some source other than the actual active environment, there's nothing we can do about this.


Backport #18046 to v1.19.x

Disabling cares on android should be backported to v1.19.x.

Disabed in #18050


Bump metrics-bom from 4.1.20 to 4.2.0-rc.1

Bumps metrics-bom from 4.1.20 to 4.2.0-rc.1.

Release notes
Commits

As a preparation for a Dropwizard 2.1.0 prerelease.


Incorrect port number

In websocket config docs, port number have to be 5001 as described in text explanation instead of 50000.

In websocket config docs, port number have to be 5001 as described in text explanation instead of 50000.

Hi Onurkan!
Yes, you are right, ports do not match now in SignalR paragraph.
But it is still not clear: should it be 5001 or 50000 actually?
Let's ask Tom, and he will decide.

Hi @raman-m .
It should be 5001

Duplicate of #1678
@onurkanbakirci
Thank you, Onurkan Bakırcı!

Duplicate of #1678


Failed to load multiple jar packages

jar_path1 = './lib/A.jar'
jar_path2 = './lib/B.jar'
jar_path = "-Djava.class.path=%s;%s"%(jar_path1,jar_path2)
TypeError: Class com.XXX.XXX.XXX is not found
How can I further position？Thanks！！！

Confirm that the class path is correct

Additional informations：
jar_path1 = './lib/gmssl/security-0.0.1-SNAPSHOT-jar-with-dependencies.jar'
jar_path2 = './lib/gmssl/welink-java-sdk.jar'
jar_path = "-Djava.class.path=%s;%s"%(jar_path1,jar_path2)
jvmpath = jpype.getDefaultJVMPath()
if not jpype.isJVMStarted():
jpype.startJVM(jvmpath, "-ea", jar_path)
TypeError: Class com.XXX.XXX.XXX is not found

Did you try
jpype.startJVM('-ea', classpath=['path1', 'path2'])
print(jpype.java.lang.System.getProperty('java.class.path'))

it’s work! thanks！
jpype.startJVM('-ea', classpath=['path1', 'path2'])
print(jpype.java.lang.System.getProperty('java.class.path'))

The old method that required people to formulate the java.class.path manually was too error prone and resulted in code that did not work across platforms (windows/linux) so I added the list form keyword which is much safer.


fix after_encode_and_sign dialyzer_error

Fixes https://github.com/ueberauth/guardian/issues/252

Thank you @ericsullivan!  While we're updating the typespecs we don't we fix after_sign_in/2?  Based on the code here it does not return a connection:
https://github.com/ueberauth/guardian/blob/9720eb6fc5278a9945f4235b0488f7480aeaa086/lib/guardian/plug.ex#L179-L184

I put additional updates to the typespec in a different PR because dialyzer failed without this change, but wasn't complaining about the other code. Should "mix dialyzer" be added to travis.yml?
I think after_sign_in does return a conn. The default hook implementation returns conn and the api_sign_in also has a method signature that returns conn.

@ericsullivan if you can rebase this to resolve the conflict I'd be happy to merge 👍

https://github.com/ueberauth/guardian/pull/256 actually included this fix. Since that was merged first this is no longer needed.


Animate right away

Is there an easy way to get the image shown and start animating right away? It seems it needs to complete one cycle first, which will last for an interval within the durationRange.
A working dirty hack is doing something like this:
private var firstRun = true
func startNewAnimation() {
    var dur = durationRange
    if firstRun {
        firstRun = false
        dur = DurationRange(0, max: 0.1)
    }
    currentImageView.transform = CGAffineTransform.identity
    currentImageView.size = self.size
    let animation = KenBurnsAnimation(targetImage: currentImageView, zoomIntensity: zoomIntensity, durationRange: dur, pansAcross: pansAcross)
    animation.completion = self.didFinishAnimation
    animation.willFadeOut = self.willFadeOutAnimation
    animations.append(animation)
}

@thbaja you should just need to call setImage before startAnimating right?  That sets the image immediately.

Sorry for not getting back to you on this issue before, but now I've had a chance to take a look on it.
I'm using autolayout to set up the UI including the KenBurnsImageView. I do this on viewDidLoad, which means the subviews haven't been laid out yet giving a size of zero. When starting a new animation cycle the size of self is used, which can be seen in the code snippet above.
That is why I had to wait an animation cycle before seeing the image and animation.
For future reference I think the best solutions in prioritized order are:

Don't use autolayout.
Alternative is to start animation in viewDidLayoutSubviews, but one needs to be aware that this can be called several times.
Starting animations in viewDidAppear is a bit to late and doesn't look good.

Thanks for the thorough discussion @thbaja


Using react-redux-form and redux-thunk

Hello, I am attempting to add in react-redux-form into my boilerplate app and having a difficult time understanding how the dispatches work.
I have a 3 tier compotenent, FuelingPage, FuelingForm, and FuelingFormFirstPage.
How would I access dispatch from FuelingFormFirstPage or even FuelingForm as instructed here: https://davidkpiano.gitbooks.io/react-redux-form/content/validation.html ? I am trying to validate the form input before changing the page state to the next page.
My current setup is exactly like the existing example with the addition of a changePage action which changes the appState's page.

To dispatch an action in a child component, pass a function down from your container component.  I suggesting passing the bound action down via props to your child components. Check the Redux docs for bindActionCreators for a handy helper method.


generate hived config from layout.yaml

Coverage remained the same at 33.977% when pulling 0b84481525f53ffe5b38b16519929bbcb2036e8f on suiguoxin:hived into 27ddacabb21c7b8c3a49afdd470138dbf0eb14b1 on microsoft:master.


Automatic Save Prompt fails for new files after session

[This is likely related to Issue #206]
New file's status is forgotten between Parallax IDE sessions - leading to loss.

Create a new file
Don't save it
Close Parallax IDE
Start Parallax IDE
[Source is displayed, as expected]
Select another file from the Project/File view
Parallax IDE immediately displays selected file without prompting to save the new and unsaved file first

The new and unsaved file is lost forever

NOTE: When this is fixed, make sure the solution doesn't negatively affect the scenario where the user has modified an existing file, closed Parallax IDE, started Parallax IDE and navigated away to another file- this currently works perfectly as expected.

Due to the filesystem refactor, this should be fixed in sprint 8.

Looking forward to it.

Unable to fully test this because of issues #231, #232, #234, #235, and #236.

Verified fixed.


ziti edge create auth policy --primary-ext-jwt-allowed-signers does not support name or id

 ziti edge create auth-policy a0-ap --primary-ext-jwt-allowed --primary-ext-jwt-allowed-signers a0 --output-request-json
Where a0 is a name.
could not copy request body: <nil>error: response status code does not match any response statuses defined for this endpoint in the swagger spec (status 404): {}

Download
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
In the installer menu, select "gcc."


ESM: relative paths do not work from command line

Steps to Reproduce:

Run code-exploration .
It opens the root

Maybe the current working directory is not properly set?

Verification: use the latest released exploration build from https://builds.code.visualstudio.com/builds/exploration


Update script.js and contributing.md

Hi @ShahbaazX786
Thankyou for contributing but this PR has some conflicts. Please take a fresh pull and re-raise the PR after resolving this.


some docs correction

https://github.com/PLhery/node-twitter-api-v2/blob/36821932dbde93129168e8b47af4e1e377552bde/doc/basics.md#make-requests-behind-a-proxy

should be new TwitterApi(bearToken, {'httpAgent': proxyAgent}) instead of new TwitterApi(bearToken, {proxyAgent}) according to https://github.com/PLhery/node-twitter-api-v2/blob/6cd5558d82d036371e30e73a085e1b3a4517447e/src/types/client.types.ts#L70

I think this issue has been fixed already, why is it not closed....


Split Place command key-binding ignore current profile and open default profile

Windows Terminal version
1.17.1023
Windows build number
10.0.22621.0
Other Software
No response
Steps to reproduce

Open Windows Terminal in non-default Profile such as VS Command Prompt
Hit <Shift-Alt-+> a new terminal pane is opened on right
The new split is opened in Default Profile
However if I right click on tab and select "Split Tab" the split pane is opened in the current profile

Expected Behavior
<Shift-Alt-+> a new terminal pane is opened on right with the Current Profile
Actual Behavior
<Shift-Alt-+> a new terminal pane is opened on right with the Default Profile

Yep, the splitPane action has another arg for behaving in the duplicating way which the default keybindings don't have. You can add "splitMode":"duplicate" to the actions to get that behavior, like so:
{ "command": { "action": "splitPane", "split": "down", "splitMode":"duplicate" }, "keys": "alt+shift+-" },
{ "command": { "action": "splitPane", "split": "right", "splitMode":"duplicate" }, "keys": "alt+shift+plus" },

We probably won't be able to change this though, as we've shipped that keybinding without the duplicate for a few years now, and we don't want to break everyone who does like it opening the default profile.
Thanks!

Then a better option will be to add update the default settings.json file. And there is no way a bug fix can break expectations.
If people love Default Profile then the behaviour should be same in the UI menu options as well. Currently there is no way to duplicate Default Profile using the mouse.
A bug is a bug, not a feature in disguise, there will be no love lost for having a consistent behaviour in UI and KeyBindings


Include version IDs for "first" versions

It seems like we are not including the version IDs for the "first" versions of documents. I'm not sure what the technical limitations are, but we should do our best to retain this information as part of the export format.

I looked into this a bit more. The fact that docs have a version prop is a bit of a bug/artifact I think because we kappa-osm was not omitting that prop when writing. When reading the version prop is overwritten. As such, I think the version prop read from the doc is actually incorrect, and is the version of the previous document.


Save streams per worksheet not workbook

See https://speckle.community/t/speckle-excel-connector-slow/3794/11

Closing this ticket as we are moving to Jira to reduce noise. You can access it there.


ReduxDevTools problem on 3.0.0

After upgrading on<EMAIL_ADDRESS>the Redux DevTools no longer inspect state.
I've tried with @ngrx/store-log-monitor:3.0.0 and its fine.

same issue...

same here :(

Is there an estimate time of fixing this bug?

Here is what needs to be done to fix all the problems:

A typo which makes ReduxDevtoolsExtension undiscoverable.

instrument.ts
export function _createReduxDevtoolsExtension() {`
  if (typeof window !== 'undefined' && (window as any).devToolsExtension) {`
    return (window as any).devtoolsExtension;`  // <- typo, should be devToolsExtension
  }

  return null;
}

A bug causing the redirection of lifted actions into the regular dispatch

extension.ts
    // Listen for unlifted actions
    const actions$ = applyOperators(changes$, [
      //[ filter, change => change.type === ExtensionActionTypes.DISPATCH ], // that's incorrect
      [ filter, change => change.type === ExtensionActionTypes.ACTION ],     // that's correct
      [ map, change => change.payload ]
    ]);

A bug preventing the ReduxDevtoolsExtension from being notified about the lifted state changes

extension.ts
  notify(action, state: LiftedState) {
    if (!this.devtoolsExtension /*|| action.type !== ActionTypes.PERFORM_ACTION*/) { // we should notify of everything
      return;
    }

    //this.devtoolsExtension.send(unliftAction(state), unliftState(state), false, this.instanceId); // this doesn't seem to be needed
    this.devtoolsExtension.send(null, state, false, this.instanceId);
  }

@avoskresensky Ive done what youve said but still no change..

for me it worked

Do the changes in the transpiled js files instead of the typescript source, at least that what I had to do.

And another bug preventing the dispatching of hand-created actions:

extension.ts
    // Listen for unlifted actions
    const actions$ = applyOperators(changes$, [
      [ filter, change => change.type === ExtensionActionTypes.DISPATCH ],
   // [ map, change => change.payload ] <- this doesn't work, the payload is a string
       [map, function (change) { return typeof change.payload === 'string' ? eval('(' + change.payload + ')') : change.payload; }]
    ]);

@ritox842, as @Sn3b correctly said, you'll need to modify the JS files if you want to patch your node module in place after the installation.
I'm providing the references to the original TS files to expedite the proper fix.
I've no time to make a fork and issue a PR at the moment, so that'll have to be it for now.

@avoskresensky Big thanks for tracking down the changes. ❤ I know you don't have time to send me a PR but can you shoot me your email address so I can set you as the commit author on the patch?

Fixed in v3.1.0. I'll make an official announcement a little later but as a bonus I've added the ability to apply the instrumentation conditionally if the extension is present. This will not work if you also want to use @ngrx/store-log-monitor.
Usage:
@NgModule({
  imports: [
    StoreDevtoolsModule.instrumentOnlyWithExtension()
  ]
})
export class AppModule { }

instrumentOnlyWithExtension() is AOT friendly making it ready for production builds.
Big thanks again to @avoskresensky for fixing the extension interop.

I did changed the .js files..
Any way, Iv'e upgrade the devtools to 3.1.0 and now it works.
Many Thanks @avoskresensky @MikeRyan52 !!!!!

Thanks @avoskresensky and @MikeRyan52!
@MikeRyan52 if you have time maybe you should update the changelog, and let the others know about the instrumentOnlyWithExtension() feeture. Maybe not everyone reads commits and closed issues and it can be helpful.

Thank you @avoskresensky for patching and @MikeRyan52 for update release.
Great work, maybe next time I will help you on troubleshooting and resolution :D

Thanks @avoskresensky and @MikeRyan52 :+1:


Add fullscreen control to window API

The full screen parameter in the window constructor doesn't maximize the window, it makes the browser control full screen. This might be right in some situations, but there should be a way to make the window appear maximized.

done in v2


Dmp 3986.media linked case enhance

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/DMP-3986
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x ] No

Looks fine, but would feel better if a integration test had a check in it for the new columns being populated correctly


Add table of student's repositories to show roster_student page

This pull request partially addresses issue #89. It implements a rudimentary substring matching way of listing a student's GitHub repositories within a course organization. For reasons elaborated on in exhaustive detail here, it is resource prohibitive to use GitHub's API to generate a list of repositories in an organization that a user has either created or contributed to. For this reason, @pconrad and I decided to implement this functionality for the time being by simply showing repositories in the organization whose name contain the user's GitHub organization.
It implements a table on the show roster_student page that contains three things:

The repository's name, which is a hyperlink to the repository on GitHub.com
Other contributors to the repository: this uses the same matching logic as explained above to find any other student's GitHub ID contained in the repository's name and lists their name.
The date the repository was last modified.

The show roster_student page now looks like this when the student has an associated GitHub ID:

10201f8 successfully resolved TravisCI test failure. Problem was with the stub that facilitated the test running, not anything to do with functionality.


Changing directory is not case-sensitive on Windows, making the CWD in the BubbleOS prompt look strange

Using the cd command to change into a directory such as c:\this\is\a\test will make the current working directory on BubbleOS that path, with the incorrect casing (drive letter should be capitalized). Even though Windows paths are not case-sensitive, the Command Prompt and PowerShell both show case-sensitive paths, which BubbleOS does not have, making it look strange in some cases.
The path will persist until BubbleOS is restarted or the correct casing is entered in cd.

This issue has been present since the first version of BubbleOS, v0.1.5, making this the oldest known issue in BubbleOS so far. Wow!


Added World Clock Extension

Description
This JS extension displays the current time for selected cities across the world. This extension allows users to easily add or remove cities. It provides a user-friendly interface with clear labeling and intuitive controls for managing the world clocks.
Fixes:  #210

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[X] I have made this from my own
[ ] I have taken help from some online resourses
[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[X] My changes generate no new warnings

@Sulagna-Dutta-Roy Pls review my PR and merge it if it is good to go

Yes, I am working on it. Currently it's a mess from my side. Thanks for the patience


NOISSUE - Update authors list

Add Dejan's recognition
Signed-off-by: drasko<EMAIL_ADDRESS>

Codecov Report

Merging #569 into master will decrease coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #569      +/-   ##
==========================================
- Coverage   86.92%   86.86%   -0.06%
==========================================
  Files          62       62
  Lines        3381     3381
==========================================
- Hits         2939     2937       -2
- Misses        304      305       +1
- Partials      138      139       +1

Impacted Files
Coverage Δ

writers/cassandra/init.go
60% <0%> (-20%)
:arrow_down:

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 dc16eb5...eefe4cc. Read the comment docs.


Cant run on windows container

Sending build context to Docker daemon  4.791MB
Step 1/12 : FROM mcr.microsoft.com/dotnet/core/sdk:2.2 AS build
2.2: Pulling from dotnet/core/sdk
no matching manifest for windows/amd64 10.0.16299 in the manifest list entries

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

ID: 3653642e-61ef-717b-5436-9bd0a3c4e6f4
Version Independent ID: 80c1ce51-46fb-0693-525a-7cad37150c7b
Content: Docker images for ASP.NET Core
Content Source: aspnetcore/host-and-deploy/docker/building-net-docker-images.md
Product: aspnet-core
Technology: aspnetcore-hostdeploy
GitHub Login: @tdykstra
Microsoft Alias: tdykstra

cc @spboyer

@kmukul123 - I was able to pull the image direct.
> docker pull mcr.microsoft.com/dotnet/core/sdk:2.2
Pulling from dotnet/core/sdk
e46172273a4e: Downloading [>

Try running the docker pull command and/or restarting docker. (right click the whale in the task tray).
docker pull mcr.microsoft.com/dotnet/core/sdk:2.2

Thanks for contacting us. We believe that the question you've raised have been answered. If you still feel a need to continue the discussion, feel free to reopen it and add your comments.


scalajs-compiler, scalajs-library, ... 1.5.0 (was 0.6.33)

Updates

org.scala-js:scalajs-compiler
org.scala-js:scalajs-library
org.scala-js:scalajs-test-bridge

from 0.6.33 to 1.5.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-js" } ]

labels: library-update, semver-major

I've included this in #393


[FEATURE] wash app undeploy should accept files as the argument

Documentation says: "You can think of a wadm application like a Kubernetes Deployment." . Since people are familiar to Kubernetes, it would be advantageous if wadm behaved analogous to Kubernetes. At least, in terms of the undeployment of an app, this is not the case:
# deploy with kubernetes
kubectl apply -f deployment.yaml

# undeploy with kubernetes
kubectl delete -f deployment.yaml

with Wash/Wadm/Wasmcloud, I faced:
$ wash app deploy wadm.yaml
Successfully deployed model rust-http-hello-world v0.0.3

$ wash app undeploy wadm.yaml
Invalid subject: Found extra components of subject, ensure your manifest name consists of only alphanumeric characters, dashes, and underscores.

$ wash app list

  Name                    Latest Version   Deployed Version   Deploy Status   Description
  rust-http-hello-world   v0.0.3           v0.0.3              Compensating   HTTP hello world demo in Rust, using the WebAssembly Component Model and WebAssembly Interfaces Types (WIT)

$ wash app undeploy rust-http-hello-world
Successfully undeployed model rust-http-hello-world

Therefore, the following feature request: wash app undeploy wadm.yaml should undeploy the app which it previously deployed via wash app deploy wadm.yaml.

Hello folks. After speaking with Brooks Townsend on the Slack channel, I would like to get this issue assigned. Thank you.

Thank you, Brooks. I am now working on it and will open a WIP: PR asap.

#1495

Hey @thomastaylor312 note that we have this supported in wash delete -- I just made a quick PR for this as well


Add check list.json also add pdf

Add checklist

@tk-t0n0y Can you be more specific?
If you're asking for another format besides markdown for the mind map, you have some tools that can convert it for you. Also, markmap (what is being used to generate the mind map from the markdown) renders in SVG so I guess is also possible to convert it to PDF.
Does this solves your request?

Hello , how to download this mindmap ?

@jsnode2121212 its currently on the todo list :)


Rapid lag build up with prefabs

2 or 3 prefabs is enough to lag one of my players solid when detached the lang ceases to be an issue think it might hav somthing to do with a version compatability isssue

The version compatibility is just a general indicator that I haven't made any updates for the most recent version nothing more.
Can you look in the console of the player if it's spamming error messages maybe?


[Home] Wallet card - Text overlap in CRC currency

App version: v0.1.91

Select CRC in Settings :: Currency.
Have a 1m sats in the wallet.
The crc value overlaps with 'Spendable on-chain' label

I think we should move the Wallet type 'Spendable Onchain' to the left column. @mocodesmo

Moved all text items to the left


Delta Message Compression support not listed in the Known Limitations

Does ably-flutter currently support Delta Message Compression? I know it is not listed in the readme, but I see the PR (https://github.com/ably/ably-flutter/pull/123) is still open. @tiholic / @QuintinWillison ?
If this is correct, @AndyNicks we will need to update the readme (add it to the Known Limitations section) and also correct the feature support matrix once again.

@kavalerov DeltaCompression is still not available for flutter.
#123 aims to add support for delta extension in MessageExtras and it may need wait for an update from ably-java.
ref: discussion 1, discussion 2

I added Delta Compression to Known Limitations section of README as well as updated the Matrix

Considering the above I think we can close this issue.