Error re signing request when running integration tests

@tyler-ball asked me to try running the integration tests to see if I got similar problems to @metadave.
I've checked I can create resources in eu-west-1 using with_driver 'aws::eu-west-1'
To run the integration tests, I did the following:
bundle install --path vendor
export AWS_TEST_DRIVER=aws::eu-west-1
bundle exec rspec -b
Most of the tests fail with:
ERROR Cannot sign the request without a client name, check that :node_name is assigned
Attached is the output (sanitized).
I did notice this:
     driver #<Chef::Provisioning::AWSDriver::Driver:0x0000000cc3a800 @driver_url="aws::eu-west-1", @config={:log_level=>:info, :chef_server_url=>"https://localhost:443",
      :node_name=>nil, :client_key=>"/etc/chef/client.pem", :http_retry_count=>0, :authentication_protocol_version=>"1.0",

which suggests the node_name is not getting set.
Other possible relevant things:

Nothing was created in nodes
I do not have a xxx.pem or knife.rb in ~/.chef  (but I can run chef-client -z and create machine). I tried creating one but it does not make a difference.
I have my secret key in .aws/credentials, not in .aws/config
To be able to converge an AWS instance in eu-west-1, I had to add inbound SSH rule as the default VPC does not allow this.

---- rspec -b output
Run options:
  include {:focus=>true}
  exclude {:super_slow=>true}

All examples were filtered out; ignoring {:focus=>true}

Chef::Resource::AwsCacheSubnetGroup
  When the Chef server exists
    when the chef repo exists and with a VPC with an internet gateway and subnet
ERROR Cannot sign the request without a client name, check that :node_name is assigned
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/authenticator.rb:88:in `authentication_headers'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/authenticator.rb:43:in `handle_request'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http.rb:226:in `block in apply_request_middleware'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http.rb:224:in `each'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http.rb:224:in `inject'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http.rb:224:in `apply_request_middleware'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http.rb:141:in `request'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http.rb:110:in `get'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-provisioning-1.2.0/lib/chef/provisioning/chef_managed_entry_store.rb:30:in `get_data'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-provisioning-1.2.0/lib/chef/provisioning/managed_entry_store.rb:72:in `get'
/home/christine/git/chef-provisioning-aws/lib/chef/provisioning/aws_driver/aws_resource_with_entry.rb:50:in `get_id_from_managed_entry'
/home/christine/git/chef-provisioning-aws/lib/chef/provisioning/aws_driver/aws_resource_with_entry.rb:90:in `get_driver_and_id'
/home/christine/git/chef-provisioning-aws/lib/chef/provisioning/aws_driver/aws_resource_with_entry.rb:65:in `to_s'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/formatters/doc.rb:215:in `resource_action_start'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/event_dispatch/dispatcher.rb:29:in `block (2 levels) in def_forwarding_method'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/event_dispatch/dispatcher.rb:29:in `each'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/event_dispatch/dispatcher.rb:29:in `block in def_forwarding_method'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/resource.rb:540:in `run_action'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/runner.rb:49:in `run_action'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/runner.rb:81:in `block (2 levels) in converge'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/runner.rb:81:in `each'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/runner.rb:81:in `block in converge'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/resource_collection/resource_list.rb:83:in `block in execute_each_resource'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/resource_collection/stepable_iterator.rb:116:in `call'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/resource_collection/stepable_iterator.rb:116:in `call_iterator_block'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/resource_collection/stepable_iterator.rb:85:in `step'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/resource_collection/stepable_iterator.rb:104:in `iterate'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/resource_collection/stepable_iterator.rb:55:in `each_with_index'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/resource_collection/resource_list.rb:81:in `execute_each_resource'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/runner.rb:80:in `converge'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/cheffish-1.2/lib/cheffish/basic_chef_client.rb:69:in `block in converge'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/cheffish-1.2/lib/cheffish/basic_chef_client.rb:133:in `call'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/cheffish-1.2/lib/cheffish/basic_chef_client.rb:133:in `with_chef_config'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/cheffish-1.2/lib/cheffish/basic_chef_client.rb:68:in `converge'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/cheffish-1.2/lib/cheffish/chef_run.rb:85:in `converge'
/home/christine/git/chef-provisioning-aws/spec/aws_support.rb:145:in `block (4 levels) in <module:WithAWSClassMethods>'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/hooks.rb:357:in `instance_exec'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/hooks.rb:357:in `run'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/hooks.rb:521:in `block in run_owned_hooks_for'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/hooks.rb:520:in `each'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/hooks.rb:520:in `run_owned_hooks_for'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/hooks.rb:473:in `run'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/example_group.rb:472:in `block in run_before_context_hooks'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/memoized_helpers.rb:186:in `block in isolate_for_context_hook'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/memoized_helpers.rb:182:in `instance_exec'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/memoized_helpers.rb:182:in `isolate_for_context_hook'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/example_group.rb:471:in `run_before_context_hooks'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/example_group.rb:520:in `run'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/example_group.rb:522:in `block in run'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/example_group.rb:522:in `map'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/example_group.rb:522:in `run'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/example_group.rb:522:in `block in run'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/example_group.rb:522:in `map'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/example_group.rb:522:in `run'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/runner.rb:115:in `block (3 levels) in run_specs'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/runner.rb:115:in `map'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/runner.rb:115:in `block (2 levels) in run_specs'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/configuration.rb:1627:in `with_suite_hooks'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/runner.rb:114:in `block in run_specs'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/reporter.rb:77:in `report'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/runner.rb:113:in `run_specs'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/runner.rb:89:in `run'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/runner.rb:73:in `run'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/lib/rspec/core/runner.rb:41:in `invoke'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/rspec-core-3.3.0/exe/rspec:4:in `<top (required)>'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/bin/rspec:23:in `load'
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/bin/rspec:23:in `<main>'
      aws_cache_subnet_group 'test-subnet-group' creates a cache subnet group (FAILED - 1)

An error occurred in an `after(:context)` hook.
  ArgumentError: Cannot sign the request without a client name, check that :node_name is assigned
  occurred at /home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'

Chef::Resource::AwsEbsVolume
  When the Chef server exists
    when the chef repo exists and when connected to AWS
      aws_ebs_volume 'test_volume' creates an ebs volume
Recipe: basic_chef_client::block
Recipe: basic_chef_client::block
      aws_ebs_volume 'test_volume_az' creates an ebs volume when provided proper full AZ
      action :delete
[2015-06-18T16:58:49-05:00] INFO: Running queued delayed notifications before re-raising exception
[2015-06-18T16:58:49-05:00] INFO: Running queued delayed notifications before re-raising exception
        deletes the ebs volume

Chef::Resource::AwsKeyPair
  When the Chef server exists
    when the chef repo exists and when connected to AWS
      aws_key_pair 'test_key_pair' creates a key pair

Chef::Resource::AwsRouteTable
  When the Chef server exists
    when the chef repo exists and with a VPC with an internet gateway
ERROR Cannot sign the request without a client name, check that :node_name is assigned
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'
<REMOVED - SAME AS PREVIOUS>

      aws_route_table 'test_route_table' with no parameters except VPC creates a route table (FAILED - 2)
      aws_route_table 'test_route_table' with routes creates a route table (FAILED - 3)
      ignores routes whose target matches ignore_route_targets (FAILED - 4)

An error occurred in an `after(:context)` hook.
  ArgumentError: Cannot sign the request without a client name, check that :node_name is assigned
  occurred at /home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'

Chef::Resource::AwsSecurityGroup
  When the Chef server exists
    when the chef repo exists and without a VPC
      aws_security_group 'test_sg' with no attributes works
Recipe: basic_chef_client::block
Recipe: basic_chef_client::block
      can reference a security group by name or id
      raises an error trying to reference a security group by an unknown id
    when the chef repo exists and in a VPC
ERROR Cannot sign the request without a client name, check that :node_name is assigned
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'
<REMOVED - SAME AS PREVIOUS>
      aws_security_group 'test_sg' with no attributes works (FAILED - 5)
      aws_security_group 'test_sg' with inbound and outbound rules works (FAILED - 6)

An error occurred in an `after(:context)` hook.
  ArgumentError: Cannot sign the request without a client name, check that :node_name is assigned
  occurred at /home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'

    when the chef repo exists and when narrowing from multiple VPCs
ERROR Cannot sign the request without a client name, check that :node_name is assigned
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'
<REMOVED - SAME AS PREVIOUS>
      raises an error if it finds multiple security groups (FAILED - 7)
      correctly returns the security group when vpc is specified (FAILED - 8)

An error occurred in an `after(:context)` hook.
  ArgumentError: aws_security_group[test_sg] (basic_chef_client::block line 113) had an error: ArgumentError: Cannot sign the request without a client name, check that :node_name is assigned
  occurred at /home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'

An error occurred in an `after(:context)` hook.
  ArgumentError: Cannot sign the request without a client name, check that :node_name is assigned
  occurred at /home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'

Chef::Resource::AwsSubnet
  When the Chef server exists
    when the chef repo exists and with a VPC with an internet gateway and route table
ERROR Cannot sign the request without a client name, check that :node_name is assigned
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'
<REMOVED - SAME AS PREVIOUS>
      aws_subnet 'test_subnet' with no parameters except VPC creates a route table (FAILED - 9)
      aws_subnet 'test_subnet' with all parameters creates a route table (FAILED - 10)

An error occurred in an `after(:context)` hook.
  ArgumentError: Cannot sign the request without a client name, check that :node_name is assigned
  occurred at /home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'

AWS Tagged Items
  When the Chef server exists
    when the chef repo exists and when connected to AWS
Recipe: basic_chef_client::block
Recipe: basic_chef_client::block
Recipe: basic_chef_client::block
Recipe: basic_chef_client::block
  * aws_security_group[test_sg] action destroy

    ================================================================================
    Error executing action `destroy` on resource 'aws_security_group[test_sg]'
    ================================================================================

    ArgumentError
    -------------
    Cannot sign the request without a client name, check that :node_name is assigned

    Resource Declaration:
    ---------------------
    # In /home/christine/git/chef-provisioning-aws/spec/integration/aws_security_group_spec.rb

    113:           aws_security_group 'test_sg' do
    114:             vpc 'test_vpc1'
    115:             action :destroy
    116:           end
    117:           aws_security_group 'test_sg' do

    Compiled Resource:
    ------------------
    # Declared in /home/christine/git/chef-provisioning-aws/spec/integration/aws_security_group_spec.rb:113:in `block (5 levels) in <top (required)>'

    aws_security_group("test_sg") do
      action [:destroy]
      retries 0
      retry_delay 2
      default_guard_interpreter :default
      driver #<Chef::Provisioning::AWSDriver::Driver:0x0000000cc3a800 @driver_url="aws::eu-west-1", @config={:log_level=>:info, :chef_server_url=>"https://localhost:443",
      :node_name=>nil, :client_key=>"/etc/chef/client.pem", :http_retry_count=>0, :authentication_protocol_version=>"1.0",
      :driver=>#<Chef::Provisioning::AWSDriver::Driver:0x0000000cc3a800 ...>,
      :stdout=>#<Cheffish::ChefRun::StringIOTee:0x0000000ea54d18
      @streams=[#<AWSSupport::DelayedStream:0x0000000ea31520 @streams=[#<IO:<STDOUT>>], @buffer=#<StringIO:0x0000000ea31458>,
      @thread=#<Thread:0x0000000ea31408 sleep>>]>, :stderr=>#<Cheffish::ChefRun::StringIOTee:0x0000000ea54c28 @streams=[#<AWSSupport::DelayedStream:0x0000000ea312c8 @streams=[#<IO:<STDERR>>], @buffer=#<StringIO:0x0000000ea31200>, @thread=#<Thread:0x0000000ea311b0 sleep>>]>, :log_location=>#<Cheffish::ChefRun::StringIOTee:0x0000000ea54b38 @streams=[#<AWSSupport::DelayedStream:0x0000000ea31098 @streams=[#<IO:<STDOUT>>], @buffer=#<StringIO:0x0000000ea30fd0>, @thread=#<Thread:0x0000000ea30f80 sleep>>]>, :verbose_logging=>false}, @aws_credentials=#<Chef::Provisioning::AWSDriver::Credentials:0x0000000cc3a6e8 @credentials={REMOVED BY CHRISTINE!!!}>, @aws_config=<AWS::Core::Configuration>, @ec2=<AWS::EC2>>
      chef_server {:chef_server_url=>"https://localhost:443", :options=>{:client_name=>nil, :signing_key_filename=>"/etc/chef/client.pem"}}
      declared_type :aws_security_group
      cookbook_name "basic_chef_client"
      recipe_name "block"
      vpc "test_vpc1"
    end

Recipe: basic_chef_client::block
Recipe: basic_chef_client::block
Recipe: basic_chef_client::block
      aws_ebs_volume 'test_volume' created with default Name tag
[2015-06-18T16:59:26-05:00] INFO: Running queued delayed notifications before re-raising exception
[2015-06-18T16:59:26-05:00] INFO: Running queued delayed notifications before re-raising exception
Recipe: basic_chef_client::block
  * aws_ebs_volume[test_volume_a] (no AWS object id) action create
    - create new aws_ebs_volume[test_volume_a] (no AWS object id) in eu-west-1
    - wait for new aws_ebs_volume[test_volume_a] (no AWS object id) in eu-west-1 to become available
    - applying tags {"byebye"=>"true"}
    - create data bag aws_ebs_volume at http://<IP_ADDRESS>:8900/organizations/foo
    - create data bag item test_volume_a at http://<IP_ADDRESS>:8900/organizations/foo
    -   add reference = {"id"=>"vol-dcaecccf"}
    -   add driver_url = "aws::eu-west-1"
  * aws_ebs_volume[test_volume_a] (vol-dcaecccf) action create (up to date)
Recipe: basic_chef_client::block
  * aws_ebs_volume[test_volume_a] (vol-dcaecccf) action create (up to date)
Recipe: basic_chef_client::block
  * aws_ebs_volume[test_volume_a] (vol-dcaecccf) action create
    - applying tags {"Name"=>"test_volume_b", "project"=>"X"}
    - deleting tags ["byebye"]
  * aws_ebs_volume[test_volume_a] (vol-dcaecccf) action create (up to date)
Recipe: basic_chef_client::block
  * aws_ebs_volume[test_volume_a] (vol-dcaecccf) action create (up to date)
      aws_ebs_volume 'test_volume' tags are updated
[2015-06-18T16:59:44-05:00] INFO: Running queued delayed notifications before re-raising exception
[2015-06-18T16:59:44-05:00] INFO: Running queued delayed notifications before re-raising exception
[2015-06-18T16:59:44-05:00] INFO: Running queued delayed notifications before re-raising exception
[2015-06-18T16:59:44-05:00] INFO: Unable to access cache at /var/chef. Switching cache to /home/christine/.chef
[2015-06-18T16:59:44-05:00] INFO: Unable to access cache at /var/chef. Switching cache to /home/christine/.chef
[2015-06-18T16:59:44-05:00] INFO: Unable to access cache at /var/chef. Switching cache to /home/christine/.chef
[2015-06-18T16:59:44-05:00] INFO: Unable to access cache at /var/chef. Switching cache to /home/christine/.chef
[2015-06-18T16:59:44-05:00] INFO: Running queued delayed notifications before re-raising exception
[2015-06-18T16:59:44-05:00] INFO: Running queued delayed notifications before re-raising exception
[2015-06-18T16:59:44-05:00] INFO: Running queued delayed notifications before re-raising exception
[2015-06-18T16:59:44-05:00] INFO: Running queued delayed notifications before re-raising exception
      aws_ebs_volume 'test_volume' tags are not changed when not updated
      aws_ebs_volume 'test_volume' created with new Name tag
      aws_ebs_volume 'test_volume' created with custom tag
Recipe: basic_chef_client::block
  * load_balancer[lbtest] action create
    - create load balancer lbtest in eu-west-1
    -   enable availability zones ["eu-west-1a", "eu-west-1b"]
    -   with listeners [{:protocol=>:http, :port=>80, :instance_port=>80, :instance_protocol=>:http}]
    -   with tags {:marco=>"polo", "happyhappy"=>"joyjoy"}
    - applying tags {"marco"=>"polo", "happyhappy"=>"joyjoy"}
    - create data bag load_balancer at http://<IP_ADDRESS>:8900/organizations/foo
    - create data bag item lbtest at http://<IP_ADDRESS>:8900/organizations/foo
    -   add reference = {"driver_version"=>"1.3.0.dev.1", "allocated_at"=>"2015-06-18 22:01:01 UTC"}
    -   add driver_url = "aws::eu-west-1"
  * load_balancer[lbtest] action create (up to date)
Recipe: basic_chef_client::block
  * load_balancer[lbtest] action create (up to date)
Recipe: basic_chef_client::block
  * load_balancer[lbtest] action create
    - applying tags {"default"=>"value1"}
    - deleting tags ["happyhappy", "marco"]
  * load_balancer[lbtest] action create (up to date)
Recipe: basic_chef_client::block
  * load_balancer[lbtest] action create (up to date)
      load balancer 'lbtest' tagged with load_balancer_options
      does not error when a class does not define #aws_tags

Chef::Resource::AwsVpc
  When the Chef server exists
    when the chef repo exists and When AWS has a DHCP options
ERROR Cannot sign the request without a client name, check that :node_name is assigned
/home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'
<REMOVED - SAME AS PREVIOUS>
      aws_vpc 'vpc' with no attributes fails to create a VPC (must specify cidr_block) (FAILED - 11)
      Creating an aws_vpc
        aws_vpc 'vpc' with cidr_block '<IP_ADDRESS>/24' creates a VPC (FAILED - 12)
        aws_vpc 'vpc' with all attributes creates a VPC (FAILED - 13)
      and an existing VPC with values filled in
        and a route table inside that VPC
          aws_vpc can update the main_route_table to it (FAILED - 14)

An error occurred in an `after(:context)` hook.
  ArgumentError: Cannot sign the request without a client name, check that :node_name is assigned
  occurred at /home/christine/git/chef-provisioning-aws/vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'

Chef::Provisioning::AWSDriver::Credentials
  loading config INI files
    unified config ini file
      loads the 'work_iam' profile from a unified config file
      loads the 'personal' profile from a unified config file
    enterprise config ini file
      loads the 'work_iam' profile from a enterprise config file
      loads the 'enterprise' profile from a enterprise config file
    separate config and credential ini files
      loads the 'work_iam' profile from a separate config files
      loads the 'personal' profile from a separate config files

Failures:

  1) Chef::Resource::AwsCacheSubnetGroup When the Chef server exists when the chef repo exists and with a VPC with an internet gateway and subnet aws_cache_subnet_group 'test-subnet-group' creates a cache subnet group
     Failure/Error: Unable to find matching line from backtrace
     ArgumentError:
       Cannot sign the request without a client name, check that :node_name is assigned
     # ./vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'
<REMOVED - SAME AS PREVIOUS>

  2) Chef::Resource::AwsRouteTable When the Chef server exists when the chef repo exists and with a VPC with an internet gateway aws_route_table 'test_route_table' with no parameters except VPC creates a route table
     Failure/Error: Unable to find matching line from backtrace
     ArgumentError:
       Cannot sign the request without a client name, check that :node_name is assigned
     # ./vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'
<REMOVED - SAME AS PREVIOUS>

  3) Chef::Resource::AwsRouteTable When the Chef server exists when the chef repo exists and with a VPC with an internet gateway aws_route_table 'test_route_table' with routes creates a route table
     Failure/Error: Unable to find matching line from backtrace
     ArgumentError:
       Cannot sign the request without a client name, check that :node_name is assigned
     # ./vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'
<REMOVED - SAME AS PREVIOUS>

  4) Chef::Resource::AwsRouteTable When the Chef server exists when the chef repo exists and with a VPC with an internet gateway ignores routes whose target matches ignore_route_targets
     Failure/Error: Unable to find matching line from backtrace
     ArgumentError:
       Cannot sign the request without a client name, check that :node_name is assigned
     # ./vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'
<REMOVED - SAME AS PREVIOUS>

  5) Chef::Resource::AwsSecurityGroup When the Chef server exists when the chef repo exists and in a VPC aws_security_group 'test_sg' with no attributes works
     Failure/Error: Unable to find matching line from backtrace
     ArgumentError:
       Cannot sign the request without a client name, check that :node_name is assigned
     # ./vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'
<REMOVED - SAME AS PREVIOUS>

  6) Chef::Resource::AwsSecurityGroup When the Chef server exists when the chef repo exists and in a VPC aws_security_group 'test_sg' with inbound and outbound rules works
     Failure/Error: Unable to find matching line from backtrace
     ArgumentError:
       Cannot sign the request without a client name, check that :node_name is assigned
     # ./vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'
<REMOVED - SAME AS PREVIOUS>

  7) Chef::Resource::AwsSecurityGroup When the Chef server exists when the chef repo exists and when narrowing from multiple VPCs raises an error if it finds multiple security groups
     Failure/Error: Unable to find matching line from backtrace
     ArgumentError:
       Cannot sign the request without a client name, check that :node_name is assigned
     # ./vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'
<REMOVED - SAME AS PREVIOUS>

  8) Chef::Resource::AwsSecurityGroup When the Chef server exists when the chef repo exists and when narrowing from multiple VPCs correctly returns the security group when vpc is specified
     Failure/Error: Unable to find matching line from backtrace
     ArgumentError:
       Cannot sign the request without a client name, check that :node_name is assigned
     # ./vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'
<REMOVED - SAME AS PREVIOUS>

  9) Chef::Resource::AwsSubnet When the Chef server exists when the chef repo exists and with a VPC with an internet gateway and route table aws_subnet 'test_subnet' with no parameters except VPC creates a route table
     Failure/Error: Unable to find matching line from backtrace
     ArgumentError:
       Cannot sign the request without a client name, check that :node_name is assigned
     # ./vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'
<REMOVED - SAME AS PREVIOUS>

  10) Chef::Resource::AwsSubnet When the Chef server exists when the chef repo exists and with a VPC with an internet gateway and route table aws_subnet 'test_subnet' with all parameters creates a route table
      Failure/Error: Unable to find matching line from backtrace
      ArgumentError:
        Cannot sign the request without a client name, check that :node_name is assigned
      # ./vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'
<REMOVED - SAME AS PREVIOUS>

  11) Chef::Resource::AwsVpc When the Chef server exists when the chef repo exists and When AWS has a DHCP options aws_vpc 'vpc' with no attributes fails to create a VPC (must specify cidr_block)
      Failure/Error: Unable to find matching line from backtrace
      ArgumentError:
        Cannot sign the request without a client name, check that :node_name is assigned
      # ./vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'
<REMOVED - SAME AS PREVIOUS>

  12) Chef::Resource::AwsVpc When the Chef server exists when the chef repo exists and When AWS has a DHCP options Creating an aws_vpc aws_vpc 'vpc' with cidr_block '<IP_ADDRESS>/24' creates a VPC
      Failure/Error: Unable to find matching line from backtrace
      ArgumentError:
        Cannot sign the request without a client name, check that :node_name is assigned
      # ./vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'
 <REMOVED - SAME AS PREVIOUS>

  13) Chef::Resource::AwsVpc When the Chef server exists when the chef repo exists and When AWS has a DHCP options Creating an aws_vpc aws_vpc 'vpc' with all attributes creates a VPC
      Failure/Error: Unable to find matching line from backtrace
      ArgumentError:
        Cannot sign the request without a client name, check that :node_name is assigned
      # ./vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'
<REMOVED - SAME AS PREVIOUS>

  14) Chef::Resource::AwsVpc When the Chef server exists when the chef repo exists and When AWS has a DHCP options and an existing VPC with values filled in and a route table inside that VPC aws_vpc can update the main_route_table to it
      Failure/Error: Unable to find matching line from backtrace
      ArgumentError:
        Cannot sign the request without a client name, check that :node_name is assigned
      # ./vendor/ruby/2.1.0/gems/chef-12.3.0/lib/chef/http/auth_credentials.rb:40:in `signature_headers'
<REMOVED - SAME AS PREVIOUS>

Finished in 2 minutes 26.9 seconds (files took 2.41 seconds to load)
34 examples, 14 failures

Failed examples:

rspec ./spec/integration/aws_cache_subnet_group_spec.rb:19 # Chef::Resource::AwsCacheSubnetGroup When the Chef server exists when the chef repo exists and with a VPC with an internet gateway and subnet aws_cache_subnet_group 'test-subnet-group' creates a cache subnet group
rspec ./spec/integration/aws_route_table_spec.rb:13 # Chef::Resource::AwsRouteTable When the Chef server exists when the chef repo exists and with a VPC with an internet gateway aws_route_table 'test_route_table' with no parameters except VPC creates a route table
rspec ./spec/integration/aws_route_table_spec.rb:25 # Chef::Resource::AwsRouteTable When the Chef server exists when the chef repo exists and with a VPC with an internet gateway aws_route_table 'test_route_table' with routes creates a route table
rspec ./spec/integration/aws_route_table_spec.rb:39 # Chef::Resource::AwsRouteTable When the Chef server exists when the chef repo exists and with a VPC with an internet gateway ignores routes whose target matches ignore_route_targets
rspec ./spec/integration/aws_security_group_spec.rb:66 # Chef::Resource::AwsSecurityGroup When the Chef server exists when the chef repo exists and in a VPC aws_security_group 'test_sg' with no attributes works
rspec ./spec/integration/aws_security_group_spec.rb:78 # Chef::Resource::AwsSecurityGroup When the Chef server exists when the chef repo exists and in a VPC aws_security_group 'test_sg' with inbound and outbound rules works
rspec ./spec/integration/aws_security_group_spec.rb:124 # Chef::Resource::AwsSecurityGroup When the Chef server exists when the chef repo exists and when narrowing from multiple VPCs raises an error if it finds multiple security groups
rspec ./spec/integration/aws_security_group_spec.rb:131 # Chef::Resource::AwsSecurityGroup When the Chef server exists when the chef repo exists and when narrowing from multiple VPCs correctly returns the security group when vpc is specified
rspec ./spec/integration/aws_subnet_spec.rb:26 # Chef::Resource::AwsSubnet When the Chef server exists when the chef repo exists and with a VPC with an internet gateway and route table aws_subnet 'test_subnet' with no parameters except VPC creates a route table
rspec ./spec/integration/aws_subnet_spec.rb:37 # Chef::Resource::AwsSubnet When the Chef server exists when the chef repo exists and with a VPC with an internet gateway and route table aws_subnet 'test_subnet' with all parameters creates a route table
rspec ./spec/integration/aws_vpc_spec.rb:101 # Chef::Resource::AwsVpc When the Chef server exists when the chef repo exists and When AWS has a DHCP options aws_vpc 'vpc' with no attributes fails to create a VPC (must specify cidr_block)
rspec ./spec/integration/aws_vpc_spec.rb:13 # Chef::Resource::AwsVpc When the Chef server exists when the chef repo exists and When AWS has a DHCP options Creating an aws_vpc aws_vpc 'vpc' with cidr_block '<IP_ADDRESS>/24' creates a VPC
rspec ./spec/integration/aws_vpc_spec.rb:26 # Chef::Resource::AwsVpc When the Chef server exists when the chef repo exists and When AWS has a DHCP options Creating an aws_vpc aws_vpc 'vpc' with all attributes creates a VPC
rspec ./spec/integration/aws_vpc_spec.rb:73 # Chef::Resource::AwsVpc When the Chef server exists when the chef repo exists and When AWS has a DHCP options and an existing VPC with values filled in and a route table inside that VPC aws_vpc can update the main_route_table to it

AH!  I just read my own blog. AWS does not give you inbound SSH access by default into its VPCs. As I had not used eu-west-1 before, I needed to do this. Now I am getting the 'client.pem' issue.
https://christinemdraper.wordpress.com/2015/01/31/deploying-a-multi-node-application-to-aws-using-chef-provisioning/

Note I do have an /etc/chef/client.pem on my workstation... that seems to be needed, or else I get the problem in #231

Thanks so @christinedraper for looking into this!
Running the commands you posted above w/ ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-darwin14] yields similar errors.
I got past the error using ChefDK (chefdk-0.6.0-1) via eval "$(chef shell-init bash)", however, chefdk-0.6.2-1 (the latest release) also produces the errors.

This totally sucks that our test suite depends on all this setup working - we should be creating a mock pem file (since chef-zero doesn't need a valid one) and making a mock node_name to supply to all the necessary config.

Hey @christinedraper - what happens if you create an /etc/chef/client.rb with a node_name 'foo' content?

Adding a client.rb with just a node_name doesn't change anything... still get similar failures with Cannot sign the request without a client name, check that :node_name is assigned

Grrr - this is frustrating because I cannot reproduce the error.  I don't have anything in .chef, ~/.chef or /etc/chef...

I'll be at office hours. Before then and now, I'll try to find time to experiment with a few things. For example, it might be because I do have stuff in ~/.chef.
Am I running the same commands as you:
bundle install --path vendor
export AWS_TEST_DRIVER=aws::eu-west-1
bundle exec rspec -b
And do you have any other env variables that might be responsible

I run AWS_TEST_DRIVER=aws::us-east-1 bundle exec rspec ./spec/integration/aws_subnet_spec.rb.  But I just tried with your commands and got the same output.  I have both a ~/.aws/config and ~/.aws/credentials but the error is coming from the Chef server, not AWS, so I don't think that has anything to do with it.

Ah! Now I've engaged my ruby brain and switched out of javascript-land...
I cleaned out Gemfile.lock and my  'vendor' directory and reran bundle install. Now on the current dev driver, I do not get the previous problem. All the tests except one succeed, and looks like it cleaned up nicely after itself.
fyi, this is the failure:
rspec ./spec/integration/aws_route_table_spec.rb:39 # Chef::Resource::AwsRouteTable When the Chef server exists when the chef repo exists and with a VPC with an internet gateway ignores routes whose target matches ignore_route_targets

So I think this issue can be closed.

@christinedraper I have seen that one fail locally too.  I'm going to close this and we can address that in another bug!


Check card against DL and VRT

Check card

[ ] matches DL
[ ] check VRT passes
[ ] check and update migration guides example

VRT fail caused by workflow icon size change.


isMounted is deprecated

Can't just remove this, it needs to be handled internally by the component.
i.e. set something on the instance in componentDidMount / unset it on componentWillUnmount

For sure,  PR was meant to be marked as WIP

I don't have time to do this,  closing and leaving https://github.com/JedWatson/react-tappable/issues/105 open


[SUPPORT] sparksql query perfermance degrade in hudi 0.14-rc

Tips before filing an issue

Have you gone through our FAQs?

Join the mailing list to engage in conversations and get faster support at<EMAIL_ADDRESS>

If you have triaged this as a bug, then file an issue directly.

Describe the problem you faced
A clear and concise description of the problem.
To Reproduce
Steps to reproduce the behavior:
details from ：https://issues.apache.org/jira/browse/HUDI-6941
@boneanxs @codope @danny0405 @stream2000   have a review plz
@codope https://github.com/apache/hudi/pull/9273 seems  cause it
Expected behavior
A clear and concise description of what you expected to happen.
Environment Description

Hudi version :

Spark version :

Hive version :

Hadoop version :

Storage (HDFS/S3/GCS..) :

Running on Docker? (yes/no) :

Additional context
Add any other context about the problem here.
Stacktrace
Add the stacktrace of the error.

looking into this

Eager listing all partition files in file index cause it. It seems not a good idea to get all files in initialization especially when the files are huge.

@xuzifu666 Thanks for highlighting the issue. This is indeed a regression. The code block https://github.com/apache/hudi/blob/e6be39661a0aaed4227f8bcbec54e0abaf97fb22/hudi-spark-datasource/hudi-spark-common/src/main/scala/org/apache/hudi/HoodieFileIndex.scala#L471-L474 is the main cause. It should be further special cased and not simply depend on number of partition columns. I am going to revert the eager listing first and then put in a proper fix, which should also take care of HUDI-6320. Additionally, we need some tests to assert spark DAGs for reads much like TestSparkDataSourceDAGExecution.

@xuzifu666 @wecharyu Thanks for highlighting the issue. This is indeed a regression. The code block
https://github.com/apache/hudi/blob/e6be39661a0aaed4227f8bcbec54e0abaf97fb22/hudi-spark-datasource/hudi-spark-common/src/main/scala/org/apache/hudi/HoodieFileIndex.scala#L471-L474
is the main cause. It should be further special cased and not simply depend on number of partition columns. I am going to revert the eager listing first and then put in a proper fix, which should also take care of HUDI-6320. Additionally, we need some tests to assert spark DAGs for reads much like TestSparkDataSourceDAGExecution.

ok，thx and I submit a quick fix https://github.com/apache/hudi/pull/9862，but can not confirm whether cause other risk@codope

Thanks @xuzifu666. I have fixed some tests and other issues in #9863


Progress HUD not covering full screen.

I am using version 2.0.3.

I am using the following code snippet in a helper file to show the progress HUD.
    var progressBar = JGProgressHUD(style: .light)
    progressBar?.detailTextLabel.text = "Loading.."
    progressBar?.textLabel.text = "Some message . "
    progressBar?.contentView.backgroundColor = .white
    progressBar?.backgroundColor = getColor(black50)
    progressBar?.show(in: self.view)

I am putting a translucent background behind the progress view.
As seen in the attached image, the Progress HUD isn't covering the full screen. I have tried changing the Edge Insets and also changing the frame rect. But still the full screen is not getting covered by the translucent background.
What is the solution for this ?

You must show the HUD inside a view that fully covers the screen to achieve your desired behavior.  The HUD, or its background, will only cover the area of its superview.


 If autosquash fails, it will leave the fixup commit.
close #220
close #503

Basically done, not sure how to interactive with Rebase dashboard though.

If this is all, it look good.

I am good for now. I guess rebase dashboard related issues should be addressed in another PR.

@randy3k, can you add an entry to the rebase docs?

Done (I was able to use this new feature to fixup this PR.)

Haha awesome.  This LGTM!  Merge away.

🎉


Update Blog “biryani”

Automatically generated by Netlify CMS

👷 Deploy Preview for ekhdmny processing.

Name
Link

🔨 Latest commit
7368fbbeebe40163e6db86adfdc65a6e74ce92e2

🔍 Latest deploy log
https://app.netlify.com/sites/ekhdmny/deploys/6383492254daea00098baa8a


🐞 [Bug]: Mismatch in farm location.

Is there an existing issue for this?

[X] I have searched the existing issues

which package/s did you face the problem with?
Dashboard
What happened?
The farm is located in Greece but on the dashboard shows in the United States.
Steps To Reproduce
No response
which network/s did you face the problem on?
Main
version
2.3.4
Twin ID/s
No response
Node ID/s
635
Farm ID/s
3617
Contract ID/s
No response
Relevant screenshots/screen records

Relevant log output
![image](https://github.com/threefoldtech/tfgrid-sdk-ts/assets/95933607/f20dc845-a8ec-4fe0-b15f-2cc4b8f658f6)

all of the nodes in this link are USA

The same ticket is already open here, so I will close this ticket.


Large drift, tuning, optimizing the kiss_icp poses ?

Hello,
First of all, thank you for providing such an easy to use tool.
My question is related to the odometry drift, i am running the python app using a folder of pcds. The kiss_icp odometry drift can be minimized for a sparse dataset using the comment at : https://github.com/PRBonn/kiss-icp/issues/128#issuecomment-1505258331. However i would like to know if there is a way to correct the trajectory or poses obtained from kiss_icp rather then running the pipeline of map_clousre_pipeline by default, since the drift is too large for my dataset without tuning parameters.
Thank you again, and waiting for your answer.

Hey @Efesendil, thanks for showing interest in our work.
If I understood your issue correctly, you refer to the removal of the double downsampling PRBonn/kiss-icp#128 (comment). Sadly, this can only be done by editing the KISS-ICP pipeline source code, and not via tha map_closures_pipeline. You can only change the KISSConfig parameters through the pipeline.py file here.


Add SSH option to log in some vps/dedicated servers

Add SSH option to log in some vps/dedicated servers

Environment
Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):

Any other software?

Steps to reproduce

Expected behavior

Actual behavior

You can easily add SSH profiles. See https://docs.microsoft.com/en-us/windows/terminal/tutorials/ssh

Yea I'm not sure what you want from us here. Just add whatever profiles you want?


PSR-16 doesn't mention InvalidArgumentException for invalid TTL

The current PSR-16 integrations tests expect an InvalidArgumentException to be thrown[1] when passing an invalid $ttl. I think that is wrong, or at least premature. The spec does not specify[2] what should happen in the case of invalid input and leaves that up to the library.
There is a PR[3] to make it official that an invalid TTL results in an InvalidArgumentException. However, it has not been merged in a month.
There is another PR[4] (to PSR-6, but I assume PSR-16 to follow suit should it pass) to throw a TypeError (or trigger_error). It's been around for longer, but could be brought back up with FIG 3 in place.
In short: I don't think this behavior for TTL should be enforced, since 1) it's undefined in the spec, and 2) there are competing ideas on how to eventually define it in spec.
1: https://github.com/php-cache/integration-tests/blob/master/src/SimpleCacheTest.php#L509
2: https://groups.google.com/forum/#!topic/php-fig/TQX0-DpKTKM
3: https://github.com/php-fig/fig-standards/pull/858
4: https://github.com/php-fig/fig-standards/pull/787

Closing as explained in https://github.com/php-cache/integration-tests/pull/77#issuecomment-718464198


v4.0.0

What does this PR do?

Update dependencies
Set v4.0.0

How should it be tested manually?
yarn test
# or
npm test

Pull Request Test Coverage Report for Build 52

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 38:
0.0%

Covered Lines:
52

Relevant Lines:
52

💛  - Coveralls


remote workloadmeta: ensure EOF actually triggers a re-sync

What does this PR do?
This PR fixes the handling of EOF by the remote workloadmeta. Currently, when Recv returns an EOF error we continue with the same stream which can cause some real issue for the client since the server is no longer available. This is for example happening when the core agent (the remote wm server in our case) is getting OOM-killed, and it's triggering huge CPU usage (and allocation) for the security agent when using the remote mode.
Basically we fall into a loop of:
- call Recv -> this allocates a new buffer for the message
- instantly get EOF
- continue -> start again

This PR fixes this issue by asking for a re-sync when EOF is reached.
This fix is not entirely new, it was already done like that before https://github.com/DataDog/datadog-agent/pull/17682/files#diff-a48cb39c4455a8d213283cd15194c52730ed1bce9e6413533ef597776d3234e3L175
Open question: should EOF errors be reported by telemetry and the log ?
Motivation
I have been investigating very high CPU usage of the security agent for some time (example profile). This issue is preventing us from using the remote WM more broadly.
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes
2 components use the remote workloadmeta:

non-core agents using it to sync their store with the one from the agent, especially the case of the security-agent. This needs to be QA-ed by ensuring the datadog.security_agent.runtime.containers_running metric is reporting correctly when the remote mode is enabled. The process agent can also make use of this in some configuration
the core agent uses this to sync process data with the process agent (in this case the core agent is the client and the process agent is the server)

/merge


Update minters.json

Include Poorly Drawn Chibi Gang Nft And Archtects Ban Address

Is this a duplicate of #2? (or technically, the other way around?)
Can I close this?


Allow selint-disable comment after declaration in require block

Fixes: 3f83758c1825c1e720867e18ab97ee18ef0eadf9 ("Separate grammar for real declarations and require content")

Something weird is going on with actions/checkout in the integration pipeline on this PR.  It was originally failing on an intermittent github error, but now on rerun, it's not fetching the pr ref.
I noticed that there is an actions/checkout v2 so I updated to that.  Try rebasing on it and see if that fixes the integration pipeline issue.


Missing License

If you want anyone to ever consider using this you need to add a license.

Thanks for the suggestion. I have added the MIT license.


NetAdapterSetCurrentLinkLayerAddress and NetAdapterSetPermanentLinkLayerAddress pages should link to NET_ADAPTER_LINK_LAYER_ADDRESS

The pages for NetAdapterSetCurrentLinkLayerAddress() and NetAdapterSetPermanentLinkLayerAddress() mention NET_ADAPTER_LINK_LAYER_ADDRESS in some places, but neither of those like to it.
They should probably link those references to https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/netadapter/ns-netadapter-net_adapter_link_layer_address.

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

ID: f1e37526-fac2-5df7-5010-0fe25357e1ef
Version Independent ID: 63f791ae-96b8-49b8-a910-a314adce87ef
Content: NetAdapterSetCurrentLinkLayerAddress function (netadapter.h) - Windows drivers
Content Source: wdk-ddi-src/content/netadapter/nf-netadapter-netadaptersetcurrentlinklayeraddress.md
Product: windows-hardware
Technology: wdk-api-reference
GitHub Login: @aviviano
Microsoft Alias: amvivian

Thanks for helping us improve the docs, @guyharris! We've added these links.


Add fixed length array to Binary conversion

As discovered in https://github.com/CosmWasm/cosmwasm/issues/476

Did you have to bump to 1.44 for this to run? Or just a random update while you were at it?

The implementation impl<const N: usize, T> From<[T; N]> for Vec<T> requires 1.44 (https://doc.rust-lang.org/src/alloc/vec.rs.html#2456-2468). This is used for the owned conversion to the inner vector in
                fn from(source: [u8; $N]) -> Self {
                    // Implementation available for $N <= 32.
                    // Requires https://caniuse.rs/features/vec_from_array, avaiable since Rust 1.44.0.
                    Self(source.into())
                }

I saw the CHANGELOG entry. It would be good to add this info to the README (1.44.1+)

Github does not update PR after updating the branch. Merged manually in https://github.com/CosmWasm/cosmwasm/commit/0c3938aa85efb876be879a689f636fd1189bfe12

Wow, github is being funny. Shows this as closed, but shows me a button to merge pull request.

Who'd have thought Microsoft would "move fast and break things"?


Execution of subquent node is hold until one output with no dependencies is executed

Hello,
We are trying to parallelize I/O for one of our pipelines.
We have a node that downloads a dataset and we store it in a file system and in memory (node 1). The output stored in memory is what we use in the rest of the pipeline (node 2). The problem is that it does not parallelize the saving to the file system (which is slow) with the execution of node two.
Pipeline:

According to the description of the proyect isn't supposed to save the output in the slow filesystem at the same time that runs the nodes that don't depend on that output?

Ok, nevermind, I have understood that what the package does it's what we do with another output for memory in the pipeline. So it will not have to load from csv if there is only an output to the filesystem for the data to be used later on.


add image load safety

it's kind of a weird idea because most people can just do a try else case on images, but why not set a flag to true for image load safety, basically what happens is if the asset does not render, instead of throwing an exception, why not paint an asset that says file not found or use https://publicdomainvectors.org/en/free-clipart/Vector-illustration-of-image-did-not-load-icon/22266.html
the reason why i am saying this is because, newbies don't know what that means when an exception is thrown, or they might not know how to fix it right away. and sometimes assets just don't load because the file is not perfectly formatted yet, this can be an issue for people with older laptop. think accessibility for those who are less fortunate to have a newer system.
oftentimes when an asset is not perfect it will throw an exception, that takes people with older systems more time because they have to stop the app, fix the code and then recompile, which xcode updated their compiler and it takes almost 2 minutes to compile if the user has an older system and has to fire back up the code due to the image throw exception, i think it is found in the asset_bundle.dart file.
i tried editing it but i broke the code and had to delete and redownload flutter in order to fix it. i'll try again one of these days and send in a push request. but something as simple as returning an flutter drawn asset by default on exception would make the code a lot more accessible to people who work or go to school full time and don't have the resources to get a new system and also who are new to the platform. think of it as the null safety for images.  just make a flag where someone can set to ignore the safety, if they want to code in their own exception. thanks

@trailerzone
does this fit your needs?
https://flutter.dev/docs/cookbook/images/fading-in-images

@trailerzone
does this fit your needs?
https://flutter.dev/docs/cookbook/images/fading-in-images

not exactly, this is more so for things like an svg loaded locally or a png/gif loaded locally, so if you want to load a local asset that throws an error, the system would display a placeholder image instead of throwing the error. so for for local files only, this widget looks like it was made for waiting on network images? unless it can load a placeholder if a local asset throws an error/can't load?

it's this area of image_provider.dart that throws the error when a local png cannot load.
@protected
Future<ui.Codec> _loadAsync(AssetBundleImageKey key, DecoderCallback decode) async {
ByteData? data;
// Hot reload/restart could change whether an asset bundle or key in a
// bundle are available, or if it is a network backed bundle.
try {
data = await key.bundle.load(key.name);
} on FlutterError { // this area, why can't the system return a placeholder asset instead start says this message rather than breaking the code? maybe there is an easier way but, it looks problematic for a ton of people.
PaintingBinding.instance!.imageCache!.evict(key);
rethrow;
}
// key.bundle.load has a non-nullable return type, but might be null when
// running with weak checking, so we need to null check it anyway (and
// ignore the warning that the null-handling logic is dead code).
if (data == null) { // ignore: dead_code
PaintingBinding.instance!.imageCache!.evict(key);
throw StateError('Unable to read data');
}
return await decode(data.buffer.asUint8List());
}
}

Image.asset has an error builder callback that can be defined. More information here: https://api.flutter.dev/flutter/widgets/ImageErrorWidgetBuilder.html

there is

Image.asset has an error builder callback that can be defined. More information here: https://api.flutter.dev/flutter/widgets/ImageErrorWidgetBuilder.html

yeah except i do not think that it works on AssetImage for when you are using it with boxdecoration.

Image.asset has an error builder callback that can be defined. More information here: https://api.flutter.dev/flutter/widgets/ImageErrorWidgetBuilder.html

yeah except i do not think that it works on AssetImage for when you are using it with boxdecoration.

@trailerzone
can you provide a minimal reproducible code sample to demonstrate that

Hi @trailerzone
Can you please provide your flutter doctor -v and a minimal complete reproducible code sample and flutter run --verbose logs running the minimal code sample?
Thank you

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Update codebase to use latest dependencies and idioms

This large set of commits was a fun side-project of mine for a while now. These commits are divided by minimum version of Rust necessary to make subsequent dependency updates work in order to make grokking them straightforward. Feel free to be picky about what you want to keep, but I've tried to be as minimal as I thought prudent while still netting nice gains for maintenance.
Each individual commit has had cargo test done locally and then had CI run against it. There should be only be concerns about where one wants to draw the line in terms of minimum Rust support versus how up-to-date one wants to be with "modern" Rust.
Thanks for making this great tool. I hope that this makes your life easier. :)

This issue has been open for more than a year, is the project dead?

@BourgondAries

This issue has been open for more than a year, is the project dead?

Yes, Daniel gave up a while ago. I thought I had a departure post stashed somewhere but apparently not.


Improve the prepare step documentation

Describe the prepare step purpose and usage instead of the old
bullet points which didn't say much. Include a couple of examples.
Adjust the default recommended packages installation order so that
it's possible to insert a prepare config between require/recommend
if needed.

Anyone willing to spend 5 minutes on a documentation improvement? The only code change is the default recommend package installation order changed to 75 to allow inserting preparation between require and recommend if needed.

Thanks!


Return to the Mods screen after watching Minecraft Credits

After using View Credits, you get Credits Screen that sets clients screen to null, which can be distracting and unpractical.
This is my mixin-free implementation to change this.

P.S. I created an unnecessary commit which is the gradle.properties one, I didn't mention to propose it in pull request, but that's how git works. I could work that out, but I think i'ts not a problem to skip it.

Added


RFC support for HM-Sec-SD-2-Team

I made the necessary changes to add support for HM-Sec-SD-2-Team in my fork: cd15a958ff689ecccd9482142426017bed1ccd0f
I now see the team entity in hass and also get the smoke detector state changes (which I did not get before as the changes are only reported by the virtual team device if the smoke detectors are configured as team). However, I would like to see somehow which of the detectors triggered this event. In the logs I see:
Aug 24 20:04:57 myhost hass[282]: 2021-08-24 20:04:57 INFO (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: address=*QEQ1953019:1, interface_id=homeassistant-wireless, key=STATE, value=False
Aug 24 20:04:57 myhost hass[282]: 2021-08-24 20:04:57 INFO (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: address=*QEQ1953019:1, interface_id=homeassistant-wireless, key=SENDERADDRESS, value=QEQ1951543:1
Aug 24 20:04:57 myhost hass[282]: 2021-08-24 20:04:57 INFO (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: address=*QEQ1953019:1, interface_id=homeassistant-wireless, key=SENDERID, value=3
But I can't see the senderaddress or senderid in hass. Therefore I added:
self.ATTRIBUTENODE.update({"SENDERADDRESS": [1],
                                   "SENDERID": [1]})

to the SmokeV2Team class but I still do not see them. I am not really familiar with the code and was just lucky that the necessary changes were easy so far. So I might made an obvious mistake here. Do you know how I get the senderid (or both) in an event or as attribute in hass so I can react on it in an automation?
I also had to add the SmokeV2Team id to the homeassistant core files. When I create a pull request here, should I create another in the homeassistant repo for those changes as well?
Thank you!

I don't see any obvious problems. In general I would replace the SensorHm at the top of the class definition with HMSensor. That way you don't have to remove the LOWBAT and RSSI_-Attributes.
Apart from that it's actually looking good so far.
No, you don't have to create a PR at Home Assistant. The new class only gets introduced with the new pyhomematic version, so I will include that when the new version is published and I open the PR in HA to include it.

Ok, got it now. I also need a corresponding entry in the HM_ATTRIBUTE_SUPPORT dictionary before it will be visible as attribute. Will test the automation tomorrow, now it's to late to trigger the alarms. ;) Thank you!


[5.1.45] Flash message with redirect() doesn't work, but works with \Redirect

Laravel Version: 5.1.45
PHP Version: 7.0
Database Driver & Version: MySQL
Session Driver: File

Description:
The issue was found and discovered on www.learnkarts[dot]com and is using secure and encrypted cookies.
We are using redirect()->back()->with('success'', 'Thanks for submission'); syntax in order to flash a success message in whole application. However, on specific page the flash didn't come. The flashdata is being set on post method, but when get is executed, the flash message doesn't get persisted in the session.
The same code happen to work on locally and on staging server where SSL isn't installed.
Steps To Reproduce:
The exact step not able to track it down, however changing
redirect()->back()->with('success', 'Thanks!') to \Redirect::back()->with('success', 'Thanks!');
Please let me know if it is laravel issue or anything else.
It has been resolved right now as mentioned above but something to seriously think on as why it had came on first place.

5.1 is no longer supported. Kindly submit a new issue if this occurs in 5.5

So, not even session driver or anything is being supported?
Any specific and solid guide to upgrade to Laravel 5.1 to 5.5?

@dakshhmehta You can use the upgrade guide in the documentation


Fix broken URL to SYNTHESYS home page

Unexisting home.html page in www.synthesys.info

Thanks @WUlate


fix: remove logging

Removes the route / api logging
[GIN] 2023/05/16 - 18:44:05 | 200 |      69.131µs |      <IP_ADDRESS> | GET      "/"
[GIN] 2023/05/16 - 18:44:05 | 200 |      82.867µs |      <IP_ADDRESS> | GET      "/"
[GIN] 2023/05/16 - 18:44:15 | 200 |      72.758µs |      <IP_ADDRESS> | GET      "/"
[GIN] 2023/05/16 - 18:44:15 | 200 |      21.961µs |      <IP_ADDRESS> | GET      "/"
[GIN] 2023/05/16 - 18:44:25 | 200 |      55.215µs |      <IP_ADDRESS> | GET      "/"
[GIN] 2023/05/16 - 18:44:25 | 200 |      14.449µs |      <IP_ADDRESS> | GET      "/"
[GIN] 2023/05/16 - 18:44:35 | 200 |      85.641µs |      <IP_ADDRESS> | GET      "/"
[GIN] 2023/05/16 - 18:44:35 | 200 |      60.083µs |      <IP_ADDRESS> | GET      "/"
[GIN] 2023/05/16 - 18:44:45 | 200 |      73.518µs |      <IP_ADDRESS> | GET      "/"
[GIN] 2023/05/16 - 18:44:45 | 200 |      24.927µs |      <IP_ADDRESS> | GET      "/"
[GIN] 2023/05/16 - 18:44:55 | 200 |      56.337µs |      <IP_ADDRESS> | GET      "/"

hmmm, i like the logging :)

General yes but this just spamming the log, we should log error cases if we need to.


Upgrade Checkstyle to latest version (6.15)

The one rule that I removed got removed in Checkstyle. See

Great!
Would be nice to remove these versions to dependencies.gradle at some point


mongodb pod hangs during bootstrap initialization

i'm running KubeDB 0.11.0 and using mongodb 3.6-v2. i have recently started seeing the second pod (mongodb-1) hang in the bootstrap init container. it looks exactly like this bug reported against the replicaset helm chart: 7417 (and fixed via this pull). the behavior and log messages are identical.
i upgraded to KubeDB 0.12.0 and the mongodb 3.6-v3 image when i saw the scripting on initialization has been changed from 3.6-v2. however, i still see the same behavior. the information in the bootstrap container log for mongodb-1 is more informative. it now shows:
{
    "ok" : 0,
    "errmsg" : "Quorum check failed because not enough voting nodes responded; required 2 but only the following 1 voting nodes responded: mongodb-0.mongodb-gvr.jtm.svc.cluster.local:27017; the following nodes did not respond affirmatively: mongodb-1.mongodb-gvr.jtm.svc.cluster.local:27017 failed with HostUnreachable",
    "code" : 74,
    "codeName" : "NodeNotFound",
    "operationTime" : Timestamp(1564528937, 63),
    "$clusterTime" : {
        "clusterTime" : Timestamp(1564528937, 63),
        "signature" : {
            "hash" : BinData(0,"G9Or0iuJqUQXIg6AJ/3rats6RC8="),
            "keyId" : NumberLong("6719600437672017921")
        }
    }
}
[2019-07-30T23:22:20,325149583+00:00] [replicaset.sh] Waiting for replica to reach SECONDARY state...
exception: connect failed
exception: connect failed
exception: connect failed
...

the mongodb-0 mongodb container log has the same line as before:
2019-07-30T22:47:56.182+0000 E REPL     [conn26] replSetReconfig failed; NodeNotFound: Quorum check failed because not enough voting nodes responded; required 2 but only the following 1 voting nodes responded: mongodb-0.mongodb-gvr.jtm.svc.cluster.local:27017; the following nodes did not respond affirmatively: mongodb-1.mongodb-gvr.jtm.svc.cluster.local:27017 failed with HostUnreachable

deleting the mongdb-1 pod is an easy workaround. when the pod restarts it gets through bootstrap. the rest of the pods are fine.
i'm unsure of what caused the issue to start happening in my environment, but it now happens reliably.

Hi @mer2github,
I saw the solution you provided. So, Does the problem fixes after restart is done? Or, it appears again at some point?

Seems like it is something related to firewall for port 27017.
@mer2github , can you share your configuration/crd you used to deploy this mongodb, so that I can recreate the issue? Also, how you provision this cluster? what is the kubernetes cluster version?


Pact improvements

What does this pull request do?

Implements missing @State callbacks
Implements missing IDs.

Aims to remove all state callback failed errors in tests and replace them with assertion failures.
Then we can have a conversation on what the state is expecting and how we word/implement those.
Before

After

What is the intent behind these changes?
Slowly moving towards green Pacts.

📝 Rebased


How can I configure localhost to call HTTPS api-server with  AWS Cognito ?

Describe the bug
Cognito How to
To Reproduce
Steps to reproduce the behavior:

Go to '/proxy.conf.json'

Change the Json to  ':
"/api/*": {
"target": "https://senzing-....-amazonaws.com/api/",
"secure": true,
"logLevel": "debug",
"pathRewrite": {
"^/api": ""
}
},'

npm start

See an error

Expected behavior
should prompt the AWS Cognito login and the API server call should work.
Screenshots
[HPM] Rewriting path from "/api/attribute-types" to "/attribute-types"
[1] [HPM] GET /api/attribute-types ~> https://senzing-....amazonaws.com/api/
[1] [HPM] Error occurred while trying to proxy request /attribute-types from localhost:4200 to https://senzing-....amazonaws.com/api/ (UNABLE_TO_VERIFY_LEAF_SIGNATURE) (https://nodejs.org/api/errors.html#errors_common_system_errors)
Desktop (please complete the following information):

OS: Mac OS
Browser chrome
Version 2.2.1

Additional context
I would like to know how to configure my locally running HTTP entity-search-web-app to connect to HTTPS  api-server. Also, get an authentication log-in screen of Cognito.

Hi @taenaive!
The only work we've done with AWS Cognito is in the cloudformation.yaml at https://github.com/Senzing/aws-cloudformation-ecs-poc-simple.
We aren't experts in integrating with various platforms (Kubernetes, Openshift, Swarm, AWS) with various products (Npm, Django, jetty, etc).   However, to try to help you out, 2 things:

@arawinters Can you provide any help with this request?
Email<EMAIL_ADDRESS>for your support request (We work on features and bugs in GitHub issues, but have a different ticketing system for support)

-- Michael Dockter

@taenaive currently there is no support in the webapp to screen api calls for 401/403 responses and redirect on event. The feature will have to be added to the codebase. Typically we have the webapp connect to the api server over a private subnet/addr instead of hitting a publicly accessible path. I think it's a reasonable request to add 401/403 header intercepts/redirects functionality though. I'm gonna surface your request at our standup and see about adding it. (alternatively you could clone/fork the webapp and add global http intercepts yourself)
For connecting to an HTTPS api server, I think you've got the right idea but I'll need to spin up the same configuration to test against to see what's going on there. I'm thinking there's some cookie/session/header type thing going on(guessing from the UNABLE_TO_VERIFY_LEAF_SIGNATURE part). you might try setting secure: false on that redirect(that flag tells webpack dev srvr to validate ssl certs) just to see.


Hi Team,
I would like to http://cinemalek.com/ into youtubedl
I have latest version installed on my PC
youtube-dl==2016.12.20
got below error:
DownloadError: ERROR: Unsupported URL: http://cinemalek.com/movies/2016/12/17/فيلم-rogue-one-a-star-wars-story-2016-مترجم-اون-لاين/
Thank you in advance
AGR
Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2016.12.22. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[ ] I've verified and I assure that I'm running youtube-dl 2016.12.22

Before submitting an issue make sure you have:

[ ] At least skimmed through README and most notably FAQ and BUGS sections
[ ] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[x] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add -v flag to your command line you run youtube-dl with, copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
$ youtube-dl -v <your command line>
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'http://www.youtube.com/watch?v=BaW_jenozKcj']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2016.12.22
[debug] Python version 2.7.11 - Windows-2003Server-5.2.3790-SP2
[debug] exe versions: ffmpeg N-75573-g1d0487f, ffprobe N-75573-g1d0487f, rtmpdump 2.4
[debug] Proxy map: {}
...
<end of log>

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: http://cinemalek.com/movies/2016/12/17/فيلم-rogue-one-a-star-wars-story-2016-مترجم-اون-لاين/

Description of your issue, suggested solution and other information
Explanation of your issue in arbitrary form goes here. Please make sure the description is worded well enough to be understood. Provide as much context and examples as possible.
If work on your issue requires account credentials please provide them or explain how one can obtain them.

Rogue One: A Star Wars Story is a copyrighted product: http://www.imdb.com/title/tt3748528/. youtube-dl on't support copyright infringing websites.

Hi Sir,
that was example link i have sent actually i want to extract video from below link and this is exclusive to us (OSN) i am implementing a crawler to extract out exclusive video from this site
http://cinemalek.com/series/2016/12/22/مسلسل-هوى-الروح-الموسم-الثانى-الحلقة-23/

I see no videos in the new URL, either. Crawlers are beyond the scope of youtube-dl. Just go ahead and implement crawlers.


Add a Addresses (including units) layer.

Set excludeUnits=false and locationDescriptor=parcelPoint

This is trivial but we will need a better way to display all of the units using a spiderfying/clustering approach.

This needs to be on hold too.


🌐 Language request: Hungarian

🌐 Language name (native)
Hungarian
🌐 Language code
hu-HU

Added. Thanks for your contribution :)


Question: Is hot reload supported?

It would be awesome if hot reloading was supported in the Hapi server. Do you have any plans to support that?

I've never thought about that before, but it makes sense because of serverless-offline support it as well. I'll prioritize it.


Separate Input and Output Embeddings

Looking at the megatron and openAI ckpt conversion, the input and final layers embeddings are shared and it seems that FasterTransformer does not support final layer output_projection (as in GPT3, Gopher etc). But the change log says that it supports GPT3.
wget --content-disposition https://api.ngc.nvidia.com/v2/models/nvidia/megatron_lm_345m/versions/v0.0/zip -O megatron_lm_345m_v0.0.zip
mkdir -p models/megatron-models/345m
unzip megatron_lm_345m_v0.0.zip -d models/megatron-models/345m
git clone https://github.com/NVIDIA/Megatron-LM.git
python ../sample/pytorch/utils/megatron_ckpt_convert.py -head_num 16 -i ./models/megatron-models/345m/release/ -o ./models/megatron-models/c-model/345m/ -t_g 1 -i_g 1

When I checked the directory of the weights, there are transformer layer weights, layer norm weights and model.wpe.bin and model.wte.bin, I was also expecting a model.final_projection.bin or model.output_emeddding.bin

Since the embedding is shared, FT uses model.wte.bin directly. Please refer https://github.com/NVIDIA/FasterTransformer/blob/dev/v5.0_beta/src/fastertransformer/models/gpt/GptWeight.cc#L133.

I see, thanks for pointint that out. Usually the final logit layer projection also has a bias variable to it. Are there any easy tips or steps to add this to final layer?

You need to modify the op or backend, adding the bias into "weight class", and put the bias as an input of dynamic_decode layer.
You can compare the ParallelGpt.cc source code and Decoding.cc. The latter one contains the bias.

Hey, I couldn't fint ParallelGPT.cc is this on dev/v_5.0 branch and do you mean GPTJ?

That is the model of GPT. Please find more models in src/fastertransformer/models.

Correct me if I am wrong
https://github.com/NVIDIA/FasterTransformer/blob/dev/v5.0_beta/src/fastertransformer/models/decoding/Decoding.cc#L459
But there is no bias add after the final layer projection. There is a Cuda Kernel, InvokeBiasAdd, but I dont see it being used here

After adding the post decoder embedding bias weight to GPTWeight.cc, I added the invokeaddbias after the final projection layer.
invokeAddBias(logits_buf_,
gpt_weights->post_decoder_embedding.bias,
 batch_size * beam_width_,
vocab_size_padded_,
stream_);

But I get an error like this, its a bit hard to interpret what it is.
[FT][ERROR] CUDA runtime error: an illegal memory access was encountered /workspace/FasterTransformer/src/fastertransformer/utils/memory_utils.cu:82

Please refer https://github.com/NVIDIA/FasterTransformer/blob/dev/v5.0_beta/src/fastertransformer/models/decoding/Decoding.cc#L380 and https://github.com/NVIDIA/FasterTransformer/blob/dev/v5.0_beta/src/fastertransformer/models/decoding/Decoding.cc#L477.

@byshiue Thanks for the quick response, that helps!

Can you provide the environment, reproduce step for the problems you encounter?

Hi, I fixed this issue! on dev_5.0 branch the temperature penalty kernel does not work when bias is passed in fp16. Instead I use invokeAddBias and pass a null pointer to temeprature penalty kernel.


 The same behavior reproduces both with CommandBehavior.Default and CommandBehavior.SequentialAccess, although I suspect there may be some interaction with the command behavior under the hood. Memory-wise, the expectation would be for SequentialAccess to use much less memory memory compared to the default command behavior - regardless of sync/async.
The tests were on run with .NET Core 3.0 on Ubuntu 19.04 against SQL Server running on localhost.
Related links:

https://stackoverflow.com/a/28619983/640325, with interesting profiling and benchmarking on .NET Framework (from 2015) showing a very related but slightly different issue (only async + CommandBehavior.Default trigger the x10 slowdown)
https://github.com/aspnet/EntityFrameworkCore/issues/18221, discussing this at the EF Core level.

Benchmark code:
[MemoryDiagnoser]
public class Benchmarks
{
    const string ConnectionString = "...";

    [Params(CommandBehavior.Default, CommandBehavior.SequentialAccess)]
    public CommandBehavior Behavior { get; set; }

    [GlobalSetup]
    public void Setup()
    {
        using var conn = new SqlConnection(ConnectionString);
        conn.Open();

        using (var cmd = new SqlCommand("IF NOT EXISTS (SELECT * FROM sysobjects WHERE name='TextTable' AND xtype='U') CREATE TABLE [TextTable] ([Text] VARCHAR(MAX))", conn))
            cmd.ExecuteNonQuery();

        using (var cmd = new SqlCommand("INSERT INTO [TextTable] ([Text]) VALUES (@p)", conn))
        {
            cmd.Parameters.AddWithValue("p", new string('x', 1024 * 1024 * 5));
            cmd.ExecuteNonQuery();
        }
    }

    [Benchmark]
    public async ValueTask<int> Async()
    {
        using var conn = new SqlConnection(ConnectionString);
        using var cmd = new SqlCommand("SELECT [Text] FROM [TextTable]", conn);
        await conn.OpenAsync();

        await using var reader = await cmd.ExecuteReaderAsync(Behavior);
        await reader.ReadAsync();
        return (await reader.GetFieldValueAsync<string>(0)).Length;
    }

    [Benchmark]
    public async ValueTask<int> Sync()
    {
        using var conn = new SqlConnection(ConnectionString);
        using var cmd = new SqlCommand("SELECT [Text] FROM [TextTable]", conn);
        conn.Open();

        using var reader = cmd.ExecuteReader(Behavior);
        reader.Read();
        return reader.GetFieldValue<string>(0).Length;
    }
}

Results:

BenchmarkDotNet=v0.11.5, OS=ubuntu 19.04
Intel Core i7-6700HQ CPU 2.60GHz (Skylake), 1 CPU, 8 logical and 4 physical cores
.NET Core SDK=3.0.100
  [Host]     : .NET Core 3.0.0 (CoreCLR 4.700.19.46205, CoreFX 4.700.19.46214), 64bit RyuJIT
  DefaultJob : .NET Core 3.0.0 (CoreCLR 4.700.19.46205, CoreFX 4.700.19.46214), 64bit RyuJIT

Method
Behavior
Mean
Error
StdDev
Median
Gen 0
Gen 1
Gen 2
Allocated

Async
Default
839.58 ms
43.2838 ms
127.6233 ms
930.22 ms
98000.0000
97000.0000
96000.0000
11.31 KB

Sync
Default
61.07 ms
1.0988 ms
1.0278 ms
60.80 ms
333.3333
222.2222
222.2222
10600.7 KB

Async
SequentialAccess
813.80 ms
44.3059 ms
130.6370 ms
767.23 ms
127000.0000
126000.0000
125000.0000
11.31 KB

Sync
SequentialAccess
69.54 ms
0.6815 ms
0.6375 ms
69.45 ms
375.0000
250.0000
250.0000
10672.5 KB

If the payload of the column crosses multiple packets the data has to be buffered until the end of the data is found. It's going to cause repeated re-allocations. In the case where the full length of the data isn't known it'll keep reallocating and copying into the new buffer. Bizarrely the best way to read it may to be using sequential access mode with a stream because it may only keep the current packet.
I'll have a tinker with it but if I'm right about how it works it would be a substantial change to alter the behaviour if it's possible at all.

If the payload of the column crosses multiple packets the data has to be buffered until the end of the data is found

That makes sense for non-sequential, but isn't the whole point of sequential access to stream large values? In other words, it's expected for non-sequential access to be slow (no complaints), but not for SequentialAccess. Note that this is a regression from this benchmarked behavior of the .NET Framework driver (note that I didn't confirm/rerun this), where sequential access is fast.
In addition, this should all have nothing to do with sync vs. async... I'm guessing that under the hood there's a completely different implementation for these two paths, and the async one has the issue we're seeing.

That makes sense for non-sequential, but isn't the whole point of sequential access to stream large values? In other words,

I can't speak about intent. I can tell you how the code behaves when that option is set though. The most relevant behaviour is that it specifically maintains only the currently read column SqlBuffer clearing out previous ones are reads are done, so you can't step back. That does align with the purpose of reading large values. I don't remember the de-packetization chunk handling code being particularly specialized.
I'm setting up for some benching and I'll see what I can find and if there's any room for improvement.

Well there's definitely a problem with how async reading of PLP data is done. It's not a simple one though, it's deeply rooted in how async works. I'll explain what I've found so far because it's as good a place as any to put the information for later reference.
A standard column value is of fixed length, easy to deal with. Non fixed width data has to be prefixed with it's length and then possibly reconstructed from multiple chunks. There's also an unknown length capacity where the user just has to keep requesting data until they reach and end of data packet. We're dealing with the middle option. This data spans multiple packets and is formatted as partially length prefixed data with a known length.
When reading this in sync mode it's pretty straight forward you just keep getting packets and pulling the contents of them out until the current offset in the byte buffer until you reach the end. Then you call the text encoding that corresponds to the encoding to convert your bytes into a string. Almost all of the memory overhead on sync is this string conversion. The only interruptions that are possible are internally generated.
In async mode things get complicated. Because any async method has to be interruptible by cancellation tokens and external events you have to handle state storage until a resolution to the read has been reached. This mechanism is snapshots. All async operations create a snapshot of the current reader state as their first action. Data is then requested and when received it is appended to the snapshot packet list and the snapshot is replayed to see if it can reach a resolution.
When you start reading the data from the first packet in the snapshot the data is identified as being part of a larger array of known length. An array is allocated for the full length and and attempt is made to read all the data, this fails because we don't have all the data (most of the time). Once it fails the current packet is consumable but not consumed so we can't discard it and it's left in the snapshot and we wait for more data.
Hopefully you've just seen the problem. For every packet the arrives all packets in the unresolved chain are re-processed in the snapshot replay and that reprocessing allocates an array large enough for all the output every time. so divide the size of the data 5Mib by roughly 8K chunks for default packet size and you'll have that number -1 dropped 5Mib arrays. The profile traces are quite impressive.
I've already got one PR in progress that optimizes the mechanics of snapshots. It won't help here. This is a logical problem. What I'd like to understand is why it was chosen to implement a full replay each time a packet arrives rather than trying to keep some additional state in the snapshot, as I see it there is no branch capability in the replay the only possible results are {Success, Failure, Continue} and if that's the case and backtracking can't happen it would be possible to augment snapshots with continuation state To know this you'll need to find someone who was around at the time or implemented this functionality because they'll know what the limiting factor was here, there could well be a hidden requirement I can't divine from the code,.

Thanks for the detailed info @Wraith2, it's indeed quite interesting and raises some questions.
Two immediate comments that I have:

As I wrote above, the Core version seems to be a regression compared to the Framework version - at least a some point, according to this SO, async sequential was apparently fast. It may be a good idea to run the benchmark above on .NET Framework to confirm, and then to see what's being done differently in the Framework version.
At least for byte arrays (blobs), things really should be quite simple. Assume values are length-prefixed (which seems to be the case according to your description), a byte array of the suitable size should simply be allocated and filled gradually with no extra memory overhead or needless copying. I understand the current architecture is very different, am just stating the obvious in how things should work.
Strings, on the other hand, are considerably more complicated as decoding has to take place. In Npgsql, if the string is really large, an extra byte array is allocated for the (byte) length of the string being read. Like with byte arrays, it's simply filled gradually, and decoded once at the end. This is probably not ideal (at minimum the temporary byte array should be pooled), but I doubt that this API could function much better for long streams (where GetTextReader is more suited). Here's the source code.
Am I understanding you correctly that reader state is manually snapshotted/managed for async operations? That would seem to indicate that the compiler async/await feature isn't used in SqlClient? Because the whole point of that feature is to "snapshot" the local variables in the async function and restore them later when the callback completes... Am just curious.

There's a pretty simple way to change the behaviour.
Before, restating for comparison so the number are from the same machine:

Method
Behavior
Mean
Error
StdDev
Gen 0
Gen 1
Gen 2
Allocated

Async
Default
448.84 ms
8.9453 ms
8.7855 ms
309000.0000
309000.0000
309000.0000
3.98 KB

Sync
Default
17.46 ms
0.1025 ms
0.0959 ms
406.2500
406.2500
406.2500
10244.82 KB

Async
SequentialAccess
458.23 ms
9.0577 ms
10.4309 ms
310000.0000
310000.0000
310000.0000
3.98 KB

Sync
SequentialAccess
17.38 ms
0.0638 ms
0.0596 ms
406.2500
406.2500
406.2500
10244.82 KB

After:

Method
Behavior
Mean
Error
StdDev
Gen 0
Gen 1
Gen 2
Allocated

Async
Default
130.98 ms
1.2547 ms
1.1737 ms
750.0000
500.0000
250.0000
3.95 KB

Sync
Default
17.38 ms
0.1107 ms
0.1036 ms
406.2500
406.2500
406.2500
10244.82 KB

Async
SequentialAccess
131.20 ms
0.7910 ms
0.7399 ms
750.0000
500.0000
250.0000
3.95 KB

Sync
SequentialAccess
17.35 ms
0.0806 ms
0.0754 ms
406.2500
406.2500
406.2500
10244.82 KB

It's not a very nice solution because it breaks encapsulation by making the plp data read aware of the snapshot and using it to store the target buffer between attempts to complete the execution. 3x faster, 400 times less GC. It's still almost 10x slower than the sync version but there's no way to fix that.
At the moment it performs a complete attempt to fill the buffer on every packet received and stores all packets received in a queue until the command succeeds or is cancelled.  The good solution is to change the entire way that async behaves and to make it store continuation progress in the intermediate buffer before returning it. This would decrease memory usage by removing the packet queue and increase speed by removing wasted cpu in continual replays. It's a major task that needs agreement and planning officially.
Perf will also be improved by https://github.com/dotnet/SqlClient/pull/198

Ack: PRs for Perf improvement are on hold for review for a while, till we get driver stabilized for breaking issues.

@Wraith2 can you share your project that you used to benchmark this issue?
I had a chat with @roji  and we are seeing worse benchmarks than were originally reported.
| Method |         Behavior |       Mean |    Error |    StdDev |     Median |       Gen 0 |       Gen 1 |       Gen 2 |  Allocated |
|------- |----------------- |-----------:|---------:|----------:|-----------:|------------:|------------:|------------:|-----------:|
|  Async |          Default |   961.5 ms | 35.20 ms | 103.80 ms | 1,007.5 ms |<PHONE_NUMBER> |<PHONE_NUMBER> |<PHONE_NUMBER> | 3661.01 MB |
|   Sync |          Default |   893.9 ms |  3.09 ms |   2.89 ms |   893.8 ms |           - |           - |           - |      15 MB |
|  Async | SequentialAccess | 1,888.8 ms | 42.94 ms | 126.60 ms | 1,929.5 ms |<PHONE_NUMBER> |<PHONE_NUMBER> |<PHONE_NUMBER> | 3525.79 MB |
|   Sync | SequentialAccess | 1,878.2 ms | 37.43 ms |  71.21 ms | 1,865.5 ms |           - |           - |           - |      15 MB |

We are wondering how the original results were obtained? @Roji is going to backtrack to the version of SqlClient that he may have run the original benchmarks on.
@Wraith2 in the meanwhile, can you provide your repro project. In case this is a regression in the version of SqlClient that we have been testing with, we need to remove the regression first.
The repos we have used are https://github.com/roji/SqlClientAsyncBenchmark
and
https://github.com/saurabh500/sqlclientrepros/tree/master/asyncperf

This was run on Windows as well as Linux. The benchmarks show 3.6 Gigs allocation for async :(

It isn't the version of SqlClient - it seems to be a difference between BenchmarkDotNet 11.5 and the recently-released 12.0. I'll investigate a bit more deeply to understand which one is reporting correct results.

Here we go, from the release notes for BDN 0.12.0:

Improved MemoryDiagnoser
Now MemoryDiagnoser includes memory allocated by all threads that were live during benchmark execution: a new GC API was exposed in .NET Core 3.0 preview6+. It allows to get the number of allocated bytes for all threads. #1155, #1153, #723

I'll reach out to the BDN folks, but I'd tend to trust the new results by default unless we find out otherwise...

I noted in my PR https://github.com/dotnet/SqlClient/pull/285 that BDN wasn't showing the correct memory figures and used dotMemory results to show the difference made by my changes. The new numbers you give look much more reasonable.

Makes sense now, thanks @Wraith2!

@Wraith2 Sorry for posting on an old issue but the rabbit hole led here. The last benchmark you mentioned here states that async runs ~10x slower than sync. Is this still the case? Has this been addressed in another issue in this repo or if not, is any work planned?

Yes, this is still the case. It can't be addressed without deep changes to the library. At the moment i'm working on consolidating the netcore and netfx codebases so that we don't have to work on two different libraries at once which will hopefully free up development time overall.
As for plans. I'm an external contributor and know only what is posted on this repo publicly. I plan to work on async but it's going to be a slow project once I get started and I won't be starting anytime soon. What the owning team intend I have no idea. Stability and new features seem to be the current goals.

Understood. Thanks for your response and contributions to such a critical library.

I still see the same problem on 3.1.1, I cant understand - the issue is closed but when was it fixed?

This individual issue was sped up with a cache. The larger issue is still open under https://github.com/dotnet/SqlClient/issues/593

This is still a major issue.
I have been troubleshooting spikes in CPU and slow SQL statements only to come to this thread.
GetClaimsAsync in Microsoft.AspNetCore.Identity calls SQL that has a table of nvarchar(max) for claims and values.
Changing the table to nvarchar(255)  seem to resolve the issue.
This issue is having a knock on affect to other libraries :(


Add type conversion for mailing lists

This PR contains the following changes:

data type transformation from a pandas.DataFrame to List[mailbox.mboxMessage]

Codecov Report

Merging #571 (eb420c7) into main (3e73dc5) will decrease coverage by 0.30%.
The diff coverage is 11.76%.

@@            Coverage Diff             @@
##             main     #571      +/-   ##
==========================================
- Coverage   72.75%   72.44%   -0.31%
==========================================
  Files          27       27
  Lines        3344     3361      +17
==========================================
+ Hits         2433     2435       +2
- Misses        911      926      +15

Flag
Coverage Δ

unittests
72.44% <11.76%> (-0.31%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

bigbang/bigbang_io.py
72.78% <11.76%> (-7.99%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Refactored metadata.rs

Removed redundant if lets
Minimized code duplication
Split off get fetching of the package table into a separate function
Overall style and formatting changes

Ah, turns out using &[Value] doesn't work because it's a closure fed into the function, and therefore its signature has to perfectly match


Mesher not working

I tried to run the example code given  for the images. But the Mesher  doesnot produce any meshes.

please tell me how you have executed this code i am getting the same error any solution

i am from iit bomabay


Updating tcnative version to match grpc version

To finish off https://github.com/GoogleCloudPlatform/google-cloud-java/issues/1691 .

LGTM once tests pass

Coverage increased (+0.004%) to 80.959% when pulling 837f46b81372692b677679c820e22629d010a4fd on garrettjonesgoogle:alt into 8c9636b15b2b66495cda221d2e122710c8447b13 on GoogleCloudPlatform:master.


Enhance onboarding test - add page context

Looks neater and I prefer the context's approach, but it won't solve the flaky problem as the app fails at the invitation reception stage which is endlessly loading every other time when I use the app myself

as the app fails at the invitation reception stage which is endlessly loading every other time when I use the app myself

That's because the app shows an alert which stops the main thread blocking the sync messages required to upload the invitation.
Changing the alert with a toast should fix the issue.

as the app fails at the invitation reception stage which is endlessly loading every other time when I use the app myself

That's because the app shows an alert which stops the main thread blocking the sync messages required to upload the invitation.
Changing the alert with a toast should fix the issue (or make it less likely to happen).

Invitation is accepted  in the other window not the one with the alert. I can see the problem when I manually close the alert popup and insert the link in another new window, then probably need to reload it a couple of times.

@marinoska
Pushed a fix.
When testing locally I was getting in the test console Failed to accept invite Error: Trying to accept invite: Group/owned value unavailable from all peers
This happens when the Group on the other side haven't been uploaded yet.
Added a fix with by adding a timeout after the invite creation but the test is still failing on CI on the first run (succedes on the second retry)
Hopefully #759 would bring a little more stability on this side.

Tested here if the retry system would help but no luck.
We need to do a deeper investigation on the problem.

LGTM
praise: I like ALOT how you set up the test code.
Very clean and easy to understand.

Thank you!


Added Keycloak 23.0.4, using getGroupByPath again and inverted briefRepresentation

What this PR does / why we need it:
As Keycloak 23.0.4 inverted the briefRepresentation flag, this needs to fix it.
Which issue this PR fixes: fixes #976
Special notes for your reviewer:

Updated CI to use Keycloak 23.0.4
Changed briefRepresentation from false to true (mistakenly considered full: #25096)
Using getGroupByPath again after being fixed (#25111)

PR Readiness Checklist:
Complete these before marking the PR as ready to review:

[x] the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR

@jonasvoelcker thank you for the quick turnaround!

Hi @st3v0rr, this one should be working, could you please try to rerun the failing build?

Hi @jkroepke, any chance to get this merged soon?


can you provide a release package download url

My company has limited network.So ,I can't download the package from the NPM,can you provide a release package download url?

If you are suing windows, the package is avialable at https://www.microsoft.com/en-us/download/details.aspx?id=48593 and thorugh Nuget: https://www.nuget.org/packages/Microsoft.TypeScript.Compiler/
for npm package contents, consider using git clone --depth 1

You mean using instead of suing? :wink:

:D thanks, updated.