add cartopy package

Add cartopy to the list of embedded libraries in the Sepal Python environment. Cartopy is a python package designed to produce maps and other geospatial data analyses.

cartopy requires python >=3.9. So this is pending #297.

Since Sepal is now running python 3.10.12 as per #297, I would like to reiterate this feature request.

what is preventing you from installing this package in your environment as suggested here: https://docs.sepal.io/en/latest/cli/python.html#customization ?


NTP on Container Linux baremetal

Bug
Environment

Platform: bare-metal
OS: container-linux
Release: v1.13.4
Terraform: v0.11.11
Plugins: terraform-provider-matchbox v0.2.3

Problem
I have rook-0.9.3 (ceph) install on my cluster and it works well but am getting ntp errors "clock skew 0.420116s > max 0.05s" that I would like to resolve.  I have internal NTP servers that I would like to use but I am unsure how to get the cluster to use them.
I wrote a script that forced timesyncd to use my time-servers but I believe typesyncd is not accurate enough for ceph so want to try using ntpd instead. Unfortunatly am having trouble configuring NTP from within coreos so thought I would be best to ask here.
Desired Behavior
Enable a Typhoon cluster use a specific internal ntp server/s.

Hey Keith, Container Linux hosts provision themselves according to a Container Linux Config. See the Container Linux docs on customizing your NTP upstreams. Typhoon has a unique feature to accept a list of Container Linux Config snippets that will be validated and merged into the main config, so you can provide a snippet for that purpose without Typhoon needing a special feature.

Hope that guides you in the right direction. If you arrive at a useful CLC snippet and feel comfortable, it could help future askers to post it.

Hi, I wasn't aware of snippets, but they were simple to implement and worked perfectly each time !!cheers!!!
For me switching from timesyncd to ntpd didn't fix our ceph time problem because ntpd still wouldn't use the correct servers (I think this is a container Linux problem) so we're stuck with timesyncd.
I run the below snippets separately but I guess you can combine them into one ? Although I am a bit wary of screwing up the boot process and having to take a unplanned day trip to our datacetner. (We have cheap Dell ipmi cards that aren't the best).
Below are the snippets I am using for setting the timesyncd time servers and for wiping our data disks at boot time.
storage:
files:
- path: /etc/systemd/timesyncd.conf
filesystem: root
mode: 0644
contents:
inline: |
[Time]
NTP=0.primary-timeserver.com 1.another-timeserver.com
storage:
disks:
- device: "/dev/sdb"
wipe_table: true
- device: "/dev/sdc"
wipe_table: true
If someone else has the same ceph time issue then I also found that running the following on each nodes resolved our time drifting issue.
sudo timedatectl set-ntp true
sudo ntpdate primary-timeserver.com
sudo hwclock -w

You can combine or divide snippets as desired, whatever makes sense. An Ignition document served to a machine is one document, so its the same result either way. Hopefully you end up finding a declarative way to do what you're hoping for eventually without scripting.

@Keithsc, I also had the same problem with Ceph reporting clock skew with timesyncd. I switched to ntpd and this solved the clock skew messages for me. This is the snippet I'm using:
# The Ceph monitor processes seem to have a problem with the way timesyncd
# synchronizes time and are reporting "clow skew". Switch to NTP.
# Configure at least four NTP servers to be able to detect a falseticker
# even when one of the other servers isn't reachable (anymore).
#
systemd:
  units:
    - name: systemd-timesyncd.service
      mask: true
    - name: ntpd.service
      enable: true

storage:
  files:
    - path: /etc/ntp.conf
      filesystem: root
      contents:
        inline: |
          server 0.coreos.pool.ntp.org
          server 1.coreos.pool.ntp.org
          server 2.coreos.pool.ntp.org
          server 3.coreos.pool.ntp.org
          restrict default nomodify nopeer noquery notrap limited kod
          restrict <IP_ADDRESS>
          restrict [::1]

Is there a reason why you want to merge your different snippets? I've quite a few of these snippets each in a different file and feed these into the Typhoon module with some terraform magic . Each snippet/file corresponds to one system tweak which I then can enable for each system individually. clc_snippets for bare-metal were a godsend and saved me a lot of manual patching of the Typhoon module.


Add two config properties to disable the add-topic-partition procedure and the topic-reassig-partition-and-leader-elect procedure respectively

Config props added:

topic-management.topicAddPartitionEnabled
topic-management.topicReassignPartitionAndElectLeaderEnabled

Both default to true for backward compatibility.

Is this being separated because CC won't create additional partitions, but it will move leadership and otherwise do "balancing"?

Is this being separated because CC won't create additional partitions, but it will move leadership and otherwise do "balancing"?

Yes. CC does not have the feature to add partition(s) for a topic currently. So we need to continue relying on KMF to add partitions for KMF topics.
This change gives us the option to stop KMF from rebalancing KMF topics and the rebalancing job will be done by CC (see PR)


2024-10-26 — 1 new commit(s) made to reference.md in Google Transit's repo

Commit Nº 1
AUTHOR × DATE

Sergio Delgado Rodriguez ( Sergiodero )
October 25, 2024   @   10:08 AM ETC (02:08 PM UTC)

MESSAGE
Update revision history (October 2024) (#513)
* Update RT revision history
* Adjust formatting on Schedule Revision History
* Update Schedule Reference latest revision date

FILES CHANGED

https://github.com/google/transit/commit/eb71ab1ce08857ed9b8b9e082a1f4c794c7c2d1c

https://github.com/google/transit/commit/eb71ab1ce08857ed9b8b9e082a1f4c794c7c2d1c

Editorial changes, no implications for the validator.


Internal Server Error 500 when choosing a Search Provider with MySQL backend

I have set up Scumblr with the SQLite default database/'development' environment and it works fine.
Today I set up a new environment except with MySQL as backend and using the 'production' environment. I configured the providers with the exact same API keys etc as the first environment.
When I go to create a new Search with any provider (Google Search, or Twitter for example), I find that the form doesn't automatically change to displaying the provider-specific fields (e.g 'Max results / search specific user' for Twitter, or 'Custom Search id (cx)' for Google).
After choosing Google Search or Twitter Search from the drop-down combo, I see this in my production.log:
Error (24d5dfde-eca6-4731-a8e3-ae3c6512a544): NoMethodError  in ProvidersController#options
undefined method `[]' for #<OpenStruct>

Full Trace:
/opt/scumblr/Scumblr/app/views/providers/_options_fields.html.erb:5:in `block (2 levels) in _app_views_providers__options_fields_html_erb__744959149249925282_55089640'
/opt/scumblr/Scumblr/app/views/providers/_options_fields.html.erb:2:in `each'
/opt/scumblr/Scumblr/app/views/providers/_options_fields.html.erb:2:in `block in _app_views_providers__options_fields_html_erb__744959149249925282_55089640'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/helpers/capture_helper.rb:38:in `block in capture'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/helpers/capture_helper.rb:200:in `with_output_buffer'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/helpers/capture_helper.rb:38:in `capture'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/helpers/form_helper.rb:699:in `fields_for'
/opt/scumblr/Scumblr/app/views/providers/_options_fields.html.erb:1:in `_app_views_providers__options_fields_html_erb__744959149249925282_55089640'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/template.rb:143:in `block in render'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.9/lib/active_support/notifications.rb:161:in `instrument'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/template.rb:141:in `render'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/renderer/partial_renderer.rb:306:in `render_partial'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/renderer/partial_renderer.rb:279:in `block in render'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/renderer/abstract_renderer.rb:38:in `block in instrument'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.9/lib/active_support/notifications.rb:159:in `block in instrument'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.9/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.9/lib/active_support/notifications.rb:159:in `instrument'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/renderer/abstract_renderer.rb:38:in `instrument'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/renderer/partial_renderer.rb:278:in `render'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/renderer/renderer.rb:47:in `render_partial'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/renderer/renderer.rb:21:in `render'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/helpers/rendering_helper.rb:24:in `render'
/opt/scumblr/Scumblr/app/views/providers/options.js.erb:1:in `_app_views_providers_options_js_erb___2938630473595440416_52625300'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/template.rb:143:in `block in render'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.9/lib/active_support/notifications.rb:161:in `instrument'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/template.rb:141:in `render'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/renderer/template_renderer.rb:49:in `block (2 levels) in render_template'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/renderer/abstract_renderer.rb:38:in `block in instrument'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.9/lib/active_support/notifications.rb:159:in `block in instrument'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.9/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.9/lib/active_support/notifications.rb:159:in `instrument'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/renderer/abstract_renderer.rb:38:in `instrument'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/renderer/template_renderer.rb:48:in `block in render_template'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/renderer/template_renderer.rb:56:in `render_with_layout'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/renderer/template_renderer.rb:47:in `render_template'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/renderer/template_renderer.rb:17:in `render'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/renderer/renderer.rb:42:in `render_template'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_view/renderer/renderer.rb:23:in `render'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/abstract_controller/rendering.rb:127:in `_render_template'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_controller/metal/streaming.rb:219:in `_render_template'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/abstract_controller/rendering.rb:120:in `render_to_body'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_controller/metal/rendering.rb:33:in `render_to_body'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_controller/metal/renderers.rb:26:in `render_to_body'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/abstract_controller/rendering.rb:97:in `render'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_controller/metal/rendering.rb:16:in `render'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_controller/metal/instrumentation.rb:41:in `block (2 levels) in render'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.9/lib/active_support/core_ext/benchmark.rb:12:in `block in ms'/usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'                                                                                [
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.9/lib/active_support/core_ext/benchmark.rb:12:in `ms'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_controller/metal/instrumentation.rb:41:in `block in render'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_controller/metal/instrumentation.rb:84:in `cleanup_view_runtime'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activerecord-4.0.9/lib/active_record/railties/controller_runtime.rb:25:in `cleanup_view_runtime'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_controller/metal/instrumentation.rb:40:in `render'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_controller/metal/mime_responds.rb:191:in `respond_to'
/opt/scumblr/Scumblr/app/controllers/providers_controller.rb:28:in `options'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/abstract_controller/base.rb:189:in `process_action'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_controller/metal/rendering.rb:10:in `process_action'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/abstract_controller/callbacks.rb:18:in `block in process_action'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.9/lib/active_support/callbacks.rb:413:in `_run__3162839066334499664__process_action__callbacks'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.9/lib/active_support/callbacks.rb:80:in `run_callbacks'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/abstract_controller/callbacks.rb:17:in `process_action'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_controller/metal/rescue.rb:29:in `process_action'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_controller/metal/instrumentation.rb:31:in `block in process_action'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.9/lib/active_support/notifications.rb:159:in `block in instrument'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.9/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.9/lib/active_support/notifications.rb:159:in `instrument'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activerecord-4.0.9/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/abstract_controller/base.rb:136:in `process'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/abstract_controller/rendering.rb:44:in `process'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_controller/metal.rb:195:in `dispatch'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_controller/metal.rb:231:in `block in action'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_dispatch/routing/route_set.rb:82:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_dispatch/routing/route_set.rb:82:in `dispatch'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_dispatch/routing/route_set.rb:50:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_dispatch/journey/router.rb:71:in `block in call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_dispatch/journey/router.rb:59:in `each'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_dispatch/journey/router.rb:59:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_dispatch/routing/route_set.rb:676:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/warden-1.2.3/lib/warden/manager.rb:35:in `block in call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/warden-1.2.3/lib/warden/manager.rb:34:in `catch'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/warden-1.2.3/lib/warden/manager.rb:34:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/etag.rb:23:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/conditionalget.rb:25:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/head.rb:11:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_dispatch/middleware/flash.rb:241:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:225:in `context'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:220:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_dispatch/middleware/cookies.rb:486:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activerecord-4.0.9/lib/active_record/query_cache.rb:36:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activerecord-4.0.9/lib/active_record/connection_adapters/abstract/connection_pool.rb:626:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.9/lib/active_support/callbacks.rb:373:in `_run__3542382758811078735__call__callbacks'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.9/lib/active_support/callbacks.rb:80:in `run_callbacks'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_dispatch/middleware/remote_ip.rb:76:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/railties-4.0.9/lib/rails/rack/logger.rb:38:in `call_app'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/railties-4.0.9/lib/rails/rack/logger.rb:20:in `block in call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.9/lib/active_support/tagged_logging.rb:68:in `block in tagged'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.9/lib/active_support/tagged_logging.rb:26:in `tagged'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.9/lib/active_support/tagged_logging.rb:68:in `tagged'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/railties-4.0.9/lib/rails/rack/logger.rb:20:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/methodoverride.rb:21:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/runtime.rb:17:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.9/lib/active_support/cache/strategy/local_cache.rb:83:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/sendfile.rb:112:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.9/lib/action_dispatch/middleware/ssl.rb:24:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/railties-4.0.9/lib/rails/engine.rb:511:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/railties-4.0.9/lib/rails/application.rb:97:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/railties-4.0.9/lib/rails/railtie/configurable.rb:30:in `method_missing'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/lint.rb:49:in `_call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/lint.rb:37:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/showexceptions.rb:24:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/commonlogger.rb:33:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:217:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/chunked.rb:43:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/content_length.rb:14:in `call'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:576:in `process_client'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:670:in `worker_loop'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:525:in `spawn_missing_workers'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:140:in `start'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/gems/unicorn-4.8.3/bin/unicorn:126:in `<top (required)>'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/bin/unicorn:23:in `load'
/opt/scumblr/Scumblr/vendor/bundle/ruby/1.9.1/bin/unicorn:23:in `<main>'

Request:
{"provider"=>"SearchProvider::Google",
 "action"=>"options",
 "controller"=>"providers"}
  Rendered shared/_notification.html.erb (0.1ms)
  Rendered shared/_ajax_error.js.erb (0.4ms)
Completed 500 Internal Server Error in 21ms (Views: 0.8ms | ActiveRecord: 0.2ms)
Started GET "/searches/events" for <IP_ADDRESS> at 2015-03-11 02:52:40 +0000
Processing by SearchesController#events as */*
  Rendered searches/_statuses.html.erb (0.0ms)
  Rendered searches/events.js.erb (0.4ms)
Completed 200 OK in 7ms (Views: 1.0ms | ActiveRecord: 0.1ms)

I am no expert in Rails by any means, so am struggling to understand the exception. It's quite possible I've missed a step in this second setup, but I can't find what it would be. So I'm raising this ticket in case it's a bug with using MySQL as backend (or some bug present by default in the production environment's config).
This is Ubuntu 14.04 with Percona Server 5.5 (drop-in replacement for MySQL), using the mysql2 gem.  I am using Unicorn with Nginx. All other software and their versions are exactly as per the wiki Setup instructions.
Please let me know if I can provide any other info.
Thanks.

Hmm OK, this doesn't appear related to MySQL or even the production Rails env. I now reproduce it on SQLite with the development environment, so I guess I have done something else wrong. I re-set up the environment from scratch but still get the same problem.
Any tips on how to troubleshoot that rails exception are appreciated, don't know where to start!

I have resolved my issue after another re-install. I think it was something to do with setting it up as a non-privileged user, along with the fact that its default shell was not bash, so possibly rbenv settings were not respected.


Stack(finding the next greater element)

Description 📜
Next greater element

to find the next greater element using stack

Domain of Contribution 📊

[x ] C/CPP

/assign


Improve roadmap table on mobile

The Roadmap table (and probably the table component in general) might need some improvements for small screens.

Reported by @AndreyYolkin on Discord

I am wondering also of using the props component instead of tables (it's always a pain), similar to https://ui.nuxt.com/overlays/modal#props

WDYT?

Yes, that looks neat on mobile 👏

I think badges should not break:


analyze fails when specifying paths in config

setup
the workflow:
name: "lala"

on:
  push:
    branches: [ '*' ]

jobs:
  analyze:
    name: Analyze CodeQL
    runs-on: [self-hosted, Windows, x64,]

    strategy:
      fail-fast: false

    permissions:
      actions: read
      contents: read
      security-events: write

    steps:
    - name: Checkout repository
      uses: actions/checkout@v3

    - name: Initialize CodeQL
      uses: github/codeql-action/init@v2
      with:
        languages: 'python'
        config-file: ./.github/codeql/config.yml

    - name: Autobuild
      uses: github/codeql-action/autobuild@v2

    - name: Perform CodeQL Analysis
      uses: github/codeql-action/analyze@v2
      with:
        category: 'base security checks'

the .github/codeql/config.yml config file
name: "my CodeQL config for security checks"

paths:
  - xxx_yyyyyyyyy_zzzzzzz

so only 1 path should be scanned as explained here in the github documentation.
issue
after specifying the paths: in the config file, i get this error in the Perform CodeQL Analysis step
[ERROR] bad escape \m at position 25

see full logs:
##[debug]Evaluating condition for step: 'Perform CodeQL Analysis'
##[debug]Evaluating: success()
##[debug]Evaluating success:
##[debug]=> true
##[debug]Result: true
##[debug]Starting: Perform CodeQL Analysis
##[debug]Register post job cleanup for action: github/codeql-action/analyze@v2
##[debug]Loading inputs
##[debug]Evaluating: github.workspace
##[debug]Evaluating Index:
##[debug]..Evaluating github:
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'workspace'
##[debug]=> 'C:\actions-runner\_work\yyyyyyyyy_zzzzzzz\yyyyyyyyy_zzzzzzz'
##[debug]Result: 'C:\actions-runner\_work\yyyyyyyyy_zzzzzzz\yyyyyyyyy_zzzzzzz'
##[debug]Evaluating: github.token
##[debug]Evaluating Index:
##[debug]..Evaluating github:
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'token'
##[debug]=> '***'
##[debug]Result: '***'
##[debug]Evaluating: toJson(matrix)
##[debug]Evaluating toJson:
##[debug]..Evaluating matrix:
##[debug]..=> null
##[debug]=> 'null'
##[debug]Result: 'null'
##[debug]Loading env
Run github/codeql-action/analyze@v2

##[debug]Sending status report: {"workflow_run_id":4007210109,"workflow_name":"lala","job_name":"analyze","analysis_key":".github/workflows/workflow.yml:analyze","commit_oid":"29f4229b61cb9860799e64174cae278944301ec4","ref":"refs/heads/test-codeql-config-paths","action_name":"finish","action_ref":"v2","action_oid":"unknown","started_at":"2023-01-25T15:28:43.420Z","action_started_at":"2023-01-25T15:29:16.499Z","status":"starting","testing_environment":"","runner_os":"Windows","action_version":"2.1.39","matrix_vars":"null","runner_arch":"X64","runner_os_release":"10.0.17763"}
##[debug]Loaded config:
##[debug]{"languages":["python"],"queries":{"python":{"builtin":["C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Expressions\\UseofInput.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CVE-2018-1281\\BindToAllInterfaces.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-020\\IncompleteHostnameRegExp.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-020\\IncompleteUrlSubstringSanitization.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-020\\OverlyLargeRange.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-022\\PathInjection.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-078\\CommandInjection.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-079\\ReflectedXss.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-089\\SqlInjection.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-090\\LdapInjection.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-094\\CodeInjection.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-116\\BadTagFilter.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-209\\StackTraceExposure.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-215\\FlaskDebug.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-285\\PamAuthorization.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-295\\MissingHostKeyValidation.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-312\\CleartextLogging.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-312\\CleartextStorage.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-326\\WeakCryptoKey.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-327\\BrokenCryptoAlgorithm.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-327\\InsecureDefaultProtocol.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-327\\InsecureProtocol.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-327\\WeakSensitiveDataHashing.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-352\\CSRFProtectionDisabled.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-377\\InsecureTemporaryFile.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-502\\UnsafeDeserialization.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-601\\UrlRedirect.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-611\\Xxe.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-643\\XpathInjection.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-730\\PolynomialReDoS.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-730\\ReDoS.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-730\\RegexInjection.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-776\\XmlBomb.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Security\\CWE-918\\FullServerSideRequestForgery.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Diagnostics\\ExtractionWarnings.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Diagnostics\\SuccessfullyExtractedFiles.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Summary\\LinesOfCode.ql","C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\qlpacks\\codeql\\python-queries\\0.6.0\\Summary\\LinesOfUserCode.ql"],"custom":[]}},"pathsIgnore":[],"paths":["xxx_yyyyyyyyy_zzzzzzz"],"packs":{},"originalUserInput":{"name":"My CodeQL config for security checks","paths":["xxx_yyyyyyyyy_zzzzzzz"]},"tempDir":"C:\\actions-runner\\_work\\_temp","codeQLCmd":"C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\codeql.exe","gitHubVersion":{"type":0},"dbLocation":"C:\\actions-runner\\_work\\_temp\\codeql_databases","debugMode":true,"debugArtifactName":"debug-artifacts","debugDatabaseName":"db","augmentationProperties":{"injectedMlQueries":false,"packsInputCombines":false,"queriesInputCombines":false},"trapCaches":{},"trapCacheDownloadTime":0}
C:\actions-runner\_work\_tool\CodeQL\0.0.0-20230105\x64\codeql\codeql.exe version --format=terse
2.12.0
::group::Extracting python
Extracting python
  C:\actions-runner\_work\yyyyyyyyy_zzzzzzz\codeql-action-python-autoinstall\Scripts\python.exe C:\actions-runner\_work\_actions\github\codeql-action\v2\python-setup\find_site_packages.py
  C:\actions-runner\_work\yyyyyyyyy_zzzzzzz\codeql-action-python-autoinstall\lib\site-packages
  Setting LGTM_INDEX_IMPORT_PATH=C:\actions-runner\_work\yyyyyyyyy_zzzzzzz\codeql-action-python-autoinstall\lib\site-packages

  C:\actions-runner\_work\yyyyyyyyy_zzzzzzz\codeql-action-python-autoinstall\Scripts\python.exe -c "import sys; print(sys.version_info[0])"
  3
  Setting LGTM_PYTHON_SETUP_VERSION=3

  C:\actions-runner\_work\_tool\CodeQL\0.0.0-20230105\x64\codeql\codeql.exe database trace-command C:\actions-runner\_work\_temp\codeql_databases\python -- C:\actions-runner\_work\_tool\CodeQL\0.0.0-20230105\x64\codeql\python\tools\autobuild.cmd
  Running command in C:\actions-runner\_work\yyyyyyyyy_zzzzzzz\yyyyyyyyy_zzzzzzz: [C:\actions-runner\_work\_tool\CodeQL\0.0.0-20230105\x64\codeql\python\tools\autobuild.cmd]
  [2023-01-25 16:29:20] [build-stdout] Python 3.9.13
  [2023-01-25 16:29:20] [build-stderr] Installed Pythons found by py Launcher for Windows *
  [2023-01-25 16:29:20] [build-stdout] Python 2 not found!
  [2023-01-25 16:29:20] [build-stderr] Requested Python version (2) not installed, use -0 for available pythons
  [2023-01-25 16:29:20] [build-stdout]  -3.9-64Source root appears to be the real root.
  [2023-01-25 16:29:20] [build-stdout] Trying to guess Python version based on installed versions
  [2023-01-25 16:29:20] [build-stdout] Wanted to run Python 2, but it is not available. Using Python 3 instead
  [2023-01-25 16:29:20] [build-stdout] This script is running Python 3, but Python 2 is also available (as 'py -3')
  [2023-01-25 16:29:20] [build-stdout] Calling py -3 C:\actions-runner\_work\_tool\CodeQL\0.0.0-20230105\x64\codeql\python\tools\get_venv_lib.py
  [2023-01-25 16:29:20] [build-stdout] Calling py -3 -S C:\actions-runner\_work\_tool\CodeQL\0.0.0-20230105\x64\codeql\python\tools\python_tracer.py -v -z all -c C:\actions-runner\_work\_temp\codeql_databases\python\working\trap_cache -p C:\actions-runner\_work\yyyyyyyyy_zzzzzzz\codeql-action-python-autoinstall\lib\site-packages -p C:\Users\XBMEMKIT\AppData\Roaming\Python\Python39\site-packages -R xxx_yyyyyyyyy_zzzzzzz --filter include:xxx_yyyyyyyyy_zzzzzzz
  [2023-01-25 16:29:21] [build-stdout] Python 3.9.13
  [2023-01-25 16:29:21] [build-stdout] [INFO] Extraction will use the Python 3 standard library.
  [2023-01-25 16:29:21] [build-stdout] [INFO] sys_path is: ['C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\python\\tools', 'C:\\actions-runner\\_work\\_tool\\Python\\3.9.13\\x64\\python39.zip', 'C:\\actions-runner\\_work\\_tool\\Python\\3.9.13\\x64\\DLLs', 'C:\\actions-runner\\_work\\_tool\\Python\\3.9.13\\x64\\lib', 'C:\\actions-runner\\_work\\_tool\\Python\\3.9.13\\x64']
  Error: 1-25 16:29:21] [build-stdout] [ERROR] bad escape \m at position 25
  [2023-01-25 16:29:21] [build-stderr] Traceback (most recent call last):
  [2023-01-25 16:29:21] [build-stderr]   File "C:\actions-runner\_work\_tool\CodeQL\0.0.0-20230105\x64\codeql\python\tools\index.py", line 25, in <module>
  [2023-01-25 16:29:21] [build-stderr]     buildtools.index.main()
  [2023-01-25 16:29:21] [build-stderr]   File "C:\actions-runner\_work\_tool\CodeQL\0.0.0-20230105\x64\codeql\python\tools\python3src.zip\buildtools\index.py", line 182, in main
  [2023-01-25 16:29:21] [build-stderr]   File "C:\Program Files\Python39\lib\subprocess.py", line 373, in check_call
  [2023-01-25 16:29:21] [build-stderr]     raise CalledProcessError(retcode, cmd)
  [2023-01-25 16:29:21] [build-stderr] subprocess.CalledProcessError: Command '['py', '-3', '-S', 'C:\\actions-runner\\_work\\_tool\\CodeQL\\0.0.0-20230105\\x64\\codeql\\python\\tools\\python_tracer.py', '-v', '-z', 'all', '-c', 'C:\\actions-runner\\_work\\_temp\\codeql_databases\\python\\working\\trap_cache', '-p', 'C:\\actions-runner\\_work\\yyyyyyyyy_zzzzzzz\\codeql-action-python-autoinstall\\lib\\site-packages', '-p', 'C:\\Users\\XBMEMKIT\\AppData\\Roaming\\Python\\Python39\\site-packages', '-R', 'xxx_yyyyyyyyy_zzzzzzz', '--filter', 'include:xxx_yyyyyyyyy_zzzzzzz']' returned non-zero exit status 1.
  Error: 1-25 16:29:21] [ERROR] Spawned process exited abnormally (code 1; tried to run: [C:\actions-runner\_work\_tool\CodeQL\0.0.0-20230105\x64\codeql\tools\win64\runner.exe, cmd.exe, /C, type, NUL, &&, C:\actions-runner\_work\_tool\CodeQL\0.0.0-20230105\x64\codeql\python\tools\autobuild.cmd])
  A fatal error occurred: Exit status 1 from command: [C:\actions-runner\_work\_tool\CodeQL\0.0.0-20230105\x64\codeql\tools\win64\runner.exe, cmd.exe, /C, type, NUL, &&, C:\actions-runner\_work\_tool\CodeQL\0.0.0-20230105\x64\codeql\python\tools\autobuild.cmd]
  Error: A fatal error occurred.
  ##[debug]Sending status report: {"workflow_run_id":4007210109,"workflow_name":"lala","job_name":"analyze","analysis_key":".github/workflows/workflow.yml:analyze","commit_oid":"29f4229b61cb9860799e64174cae278944301ec4","ref":"refs/heads/test-codeql-config-paths","action_name":"finish","action_ref":"v2","action_oid":"unknown","started_at":"2023-01-25T15:28:43.420Z","action_started_at":"2023-01-25T15:29:16.499Z","status":"failure","testing_environment":"","runner_os":"Windows","action_version":"2.1.39","cause":"A fatal error occurred.","exception":"Error: A fatal error occurred.\n    at toolrunnerErrorCatcher (C:\\actions-runner\\_work\\_actions\\github\\codeql-action\\v2\\lib\\toolrunner-error-catcher.js:72:27)\n    at processTicksAndRejections (node:internal/process/task_queues:96:5)\n    at async Object.extractScannedLanguage (C:\\actions-runner\\_work\\_actions\\github\\codeql-action\\v2\\lib\\codeql.js:616:13)\n    at async createdDBForScannedLanguages (C:\\actions-runner\\_work\\_actions\\github\\codeql-action\\v2\\lib\\analyze.js:81:13)\n    at async finalizeDatabaseCreation (C:\\actions-runner\\_work\\_actions\\github\\codeql-action\\v2\\lib\\analyze.js:102:5)\n    at async runFinalize (C:\\actions-runner\\_work\\_actions\\github\\codeql-action\\v2\\lib\\analyze.js:276:21)\n    at async run (C:\\actions-runner\\_work\\_actions\\github\\codeql-action\\v2\\lib\\analyze-action.js:167:29)\n    at async runWrapper (C:\\actions-runner\\_work\\_actions\\github\\codeql-action\\v2\\lib\\analyze-action.js:238:9)","completed_at":"2023-01-25T15:29:21.658Z","matrix_vars":"null","runner_arch":"X64","runner_os_release":"10.0.17763","codeql_version":"2.12.0","ml_powered_javascript_queries":"false"}
  ##[debug]Node Action run completed with exit code 1
  ##[debug]CODEQL_ACTION_VERSION='2.1.39'
  ##[debug]CODEQL_ACTION_FEATURE_SARIF_COMBINE='true'
  ##[debug]CODEQL_ACTION_FEATURE_WILL_UPLOAD='true'
  ##[debug]CODEQL_ACTION_FEATURE_MULTI_LANGUAGE='false'
  ##[debug]CODEQL_ACTION_FEATURE_SANDWICH='false'
  ##[debug]Finishing: Perform CodeQL Analysis

note

the error is only there when paths: is specified.
when this is commented, there is no problem.name: "my CodeQL config for security checks"

# paths:
#   - xxx_yyyyyyyyy_zzzzzzz

the xxx_yyyyyyyyy_zzzzzzz path does exist

Thanks for the report. Could you double check that there are no strange characters on the lines where you define the paths? For example a stray "no break space". I doubt that is the problem, but still worth checking.

@aibaars, that was my first guess as well.
i confirm that there are no strange characters in the whole .github/codeql/config.yml file.
it is a copy of the documentation with some edits.
in the issue description you the litteral content of the .github/codeql/config.yml.

@bisdevres The error message looks like it is coming from Python's re library. The path filtering is implemented using regex matching, however, I do not understand where a stray \ or a m would come from. The path you provide contains neither of these :confused: .
Have you tried enclosing the path with (single) quotes? It shouldn't really matter, but still worth a try. Also could you double check the character encoding of the file?
Another thing to try would be to use a Linux runner (ubuntu-latest on github.com) or a self-hosted one on GitHub Enterprise if you have those available. If that works then there is probably a bug somewhere related to path separator handling (` vs /).

Hi @bisdevres thanks for reporting this problem. I've narrowed down the problem. Since the fix had to go to our internal tooling, it will take a little time to be propagated into what the action uses. Until then, I would recommend you just run the analysis on ubuntu -- whether you use windows or ubuntu to run the the analysis should not change the results you get :blush:

@aibaars
i just ran a test with using the single quotes:
name: "My CodeQL config for security checks"

paths:
 - 'xxx_yyyyyyyyy_zzzzzzz'

this give the same error
doing some other tests:
1. check if error depends on specified path
in another test i tried a different path in the config file:
name: "My CodeQL config for security checks"

paths:
 - lala

this gives the same error.
2. finding the source of \m
in the issue description i masked the logs.
this was not so smart because it hides a clue.
the C:\actions-runner\_work\yyyyyyyyy_zzzzzzz\... path from the logs:
Running command in C:\actions-runner\_work\yyyyyyyyy_zzzzzzz\yyyyyyyyy_zzzzzzz: [C:\actions-runner\_work\_tool\CodeQL\0.0.0-20230105\x64\codeql\python\tools\autobuild.cmd]

is actually more like C:\actions-runner\_work\microdata_utility\...
so it has \m on position 27, which is position 25 if you don't count the C:. 😛
(yes, we're close to becoming insane 🤷♂)
to test if this has anything to do with the path where the repo is cloned, i tried running this on a runner with a different path.
in this new test i got this error:
Running command in C:\temp\runner\_work\microdata_utility\microdata_utility...
...
[ERROR] bad escape \m at position 20

in this new path (C:\temp\runner\_work\microdata_utility\microdata_utility) the \m is at position 22, which is 20 if you don't count the C:.
so i might be on to something here 😃
question
do you have any idea how this could be related to the path where the code is cloned?

The root case is that we forgot to escape repository root folder when constructing the regular expression used to match paths. Roughly we had re.compile(repo_root + path_separator + include_pattern); we should have had regex_escape(repo_root) + ... .
Things work on Linux because it uses / as path separator which has no special meaning in regular expressions. @RasmusWL fixed the bug, so things should work fine on Windows in the next release of CodeQL . Thanks for reporting this and your detailed tests and descriptions!

thanks for the quick fix @aibaars and @RasmusWL!


Read Private & Sequence tags as JSON with Keyword (str) as key instead of Tag (int)

To make the private and sequence tags more usable, the JSON should use the keyword of the tag as keys instead of the tag itself

Can we find a mapping from private tag (int) to keyword (str) ?
Maybe this should still be optional (but activated by default) as some people might work with private tags (int) that are non-standard?

Agree, it should be optional. For private tags maybe the feature is less relevant since it requires this tag <-> keyword mapping like you mentioned. But for the SQ VR tags it's a lot more feasible since we know the mapping there

Do we want to address https://github.com/kaiko-ai/spark-dicom/pull/48#discussion_r812785954 ?


Changing ownership of dump/coco fails during vagrant up

I'm getting the following error when I'm running vagrant up. Keep in mind I'm running Vagrant with VMware Fusion instead of Virtualbox. I wouldn't think that would cause this particular problem, but I thought I would mention it.
I'm running Mac OS X, v. 10.10.1. Because of that, there's no such thing as an "administrative command prompt". I've tried to run git clone and vagrant up with the sudo command, but that causes other problems.
I tried to simply ignore the problem and run vagrant ssh -c "cd /coco && brunch watch", but I get another error from node.js saying that it can't find lodash.
==> default: dump/
==> default: dump/coco/
==> default: dump/coco/levels.bson
==> default: tar:
==> default: dump/coco/levels.bson: Cannot change ownership to uid 1000, gid 1000
==> default: : Operation not permitted
==> default: dump/coco/campaigns.metadata.json
==> default: tar:
==> default: dump/coco/campaigns.metadata.json: Cannot change ownership to uid 1000, gid 1000
==> default: : Operation not permitted
==> default: dump/coco/campaigns.bson
==> default: tar:
==> default: dump/coco/campaigns.bson: Cannot change ownership to uid 1000, gid 1000
==> default: : Operation not permitted
==> default: dump/coco/patches.bson
==> default: tar:
==> default: dump/coco/patches.bson: Cannot change ownership to uid 1000, gid 1000
==> default: : Operation not permitted
==> default: dump/coco/articles.bson
==> default: tar:
==> default: dump/coco/articles.bson: Cannot change ownership to uid 1000, gid 1000
==> default: : Operation not permitted
==> default: dump/coco/patches.metadata.json
==> default: tar:
==> default: dump/coco/patches.metadata.json: Cannot change ownership to uid 1000, gid 1000
==> default: : Operation not permitted
==> default: dump/coco/level.systems.bson
==> default: tar:
==> default: dump/coco/level.systems.bson: Cannot change ownership to uid 1000, gid 1000
==> default: : Operation not permitted
==> default: dump/coco/achievements.metadata.json
==> default: tar:
==> default: dump/coco/achievements.metadata.json: Cannot change ownership to uid 1000, gid 1000
==> default: : Operation not permitted
==> default: dump/coco/level.components.bson
==> default: tar:
==> default: dump/coco/level.components.bson: Cannot change ownership to uid 1000, gid 1000
==> default: : Operation not permitted
==> default: dump/coco/thang.types.bson
==> default: tar:
==> default: dump/coco/thang.types.bson: Cannot change ownership to uid 1000, gid 1000
==> default: : Operation not permitted
==> default: dump/coco/media.chunks.metadata.json
==> default: tar:
==> default: dump/coco/media.chunks.metadata.json: Cannot change ownership to uid 1000, gid 1000
==> default: : Operation not permitted
==> default: dump/coco/media.files.metadata.json
==> default: tar:
==> default: dump/coco/media.files.metadata.json: Cannot change ownership to uid 1000, gid 1000
==> default: : Operation not permitted
==> default: dump/coco/achievements.bson
==> default: tar:
==> default: dump/coco/achievements.bson: Cannot change ownership to uid 1000, gid 1000
==> default: : Operation not permitted
==> default: dump/coco/thang.types.metadata.json
==> default: tar:
==> default: dump/coco/thang.types.metadata.json: Cannot change ownership to uid 1000, gid 1000
==> default: : Operation not permitted
==> default: dump/coco/media.files.bson
==> default: tar:
==> default: dump/coco/media.files.bson: Cannot change ownership to uid 1000, gid 1000
==> default: : Operation not permitted
==> default: dump/coco/level.components.metadata.json
==> default: tar:
==> default: dump/coco/level.components.metadata.json: Cannot change ownership to uid 1000, gid 1000
==> default: : Operation not permitted
==> default: dump/coco/articles.metadata.json
==> default: tar:
==> default: dump/coco/articles.metadata.json: Cannot change ownership to uid 1000, gid 1000
==> default: : Operation not permitted
==> default: dump/coco/levels.metadata.json
==> default: tar:
==> default: dump/coco/levels.metadata.json: Cannot change ownership to uid 1000, gid 1000
==> default: : Operation not permitted
==> default: dump/coco/media.chunks.bson
==> default: tar:
==> default: dump/coco/media.chunks.bson: Cannot change ownership to uid 1000, gid 1000
==> default: : Operation not permitted
==> default: dump/coco/level.systems.metadata.json
==> default: tar: dump/coco/level.systems.metadata.json: Cannot change ownership to uid 1000, gid 1000: Operation not permitted
==> default: tar: dump/coco: Cannot change ownership to uid 1000, gid 1000: Operation not permitted
==> default: tar: dump: Cannot change ownership to uid 1000, gid 1000: Operation not permitted
==> default: tar: Exiting with failure status due to previous errors

I would really love to get this working and merged into codecombat's code via #2106, so please let me know if I can provide further information or support!

I'm guessing this is a Mac specific issue; this has worked relatively recently for me on windows. Maybe try changing: https://github.com/dpen2000/Codecombat-Vagrant/blob/master/fillMongo.sh#L5 and adding "--no-same-owner" (see http://www.krenger.ch/blog/linux-tar-cannot-change-ownership-to-permission-denied/)
The need for "administrative command prompt" was to get round issues with windows and sym links.
I hope this helps.

Fantastic, that part works now. Thanks!
Unfortunately, I'm getting the following error when running vagrant ssh -c "cd /coco && brunch watch":
Error: couldn't load config /coco/config.coffee. Error: Cannot find module 'lodash'
  at Object.exports.loadConfig (/usr/lib/node_modules/brunch/lib/helpers.js:514:15)
  at Object.exports.loadConfig (/usr/lib/node_modules/brunch/lib/helpers.js:512:24)
  at initialize (/usr/lib/node_modules/brunch/lib/watch.js:453:20)
  at new BrunchWatcher (/usr/lib/node_modules/brunch/lib/watch.js:607:7)
  at module.exports.watch (/usr/lib/node_modules/brunch/lib/watch.js:663:12)
  at start (/usr/lib/node_modules/brunch/lib/index.js:13:33)
  at Command.<anonymous> (/usr/lib/node_modules/brunch/node_modules/commander/index.js:249:8)
  at Command.emit (events.js:98:17)
  at Command.parseArgs (/usr/lib/node_modules/brunch/node_modules/commander/index.js:472:12)
  at Command.parse (/usr/lib/node_modules/brunch/node_modules/commander/index.js:370:21)
  at Object.exports.run (/usr/lib/node_modules/brunch/lib/cli.js:49:13)
  at Object.<anonymous> (/usr/lib/node_modules/brunch/bin/brunch:11:22)
  at Module._compile (module.js:456:26)
  at Object.Module._extensions..js (module.js:474:10)
  at Module.load (module.js:356:32)
  at Function.Module._load (module.js:312:12)
  at Function.Module.runMain (module.js:497:10)
  at startup (node.js:119:16)
  at node.js:906:3

Any ideas on this one? I'll look at it a bit more later.

Hey, @ssfinney: Could you send me a PR for this change? I'd hate to get syntax slightly wrong

@dpen2000 Done, via #15.


[Github] NEXT-00000 - Allow activating staging mode via console with no interaction

1. Why is this change necessary?
Currently, it is not possible to activate staging mode via CLI command system:setup:staging with the --no-interaction option.
2. What does this change do, exactly?
It changes the default of the confirm-question to true, to allow activating staging mode via CLI command system:setup:staging with the --no-interaction option.
3. Describe each step to reproduce the issue or behavior.
Follow the documentation here: https://developer.shopware.com/docs/guides/hosting/configurations/shopware/staging.html#activate-the-staging-mode, with the --no-interaction option
4. Please link to the relevant issues (if any).
There aren't any.
5. Checklist

[x] I have rebased my changes to remove merge conflicts
[x] I have written tests and verified that they fail without my change
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfill them.

Imported from Github. Please see: https://github.com/shopware/shopware/pull/5402

[public]

Status Change: Open

This issue is ready for implementation.
[created from NEXT-39484, comment 511223]

[public]

Status Change: In Review

Work on this ticket is complete and is now pending review.
[created from NEXT-39484, comment 511225]

[public]

Status Change: Resolved

The ticket has been successfully completed; the solution is implemented and verified.
[created from NEXT-39484, comment 511226]

[public]

FixVersion Change: <IP_ADDRESS>

This issue will be / was solved in Shopware version <IP_ADDRESS>.
[created from NEXT-39484, comment 511227]


Add publication and citation to README and contribution guidelines

👍
Looks good to me. Merge when ready.


Zbjammer on cc2531

Hello,
I'm trying to use the zbjammer with the cc2531. I've flashed the cc2531 with the Bumblebee version 2.1 revision 1 and am using the develop branch of killerbee.
When I'm executing zbjammer I get the following error message:
❯ zbjammer -c 15
zbjammer: jamming channel 15
*** WARNING: this may not actually work on your hardware! Check with spectrum analyser!
*** NOTICE: it is your responsibility to comply with local law. Please check radio spectrum laws in your area before
    proceeding. Hit <ENTER> to continue or CTL-C to abort.
Traceback (most recent call last):
  File "/Users/emily/.pyenv/versions/3.10.4/bin/zbjammer", line 4, in <module>
    __import__('pkg_resources').run_script('killerbee==3.0.0b2', 'zbjammer')
  File "/Users/emily/.pyenv/versions/3.10.4/lib/python3.10/site-packages/pkg_resources/__init__.py", line 651, in run_script
    self.require(requires)[0].run_script(script_name, ns)
  File "/Users/emily/.pyenv/versions/3.10.4/lib/python3.10/site-packages/pkg_resources/__init__.py", line 1448, in run_script
    exec(code, namespace, namespace)
  File "/Users/emily/.pyenv/versions/3.10.4/lib/python3.10/site-packages/killerbee-3.0.0b2-py3.10-macosx-12.2-x86_64.egg/EGG-INFO/scripts/zbjammer", line 51, in <module>
    if not kb.jammer_on():
  File "/Users/emily/.pyenv/versions/3.10.4/lib/python3.10/site-packages/killerbee-3.0.0b2-py3.10-macosx-12.2-x86_64.egg/killerbee/__init__.py", line 459, in jammer_on
    return self.driver.jammer_on(channel=channel, method=method)
TypeError: Bumblebee.jammer_on() got an unexpected keyword argument 'method'

Does anybody know what I can do to resolve this issue?
Thanks,
Emily

Are you able to perform packet sniffing using bumblebee?


Possible to default to manual entry

Is there an extra to pass to the CardIOActivity that will default it to manual keyboard entry with the option to use the camera?

No.
However, you're welcome to modify the source yourself if you desire such a feature.

Created pr for this: https://github.com/card-io/card.io-Android-source/pull/25


Some beautiness

Added some ES6 features and formatted.

You are fast like the meteor. With your help needs to be written a new reactive framework.

Sorry, could you give me the reference, where from did you know, about it is a bad habit to not use semicolons in the EcmaScript 6 environment.
I'd also asked in Vue chat about it, and there I heard the opposite thing, that using of semicolons is the Mauveton.

You know, you should never critic someone about his code style, but should critic him about the absence of complexity in his code. Because it's not matter really, using you single quotes, or double, but if you use double, please use double every time, at least in the limit of one application.

If you are interesting
root: true
extends: default
env:
  es6: true
  browser: true
parserOptions:
  ecmaVersion: 6
  allowImportExportEverywhere: false
globals:
  $: true
  google: true
  window: true
  require: true
  CSRF_TOKEN: true
rules:
  indent:
    - 1
    - 4
  quotes:
    - 1
    - single
  linebreak-style:
    - 2
    - unix
  semi:
    - 1
    - always # - never
  no-undef:
    - 2
  space-before-function-paren:
    - 2
  array-bracket-spacing:
    - 0
  no-var:
    - 0
  one-var:
    - 1
    - never # - always
  prefer-const:
    - 0
  comma-dangle:
    - 2
    - only-multiline
  no-extra-parens:
    - 0

Dear Piterden: I am very sorry, if my comment came over in a harsh way! Please forgive me!!! I apologise profoundly!!!
I will check up on the semicolon issue. The source I have is somewhere at Angular, where it comes up in the discourse of minification. If I find the link again, I will post it.
However, it is very likely that there are changes in ES6, which I missed... so please ignore my statement!
Thanks for your posts! I keep playing around with them and will come back!

Thank you!
Peace!

))


Unload key command in TPM 2.0

I'm working on TPM and I have a trouble. If my key tree to much, I must load all parrent keys, but TPM simulator just support 9 key slots. I fond unload key funtion but there was no unload key function in specification tpm 2.0.
Is there any way to unload key in TPM 2.0?
Thank you!

I think you want Tss2_Sys_EvictControl.
See section 28 on context management in:
https://trustedcomputinggroup.org/wp-content/uploads/TPM-Rev-2.0-Part-3-Commands-01.38.pdf
From: khanhnt93<EMAIL_ADDRESS>Sent: Tuesday, October 31, 2017 1:56 AM
To: 01org/tpm2-tss<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [01org/tpm2-tss] Unload key command in TPM 2.0 (#596)
I'm working on TPM and I have a trouble. If my key tree to much, I must load all parrent keys, but TPM simulator just support 9 key slots. I fond unload key funtion but there was no unload key function in specification tpm 2.0.
Is there any way to unload key in TPM 2.0?
Thank you!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@khanhnt93 AFAIK @jiazhang0 wrote a tpm2_flushcontext tool that uses Tss2_Sys_FlushContext. It should be useful for what you want to achieve.


[FEAT] Wildcard for language in multilanguage sitemap patterns

Feature request
Summary
We suggest adding a wildcard for languages in the sitemap URL patterns configuration.
Why is it needed?
Maybe it is not clear in the documentation, but now we can either create a global or language-per-language pattern.
In case we choose the global pattern it will be like: ``/en/posts/[slug]whereen` is the default language.
Using a wildcard/field on the pattern gives an issue now:

The other alternative is stating parameter language by language, but if the site has more than five languages, it will become a big annoying issue.
Suggested solution(s)
So, either making it clear in the documentation or enabling the [lang] field to be used as a wildcard will improve a lot the developer experience with this wonderful plugin.
Related issue(s)/PR(s)
Let us know if this is related to any issue/pull request.

Hi @SalahAdDin
Thanks for reporting yet another great feature request!
You really help us push our plugins to the next level.
About the sitemap plugin; we are currently in the process of migrating the plugin to the Webtools suite.
Just now I've released the first beta version of the Webtools Sitemap Addon to NPM
It has all the same features you're used to from the standalone Sitemap plugin, but uses the core Webtools plugin for it's URL management.
The issue you created about the "Wildcard for language" is a feature that's already integrated in Webtools.
That being said I would love it if you could give Webtools and the Sitemap addon a try. I think you'll like it a lot.

Hi @SalahAdDin
Thanks for reporting yet another great feature request! You really help us push our plugins to the next level.
About the sitemap plugin; we are currently in the process of migrating the plugin to the Webtools suite. Just now I've released the first beta version of the Webtools Sitemap Addon to NPM It has all the same features you're used to from the standalone Sitemap plugin, but uses the core Webtools plugin for it's URL management.
The issue you created about the "Ignore all content types..." is a feature that's already integrated in Webtools.
That being said I would love it if you could give Webtools and the Sitemap addon a try. I think you'll like it a lot.

There are some issues with this, the first, it is not clear if we need to install core-webtools, so we installed only the adding and we got the issue:

This happens when we don't setup the configuration, when we do it, it fails even to load the admin:
    ~/Projects/Portfolio/backend    PBE-001-strapi-4 !4  yarn develop                                                                              ✔  20s   system 
✔ Cleaning dist dir (10ms)
⠋ Building build context
[INFO] Including the following ENV variables as part of the JS bundle:
    - ADMIN_PATH
    - STRAPI_ADMIN_BACKEND_URL
    - STRAPI_TELEMETRY_DISABLED
✔ Building build context (107ms)
✔ Creating admin (9161ms)
⠙ Loading Strapi[ERROR]  There seems to be an unexpected error, try again with --debug for more information

┌───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│                                                                                │
│   Error: Error loading the plugin sitemap because sitemap is not installed. Please either install the plugin or remove it's configuration.        │
│       at Object.loadPlugins (/home/luisalaguna/Projects/Portfolio/backend/node_modules/@strapi/strapi/dist/core/loaders/plugins/index.js:83:13)   │
│       at async Strapi.loadPlugins (/home/luisalaguna/Projects/Portfolio/backend/node_modules/@strapi/strapi/dist/Strapi.js:311:5)                 │
│       at async Promise.all (index 3)                                                                                │
│       at async Strapi.register (/home/luisalaguna/Projects/Portfolio/backend/node_modules/@strapi/strapi/dist/Strapi.js:341:5)                    │
│       at async Strapi.load (/home/luisalaguna/Projects/Portfolio/backend/node_modules/@strapi/strapi/dist/Strapi.js:425:5)                        │
│       at async Object.develop (/home/luisalaguna/Projects/Portfolio/backend/node_modules/@strapi/admin/dist/_chunks/index-sNH2VWbC.js:837:28)     │
│       at async develop (/home/luisalaguna/Projects/Portfolio/backend/node_modules/@strapi/admin/dist/_chunks/develop-YNTGWKMC.js:61:5)            │
│       at async Command.parseAsync (/home/luisalaguna/Projects/Portfolio/backend/node_modules/commander/lib/command.js:923:5)                      │
│       at async Module.runStrapiCommand (/home/luisalaguna/Projects/Portfolio/backend/node_modules/@strapi/strapi/dist/commands/index.js:130:3)    │
│                                                                                │
└───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

Installing web tools works fine, but the sitemap cannot be enabled since the config is still broken.
So, it is not usable yet.
I think it is required to update the documentation!

Ok, cool, it seems I was able to setup the sitemap:
  webtools: {
    sitemap: {
      enabled: true,
      config: {
        cron: "* * * * 7",
        xsl: true,
        autoGenerate: false,
        caching: true,
      },
    },
  },

I don't know if it is the right way but at least It does not break the run.
It would be useful to add this to the documentation.

But, it seems there is an issue with the web tools URL patterns screen:

It never finishes to load, why?

Unsure, might be a bug. Please for all of these issues report them on the webtools repo

Opened: https://github.com/pluginpal/strapi-webtools/issues/150


sqliteexception no such table (code 1) when selecting database

hello there. I pre-populate an sqlite database
my nativescript will download it via http module getFile.
after download, I do these
Sqlite.exists(unique_file_name.db) = return false
Sqlite.copyDatabase(unique_file_name.db) = return true
Sqlite.exists(unique_file_name.db) = return true
after checking that it is successfully copied, I initialise the database
new Sqlite(unique_file_name.db)  > db.isOpen() returns true
so after db.isOpen() returns true, I get some data using db.get or db.all, it gives me

sqliteexception no such table (code 1)

I have checked the db.file. it can be opened using DB Browser for SQLite program in windows.
In the Pragmas tab, it reports the "User Version" as 0 (zero). Wondering if it is related
Any help would be greatly appreciated

Have you tried the demo application?

Please note; if you are trying to SHIP the database inside the application; you MUST update the webpack.config.js file to add your filename to the copy step.   Otherwise your database is NOT shipped in the application to be extracted at a later point.


Try out specs against MRI 2.6 + Rubygems 3.0

What was the end-user problem that led to this PR?
The problem was that our Azure build was using outdated versions of ruby and rubygems.
What was your diagnosis of the problem?
My diagnosis was that we should update them.
What is your fix for the problem, implemented in this PR?
My fix is to update them. With the latest versions, failures go down to 319.

/cc @MSP-Greg If you have time and will to help us getting the remaining tests green, let me know. I can help out with anything needed.

@deivid-rodriguez
Probably wait till the weekend. You ok with switching to Actions for Windows?

Yes, that was in our plans anyways, so :+1:.

I'll get this in for now.
@bundlerbot merge


Aloha Documentation: Language is being reset anytime a page is reloaded.

In the upper right corner of the documentation page user can switch to preferred langauge.
Refreshing the page resets language back to Deutsch.
Same for links opened in new page, they are in Deutsch regardless of what was chosen as a preferred language.
We need a solution where the documentation stays in a preferred language.
Technical discussion

cookies
Broswer Preferred language

done

ОК


feat(pulseaudio): add support for source device

What type of PR is this? (check all applicable)

[ ] Refactor
[X] Feature
[ ] Bug Fix
[ ] Optimization
[ ] Documentation Update
[ ] Other: Replace this with a description of the type of this PR

Description
Update pulseaudio module to accept a source instead of a sink.
This is quite similar to #2238 but I had the feeling there was too
much code duplication. At first, I did try to rely heavily on
templating to avoid that and keep the number of lines changed to a
minimum, but my C++ foo was not good enough (I can push what I have
currently if someone is interested, but it does not compile).
In this attempt, only a few functions are templated (not the whole
class) and a few helper functions are introduced to implement the
differences.
Instead of using switch/case to implement the differences, helper
functions could be specified as an abstract class and implemented by
different classes. I think this is not worth the effort.
[module/speaker]
type = internal/pulseaudio
format-volume = <label-volume>
format-muted = <label-muted>
label-volume = speaker: %percentage: 2%%
label-muted = muted speaker: %percentage: 2%%

[module/micro]
type = internal/pulseaudio
source = "@DEFAULT_SOURCE"
format-volume = <label-volume>
format-muted = <label-muted>
label-volume = micro: %percentage: 2%%
label-muted = muted micro: %percentage: 2%%

Fix #1096.
Documentation (check all applicable)

[x] This PR requires changes to the Wiki documentation (describe the changes)
[x] This PR requires changes to the documentation inside the git repo (please add them to the PR).
[ ] Does not require documentation changes

After thinking a bit, I think I can make something a bit more concise!

I am unable to make inheritance work. I have errors around the use of factory_util::unique<pulseaudio> which seems to not play nice when the concrete class is not pulseaudio but a subclass. Something about operator= not being here. Also, it doesn't help much for the number of line of code. Again, I can push the code if you want to try to debug. Surely, I am a bit limited by my C++ knowledge.
I'll stop working on this until I get a feedback for a direction to follow. I am currently using the module as is.

Hi,
I want to tackle pulseaudio source/sink thing for my use as well. I will probably go from scratch & add it from current HEAD since this has been stale since 2021 :slightly_smiling_face:
I did share some fixes/enhancements for backlight module - would you be interested in this as well?
BR
X.

Yes, sorry, I didn't followup. I am using this code without any issue. It only crashes when Pulseaudio is restarted. As it works for me, I don't have the motivation to go the extra mile to finish the PR. Feel free to take over or start from scratch.

Okay, I'll take a closer look at what has been done and adapt it to the current master HEAD so it can be merged easily :slightly_smiling_face: I've already shared some improvements for backlight module so I will do that for pulse as well.
I tend to play with pulse/pipewire a lot so restarts are happening quite regularly so this would be one thing to fix for me :grin:

Hey @xoores, is this still something you're working on or did you give up on the project?

Hey @xoores, is this still something you're working on or did you give up on the project?

Hi! Did not give up but also did not really want to waste much time writing a code that would not be accepted (I have another pull opened for backlight module). :sweat_smile:
I will probably get to this as well but I have some work-related tasks that I needed to prioritize :slightly_smiling_face:

did not really want to waste much time writing a code that would not be accepted

oh yeah makes total sense :)

I will probably get to this as well but I have some work-related tasks that I needed to prioritize slightly_smiling_face

sure thing! take the time you need bro, there's no rush aha. enjoy yourself, that's the only thing that matters :heart:

I have updated this PR to work against master. No other change. I can resume work on this if nobody else has stepped up with a better approach. From my understanding, the current PR is mostly good.


Report exceptions

Hi, if there is any exception thrown during the compilation it's completely ignored and the response from the API is just 500... there is no extra info to figure out what went wrong... so I have added a report() to at least get it logged into the logs and give more clues of why there was a 500 error...

Never mind this PR.. seems the OPcache just crashes randomly with apparently no reason...
Sometimes I get Zend OPcache could not compile file some other time it compiles successfully... so in the end, it is just cluttering the log files. I guess all these files it couldn't compile for no reason could be simply ignored.

I just realized the crash is due that it hit the opcache.max_accelerated_files limit...


Error when running parallel updates to the same wiki

Describe the bug
It seems the problem reported in #478 still exists. When working with multiple releases at the same time, I get the following message:
Error: To https://.visualstudio.com//_git/.wiki
! [remote rejected] wikiMaster -> wikiMaster (TF401028: The reference 'refs/heads/wikiMaster' has already been updated by another client, so you cannot update it. Please try again.)
error: failed to push some refs to 'https://.visualstudio.com//_git/.wiki'
Error: To https://.visualstudio.com//_git/.wiki
! [remote rejected] wikiMaster -> wikiMaster (TF401028: The reference 'refs/heads/wikiMaster' has already been updated by another client, so you cannot update it. Please try again.)
error: failed to push some refs to 'https://.visualstudio.com//_git/.wiki'
WIKI Updated Task Version: 1.14.4.
To Reproduce
Run to releases in parallel that will update the same wiki.
Expected behavior
Retry should be performed automatically by the task after a new pull in git repository.
What is the issue see:

Azure DevOps Services

The problem here is the way Git works, you can only push to the remote if you are up to date i.e. pulled any changes made by other users/processes. The task, as it stands, does a pull as the last step prior to doing the push, so I can't see I can do any more to mitigate these parallel race conditions from occurring in the first place.
The only thought I have had is that I could put in a retry loop e.g. try a pull/push cycle say 5 times on the pull error before failing the tasks.
Do you have any other thoughts has to how this could be addressed

I retry loop should be fine. It might be a good idea to have an small interval between each try (maybe 5 seconds?). I don't see any problem in wait a bit more for the task finish as long as it succeed.
Right now in our release step we run many other tasks before the wiki updater. If wiki updater fails, we have to run all the release step again. That's why is so important to guarantee that the task will be executed with success.

Ok, a retry look it is then. I will look at it as a soon as I get a chance


Error while running check_live.py example

Describe the bug
When running python check_live.py it crashes with following error message:
Traceback (most recent call last):
File "[..]/check_live.py", line 7, in
client: TikTokLiveClient = TikTokLiveClient(
File "[..]/.local/lib/python3.10/site-packages/TikTokLive/client/client.py", line 63, in init
self._web: TikTokWebClient = TikTokWebClient(
File "[..]/.local/lib/python3.10/site-packages/TikTokLive/client/web/web_client.py", line 34, in init
super().init(**kwargs)
TypeError: TikTokHTTPClient.init() got an unexpected keyword argument 'proxy'
Expected Behaviour
Does not crash
Actual Behaviour
If applicable, include screenshots!
...
Package Version
My version of TikTokLive is TikTokLive-6.3.0.post1.
Operating System

[ ] Windows
[x] Linux
[ ] MacOS
[ ] Other (Specifically, ...)

Anything Else
If there's anything else, add it here.

Error doesn't occur when downgraded to TikTokLive-6.3.0

Fixed in https://github.com/isaackogan/TikTokLive/commit/54f4dd091b56e1789c6b2746b733c7e3ed37c171.
Upgrade with pip install --upgrade TikTokLive==6.3.0.post2.


Revamped the VR Lab Website

Went through the repository and updated the template due to some files being missing or outdated. Hopefully this should resolve issues for future developments on the website. Had a fun time recreating the site and hopefully looking forward to see new content.
New Things:

Light/Dark Modes
Removed unused content throughout the repo
Cleaned up code
Working on documentation if anyone wants to try and help out maintaining the site

Jhundon

👷 Deploy Preview for virtualrealitylab processing.

Name
Link

🔨 Latest commit
74d193041b7edc67fad0d3a678d5100d29a19e5a

🔍 Latest deploy log
https://app.netlify.com/sites/virtualrealitylab/deploys/666212c580d08a000898c5a1


RAG tutorial

Closes #14
Adds a new tutorial to Llama Index, based on the Github Repo Reader tutorial by Llama Index but focused on Argilla's docs

Looks good. Just two minor comments:

I would pin these: pip install argilla-llama-index llama-index-readers-github

@burtenshaw to any version in particular? Or just the one that works with my setup.

I would change the notebook's file name to something that explains what it is.

Okay, will do :)


add a type so that Duration is marshalled more pleasantly

Currently:
trimble@tartu:~/proj/pbs$ bin/api -c
{
  "version": "main.24.3735d77",
  "truncate": 99,
  "bolt": {
    "path": "photo.db"
  },
  "server": {
    "host": "",
    "port": 8088,
    "timeout":<PHONE_NUMBER>0
  }
}

better would be something like: "timeout": "30s"

Would be better, but too much work as envconfig ignores a wrapped time.Duration : (


add keycloak docs

https://github.com/rancher/docs/issues/668

Closing in favor of https://github.com/rancher/docs/pull/753


Can't tab-complete suggestions

Type: Bug
When I get GitHub Copilot suggestions (or suggestions from other extensions), I can't tab complete the suggestions. When pressing Tab, a tab character is emitted instead of the suggested completion.
 Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.
Happy coding!

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

Here's a basic screencap of the issue:

I'm hitting this issue in C# and Markdown. The suggestions come from GitHub Copilot.
This occurs for any Copilot suggestion on my machine.

Can you try with default settings and default keybindings and just the copilot extension enabled?

I have the same problem with autocomplete in Typescript, but I don't use Copilot or anything.
I have the default shortcut (CTRL + SPACE)

Hi same problem in Python on macOS.  If the suggestion widget is showing, then completing inline suggestions is actually greyed out, even when you hover it.  So it's not an issue with keybindings WHATSOEVER.  Somehow the suggestions widget is just flat out disabling inline suggestions.

same in Golang, no suggestion with keyboard shortcut (CTRL + SPACE) in portable version
Version: 1.78.2
Commit: b3e4e68a0bc097f0ae7907b217c1119af9e03435
Date: 2023-05-10T14:39:26.248Z
Electron: 22.5.2
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: No

After a few tests, the bug also appears in version 1.77.3.
On Windows 11:
Version: 1.77.3 (user setup)
Commit: 704ed70d4fd1c6bd6342c436f1ede30d1cff4710
Date: 2023-04-12T09:16:02.548Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: Yes
On Windows 10, the shortcut is functional:
Version: 1.77.3 (user setup)
Commit: 704ed70d4fd1c6bd6342c436f1ede30d1cff4710
Date: 2023-04-12T09:16:02.548Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19045
Sandboxed: Yes
And after an update on my version in Windows 10, the bug doesn't appear.
I conclude that the bug occurs on Windows 11.

@jkoritzinsky @jrieken @hediet @Xenxia
After another test, I discovered that the shortcut was used by Peek in PowerToys.
@jkoritzinsky maybe you use PowerToys too.

Any tips to root out which extension is having the bad interaction @jkoritzinsky ?  I don't have learn-markdown, but I do have a bunch of extensions, so guessing that's the issue

Honestly I just went through my extension list and tried disabling the first markdown-related extension (as tab-complete was working in other language modes for me).

Closing because this seems to be an extension issue.


Mocked SOAP operation requesting access to real endpoint

I have created a new SOAP project and imported the WSDL file. I have no access to the real endpoint of this service from my machine. I have created a response for one of the operations. The status of the operation is "Mocked". When I try to make a request to this mocked operation, Castlemock either tries to access or redirects to the real endpoint and fails. My java client throws an java.net.UnknownHostException: <real_endpoint>. Tested on versions 1.29 and 1.33.

Hi @Honatas.
That seems very odd. How do you call the SOAP service? Does your software retrieve the WSDL file from Castle Mock? Please note that Castle Mock will not alter the WSDL file in any way. This means that if the WSDL file is referring to the original host, your software might extract that URL and use that instead. In those cases you need to specifically override the WSDL endpoint URL in your code.
Would it be possible for you to send me the exported project?
You can send it to me directly on<EMAIL_ADDRESS>Thank you very much!
Best regards,
Karl Dahlgren

The WSDL contained the real endpoint URL. Overriding it in my code was not enough. To make this work I had to do the following:
1 - Create a new Castlemock project
2- Check the created project url to get the project ID
3- Build the new endpoint URL using the project ID and modify it in the WSDL
4- Upload the modified WSDL to the Castlemock project
This is not a Castlemock issue. Anyway, I'd suggest to display the project ID in the project page.
Thanks and sorry for the trouble.


Mod fails to load at creating Diesel Generators Stage

Mod fails to load either at the stage of creating diesel generators or directly after. Complaints of Generator creating more electricity than consuming mechanical power.
Log is attached.
22-06-09_09-47-45_6126.log

Looked to be a conflict with CheatMenu, closing due to lack of troubleshooting on my part

This error ist a Assert error and cannot try catch. This is okey.


chore(dms): Change checks IDs to match with metadata

Context
Actual DMS checks do not match name of the class and metadata name.
Description
Changed name to match in checks:

dms_instance_multi_az_enabled
dms_instance_no_public_access

License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This does not need backport since the service is only present in v4.


 It is a subset of the CI job bazel_tests.
BUG=see description

There are a few CI cleanups coming on this branch ahead of enabling CI testing of compression. These cleanups are on a separate branch in order to make review and merging a little more parallel.

I tried to delete a CI job in this PR, but the deleted job tried to run and failed. Does some version other than the .github/workflows directory in the commit which triggers CI govern the CI run?

I tried to delete a CI job in this PR, but the deleted job tried to run and failed. Does some version other than the .github/workflows directory in the commit which triggers CI govern the CI run?

Yes, it appears GitHub runs the workflows in the commit into which the PR will be merged. Therefore the job and its script cannot be removed at the same time. Fixed by 55135d1.


Git Clone recursive failed

just do
git clone https://github.com/triton-inference-server/tensorrtllm_backend --recursive

Error message
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
fatal: clone of 'git@github.com:NVIDIA/TensorRT-LLM.git' into submodule path '/home/ubuntu/test/tensorrtllm_backend/tensorrt_llm' failed
Failed to clone 'tensorrt_llm'. Retry scheduled
Cloning into '/home/ubuntu/test/tensorrtllm_backend/tensorrt_llm'...
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.

please adjust the .gitmodules file by rewriting the tensorrt_llm module to https
sed -i 's/git@github.com:NVIDIA/TensorRT-LLM.git/https://github.com/NVIDIA/TensorRT-LLM.git/g' .gitmodules

This issue can be resolved by adding your public ssh key to GitHub
[https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account]

Closing.
@lanking520 Please re-open if you still see the issue.


fix(imageInput): Image input was not checking what file was being upl…

…oaded. now if a user tries to upload an invalid image the webpage will give an error
@wski @rkenyon1969 @clarkjefcoat @SOAP1914

Please rebase these together once the unit tests pass


Migrate all embedded youtube videos to the youtube-nocookie domain

Is your feature request related to a problem? Please describe.
We currently have a mix of youtube embeds with youtube and the youtube-nocookie domain.
Describe the solution you'd like
Only use the youtube-nocookie domain.
Additional context
This is also relevant for new embeds

Hey @pmig , Should I work on this issue ?

Hey @pmig , while going through the mdx file, I noticed that the <iframe> tag is not working as intended. Instead it is just rendering the tag as a plain text.
Should I fix this also ?


[Feature Request] image search in REPOSITORY support

Support search image in REPOSITORY I think it's very useful when people create container or service or pull images (in create service, create container, pull images pages),
for example like this:
Create a service, usd cirros, search cirros

cc @ncresswell

Yeah,  nice to have feature, but lower in priority.
Rgds,
Neil Cresswell
On 16/07/2018, at 6:43 PM, Anthony Lapenna <notifications<EMAIL_ADDRESS>wrote:
cc @ncresswellhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ncresswell&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=3CH4pbGQ9EQY8awUJ4alLM0S77T46ieFnJG147SeIAc&s=EQhT4mLMvev4zlZyfQ1SlkftyMFERFsmHMSheJVGwXQ&e=
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_portainer_portainer_issues_2043-23issuecomment-2D405160254&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=3CH4pbGQ9EQY8awUJ4alLM0S77T46ieFnJG147SeIAc&s=xIgyCulmWOMakgPYaT0gEsekeL3Ew2DD-yxak34U_Wc&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AWGrlfzM0Nm5-5F2KGS6KX-2Db3pO1jlkM7uks5uHDYJgaJpZM4VQKP5&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=3CH4pbGQ9EQY8awUJ4alLM0S77T46ieFnJG147SeIAc&s=Ag-9aIARNihQn7AOuwn4pp99vCVDP2FLJBBVd4E6X_c&e=.

Super disagree with search being of lower priority. With all the other great features of Portainer, this seems a very odd omission. Not sure how you guys work, but I often browse through docker hub looking at various images before choosing one to use. Synology's docker package and Cockpit's container management both have this feature, so it seems out of place that I have to have 2 browser windows open and copy and paste the image name to portainer

Same here, should be high as priority

Tghis really is the only missing thing using portainer


Add link to benchmark in README

@yegor256 can we add some information about how we get information for https://yegor256.github.io/fibonacci/index.html ?

@MCJOHN974 what do you mean? what is "some information"?

@yegor256 if code that collected information is open source -- link to repository. If we used some not open source tools -- names of this tools or links to websites of this tools

@yegor256 there is a link to this repository in the page, at the bottom

@yegor256 I mean not the code of programs, which performance we are measuring. I mean tools that count assembly instructions and time

@MCJOHN974 we use "perf". The HTML reports explicits mentions it.


Enhancement request: Ability for SDK clients to override the useragent string with their own value

Enhancement request is to enhance the SDK to allow SDK clients to set their own useragent string value, as an optional parameter when initialising the DV client.
This would allow the following clients to set their own useragents for Splunk analysis:

The DV Terraform provider
The upcoming CLI

Now exists