init_record hangs on ubuntu16 with custom socket or pid_file

Cookbook version
7.2.0
Chef-client version
12.9.41
with kitchen, vagrant and chef_solo
Platform Details
Happens on fresh provisioning of
Ubuntu 16.04
The issue is not present on Ubuntu 14.04
Scenario:
[What you are trying to achieve and you can't?]
Creating and starting of mysql_service
Steps to Reproduce:
[If you are filing an issue what are the things we need to do in order to repro your problem? How are you using this cookbook or any resources it includes?]
include_recipe 'apt'

mysql_service 'default' do
  instance 'default'
  bind_address <IP_ADDRESS>
  port 3306
  initial_root_password '' # password will be set in another resource. Use empty password to override the default
  version node['mysql']['version']
  error_log '/var/log/mysql/error.log'
  pid_file '/run/mysql-foo/mysqld.pid'
  socket '/run/mysql-foo/mysqld.sock'
  action [:create, :start, :restart]
end

Expected Result:
mysql-default service successfully installed and running, with the custom socket and pid_file
Actual Result:
The provisiong hangs on execution of the init_records_script ( https://github.com/chef-cookbooks/mysql/blob/v7.2.0/libraries/helpers.rb#L163 )
init_script
root@default-ubuntu-1604:/tmp# cat mysql-default/my.sql
UPDATE mysql.user SET authentication_string=PASSWORD(''), password_expired='N' WHERE user = 'root';
DELETE FROM mysql.user WHERE USER LIKE '';
DELETE FROM mysql.user WHERE user = 'root' and host NOT IN ('<IP_ADDRESS>', 'localhost');
FLUSH PRIVILEGES;
DELETE FROM mysql.db WHERE db LIKE 'test%';
DROP DATABASE IF EXISTS test ;

MySQL error log
cat /var/log/mysql/error.log
2016-08-30T14:50:30.668362Z 1 [Note] A temporary password is generated for root@localhost: ,(AafC_kp3/e
2016-08-30T14:50:33.776263Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.13-0ubuntu<IP_ADDRESS>) starting as process 5384 ...
2016-08-30T14:50:33.782260Z 0 [Note] InnoDB: PUNCH HOLE support available
2016-08-30T14:50:33.782302Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-08-30T14:50:33.782311Z 0 [Note] InnoDB: Uses event mutexes
2016-08-30T14:50:33.782318Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2016-08-30T14:50:33.782324Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-08-30T14:50:33.782331Z 0 [Note] InnoDB: Using Linux native AIO
2016-08-30T14:50:33.782593Z 0 [Note] InnoDB: Number of pools: 1
2016-08-30T14:50:33.782698Z 0 [Note] InnoDB: Using CPU crc32 instructions
2016-08-30T14:50:33.785757Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2016-08-30T14:50:33.800484Z 0 [Note] InnoDB: Completed initialization of buffer pool
2016-08-30T14:50:33.805271Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2016-08-30T14:50:33.821598Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2016-08-30T14:50:33.835440Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2016-08-30T14:50:33.835521Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2016-08-30T14:50:33.872521Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2016-08-30T14:50:33.873377Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2016-08-30T14:50:33.873395Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2016-08-30T14:50:33.875403Z 0 [Note] InnoDB: Waiting for purge to start
2016-08-30T14:50:33.933178Z 0 [Note] InnoDB: 5.7.13 started; log sequence number 2523957
2016-08-30T14:50:33.937459Z 0 [Note] Plugin 'FEDERATED' is disabled.
2016-08-30T14:50:33.937564Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql-default/ib_buffer_pool
2016-08-30T14:50:33.941937Z 0 [Note] InnoDB: Buffer pool(s) load completed at 160830 14:50:33
2016-08-30T14:50:33.944745Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
2016-08-30T14:50:33.944775Z 0 [Note] Server hostname (bind-address): '<IP_ADDRESS>'; port: 3306
2016-08-30T14:50:33.944888Z 0 [Note]   - '<IP_ADDRESS>' resolves to '<IP_ADDRESS>';
2016-08-30T14:50:33.944925Z 0 [Note] Server socket created on IP: '<IP_ADDRESS>'.
2016-08-30T14:50:33.945028Z 0 [ERROR] /usr/sbin/mysqld: Can't create/write to file '/run/mysql-foo/mysqld.pid' (Errcode: 2 - No such file or directory)
2016-08-30T14:50:33.945041Z 0 [ERROR] Can't start server: can't create PID file: No such file or directory

Example chef debug output:
(only with pid_file set, but it it's the same with socket)
           * directory[default :create /etc/mysql-default] action create[2016-08-30T14:35:00+00:00] INFO: Processing directory[default :create /etc/mysql-default] action create (/tmp/kitchen/cookbooks/mysql/libraries/provider_mysql_service_base.rb line 91)
       [2016-08-30T14:35:00+00:00] DEBUG: Providers for generic directory resource enabled on node include: [Chef::Provider::Directory]
       [2016-08-30T14:35:00+00:00] DEBUG: Provider for action create on resource directory[default :create /etc/mysql-default] is Chef::Provider::Directory
       [2016-08-30T14:35:00+00:00] INFO: directory[default :create /etc/mysql-default] created directory /etc/mysql-default

             - create new directory /etc/mysql-default[2016-08-30T14:35:00+00:00] DEBUG: Found current_mode == nil, so we are creating a new file, updating mode
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_mode == nil, so we are creating a new file, updating mode
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_uid == nil, so we are creating a new file, updating owner
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_gid == nil, so we are creating a new file, updating group
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_uid == nil, so we are creating a new file, updating owner
       [2016-08-30T14:35:00+00:00] INFO: directory[default :create /etc/mysql-default] owner changed to 110
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_gid == nil, so we are creating a new file, updating group
       [2016-08-30T14:35:00+00:00] INFO: directory[default :create /etc/mysql-default] group changed to 116
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_mode == nil, so we are creating a new file, updating mode
       [2016-08-30T14:35:00+00:00] INFO: directory[default :create /etc/mysql-default] mode changed to 750

             - change mode from '' to '0750'
             - change owner from '' to 'mysql'
             - change group from '' to 'mysql'[2016-08-30T14:35:00+00:00] DEBUG: selinux utilities can not be found. Skipping selinux permission fixup.

           * directory[default :create /etc/mysql-default/conf.d] action create[2016-08-30T14:35:00+00:00] INFO: Processing directory[default :create /etc/mysql-default/conf.d] action create (/tmp/kitchen/cookbooks/mysql/libraries/provider_mysql_service_base.rb line 100)
       [2016-08-30T14:35:00+00:00] DEBUG: Providers for generic directory resource enabled on node include: [Chef::Provider::Directory]
       [2016-08-30T14:35:00+00:00] DEBUG: Provider for action create on resource directory[default :create /etc/mysql-default/conf.d] is Chef::Provider::Directory
       [2016-08-30T14:35:00+00:00] INFO: directory[default :create /etc/mysql-default/conf.d] created directory /etc/mysql-default/conf.d

             - create new directory /etc/mysql-default/conf.d[2016-08-30T14:35:00+00:00] DEBUG: Found current_mode == nil, so we are creating a new file, updating mode
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_mode == nil, so we are creating a new file, updating mode
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_uid == nil, so we are creating a new file, updating owner
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_gid == nil, so we are creating a new file, updating group
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_uid == nil, so we are creating a new file, updating owner
       [2016-08-30T14:35:00+00:00] INFO: directory[default :create /etc/mysql-default/conf.d] owner changed to 110
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_gid == nil, so we are creating a new file, updating group
       [2016-08-30T14:35:00+00:00] INFO: directory[default :create /etc/mysql-default/conf.d] group changed to 116
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_mode == nil, so we are creating a new file, updating mode
       [2016-08-30T14:35:00+00:00] INFO: directory[default :create /etc/mysql-default/conf.d] mode changed to 750

             - change mode from '' to '0750'
             - change owner from '' to 'mysql'
             - change group from '' to 'mysql'[2016-08-30T14:35:00+00:00] DEBUG: selinux utilities can not be found. Skipping selinux permission fixup.

           * directory[default :create /run/mysql-default] action create[2016-08-30T14:35:00+00:00] INFO: Processing directory[default :create /run/mysql-default] action create (/tmp/kitchen/cookbooks/mysql/libraries/provider_mysql_service_base.rb line 109)
       [2016-08-30T14:35:00+00:00] DEBUG: Providers for generic directory resource enabled on node include: [Chef::Provider::Directory]
       [2016-08-30T14:35:00+00:00] DEBUG: Provider for action create on resource directory[default :create /run/mysql-default] is Chef::Provider::Directory
       [2016-08-30T14:35:00+00:00] INFO: directory[default :create /run/mysql-default] created directory /run/mysql-default

             - create new directory /run/mysql-default[2016-08-30T14:35:00+00:00] DEBUG: Found current_mode == nil, so we are creating a new file, updating mode
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_mode == nil, so we are creating a new file, updating mode
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_uid == nil, so we are creating a new file, updating owner
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_gid == nil, so we are creating a new file, updating group
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_uid == nil, so we are creating a new file, updating owner
       [2016-08-30T14:35:00+00:00] INFO: directory[default :create /run/mysql-default] owner changed to 110
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_gid == nil, so we are creating a new file, updating group
       [2016-08-30T14:35:00+00:00] INFO: directory[default :create /run/mysql-default] group changed to 116
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_mode == nil, so we are creating a new file, updating mode
       [2016-08-30T14:35:00+00:00] INFO: directory[default :create /run/mysql-default] mode changed to 755

             - change mode from '' to '0755'
             - change owner from '' to 'mysql'
             - change group from '' to 'mysql'[2016-08-30T14:35:00+00:00] DEBUG: selinux utilities can not be found. Skipping selinux permission fixup.

           * directory[default :create /var/log/mysql-default] action create[2016-08-30T14:35:00+00:00] INFO: Processing directory[default :create /var/log/mysql-default] action create (/tmp/kitchen/cookbooks/mysql/libraries/provider_mysql_service_base.rb line 118)
       [2016-08-30T14:35:00+00:00] DEBUG: Providers for generic directory resource enabled on node include: [Chef::Provider::Directory]
       [2016-08-30T14:35:00+00:00] DEBUG: Provider for action create on resource directory[default :create /var/log/mysql-default] is Chef::Provider::Directory
       [2016-08-30T14:35:00+00:00] INFO: directory[default :create /var/log/mysql-default] created directory /var/log/mysql-default

             - create new directory /var/log/mysql-default[2016-08-30T14:35:00+00:00] DEBUG: Found current_mode == nil, so we are creating a new file, updating mode
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_mode == nil, so we are creating a new file, updating mode
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_uid == nil, so we are creating a new file, updating owner
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_gid == nil, so we are creating a new file, updating group
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_uid == nil, so we are creating a new file, updating owner
       [2016-08-30T14:35:00+00:00] INFO: directory[default :create /var/log/mysql-default] owner changed to 110
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_gid == nil, so we are creating a new file, updating group
       [2016-08-30T14:35:00+00:00] INFO: directory[default :create /var/log/mysql-default] group changed to 116
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_mode == nil, so we are creating a new file, updating mode
       [2016-08-30T14:35:00+00:00] INFO: directory[default :create /var/log/mysql-default] mode changed to 750

             - change mode from '' to '0750'
             - change owner from '' to 'mysql'
             - change group from '' to 'mysql'[2016-08-30T14:35:00+00:00] DEBUG: selinux utilities can not be found. Skipping selinux permission fixup.

           * directory[default :create /var/lib/mysql-default] action create[2016-08-30T14:35:00+00:00] INFO: Processing directory[default :create /var/lib/mysql-default] action create (/tmp/kitchen/cookbooks/mysql/libraries/provider_mysql_service_base.rb line 127)
       [2016-08-30T14:35:00+00:00] DEBUG: Providers for generic directory resource enabled on node include: [Chef::Provider::Directory]
       [2016-08-30T14:35:00+00:00] DEBUG: Provider for action create on resource directory[default :create /var/lib/mysql-default] is Chef::Provider::Directory
       [2016-08-30T14:35:00+00:00] INFO: directory[default :create /var/lib/mysql-default] created directory /var/lib/mysql-default

             - create new directory /var/lib/mysql-default[2016-08-30T14:35:00+00:00] DEBUG: Found current_mode == nil, so we are creating a new file, updating mode
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_mode == nil, so we are creating a new file, updating mode
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_uid == nil, so we are creating a new file, updating owner
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_gid == nil, so we are creating a new file, updating group
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_uid == nil, so we are creating a new file, updating owner
       [2016-08-30T14:35:00+00:00] INFO: directory[default :create /var/lib/mysql-default] owner changed to 110
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_gid == nil, so we are creating a new file, updating group
       [2016-08-30T14:35:00+00:00] INFO: directory[default :create /var/lib/mysql-default] group changed to 116
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_mode == nil, so we are creating a new file, updating mode
       [2016-08-30T14:35:00+00:00] INFO: directory[default :create /var/lib/mysql-default] mode changed to 750

             - change mode from '' to '0750'
             - change owner from '' to 'mysql'
             - change group from '' to 'mysql'[2016-08-30T14:35:00+00:00] DEBUG: selinux utilities can not be found. Skipping selinux permission fixup.

           * template[default :create /etc/mysql-default/my.cnf] action create[2016-08-30T14:35:00+00:00] INFO: Processing template[default :create /etc/mysql-default/my.cnf] action create (/tmp/kitchen/cookbooks/mysql/libraries/provider_mysql_service_base.rb line 137)
       [2016-08-30T14:35:00+00:00] DEBUG: Providers for generic template resource enabled on node include: [Chef::Provider::Template]
       [2016-08-30T14:35:00+00:00] DEBUG: Provider for action create on resource template[default :create /etc/mysql-default/my.cnf] is Chef::Provider::Template
       [2016-08-30T14:35:00+00:00] DEBUG: Touching /etc/mysql-default/my.cnf to create it
       [2016-08-30T14:35:00+00:00] INFO: template[default :create /etc/mysql-default/my.cnf] created file /etc/mysql-default/my.cnf

             - create new file /etc/mysql-default/my.cnf[2016-08-30T14:35:00+00:00] DEBUG: calculating checksum of /etc/mysql-default/.chef-my.cnf20160830-2318-1kc9vzm to compare with
       [2016-08-30T14:35:00+00:00] DEBUG: Running: diff -u /etc/mysql-default/my.cnf /etc/mysql-default/.chef-my.cnf20160830-2318-1kc9vzm
       [2016-08-30T14:35:00+00:00] DEBUG: Reading modes from /etc/mysql-default/my.cnf file
       [2016-08-30T14:35:00+00:00] DEBUG: Applying mode = 644, uid = 0, gid = 0 to /etc/mysql-default/.chef-my.cnf20160830-2318-1kc9vzm
       [2016-08-30T14:35:00+00:00] DEBUG: Moving temporary file /etc/mysql-default/.chef-my.cnf20160830-2318-1kc9vzm into place at /etc/mysql-default/my.cnf
       [2016-08-30T14:35:00+00:00] INFO: template[default :create /etc/mysql-default/my.cnf] updated file contents /etc/mysql-default/my.cnf

             - update content in file /etc/mysql-default/my.cnf from none to 513034
             --- /etc/mysql-default/my.cnf  2016-08-30 14:35:00.591276077 +0000
             +++ /etc/mysql-default/.chef-my.cnf20160830-2318-1kc9vzm   2016-08-30 14:35:00.591276077 +0000
             @@ -1 +1,24 @@
             +# Chef generated my.cnf for instance mysql-default
             +
             +[client]
             +default-character-set          = utf8
             +port                           = 3306
             +socket                         = /run/mysql-default/mysqld.sock
             +
             +[mysql]
             +default-character-set          = utf8
             +
             +[mysqld]
             +user                           = mysql
             +pid-file                       = /run/mysql-foo/mysqld.pid
             +socket                         = /run/mysql-default/mysqld.sock
             +bind-address                   = <IP_ADDRESS>
             +port                           = 3306
             +datadir                        = /var/lib/mysql-default
             +tmpdir                         = /tmp
             +log-error                      = /var/log/mysql/error.log
             +!includedir /etc/mysql-default/conf.d
             +
             +[mysqld_safe]
             +socket                         = /run/mysql-default/mysqld.sock[2016-08-30T14:35:00+00:00] DEBUG: Found current_mode == nil, so we are creating a new file, updating mode
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_mode == nil, so we are creating a new file, updating mode
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_uid == nil, so we are creating a new file, updating owner
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_gid == nil, so we are creating a new file, updating group
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_uid == nil, so we are creating a new file, updating owner
       [2016-08-30T14:35:00+00:00] INFO: template[default :create /etc/mysql-default/my.cnf] owner changed to 110
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_gid == nil, so we are creating a new file, updating group
       [2016-08-30T14:35:00+00:00] INFO: template[default :create /etc/mysql-default/my.cnf] group changed to 116
       [2016-08-30T14:35:00+00:00] DEBUG: Found current_mode == nil, so we are creating a new file, updating mode
       [2016-08-30T14:35:00+00:00] INFO: template[default :create /etc/mysql-default/my.cnf] mode changed to 600

             - change mode from '' to '0600'
             - change owner from '' to 'mysql'
             - change group from '' to 'mysql'[2016-08-30T14:35:00+00:00] DEBUG: selinux utilities can not be found. Skipping selinux permission fixup.

           * bash[default :create initial records] action run[2016-08-30T14:35:00+00:00] INFO: Processing bash[default :create initial records] action run (/tmp/kitchen/cookbooks/mysql/libraries/provider_mysql_service_base.rb line 158)
       [2016-08-30T14:35:00+00:00] DEBUG: Providers for generic bash resource enabled on node include: [Chef::Provider::Script]
       [2016-08-30T14:35:00+00:00] DEBUG: Provider for action run on resource bash[default :create initial records] is Chef::Provider::Script

If you look at your service settings you have it as default so is going to create the mysql-default directory. This shown in the my.cnf for instance mysql-default.
Your pid file isn't being created because the mysql-foo directory doesn't exist if you aren't creating the directory as evident in the logfile
2016-08-30T14:50:33.945028Z 0 [ERROR] /usr/sbin/mysqld: Can't create/write to file '/run/mysql-foo/mysqld.pid' (Errcode: 2 - No such file or directory)

The above assessment seems on point and with the substantial changes to the cookbook since then I'm closing this one but feel free to open new ones if issues present themselves.


AttributeError: 'Tensor' object has no attribute 'dtpye'

models\SCINet.py", line 355, in forward output = torch.zeros(x.shape,dtype=x.dtpye).cuda()
dtype=x.dtype

Sorry, this is a typo, please change the x.dtpye as x.dtype.
We have fixed the typo in this file.
Thanks for your attention.

Sorry, this is a typo, please change the x.dtpye as x.dtype.
We have fixed the typo in this file.
Thanks for your attention.


Add how-to on retrieving jobs

What is the expected feature or enhancement?
At one point there was documentation on how to retrieve a previously submitted job, its results and parameters used. I can't seem to find that anywhere now.
Acceptance criteria
Add a Retrieve a previous job section under How to that explains how to retrieve a previously submitted job, its results and parameters used.

Apparently there is doc on this already, but it's buried inside "Run a session" for some reason.

I spoke to @jyu00 and she said we can just pull out that information into a separate topic.


Print the Droplet ID after create

Saves having to do a fuzzy search afterward
Updates spec with new output

Coverage remained the same at 98.0% when pulling f69a7881c5a52291fd80f84f7e6b8bda9962d994 on lachesis-id into d9e98b1165b9e51ccaf58f64d690e331dc67bcad on master.

Coverage remained the same at 98.0% when pulling f69a7881c5a52291fd80f84f7e6b8bda9962d994 on lachesis-id into d9e98b1165b9e51ccaf58f64d690e331dc67bcad on master.

Coverage remained the same at 98.0% when pulling f69a7881c5a52291fd80f84f7e6b8bda9962d994 on lachesis-id into d9e98b1165b9e51ccaf58f64d690e331dc67bcad on master.

Closes #265


feat: add integration with AsyncAPI Server API

Description
Add integration with AsyncAPI Server API (#86):

generate only html-template and markdown-template

TODO:

[ ] create repo and initial PR for #86
[ ] add possibility to pass (by form) template parameters

Related issue(s)
Part of #80 #86

Handling it in the https://github.com/asyncapi/studio/pull/229


COMException Class not registered when initializing CollectionViewSource

Describe the bug
The following exception occurs when initializing a CollectionViewSource instance from a MsTest execution:
System.Reflection.TargetInvocationException
HResult=0x80131604
Message=Exception has been thrown by the target of an invocation.
Source=System.Private.CoreLib
StackTrace:
at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean wrapExceptions, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& hasNoDefaultCtor)
at System.RuntimeType.CreateInstanceDefaultCtorSlow(Boolean publicOnly, Boolean wrapExceptions, Boolean fillCache)
at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, Boolean wrapExceptions)
at System.Activator.CreateInstanceT
at WinRT.WeakLazy1.get_Value()    at WinRT.ActivationFactory1.ActivateInstanceI
at Microsoft.UI.Xaml.Data.CollectionViewSource..ctor()
at Example.ExampleVm..ctor() in C:\Users\Terry Cox\Documents\Projects\Tests and Spikes\Example\Example\Example\ExampleVm.cs:line 36
at ExampleTest.UnitTest1.TestMethod1() in C:\Users\Terry Cox\Documents\Projects\Tests and Spikes\Example\ExampleTest\UnitTest1.cs:line 12
This exception was originally thrown at this call stack:
[External Code]
Inner Exception 1:
COMException: Class not registered (0x80040154 (REGDB_E_CLASSNOTREG))
The CollectionViewSource constructor executes properly from the Win32 Windows Application project rather than from the MsTest. The evident difference is that the CollectionViewSource constructor is invoked via reflection from the test session.
Steps to reproduce the bug:
Extract the attached Example.zip file. It contains an application created from the C# Blank App, Packaged (WinUI 3 in Desktop) Visual Studio template for Project Reunion 0.8.0-preview. An MsTest project was added to the solution using the Unit Test Project (.NET Core) template. Both the desktop app and the MsTest project were modified as shown in the code. To demonstrate the problem, build the solution and:

Set ExampleTest as the Startup Project and run or debug all tests. The test will fail with the above exception.
Set Example (Package) as the Startup Project and run or debug the app. The application will execute without an exception.
Comment out line 36 in file ExampleVm.cs ]colorSource = new CollectionViewSource();]
Set ExampleTest as the Startup Project and run or debug all tests. The test will run without issue.

Version Info

NuGet package version:
Microsoft.ProjectReunion 0.8.0-preview
Microsoft.ProjectReunion.WinUI 0.8.0-preview
coverlet.collector 1.3.0
Microsoft.NET.Test.Sdk 16.7.1
MSTest.TestAdapter 2.1.1
MSTest.TestFramework 2.1.1

Edition	Windows 10 Pro
Version	21H1
Installed on	4/17/2021
OS build	19043.1023
Experience	Windows Feature Experience Pack 120.2212.2020.0

Here's a better Example.zip (with .obj and .bin folders removed).
Example.zip

Thanks for filing this! Transferring to the WinUI XAML team to investigate.


[v1.8] chore: Update argocd-operator to fix sso test failure

What type of PR is this?
/kind bug
What does this PR do / why we need it:
Backport #529 into v1.8. This PR updates argocd-operator commit to include the fix added in https://github.com/argoproj-labs/argocd-operator/pull/932.
Which issue(s) this PR fixes:
Fixes GITOPS-2929

/test v4.12-kuttl-parallel

/retest

/lgtm
/approve


Info for Developer in Log

In ioBroker Log i found this Information:
tado.0 | 2020-08-05 07:20:40.674 | error | (2298) Send this info to developer !!! { Unhandable information found in DoHome : "legacyHeatingInstallationsEnabled" with value : true
-- | -- | -- | --

Versions:

Adapter version: 0.1.9
JS-Controller version: 3.1.6
Node version: 10.22.0
Operating system: Linux Ubuntu 18.04 LTS

double entry to https://github.com/iobroker-community-adapters/ioBroker.tado/issues/32


Backend pieces of auto-update enable/disable

This updates Brackets for the API changes necessary for https://github.com/mozilla/thimble.mozilla.org/issues/1417.
There are 2 types of "reloads" that we do.  The first is a full reload for cases where the DOM needs to be altered in a way that can't be done easily, which is like refreshing the browser tab.  The second is a dynamic injection of content that doesn't warrant a full reload.  For example, updating the text in a paragraph tag.
This patch makes it possible to stop the first kind of reload, which is what I think we want.  If we decide that we also want to stop the second type, it's going to be hacky.  I would need to inspect messages going over the LiveDev transport, and look for things like "_LD.applyDOMEdits([{"type":"textReplace"... deep inside the string of a Runtime.evaluate message.  I could do this, but if I don't have to, I'd rather not.
cc @flukeout
r? @gideonthomas

It looks like if I want to do 2), I could also try to prevent it at the source, which is https://github.com/mozilla/brackets/blob/master/src/LiveDevelopment/MultiBrowserImpl/documents/LiveHTMLDocument.js#L212-L229, specifically line 221.  I'd just need to wrap this in a guard that can be enabled/disabled via the Bramble client.

One thing to consider here: our highlighting code depends on the DOM being a) up-to-date such that b) DOM nodes referenced in the editor actually exist in the preview.  If the editor and preview are allowed to drift out of sync dramatically, the highlighting code is going to get more and more unusable, as new additions to the editor cease to appear in the preview.

I don't think we should support the second case. From what I understand, the issue was that it was annoying that the preview was flickering because of a full refresh (the first case). So allowing a toggle on that should be fine. Toggling live dev based on LiveDocuments might be overkill. I think we we make it clear in the UI that should be fine.
As for the highlighting code, we can force a reload (which should sync DOM elements) when it is toggled, can't we?

The patch itself lgtm! r+

Okay, I'm going to start work on a companion PR in Thimble to match this effort. Will holler if I run into problems.

@flukeout I'm going to land this.  If we decide to change the disabled state to also block dynamic injection, we can do it in a new patch.  I think that @gideonthomas is right, we probably don't want it.

@humphd okay perfect, PR incoming for the toggle later today


Forbid underscore as first character in identifiers

Currenlty there is no restriction on underscores in identifiers. This should be validated and constrained to allow for generated code to use leading underscores and multiple consecutive underscores as a way to guarantee non-clashing names in generated code.
For example, if the compiler generates the identifier baz in package foo/bar as __foo_bar__baz, where double underscores are used before and after the package name segments, the user couldn't create a clashing identifier.
Also, in the future the identifier _ should be treated as a wildcard in bindings and patterns, e.g.
let _ = just_do_it().

Another, perhaps better way for the user, would be to just remove all underscores from identifiers during compilation, and only letting the compiler use them. On the other hand, that would make debugging slightly more cumbersome.


Domain update bug fixes.

Recently, we decided to move from moo.io to ryos.io so we need to update package names, documentation as well as references immediately.

Fixed with the 0.1.5


Improve Oculus SDK controller detection

Replace OVRInput.GetActiveController with GetConnectedControllers
for earlier and more reliable controller type detection.
GetActiveController only reports the type of the single controller
whose inputs are being processed right now, whereas
GetConnectedControllers reports the overall controller scheme type
as soon as the SDK has connected to them.
Fixes #1712 (more discussion and justification in that thread)

There were the following issues with your Pull Request

Commit: 77f8b7f2e10fd34df9d8320300f57d02c9f59b03
Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/thestonefox/SteamVR_Unity_Toolkit

This message was auto-generated by https://gitcop.com

Fixed in https://github.com/thestonefox/VRTK/pull/1739


Tree column titles have weird sizes across the editor

Godot version
18bd0fee5a8aa360177cbe14a16d6be69f088d8f
System information
N/A
Issue description
Across various areas of the editor, Tree items that have visible column names have very weird spacing, often resulting in cutoff strings:

They also seem to ignore the right border:

I'm almost certain that is related to this PR: #49917
CC @groud Never mind, it caused by #50146, CC @reduz
Steps to reproduce
Just search for Tree elements with visible column names.
Minimal reproduction project
No response

See also: #50657

Duplicate of #52891.


Svelte-Scoped & Dynamic Class limitations (safelist)

UnoCSS version
0.53.1
Describe the bug
It seems the dynamic CSS generation is currently having issues and I'm not aware of any workaround according to the docs.
Safelist approach is having a bug (see point 2 mentioned below)
The reproductions link shows the following:
1.) Fixed result possibilities (without layout change)
The two layouts that should be achieved.
2.) Dynamic class / Safelist approach
(Safelist must be reenabled in the example. This caused issues with the other styles when enabled -> Bug)
3.) Class attribute approach
(This is causing issues when having something like "sm:basis-1/2" which will not work.)
Reproduction
https://stackblitz.com/edit/unocss-unocss-w4tud7
System Info
No response
Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

You can accomplish what you'd like by using a class expression with % instead of a fraction, class:sm:basis-50%={!grid} as seen in https://stackblitz.com/edit/unocss-unocss-pqv7fv?file=src%2Froutes%2F%2Bpage.svelte Compare https://unocss.dev/interactive/?s=sm:basis-1/2 with https://unocss.dev/interactive/?s=sm:basis-50%.
And yes, as you pointed out the safelist approach is prone to quirks if you are not aware of the ordering situation. Safelist classes come first, followed by component scoped classes. I think you'll find that class expressions solve all of the use cases shown in your repro.

I wanted to add also that your syntax is not supported:
class={`grid grid-cols-1 ${gridClasses} gap-4`}

That sort of thing would be written as class="grid grid-cols-1 {gridClasses} gap-4". See supported syntax. String interpolation is not needed inside the template html and makes Svelte harder to read.

All right, thanks for the explanation


Vue3 + Vite example ?

Is your feature request related to a problem?
[X] Root Config [X] Micro-frontend/parcel
Describe the solution you'd like
Is it possible to have a little example with a small micro-frontend project and root project from vite and vue3?
Describe alternatives you've considered
I tried to reproduce what you'd achieve with https://github.com/webJose/single-spa-and-svelte but with a vue3 project.
It works on dev mode (microfrontend as dev, and root as dev), but it doesn't works on preview. The components are loaded but the CSS is not displayed. I have no CSS files, only

Yes, I used an import map named my-app (forgot to include on my previous comment), which links to : http://localhost:5173/spa.js
root is on 5174 and spa is on 5173
I will take time to perform a public repo and share the code, thanks!

A complete example of Vite + single-spa + web component would be very helpful to me. Otherwise, great job.

Hello, @lencys.  This GitHub has Discussions open, if you would like to start one.
As for web components, I don't do them, but if you would like to contribute with an example, it would be welcome.
Cheers.

Hello, @quentin-desbin.  Any updates?  If you can, let me know so I can close the issue.  Thanks!

I didn't get the time to re-test and create a public repo (it was tested on my enterprise repo), maybe you can close and when I will get time I can reopen with a link ;) ?

Apologies for rehashing this thread, but I have a very similar setup. Vue3 root app and Vue3 mife, both with Vite of course.
I managed to get the two working with some minor issues here and there related to CSS and especially routing when trying to navigate to a separate mife (it's as if the active mife's router takes precedence. I might have workarounds for these, but have a bigger issue at hand while still testing whether this is a viable solution.
In my root app, I'm passing customProps in my main.ts file:
registerApplication({
    name: 'paymentGate',
    app: () => import(/* @vite-ignore */ paymentGateoModule),
    activeWhen: '/payment-gate/',
    customProps: {some: 'value'}
})

I can't quite figure out how to get those props in the mife. My spa.ts looks like this:
const lc = singleSpaVue({
    createApp,
    appOptions: {
        render() {
            return h(App, {
                props: {
                    name: 'paymentGate'
                    // mountParcel: this.mountParcel,
                    // singleSpa: this.singleSpa
                }
            })
        }
    },
    handleInstance: (app) => {
        registerPlugins(app)
        app.use(router)
    }
})
const cssLc = cssLifecycleFactory('spa')

console.log(lc)
export const bootstrap = [cssLc.bootstrap, lc.bootstrap]
export const mount = [cssLc.mount, lc.mount]
export const unmount = [cssLc.unmount, lc.unmount]

*the mountParcel and singleSpa keys don't seem to exist in single-spa-vue on appOptions.
I'm not 100% sure whether I even have the setup right due to the lack of documentation and examples.
I also can't figure out how to get to those customProps in the mife.

Hello, @ibjorn.  The TypeScript from the single-spa packages is not to be trusted.  If the comment says "uncomment to assign the props", you should do it.  By extension, I can only imagine that you can also do it for your custom props.

Hi @webJose, pardon my ignorance, but where is that comment you mention?

Interesting:  Don't remember.  Anyway:  The Vue documentation states that properties coming from single-spa are available in the this object.  Have you examined the object to validate this claim?

When I log this, I see my custom prop there, along with singleSpa and mountParcel. However, as mentioned above, TypeScript complains bitterly about where I am trying to add it as props, as per my comment above.
Do you perhaps have any tips on how I could get it from there into my app?
Would it be wise to push it to a store inside spa.ts? Seems like something that should be handled in App.vue rather? Sorry, I know I'm digressing from the subject, I just can't find any info on this for Vue. Tons for React, nothing for Vue.

Typescript is just type checking.  The single-spa packages are notoriously bad in the TypeScript arena.  My recommendation is:  Examine the objects, follow the instructions and give TypeScript, in this particular case, the least priority.  In other words:  If I were you, I'd just add as the example states, and ignore TS errors with // @ts-ignore or // @ts-expect-error.

I have to admit, it feels to me like single-spa isn't really ready for Vue.

@ibjorn not sure that can help you because we are not using but we are using single-spa with customProps and it's working like a charm
root app:
registerApplication(
    "name",
    // eslint-disable-next-line no-undef
    () => System.import("name"),
    (location) => location.pathname.startsWith("/"),
    { myProp: "example" }
)

On the spa/mife:
singleSpaVue({
    createApp,
    appOptions: {
        render() {
            console.log(this.myProp) // will return "example"
            return h(App)
        }
    },
)}

Maybe it can helps you ;)
And to make this prop available in whole app, we exposed it in window (not the best, but the easiest in our case)

Hi @quentin-desbin, thanks for the reply. That is more or less what I currently have. I see what you're doing differently there under appOptions.
I'm just a bit stumped as to how I can securely get those props into my app.

So this is the interesting thing. I can see my props, and they're in <App />. But how does one access them?

Cracked it.
So, in  spa.ts I provide the props:
const lc = singleSpaVue({
    createApp,
    appOptions: {
        render() {
            return h(App)
        }
    } as any,
    handleInstance: (app, props) => {
        registerPlugins(app)
        app.use(router)
        app.provide('appProps', props)
    }
})

And in App.vue I simply inject them:
const props = inject('appProps')

onMounted(() => {
  console.log(props)
})

Easy-peasy, 🍋 squeezy.


Warning that SHA-512 truncated to 256 is not SHA-512/526.

As suggested in multiformats/multihash#101, a clarification to avoid headaches to whomever calculates a different values and doesn't understand why. (like I did)
PS: 215 in the commit title is a strange typo for 256.

Thanks!


Validation error “Exceeded max number of characters”

Describe the problem or bug
When attempting to upload to Docker Hub, the request fails with the status code 400 and a message “Exceeded max number of characters”.
docker-pushrm version
1.9.0
Docker CLI version and platform
24.0.0 on Fedora CoreOS 38.20230430.3.1
exact command that you're running
example: docker run --rm -t -v /tmp:/tmp -e DOCKER_USER=[username] -e DOCKER_PASS=[token] chko/docker-pushrm --file [filepath] marvinruder/rating-tracker --debug
debug output
DEBU root cmd init config
DEBU home dir: /home
DEBU subcommand "pushrm" called
DEBU Using target: docker.io/marvinruder/rating-tracker:latest
DEBU using README file: /tmp/jenkins-cache/README/c46bbe76
DEBU server: docker.io
DEBU namespace: marvinruder
DEBU repo: rating-tracker
DEBU tag: latest
DEBU repo provider: dockerhub
DEBU Dockerhub.GetAuthident called
DEBU using credentials for user marvinruder from generic env var
DEBU Using Docker creds: marvinruder ********
DEBU Dockerhub.Pushrm called
DEBU retrieve Dockerhub jwt token, status code: 200
DEBU push readme, response body: {"message":"httperror 400: request had 1 validation error","errinfo":{"fielderrors":{"full_description":"Exceeded max number of characters"}}}
DEBU push README, status code: 400
DEBU error pushing README, bad status code for response: 400 Bad Request
ERRO error pushing readme to repo server. See error message below. Run with "--debug" for more details.

error pushing README, bad status code for response: 400 Bad Request

Additional context
Manually adding the entire README using a web browser ~works fine~ (see comment). The file is 26148 bytes long.

Closing as the bug also appears when manually uploading on the webpage (without any error message though, the new README is accepted and is shown immediately after, but reloading the page shows the old one again. Took me a moment to realize this.). Will report to Docker Hub instead (at least so that they handle errors properly).

anyways thanks for the info, wasn't aware of it :)


Copy to clipboard not working

Current Behavior
"Copy to clipboard" is not working and throws an error in the browser console
TypeError: undefined is not an object (evaluating 'navigator.clipboard.writeText')

Expected Behavior
Text should be copied to clipboard
Steps to Reproduce
No response
Version
v1.0.0
What operating system did the problem occur on (e.g. Ubuntu 22.04, macOS 12.0, Windows 11)?
Chrome, Safari
Anything else?
No response

odd, I removed a pollyfill, looked like it was no longer required (and works for me across all browsers): https://caniuse.com/mdn-api_clipboard_writetext
I'll add it back 👍🏼

Please note, the issue with the clipboard is on both Hostd and entered.


dropbear: 2018.76 -> 2019.78

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/dropbear/versions.
meta.description for dropbear is: '"A small footprint implementation of the SSH 2 protocol"'.

Checks done (click to expand)

built on NixOS
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 2019.78 with grep in /nix/store/kpnz53fg2n7siva6i75fjxpmi1asw2rw-dropbear-2019.78
directory tree listing: https://gist.github.com/e63defeaa485b4a9207cc890e810d786
du listing: https://gist.github.com/ddb318691bdda8892007ea6520fa67d1

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
dropbear

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/kpnz53fg2n7siva6i75fjxpmi1asw2rw-dropbear-2019.78 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A dropbear https://github.com/r-ryantm/nixpkgs/archive/dc418e71c6f35033dbf759ec8105f392ec6d956c.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/kpnz53fg2n7siva6i75fjxpmi1asw2rw-dropbear-2019.78
ls -la /nix/store/kpnz53fg2n7siva6i75fjxpmi1asw2rw-dropbear-2019.78/bin

cc @abbradar for testing.

This pull request has been mentioned on Nix community. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/5


FX: external backend ENCRYPTION

In s3server we have bucket level encryption.
AWS S3 has object level encryption.
When we did the AWS backend on s3server, we decided to rely on AWS S3's object level encryption (instead of our own) so that encrypted objects would be readable if accessed directly from AWS S3. Now that we are bringing Azure into the picture, this gets complicated since Azure encryption is at the account level and s3server will not be messing with the account level settings.
To make things consistent and to best carry-out the intent of users:

If a user creates an encrypted bucket, we always do the encryption on a put to this bucket (even if going to the azure or aws backends).

When setting up a locationConfig entry for the aws backend, we will allow them to set an option of "serverSideEncryption: true".  If they set this option, any time we put to this location constraint, we will send the appropriate headers to AWS so that they encrypt.

NOTE: I could not find any documentation about the CloudServer Encryption

CONFLICT (add/add): Merge conflict in tests/locationConfigTests.json
CONFLICT (add/add): Merge conflict in lib/data/multipleBackendGateway.js
CONFLICT (add/add): Merge conflict in lib/data/locationConstraintParser.js
CONFLICT (add/add): Merge conflict in lib/data/external/AwsClient.js
CONFLICT (add/add): Merge conflict in lib/Config.js

PR has been updated. Reviewers, please be cautious.

@electrachong, I think leaving the encryption in the main document is fine for now. If people want more detail on the encryption we can expand it into its own doc later.

@ironman-machine try

Hello @nicolas2bert
"try": Success: Try build successfully launched on 'http://ci.ironmann.io/gh/scality/Integration/14626' with the following env. args:
{
    "SCALITY_INTEGRATION_BRANCH": "ultron/master",
    "REPO_NAME": "S3",
    "DEFAULT_BRANCH": "master",
    "SCALITY_S3_BRANCH": "fx/external/encryption"
}

:broken_heart: :umbrella: circleCI test failed.

@ironman-machine r+

Hello @LaurenSpiegel
"r+": Success

:hourglass: PR is now pending. CI build url: http://ci.ironmann.io/gh/scality/Integration/14673

:broken_heart: :umbrella: circleCI test failed.

@ironman-machine try

Hello @nicolas2bert
"try": Success: Try build successfully launched on 'http://ci.ironmann.io/gh/scality/Integration/14674' with the following env. args:
{
    "SCALITY_INTEGRATION_BRANCH": "ultron/master",
    "REPO_NAME": "S3",
    "DEFAULT_BRANCH": "master",
    "SCALITY_S3_BRANCH": "fx/external/encryption"
}

:broken_heart: :umbrella: circleCI test failed.

@ironman-machine try

Hello @nicolas2bert
"try": Success: Try build successfully launched on 'http://ci.ironmann.io/gh/scality/Integration/14675' with the following env. args:
{
    "SCALITY_INTEGRATION_BRANCH": "ultron/master",
    "REPO_NAME": "S3",
    "DEFAULT_BRANCH": "master",
    "SCALITY_S3_BRANCH": "fx/external/encryption"
}

:sunny: :+1: circleCI test succeeded!

@ironman-machine try

Hello @nicolas2bert
"try": Success: Try build successfully launched on 'http://ci.ironmann.io/gh/scality/Integration/14681' with the following env. args:
{
    "SCALITY_INTEGRATION_BRANCH": "ultron/master",
    "REPO_NAME": "S3",
    "DEFAULT_BRANCH": "master",
    "SCALITY_S3_BRANCH": "fx/external/encryption"
}

@ironman-machine try

Hello @nicolas2bert
"try": Success: Try build successfully launched on 'http://ci.ironmann.io/gh/scality/Integration/14683' with the following env. args:
{
    "SCALITY_INTEGRATION_BRANCH": "ultron/master",
    "REPO_NAME": "S3",
    "DEFAULT_BRANCH": "master",
    "SCALITY_S3_BRANCH": "fx/external/encryption"
}

:broken_heart: :umbrella: circleCI test failed.

@ironman-machine try

Hello @nicolas2bert
"try": Success: Try build successfully launched on 'http://ci.ironmann.io/gh/scality/Integration/14691' with the following env. args:
{
    "SCALITY_INTEGRATION_BRANCH": "ultron/master",
    "REPO_NAME": "S3",
    "DEFAULT_BRANCH": "master",
    "SCALITY_S3_BRANCH": "fx/external/encryption"
}

:sunny: :+1: circleCI test succeeded!

@ironman-machine try

Hello @nicolas2bert
"try": Success: Try build successfully launched on 'http://ci.ironmann.io/gh/scality/Integration/14694' with the following env. args:
{
    "SCALITY_INTEGRATION_BRANCH": "ultron/master",
    "REPO_NAME": "S3",
    "DEFAULT_BRANCH": "master",
    "SCALITY_S3_BRANCH": "fx/external/encryption"
}

:broken_heart: :umbrella: circleCI test failed.

@ironman-machine try

Hello @nicolas2bert
"try": Success: Try build successfully launched on 'http://ci.ironmann.io/gh/scality/Integration/14704' with the following env. args:
{
    "SCALITY_INTEGRATION_BRANCH": "ultron/master",
    "REPO_NAME": "S3",
    "DEFAULT_BRANCH": "master",
    "SCALITY_S3_BRANCH": "fx/external/encryption"
}

:sunny: :+1: circleCI test succeeded!


[vcpkg baseline][rest-rpc] Skip check in baseline

Because the msgpack in rest-rpc is very different from the header file of port msgpack, disable the check of rest-rpc in the baseline and add error message to notify users.
Error log:
error: The following files are already installed in /home/vzhli17/jim/vcpkg/installed/x64-android and are in conflict with rest-rpc:x64-android
Installed by msgpack:x64-android
include/msgpack/preprocessor/tuple/to_seq.hpp
    include/msgpack/preprocessor/tuple/pop_back.hpp
    include/msgpack/preprocessor/tuple/pop_front.hpp
    include/msgpack/preprocessor/tuple/push_back.hpp
    include/msgpack/preprocessor/tuple/push_front.hpp
    include/msgpack/preprocessor/tuple/rem.hpp
    include/msgpack/preprocessor/tuple/remove.hpp
    include/msgpack/preprocessor/tuple/replace.hpp
    include/msgpack/preprocessor/tuple/reverse.hpp
    include/msgpack/preprocessor/tuple/size.hpp
    include/msgpack/preprocessor/tuple/to_array.hpp
    include/msgpack/preprocessor/tuple/to_list.hpp
    include/msgpack/preprocessor/tuple/insert.hpp
    include/msgpack/preprocessor/variadic.hpp

[X] Changes comply with the maintainer guide.
[ ] ~SHA512s are updated for each updated download.~
[ ] ~The "supports" clause reflects platforms that may be fixed by this new version.~
[ ] ~Any fixed CI baseline entries are removed from that file.~
[ ] ~Any patches that are no longer applied are deleted from the port's directory.~
[ ] ~The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.~
[ ] ~Only one version is added to each modified port's versions file.~

Or actually start maintaining it properly. #41772.

Duplicate of https://github.com/microsoft/vcpkg/pull/41772.


Recommendations needed: Copying TIFF image to PDF structure / Writing a layer on the TIFF image

Dear Members of gofpdf,
Thank you for this wonderful project.
I would like to make a simplistic TIFF2PDF. I used to have it in java and I miss it. I can not though execute a command line util in the working environment.
I would like to know that if
i would be able to read the TIFF structure in someway (dimensions, meta, CCIT-6 compressed )
what I should do from fpdf side to copy it in the FPDF structure?
Thank you in advance!

Thanks, @dtrehas. My preferred way of supporting TIFFs would be as a separate package in the contrib directory. This is because Go's standard library doesn't support the format and I am reluctant to make gofpdf dependent on non-standard packages. Most likely you could use the Go supplementary package tiff to generate a gofpdf.ImageInfoType structure. I am not familiar with the TIFF format so I am not sure whether this would be straightforward or not. In fpdf.go we could then add a method to register an ImageInfoType structure directly, bypassing the usual png/gif/jpg methods.
Do you have any experience with the tiff package?

Not really.. but I tried a bit a few years ago.
I found that there is https://github.com/pascaldekloe/got.6 library that can not be compiled.
It was from the original tiff package that used to be released with GO long time go.
I could try to modify it a bit.

I just added support for standard TIFF images in gofpdf documents. See tiff.


Q: How to define MethodSettings stage configuration in SAM?

Hi @all
I would appreciate some guidance here from anyone who has managed to successfully configure stage AWS::ApiGateway::Stage/MethodSettings using SAM (such as MetricsEnabled, DataTraceEnabled).
Much appreciated for your help.

Right now this is unsupported. Native support for it in SAM is already implemented. QA and code push remaining. Should be out in a couple of weeks.

+1

Hi @sanathkr
Any updates so far?

What's the status on this?

Ping.


Google lens screen

a great app but it needs more improvements but why you just add Google to me that it also has Google lenses that I hope you add in an upcoming update

Hi @WestonLuca. Last time I checked, the Google App doesn't expose an android-activity of its translate feature. I'll check again if anything changed meanwhile later when I work on this.

Hi @WestonLuca. Last time I checked, the Google App doesn't expose an android-activity of its translate feature. I'll check again if anything changed meanwhile later when I work on this.

Hi, I have installed version 6 But it did not work for me. I hope you
support old Android versions so that it works  Thanks for applying. I wish
you success
في الخميس، 13 أبريل 2023 3:37 ص Vamsi Krishna Reddy Satti <
@.***> كتب:

Hi @WestonLuca https://github.com/WestonLuca. Last time I checked, the
Google App doesn't expose an android-activity of its translate feature.
I'll check again if anything changed meanwhile later when I work on this.
—
Reply to this email directly, view it on GitHub
https://github.com/vamsi3/screen-translator/issues/9#issuecomment-1506245782,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A7BROWJOJHHVKSNPKP5JYCDXA5REXANCNFSM6AAAAAAWXN6QRE
.
You are receiving this because you were mentioned.Message ID:
@.***>


Question: How to correctly handle a Session

Hi !
It's more a best practice question than an issue.
I have historical code which I'm updating from rust-pkcs11 to rust-cryptoki.
The usage of cryptoki is to extract certificates and sign some data but also implements the rustls sign capacity :
impl Signer for PKCS11RSASigner {
    fn sign(&self, message: &[u8]) -> Result<Vec<u8>, TLSError> {
        let mut h = Sha256::default();
        let to_sign2 = h.digest(message).to_bytes();

        let mut final_to_sign = vec![0x30, 0x31, 0x30, 0x0D, 0x06, 0x09, 0x60, 0x86, 0x48, 0x01, 0x65, 0x03, 0x04, 0x02, 0x01, 0x05, 0x00, 0x04, 0x20];
        final_to_sign.extend_from_slice(to_sign2.as_slice());

        sign_with_key(final_to_sign.clone(), AUTHENTICATION_KEY_ID).map_err(|err| {
            error!("rustls sign_with_key error : {:?}", err);
            TLSError::NoCertificatesPresented
        })
    }
}

What is be the best practice to handle a session here ?
Create a new one just inside this implementation while there is already one active in the function calling rustls ?
Thanks a lot for your feedback 🙏

My unfinished prototype can be found here: https://github.com/parallaxsecond/rust-cryptoki/pull/192
but essentially, my approach was for the signer to carry a SessionLike object:
#[derive(signature::Signer)]
pub struct Signer<C: SignAlgorithm, S: SessionLike> {
    session: S,
    private_key: ObjectHandle,
    verifying_key: VerifyingKey<C>,
}

SessionLike defining the "entrypoints" for the signer to tap into cryptoki:
pub trait SessionLike {
    fn create_object(&self, template: &[Attribute]) -> Result<ObjectHandle>;
    fn find_objects(&self, template: &[Attribute]) -> Result<Vec<ObjectHandle>>;
    fn get_attributes(
        &self,
        object: ObjectHandle,
        attributes: &[AttributeType],
    ) -> Result<Vec<Attribute>>;
    fn update_attributes(&self, object: ObjectHandle, template: &[Attribute]) -> Result<()>;
    fn sign(&self, mechanism: &Mechanism, key: ObjectHandle, data: &[u8]) -> Result<Vec<u8>>;
    fn generate_random_slice(&self, random_data: &mut [u8]) -> Result<()>;
    fn wrap_key(
        &self,
        mechanism: &Mechanism,
        wrapping_key: ObjectHandle,
        key: ObjectHandle,
    ) -> Result<Vec<u8>>;
    fn login(&self, user_type: UserType, pin: Option<&AuthPin>) -> Result<()>;
    fn logout(&self) -> Result<()>;
}

SessionLike is then defined for &'s Session and Session. If you then wanted to define the trait for an Arc<Session> or an Arc<Mutex<Session>> I think that's possible.
I don't think the thread-safety garantees or uniqueness of the session are defined at the spec level. I know the two implementation I worked with in the past had varying behavior. One of them you had to opt-in to have thread-safety.

On my case, the Signer trait in defined insite rustls crate: https://github.com/rustls/rustls/blob/20023ee91fbd0c27503b0693825bf7d23cabdbe2/rustls/src/crypto/signer.rs#L75 So I can't change it.

Ack. But PKCS11RSASigner is in your crate? If so then the reference to the Session can live there... :thinking:

I get this error.
error[E0277]: `S` cannot be shared between threads safely
    |
231 | impl<S> Signer for PKCS11RSASigner<S>
    |                    ^^^^^^^^^^^^^^^^^^ `S` cannot be shared between threads safely
    |
note: required because it appears within the type `PKCS11RSASigner<S>`
    |
220 | struct PKCS11RSASigner<S: SessionLike> {
    |        ^^^^^^^^^^^^^^^
note: required by a bound in `Signer`
   --> .cargo/git/checkouts/rustls-4595b772ffea9fe4/f0c30ed/rustls/src/sign.rs:24:27
    |
24  | pub trait Signer : Send + Sync {
    |                           ^^^^ required by this bound in `Signer`

Hmm... sounds like it may need wrapping in an Arc<Mutex<Session>>... your code is not open-source so we can test directly there? :thinking:

Unfortunately it's not, I could try to make a small example but it will take me some time.
I tried to put Session in an Arc Mutex some time ago but I couldn't manage as Session isn't clonable

Unfortunately it's not, I could try to make a small example but it will take me some time.

Completely understandable :+1:

I tried to put Session in an Arc Mutex some time ago but I couldn't manage as Session isn't clonable

Hmm... As far as I know neither Arc nor Mutex requires the thing to be cloneable? :thinking: (Arc has a clone function but it clones the Arc object not the inner one).

I checked in Parsec and we open and close sessions just to perform one single operation. I think it's fine to open sessions in parallel but I think that the Login and Logout status of all sessions are affected at the same time


English and Music in TEDxJP 10k corpus

The TEDxJP 10k corpus contains some inapporopriate data for evaluation of Japanese speech recognition.
In following videos, Japanese people talk in English.
But the corpus uses subtitles that are automatically translated into Japanese.

Aj-DXM5Zqms
Ba5Jl1_JKZY
Mc044I55SCY

Then, following videos contain some music (corpus uses the interval of music).

ydhfjNRFzaM
BLElQZfR_2M
TWeYkdIQsk0
Ab-KZT06gR0
gffgHgnEhtA
kU9LcoHaFLo

It may be better to be removed from the corpus.

@eiichiroi
Thank you for pointing out this issue.
We examined the videos you mentioned and

removed English utterances in Aj-DXM5Zqms, Ba5Jl1_JKZY and gffgHgnEhtA
kept Mc044I55SCY as a part used in our data includes only Japanese utteranes
Kept ydhfjNRFzaM, BLElQZfR_2M, TWeYkdIQsk0, Ab-KZT06gR0, and kU9LcoHaFLo as, though they are singing voices (or rap), their transcriptions are actually correct.

@eiichiroi
Thank you for pointing out this issue.
We examined the videos you mentioned and

removed English utterances in Aj-DXM5Zqms, Ba5Jl1_JKZY and gffgHgnEhtA
kept Mc044I55SCY as a part used in our data includes only Japanese utteranes
Kept ydhfjNRFzaM, BLElQZfR_2M, TWeYkdIQsk0, Ab-KZT06gR0, and kU9LcoHaFLo as, though they are singing voices (or rap), their transcriptions are actually correct.

The above modification was made in https://github.com/laboroai/TEDxJP-10K as TEDxJP-10K_v1.1 .

The above modification was made in https://github.com/laboroai/TEDxJP-10K as TEDxJP-10K_v1.1 .

Thank you!

Thank you!


added batch processing to pipelines

Description :sparkles:
added batch processing to pipelines

Codecov Report

Merging #1056 (41cd6b6) into develop (ca0ca00) will increase coverage by 19.00%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           develop    #1056       +/-   ##
============================================
+ Coverage    64.58%   83.59%   +19.00%
============================================
  Files          905       66      -839
  Lines        25098     2188    -22910
  Branches      2546        0     -2546
============================================
- Hits         16209     1829    -14380
+ Misses        8500      359     -8141
+ Partials       389        0      -389

Impacted Files
Coverage Δ

backend/shared/shared/ytj/ytj_client.py
27.58% <0.00%> (-65.52%)
:arrow_down:

backend/shared/shared/common/decorators.py
37.93% <0.00%> (-58.63%)
:arrow_down:

...nd/shared/shared/service_bus/service_bus_client.py
27.65% <0.00%> (-57.45%)
:arrow_down:

backend/shared/shared/yrtti/yrtti_client.py
39.39% <0.00%> (-51.52%)
:arrow_down:

backend/shared/shared/audit_log/viewsets.py
45.56% <0.00%> (-50.64%)
:arrow_down:

backend/shared/shared/common/lang_test_utils.py
60.00% <0.00%> (-40.00%)
:arrow_down:

backend/shared/shared/models/mixins.py
66.66% <0.00%> (-33.34%)
:arrow_down:

backend/shared/shared/common/utils.py
75.00% <0.00%> (-25.00%)
:arrow_down:

backend/shared/shared/audit_log/audit_logging.py
76.59% <0.00%> (-23.41%)
:arrow_down:

backend/shared/shared/common/tests/conftest.py
86.95% <0.00%> (-13.05%)
:arrow_down:

... and 839 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 ca0ca00...41cd6b6. Read the comment docs.


About what happens after "Colcon Build"

What happens when I run Python helloWorld.py，display
/home/liu/FastDDSpydemo/fastdds_python_ws/build/fastdds_python_examples/HelloWorldExample/_HelloWorldWrapper.so: Undefined symbol: PyCMethod_New "What's up with this

Hi @liuying0125, thanks for using Fast DDS. and sorry for the late response.
I could not reproduce your issue, could you confirm it is still happening in our latest version v1.3.0?


failed to call createTracker when run tests with phantomjs

Recently I upgraded the version of react-router of my project to latest stable release v2.8.1 and in the meantime I changed to use react-router-redux instead of redux-router which is not compatible with react-router v2. and then I upgraded redux-segment version to 1.4.2.
My system works well on browsers, but all tests failed and I got an error says failed to execute createTraker.
`
[ERROR - 2016-10-20T05:42:00.778Z] Session [ea29d420-9687-11e6-a335-a901cb9e5efe] - page.onError - msg: TypeError: undefined is not a constructor (evaluating 'Object.assign({}, { mapper : _configuration.defaultMapper.mapper }, customOptions.mapper)')
phantomjs://platform/console++.js:263 in error
[ERROR - 2016-10-20T05:42:00.778Z] Session [ea29d420-9687-11e6-a335-a901cb9e5efe] - page.onError - stack:
createTracker (http://localhost:19001/assets/site.bundle.js:121916)
(anonymous function) (http://localhost:19001/assets/site.bundle.js:45848)
webpack_require (http://localhost:19001/assets/vendor.bundle.js:51)
(anonymous function) (http://localhost:19001/assets/site.bundle.js:18740)
(anonymous function) (http://localhost:19001/assets/site.bundle.js:18769)
webpack_require (http://localhost:19001/assets/vendor.bundle.js:51)
(anonymous function) (http://localhost:19001/assets/site.bundle.js:35)
webpack_require (http://localhost:19001/assets/vendor.bundle.js:51)
webpackJsonpCallback (http://localhost:19001/assets/vendor.bundle.js:22)
phantomjs://platform/console++.js:263 in error
`
Can someone have a look at this issue and create a pull request please?

I think the issue here @htxiong is that PhantomJS doesn't support Object.assign. Are you able to add a polyfill to your configuration?

@bertrandk thanks for quick reply.
I add both phantomjs-polyfill &  phantomjs-polyfill-object-assign to my project, and its still get this error.

@htxiong I need some help recreating this in order to help. Would you be able to share either your test runner configuration or a small reproducible case? Mostly, I just need to know what version of PhantomJS you're running, what test runner you're using and how you've setup the polyfills above.
This error is usually the PhantomJS equivalent of Uncaught TypeError: Object.assign is not a function.

@bertrandk the test runner I am using is karma and the version of phantomjs is 2.1.7. All test dependencies shown below.
"devDependencies": {     "chai": "3.3.0",     "chai-as-promised": "5.1.0",     "karma": "0.13.9",     "karma-chai": "0.1.0",     "karma-chai-as-promised": "0.1.2",     "karma-clear-screen-reporter": "0.0.1",     "karma-mocha": "0.2.1",     "karma-mocha-reporter": "1.1.3",     "karma-phantomjs-launcher": "0.2.1",     "karma-sinon": "1.0.4",     "karma-sinon-chai": "1.1.0",     "karma-webpack": "1.7.0",     "mocha": "2.3.4",     "phantomjs": "2.1.7",     "phantomjs-polyfill": "0.0.2",     "phantomjs-polyfill-object-assign": "0.0.2",     "redux-devtools": "3.2.0",     "redux-devtools-dock-monitor": "1.1.1",     "redux-devtools-log-monitor": "1.0.11",     "sinon": "1.17.2",     "webpack-error-notification": "0.1.5"   }
and my karma conf file is:
`
frameworks: ["mocha", "chai-as-promised", "sinon", "sinon-chai"],
	// list of files / patterns to load in the browser
	files: [
		'node_modules/phantomjs-polyfill/bind-polyfill.js',
		'node_modules/phantomjs-polyfill-object-assign/object-assign-polyfill.js',
		ENTRY
	],

`

there is a post on stackoverflow for this issue and a solution provided. I tried it but with no luck to solve mine.
http://stackoverflow.com/questions/36706829/npm-karma-phantomjs-undefined-is-not-a-contructor

@htxiong If you're still interested, build 1.5.0 should cleanly support envs where Object.assign isn't there.

Thanks @bertrandk.


[es-dev-server] better babel error UX

When babel is turned on errors are logged to the console. It's hard to distinguish whether the errors are actually from the current compile or from a previous compile. Especially in watch mode it get very spammy because it compiles while typing.
We can looking into some solutions, such as clearing the terminal on refresh or maybe only logging to the browser.

This wwas implemented


PosStr is unnecessary

We always have the remaining input. We can just calculate line and column dynamically when an error occurs.

No actually we do need it be able to refer to line and column number in later steps of the compiler.


[PE-D][Tester A] Error handling for clear can be improved, since it is actually a known command.

Better error handing could have been done for the clear command. When keying in the clear command, it says unknown command, when actually it is known, just that I am missing the demarcators.

Labels: severity.VeryLow type.FeatureFlaw
original: lesterong/ped#5

Fixed by https://github.com/AY2223S1-CS2103-W14-1/tp/pull/224


3.x Enhance null checking for input event

Fixes: #69214
Input events passing through various event functions can be null which causes the engine to crash, so checking InputEvent is null for every input function is necessary.

Methods such as _input(), _unhandled_input(), and _gui_input() are callbacks. They are guaranteed to received a valid InputEvent. Users are supposed to provide input event via Input.parse_input_event(), which does check for null.
IMHO, the cause of the crash is "calling them with nulls" instead of "not checking for null in them". But since we dont's have a way to forbid access to internal methods (see https://github.com/godotengine/godot-proposals/issues/2285) or marking non-null parameters, I think this is okay.

the cause of the crash is "calling them with nulls" instead of "not checking for null in them".

Recall from my memory. It is the callee whom responsible for handling these tasks.

It is the callee whom responsible for handling these tasks.

Well, these methods are not supposed to be called by the user. When called by the engine, it guarantees it won't call them with null.


Unhandled Promise Rejection before tests are running

Getting this error before any of the tests are run:
[UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "AxiosError: Request failed with status code 400".]
{code: 'ERR_UNHANDLED_REJECTION'
}
Any ideas of what could be causing this issue?

Hello @JacksonLei123 !
Could you please provide your playwright and RP agent configs?

Sure! Basically I have:
export const RPconfig = {
     token: TOKEN,
     endpoint: ENDPOINT,
     project: PROJECT,
     launch: LAUNCH_NAME
};
const config: PlaywrightTestConfig = {
    projects: [{
         name: PROJECTNAME,
         testDir: TESTDIRECTORY,
         use: {
            browserName: 'chromium',
            proxy : {server: SERVERURL}
         }
    }],
   reporter: ['@reportportal/agent-js-playwright', RPconfig}]

}

I would run npx playwright test --project=PROJECTNAME then the console logs Running x tests using y worker and then that when the error gets shown

Do the following requests reach the RP server?
Could you run the tests with debug: true to collect more verbose output related to the requests the agent sends.

It doesn't look like the requests reach the RP server since I don't see any tests being registered in the Report Portal UI. After running the tests with debug: true, I additionally get:
Start launch with tempId TEMPID
{
    name: LAUNCH_NAME,
    startTime:<PHONE_NUMBER>372,
    description: undefined,
    attributes: [
          {
             key: 'agent'
             value<EMAIL_ADDRESS>             system: true
          }
   ],
   rerun: undefined,
   rerunOf: undefined,
   mode: 'DEFAULT',
   id: undefined
}

followed by the original error

The logged request you provided looks fine.
Could you run our example and make sure the behavior is still there?
I just want to exclude network-specific and RP instance errors to make sure the issue is on the agent side.

Yup the error is still there when I run the example

So seems like the issue is not related to this agent, because the examples works fine.
What is your reportportal version?

Hello @JacksonLei123 !
Is the issue still relevant?
Could you please try to start the new launch by RP API request?
You can use Swagger API spec from API page:

If I understand correctly, you inserted LAUNCH_NAME without quotes as a placeholder, but in fact you configured the launch name as a string.
I'm still assuming there's an issue with the RP API service as the request you shared looks valid and can't throw a 400 error.

Hello @JacksonLei123 !
Is your issue still relevant?

Hello @JacksonLei123 !
I'll close the issue for now, feel free to reopen it if needed.


C.LUI immediate field should be nzimm, not nzuimm?

Instruction C.LUI has a 6-bit immediate constant specified as "nzuimm[17:12]", but this constant is then said to be sign-extended.  Should this be written "nzimm" instead of "nzuimm"?  (If not, what does the 'u' stand for?)

Indeed, fixed in 3e6b37033d0ec9a2e0cc132b885655afa100589e, thanks.


2025-04-28-perpetual-text

OpenReview Submission Thread

Checklist before opening a PR

[X] I am opening a pull request against the main branch of the 2025 repo.

[X] My post and all associated references to it are all lowercase, i.e
  2025-04-28-Sample-Test.md               -> 2025-04-28-sample-test.md
  assets/img/2025-04-28-Sample-Test/ 	-> assets/img/2025-04-28-sample-test/

[X] The title of my PR is exactly the name of my markdown file

i.e. _posts/2025-04-28-[submission-name].md would require a PR name 2025-04-28-[submission-name]

[X] I have anonymized my post: my author's list is Anonymous, and there is no potential
content which can reveal my/my collaborators identities.

[X] My post matches the formatting requirements, including (but not limited to):

[X] I have ONLY MODIFIED files in the following locations (failure to do so will result in
your PR automatically being closed!):

a Markdown (or HTML) file in _posts/ with the format _posts/2025-04-28-[submission-name].md (or .html)
static image assets added to assets/img/2025-04-28-[submission-name]/
interactive HTML figures added  to assets/html/2025-04-28-[submission-name]/
citations in a bibtex file in assets/bibliography/2025-04-28-[submission-name].bib

[X] I have a short 2-3 sentence abstract in the description field of my front-matter
[X] I have a table of contents, formatted using the toc field of my front-matter
[X] My bibliography is correctly formatted, using a .bibtex file as per the sample post

Any other comments

fixed


Propagate service monitored label

What did you do?
my service have labels pfid.
My servicemonitor use label pfid on selector
But those label is not propagate on prometheus metrics
What did you expect to see?
i want to have access on all or select of labels available on service to prometheus metrics

While this is generally possible, you can also join all labels of a service onto metrics using the metrics available in kube-state-metrics
https://github.com/kubernetes/kube-state-metrics/blob/master/Documentation/service-metrics.md#service-metrics
Does that work for you?

Sorry.
when i am not clear.
I use mysql_exporter on a pod with label pfid
on my service monitor i have matchExpressions
spec:
  jobLabel: k8s-app
  selector:
    matchExpressions:
      - { key: pfid, operator: Exists}

But when metrics show metric mysql_exporter_scrapes_total on prometheus, fidlabel used on selector is not available on metrics. I have only basic label
mysql_exporter_scrapes_total{endpoint="mysqld-exporter",instance="<IP_ADDRESS>:9104",job="mysqld-exporter",namespace="srnt-sgl1",pod="mysql-2760336166-hg3rf",service="mysqld-exporter"}
`
My genrated config:
- job_name: monitoring/mysqld-exporter/0
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  kubernetes_sd_configs:
  - api_server: null
    role: endpoints
    namespaces:
      names: []
  relabel_configs:
  - source_labels: [__meta_kubernetes_service_label_pfid]
    separator: ;
    regex: .+
    replacement: $1
    action: keep

Yes, the excerpt of the Prometheus config only says that a target with that meta label will be kept, not that it will have that target after relabeling. Relabeling is exactly the kind of black magic we want to keep out of the Prometheus Operator in terms of configurability.
What you are seeing is the mix of Prometheus labels and Kubernetes labels. While they can be used in a compatible manner, they are not the same.

Yes i'm right with you. but how can i make to configure or request with Kubernetes labels? i have not found information or example.

If you have kube-state-metrics running and are scraping its metrics, then you can join the kube_service_labels metric onto the mysql_exporter_scrapes_total metric.
mysql_exporter_scrapes_total * on(service) group_right() kube_service_labels

I have the same issue.
We have labels we want to propagate from kubernetes into prometheus. The above solution on a random metric resulted in:
{code}
Error executing query: many-to-many matching not allowed: matching labels must be unique on one side
{code}
But whatever the case, we don't want to always have to write a query that's 3 times longer than it should be, just because we're running prometheus operator.
Any other suggestions?

We're aiming to make the majority of common cases very easy with great experience, there will always be a case that's not very well supported, at that point we want to make sure you can achieve what you want, but can't always make it easy. If you disagree with how the Prometheus Operator generates a configuration off of ServiceMontior objects, then you can still opt for a custom configuration, and handle everything down to relabeling rules yourself :slightly_smiling_face:.

I respect your desire to limit the scope of your application.
Of course, I disagree with:

We're aiming to make the majority of common cases
..which implies that my and @sebglon 's case is not common ;)
All I need is an on/off switch for kubernetes label propagation for servicemonitors. Going the custom config route is not an option for me (very self service orientated org).

@brancz If we implement such a feature on our own, will you consider accepting a pull request?

Considering there seems to be a lot of interest in this, I would like to discuss the design for this to ensure that we're happy with the result. Options that we could do:

Relabel all labels of a service onto targets

With an additional prefix for these labels would mean potential usability concerns, omitting a prefix would allow for possible collisions. We could formally describe the order of how labels are relabeled to targets and document the expected behavior to avoid confusion, but Prometheus reserved labels are still possible to be overridden (again we can document if we forbid to do this, but it's possibly a usability concern).
The other option would be to whitelist labels per ServiceMonitor to be relabeled onto targets.

Let me know your thoughts.

Of the two, whitelisting labels would empower the user the most. Any concerns about keeping your whitelist of labels in sync with changes to the service labels, would be a concern of the deployment tooling.
Personally, I'd like to be able to add custom relabeling configuration to a job. This way you'd gain more flexibility (I'd like to rename labels for example).

Here is an example joining the team label:
100*(count by (job) ((up == 0) * on(pod) group_left(label_team) kube_pod_labels))/(count by (job) (up * on(pod) group_left(label_team) kube_pod_labels))

Original query looks like this:
100 * (count(up == 0) BY (job) / count(up) BY (job)) > 10

The original query takes 1500ms to run on on 1h data
The joining takes more than double that time to run.
So it might be a performance enhancement to allow putting labels on the jobs
I would ideally have a whitelisting on the ServiceMonitor object. Both for pod and service.

The performance of a query is something that can easily be fixed with recording rules, but I think it's still fair to relabel white-listed labels onto targets. The next question would be, how do we want this to look like usability wise. I would propose a list of label-names as a field of the ServiceMonitor object.
For example:
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  name: myteam
  labels:
    team: myteam
spec:
  selector:
    matchLabels:
      team: my-team
  targetLabels:
  - team
  endpoints:
  - port: web

This part would be the new part:
  targetLabels:
  - team

This would cause the "team" label of services (and pods?) to be relabeled onto the targets discovered through this ServiceMonitor. I would still propose the label_ prefix, just for joins to be easy with metrics from kube-state-metrics.
How does that sound?

That would be a perfect solution from my perspective.
I dont know if anyone needs pods and service labels separated. If so there might be a need for two lists, perhaps targetPodLabels and targetServiceLabels. I would prefer just taking service and pods labels, with pods having priority.
I agree with keeping the label_ prefix consistent with kube-state-metrics

@brancz As a user, I’d like to:

be able to propagate labels from both service and pod (on my choice)
be able to select labels for propagation using regular expressions, e.g. org_.* or example\.org/.*
be able to rename labels during propagation, e.g. example.org/feature: true => org_feature: true
be able to override default prefix (label_), if any
not to worry about accidentally overriding internal labels, such as namespace, service, pod, job

E.g.,
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  name: myteam
  labels:
    team: myteam
spec:
  selector:
    matchLabels:
      team: my-team
  endpoints:
  - port: web
  propagateLabels:
  - source: # optional, both `pod` and `service` by default; the order could be taken into account in corner cases
    - pod
    - service
    match: "example\.org/(.*)" # optional, match any by default
    rename: "org_$1"           # optional, original value by default
  - match: "org_.*"            # more typical case

@brancz that is really good news. If there exists any WIP I would love testing this feature.
To add some context on the importance of this feature, consider that a lot of community supported Grafana dashboards are using the labels that will be added from e.g. (swap pod with either service or node ++ for other usecases):
    - separator: ;
      regex: __meta_kubernetes_pod_label_(.+)
      replacement: $1
      action: labelmap

After migrating to prometheus-operator I found I had to edit many our community supported dashboards, effectively having to maintain those ourself. The same goes for a good set of alerts I have gathered around. Luckily most of them come from the well curated set of alerts from CoreOS.
Metric relabeling only takes me a step of the way as it won't consider the meta info available when scraping.  Not sure how the WriteRelabelConfigs works though. Would that perhaps solve my usecase?

Have you a PR to track the change ?

Dashboards and alerts are and always will be opinionated to the setup of the person who created them, it's unlikely, that we will ever be able to unify all dashboards and alerts. In the very first days of the operator we actually did relabel all labels onto a target, this caused various problem, which is why we ultimately removed them from the targets. Instead I recommend joining the labels onto the metrics at query time using the kube_*_labels metrics from kube-state-metrics. An example of how to do that can be found here: https://github.com/kubernetes/kube-state-metrics/issues/137#issuecomment-299837471

We added relabeling support for the remote read/write and metric relabeling, so I'd suggest that we add full relabeling capabilities to the ServiceMonitor/Endpoints object as well.
Great news, It will make federation a lot easier as well.

Hi,
Doing the re-label via kube_pod_labels at query time seems quite a handful when you end up with lots of recording rules / alerts.
Our current use-case would be to create an environment label on each service, but if we consider that it's super easy to (and useful) to create labels on k8s, we'll want to extend this further.
Given the amount of rules we have (then add on 3rd-party ones), there's an awful lot of re-labelling that would have to be done, and I don't see how we can manage this in a nice way.
Propagating service-monitor labels sounds ideal for us - so I'm wondering whether there's any updates in this area?
I'm also wondering whether I've missed a trick here (how is everyone else doing this?).

I'm also interested in the capability. We deploy different configs of our service with identifying labels and it'd be ideal to see these propagated through Prometheus Operator so I can select using them in Grafana.
Forwarding all labels with a prefix seems ideal for my use case.

I have replicated the coreos alerts with grouping where applicable. Just looking for personal time to create a PR, if there is interest?
E.g.
       - alert: PodFrequentlyRestarting
          expr: ( sum( increase( kube_pod_container_status_restarts[1h]) ) by (pod) > 2) / on(pod) group_right() kube_pod_labels
          for: 10m
          labels:
            severity: warning
          annotations:
            description: Pod {{$labels.namespaces}}/{{$labels.pod}} is was restarted {{$value}}
              times within the last hour
            summary: Pod is restarting frequently```


onchain-verifier: measuring gas usage for grand product argument

I got some troubles using foundry's gas-report to work with the code with internal functions, but will continue to investigate.
For now this is a new test that outputs some gas benchmarks for the internal functions of the verifier when BENCHMARK_LOGGING=true using a wrapper around the grand product argument library
You can run the gas report with BENCHMARK_LOGGING=true forge test --via-ir --ffi -vv --match-test testGasGrandProductVerify
I don't think it's the best, so would love some ideas on how to make it better!

btw one pattern I've used in the past is a function modifier that prints the gas of the modified function:
modifier logGas(string memory label) {
    uint256 gasUsed = gasleft();
    _;
    gasUsed -= gasleft();
    console.log(label, gasUsed);
}

this can be used for internal functions, similar to the in-line logging you have now


[VSCode] [Wearable] Unable to add new page

Technical
[VSCode] [Wearable] Unable to add new page

page name field is not editable

not able to reproduce more


Filter Expression can only contain non-primary key attribute

ERROR:cloudwanderer.utils:An error occurred (ValidationException) when calling the Query operation: Filter Expression can only contain non-primary key attributes: Primary key attribute: _resource_type_index
Traceback (most recent call last):
  File "/Users/sammartin/git/CloudWanderer/cloudwanderer/utils.py", line 21, in exception_logging_wrapper
    method(**kwargs)
  File "/Users/sammartin/git/CloudWanderer/cloudwanderer/cloud_wanderer.py", line 106, in write_resources_in_region
    self.write_resources_of_service_in_region(
  File "/Users/sammartin/git/CloudWanderer/cloudwanderer/cloud_wanderer.py", line 141, in write_resources_of_service_in_region
    self.write_resources_of_type_in_region(
  File "/Users/sammartin/git/CloudWanderer/cloudwanderer/cloud_wanderer.py", line 175, in write_resources_of_type_in_region
    self._clean_resources_in_region(service_name, resource_type, region_name, urns)
  File "/Users/sammartin/git/CloudWanderer/cloudwanderer/cloud_wanderer.py", line 201, in _clean_resources_in_region
    storage_connector.delete_resource_of_type_in_account_region(
  File "/Users/sammartin/git/CloudWanderer/cloudwanderer/storage_connectors/dynamodb.py", line 276, in delete_resource_of_type_in_account_region
    for resource in resource_records:
  File "/Users/sammartin/git/CloudWanderer/cloudwanderer/storage_connectors/dynamodb.py", line 239, in read_resources
    result = self.dynamodb_table.query(**query_args)
  File "/Users/sammartin/.pyenv/versions/3.8.6/lib/python3.8/site-packages/boto3/resources/factory.py", line 520, in do_action
    response = action(self, *args, **kwargs)
  File "/Users/sammartin/.pyenv/versions/3.8.6/lib/python3.8/site-packages/boto3/resources/action.py", line 83, in __call__
    response = getattr(parent.meta.client, operation_name)(*args, **params)
  File "/Users/sammartin/.pyenv/versions/3.8.6/lib/python3.8/site-packages/botocore/client.py", line 357, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/Users/sammartin/.pyenv/versions/3.8.6/lib/python3.8/site-packages/botocore/client.py", line 676, in _make_api_call
    raise error_class(parsed_response, operation_name)
botocore.exceptions.ClientError: An error occurred (ValidationException) when calling the Query operation: Filter Expression can only contain non-primary key attributes: Primary key attribute: _resource_type_index

This only occurs when using the experimental concurrency support and is not yet reliably reproducible.
If anyone has a reproducible scenario, please post it herel

This only occurs when using the experimental concurrency support and is not yet reliably reproducible.
If anyone has a reproducible scenario, please post it herel

Closing as this seems to have been fixed in release 0.13.0.


fix: sync to_parquet arguments

continuing story from #328, now for writing

Codecov Report

Merging #334 (8473dc3) into main (483ed21) will increase coverage by 0.20%.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main     #334      +/-   ##
==========================================
+ Coverage   94.57%   94.78%   +0.20%
==========================================
  Files          20       20
  Lines        2490     2475      -15
==========================================
- Hits         2355     2346       -9
+ Misses        135      129       -6

Files Changed
Coverage Δ

src/dask_awkward/lib/io/parquet.py
91.92% <100.00%> (+2.72%)
:arrow_up:

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


${config:} variables fail to resolve in multi-root workspace launch configurations.

Issue Type: Bug
When I try to use ${confg:<name>} variables in multi-root workspace launch configurations, they fail to resolve with error:
'${config:<name>}' can not be resolved in a multi folder workspace. Scope this variable using ':' and a workspace folder name.

This is not right, as there is no way to scope config variables with workspace folder names.
Minimal example, launching the configuration Launch Program will fail to resolve the config variable:
Hierarchy:
Desktop:
  test1
  test2
  test.code-workspace

test.code-workspace:
{
  "folders": [
    {
      "path": "./test1"
    },
    {
      "path": "./test2"
    }
  ],
  "launch": {
    "configurations": [
      {
        "name": "Launch Program",
        "type": "node",
        "request": "launch",
        "program": "${config:editor.fontSize}"
      }
    ]
  }
}

VS Code version: Code 1.45.0 (d69a79b73808559a91206d73d7717ff5f798f23c, 2020-05-07T15:57:33.467Z)
OS version: Darwin x64 19.4.0

Can confirm. It's really annoying since I can't launch debug configuration in my workspace :(


Add k8s-ci-robot as Kubeflow admin

Because of https://github.com/kubeflow/pipelines/issues/1653#issuecomment-662211749, k8s-ci-bot needs org admin permission to do its job.
For security concerns, k8s-ci-bot is also kubernetes organization's admin, so we think it's fine https://github.com/kubeflow/pipelines/issues/1653#issuecomment-668625178

/assign @jlewi @rmgogogo
/approve

/lgtm


disable-dih-scheduler-3

This branch disables the DIH scheduler in /etc/solr/conf/web.xml You can reenable it following the instructions in that file and in the example dataimport.properties in /usr/share/doc/solr-common
Fixes #3

As usual, a built package can be found in my PPA at https://launchpad.net/~esteve/+archive/solr-stable

LGTM!


chore(stash): release package to npm

replaced by https://github.com/latticexyz/mud/pull/3184 so we can start publishing snapshots


chore: update repo

update version to <IP_ADDRESS>-5
Issue: https://github.com/linuxdeepin/developer-center/issues/5731
Log: update repo

/skip

/approve


Initiating HTTP/2 connections with prior knowledge are currently not supported

Steps to reproduce the problem:

Run mitmproxy in transparent mode:

mitmproxy --mode transparent [--showhost]

Generate traffic through the transparent proxy (traffic is redirected to mitmproxy via iptables in Linux) from an Android client. The Android client tries multiple HTTP/2 connections to various Google servers, typically in the 216.58.x.y & 172.217.w.z IP address ranges.
All these connections appear in the Flows list as shown, followed by a "Connection killed" error message (in red color):

PRI https://216.58.x.y HTTP/2.0

The log generates a related warning ("warn:", in orange color): "Initiating HTTP/2 connections with prior knowledge are currently not supported".
All these connections and error messages overload the Flows list with garbage, making difficult to complete the analysis over the interesting flows.

Questions and recommendations:
a)- May I suggest the creation of a global (not just for specific IP address ranges) temporary workaround or command line switch to be able to disable displaying these flows until HTTP/2 connections with prior knowledge is supported in mitmproxy? Current workaround:
 mitmproxy --mode transparent [--showhost] --ignore-hosts 172\.217\.\d+\.\d+ --ignore-hosts 216\.58\.\d+\.\d+

b)- Are there any plans to support HTTP/2 connections with prior knowledge in the mitmproxy roadmap? ETA?
Any other comments? What have you tried so far?
Disabling HTTP/2 support in mitmproxy via the "--no-http2" option does not solve the issue, as it seems the Android client keeps trying these connections as HTTP/2, with no prior negotiation.
System information
Kali Linux: mitmproxy --version
Mitmproxy: 4.0.4
Python:    3.6.5rc1
OpenSSL:   OpenSSL 1.1.0h  27 Mar 2018
Platform:  Linux-4.15.0-kali3-amd64-x86_64-with-Kali-kali-rolling-kali-rolling

For the record: The suggested workaround (item "a)" above) does not always work (although initially it seemed to work), as there are scenarios where the "PRI" and "Connection killed" entries (with the same IP address ranges) still appear in the Flows list, although they have been ignored (and mitmproxy reflects "Ignore:2") :(

currently facing this issue, would be happy to contribute in anyway i can.

@raulsiles Do you have any updates on this?
I'm using the "regular http proxy" and your first solution with the ignore host --ignore-hosts 172\.217\.\d+\.\d+ is indeed not working, but I think in my setup this is because I should use the hostname instead of the ip, as mentioned here.
BUT the --no-http2 option is working for me! thank you for that one! Maybe the option is not applicable for a transparent proxy?
I want to change my setup to transparent mode too, so it would be nice if there is any progress, or any idea how to solve this.

@HasBert I do not have any update on this. My testing setup is based on using transparent mode, therefore my initial description in this issue still applies (unless someone tells me there are new capabilities to fix it).

Hey @raulsiles
My "solution" was posted too early, the error occured right after I wrote my answer. So it was not working. This is the same error you noted in your description:

All these connections appear in the Flows list as shown, followed by a "Connection killed" error message (in red color):
PRI https://216.58.x.y HTTP/2.0

However, as you can see The HTTP Method is always PRI and the domain https://216.58.x.y or https://172.217.x.y.
I never saw a PRI http-method before, and read that it is a http2 specific method. It is mentiod in this thread.
The http2=boolean option does not solve this specific problem, the flows are the same. maybe that's because it's not supported yet? @mhils
Anyways if you filter your flows on http-method (PRI) with the options view_filter for mitmproxy and mitmweb, or dumper_filter for mitmdump, then you can dismiss this problem.
config.yml
view_filter: "!(~m PRI)"
#or
dumper_filter: "!(~m PRI)"

This options show every request with http-method NOT matching PRI. So you'll maybe miss some PRI request that would've worked on other URLs, if they work on other URLs.
I'm currently trying to get your regex 172\.217\.\d+\.\d+ to work with the ~d filter expression.
view_filter: "!(~d 172\.217\.\d+\.\d+)"

I'll let you know, if I get it to work. I have problems with the regex inside the config.yaml file. ;)

ahh, what about this as a root cause: HTTP2 clients are supposed to send: PRI * HTTP/2.0 as part of their connection preface. If there's a transparent proxy (or badly behaved client) that doesn't understand HTTP2, then normally it would transform GET /foo HTTP/1.0 (send via TLS) to GET https://<IP_ADDRESS>/foo HTTP/1.0 (to send via proxy). It applies the same transform to the HTTP2 request to get: PRI https://<IP_ADDRESS>* HTTP/2.0 (this is what I see from the Android emulator when it has a manual proxy configured)
So I'd guess that for these style of requests: mitmproxy should parse out the IP address, and use that as the upstream address.

Is this a limitation with hyper-h2 or MITM itself? Would be great if it could be solved as we have the same problem as @raulsiles : Iptables based transparent intercept and an Android app that uses Google's Firebase which makes use of prior knowledge HTTP/2 connections. Workaround for us is excluding the firebase API domains but then we lose intercept capability for these.

Not in scope for us - but happy to review a PR.


scipy.stats.mannwhitneyu function missing keyword argument : nan_policy

The nan_policy keyword argument does not appear to be written into the scipy.stats.mannwhitneyu function, but is present in the documentation..

Yes, it is accepted and handled by the _axis_nan_policy decorator.


Remove group concept from AvgHistogramFunction

Fix

[ ] Add a unit test to verify that the fix works.
[x] Explain briefly why the bug exists and how to fix it.

Remove group concept from AvgHistogramFunction. Heatmap(function result) doesn't support labels. FYI @wankai123

[ ] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
[x] Update the CHANGES log.

If labels left(not fully aggregated) when calling histogram, the new implementation will ignore them(in the group field), and aggregate them as multiple records.


Add handling to disable items on context menu

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes
Fixed #4499.
Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the forum/slack team.
[x] I have run npm run test to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Thank you!


bootstrap 5 scrollspy misbehaves if you reload on middle of a page

I have scrollspy in one of my pages. The scroll element is body.
It works all fine on the first load, but if you reload the page in the middle (scroll and then reload), all scrollspy stuff gets buggy !!

Well, all problems require a demo on codepen or jsfiddle.
Anyways, my question is placeholders also works with scrollspy?
Load placeholder on page scroll.
That would be excellent if it does.

Bug reports must include a live demo of the issue. Per our contributing guidelines, please create a reduced test case via CodePen or JS Bin and report back with your link, Bootstrap version, and specific browser and operating system details.

This is a saved reply.

bootstrap 5 scrollspy problem
This is the pen i wrote
to recreate the situation i am suffering from:

scroll to the middle of the page
in the console of codepen  run this window.location.reload()
after this reload checkout the scrollspy navbar :)