[BUG] Unable to create a new configuration file using redirection

ISSUE TYPE

Bug Report

SUMMARY
Unable to create a new configuration file using redirection.
You can try ansible-navigator config init -m stdout > ansible.cfg to reproduce it.
ANSIBLE-NAVIGATOR VERSION
ansible-navigator 3.4.3.dev6

CONFIGURATION
LOG FILE
STEPS TO REPRODUCE
Run ansible-navigator config init -m stdout > ansible.cfg
cat ansible.cfg

=
[defaults]
# (boolean) By default Ansible will issue a warning when received from a task action (module or action plugin)
# These warnings can be silenced by adjusting this setting to False.
action_warnings=True

# (list) Accept list of cowsay templates that are 'safe' to use, set to empty list if you want to enable all installed templates.
cowsay_enabled_stencils=bud-frogs, bunny, cheese, daemon, default, dragon, elephant-in-snake, elephant, eyes, hellokitty, kitty, luke-koal>

# (string) Specify a custom cowsay path or swap in your cowsay implementation of choice
cowpath=

# (string) This allows you to chose a specific cowsay stencil for the banners or use 'random' to cycle through them.
cow_selection=default

# (boolean) This option forces color mode even when running without a TTY or the "nocolor" setting is True.
force_color=False

# (path) The default root path for Ansible config files on the controller.
home=~/.ansible

# (boolean) This setting allows suppressing colorizing output, which is used to give a better indication of failure and status information.
nocolor=False

# (boolean) If you have cowsay installed but want to avoid the 'cows' (why????), use this.
nocows=False

# (boolean) Sets the default value for the any_errors_fatal keyword, if True, Task failures will be considered fatal errors.
any_errors_fatal=False

# (path) The password file to use for the become plugin. --become-password-file.
# If executable, it will be run and the resulting stdout will be used as the password.
become_password_file=

# (pathspec) Colon separated paths in which Ansible will search for Become Plugins.
become_plugins={{ ANSIBLE_HOME ~ "/plugins/become:/usr/share/ansible/plugins/become" }}

# (string) Chooses which cache plugin to use, the default 'memory' is ephemeral.
fact_caching=memory

# (string) Defines connection or path information for the cache plugin
fact_caching_connection=

# (string) Prefix to use for cache plugin files/tables
fact_caching_prefix=ansible_facts

# (integer) Expiration timeout for the cache plugin data
fact_caching_timeout=86400

# (list) List of enabled callbacks, not all callbacks need enabling, but many of those shipped with Ansible do as we don't want them activ>
callbacks_enabled=

# (string) When a collection is loaded that does not support the running Ansible version (with the collection metadata key `requires_ansib>
collections_on_ansible_version_mismatch=warning

# (pathspec) Colon separated paths in which Ansible will search for collections content. Collections must be in nested *subdirectories*, n>

collections_path={{ ANSIBLE_HOME ~ "/collections:/usr/share/ansible/collections" }}

# (boolean) A boolean to enable or disable scanning the sys.path for installed collections
collections_scan_sys_path=True

# (path) The password file to use for the connection plugin. --connection-password-file.
connection_password_file=

# (pathspec) Colon separated paths in which Ansible will search for Action Plugins.
action_plugins={{ ANSIBLE_HOME ~ "/plugins/action:/usr/share/ansible/plugins/action" }}

# (boolean) When enabled, this option allows lookup plugins (whether used in variables as ``{{lookup('foo')}}`` or as a loop as with_foo) >
# By default, such data is marked as unsafe to prevent the templating engine from evaluating any jinja2 templating language, as this could>
allow_unsafe_lookups=False

# (boolean) This controls whether an Ansible playbook should prompt for a login password. If using SSH keys for authentication, you probab>
ask_pass=False
:[defaults]
# (boolean) By default Ansible will issue a warning when received from a task action (module or action plugin)
# These warnings can be silenced by adjusting this setting to False.
action_warnings=True

# (list) Accept list of cowsay templates that are 'safe' to use, set to empty list if you want to enable all installed templates.
cowsay_enabled_stencils=bud-frogs, bunny, cheese, daemon, default, dragon, elephant-in-snake, elephant, eyes, hellokitty, kitty, luke-koal>

# (string) Specify a custom cowsay path or swap in your cowsay implementation of choice
cowpath=

# (string) This allows you to chose a specific cowsay stencil for the banners or use 'random' to cycle through them.
cow_selection=default

# (boolean) This option forces color mode even when running without a TTY or the "nocolor" setting is True.
force_color=False

# (path) The default root path for Ansible config files on the controller.
home=~/.ansible

# (boolean) This setting allows suppressing colorizing output, which is used to give a better indication of failure and status information.
nocolor=False

# (boolean) If you have cowsay installed but want to avoid the 'cows' (why????), use this.
nocows=False

# (boolean) Sets the default value for the any_errors_fatal keyword, if True, Task failures will be considered fatal errors.
any_errors_fatal=False

# (path) The password file to use for the become plugin. --become-password-file.
# If executable, it will be run and the resulting stdout will be used as the password.
become_password_file=

# (pathspec) Colon separated paths in which Ansible will search for Become Plugins.
become_plugins={{ ANSIBLE_HOME ~ "/plugins/become:/usr/share/ansible/plugins/become" }}
:[defaults]
# (boolean) By default Ansible will issue a warning when received from a task action (module or action plugin)
# These warnings can be silenced by adjusting this setting to False.
action_warnings=True

# (list) Accept list of cowsay templates that are 'safe' to use, set to empty list if you want to enable all installed templates.
cowsay_enabled_stencils=bud-frogs, bunny, cheese, daemon, default, dragon, elephant-in-snake, elephant, eyes, hellokitty, kitty, luke-koal>

# (string) Specify a custom cowsay path or swap in your cowsay implementation of choice
cowpath=

# (string) This allows you to chose a specific cowsay stencil for the banners or use 'random' to cycle through them.
cow_selection=default

# (boolean) This option forces color mode even when running without a TTY or the "nocolor" setting is True.
force_color=False

# (path) The default root path for Ansible config files on the controller.
home=~/.ansible

# (boolean) This setting allows suppressing colorizing output, which is used to give a better indication of failure and status information.
nocolor=False

# (boolean) If you have cowsay installed but want to avoid the 'cows' (why????), use this.
nocows=False

# (boolean) Sets the default value for the any_errors_fatal keyword, if True, Task failures will be considered fatal errors.
any_errors_fatal=False

# (path) The password file to use for the become plugin. --become-password-file.
# If executable, it will be run and the resulting stdout will be used as the password.
become_password_file=

# (pathspec) Colon separated paths in which Ansible will search for Become Plugins.
become_plugins={{ ANSIBLE_HOME ~ "/plugins/become:/usr/share/ansible/plugins/become" }}
:[defaults]
# (boolean) By default Ansible will issue a warning when received from a task action (module or action plugin)
# These warnings can be silenced by adjusting this setting to False.
action_warnings=True

# (list) Accept list of cowsay templates that are 'safe' to use, set to empty list if you want to enable all installed templates.
cowsay_enabled_stencils=bud-frogs, bunny, cheese, daemon, default, dragon, elephant-in-snake, elephant, eyes, hellokitty, kitty, luke-koal>

# (string) Specify a custom cowsay path or swap in your cowsay implementation of choice
cowpath=

# (string) This allows you to chose a specific cowsay stencil for the banners or use 'random' to cycle through them.
cow_selection=default

# (boolean) This option forces color mode even when running without a TTY or the "nocolor" setting is True.
force_color=False

# (path) The default root path for Ansible config files on the controller.
home=~/.ansible

# (boolean) This setting allows suppressing colorizing output, which is used to give a better indication of failure and status information.
nocolor=False

# (boolean) If you have cowsay installed but want to avoid the 'cows' (why????), use this.
nocows=False

# (boolean) Sets the default value for the any_errors_fatal keyword, if True, Task failures will be considered fatal errors.
any_errors_fatal=False

# (path) The password file to use for the become plugin. --become-password-file.
# If executable, it will be run and the resulting stdout will be used as the password.
become_password_file=

# (pathspec) Colon separated paths in which Ansible will search for Become Plugins.
become_plugins={{ ANSIBLE_HOME ~ "/plugins/become:/usr/share/ansible/plugins/become" }}

# (string) Chooses which cache plugin to use, the default 'memory' is ephemeral.
fact_caching=memory

# (string) Defines connection or path information for the cache plugin
fact_caching_connection=

# (string) Prefix to use for cache plugin files/tables
fact_caching_prefix=ansible_facts

# (integer) Expiration timeout for the cache plugin data
fact_caching_timeout=86400

# (list) List of enabled callbacks, not all callbacks need enabling, but many of those shipped with Ansible do as we don't want them activ>
callbacks_enabled=

# (string) When a collection is loaded that does not support the running Ansible version (with the collection metadata key `requires_ansib>
collections_on_ansible_version_mismatch=warning

# (pathspec) Colon separated paths in which Ansible will search for collections content. Collections must be in nested *subdirectories*, n>

collections_path={{ ANSIBLE_HOME ~ "/collections:/usr/share/ansible/collections" }}

# (boolean) A boolean to enable or disable scanning the sys.path for installed collections
collections_scan_sys_path=True

# (path) The password file to use for the connection plugin. --connection-password-file.
connection_password_file=

# (pathspec) Colon separated paths in which Ansible will search for Action Plugins.
action_plugins={{ ANSIBLE_HOME ~ "/plugins/action:/usr/share/ansible/plugins/action" }}

# (boolean) When enabled, this option allows lookup plugins (whether used in variables as ``{{lookup('foo')}}`` or as a loop as with_foo) >
# By default, such data is marked as unsafe to prevent the templating engine from evaluating any jinja2 templating language, as this could>
allow_unsafe_lookups=False

# (boolean) This controls whether an Ansible playbook should prompt for a login password. If using SSH keys for authentication, you probab>
ask_pass=False
:[defaults]
# (boolean) By default Ansible will issue a warning when received from a task action (module or action plugin)
# These warnings can be silenced by adjusting this setting to False.
action_warnings=True

# (list) Accept list of cowsay templates that are 'safe' to use, set to empty list if you want to enable all installed templates.
cowsay_enabled_stencils=bud-frogs, bunny, cheese, daemon, default, dragon, elephant-in-snake, elephant, eyes, hellokitty, kitty, luke-koal>

# (string) Specify a custom cowsay path or swap in your cowsay implementation of choice
cowpath=

# (string) This allows you to chose a specific cowsay stencil for the banners or use 'random' to cycle through them.
cow_selection=default

# (boolean) This option forces color mode even when running without a TTY or the "nocolor" setting is True.
force_color=False

# (path) The default root path for Ansible config files on the controller.
home=~/.ansible

# (boolean) This setting allows suppressing colorizing output, which is used to give a better indication of failure and status information.
nocolor=False

# (boolean) If you have cowsay installed but want to avoid the 'cows' (why????), use this.
nocows=False

# (boolean) Sets the default value for the any_errors_fatal keyword, if True, Task failures will be considered fatal errors.
any_errors_fatal=False

# (path) The password file to use for the become plugin. --become-password-file.
# If executable, it will be run and the resulting stdout will be used as the password.
become_password_file=

# (pathspec) Colon separated paths in which Ansible will search for Become Plugins.
become_plugins={{ ANSIBLE_HOME ~ "/plugins/become:/usr/share/ansible/plugins/become" }}

# (string) Chooses which cache plugin to use, the default 'memory' is ephemeral.
fact_caching=memory

# (string) Defines connection or path information for the cache plugin
fact_caching_connection=

# (string) Prefix to use for cache plugin files/tables
fact_caching_prefix=ansible_facts

# (integer) Expiration timeout for the cache plugin data
fact_caching_timeout=86400

# (list) List of enabled callbacks, not all callbacks need enabling, but many of those shipped with Ansible do as we don't want them activ>
callbacks_enabled=

# (string) When a collection is loaded that does not support the running Ansible version (with the collection metadata key `requires_ansib>
collections_on_ansible_version_mismatch=warning

# (pathspec) Colon separated paths in which Ansible will search for collections content. Collections must be in nested *subdirectories*, n>

collections_path={{ ANSIBLE_HOME ~ "/collections:/usr/share/ansible/collections" }}

# (boolean) A boolean to enable or disable scanning the sys.path for installed collections
collections_scan_sys_path=True

# (path) The password file to use for the connection plugin. --connection-password-file.
connection_password_file=

# (pathspec) Colon separated paths in which Ansible will search for Action Plugins.
action_plugins={{ ANSIBLE_HOME ~ "/plugins/action:/usr/share/ansible/plugins/action" }}

# (boolean) When enabled, this option allows lookup plugins (whether used in variables as ``{{lookup('foo')}}`` or as a loop as with_foo) >
# By default, such data is marked as unsafe to prevent the templating engine from evaluating any jinja2 templating language, as this could>
allow_unsafe_lookups=False

# (boolean) This controls whether an Ansible playbook should prompt for a login password. If using SSH keys for authentication, you probab>
ask_pass=False
:[defaults]
# (boolean) By default Ansible will issue a warning when received from a task action (module or action plugin)
# These warnings can be silenced by adjusting this setting to False.
action_warnings=True

# (list) Accept list of cowsay templates that are 'safe' to use, set to empty list if you want to enable all installed templates.
cowsay_enabled_stencils=bud-frogs, bunny, cheese, daemon, default, dragon, elephant-in-snake, elephant, eyes, hellokitty, kitty, luke-koal>

# (string) Specify a custom cowsay path or swap in your cowsay implementation of choice
cowpath=

# (string) This allows you to chose a specific cowsay stencil for the banners or use 'random' to cycle through them.
cow_selection=default

# (boolean) This option forces color mode even when running without a TTY or the "nocolor" setting is True.
force_color=False

# (path) The default root path for Ansible config files on the controller.
home=~/.ansible

# (boolean) This setting allows suppressing colorizing output, which is used to give a better indication of failure and status information.
nocolor=False

# (boolean) If you have cowsay installed but want to avoid the 'cows' (why????), use this.
nocows=False

# (boolean) Sets the default value for the any_errors_fatal keyword, if True, Task failures will be considered fatal errors.
any_errors_fatal=False

# (path) The password file to use for the become plugin. --become-password-file.
# If executable, it will be run and the resulting stdout will be used as the password.
become_password_file=

# (pathspec) Colon separated paths in which Ansible will search for Become Plugins.
become_plugins={{ ANSIBLE_HOME ~ "/plugins/become:/usr/share/ansible/plugins/become" }}

# (string) Chooses which cache plugin to use, the default 'memory' is ephemeral.
fact_caching=memory

# (string) Defines connection or path information for the cache plugin
fact_caching_connection=

# (string) Prefix to use for cache plugin files/tables
fact_caching_prefix=ansible_facts

# (integer) Expiration timeout for the cache plugin data
fact_caching_timeout=86400

# (list) List of enabled callbacks, not all callbacks need enabling, but many of those shipped with Ansible do as we don't want them activ>
callbacks_enabled=

# (string) When a collection is loaded that does not support the running Ansible version (with the collection metadata key `requires_ansib>
collections_on_ansible_version_mismatch=warning

# (pathspec) Colon separated paths in which Ansible will search for collections content. Collections must be in nested *subdirectories*, n>

collections_path={{ ANSIBLE_HOME ~ "/collections:/usr/share/ansible/collections" }}

# (boolean) A boolean to enable or disable scanning the sys.path for installed collections
collections_scan_sys_path=True

# (path) The password file to use for the connection plugin. --connection-password-file.
connection_password_file=

# (pathspec) Colon separated paths in which Ansible will search for Action Plugins.
action_plugins={{ ANSIBLE_HOME ~ "/plugins/action:/usr/share/ansible/plugins/action" }}

# (boolean) When enabled, this option allows lookup plugins (whether used in variables as ``{{lookup('foo')}}`` or as a loop as with_foo) >
# By default, such data is marked as unsafe to prevent the templating engine from evaluating any jinja2 templating language, as this could>
allow_unsafe_lookups=False

# (boolean) This controls whether an Ansible playbook should prompt for a login password. If using SSH keys for authentication, you probab>
ask_pass=False
:

EXPECTED RESULTS
It should been working like ansible-config init > ansible.cfg
ACTUAL RESULTS
Run ansible-navigator config init -m stdout > ansible.cfg
cat ansible.cfg

=
[defaults]
# (boolean) By default Ansible will issue a warning when received from a task action (module or action plugin)
# These warnings can be silenced by adjusting this setting to False.
action_warnings=True

# (list) Accept list of cowsay templates that are 'safe' to use, set to empty list if you want to enable all installed templates.
cowsay_enabled_stencils=bud-frogs, bunny, cheese, daemon, default, dragon, elephant-in-snake, elephant, eyes, hellokitty, kitty, luke-koal>

# (string) Specify a custom cowsay path or swap in your cowsay implementation of choice
cowpath=

# (string) This allows you to chose a specific cowsay stencil for the banners or use 'random' to cycle through them.
cow_selection=default

# (boolean) This option forces color mode even when running without a TTY or the "nocolor" setting is True.
force_color=False

# (path) The default root path for Ansible config files on the controller.
home=~/.ansible

# (boolean) This setting allows suppressing colorizing output, which is used to give a better indication of failure and status information.
nocolor=False

# (boolean) If you have cowsay installed but want to avoid the 'cows' (why????), use this.
nocows=False

# (boolean) Sets the default value for the any_errors_fatal keyword, if True, Task failures will be considered fatal errors.
any_errors_fatal=False

# (path) The password file to use for the become plugin. --become-password-file.
# If executable, it will be run and the resulting stdout will be used as the password.
become_password_file=

# (pathspec) Colon separated paths in which Ansible will search for Become Plugins.
become_plugins={{ ANSIBLE_HOME ~ "/plugins/become:/usr/share/ansible/plugins/become" }}

# (string) Chooses which cache plugin to use, the default 'memory' is ephemeral.
fact_caching=memory

# (string) Defines connection or path information for the cache plugin
fact_caching_connection=

# (string) Prefix to use for cache plugin files/tables
fact_caching_prefix=ansible_facts

# (integer) Expiration timeout for the cache plugin data
fact_caching_timeout=86400

# (list) List of enabled callbacks, not all callbacks need enabling, but many of those shipped with Ansible do as we don't want them activ>
callbacks_enabled=

# (string) When a collection is loaded that does not support the running Ansible version (with the collection metadata key `requires_ansib>
collections_on_ansible_version_mismatch=warning

# (pathspec) Colon separated paths in which Ansible will search for collections content. Collections must be in nested *subdirectories*, n>

collections_path={{ ANSIBLE_HOME ~ "/collections:/usr/share/ansible/collections" }}

# (boolean) A boolean to enable or disable scanning the sys.path for installed collections
collections_scan_sys_path=True

# (path) The password file to use for the connection plugin. --connection-password-file.
connection_password_file=

# (pathspec) Colon separated paths in which Ansible will search for Action Plugins.
action_plugins={{ ANSIBLE_HOME ~ "/plugins/action:/usr/share/ansible/plugins/action" }}

# (boolean) When enabled, this option allows lookup plugins (whether used in variables as ``{{lookup('foo')}}`` or as a loop as with_foo) >
# By default, such data is marked as unsafe to prevent the templating engine from evaluating any jinja2 templating language, as this could>
allow_unsafe_lookups=False

# (boolean) This controls whether an Ansible playbook should prompt for a login password. If using SSH keys for authentication, you probab>
ask_pass=False
:[defaults]
# (boolean) By default Ansible will issue a warning when received from a task action (module or action plugin)
# These warnings can be silenced by adjusting this setting to False.
action_warnings=True

# (list) Accept list of cowsay templates that are 'safe' to use, set to empty list if you want to enable all installed templates.
cowsay_enabled_stencils=bud-frogs, bunny, cheese, daemon, default, dragon, elephant-in-snake, elephant, eyes, hellokitty, kitty, luke-koal>

# (string) Specify a custom cowsay path or swap in your cowsay implementation of choice
cowpath=

# (string) This allows you to chose a specific cowsay stencil for the banners or use 'random' to cycle through them.
cow_selection=default

# (boolean) This option forces color mode even when running without a TTY or the "nocolor" setting is True.
force_color=False

# (path) The default root path for Ansible config files on the controller.
home=~/.ansible

# (boolean) This setting allows suppressing colorizing output, which is used to give a better indication of failure and status information.
nocolor=False

# (boolean) If you have cowsay installed but want to avoid the 'cows' (why????), use this.
nocows=False

# (boolean) Sets the default value for the any_errors_fatal keyword, if True, Task failures will be considered fatal errors.
any_errors_fatal=False

# (path) The password file to use for the become plugin. --become-password-file.
# If executable, it will be run and the resulting stdout will be used as the password.
become_password_file=

# (pathspec) Colon separated paths in which Ansible will search for Become Plugins.
become_plugins={{ ANSIBLE_HOME ~ "/plugins/become:/usr/share/ansible/plugins/become" }}
:[defaults]
# (boolean) By default Ansible will issue a warning when received from a task action (module or action plugin)
# These warnings can be silenced by adjusting this setting to False.
action_warnings=True

# (list) Accept list of cowsay templates that are 'safe' to use, set to empty list if you want to enable all installed templates.
cowsay_enabled_stencils=bud-frogs, bunny, cheese, daemon, default, dragon, elephant-in-snake, elephant, eyes, hellokitty, kitty, luke-koal>

# (string) Specify a custom cowsay path or swap in your cowsay implementation of choice
cowpath=

# (string) This allows you to chose a specific cowsay stencil for the banners or use 'random' to cycle through them.
cow_selection=default

# (boolean) This option forces color mode even when running without a TTY or the "nocolor" setting is True.
force_color=False

# (path) The default root path for Ansible config files on the controller.
home=~/.ansible

# (boolean) This setting allows suppressing colorizing output, which is used to give a better indication of failure and status information.
nocolor=False

# (boolean) If you have cowsay installed but want to avoid the 'cows' (why????), use this.
nocows=False

# (boolean) Sets the default value for the any_errors_fatal keyword, if True, Task failures will be considered fatal errors.
any_errors_fatal=False

# (path) The password file to use for the become plugin. --become-password-file.
# If executable, it will be run and the resulting stdout will be used as the password.
become_password_file=

# (pathspec) Colon separated paths in which Ansible will search for Become Plugins.
become_plugins={{ ANSIBLE_HOME ~ "/plugins/become:/usr/share/ansible/plugins/become" }}
:[defaults]
# (boolean) By default Ansible will issue a warning when received from a task action (module or action plugin)
# These warnings can be silenced by adjusting this setting to False.
action_warnings=True

# (list) Accept list of cowsay templates that are 'safe' to use, set to empty list if you want to enable all installed templates.
cowsay_enabled_stencils=bud-frogs, bunny, cheese, daemon, default, dragon, elephant-in-snake, elephant, eyes, hellokitty, kitty, luke-koal>

# (string) Specify a custom cowsay path or swap in your cowsay implementation of choice
cowpath=

# (string) This allows you to chose a specific cowsay stencil for the banners or use 'random' to cycle through them.
cow_selection=default

# (boolean) This option forces color mode even when running without a TTY or the "nocolor" setting is True.
force_color=False

# (path) The default root path for Ansible config files on the controller.
home=~/.ansible

# (boolean) This setting allows suppressing colorizing output, which is used to give a better indication of failure and status information.
nocolor=False

# (boolean) If you have cowsay installed but want to avoid the 'cows' (why????), use this.
nocows=False

# (boolean) Sets the default value for the any_errors_fatal keyword, if True, Task failures will be considered fatal errors.
any_errors_fatal=False

# (path) The password file to use for the become plugin. --become-password-file.
# If executable, it will be run and the resulting stdout will be used as the password.
become_password_file=

# (pathspec) Colon separated paths in which Ansible will search for Become Plugins.
become_plugins={{ ANSIBLE_HOME ~ "/plugins/become:/usr/share/ansible/plugins/become" }}

# (string) Chooses which cache plugin to use, the default 'memory' is ephemeral.
fact_caching=memory

# (string) Defines connection or path information for the cache plugin
fact_caching_connection=

# (string) Prefix to use for cache plugin files/tables
fact_caching_prefix=ansible_facts

# (integer) Expiration timeout for the cache plugin data
fact_caching_timeout=86400

# (list) List of enabled callbacks, not all callbacks need enabling, but many of those shipped with Ansible do as we don't want them activ>
callbacks_enabled=

# (string) When a collection is loaded that does not support the running Ansible version (with the collection metadata key `requires_ansib>
collections_on_ansible_version_mismatch=warning

# (pathspec) Colon separated paths in which Ansible will search for collections content. Collections must be in nested *subdirectories*, n>

collections_path={{ ANSIBLE_HOME ~ "/collections:/usr/share/ansible/collections" }}

# (boolean) A boolean to enable or disable scanning the sys.path for installed collections
collections_scan_sys_path=True

# (path) The password file to use for the connection plugin. --connection-password-file.
connection_password_file=

# (pathspec) Colon separated paths in which Ansible will search for Action Plugins.
action_plugins={{ ANSIBLE_HOME ~ "/plugins/action:/usr/share/ansible/plugins/action" }}

# (boolean) When enabled, this option allows lookup plugins (whether used in variables as ``{{lookup('foo')}}`` or as a loop as with_foo) >
# By default, such data is marked as unsafe to prevent the templating engine from evaluating any jinja2 templating language, as this could>
allow_unsafe_lookups=False

# (boolean) This controls whether an Ansible playbook should prompt for a login password. If using SSH keys for authentication, you probab>
ask_pass=False
:[defaults]
# (boolean) By default Ansible will issue a warning when received from a task action (module or action plugin)
# These warnings can be silenced by adjusting this setting to False.
action_warnings=True

# (list) Accept list of cowsay templates that are 'safe' to use, set to empty list if you want to enable all installed templates.
cowsay_enabled_stencils=bud-frogs, bunny, cheese, daemon, default, dragon, elephant-in-snake, elephant, eyes, hellokitty, kitty, luke-koal>

# (string) Specify a custom cowsay path or swap in your cowsay implementation of choice
cowpath=

# (string) This allows you to chose a specific cowsay stencil for the banners or use 'random' to cycle through them.
cow_selection=default

# (boolean) This option forces color mode even when running without a TTY or the "nocolor" setting is True.
force_color=False

# (path) The default root path for Ansible config files on the controller.
home=~/.ansible

# (boolean) This setting allows suppressing colorizing output, which is used to give a better indication of failure and status information.
nocolor=False

# (boolean) If you have cowsay installed but want to avoid the 'cows' (why????), use this.
nocows=False

# (boolean) Sets the default value for the any_errors_fatal keyword, if True, Task failures will be considered fatal errors.
any_errors_fatal=False

# (path) The password file to use for the become plugin. --become-password-file.
# If executable, it will be run and the resulting stdout will be used as the password.
become_password_file=

# (pathspec) Colon separated paths in which Ansible will search for Become Plugins.
become_plugins={{ ANSIBLE_HOME ~ "/plugins/become:/usr/share/ansible/plugins/become" }}

# (string) Chooses which cache plugin to use, the default 'memory' is ephemeral.
fact_caching=memory

# (string) Defines connection or path information for the cache plugin
fact_caching_connection=

# (string) Prefix to use for cache plugin files/tables
fact_caching_prefix=ansible_facts

# (integer) Expiration timeout for the cache plugin data
fact_caching_timeout=86400

# (list) List of enabled callbacks, not all callbacks need enabling, but many of those shipped with Ansible do as we don't want them activ>
callbacks_enabled=

# (string) When a collection is loaded that does not support the running Ansible version (with the collection metadata key `requires_ansib>
collections_on_ansible_version_mismatch=warning

# (pathspec) Colon separated paths in which Ansible will search for collections content. Collections must be in nested *subdirectories*, n>

collections_path={{ ANSIBLE_HOME ~ "/collections:/usr/share/ansible/collections" }}

# (boolean) A boolean to enable or disable scanning the sys.path for installed collections
collections_scan_sys_path=True

# (path) The password file to use for the connection plugin. --connection-password-file.
connection_password_file=

# (pathspec) Colon separated paths in which Ansible will search for Action Plugins.
action_plugins={{ ANSIBLE_HOME ~ "/plugins/action:/usr/share/ansible/plugins/action" }}

# (boolean) When enabled, this option allows lookup plugins (whether used in variables as ``{{lookup('foo')}}`` or as a loop as with_foo) >
# By default, such data is marked as unsafe to prevent the templating engine from evaluating any jinja2 templating language, as this could>
allow_unsafe_lookups=False

# (boolean) This controls whether an Ansible playbook should prompt for a login password. If using SSH keys for authentication, you probab>
ask_pass=False
:[defaults]
# (boolean) By default Ansible will issue a warning when received from a task action (module or action plugin)
# These warnings can be silenced by adjusting this setting to False.
action_warnings=True

# (list) Accept list of cowsay templates that are 'safe' to use, set to empty list if you want to enable all installed templates.
cowsay_enabled_stencils=bud-frogs, bunny, cheese, daemon, default, dragon, elephant-in-snake, elephant, eyes, hellokitty, kitty, luke-koal>

# (string) Specify a custom cowsay path or swap in your cowsay implementation of choice
cowpath=

# (string) This allows you to chose a specific cowsay stencil for the banners or use 'random' to cycle through them.
cow_selection=default

# (boolean) This option forces color mode even when running without a TTY or the "nocolor" setting is True.
force_color=False

# (path) The default root path for Ansible config files on the controller.
home=~/.ansible

# (boolean) This setting allows suppressing colorizing output, which is used to give a better indication of failure and status information.
nocolor=False

# (boolean) If you have cowsay installed but want to avoid the 'cows' (why????), use this.
nocows=False

# (boolean) Sets the default value for the any_errors_fatal keyword, if True, Task failures will be considered fatal errors.
any_errors_fatal=False

# (path) The password file to use for the become plugin. --become-password-file.
# If executable, it will be run and the resulting stdout will be used as the password.
become_password_file=

# (pathspec) Colon separated paths in which Ansible will search for Become Plugins.
become_plugins={{ ANSIBLE_HOME ~ "/plugins/become:/usr/share/ansible/plugins/become" }}

# (string) Chooses which cache plugin to use, the default 'memory' is ephemeral.
fact_caching=memory

# (string) Defines connection or path information for the cache plugin
fact_caching_connection=

# (string) Prefix to use for cache plugin files/tables
fact_caching_prefix=ansible_facts

# (integer) Expiration timeout for the cache plugin data
fact_caching_timeout=86400

# (list) List of enabled callbacks, not all callbacks need enabling, but many of those shipped with Ansible do as we don't want them activ>
callbacks_enabled=

# (string) When a collection is loaded that does not support the running Ansible version (with the collection metadata key `requires_ansib>
collections_on_ansible_version_mismatch=warning

# (pathspec) Colon separated paths in which Ansible will search for collections content. Collections must be in nested *subdirectories*, n>

collections_path={{ ANSIBLE_HOME ~ "/collections:/usr/share/ansible/collections" }}

# (boolean) A boolean to enable or disable scanning the sys.path for installed collections
collections_scan_sys_path=True

# (path) The password file to use for the connection plugin. --connection-password-file.
connection_password_file=

# (pathspec) Colon separated paths in which Ansible will search for Action Plugins.
action_plugins={{ ANSIBLE_HOME ~ "/plugins/action:/usr/share/ansible/plugins/action" }}

# (boolean) When enabled, this option allows lookup plugins (whether used in variables as ``{{lookup('foo')}}`` or as a loop as with_foo) >
# By default, such data is marked as unsafe to prevent the templating engine from evaluating any jinja2 templating language, as this could>
allow_unsafe_lookups=False

# (boolean) This controls whether an Ansible playbook should prompt for a login password. If using SSH keys for authentication, you probab>
ask_pass=False
:

ADDITIONAL INFORMATION
I had fixed it at https://github.com/ansible/ansible-runner/pull/1306

In the meantime, you can override the PAGER environment variable in the EE, which will allow the file to be written without any prompting:
ansible-navigator config init -m stdout --senv PAGER=cat > file.txt

(this could also be put in the navigator config file)

Let us know if this works for you, we could consider conditionally setting the environment variable by default for the user if we detect config init
BTW- is ee support is disabled the senv won't work, it would need to be done like this before the proc
PAGER=cat ansible-navigator config init -m stdout --ee false


Filter out the extra fields with no additional info in Cleveland Museum metadata

Fixes
Fixes https://github.com/WordPress/openverse-catalog/issues/825 by @AetherUnbound
Description
This PR removes the default empty string assignment to metadata, while extracting metadata fields from input data object.
So that all the None value fields would be filtered out at the second to last line of the _get_metadata function, resulting in only metadata fields which has info.
Testing Instructions
Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[x] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[ ] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Looks like linting is still failing, you can address this by running just lint locally and committing the changes.


clean:content command

I was wondering if we should put a warning before the command because it could be quite destructive.

👍 @bastianallgeier


Welcome to dbus-serialbattery Discussions!

Discussed in https://github.com/Louisvdw/dbus-serialbattery/discussions/55

Originally posted by Louisvdw September 30, 2021
👋 Welcome!
We’re using Discussions as a place to connect with other members of our community. We hope that you:

Ask questions you’re wondering about.
Assist others.
Share ideas.
Engage with other community members.
Welcome others and are open-minded. Remember that this is a community we
build together 💪.

To get started, comment below with an introduction of yourself and tell us about what BMS/Battery you use. We also love to see pictures of your system if you have.

Sorry did it wrong.


Add solved property in problems model

Add a property 'solved' to show how many people have solved that particular problem.

yeah but submissions will generally be very high on such a website .. so don't u think it's better to just store it instead of querying the whole db @Vishal1541  ?

@vsvipul I have currently implemented it using query: http://localhost:3000/problems/all (solved column) and closing this issue for now. We can discuss it and come up with some better approach, if possible, because we also need to show which users have solved that problem.


Remove use of zero-length arrays.

Resolves #1564.

Codecov Report

Merging #1570 into master will increase coverage by 1.51%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #1570      +/-   ##
==========================================
+ Coverage   69.63%   71.15%   +1.51%
==========================================
  Files         157      152       -5
  Lines       20130    18357    -1773
  Branches     2483     2262     -221
==========================================
- Hits        14018    13062     -956
+ Misses       5216     4485     -731
+ Partials      896      810      -86

Impacted Files
Coverage Δ

src/core/thread/network_diagnostic.cpp
3.96% <0%> (ø)
:arrow_up:

src/core/thread/network_diagnostic_tlvs.hpp
0% <0%> (ø)
:arrow_up:

examples/platforms/posix/misc.c
0% <0%> (-66.67%)
:arrow_down:

src/core/api/icmp6_api.cpp
50% <0%> (-50%)
:arrow_down:

src/ncp/spinel.c
52.4% <0%> (-24.7%)
:arrow_down:

src/core/net/ip6.hpp
66.66% <0%> (-22.23%)
:arrow_down:

src/core/coap/coap_client.cpp
50% <0%> (-19.07%)
:arrow_down:

src/core/api/ip6_api.cpp
41.93% <0%> (-17.75%)
:arrow_down:

src/core/mac/mac_whitelist.cpp
76.59% <0%> (-17.03%)
:arrow_down:

src/core/coap/coap_client.hpp
57.89% <0%> (-15.79%)
:arrow_down:

... and 24 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 009dd36...87d926d. Read the comment docs.


Please maintain the module

It was a great tool I've used in various projects.
It's very helpful to maintain the images by this module
but nowadays I am not able to upload image with a new version of Yii,
Please maintain if possible
Thanks

I'm sorry, I'm to busy for maintenance the module. I don't work a lot with PHP these days. So feel free to fork it or use other forks to develop futher

Thank you, Thank you!


Added Zeal version 0.6.1.

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

Microsoft Reviewers: Open in CodeFlow

Oof. I'll close this until the issue is fixed.


Problem during the downloading of the generated mp3 file

I have problems with the generated mp3 file. It is too short and it is not a valid mp3 file.
Are you experiencing the same issue?
Best regards!

Solved with this commit https://github.com/areski/python-acapela/commit/ba5d60b0ef589edb275631e6282a3e45f8d5c9f9


How to set Content-Disposition & Content-Encoding with S3 TransferManager?

I can't seem to figure out how to set the Content-Disposition or Content-Encoding headers for files uploaded to S3 with the TransferManager.
If I try to use "metadata" all of my headers are prefixed with "x-amz-meta", which is not desired.
The TransferHandle has a SetContentType method, but no SetContentDisposition or SetContentEncoding methods.
PutObjectRequest does have a SetContentDisposition & SetContentEncoding, so it seems like it should be possible somehow?
How is this accomplished with TransferManager & UploadFile?
Which version of the SDK?
commit 0e0a8ea5aee8d4616e8b5ca0ef4a561b6d217521
Author: aws-sdk-cpp-automation<EMAIL_ADDRESS>Date:   Tue Apr 30 19:34:04 2019 +0000

Use TransferManagerConfiguration::putObjectTemplate.
/**
 * If you have special arguments you want passed to our put object calls, put them here. We will copy the template for each put object call
 * overriding the body stream, bucket, and key. If object metadata is passed through, we will override that as well.
 */
Aws::S3::Model::PutObjectRequest putObjectTemplate;

Thanks for that. I'll poke around to see if this can be made dynamic. It does appear though at first glance that this will apply the same settings to all files uploaded through this manager?
I'm trying to upload a bunch of disparate files with individual dispositions & content types.

It does appear though at first glance that this will apply the same settings to all files uploaded through this manager?

Correct.

I'm trying to upload a bunch of disparate files with individual dispositions & content types.

You can't do that with the current implementation.

We might have to do something like this: https://github.com/aws/aws-sdk-cpp/pull/944/ but also add content-disposition.
Adding new parameters is not scalable though, we'll have to pass a struct with all the options/settings.

So yeah, I had to make a fork and add the support myself.
Obviously, it'd be done somewhat differently if it were to make it in to the aws owned repo (these changes break the interface by adding more parameters)
https://github.com/leolabs-space/aws-sdk-cpp/commits/headers-for-transfer-manager-upload

Agree about passing in a struct. Its not really clear to me why I can't pass them in the metadata in the first place though, honestly. It seems weird that x-amz- is added to all the header names.

Another approach I considered is allowing the user to specify a PutObjectRequest factory function for each upload.

@chrisrosner Were you ever able to set Content-Disposition via putObjectTemplate in the TransferManagerConfiguration? ... putObjectTemplate.SetContentDisposition(R"(attachment; filename="file.pdf";)") just doesn't seem to work and as you pointed out, setting the metadata in the transfer itself unexpectedly prepends "x-amz-" to the field name.

No, unfortunately the only option I saw was to fork the repo and and to
make a low effort patch.
On Mon, Jun 1, 2020, 4:52 AM nickdademo<EMAIL_ADDRESS>wrote:

@chrisrosner https://github.com/chrisrosner Were you ever able to set
Content-Disposition via putObjectTemplate in the
TransferManagerConfiguration? ... putObjectTemplate.SetContentDisposition(R"(attachment;
filename="file.pdf";)") just doesn't seem to work and as you pointed out,
setting the metadata in the transfer itself unexpectedly prepends "x-amz-"
to the field name.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aws/aws-sdk-cpp/issues/1151#issuecomment-636812775,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGHLZDBJ5JEJJ7GCOSH5KHTRUOJANANCNFSM4HRSLDIA
.

@chrisrosner That's unfortunate! Perhaps I will do the same.
@marcomagdy Is this putObjectTemplate method to set the ContentDisposition expected to work?


cask/artifact/moved: fix permission handling when removing directories

While target.parent.writable? is a sufficient check if we can remove a file or an empty directory, it is insufficient to test whether we can remove the entire directory tree as the directory itself and all non-empty recursive subdirectories will need write permissions. Utils.gain_permissions_remove already handles this for us so use it unconditionally.
Note that using Utils.gain_permissions_remove doesn't mean that sudo will always be used - it will still try to remove without sudo if possible.

Not entirely sure why there's a test that expects uninstalling to fail? Seems really weird to only raise permission for files but not directories.

Seems really weird to be perfectly ok raising permission if the parent directory isn't writable but not if a child directory is.

Agreed.


MGB Contrast Wheel

Gekkio,
I was checking your schematic for the MGB. I’m new to this so I don’t understand that much. I have an MGB and the contrast wheel doesn’t work. It was working before but not anymore. I need your help trying to diagnose what could it be. I change the contrast wheel with a new one but the issue persist.
Respectfully,
George

Hello,
This is not really the best place to ask for repair/modding/diagnostics help. I recommend the /r/gameboy reddit, or even better, its Discord server (https://discord.gg/gameboy). There are many knowledgeable people there (including me), and it's much easier to have a discussion there instead of here in a random Github issue very few people will read :slightly_smiling_face:


EBS Volume from other volume does not obey most_recent_snapshot

I'm creating an EBS volume by using a volume ID as the initial snapshot_id in the resource. Even with most_recent_snapshot set to true, the oldest snapshot is always used.
aws_ebs_volume 'aem_ebs_volume' do
size 1000
device '/dev/sdi'
volume_type 'gp2'
most_recent_snapshot true
action [:create, :attach]
snapshot_id 'vol-a1b2c3d4'
end
Any ideas?

encountered same issue here too.

This issue should be fixed from my changes so i think it can be closed


Sythetic Data uses DataProfiler ; but pins scipy==1.8.0 while dataprofiler uses scipy>=1.10.0

General Information:

OS: Linux
Python version: 3.10
Library version: dataprofiler=0.10.5 &  synthetic-data=1.2.1

Describe the bug:
Dependencies of synthetic data are scipy==1.8.0  and dataprofiler, but DataProfiler has scipy>=1.10.0
numpy>=1.22
scikit-learn>=1.1.0
scipy==1.8.0
dataprofiler>=0.8.8

https://github.com/capitalone/DataProfiler/blob/main/requirements.txt#L13
scipy>=1.10.0
https://github.com/capitalone/synthetic-data/blob/main/requirements.txt#L3
scipy==1.8.0
dataprofiler>=0.8.8

https://github.com/capitalone/DataProfiler/blob/main/requirements-ml.txt#L1
scikit-learn>=0.23.2
To use these the two together - DataProfiler[full] + synthetic-data

probably makes sense to remove scipy from synthetic (it will inherit and match the needed dependency form data profiler.
If we want to retain scipy, we should make it >=1.10.0 and that will atleast ensures pip manages to resolve faster without overriding

To Reproduce:
Expected behavior:
Screenshots:
Additional context:
https://github.com/capitalone/synthetic-data/pull/342

@taylorfturner - Do you have any idea when the next release is planned for - Just trying to get an idea of when this change will make it to PyPi. Thank you.

Hey @rxm7706 -- thanks for the ping. Yes, next week we will be doing a deployment of capitalone/DataProfiler -- can probably do a release of this repo as well. Thanks!

@rxm7706 Release conducted last week. Thanks!


Fix chat header shows split creator and split user avatar briefly when splitting expense

Details

When creating a new split bill, we include the current user as the participant of the 1:1 chat, so the avatar shows 2 user. The BE then returns the correct participant.
Fixed Issues

$ https://github.com/Expensify/App/issues/40904
PROPOSAL: https://github.com/Expensify/App/issues/40904#issuecomment-2075286998
Tests

Same as QA Steps

[x] Verify that no errors appear in the JS console

Offline tests

Same as QA Steps
QA Steps

Create a new split bill with 1 user with whom you never chatted before
Verify the avatar in the chat header shows a single avatar of the user

[x] Verify that no errors appear in the JS console

PR Author Checklist

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/50919443/fd976b14-7edb-4d17-909b-c7a82918e9f8

Android: mWeb Chrome

https://github.com/Expensify/App/assets/50919443/aae09540-7b18-41ee-a0ba-155078c6192e

iOS: Native

https://github.com/Expensify/App/assets/50919443/6e6c1ae9-7219-4d52-99bc-53b4e6fba0a7

iOS: mWeb Safari

https://github.com/Expensify/App/assets/50919443/aeee52ea-7b16-49c7-83f9-08cd569f5677

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/50919443/1822a5ce-2ed2-45e6-ba9c-708272ea1cde

MacOS: Desktop

https://github.com/Expensify/App/assets/50919443/69d4436d-6c28-4a7a-9c4a-c4db981ee3d1

🚀 Deployed to staging by https://github.com/madmax330 in version: 1.4.74-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/chiragsalian in version: 1.4.74-6 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Make javaslang.collection.Iterator a Traversable

To do this, we (re-)add TraversableOnce. All methods of Traversable are move to TraversableOnce and Traversable extends TraversableOnce.
Then Iterator extends TraversableOnce.
Additionally we add two methods to TraversableOnce:

boolean hasDefiniteSize() // Iterator, Stream , Gen and Arbitrary return(s) false, all others return true
boolean isTraversableAgain() // Iterator returns false, all (others) return true

Note: TraversableOnce has undefined size and is not traversable again by definition.

Add zip*/unzip to Iterator.  More methods missing? Look at https://github.com/scala/scala/blob/v2.12.0-M2/src/library/scala/collection/Iterator.scala


networkd: also load builtin modules

Motivation for this change
Things done

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

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

What will change as the result?

Systemd comes with default units for systemd-nspawn interfaces:
lrwxrwxrwx  54 root 29 Sep  9:55 80-container-host0.network -> /etc/static/systemd/network/80-container-host0.network
lrwxrwxrwx  51 root 29 Sep  9:55 80-container-ve.network -> /etc/static/systemd/network/80-container-ve.network
lrwxrwxrwx  51 root 29 Sep  9:55 80-container-vz.network -> /etc/static/systemd/network/80-container-vz.network
lrwxrwxrwx  43 root 29 Sep  9:55 99-default.link -> /etc/static/systemd/network/99-default.link

However I currently chase down a NixOS-specific bug, where Driver=veth never matches.

This is an off-topic comment admittedly, but neat trick with attrNames and readDir - I hadn't thought of that pattern but can easily see where that will make things much cleaner. Thanks @Mic92!

The bug in systemd still exists, but I know why. So lets merge it.

@Mic92: stable network interfaces got broken (or the test): https://hydra.nixos.org/build/70356440  I haven't yet looked into the real reasons.

@vcunat ah, I have to rethink this. https://github.com/NixOS/nixpkgs/pull/33617 would be also required for this.

reverted in a5dcde1a6fb3d5d1b8c29a46fd5926de1640ab45 for the time beeing


Jitter shadow map dithering pattern across frames when TAA is enabled

Supersedes: https://github.com/godotengine/godot/pull/61834
This closes https://github.com/godotengine/godot-proposals/issues/4179 and closes https://github.com/godotengine/godot/issues/53534.
Credit to @Calinou who did most of the work. I just did some final cleanup to improve the quality before it was ready to merge
I ended up rebasing while working on the improvements described in https://github.com/godotengine/godot/pull/61834#issuecomment-2372215710 so I figured it was less work overall for us to open a new PR.
This PR builds on the current state of https://github.com/godotengine/godot/pull/61834, see that PR for a full description/history

Will the improved documentation of this comment of yours in https://github.com/godotengine/godot/pull/61834

We need to document that FSR2.2 at 1.0 scale is more sensitive to high contrast areas than TAA or FSR2.2 at lower scales as this will impact many users.

be included in another PR? I think it wouldn't be obvious why these artifacts will be found in various strengths in different locations in a level so documenting it would be great.

Will the improved documentation of this comment of yours in #61834

We need to document that FSR2.2 at 1.0 scale is more sensitive to high contrast areas than TAA or FSR2.2 at lower scales as this will impact many users.

be included in another PR? I think it wouldn't be obvious why these artifacts will be found in various strengths in different locations in a level so documenting it would be great.

Yes, the docs are hosted in a separate repository. So the documentation update will necessarily be in another PR

Thanks!


Upgraded to RN 0.48.

Now trying for RN 0.49 😄

👍

Maybe you can also upgrade react. We are still using the alpha version at the moment.

React's version is whatever peerDependency the React Native has with the given release. They still haven't moved to 16.0.0 final, so we shouldn't either.

Looks like it works. Merging.


Unity3D - Camera Rendering Upside Down

Describe the bug

With certain Unity titles, the final image will render upside-down.  This occurs only to certain titles on the engine.

Tested with Xuan-Yuan Sword 6: The Gate of Firmament

DXVK-Remix abdd865
Bridge-Remix 9833d09
GPU: Nvidia Geforce RTX 3080

Driver: Nvidia Studio Driver 536.67

Steam - Latest Release

To Reproduce
Steps to reproduce the behavior:

Open Xuan-Yuan Sword 6: The Gate of Firmament on Steam
Make sure the game is set to Fullscreen in settings, then close the game

If Remix is enabled, only use fullscreen mode; see #178

Set up DXVK-Remix and Bridge-Remix accordingly (a basic rtx.conf with UI tags is included)
All in-engine gameplay will render upside-down while the HUD remains the correct direction.

rtxconf.zip
Other known affected titles:

Dreadout
Gang Beasts Alpha 0.0.3

Unity titles NOT affected:

Ravenfield (Alpha builds)
Slender
Deus Ex: The Fall
Shadowrun Returns

Expected behavior
Unity normally compensates for this behavior in its own renderer, and behavior is inconsistent-- in some Unity games, the camera remains facing the correct direction.  We may need a manual toggle to flip the final image, rasterized elements included (if the HUD is flipped) or to manually add a 180 degrees pitch/yaw turn to the final camera output (if only the 3D scene is flipped).
Screenshots

REMIX-2064 for tracking.


Release 5.0.0

Signed-off-by: Seth Thomas<EMAIL_ADDRESS>Description
[Describe what this change achieves]
Issues Resolved
[List any existing issues this PR resolves]
Check List

[x] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[x] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable
[x] All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

is there any 'breaking' change? the jump to 5.x is irritating me if I look at the changelog

anyways. I really appreciate seeing progress in with the cookbook :-)

maybe jenkins 2 support? I'm also very thankful!

@ehaselwanter there are definitely a few things that would be considered breaking

stable is now default for grabbing builds and update-center
jvm_options are set for 2.x by default
since it's 2.x you'll want to check out the test recipe for the plugins needed that were moved out of core

I'll review and make some notes since I can call this out better like I've done for some other recent major rewrites. Most of the changes were in the service of 2.x support or fixing things that were inherently broken (bad urls, dpkg_autostart).


Bump live-common with latest socket implementation

For the test plan, Please refer to
https://github.com/LedgerHQ/lld-v2/pull/164
it will be similar but we need to test in both iOS and Android because known implementation difference we noticed in the past.

Nano X (latest firmware) on Android & iOS:

[x] Refusing allow manager
[x] Disconnecting device in various time of the flow (lockscreen + bluetooth off)
[x] Opening the app in the middle of the flow
[x] Interrupting the entering of manager and coming back to it
[x] interrupting the apps installation
[x] network down at the beginning of the flow
[x] network down in the middle => Connection failed (websocket error)

ccaf77b2 (HEAD -> live-common-socket-rework, gre/live-common-socket-rework) Bump live-common with latest socket implementation


feat: implement solidjs adapter for v8 alpha

This PR implements a solidjs adapter for react-table v8 alpha as discussed in this twitter thread https://twitter.com/tannerlinsley/status/1511336168008212481.

Would love to see the fork submitted to SolidHack (https://hack.solidjs.com read the submission guidelines). A small demo site would help with retaining votes for your submission!

I'm sorry @Mokshit06, I don't see this PR before submitting my own PR #3801. But, my PR focus first on modifying the core to work well with Solid signal reactivity primitive. Maybe we can collaborate?

Thanks @izznatsir, I overlooked that we need to keep the options also reactive, but do we really need to modify the core to work well with solid? Would helpers like mergeProps from solid-js help with retaining reactivity for options?

I've pushed another commit that adds a mergeOptions function arg to the options, which was one of the things breaking reactivity, because initially it was doing Object.assign which would call all the getters eagerly. Now the adapter can specify how it wants to merge the options, and the solid adapter creates a proxy with mergeProps which lazily searches for keys from the objects passed.
I think that adding accessor API to the core might convolute the API since now only a few properties are functions and others are primitives. Rather we can just tell the user to use getters wherever they want to make the property reactive like:
const instance = createTable(table, {
    get data() {
        return data()
    },
    columns: columns()
})

Here the data is a lazy getter and will be reactive, whereas columns would not get updated.
It also updates uses of event.persist() to first check it exists because its only available in react.

Wow, that's cool! Definitely much cleaner approach. Let me play around with it to see if there is something missed.

I've had to comment out the /** @jsxImportSource solid-js */ for now because it's causing some compilation issues on the build:
➜  react-table (alpha) ✗ yarn build
yarn run v1.22.11
$ rollup --config rollup.config.js && tsc -b

/Users/tannerlinsley/GitHub/react-table/packages/table-core/src/index.tsx → packages/table-core/build/esm...
created packages/table-core/build/esm in 3.3s

/Users/tannerlinsley/GitHub/react-table/packages/table-core/src/index.tsx → packages/table-core/build/cjs...
created packages/table-core/build/cjs in 3.1s

/Users/tannerlinsley/GitHub/react-table/packages/table-core/src/index.tsx → packages/table-core/build/umd/index.development.js...
created packages/table-core/build/umd/index.development.js in 3.9s

/Users/tannerlinsley/GitHub/react-table/packages/table-core/src/index.tsx → packages/table-core/build/umd/index.production.js...
 index.production.js ⏤  14.8 kB
created packages/table-core/build/umd/index.production.js in 6.5s

/Users/tannerlinsley/GitHub/react-table/packages/react-table/src/index.tsx → packages/react-table/build/esm...
created packages/react-table/build/esm in 317ms

/Users/tannerlinsley/GitHub/react-table/packages/react-table/src/index.tsx → packages/react-table/build/cjs...
created packages/react-table/build/cjs in 321ms

/Users/tannerlinsley/GitHub/react-table/packages/react-table/src/index.tsx → packages/react-table/build/umd/index.development.js...
created packages/react-table/build/umd/index.development.js in 294ms

/Users/tannerlinsley/GitHub/react-table/packages/react-table/src/index.tsx → packages/react-table/build/umd/index.production.js...
 index.production.js ⏤  995 B
created packages/react-table/build/umd/index.production.js in 2.2s

/Users/tannerlinsley/GitHub/react-table/packages/solid-table/src/index.tsx → packages/solid-table/build/esm...
[!] (plugin babel) SyntaxError: /Users/tannerlinsley/GitHub/react-table/packages/solid-table/src/index.tsx: importSource cannot be set when runtime is classic.
> 1 | /** @jsxImportSource solid-js */
    | ^
  2 | import {
  3 |   AnyGenerics,
  4 |   CreateTableFactoryOptions,
packages/solid-table/src/index.tsx
SyntaxError: /Users/tannerlinsley/GitHub/react-table/packages/solid-table/src/index.tsx: importSource cannot be set when runtime is classic.
> 1 | /** @jsxImportSource solid-js */
    | ^
  2 | import {
  3 |   AnyGenerics,
  4 |   CreateTableFactoryOptions,
    at File.buildCodeFrameError (/Users/tannerlinsley/GitHub/react-table/node_modules/@babel/core/lib/transformation/file/file.js:249:12)
    at NodePath.buildCodeFrameError (/Users/tannerlinsley/GitHub/react-table/node_modules/@babel/traverse/lib/path/index.js:139:21)
    at PluginPass.enter (/Users/tannerlinsley/GitHub/react-table/node_modules/@babel/plugin-transform-react-jsx/lib/create-plugin.js:143:28)
    at newFn (/Users/tannerlinsley/GitHub/react-table/node_modules/@babel/traverse/lib/visitors.js:177:21)
    at NodePath._call (/Users/tannerlinsley/GitHub/react-table/node_modules/@babel/traverse/lib/path/context.js:53:20)
    at NodePath.call (/Users/tannerlinsley/GitHub/react-table/node_modules/@babel/traverse/lib/path/context.js:40:17)
    at NodePath.visit (/Users/tannerlinsley/GitHub/react-table/node_modules/@babel/traverse/lib/path/context.js:100:31)
    at TraversalContext.visitQueue (/Users/tannerlinsley/GitHub/react-table/node_modules/@babel/traverse/lib/context.js:103:16)
    at TraversalContext.visitSingle (/Users/tannerlinsley/GitHub/react-table/node_modules/@babel/traverse/lib/context.js:77:19)
    at TraversalContext.visit (/Users/tannerlinsley/GitHub/react-table/node_modules/@babel/traverse/lib/context.js:131:19)

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I'll need some help fixing those issues (which I am very unfamiliar with) before we can uncomment that line.

We would need solid's babel plugin to compile its jsx to js, since it isn't using the standard jsx transform. But I think since we're just having one jsx element inside the render function, we might as well change it to createComponent call, which is what it would get transformed into

Yep, babel is currently transpiling it to the following, which wouldn't work:
function render(Comp, props) {
  if (!Comp) return null;

  if (typeof Comp === 'function') {
    return /*#__PURE__*/React.createElement(Comp, props);
  }

  return Comp;
}

Should I create a new PR for fixing this issue?

#3840 fixes this


[Android] Task Canceled Exception thrown when suspending app during Purchase flow

Bug Information
Version Number of Plugin: 5.1.0
Device Tested On: Pixel 3 (Android 12) emulator and Moto G7 Play (Android 10) actual device
Version of VS: 2019 16.11.9
Version of Xamarin: <IP_ADDRESS>7
Google Play store version: 29.1.10-21
Steps to reproduce the Behavior
Call PurchaseAsync(), so that the Google Play purchase window opens.
Before tapping the button to subscribe press the device home button. Then return to the app. Notice a Task Canceled Exception is thrown.
Expected Behavior
Suspending the app and then returning to the app when the Google Play window is showing should not cause a Task Canceled Exception.
Actual Behavior
Suspending the app and then returning to the app when the Google Play window is showing throws a Task Canceled Exception. Note, there are links on the Google Play window for viewing the Terms of Service, etc., and so it would be a completely expected workflow to suspend the app at this point, then return.
Code snippet
Screenshots

This was an issue of calling ConnectAsync when I was already connected. Needed to use the IsConnected property to check if we need to call ConnectAsync upon resuming the app.


BUG: Make dict iterators real iterators, provide "next()" in Python 2

Currently, compat.itervalues and friends are not real iterators (under Python 3): compare
In [3]: next(six.itervalues({1:2}))
Out[3]: 2

with
In [4]: next(pd.compat.itervalues({1:2}))
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-4-177f5d3e9571> in <module>()
----> 1 next(pd.compat.itervalues({1:2}))

TypeError: 'dict_values' object is not an iterator

This PR fixes this (it drops support for **kwargs: although it is supported by six, I fail to see what's the utility, and it's anyway apparently not used in the pandas codebase - but if I'm missing something, it is trivial to reintroduce it) and provides next() in Python 2.

Why don't we just use the six code almost directly?
if PY3:
    def iterkeys(d, **kw):
        return iter(d.keys(**kw))

    def itervalues(d, **kw):
        return iter(d.values(**kw))

    def iteritems(d, **kw):
        return iter(d.items(**kw))

    def iterlists(d, **kw):
        return iter(d.lists(**kw))

    viewkeys = operator.methodcaller("keys")

    viewvalues = operator.methodcaller("values")

    viewitems = operator.methodcaller("items")
else:
    def iterkeys(d, **kw):
        return d.iterkeys(**kw)

    def itervalues(d, **kw):
        return d.itervalues(**kw)

    def iteritems(d, **kw):
        return d.iteritems(**kw)

    def iterlists(d, **kw):
        return d.iterlists(**kw)

    viewkeys = operator.methodcaller("viewkeys")

    viewvalues = operator.methodcaller("viewvalues")

    viewitems = operator.methodcaller("viewitems")

Makes sense, except that you could not use anymore compat.iteritems(NDFrame), given that NDFrame.iter is not callable (while the six Python 3 version expects it to be so, since dict.iter is).
But still the right thing to do is probably to (also) change each compat.iteritems(NDFrame) to iter(NDFrame.iteritems()). There aren't tons of them.
(then, I still fail to understand the **kw thing, but never mind)

yeh the compat was done a long time ago, its possible the actual six code was changed since then (to be better) and we have the original. ok with these kinds of changes (e.g. they do a slightly better check for next compat)

the keyword argument passing is needed to generate the correct error messages.

... I still don't understand: which error messages?

when you pass a keyword argument, the real function gets to tell you that it doesn't need any.  the other error messages still are wrong tho.  but these things are not super important

Got it!

Above, I clearly made a mistake writing NDFrame.iter rather than NDFrame.items, and anyway it is not NDFrame, but only Series and DataFrame.
That said, I ended up

making my compat code semantically equivalent to six - but tell me if you also want it more verbose
changing compat.iter*(obj) to obj.iter*() only when obj was an NDFrame with ndim (possibly) >2

What I didn't do but may be worth doing in the medium/long run:

changing compat.iter*(obj) to obj.iter*() whenever obj is an NDFrame (and in the short run, not using the former in new code)
removing Series.items() and DataFrame.items() (they are aliases for iteritems(), not even documented)

It is true that one driver of the decision is to avoid problems with features (Panel, in which  items is an axis) which will be probably deprecated... but I don't see any downside (apart from a minor one: we are sticking to Python 2-sounding method names).

Is anything expected from me here?

write out all of the other methods there strongly a couple instead of evaluating them at run time

ping

thanks @toobaz


[SQL Lab] Backtick in SQL preview query making it fail when user only have schema access

When user is only granted schema access, preview query is generated in from of SCHEMA_NAME.TABLE_NAME which failed the query.
Expected results
Preview query success when user only have schema access.
Actual results
Preview query failed
Screenshots

How to reproduce the bug

Grant only schema access to user
Go to SQLLab
Choose the DB and the granted schema
Choose any table.
See the error.

Environment
(please complete the following information):

superset version: > 1.1 (current master) (<1.1 should also have this problem)
python version: 3.7

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

This can be fixed by either:

Changing the sql_parse to strip backtick.
Changing the frontend to make the query without backtick.

duplicate for #14233

Closing in favor of https://github.com/apache/superset/issues/14233


Fix: job start fail

Proposed Changes

job start fail
error buy data token

The test deployment failed for some subgraph-related reason, I just restarted it in Netlify and it worked on the second try. You can see the preview here.
Think the dev branch needs a bump commit to refresh the Netlify actions but I don't have privileges to do it.


Resolves #1732

Fix example 2 and New-CimSession link.
https://github.com/MicrosoftDocs/windows-powershell-docs/issues/1732

Docs Build status updates of commit 7f11975:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/hyper-v/New-VM.md
:white_check_mark:Succeeded

docset/winserver2012-ps/hyper-v/New-VM.md
:white_check_mark:Succeeded

docset/winserver2012r2-ps/hyper-v/New-VM.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

cc @dariomws @get-itips @tseward


Eclipse generate throws IllegalAccessError when generating from source code

Expected behavior
As a CobiGen Eclipse user, I want CobiGen to complete the generate process when generating from JPA entity inside the source code. Not from the project explorer.
Actual behavior
Nothing gets generated. In the worst case, Eclipse throws an IllegalAccessError.
Steps to reproduce (bug) / Use Case of feature request (enhancement)

Go inside the source code of the file you want to generate from.
Select for example the class name and right click.
Select cobigen->generate.

The getActiveWorkbenchWindow loops really long in: https://github.com/devonfw/cobigen/blob/d955e2898331723e77e7660c5454557077870541/cobigen-eclipse/cobigen-eclipse/src/com/devonfw/cobigen/eclipse/common/tools/PlatformUIUtil.java#L47-L52 which gets called from here: https://github.com/devonfw/cobigen/blob/d955e2898331723e77e7660c5454557077870541/cobigen-eclipse/cobigen-eclipse/src/com/devonfw/cobigen/eclipse/generator/GeneratorWrapperFactory.java#L103-L114

Hey team! Please add your planning poker estimate with ZenHub @GuentherJulian @jan-vcapgemini @mdukhan


Feature/9 option menu worlds

This is the world switcher
Use
_world.getResource<resources::EngineResource>().engine->setScene<game::SettingsMenuScene>();
and replace SettingsMenuScene by your scene to switch scenes

Almost good for me, but switchScene should be called after each drawFrame by the engine itself instead of being called by the scenes. Only one switchScene afer _scene->drawFrame() and we're done for all the scenes.

I can't because of enscriptem's loop


migrate pending mixpanel properties => hubspot

events

[x] Applying CartoCSS style manually
[x] Applying color as basemap
[x] Applying a pattern as basemap
[x] Applying filter
[x] Choose a wizard
[x] Click Publish Visualization
[x] Common data clicked
[x] Dashboard viewed
[x] Dashboard viewed for the first time
[x] Exported table data
[x] Geocoding failed <- This should be Geocoding and save the status as metadata
[x] Performing a query
[x] Use visual merge
[x] Import successful <- Save format, size and duration?
[x] WMS layer selected
[x] Visited Login page
[x] Logged in
[x] Open create table
[x] Open create map

Contact properties removed, can be inferred from current events

[ ] success_import_count
[ ] publish_visualization_last_clicked
[ ] table_count
[ ] visualization_count
[ ] failed_import_count
[ ] last_visualization_created_at

Tracked but not listed

[x] Geocoding admin
[x] Geocoding zip
[x] Geocoding world
[x] Geocoding namedplace
[x] Geocoding latlng
[x] Geocoding ip
[x] Geocoding address

Discarded?

[x] Import started
[x] Import failed
[x] Marker file chosen for line-color
[x] New color chose for marker-fill
[x] New color chosen for polygon-fill
[x] Pattern file chosen for polygon  fill
[x] View byebye page
[x] View Climate Page
[x] Marked Spam
[x] login_count login_count

Moved from El Soto to Baeza.

@matallo there's a js exception around these lines:
https://github.com/CartoDB/cartodb/blob/2735-hubspot/lib/assets/javascripts/cartodb/dashboard/entry.js#L124-L128
(cannot read property trigger of undefined)


Monthly Chat Agendas December (2020-12-07 and 2020-12-21)

This is the Agenda for the Monthly CRS Chats.
The general chat is going to happen on https://owasp.slack.com in the channel #coreruleset on Monday, December 7th, at 20:30 CET. That's the 1st Monday of the month. A separate issue chat is happening at the same location, same time on Monday, December 21st. That's the 3rd Monday of the month.
Items on the Agenda:  (see previous meetings decisions: here)
What happend in the meantime since the chat in early November

#1946 Update Nextcloud rules (reimplementation of #1902) - merged
#1925 Remove .axd from restricted extensions - merged
#1920 WordPress Site Health Exclusion Rule - merged
#1913 Fix stricter sibling comment for SQL Injection - merged
#1915 Monitoring tools exclusion - closed since the directives used don't work that way
#1910 Rebase PR #1794 - merged
#1901 Permit "version" string in content-type header - merged
#1899 FP in Wordpress - merged
#1846 feat(ftw): use master to get py3 support - closed and superseded by #1934
#1783 New SQLi rule - merged

PRs
environment

#1936 feat(ci): use relative paths in testing - failing tests
#1934 feat(ci): upgrades ftw to python 3 supported version - failing tests
#1906 Fixing and improving environment for testing (docker/nginx) - this brings 2 welcome bugfixes, but it also incorporates partial nginx coverage

rules

#1911 Possible fix issue 1883 - reviewer needed, we asked @fgsch, but only lately
#1887 Eliminate FPs in 932100: Rescheduled from last meeting. @piotrpazola has provided the tests we asked for, but the PR adds a look-behind regexp...
#1941 Shifting everything to phase:1 where possible (move item to the end of the PR block of the agenda)

PRs marked "work in progress" / needs action

#1938 V3.4/dev ftw main - draft
#1930 feat(ci): add test plugin to annotate failures - draft
#1929 Fixed regex for match IPv6 addr syntax - conversation about ipv6 continues
#1868 Migrate PR: RE2 compatibility for 921120 - still waiting for @dune73's blog post about it
#1845 Stop decoding things twice - still conflicting / waiting for a fix by @fgsch
#1817 Fix false positives with rule 942360

Other items

Talk about new ModSecurityv3 bug behind #1941. How to react? Do we create a phase 1 sibling of 949110 (and one for its 959100 counterpart)?
Update from the sponsoring front
Status CRS demo site
Do we want to make a try with video call monthly meeting?

Open Issues - Separate Issues Meeting (Monday, December 21st)
We generally cover 10 issues per month in a separate issue meeting. Add them as you see fit.

Issue slot 1: #1950 FP 949110 - cookie with (*.)/(.*) in value
Issue slot 2: #1942 Rule 941310: false positive for Russian letters "м" and "о"
Issue slot 3: #1931 932115 triggered by a URL containing a query string parameter of "sort"
Issue slot 4: #1922 Rules blocking Google OAuth2 redirect (callback) URLs
Issue slot 5: #1914 FP for "case" in Rule 942230
Issue slot 6: #1912 Rule 951260
Issue slot 7: #1905 False positives from 931100, 931120, and 931130 #1905
Issue slot 8:
Issue slot 9:
Issue slot 10:

How to get to our slack and join the meeting?
If you are not yet on the OWASP Slack, here is your invite: https://owasp-slack.herokuapp.com/ .
Everybody is welcome to join our community chat.

Decisions
PRs

Decisions
PRs

Issue slot 1: #1950 FP 949110 - cookie with (*.)/(.*) in value
Issue slot 2: #1942 Rule 941310: false positive for Russian letters "м" and "о" (@franbuehler)
Issue slot 3: #1931 932115 triggered by a URL containing a query string parameter of "sort" (@franbuehler)
Issue slot 4: #1922 Rules blocking Google OAuth2 redirect (callback) URLs
Issue slot 5: #1914 FP for "case" in Rule 942230 (@franbuehler)
Issue slot 6: #1912 Rule 951260
Issue slot 7: #1905 False positives from 931100, 931120, and 931130 #1905
Issue slot 8:
Issue slot 9:
Issue slot 10:


[Hammer] Realtime stats and events

The Hammer has various ad-hoc stats and measurements about what's going on with the target log, but this could probably do with a bit of a more holistic rethink about how it's all plumbed together.

Hopefully #125 makes the backbone of the plumbing clearer. Resolving this for now as I think it has been refactored to approximately the right shape.


support Chinese?

Chinese can be easily supported using the trainer please check docs

thanks! but no Chinese pre-weight in your project ,will you offer later?


Adding RuleResult from Initialize method

Loving this library :-)
For certain rules (with expensive external calls etc) I'd like to skip them if the rule was previously run within say the last 10 minutes. This is easy to do by adding a constraint in the rule initialization method.
I would however like to add a rule result that reports the rule was skipped, and the last execution time (so if the rule runs again in say 10 minutes time the rule will be executed).
As the RuleResults collection is private, I don't think I can add a rule result form the Initialize method.
I'd like your advice on whether you think it's preferable to:
Modify the source to make the ruleresults collection public (or add a public method to add a rule result etc.)
Or
Forget about using Configuration.Constraints in the Initialize method, and just do these checks within the rule execution.
The second option is obviously easiest, but it is kind of counter-intuitive and I like the separation of concerns by splitting the configuration and the actual rule processing. I do realise it's kind of odd to have a rule result when the rule hasn't actually run.
Any thoughts?

Hi Ben,
I’m glad you liking the lib. There are various ways of going about this. And probably depends on how you want to approach it. However this is what I would do.
Add a rule that has two nested rules. One of the nested rules would have a constraint that it would execute the expensive call and returns a rule result that the expensive call was executed. Other nested rule constraint would match the expensive call was already executed (n) minutes ago and returns rule result that the expensive call didn’t not get executed.
This way you would continue maintaining separation of concern by introducing rules that do one thing only.
I hope that helps.
Cheers,


Delete the breaking change tag in issue

Breaking Changes should be announced, instead to be reported as an issue.

done

Please delete the breaking change label in the issue too, which was created by you before.


libp11-kit.so.0: no version information available

The latest build of bucket-antivirus-function started to give me the following:
./bin/freshclam: /usr/lib64/libp11-kit.so.0: no version information available (required by ./bin/libgnutls.so.28)
./bin/clamscan: /usr/lib64/libp11-kit.so.0: no version information available (required by ./bin/libgnutls.so.28)
The function itself still works, but just providing those warnings after updating w/ clamav 0.103.6, would anyone know whats needed to resolve this?

Same issue here.

The updated Dockerfile from https://github.com/bluesentry/bucket-antivirus-function/pull/204 fixed this issue on my side


License?

Hi! I want to package this for the Arch User Repositories (AUR) and I was wondering if you'd settled on a license for the app.

I'll look into a few options tomorrow when I have some free time :). I'm really only familiar with MIT, so it'll likely be along those lines. At any rate, I'll get back to you shortly.

Cool, thanks!

Just added a simple MIT License.


Fix: refresh context for UnauthorizedRequest from Bing

Resolve #629
When token is expired, Bing will return such message
{"type":2,"invocationId":"1","item":{"firstNewMessageIndex":null,"defaultChatName":null,"result":{"value":"UnauthorizedRequest","message":"Token issued by https://sydney.bing.com/sydney is invalid (IDX10223: Lifetime validation failed. The token is expired. ValidTo (UTC): '12/8/2023 3:48:23 AM', Current time (UTC): '12/8/2023 3:58:42 AM'.)","error":"UnauthorizedRequest","renewCert":true,"serviceVersion":"20231207.96"}}}
There should be other scenarios for UnauthorizedRequest, I'm not sure whether it's appropriate to use it for direct comparison, what is your opinion ? @sunner

Perhaps, a relogin is required?

For the UnauthorizedRequest scenario, either a relogin or the creation of a new conversation is necessary. Consider the following solution:

Attempt to create a new conversation and retry the operation.
If successful, proceed with the remaining steps.
If the attempt fails, display an error message and advise the user to perform a relogin.

The crucial implementation step involves adding a retry flag to the context and utilizing it for both retry attempts and error display. This flag serves the additional purpose of preventing an infinite recursion loop in the chat.
If you agree with this approach, I will proceed with the implementation.

Thank you  @samanhappy for the detailed deep thinking. But IMO, the solution is too smart. I prefer showing the error message and let the user determine what to do  next. Just as Bing Chat's behavior.

When using Bing Chat, user won't get an UnauthorizedRequest message or have to relogin for expired token, so I think Bing Chat has implemented a similar solution.

Hi @PeterDaveHello , what is your opinion about this issue?

@samanhappy I'm not sure if creating a new conversation is needed, but if it is, then we can try your solution.


ARM64 support

Hey !
I'd like to "local test" kctf but my machine is running ARM64 and kctf doesn't support it :/ Is it planned ?
Thanks !
Eban

Hey there,
We're currently not working on this. Do you happen to know what's required
for ARM support?
One thing I can think of is the binaries that we're using for kind etc:
https://github.com/google/kctf/blob/v1/dist/activate#L16
And then I guess we would have to build our docker images for arm64 too.
On Tue, Jun 21, 2022 at 1:09 PM Eban @.***> wrote:

Hey !
I'd like to "local test" kctf but my machine is running ARM64 and kctf
doesn't support it :/ Is it planned ?
Thanks !
Eban
—
Reply to this email directly, view it on GitHub
https://github.com/google/kctf/issues/378, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEM2JHW3OMTFXJ24MZPV5MDVQGPGDANCNFSM5ZL5YISQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>