gem issue

I have tried to install the gem with chef
sensu_gem 'sensu-transport-snssqs' do
  action :install
end

But I cannot find the snssqs.rb anywhere in /opt/sensu:
ubuntu@ip-172-31-5-200:/opt/sensu$ find . | grep snssqs
./embedded/lib/ruby/gems/2.3.0/cache/sensu-transport-snssqs-1.0.gem
./embedded/lib/ruby/gems/2.3.0/gems/sensu-transport-snssqs-1.0
./embedded/lib/ruby/gems/2.3.0/specifications/sensu-transport-snssqs-1.0.gemspec

Sensu does not find the transport either. A manual download and placement of the file here /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/sensu-transport-6.0.0/lib/sensu/transport/snssqs.rb
did work.
The statsd dependency was also not solved automatically.

It looks like the package published at rubygems.org are outdated. Can somebody please release an updated version?

I've uploaded the latest version, dubbed it 2.0 — https://rubygems.org/gems/sensu-transport-snssqs/versions/2.0.
Let me know if that doesn't work. Thanks!

@tomwans the 2.0 still does not contain the snssqs.rb file? Where is it supposed to be installed?

oops, my bad.
let's try this again: https://rubygems.org/gems/sensu-transport-snssqs/versions/2.0.1 ?

The gem file contains the transport file, but is does not work with sensu 0.25.3:
{"timestamp":"2016-07-01T06:43:22.827803+0000","level":"warn","message":"loading config file","file":"/etc/sensu/config.json"}
{"timestamp":"2016-07-01T06:43:22.827893+0000","level":"warn","message":"loading config files from directory","directory":"/etc/sensu/conf.d"}
{"timestamp":"2016-07-01T06:43:22.827931+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/ec2_node.json"}
{"timestamp":"2016-07-01T06:43:22.827979+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/ec2_node.json","changes":{"ec2_node":[null,{"ec2_states":["terminated","stopping","shutting-down","stopped"]}]}}
{"timestamp":"2016-07-01T06:43:22.828017+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/snssqs.json"}
{"timestamp":"2016-07-01T06:43:22.828071+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/snssqs.json","changes":{"snssqs":[null,{"max_number_of_messages":10,"wait_time_seconds":2,"region":"eu-central-1","consuming_sqs_queue_url":"https://sqs.eu-central-1.amazonaws.com/001579709704/sensu-server","publishing_sns_topic_arn":"arn:aws:sns:eu-central-1:001579709704:sensu-client-1","statsd_addr":"localhost:8125","statsd_namespace":"snssqs","statsd_sample_rate":1}]}}
{"timestamp":"2016-07-01T06:43:22.828113+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/checks/disk_usage_metrics.json"}
{"timestamp":"2016-07-01T06:43:22.828167+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/checks/disk_usage_metrics.json","changes":{"checks":{"disk_usage_metrics":[null,{"type":"metric","command":"metrics-disk-usage.rb -l --scheme :::scheme_prefix::::::name:::.disk_usage","standalone":true,"handlers":["metrics"],"interval":60,"occurrences":2}]}}}
{"timestamp":"2016-07-01T06:43:22.828230+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/checks/fs_writeable_tmp.json"}
{"timestamp":"2016-07-01T06:43:22.828281+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/checks/fs_writeable_tmp.json","changes":{"checks":{"fs_writeable_tmp":[null,{"command":"check-fs-writable.rb -d /tmp","standalone":true,"handlers":["default"],"interval":60,"occurrences":5}]}}}
{"timestamp":"2016-07-01T06:43:22.828316+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/checks/load_metrics.json"}
{"timestamp":"2016-07-01T06:43:22.828367+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/checks/load_metrics.json","changes":{"checks":{"load_metrics":[null,{"type":"metric","command":"metrics-load.rb --scheme :::scheme_prefix::::::name:::.load","standalone":true,"handlers":["metrics"],"interval":60,"occurrences":2}]}}}
{"timestamp":"2016-07-01T06:43:22.828406+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/checks/memory_metrics.json"}
{"timestamp":"2016-07-01T06:43:22.828459+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/checks/memory_metrics.json","changes":{"checks":{"memory_metrics":[null,{"type":"metric","command":"metrics-memory.rb --scheme :::scheme_prefix::::::name:::.memory","standalone":true,"handlers":["metrics"],"interval":60,"occurrences":2}]}}}
{"timestamp":"2016-07-01T06:43:22.828494+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/checks/ssh.json"}
{"timestamp":"2016-07-01T06:43:22.828543+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/checks/ssh.json","changes":{"checks":{"ssh":[null,{"command":"check-banner.rb","standalone":true,"handlers":["default"],"interval":60,"occurrences":5}]}}}
{"timestamp":"2016-07-01T06:43:22.828580+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/checks/swap.json"}
{"timestamp":"2016-07-01T06:43:22.828631+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/checks/swap.json","changes":{"checks":{"swap":[null,{"command":"check-swap.rb -w 60 -c 50","standalone":true,"handlers":["default"],"interval":60,"occurrences":5}]}}}
{"timestamp":"2016-07-01T06:43:22.828672+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/checks/memory.json"}
{"timestamp":"2016-07-01T06:43:22.828750+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/checks/memory.json","changes":{"checks":{"memory":[null,{"command":"check-memory.rb -w 15 -c 10","standalone":true,"handlers":["default"],"interval":60,"occurrences":5}]}}}
{"timestamp":"2016-07-01T06:43:22.828785+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/checks/load.json"}
{"timestamp":"2016-07-01T06:43:22.828835+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/checks/load.json","changes":{"checks":{"load":[null,{"command":"check-load.rb -p -w 3,2,1 -c 9,6,3","standalone":true,"handlers":["default"],"interval":60,"occurrences":5}]}}}
{"timestamp":"2016-07-01T06:43:22.828868+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/checks/disk_usage.json"}
{"timestamp":"2016-07-01T06:43:22.828918+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/checks/disk_usage.json","changes":{"checks":{"disk_usage":[null,{"command":"check-disk-usage.rb -w 80 -c 90 -x nfs,tmpfs,fuse","standalone":true,"handlers":["default"],"interval":60,"occurrences":5}]}}}
{"timestamp":"2016-07-01T06:43:22.828955+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/checks/interface_metrics.json"}
{"timestamp":"2016-07-01T06:43:22.829007+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/checks/interface_metrics.json","changes":{"checks":{"interface_metrics":[null,{"type":"metric","command":"metrics-interface.rb --scheme :::scheme_prefix::::::name:::.interface","standalone":true,"handlers":["metrics"],"interval":60,"occurrences":2}]}}}
{"timestamp":"2016-07-01T06:43:22.829043+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/checks/cpu_metrics.json"}
{"timestamp":"2016-07-01T06:43:22.829098+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/checks/cpu_metrics.json","changes":{"checks":{"cpu_metrics":[null,{"type":"metric","command":"metrics-cpu.rb --scheme :::scheme_prefix::::::name:::.cpu","standalone":true,"handlers":["metrics"],"interval":60,"occurrences":2}]}}}
{"timestamp":"2016-07-01T06:43:22.829139+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/checks/disk_metrics.json"}
{"timestamp":"2016-07-01T06:43:22.829191+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/checks/disk_metrics.json","changes":{"checks":{"disk_metrics":[null,{"type":"metric","command":"metrics-disk.rb --scheme :::scheme_prefix::::::name:::.disk","standalone":true,"handlers":["metrics"],"interval":60,"occurrences":2}]}}}
{"timestamp":"2016-07-01T06:43:22.829225+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/filters/occurrences.json"}
{"timestamp":"2016-07-01T06:43:22.829299+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/filters/occurrences.json","changes":{"filters":{"occurrences":[null,{"attributes":{"occurrences":"eval: value > :::check.occurrences|10:::"}}]}}}
{"timestamp":"2016-07-01T06:43:22.829333+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/filters/keepalives.json"}
{"timestamp":"2016-07-01T06:43:22.829387+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/filters/keepalives.json","changes":{"filters":{"keepalives":[null,{"attributes":{"check":{"name":"keepalive","status":2},"occurrences":"eval: value > 2"}}]}}}
{"timestamp":"2016-07-01T06:43:22.829421+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/filters/chef_env_prod.json"}
{"timestamp":"2016-07-01T06:43:22.829472+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/filters/chef_env_prod.json","changes":{"filters":{"chef_env_prod":[null,{"attributes":{"client":{"chef_env":"prod"}}}]}}}
{"timestamp":"2016-07-01T06:43:22.829512+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/filters/ec2.json"}
{"timestamp":"2016-07-01T06:43:22.829563+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/filters/ec2.json","changes":{"filters":{"ec2":[null,{"attributes":{"client":{"cloud_provider":"ec2"}}}]}}}
{"timestamp":"2016-07-01T06:43:22.829599+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/filters/actions.json"}
{"timestamp":"2016-07-01T06:43:22.829647+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/filters/actions.json","changes":{"filters":{"actions":[null,{"attributes":{"action":"eval: %w[create resolve].include? value.to_s"}}]}}}
{"timestamp":"2016-07-01T06:43:22.829680+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/filters/chef.json"}
{"timestamp":"2016-07-01T06:43:22.829732+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/filters/chef.json","changes":{"filters":{"chef":[null,{"attributes":{"client":{"chef_env":"eval: value.length > 0"}}}]}}}
{"timestamp":"2016-07-01T06:43:22.829802+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/handlers/ec2_node.json"}
{"timestamp":"2016-07-01T06:43:22.829857+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/handlers/ec2_node.json","changes":{"handlers":{"ec2_node":[null,{"type":"pipe","filters":["keepalives","ec2"],"severities":["warning","critical"],"command":"handler-ec2_node-custom.rb","timeout":300}]}}}
{"timestamp":"2016-07-01T06:43:22.829891+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/handlers/metrics.json"}
{"timestamp":"2016-07-01T06:43:22.829937+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/handlers/metrics.json","changes":{"handlers":{"metrics":[null,{"type":"set","handlers":["relay"]}]}}}
{"timestamp":"2016-07-01T06:43:22.829969+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/handlers/default.json"}
{"timestamp":"2016-07-01T06:43:22.830051+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/handlers/default.json","changes":{"handlers":{"default":[null,{"type":"set","handlers":["remedy","chef_node","ec2_node"]}]}}}
{"timestamp":"2016-07-01T06:43:22.830096+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/handlers/maintenance.json"}
{"timestamp":"2016-07-01T06:43:22.830146+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/handlers/maintenance.json","changes":{"handlers":{"maintenance":[null,{"type":"pipe","command":"handler-sensu-maintenance-custom.rb","timeout":300}]}}}
{"timestamp":"2016-07-01T06:43:22.830182+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/handlers/chef_node.json"}
{"timestamp":"2016-07-01T06:43:22.830241+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/handlers/chef_node.json","changes":{"handlers":{"chef_node":[null,{"type":"pipe","filters":["keepalives","chef"],"severities":["warning","critical"],"command":"sudo handler-chef-node.rb","timeout":300}]}}}
{"timestamp":"2016-07-01T06:43:22.830278+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/handlers/deregister.json"}
{"timestamp":"2016-07-01T06:43:22.830356+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/handlers/deregister.json","changes":{"handlers":{"deregister":[null,{"type":"pipe","command":"handler-sensu-deregister.rb","timeout":300}]}}}
{"timestamp":"2016-07-01T06:43:22.830391+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/chef.json"}
{"timestamp":"2016-07-01T06:43:22.830437+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/chef.json","changes":{"chef":[null,{"server_url":"chefzero://localhost:8889","client_name":"server1-ubuntu-1404","client_key":"/tmp/kitchen/client.pem","verify_ssl":false}]}}
{"timestamp":"2016-07-01T06:43:22.830532+0000","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/client.json"}
{"timestamp":"2016-07-01T06:43:22.830608+0000","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/client.json","changes":{"client":[null,{"address":"<IP_ADDRESS>","subscriptions":["region:eu-central-1","provider:ec2","env:_default","os:linux","all"],"name":"server1-ubuntu-1404","remedy_app":"Sensu Monitoring","remedy_group":"internet_services","ec2_ami_id":"ami-09618e66","ec2_instance_id":"i-0965ef12bea8254cc","ec2_instance_type":"t2.small","ec2_av_zone":"eu-central-1b","ec2_profile":"default-hvm","ec2_region":"eu-central-1","cloud_local_ipv4":"<IP_ADDRESS>","cloud_public_ipv4":"<IP_ADDRESS>","cloud_provider":"ec2","platform":"ubuntu","platform_version":"14.04","platform_family":"debian","chef_env":"_default","scheme_prefix":"sensu.sensu.eu-central-1b."}]}}
{"timestamp":"2016-07-01T06:43:22.836986+0000","level":"warn","message":"loading extension files from directory","directory":"/etc/sensu/extensions/client"}
{"timestamp":"2016-07-01T06:43:22.837355+0000","level":"info","message":"configuring sensu spawn","settings":{"limit":12}}
{"timestamp":"2016-07-01T06:43:23.086994+0000","level":"info","message":"subscribing to type=fanout, pipe=region:eu-central-1, funnel=server1-ubuntu-1404-0.25.3-1467355402"}
{"timestamp":"2016-07-01T06:43:23.087083+0000","level":"info","message":"subscribing to type=fanout, pipe=provider:ec2, funnel=server1-ubuntu-1404-0.25.3-1467355402"}
{"timestamp":"2016-07-01T06:43:23.087124+0000","level":"info","message":"subscribing to type=fanout, pipe=env:_default, funnel=server1-ubuntu-1404-0.25.3-1467355402"}
{"timestamp":"2016-07-01T06:43:23.087158+0000","level":"info","message":"subscribing to type=fanout, pipe=os:linux, funnel=server1-ubuntu-1404-0.25.3-1467355402"}
{"timestamp":"2016-07-01T06:43:23.087240+0000","level":"info","message":"subscribing to type=fanout, pipe=all, funnel=server1-ubuntu-1404-0.25.3-1467355402"}
{"timestamp":"2016-07-01T06:43:27.489973+0000","level":"info","message":"publishing check result","payload":{"client":"server1-ubuntu-1404","check":{"type":"metric","command":"metrics-cpu.rb --scheme :::scheme_prefix::::::name:::.cpu","standalone":true,"handlers":["metrics"],"interval":60,"occurrences":2,"name":"cpu_metrics","issued":1467355407,"executed":1467355407,"duration":0.132,"output":"sensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.total.user 11188<PHONE_NUMBER>\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.total.nice<PHONE_NUMBER>407\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.total.system 1984<PHONE_NUMBER>\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.total.idle 22792<PHONE_NUMBER>\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.total.iowait 15346<PHONE_NUMBER>\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.total.irq 0<PHONE_NUMBER>\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.total.softirq 13<PHONE_NUMBER>\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.total.steal<PHONE_NUMBER>407\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.total.guest 0<PHONE_NUMBER>\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.total. 0<PHONE_NUMBER>\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.cpu0.user 11188<PHONE_NUMBER>\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.cpu0.nice<PHONE_NUMBER>407\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.cpu0.system 1984<PHONE_NUMBER>\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.cpu0.idle 22792<PHONE_NUMBER>\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.cpu0.iowait 15346<PHONE_NUMBER>\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.cpu0.irq 0<PHONE_NUMBER>\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.cpu0.softirq 13<PHONE_NUMBER>\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.cpu0.steal<PHONE_NUMBER>407\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.cpu0.guest 0<PHONE_NUMBER>\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.cpu0. 0<PHONE_NUMBER>\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.intr 0<PHONE_NUMBER>\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.ctxt<PHONE_NUMBER>355407\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.btime<PHONE_NUMBER><PHONE_NUMBER>\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.processes 19050<PHONE_NUMBER>\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.procs_running 1<PHONE_NUMBER>\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.procs_blocked 0<PHONE_NUMBER>\nsensu.sensu.eu-central-1b.server1-ubuntu-1404.cpu.cpu_count 1<PHONE_NUMBER>\n","status":0}}}
{"timestamp":"2016-07-01T06:43:30.343655+0000","level":"info","message":"received check request","check":{"client":"server1-ubuntu-1404","check":{"thresholds":{"warning":120,"critical":180},"name":"keepalive","issued":1467355410,"executed":1467355410,"output":"No keepalive sent from client for 42631 seconds (>=180)","status":2},"signature":""}}
/opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/sensu-settings-5.2.0/lib/sensu/settings/loader.rb:184:in `definition_exists?': undefined method `to_sym' for nil:NilClass (NoMethodError)
Did you mean?  to_s
	from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/sensu-settings-5.2.0/lib/sensu/settings/loader.rb:62:in `block (2 levels) in create_category_methods'
	from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/sensu-0.25.3/lib/sensu/client/process.rb:211:in `process_check_request'
	from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/sensu-0.25.3/lib/sensu/client/process.rb:273:in `block (2 levels) in setup_subscriptions'
	from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/sensu-transport-snssqs-2.0.1/lib/sensu/transport/snssqs.rb:95:in `block (3 levels) in subscribe'
	from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/sensu-transport-snssqs-2.0.1/lib/sensu/transport/snssqs.rb:59:in `statsd_time'
	from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/sensu-transport-snssqs-2.0.1/lib/sensu/transport/snssqs.rb:91:in `block (2 levels) in subscribe'
	from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/eventmachine-<IP_ADDRESS>/lib/em/iterator.rb:138:in `block in each'
	from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/eventmachine-<IP_ADDRESS>/lib/em/iterator.rb:231:in `block in spawn_workers'
	from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/eventmachine-<IP_ADDRESS>/lib/eventmachine.rb:977:in `block in run_deferred_callbacks'
	from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/eventmachine-<IP_ADDRESS>/lib/eventmachine.rb:974:in `times'
	from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/eventmachine-<IP_ADDRESS>/lib/eventmachine.rb:974:in `run_deferred_callbacks'
	from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/eventmachine-<IP_ADDRESS>/lib/eventmachine.rb:194:in `run_machine'
	from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/eventmachine-<IP_ADDRESS>/lib/eventmachine.rb:194:in `run'
	from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/sensu-0.25.3/lib/sensu/client/process.rb:18:in `run'
	from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/sensu-0.25.3/exe/sensu-client:10:in `<top (required)>'
	from /opt/sensu/bin/sensu-client:22:in `load'
	from /opt/sensu/bin/sensu-client:22:in `<main>'

Btw. this problem even occurs using a single client without any check. The client works for a few seconds and then crashes with the error above.

@runningman84 — that does look like a very strange bug. Can you try with Sensu 0.25.0? That is the version we are using today and it's been working fine for us.

I wonder how does the client receive a check request? My assumption was that the client could not receive anything from the server using snssqs?

That's correct. However, the client will try to subscribe if there are non-standalone checks to be run. Maybe one of the checks are not in pure standalone mode?

All of my checks are standalone. The problem also happens with 0.25.
I have now commented out everything in the statsd_incr and statsd_time methods. The client seems to stay alive now.


Feature/dashboard

this branch contains the waitList merged into the Dashboard

@mickeymond  please I have resolved the merged conflicts and successfully merged please check it


Improve isEmptyReport performance

Details

Because getLastVisibleMessage is quite expensive operation and MOST of the Reports are not empty we want to avoid running that function in isEmptyReport, by adding the early return statement the method will not be called everytime the isEmptyReport is called
Traces before fix:

Trace with fix:

Please note that the above results are not guaranteed to occur in every instance. The getLastVisibleMessage function will not be called only when we have reports indicating that the first two conditions have been fulfilled. In such cases, we will experience the gain.
Fixed Issues

$
PROPOSAL: https://callstack-hq.slack.com/archives/C05LX9D6E07/p1721060786438019
Tests

Offline tests

QA Steps

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

@rinej @adhorodyski is there an issue or an internal engineer working with you for this?

@arosiclair we're coming from https://expensify.slack.com/archives/C05LX9D6E07/p1721060786438019 where we conduct these improvements with @muttmuure @mountiny @neil-marcellini

@arosiclair we're coming from https://expensify.slack.com/archives/C05LX9D6E07/p1721060786438019 where we conduct these improvements with @muttmuure @mountiny @neil-marcellini

Thanks for the link. Be sure to link to our slack in the PR description since your internal slack is not accessible for us and I had no clue where this change was coming from 😅 . It also would've been good to have an issue opened to track all of those PRs and add context.
This one is very simple so I'll just go ahead and merge the change.

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@arosiclair got you, totally understand - I can see it pointing poorly 😅
Thank you for moving with this so quickly! I'll make sure we also have a container issue for these items:)

🚀 Deployed to staging by https://github.com/arosiclair in version: 9.0.10-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 9.0.10-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/mountiny in version: 9.0.10-7 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/francoisl in version: 9.0.11-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Replicate MS MARCO passage and document dataset

Can you confirm that you are able to replicate the results?


1.16 bpf nodeport svc extract

Please ensure your pull request adheres to the following guidelines:

[ ] For first time contributors, read Submitting a pull request
[ ] All code is covered by unit and/or runtime tests where feasible.
[ ] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[ ] If your commit description contains a Fixes: <commit-id> tag, then
please add the commit author[s] as reviewer[s] to this issue.
[ ] All commits are signed off. See the section Developer’s Certificate of Origin
[ ] Provide a title or release-note blurb suitable for the release notes.
[ ] Are you a user of Cilium? Please add yourself to the Users doc
[ ] Thanks for contributing!

Fixes: #issue-number
<!-- Enter the release note text here if needed or remove this section! -->

/test

No clue why the diff for nodeport_lb4() looks so pretty, but nodeport_lb6() is an utter mess :/. Let me know if I should look into that a bit more to help with review.


ionic cordova platform add ios

when i run  ionic cordova platform add ios , Always show  '⠋ Running command' never success

Hello! Thanks for opening an issue with us! As this seems like more of a support question I will urge that you ask this question on our forum or on our slack channel. Thanks for using Ionic!


Site being served over HTTP on IIS despite HSTS and redirects enabled

I hope I'm not missing something simple here, but if I deploy a brand new dotnet new razor site using 2.1.0 to our IIS hosting platform, pages can still be requested over HTTP. I have verified that the hosting environment is Production, and yet despite the app.UseHsts(); and app.UseHttpsRedirection(); insecure requests seem to still work under some circumstances.
Using Chrome, if I open a new tab and type the bare host/domain, I see a 307 Internal Redirect in the logs that gives a non-authoritative reason of HSTS, which is what I expect to see. However, if I open a new incognito tab and prefix the host/domain with http:// then the site loads with a 200 OK on an insecure connection.
Am I missing something obvious here and this is working as intended? I expected that it would be impossible to request an unencrypted version of any pages. I should note that in a development environment I cannot reproduce this behaviour, even though app.UseHsts(); is not called all insecure requests seem to be redirected.

Duplicate of https://github.com/aspnet/Home/issues/3176


How to pass args with emit call?

What I expect
emitter.emit('fooEvent', {someKey: 123});
... and my fooEvent handler will receive this data object in its args.

Yep, that's how it works. Are you having an issue then?

I tried with this example ...
var EventEmitter = require('wolfy87-eventemitter');
var ee = new EventEmitter();

function listener(data) {
    console.log('The foo event has been emitted with args: ', data);
}

ee.once('foo', listener);
ee.emitEvent('foo', {someKey: 123});

and my console.log was The foo event has been emitted with args: , undefined
I just replaced ee.emitEvent with ee.emit('foo', {someKey: 123}) and all works good, sorry :)


harmony.end is not a function

One more addition. I get this error when restarting the homebridge instance. Is it known to you?

Originally posted by @Nastras in https://github.com/nicoduj/homebridge-harmony/issues/160#issuecomment-522059858

Dependency breaking change .


Datastore: test_transaction minor refactoring

Minor refactoring and just to separate the commits from my other code

ok.  Can close it.  I'll also change it in my other commit.
On Thu, Nov 2, 2017 at 12:46 PM, Danny Hermes<EMAIL_ADDRESS>wrote:

@dhermes commented on this pull request.
@chemelnucfin https://github.com/chemelnucfin I'm inclined to say this
shouldn't be merged.
ISTM the entire PR is a "hygiene"-type PR that prefers instance member
over test-case locals.
See my comment as to why we avoid these.
In datastore/tests/unit/test_transaction.py
https://github.com/GoogleCloudPlatform/google-cloud-python/pull/4330#discussion_r148640390
:

@@ -19,6 +19,9 @@

class TestTransaction(unittest.TestCase):

def setUp(self):

   self.project = 'PROJECT'

Please just use a class constant instead of setUp. (In general we avoid
setUp and tearDown at all costs because we'd prefer state to be "obvious"
like a class constant or local to each test case.)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-python/pull/4330#pullrequestreview-73916853,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADzDDIJkXQe_4Gq_fnop-brpJZOOD9Feks5syhwfgaJpZM4QQPdT
.


Add french international characters

Hi, thanks for your amazing work on this repository!
I added the definition for french international characters. Tested on Linux only, works great.

Fantastic, thanks for sharing!


Django3.0 compatibility issue

django-import-export 1.2.0 does not work with Django 3.0 because it dropped its internal version of six.
The following files are affected:

widgets.py
admin.py
resources.py
base_formats.py

Yep, we will need a release for this to be fixed as it was merged to master a while ago. @bmihelac I think its about time for a release. What do you think?

I agree.

2.0 was Released yesterday


Remove auto empty trash

The file picker now gives you granular control over the trash folder so this option is no longer needed.

This has been fixed. Auto empty trash has been removed from the game creator.


CIP8 Encryption Scheme

Description
This PR adds an encryption scheme to the OffchainData introduced by CIP8. It allows for data to be encrypted with a key that can either be directly embedded and encrypted to a reader's dataEncryptionKey or multiple encryptionKeys can be more centrally communicated with the EncryptedKeys schema
Other changes

Adds addAccount/removeAccount to the Wallet interface

Tested

Unit tests

Closing in favour of https://github.com/celo-org/celo-monorepo/pull/5091


stratify by selection

create a stratifcation based on the selection

could be added as stratify toolbar item to the selection column header.


Distribution of crystal in Debian (/Ubuntu ?) official releases

Hello,
For the moment crystal can be installed on Debian based systems using the package available on
crystal-lang APT repository.
I think that someday, the software will be integrated distribution's official package management systems so I took some time to check the current .deb packaging and tried to improve it a little bit.
For the moment, the archive -that seems to be generated using Omnibus- is working properly and allow to install and use the crystal tools. On the other hand, regarding to official packaging policies, I don't think it's "clean enough" to be integrated in the Debian -or Ubuntu- distribution.
So, I've built a new crystal package from scratch trying to respect Debian's packaging policy.
What I worked on is available in this repository: https://github.com/olbat/debian-crystal/ .
It allows to build Crystal 0.15.0 from a Debian/stretch (testing) machine (stable does not have libgc >= 7.4). All the build-dependencies have been set in the control file, do you think you can find the time to check them ?
I also opened a Request For Package on Debian's bugtracker to initiate the work -and also since finding a maintainer can take time: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822275 .
I don't know that much about Ubuntu, but if you find the idea interesting, someone may open a RFP  (or similar) on their tracker's too ?
I'm currently working on writing a Dockerfile to automate the building task, don't hesitate to give me your feedbacks !

Noobie question ahead:
As Ubuntu uses Debian as a base distribution, doesn't being accepted in Debian's package repository implies being available in ubuntu too (in a future release)?

Another consideration is that the language and thus its community is still moving very fast. Being accepted into Debian and getting into a stable Debian release subsequently, will mean Debian users using the official repository will be stuck on an old Crystal version that's incompatible with the rest of the ecosystem very quickly. Same basically applies to Ubuntu.
I appreciate your effort but I feel like it might come a bit too early still.

That said maintaining a Ubuntu PPA that doesn't has to comply to Debian's stability policy, using non Omnibus but hand-crafted packages can be a worthwhile effort, exploring things packaging best practices for Crystal (see for example the route we took in the Archlinux packages) or  compatibility considerations for Crystal (see for example #1614), so that we catch these things early on and don't head into a direction that'll later makes it impossible to include Crystal into mainstream distributions, once it stabilizes.

I understand, in fact I do not really know the state of the project yet, it's probably a bit too early :)
BTW the you'll want the project to be distributed into Debian or Ubuntu, do not hesitate to look into the repository I worked on to have something to start with.
Another thing that you may want take in consideration: some distributions have long release cycles and no new packages are added to stable releases so you have to wait for the next one.
For example the next Debian/stable is planed for Q1 2017, the one after this one will probably be in 2019.

I'm done working on the docker image that allow to build crystal and it's Debian package (see Dockerfile). [As you can see since build dependencies are given in the package (the debian/control) file, it's much easier to install them using mk-build-deps or apt-get build-dep]
You can build the .deb archive using the docker image by doing docker run --rm -v ${PWD}:/src/crystal olbat/debian-crystal (generated files will be copied into the repository's directory).
I tried to rebuild a new crystal package using the version of crystal that I compiled, it worked like a charm.
One last thing, during the build I got some warnings about program's linking with shared libraries that you may find interesting:
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/crystal/usr/bin/crystal was not linked against libedit.so.2 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/crystal/usr/bin/crystal was not linked against libffi.so.6 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/crystal/usr/bin/crystal was not linked against librt.so.1 (it uses none of the library's symbols)

I'd prefer to wait until we start distributing official packages for some distros. For now, I think it's better to move this discussion to a place like Google Groups, because there's nothing we'll do about this right now.


wsk activation poll with a parameter will get no response.

I followed the doc:
https://github.com/openwhisk/openwhisk/blob/e5c4e58f8dfe63601f5e4395e7582b626c426678/docs/packages.md#creating-and-using-trigger-feeds
then I wrongly typed the command
wsk activation poll activationID,
I got below output, but it seems the poll not responding.
Hit Ctrl-C to exit.
Polling for logs
The correct command should be:
wsk activation result activationID
Then I can get result.
So is it a issue? I searched the issues list title before open this one, sorry if duplicated.

> wsk activation poll -h
usage: wsk activation poll [-h] [-u AUTH] [-e EXIT] [-ss SINCE_SECS]
                           [-sm SINCE_MINS] [-sh SINCE_HRS] [-sd SINCE_DAYS]
                           [name]

positional arguments:
  name                  the namespace to poll

The value you provided is interpreted by the CLI as a namespace. Since it's a namespace that doesn't exist, you get an empty activation list.

Ah, got it, thank you, I'll close it.


Add ci

Great! I have not looked at the tests here in a while sadly. Been using the tests in juCi++ instead, but the tests here should be updated as well if they are not working.


Content Suggestion: NAME OF CONTENT TO BE ADDED

Link to Content: https://hexawallet.io
Briefly Describe Content: Add Bitcoin only Hexa wallet to the wallets section. non-custodial, no shitcoins, open source, multisig option, user friendly.
Suggested Section: Wallets section

ACK
I am working with them. Ambitious team. Non-custodial bitcoin wallet for android and iOS.

Okay cool, proceed with PR

Varunram from the hexa team here. Thanks to all for the approval, will submit a PR later today.

It's been added


Implementing support for multi-protocol chip

Analyzing ways to implement driver support for radio+mcu SoC to be used as Border Router. As I can see, currently most common way to do that currently is to build firmware for SoC and then connect it to host CPU using SPINEL-over-UART/SPI
I.e. posix application expects uart transport: spinel+hdlc+uart:///dev/ttyACM0
But since we use proprietary serialization protocol over SPI that also includes BLE/ZigBee/etc protocols, we could not reuse this model.
However, we have proprietary 802.15.4 MAC inteface available on host CPU that could be used in openthread by implementing corresponding drivers. We are currently using it this way:
[OT CLI with drivers] <--Proprietary ioctl interface--> [MAC interface in kernel] <-SPI-> [SoC with Radio]
ot-br-posix implementation expects to have SPINEL-over-SPI/UART and we are looking for a ways to be compatible with mainline openthread, so adding additional SPINEL-over-proprietary is not a good option.
I guess most appropriate way to do that would be to somehow build RCP with mac drivers for host CPU in that way:
[ot-br-posix binary] <-SPINEL-> [ot-rcp binary] <--Proprietary ioctl interface--> [MAC interface in kernel] <-SPI-> [SoC with Radio]
Similar to how it is used in simulation, but with real calls to MAC. Before wpantund got deprecated, I was able to build ot-ncp-ftd for host and use it for border router.
Is that right way to go from openthread perspective?
Are there any existing or in-progress implementation for multi-protocol chips?

@nikita-s-wrk , if the IEEE 802.15.4 MAC functionality is directly callable on the host, I suggest directly the otPlatRadio APIs such that they directly call your IEEE 802.15.4 MAC APIs. This would avoid the overhead of dealing with spinel.
You can find one example here: examples/platforms/qpg6095/radio.c

@jwhui
Thanks for reply.
But in that case it will require to have "special" build for applications like ot-br-posix, right?

@jwhui
Thanks for reply.
But in that case it will require to have "special" build for applications like ot-br-posix, right?

@nikita-s-wrk , it depends on what your goals are. If you prefer to keep spinel (and the overhead of additional IPC), then you can follow a model similar to how we run ot-daemon with a "simulated" RCP. In your case, replace the simulated RCP executable with one that calls your IEEE 802.15.4 MAC APIs.

@jwhui
Thanks for reply.
But in that case it will require to have "special" build for applications like ot-br-posix, right?

@nikita-s-wrk , it depends on what your goals are. If you prefer to keep spinel (and the overhead of additional IPC), then you can follow a model similar to how we run ot-daemon with a "simulated" RCP. In your case, replace the simulated RCP executable with one that calls your IEEE 802.15.4 MAC APIs.

I see doing it like this and keeping spinel is the only option to deliver back to mainline openthread as platform, right?

We intentionally keeps the spinel protocol in the URL, aiming at being extensible for other radio protocols.

@nikita-s-wrk , it depends on what your goals are. If you prefer to keep spinel (and the overhead of additional IPC), then you can follow a model similar to how we run ot-daemon with a "simulated" RCP. In your case, replace the simulated RCP executable with one that calls your IEEE 802.15.4 MAC APIs.

I see doing it like this and keeping spinel is the only option to deliver back to mainline openthread as platform, right?

@nikita-s-wrk , I mentioned two different approaches above:

Implement otPlatRadio* APIs directly.
Implement RCP+spinel and use IPC.

Both approaches are currently used within the GitHub repo.
Is there an alternative approach you'd like to consider/propose?

Hi Jonathan,
Implementing otPlatRadio directly will break compatibility with apps i.e. otbr-posix that I see as crucial part to be aligned to openthread project.
RCP+spinel on host side is looking good to me. However, we should ensure it will not bring significant latency due to IPC.
Different option from that could be: implement uart-over-proprietary in kernel driver and bridge SPINEL to SoC over it, running RCP as part of firmware. Downside of that - we'll be not able to update openthread without rebuilding firmware and integrating rebuild in openthread build system would be not trivial. Also, memory-constrained or fw-less chips will not work that way obviously.

@nikita-s-wrk , I agree that it seems the RCP is the quickest path forward for you. Note that the quickest path to implementing RCP is by implementing the otPlatRadio* APIs - doing so will allow you to leverage the RCP implementation in src/ncp.

Closing stale issue.


Respond to Changes in EnvDTE.ProjectKind

A change is being made to EnvDTE.ProjectKind. We will need to look through our code and make sure everything is still working and make changes as appropriate. See email on 5/24/18 titled "Breaking change: Project.Kind for C#/VB/F# CPS projects is changing". Quick summary:

Language
Previous Project.Kind
New Project.Kind

C#
{9A19103F-16F7-4668-BE54-9A1E7A4F7556}
{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}

Visual Basic
{778DAE3C-4631-46EA-AA77-85C1314464D9}
{F184B08F-C81C-45F6-A57F-5ABD9991F28F}

F#
{6EC3EE1D-3C4E-46DD-8F32-0CC8E7565705}
{F2A71F9B-5D33-465A-A702-920D77279786}

Noooo - when will this happen??

@ErikEJ To clarify a bit more:

We’re making a breaking change to the return value of EnvDTE.Project.Kind for managed C#, Visual Basic and F# projects that open in the Common Project System (CPS). These are traditionally .NET Core/ASP.NET Core/.NET Standard projects, however, can also target .NET Framework in certain scenarios.

This value has been changed to match their equivalent in the native project system (.NET Framework, Xamarin, UWP and Portable). This change does not affect the native C#/VB project systems.

Thanks!

Since EF6 doesn't support the new-style projects anyway, this is unlikely to be an issue for us. It could actually make things work, although there will likely still need to be more work done as part of the Core port.


Increase result limit for the number of entries

Increase the result limit for the number of entries or provide a configuration option for it.
Rationale: It's useful to page up/down through the results sometimes.
For now, I have been manually overriding it via:
diff --git a/lua/smart-open/matching/multithread/create.lua b/lua/smart-open/matching/multithread/create.lua
index 0d07b4a..0a2650e 100644
--- a/lua/smart-open/matching/multithread/create.lua
+++ b/lua/smart-open/matching/multithread/create.lua
@@ -12,7 +12,7 @@ local function create_matcher(matching_algorithm, context)
   local slot_count = 4 -- threadpool thread count
   local last_processed_index = 0
   local top_entries = {} -- treat it as ascending (lowest relevance last)
-  local top_entry_count = 20
+  local top_entry_count = 1024
   local waiting_threads = 0
   local history_data_cache = {}

diff --git a/lua/smart-open/matching/multithread/process.lua b/lua/smart-open/matching/multithread/process.lua
index 08d769d..f881c64 100644
--- a/lua/smart-open/matching/multithread/process.lua
+++ b/lua/smart-open/matching/multithread/process.lua
@@ -1,6 +1,6 @@
 -- prompt, cancel_token, options, last_processed_index
 local function process(prompt, cancel_token, encoded_options, encoded_entries)
-  local result_limit = 20
+  local result_limit = 1024

   local ok, result = pcall(function()
     local options = vim.mpack.decode(encoded_options)

The trouble is that this can hurt performance, especially if we're returning more entries from each job.
It would probably be better to increase the value from 50 in lua/telescope/_extensions/smart_open/finder/finder.lua to whatever you want it to be.
Unfortunately, increasing this value is also bad for performance because inserting entries into telescope is somewhat slow.  Honestly, I think 50 is even too much for most cases I can think of.  If you're moving up and down through 50 entries, what's your use case? I'm far more interested in improving the search so that the thing you're looking for is in the top 10.
I'd be open to increasing the result_limit and the priority queue limit of 50 in finder.lua a little bit if necessary if anyone wants to run experiments on performance and can find an ideal value here.

Second this, as it currently leaves a huge blank in some Telescope layouts

Also looking into having this configurable.

I haven't prioritized this because it isn't clear what such a setting is useful for beyond filling out a larger results pane.  If the entry you're looking for isn't in the top 20 items, then how efficient is it for anybody to scroll through looking for what you need?  That's what I meant when I asked about a use case.  I just think I'm missing something if the entry you need is not in the top 20 items.  So there's a couple things that make me hesitate on this:

If we make the result set configurable, then will there be more performance complaints?
Maybe this points to a deeper issue and the results are so useless that people have to page through over 20 results to get to what they need! I'd rather get feedback that can help the results be more useful than publish a setting that doesn't fix a bigger issue.

I may just be missing something, but that's why I want to hear more info.

Scrolling is beneficial when the user doesn't know exactly what they're looking for.
Example: Consider a large codebase with 10000+ files. The user wants something related to ".../sdk/.../components/...". But there may be 100s of such components.
The fastest way to figure out which files may be relevant is some sort of fuzzy search + scroll through results. Another alternative:
fd | fzf

...but then that adds a few extra steps of: (i) open another terminal, (ii) run command, (iii) once a list of candidate files is determined, open each candidate manually in the editor by searching for them again.
This use case is similar to grep-style searches through a large codebase, though it's a much more lightweight and quicker alternative since the user already has some idea of the what part of the filename is.

My use case is very similar to @YodaEmbedding. I'm not trying to find anything particularly at the beginning of the search but I need to filter a set of files and navigate through them (previewing the contents) until I can further refine the search filter.

That helps, and it's a reasonable scenario.  I'm not sure if this tool is the best for that because all you want in that case is a huge list of files more or less in the same directory.  Relevance plays virtually no part there.  Though I wonder...if you don't know what you're looking for except by name, how do you know when you've found it?
Still, I think part of the point for this plugin is to not have to have a bunch of different keybinds to jump between files.  You shouldn't have to think "Is it a buffer?  A recent file? ..." etc.  You've brought up a useful scenario and has gotten several upvotes.  Let me prioritize this, but I don't really think I can do much about the speed, and it may be slower.  I'll just mention that in the docs.

Like you said, having the same key binding to find files is a big plus. In my case I just need a bit more than 20 results when I’m not sure what I’m searching for yet.
I’ve been using 50 results (using the code changes provided by @YodaEmbedding above) and didn’t noticed any slowdowns.

OK, this is out on the 0.2.x branch.  The option is called result_limit

Thanks @danielfalk, works as expected :)


[Android] Support theme color at task switcher on Lollipop+(5.0+)

For Android version older than 5.0, this doesn't work.
BUG=XWALK-4305

@fujunwei  @halton  @lincsoon

LGTM

For Android version older than 5.0, this doesn't work.

Do you mean "older" or "newer"? The title says this change makes it work on Android >= 5.0, but the contents then say this is supposed to make it work on versions older than 5.0 (< 5.0).

Sorry for this confusion, older means  >5.0. I used a time since android begins. So android 2.2 or 4.0 is much older than android 5.0

LGTM

Sorry for this confusion, older means >5.0. I used a time since android begins. So android 2.2 or 4.0 is much older than android 5.0

2.2 is older than 5.0, and it is also < 5.0. Sorry for being picky here, but otherwise this will get very confusing in the future if someone checks this pull request or the commit message.
 This avoids confusion and also explains why you are doing what you are doing.

Thanks @rakuco, updated.

Thanks! Please backport it to 16.


Typo in filter documentation

Simplify FREME output using SPARQL filters might have a typo.
This query should return all named entities in the first sentence of the eiffel tower wikipedia article as CSV list:
entity
http://dbpedia.org/resource/Champ_de_Mars
http://dbpedia.org/resource/Torkham
http://dbpedia.org/resource/Eiffel_Tower
http://dbpedia.org/resource/France
http://dbpedia.org/resource/Paris
http://dbpedia.org/resource/Eiffel_(programming_language)

The first line of the example is "entity". Is this correct?

Yes, the first line is the header of the csv table.

Please add a sentence to the documentation to explain this.

fixed.


JAX implicitly restarted arnoldi

fix convergence test, add tests

Codecov Report

Merging #857 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #857   +/-   ##
=======================================
  Coverage   98.20%   98.21%
=======================================
  Files         129      129
  Lines       22179    22268   +89
=======================================
+ Hits        21781    21870   +89
  Misses        398      398

Impacted Files
Coverage Δ

...ensornetwork/backends/jax/jitted_functions_test.py
100.00% <ø> (ø)

tensornetwork/block_sparse/blocksparsetensor.py
99.74% <ø> (ø)

tensornetwork/backends/jax/jax_backend_test.py
99.25% <100.00%> (+0.08%)
:arrow_up:

tensornetwork/backends/jax/jitted_functions.py
97.59% <100.00%> (+0.04%)
:arrow_up:

Continue to review full report at Codecov.

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

@alewis @Thenerdstation ping for review!


372 Add Image Card Blocks

addresses #372
I went with creating a new feature instead of updating all existing.
I also increased max-width on our container by one size.


Link to wiki?

After taking a look at the documentation, I have found that some of the links that lead to the wiki is not available (eg. https://github.com/googlecreativelab/anypixel/wiki/Communications-Packets leads back to the main project page) - Is there a hidden wiki somewhere, or is it simply not published yet?

We haven't set up the wiki yet. All of the documentation is handled at the README level. Where did you surface that link that you shared? I'll look into it.
Thanks!

If it helps, I encountered that link in the readme for /backend/chromebridge (at the end of this section).

Ah @jonahsmith thank you! We didn't catch that. That link is in error. All documentation is done at the README level. There should not be a wiki.


Fabric 1.21.1

Hi! Any plans to update Collision Fix to support 1.21.1? :)

Hmm, is it doesn't work on 1.21.1?


Cross multiplication on JAX is faster in CPU compared to GPU

I tried taking the cross product of two (10,000 * 10,000) matrics on NumPy, TensorFlow and Jax to compare the time it takes to complete the operation.
On CPU:
Numpy took 58.32 seconds
TensorFlow took 64.802 seconds
Jax took 0.034 seconds
On GPU:
Numpy took 59.04 seconds (understandable because NumPy doesn't use GPU or TPU acceleration)
TensorFlow took 0.197 seconds
Jax took 2.02 seconds
Why is Jax slower on GPU(2.02 seconds) as compared to CPU(0.034 seconds)?

From the large difference on CPU I suspect you did not use .block_until_ready() on the result array when measuring the time? JAX normally computes asynchronously, which means that the function call returns immediately even though the actual numerical computation is not finished.
So, instead of
%timeit fun(arr)

for fun returning an array, rather use
%timeit fun(arr).block_until_ready()

It works. Thank you


There were missing types in the Body.

I found a better tool to generate the types.  Hopefully this matches better since it is using the Swagger yaml file.

This looks good, thanks


Can i use  React-Native and ngreact  together?

Can i use  React-Native and ngreact  together?

I dont see how. Angular is about the dom so is ngReact.
Did you have a specific scenario in mind?

Closed due to inactivity. Feel free to reopen.

Closed due to inactivity. Feel free to reopen.


No configs gives IG:dm

I tried loging in, but says no configs given
I got the username and password right!!
Need help!

I tried loging in, but says no configs given
I got the username and password right

I tried logging in, but says no configs given
I got the username and password right
Help me

Who can help me please, I have correct username and password and says No Configs Given... how can I fix it?

I tried loging in, but says no configs given
I got the username and password right!!
Need help!
I have the same problem and I do not know what to do...


Bug 404 whatever the image is

Ok I have this 404 error, I did a try with "docker pull kitematic/hello-world-nginx"
gave me :
Pulling repository kitematic/hello-world-nginx
FATA[0000] Get https://index.docker.io/v1/repositories/kitematic/hello-world-nginx/images: dial tcp: lookup index.docker.io on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:53: connection refused

Ok, adding new dns in the boot2docker image, rebooting, and removing dnscrypt.
All that solved my problem.


add toggle for switching classes in binary classification case

Description
In the binary classification case for the aggregate feature importances and local importances (in the explanation component which is used in the RAI Dashboard, explanation dashboard, and error analysis dashboard), this PR adds the same drop-down as in multiclass case to allow the user to switch between the two binary classes.  Please see long-standing item:
https://github.com/microsoft/responsible-ai-toolbox/issues/374
Previously we would only show class 0 to users which was really, really confusing them a lot.
Screenshot for aggregate feature importances view:

Checklist

[x] I have added screenshots above for all UI changes.
[ ] Documentation was updated if it was needed.
[x] New tests were added or changes were manually verified.

Codecov Report

Merging #1444 (b5644a4) into main (7de48f7) will increase coverage by 3.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1444      +/-   ##
==========================================
+ Coverage   85.94%   88.95%   +3.01%
==========================================
  Files         100       34      -66
  Lines        4801     1521    -3280
==========================================
- Hits         4126     1353    -2773
+ Misses        675      168     -507

Flag
Coverage Δ

unittests
88.95% <ø> (+3.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

...idgets/raiwidgets/responsibleai_dashboard_input.py

...i/responsibleai/managers/counterfactual_manager.py

...ai/responsibleai/_tools/causal/causal_constants.py

...bleai/responsibleai/_tools/causal/causal_config.py

responsibleai/responsibleai/exceptions.py

responsibleai/responsibleai/utils.py

raiwidgets/raiwidgets/dashboard.py

.../responsibleai/modelanalysis/constants/__init__.py

raiwidgets/raiwidgets/error_handling.py

...tools/error_analysis/dashboard_schemas/__init__.py

... and 56 more

Continue to review full report at Codecov.

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


Make the check_delay parameter configurable

Abstract
This makes the currently hardcoded value of delay time between two consecutive attempts configurable, using a default value of 30 seconds, also to be backwards compatible.
Rationale
In some cases (especially when running multiple instances of the script using the "profile" option) the default value of 30 seconds is too aggressive, leading to 429 responses from the remote server.
Usage
Basically there is just another optional command line argument --retry-sec:
% python3 main.py search -h
vaccipy - Automatische Terminbuchung für den Corona Impfterminservice

usage: main.py search [-h] [-f FILE] [--configure-only] [--retry-sec RETRY_SEC]

optional arguments:
  -h, --help            show this help message and exit
  -f FILE, --file FILE  Pfad zur JSON-Datei für Kontaktdaten
  --configure-only      Nur Kontaktdaten erfassen und in JSON-Datei abspeichern
  --retry-sec RETRY_SEC, -r RETRY_SEC
                        Wartezeit zwischen zwei Versuchen (in Sekunden)

Discussion
For my use case the sweet spot is around 50 seconds using 2 distinct profiles in parallel, being able to run the two instances for several hours without issues.

Good idea, maybe we should also raise the default delay to 60 then

Good idea, maybe we should also raise the default delay to 60 then

I agree, this will also reduce the load on the kv-digital infrastructure..

Good idea, maybe we should also raise the default delay to 60 then.
Edit: Would you mind changing the default?

sure thing! done with dba896d

Thanks!

Maybe -s is a better shorthand, because -r is commonly used for recursive or read....

See #99


Responsivity problems

The sidebox can't handle smaller content container than itself. Also, it doesn't react well to resizing the content container without reloading the page.
P.S. very nice sidebox anyway

https://abouolia.github.io/sticky-sidebar/#minwidth


Update partners.md

Updating Modus Create partner description to:
Modus Create is a digital product agency that supports clients with business and product strategy consulting, customer experience, cloud services, and Agile software delivery. Our official partnerships with Atlassian, AWS, GitHub, Ionic Framework, InVision, Cloudflare, and Vue.js reinforce our proven results with digital transformation with organizations from startups to the Fortune 100.

As this is not adding but a (minor) modifying, I think we can go ahead and merge it without having to await for @yyx990803.


DynamicModel Atribute Declaration

As per documentation for the DynamicModel under Adhoc Validation  example hows attributes being passed to the model as new DynamicModel(compact('attribute_name_1','attribute_name_2')) where as this does not work and does not declare the model attributes
What steps will reproduce the problem?
$model = new DynamicModel(compact('finance_needed'));

print_r($model->attributes);

What is the expected result?
it should display
[
'finance_needed=>''
]

What do you get instead?
It shows empty array as if no attributes were declared if i try to validate like this it throws the exception

Setting unknown property: yii\base\DynamicModel::finance_needed

Additional info
If i change it to a normal array like below
new DynamicModel(['finance_needed']);
then it works correctly and declare the attribute for the model

Q
A

Yii version
2.0.15?

PHP version
5.6.35-1+ubuntu14.04.1+deb.sury.org+1

Operating system
ubuntu14.04.1

The docs could be a bit misleading for anyone who just copy pastes the example.
It uses compact which will ignore any variables it can't find.
This won't work
{
  $model = new DynamicModel(compact('finance_needed'));
  print_r($model->attributes);
}

While this will
{
  $finance_needed = 'my value here';
  $model = new DynamicModel(compact('finance_needed'));
  print_r($model->attributes);
}

If you don't need to provide values during initialisation then just pass the attribute name as you have new DynamicModel(['finance_needed']);

https://github.com/yiisoft/yii2/commit/033f2b4a13d31a5f202810eef9fad6e2c2f5e7bd

Thanks for reporting.


Show Storage Disks that are in the Disk Drive on the block texture

Possible alternative: unlike AE2 where individual drive status (stacks full, drive full) is important, drives in this mod mostly use their disks to expand storage. So instead of a drive by drive report it might be nice to have the overall drive status reflected like the energy bar on the controller.

that is a wonderful idea actually, will pass this to gusto.

Done


[nav.ts] New sidebar sections: built-ins and add-ons

Description (required)
Adds two new sections to our main sidebar: Built-ins and Add-ons.
This intends to better highlight the natural progression of learning about Astro: Basics > not basic, but included stuff you probably want > things you can add-on that are part of our  story: framework islands and hyping our rendering options
Play around and see what you think!
Current Docs -> Proposal:

Big fan of the change!

I like how this new clustering helps already place the user context when looking for docs, it just brings the wish for more, for example adding a cms is also adding integrations so it feels like it should be in add-ons but then it's also a recipe.

same comment as above regarding the ssr as add-ons, impression jumped to me when I saw it. I understand that some adapters are addon, but node js is built in I think, but I might be wrong.

one thing that triggers thoughts about add-ons vs built-ins, users might confuse them with officially supported and maintained vs provided by the community or third party, which come in mind when reading the heading "Official integrations", so it's an "official add on". If only there was a good spot where it's poosible to explain what is built in and what is add on, maybe in the intro of each first page in each category.
those are just thoughts, all in all get much better over time.

@wassfila Even the Node adapter has to be added! (FYI)

Final decision after consultation with the team:
SSR label in sidebar changed to "SSR Adapters" in keeping with the idea of the adapter being the "add on", and less to imply stuff about our actual rendering modes.
This is a non-content/breaking change that only moves items in the sidebar. But, the plan is to augment this and allow us to include a "Rendering Mode" explanatory page in basics, and eventually this SSR page will in fact be geared towards enabling and using the adapters


examples/coap (liboscore) on armv6m CI build failure on CI

Summary
error: linking with `rust-lld` failed: exit status: 1
  |
  = note: LC_ALL="C" PATH="/home/runner/.rustup/toolchains/nightly-2024-05-20-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/bin:/home/runner/.cargo/bin:/opt/hostedtoolcache/sccache/0.8.1/x64:/snap/bin:/home/runner/.local/bin:/opt/pipx_bin:/home/runner/.cargo/bin:/home/runner/.config/composer/vendor/bin:/usr/local/.ghcup/bin:/home/runner/.dotnet/tools:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin" VSLANG="1033" "rust-lld" "-flavor" "gnu" "/tmp/rustcTxUJH8/symbols.o" "/home/runner/work/RIOT-rs/RIOT-rs/examples/coap/../../build/bin/rpi-pico/coap/cargo/thumbv6m-none-eabi/release/deps/coap-1a5ba26ce4603683.coap.980900a94a691917-cgu.0.rcgu.o" "--as-needed" "-L" "/home/runner/work/RIOT-rs/RIOT-rs/examples/coap/../../build/bin/rpi-pico/coap/cargo/thumbv6m-none-eabi/release/deps" "-L" "/home/runner/work/RIOT-rs/RIOT-rs/examples/coap/../../build/bin/rpi-pico/coap/cargo/release/deps" "-L" "/home/runner/work/RIOT-rs/RIOT-rs/examples/coap/../../build/bin/rpi-pico/coap/cargo/thumbv6m-none-eabi/release/build/defmt-80592f337d3d523b/out" "-L" "/home/runner/work/RIOT-rs/RIOT-rs/examples/coap/../../build/bin/rpi-pico/coap/cargo/thumbv6m-none-eabi/release/build/liboscore-1869f3cbdcc9cefc/out" "-L" "/home/runner/work/RIOT-rs/RIOT-rs/examples/coap/../../build/bin/rpi-pico/coap/cargo/thumbv6m-none-eabi/release/build/cortex-m-15f9f17cccca1b61/out" "-L" "/home/runner/work/RIOT-rs/RIOT-rs/examples/coap/../../build/bin/rpi-pico/coap/cargo/thumbv6m-none-eabi/release/build/riot-rs-rt-40131ddd18c2793d/out" "-L" "/home/runner/work/RIOT-rs/RIOT-rs/examples/coap/../../build/bin/rpi-pico/coap/cargo/thumbv6m-none-eabi/release/build/cortex-m-rt-cf61485e44677a0d/out" "-L" "/home/runner/work/RIOT-rs/RIOT-rs/examples/coap/../../build/bin/rpi-pico/coap/cargo/thumbv6m-none-eabi/release/build/rp2040-7fe733d862f4f47d/out" "-L" "/home/runner/work/RIOT-rs/RIOT-rs/examples/coap/../../build/bin/rpi-pico/coap/cargo/thumbv6m-none-eabi/release/build/embassy-rp-30e866bf5011cef2/out" "-L" "/home/runner/work/RIOT-rs/RIOT-rs/examples/coap/../../build/bin/rpi-pico/coap/cargo/thumbv6m-none-eabi/release/build/rp-pac-57c39bb19e30139e/out" "-L" "/home/runner/.rustup/toolchains/nightly-2024-05-20-x86_64-unknown-linux-gnu/lib/rustlib/thumbv6m-none-eabi/lib" "-Bstatic" "/tmp/rustcTxUJH8/libliboscore-c1002fd4db71cefd.rlib" "/tmp/rustcTxUJH8/libcortex_m-9c72b8b9f3b7a158.rlib" "/home/runner/.rustup/toolchains/nightly-2024-05-20-x86_64-unknown-linux-gnu/lib/rustlib/thumbv6m-none-eabi/lib/libcompiler_builtins-9573e01946a4d685.rlib" "-Bdynamic" "--eh-frame-hdr" "-z" "noexecstack" "-L" "/home/runner/.rustup/toolchains/nightly-2024-05-20-x86_64-unknown-linux-gnu/lib/rustlib/thumbv6m-none-eabi/lib" "-o" "/home/runner/work/RIOT-rs/RIOT-rs/examples/coap/../../build/bin/rpi-pico/coap/cargo/thumbv6m-none-eabi/release/deps/coap-1a5ba26ce4603683" "--gc-sections" "--nmagic" "--no-eh-frame-hdr" "-Tlinkme.x" "-Tlink.x" "-Tdevice.x" "-Tisr_stack.x" "-Tlink-rp.x" "-Tdefmt.x"
  = note: rust-lld: error: undefined symbol: __gnu_thumb1_case_uqi
          >>> referenced by oscore_message.c:52 (c-src/oscore_message.c:52)
          >>>               905f1f7c3b7e961f-oscore_message.o:(get_option_behaviour) in archive /tmp/rustcTxUJH8/libliboscore-c1002fd4db71cefd.rlib

warning: `coap` (bin "coap") generated 6 warnings
error: could not compile `coap` (bin "coap") due to 1 previous error; 6 warnings emitted
FAILED: build/bin/rpi-pico/coap/coap.elf
cd examples/coap && OPENOCD_ARGS="-f interface/cmsis-dap.cfg -f target/rp2040.cfg" SCRIPTS=../../scripts CONFIG_BOARD=rpi-pico CARGO_BUILD_TARGET=thumbv6m-none-eabi CARGO_TARGET_THUMBV6M_NONE_EABI_RUNNER='probe-rs run --protocol=swd --chip RP2040' CARGO_TARGET_THUMBV6M_NONE_EABI_RUSTFLAGS="-Clink-arg=--nmagic -Clink-arg=--no-eh-frame-hdr --cfg builder=\"rpi-pico\" --cfg context=\"rpi-pico\" --cfg context=\"riot-rs\" --cfg context=\"rp\" --cfg context=\"rp2040\" -Clink-arg=-Tlinkme.x -Clink-arg=-Tlink.x -Clink-arg=-Tdevice.x -Clink-arg=-Tisr_stack.x --cfg context=\"cortex-m\" --cfg armv6m -Clink-arg=-Tlink-rp.x -Clink-arg=-Tdefmt.x --cfg capability=\"hw/usb-device-port\" -Cembed-bitcode=yes -Clto=fat -Ccodegen-units=1" CARGO_TARGET_DIR=../../build/bin/rpi-pico/coap/cargo RUSTC_WRAPPER="" DEFMT_LOG=info, CONFIG_ISR_STACKSIZE=16384 cargo  build --release --features=riot-rs-boards/rpi-pico,riot-rs/debug-console,riot-rs/defmt,riot-rs/executor-interrupt,riot-rs/hwrng,riot-rs/random,riot-rs/usb-ethernet && cp ../../build/bin/rpi-pico/coap/cargo/thumbv6m-none-eabi/release/coap ../../build/bin/rpi-pico/coap/coap.elf

This was the failing CI run: https://github.com/future-proof-iot/RIOT-rs/actions/runs/10881859932/job/30192896887?pr=413

A quick (or quack?) duck duck go run did not come up with full solutions. Potential workarounds are setting -fno-builtin-function or another optimization level, but those do not seem to address the root cause. Another avenue to check is whether we're building with GCC rather than clang for some reason -- it'd make sense to use clang given we're later also linking with it (maybe versions mismatch?).


Override all Routes/Maintenance Mode

Would it be possible to create a maintenance mode route that would over write all other routes while enabled?
Including the new route in Index.php would supersede all other routes and return whatever you want. Commenting it out, or removing would restore function of the existing routes.
Thanks for this project! Super simple to use and learn from, especially for newer developers like myself.

Hi,
somethink like this?
if(debug) {
  // Define a single route that matches all requests
  Route::add('/(.*)', function($id) {
    echo 'Edit user with id '.$id.'<br>';
  });
} else {
  // Define all not maintenance routes
  Route::add('/', function() {
    echo 'Welcome :-)';
  });
}

You know what... For some reason, I had it in my head that regular PHP statements wouldn't work... Not sure why. Brain fart.
This worked perfectly. Thank you


fix import from ES Module

The problem was that Node was treating files in dist/esm as CommonJS. The solution would be to rename all files in dist/esm to .mjs or add a package.json with type: module. This PR chooses the second option.
Fixes #80

This does not work. I tried it and it has problems with just-performance:
file:///home/xtreme/Source/private/JsAM/node_modules/limiter/dist/esm/clock.js:1
import { performance } from "just-performance";
         ^^^^^^^^^^^
SyntaxError: Named export 'performance' not found. The requested module 'just-performance' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from 'just-performance';
const { performance } = pkg;

    at ModuleJob._instantiate (node:internal/modules/esm/module_job:128:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:194:5)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:409:24)
    at async loadESM (node:internal/process/esm_loader:85:5)
    at async handleMainPromise (node:internal/modules/run_main:61:12)

Node.js v17.9.0

This does not work. I tried it and it has problems with just-performance:
file:///home/xtreme/Source/private/JsAM/node_modules/limiter/dist/esm/clock.js:1
import { performance } from "just-performance";
         ^^^^^^^^^^^
SyntaxError: Named export 'performance' not found. The requested module 'just-performance' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from 'just-performance';
const { performance } = pkg;

    at ModuleJob._instantiate (node:internal/modules/esm/module_job:128:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:194:5)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:409:24)
    at async loadESM (node:internal/process/esm_loader:85:5)
    at async handleMainPromise (node:internal/modules/run_main:61:12)

Node.js v17.9.0

Also, I tried to import it like it says in the error here in clock.js and then it can't figure out export:
/home/xtreme/Source/private/JsAcMoF/node_modules/just-performance/dist/esm/node.js:1
export { performance } from "perf_hooks";
^^^^^^

SyntaxError: Unexpected token 'export'
    at Object.compileFunction (node:vm:352:18)
    at wrapSafe (node:internal/modules/cjs/loader:1027:15)
    at Module._compile (node:internal/modules/cjs/loader:1063:27)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
    at Module.load (node:internal/modules/cjs/loader:975:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:170:29)
    at ModuleJob.run (node:internal/modules/esm/module_job:198:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:409:24)

This does not work. I tried it and it has problems with just-performance:

Yes, it won't work right now. A similar fix needs to be done for just-performance too. To test it locally, go to node_modules/just-performance/dist/esm add a package.json. Similar to what this PR adds for node-rate-limiter.
package.json
{
  "type": "module"
}

This does not work. I tried it and it has problems with just-performance:

Yes, it won't work right now. A similar fix needs to be done for just-performance too. To test it locally, go to node_modules/just-performance/dist/esm and add a package.json. Similar to what this PR adds for node-rate-limiter.
package.json
{
  "type": "module"
}

I wish I had seen your comment before now. It would have saved me some time... :smiling_face_with_tear:
I raised the corresponding PR: just-performance#4


Fixed array indexing for processing JULES multi-layer snow ensemble.

Description
Fixes array index error when processing ensemble of multi-layer snow from LIS-JULES.
Resolves #804

@emkemp Thanks for finding this bug.  Seems the bug was just a typo from the 0 in the variable name.  I will merge.


TESGroup constructor ignores use_only and never_use lists for pulse-only data sets

Original report by Joseph Fowler (Bitbucket: joe_fowler, ).

Original comment by Joseph Fowler (Bitbucket: joe_fowler, ).

Obey use_only and never_use for pulse-only data
Fixes #255


Attention the coordinates writing

point_a = [-300, -400, 300, -150, -10, 150]
point_b = [-500, -200, 400, -150, -20, 140]
If the coordinates has the point of 600 will get the error.
point_a = [-300, -400, 300, -150, -10, 150]
point_b = [-500, -600, 600, -150, -20, 140]

这个需要跟越疆技术人员沟通，看看是否能够解决问题？

It's successful working in the DOBOT CR Studio with in graphicial program.
It's not work in python program.
# Joint coordinates [x,y,z,rx,ry,rz]
    point_1 = [-176.92, -498.00, 33.44, -178.74, 1.79, -90.69]
    point_2 = [170.53, -432.66, 221.91, -89.28, 30.71, -94.31]
    point_3 = [169.80, -271.54, 65, 176.16, 0.09, -113.83]
    point_4 = [170.96, -432.74, 222.14, -89.17, -42.26, -95.17]
    point_5 = [170.21, -433.72, 223.03, -86.12, -80.95, -98.80]
    point_6 = [170.63, -432.78, 222.12, 89.34, -21.50, 85.31]
    point_7 = [-177.36, -498.42, 64.47, -179.73, 0.20, -90.66]

    while True:
        run_point(move, point_7)
        wait_arrive(point_7)
        run_point(move, point_1)
        wait_arrive(point_1)
        do_gas(dashboard, 2, 1)
        sleep(0.3)
        do_gas(dashboard, 2, 0)
        run_point(move, point_2)
        wait_arrive(point_2)
        run_point(move, point_4)
        wait_arrive(point_4)
        run_point(move, point_5)
        wait_arrive(point_5)
        run_point(move, point_6)
        wait_arrive(point_6)
        run_point(move, point_3)
        wait_arrive(point_3)
        do_gas(dashboard, 1, 1)
        sleep(0.2)
        do_gas(dashboard, 1, 0)

越疆技术人员反馈，使用JointMovJ() 函数去跑坐标；

It's not necessary for operate the BOBOT.
def wait_arrive(point_list):
    global current_actual
    while True:
        is_arrive = True

        if current_actual is not None:
            for index in range(len(current_actual)):
                if (abs(current_actual[index] - point_list[index]) > 1):
                    is_arrive = False

            if is_arrive:
                return

        sleep(0.001)


Xcode complains with 'Modifying state during view update, this will cause undefined behavior.' when using iPhoneNumberField in SwiftUI project

Hello!
Thanks for this awesome library.
I would like to know how the above Warning can be fixed.
XCode highlights the line isFirstResponder.wrappedValue = true inside these two functions:
public func textFieldDidBeginEditing(_ textField: UITextField) {
    isFirstResponder.wrappedValue = true
    onBeginEditing(textField as! PhoneNumberTextField)
}

public func textFieldDidEndEditing(_ textField: UITextField) {
    isFirstResponder.wrappedValue = false
    onEndEditing(textField as! PhoneNumberTextField)
}

As mentioned in the Title, my project is a SwiftUI project.
Any help you can provide will be highly appreciated.
Julio

Ive just seen this too. Were you able to resolve this or did you swap to a different library?

.clearButtonMode(.never)
this should fix your issue

Not working friend..

You should no longer see this warning on version 0.10.1


Validate name space not empty compiler

to fix #146

@oritstone will you merge this after short review?

@einatneu does this solves your issue ?

@meirwah - I need it to be in the precompile also

added @einatneu ... check now...

@meirwah - looks good, thanks!


Add an additional arg to manager.shell --silent in keymap.toml config file

Please describe the problem you're trying to solve
By adding this feature we can run a specific shell command silently without showing up the template input.
Would you be willing to contribute this feature?

[ ] Yes, I'll give it a shot

Describe the solution you'd like
Maybe showing up the input will add more flexibility for example attach a variable name to the input then use that variable inside the shell command .
In a real world example where compressing file(s) :
select file(s) -> pressing a key -> pop-up the input box -> set the extension (ex:7z,zip,...) -> press enter -> the shell receive the extension name and append it to the command and run it .
Additional context
No response

shell --confirm is what you're looking for, see docs here https://yazi-rs.github.io/docs/configuration/keymap/#manager.shell
Closing as already exists

I tried it but kept showing up the input field!, If so,maybe it's a bug.
thanks for your great project, I'm using it as alternative to many file managers (ex: ranger, broot,...) I already set this to @sxyazi run on startup terminal as a drop-in-replacement to GUI applications in with daily usage.

How do you use it? Could you paste your config here please? Also what's your Yazi version?

@sxyazi sorry for the delay, I checked my configs this weekend and I found the root issue.
I'm using different Terminals for different purpose and one of my terminals (WezTerm) used mainly with Yazi after switching from xplr , When I migrated my configs, folders,...etc I didn't update the shell to the new locations , and Yazi works well without crashes even by keeping she wrong locations EXCEPT it doesn't load the custom (pluggins & configs).
Note: Yazi output the issue by saying the folder doesn't exist however that time I kept work as fine for most my use cases which make me ignore the warring output.
Thanks again for your amazing program.


add support for tablegen

Great.
I really hope this gets merged into the main branch soon. I'm eager to start using this feature!


Update ScintillaNET

The version of ScintillaNET is from 2012 and is no longer maintained (see http://scintillanet.codeplex.com/).
Updating to the maintained version seems like a good idea since it's stable and supported, but there are some API changes so it's not a drop-in replacement.

This is also important to get proper Unicode support - at the moment any unicode text in shader files will cause highlighting to break as byte offsets no longer equal character offsets.

Closing this - at this point the .NET UI is basically deprecated, and we're using Scintilla directly without a wrapper in qrenderdoc.


Unable to install templates (Xcode 6.3)

I have  a bizzarre problem. I'm not able to install any package under "Templates" section.
Color schemes and plug-ins are installing without any issues, but as soon as I tap "Install" on a template it quickly goes about 1/3 of the way and than rolls back.
I read other threads with similar issues suggesting I might have outdated version of git or my Xcode is set to a wrong command line compiler.. None of this is my case. I have just one version of Xcode installed (6.3 release from Appstore) and my git version is 2.3.5. Btw the same happened to me with Xcode 6.2.
My guess is templates might be installed differently than plugins and Alcatraz probably don't have some rights on a certain folder where they might go. How can I verify that? And are there any ways (apart from re-installing Xcode) to remedy this?
Another issue I'm having (and this might be related to the proper rights issue) is that some of the plugins I install may or may not appear as custom menu items. Sometimes they are just there when I launch Xcode (as intended) and sometimes they are not...
Any help is appreciated

Could it be that those plugins simply don't support 6.3 yet?

@jurre I don't think so. As I mentioned in my original post the same issues appeared in Xcode 6.2
As for the templates - are they installed in the same folders as all the other plugins? E.g  ~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/ ?

No there's a completely separate install process for those

Ok, I got it to work.
It seems that my original suspicions about the folder permission were the origin of the issue.
Unlike with other folders my current user didn't have write permissions on the folders where Templates should go. Those are:
~Library/Developer/Xcode/Templates/
~Library/Developer/Xcode/Templates/File Templates/
By adding myself with read/write permissions on these folders resolved the issue.

:+1: :+1:


Incorrect Output Size Metrics in Spark UI

In the Spark UI for Job 2, the output size is displayed incorrectly. The UI indicates an output size of 2.4 PiB, while the actual size should be approximately 1 TB. This discrepancy can lead to confusion and incorrect resource planning.

It was fixed for static tables. Dynamic tables require extra features from java client.
Will be available in the next release.


dgen: init at 1.33

Motivation for this change
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/402

Result of nixpkgs-review pr 106359 run on x86_64-linux 1

1 package failed to build:

dgen-sdl


Partial Mode generating unexpected keys

After upgrading from version 0.7.1 to version 0.8.0, after some struggle spotting from where did my error come from, I found out that the partial mode wasn't working as expected.
How to replicate the bug:

Upgrade the package
pip install jiter==0.8.0

Get a partial and incomplete JSON and try to parse it using jiter:

>>> from jiter import from_json
>>> from_json(b'{\n "mykeyname": "hello there", \n', partial_mode=True)
{'__builtim': 'ÈîPÙªª\x00\x00hel'}

After downgrading to version 0.7.1:
>>> from jiter import from_json
>>> from_json(b'{\n "mykeyname": "hello there", \n', partial_mode=True)
{'mykeyname': 'hello there'}

System information:
Python 3.12.7 (main, Oct 29 2024, 14:29:28) [GCC 11.4.0] on linux

Thanks for the report. Looks potentially serious, x86_64 architecture?

After a quick check on both macOS and linux, I cannot reproduce this. Are you able to share any more information

Ah, I can reproduce using aarch64 builds. macOS host running the arm docker image:
$ docker run -it python:3.12 /bin/sh
# python
Python 3.12.7 (main, Nov 13 2024, 15:07:43) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
# pip install jiter
Collecting jiter
  Downloading jiter-0.8.0-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (5.2 kB)
Downloading jiter-0.8.0-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (333 kB)
Installing collected packages: jiter
Successfully installed jiter-0.8.0
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.

[notice] A new release of pip is available: 24.2 -> 24.3.1
[notice] To update, run: pip install --upgrade pip
# python
Python 3.12.7 (main, Nov 13 2024, 15:07:43) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import jiter
>>> jiter.from_json(b'{\n "mykeyname": "hello there", \n', partial_mode=True)
{'__builtim': '8 \x1béªª\x00\x00hel'}

... but I'm now struggling to reproduce from a locally-built jiter on the same docker image. 😖

Fixed in #175, will release 0.8.1 asap


chore: rename max_raw_class_size to max_contract_class_object_size

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#355  👈
#354
#284
#283 : 1 other dependent PR (#318 )
#250
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @ArniStarkware and the rest of your teammates on  Graphite