ansible-navigator run playbook.yml fails with error ansible-playbook: error: unrecognized arguments: podman

ISSUE TYPE

Bug Report

SUMMARY
Hello
ansible-navigator run is passing the podman environment as parameter to ansible-playbook
if adding the verbose option, it doesn't produce the same error
ANSIBLE-NAVIGATOR VERSION
ansible-navigator 3.5.0

running on AlmaLinux 9.2
CONFIGURATION
/root/.ansible-navigator.yml
---
ansible-navigator:
  ansible:
    cmdline: -ce podman
    config:
      help: false
    doc:
      help: false
      plugin:
        type: module
    inventory:
      help: false
    playbook:
      help: false
  ansible-builder:
    help: false
    workdir: /root
  ansible-runner:
    job-events: false
  app: settings
  collection-doc-cache-path: /root/.cache/ansible-navigator/collection_doc_cache.db
  color:
    enable: true
    osc4: true
  editor:
    command: vi +{line_number} {filename}
    console: true
  enable-prompts: false
  exec:
    command: /bin/bash
    shell: true
  execution-environment:
    container-engine: podman
    enabled: true
    image: registry/ansible/ansible:latest
    pull:
      policy: missing
  format: yaml
  images:
    details:
    - everything
  logging:
    append: true
    file: /root/ansible-navigator.log
    level: warning
  mode: stdout
  playbook-artifact:
    enable: true
    save-as: '{playbook_dir}/logs/{playbook_name}-artifact-{time_stamp}.json'
  settings:
    effective: true
    sample: false
    schema: json
    sources: false
  time-zone: UTC

ansible.cfg
[defaults]
inventory = inventory.yml

LOG FILE
relevant logs
when running normally
 cmdline_args:['/ansible/k8s/playbook.yml', '-ce', 'podman', '-i', '/ansible/inventory.yml']
2023-11-02T19:53:26.931059+00:00 DEBUG 'ansible-runner._handle_command_wrap' containerization enabled
2023-11-02T19:53:26.931555+00:00 DEBUG 'ansible-runner.wrap_args_for_containerization' container engine invocation: podman run --rm --tty --interactive -v /ansible/:/ansible/ --workdir /ansible -v /tmp/ssh-XXXXWZC0eH/:/tmp/ssh-XXXXWZC0eH/ -e SSH_AUTH_SOCK=/tmp/ssh-XXXXWZC0eH/agent.1531020 -v /root/.ssh/:/home/runner/.ssh/ -v /root/.ssh/:/root/.ssh/ --group-add=root --ipc=host -v /tmp/ansible-navigator_zbdjbbxf/artifacts/:/runner/artifacts/:Z -v /tmp/ansible-navigator_zbdjbbxf/:/runner/:Z --env-file /tmp/ansible-navigator_zbdjbbxf/artifacts/422296ac-88fe-4911-8fb2-4ef133405b6e/env.list --quiet --name ansible_runner_422296ac-88fe-4911-8fb2-4ef133405b6e --user=root registry/ansible/ansible:latest ansible-playbook /ansible/playbook.yml -ce podman -i /ansible/inventory.yml
2023-11-02T19:53:26.931612+00:00 DEBUG 'ansible-runner._handle_command_wrap' command: podman run --rm --tty --interactive -v /ansible/:/ansible/ --workdir /ansible -v /tmp/ssh-XXXXWZC0eH/:/tmp/ssh-XXXXWZC0eH/ -e SSH_AUTH_SOCK=/tmp/ssh-XXXXWZC0eH/agent.1531020 -v /root/.ssh/:/home/runner/.ssh/ -v /root/.ssh/:/root/.ssh/ --group-add=root --ipc=host -v /tmp/ansible-navigator_zbdjbbxf/artifacts/:/runner/artifacts/:Z -v /tmp/ansible-navigator_zbdjbbxf/:/runner/:Z --env-file /tmp/ansible-navigator_zbdjbbxf/artifacts/422296ac-88fe-4911-8fb2-4ef133405b6e/env.list --quiet --name ansible_runner_422296ac-88fe-4911-8fb2-4ef133405b6e --user=root registry/ansible/ansible:latest ansible-playbook /ansible/playbook.yml -ce podman -i /ansible/inventory.yml
2023-11-02T19:53:26.931955+00:00 DEBUG 'ansible_navigator.actions.run_playbook._run_runner' runner requested to start

when adding the -v at the end
cmdline_args:['/ansible/playbook.yml', '-v', '-i', '/ansible/inventory.yml']
STEPS TO REPRODUCE
ansible-navigator run playbook.yml (no other inputs)
ansible-navigator run playbook.yml -v (works correctly)
EXPECTED RESULTS
ansible-navigator run playbook.yml with no other variable execute correctly
ACTUAL RESULTS
usage: ansible-playbook [-h] [--version] [-v] [--private-key PRIVATE_KEY_FILE]
                        [-u REMOTE_USER] [-c CONNECTION] [-T TIMEOUT]
                        [--ssh-common-args SSH_COMMON_ARGS]
                        [--sftp-extra-args SFTP_EXTRA_ARGS]
                        [--scp-extra-args SCP_EXTRA_ARGS]
                        [--ssh-extra-args SSH_EXTRA_ARGS]
                        [-k | --connection-password-file CONNECTION_PASSWORD_FILE]
                        [--force-handlers] [--flush-cache] [-b]
                        [--become-method BECOME_METHOD]
                        [--become-user BECOME_USER]
                        [-K | --become-password-file BECOME_PASSWORD_FILE]
                        [-t TAGS] [--skip-tags SKIP_TAGS] [-C] [-D]
                        [-i INVENTORY] [--list-hosts] [-l SUBSET]
                        [-e EXTRA_VARS] [--vault-id VAULT_IDS]
                        [--ask-vault-password | --vault-password-file VAULT_PASSWORD_FILES]
                        [-f FORKS] [-M MODULE_PATH] [--syntax-check]
                        [--list-tasks] [--list-tags] [--step]
                        [--start-at-task START_AT_TASK]
                        playbook [playbook ...]
ansible-playbook: error: unrecognized arguments: podman

usage: ansible-playbook [-h] [--version] [-v] [--private-key PRIVATE_KEY_FILE]
                        [-u REMOTE_USER] [-c CONNECTION] [-T TIMEOUT]
                        [--ssh-common-args SSH_COMMON_ARGS]
                        [--sftp-extra-args SFTP_EXTRA_ARGS]
                        [--scp-extra-args SCP_EXTRA_ARGS]
                        [--ssh-extra-args SSH_EXTRA_ARGS]
                        [-k | --connection-password-file CONNECTION_PASSWORD_FILE]
                        [--force-handlers] [--flush-cache] [-b]
                        [--become-method BECOME_METHOD]
                        [--become-user BECOME_USER]
                        [-K | --become-password-file BECOME_PASSWORD_FILE]
                        [-t TAGS] [--skip-tags SKIP_TAGS] [-C] [-D]
                        [-i INVENTORY] [--list-hosts] [-l SUBSET]
                        [-e EXTRA_VARS] [--vault-id VAULT_IDS]
                        [--ask-vault-password | --vault-password-file VAULT_PASSWORD_FILES]
                        [-f FORKS] [-M MODULE_PATH] [--syntax-check]
                        [--list-tasks] [--list-tags] [--step]
                        [--start-at-task START_AT_TASK]
                        playbook [playbook ...]

Runs Ansible playbooks, executing the defined tasks on the targeted hosts.
ADDITIONAL INFORMATION
running on a custom image of almalinux with collection installed since it's inside an isolated network
ansible_version:
  details: ansible [core 2.15.4]
environment_variables:
  details:
    ANSIBLE_CACHE_PLUGIN: jsonfile
    ANSIBLE_CACHE_PLUGIN_CONNECTION: /runner/artifacts/dab8654f-cae1-4845-82ce-984dcad5039e/fact_cache
    ANSIBLE_CALLBACK_PLUGINS: /runner/artifacts/dab8654f-cae1-4845-82ce-984dcad5039e/callback
    ANSIBLE_HOST_KEY_CHECKING: 'False'
    ANSIBLE_RETRY_FILES_ENABLED: 'False'
    ANSIBLE_STDOUT_CALLBACK: awx_display
    ANSIBLE_UNSAFE_WRITES: '1'
    AWX_ISOLATED_DATA_DIR: /runner/artifacts/dab8654f-cae1-4845-82ce-984dcad5039e
    HOME: /root
    HOSTNAME: 85aefaa895a2
    LC_CTYPE: C.UTF-8
    PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
    PWD: /runner/project
    SHLVL: '0'
    SSH_AUTH_SOCK: /tmp/ssh-XXXXWZC0eH/agent.1531020
    TERM: xterm
    container: podman
  os_release:
  details:
  - almalinux-mantisbt-project: AlmaLinux-9
    almalinux-mantisbt-project-version: '9.2'
    ansi-color: 0;34
    bug-report-url: 'https://bugs.almalinux.org/ '
    cpe-name: cpe:/o:almalinux:almalinux:9::baseos
    documentation-url: https://wiki.almalinux.org/
    home-url: https://almalinux.org/
    id: almalinux
    id-like: rhel centos fedora
    logo: fedora-logo-icon
    name: AlmaLinux
    platform-id: platform:el9
    pretty-name: AlmaLinux 9.2 (Turquoise Kodkod)
    redhat-support-product: AlmaLinux
    redhat-support-product-version: '9.2'
    version: 9.2 (Turquoise Kodkod)
    version-id: '9.2'

Thank you

cmdargs option is intended to contain not navigator own argument but the underlying called process arguments (ansible-playbook in this case.
We will keep this bug open in order to update the documentation to be more specific.

From what i've tested, if i don't put another flag after the ansible-navigator run playbook.yml, it will fail to run with the error listed
if i add either -v or -check, the playbook executes correctly
so there seems to be a bug when the run doesn't have any arguments added that it tries to send the -ce podman as an argument to ansible-playbook which is not recognized

Hey @nuclear12 , In your given configuration file cmdline argument is declared as cmdline: -ce podman  which is causing this error.
The cmdline option is used for passing extra parameter to the corresponding command.
For example:
---
ansible-navigator:
  ansible:
    cmdline: "--forks 15"

To specify container engine as podman, simply this should work:
ansible-navigator:
  execution-environment:
    container-engine: podman

Try using --ce podman, which is the parameter for navigator at the command line. When navigator doesn't recognize a flag it will pass it to the underlying command.
(that said, we should figure out why we aren't passing it to playbook when -v is used)

Oh.....
Here's the explanation.
If you have cmdline used in your setting file and don't provide any unrecognized parameters at the command line, the settings file entry will be used and passed to ansible-playbook
If you have cmdline used in your setting file and do provide some unrecognized paramater at the command line (e.g.-v) that will get passed to ansible-playbook instead of what is in the settings file.
This is a result of how navigator handles setting precedence: https://ansible.readthedocs.io/projects/navigator/faq/#what-is-the-order-in-which-configuration-settings-are-applied

Hello
following your comments, i've tested changing the cmdline to --forks 15 and now it works with no additional arguments
emptying the cmdline breaks the run with the following error
In ansible-navigator.ansible.cmdline: none is not of type string
commenting the cmdline also enables it to works with no additional arguments
Thanks a lot for your help


Small typo on site

I don't see a repo for the documentation site itself but there's a small typo in the transform docs.

Documentation is on github. I've fixed it in the source, thanks.

Awesome, thanks!


Suggestion: Allow the user to access their own imagery using WMS or similar service

For a project we are doing in Costa Rica, it will be critical to be able to use our own imagery in some cases. A WMS or similar service would probably be the easiest option. It would also be helpful to enable use of subscription services that users have purchased from companies such as Planet (Planet uses WMTS).

This functionality is almost complete. Each institution may add its own imagery sources and projects under that institution may make use of any of these.

Just checked with a WMS service from Spain, seems to be working fine with a couple of bugs
The WMS service I used has these parameters:
Layer : PNOA
JSON : { "SERVICE":"WMS" ,"VERSION":"1.1.1","REQUEST":"GetMap","SRS":"EPSG:4326","WIDTH":"4096","HEIGHT":"4096","LAYERS":"PNOA","STYLES":"default","TRANSPARENT":"TRUE","FORMAT":"image/jpeg" }
You can test it in a project over Spain.
THE BUGS:

There is no way to edit the imagery source. The process of adding WMS services is very error prone (e.g. misttyping the JSON parameters or changing the resolution or format) so you shopuld be able to edit the imagery sources (maybe the base ones like Bing Maps or Digital Globe should be " locked" )
http://i.imgur.com/0jW6gaw.png

When I choose the PNOA as a basemap it works fine assessing plots, but if I go back to the project page (using hte Edit button) the basemap parameter appears empty, even though PNOA is in the list of avaliable sources. see images.

http://i.imgur.com/zurwJEF.png
http://i.imgur.com/gPUGd6u.png

Hi Gary,
Thanks for the update. I'll try it out soon.
Randy
On Wed, Aug 23, 2017 at 4:50 AM, herrtunante<EMAIL_ADDRESS>wrote:

Just checked with a WMS service from Spain, seems to be working fine with
a couple of bugs
The WMS service I used has these parameters:
Layer : PNOA
JSON : { "SERVICE":"WMS" ,"VERSION":"1.1.1","REQUEST":"
GetMap","SRS":"EPSG:4326","WIDTH":"4096","HEIGHT":"4096",
"LAYERS":"PNOA","STYLES":"default","TRANSPARENT":"TRUE","FORMAT":"image/jpeg"
}
You can test it in a project over Spain.
THE BUGS:

There is no way to edit the imagery source. The process of adding WMS
services is very error prone (e.g. misttyping the JSON parameters or
changing the resolution or format) so you shopuld be able to edit the
imagery sources (maybe the base ones like Bing Maps or Digital Globe should
be " locked" )
http://i.imgur.com/0jW6gaw.png
2.
When I choose the PNOA as a basemap it works fine assessing plots, but
if I go back to the project page (using hte Edit button) the basemap
parameter appears empty, even though PNOA is in the list of avaliable
sources. see images.
http://i.imgur.com/zurwJEF.png
http://i.imgur.com/gPUGd6u.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openforis/collect-earth-online/issues/82#issuecomment-324293229,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AdeR19MKAfdBrcI9Y4u9a2lsIypTGgNwks5sbAQGgaJpZM4Ozpjh
.


⚠ Jenkins Plugins Artifactory has degraded performance

In eb382d0, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1438 ms

Resolved: Jenkins Plugins Artifactory performance has improved in e5a9031 after 25 minutes.


[Bug]: Process group watchdog thread terminated with exception: CUDA error: an illegal memory access was encountered

Your current environment

The output of `python collect_env.py`
Collecting environment information...

INFO 10-12 13:49:35 llm_engine.py:184] Initializing an LLM engine (v0.5.5) with config: model='/share/project/huggingface/models/Mistral-Large-Instruct-2407', speculative_config=None, tokenizer='/share/project/huggingface/models/Mistral-Large-Instruct-2407', skip_tokenizer_init=False, tokenizer_mode=auto, revision=None, rope_scaling=None, rope_theta=None, tokenizer_revision=None, trust_remote_code=True, dtype=torch.bfloat16, max_seq_len=8192, download_dir=None, load_format=LoadFormat.AUTO, tensor_parallel_size=8, pipeline_parallel_size=1, disable_custom_all_reduce=False, quantization=None, enforce_eager=False, kv_cache_dtype=auto, quantization_param_path=None, device_config=cuda, decoding_config=DecodingConfig(guided_decoding_backend='outlines'), observability_config=ObservabilityConfig(otlp_traces_endpoint=None, collect_model_forward_time=False, collect_model_execute_time=False), seed=1234, served_model_name=/share/project/huggingface/models/Mistral-Large-Instruct-2407, use_v2_block_manager=False, enable_prefix_caching=False)
WARNING 10-12 13:49:36 multiproc_gpu_executor.py:59] Reducing Torch parallelism from 64 threads to 1 to avoid unnecessary CPU contention. Set OMP_NUM_THREADS in the external environment to tune this value as needed.
INFO 10-12 13:49:36 custom_cache_manager.py:17] Setting Triton cache manager to: vllm.triton_utils.custom_cache_manager:CustomCacheManager
(VllmWorkerProcess pid=52528) INFO 10-12 13:49:42 multiproc_worker_utils.py:215] Worker ready; awaiting tasks
(VllmWorkerProcess pid=52524) INFO 10-12 13:49:42 multiproc_worker_utils.py:215] Worker ready; awaiting tasks
(VllmWorkerProcess pid=52529) INFO 10-12 13:49:42 multiproc_worker_utils.py:215] Worker ready; awaiting tasks
(VllmWorkerProcess pid=52525) INFO 10-12 13:49:42 multiproc_worker_utils.py:215] Worker ready; awaiting tasks
(VllmWorkerProcess pid=52526) INFO 10-12 13:49:42 multiproc_worker_utils.py:215] Worker ready; awaiting tasks
(VllmWorkerProcess pid=52530) INFO 10-12 13:49:42 multiproc_worker_utils.py:215] Worker ready; awaiting tasks
(VllmWorkerProcess pid=52527) INFO 10-12 13:49:42 multiproc_worker_utils.py:215] Worker ready; awaiting tasks
INFO 10-12 13:49:42 utils.py:975] Found nccl from library libnccl.so.2
(VllmWorkerProcess pid=52528) INFO 10-12 13:49:42 utils.py:975] Found nccl from library libnccl.so.2
INFO 10-12 13:49:42 pynccl.py:63] vLLM is using nccl==2.20.5
(VllmWorkerProcess pid=52528) INFO 10-12 13:49:42 pynccl.py:63] vLLM is using nccl==2.20.5
(VllmWorkerProcess pid=52524) INFO 10-12 13:49:42 utils.py:975] Found nccl from library libnccl.so.2
(VllmWorkerProcess pid=52525) INFO 10-12 13:49:42 utils.py:975] Found nccl from library libnccl.so.2
(VllmWorkerProcess pid=52524) INFO 10-12 13:49:42 pynccl.py:63] vLLM is using nccl==2.20.5
(VllmWorkerProcess pid=52525) INFO 10-12 13:49:42 pynccl.py:63] vLLM is using nccl==2.20.5
(VllmWorkerProcess pid=52526) INFO 10-12 13:49:42 utils.py:975] Found nccl from library libnccl.so.2
(VllmWorkerProcess pid=52526) INFO 10-12 13:49:42 pynccl.py:63] vLLM is using nccl==2.20.5
(VllmWorkerProcess pid=52530) INFO 10-12 13:49:42 utils.py:975] Found nccl from library libnccl.so.2
(VllmWorkerProcess pid=52527) INFO 10-12 13:49:42 utils.py:975] Found nccl from library libnccl.so.2
(VllmWorkerProcess pid=52530) INFO 10-12 13:49:42 pynccl.py:63] vLLM is using nccl==2.20.5
(VllmWorkerProcess pid=52527) INFO 10-12 13:49:42 pynccl.py:63] vLLM is using nccl==2.20.5
(VllmWorkerProcess pid=52529) INFO 10-12 13:49:42 utils.py:975] Found nccl from library libnccl.so.2
(VllmWorkerProcess pid=52529) INFO 10-12 13:49:42 pynccl.py:63] vLLM is using nccl==2.20.5
(VllmWorkerProcess pid=52527) INFO 10-12 13:49:44 custom_all_reduce_utils.py:234] reading GPU P2P access cache from /root/.cache/vllm/gpu_p2p_access_cache_for_0,1,2,3,4,5,6,7.json
(VllmWorkerProcess pid=52530) INFO 10-12 13:49:44 custom_all_reduce_utils.py:234] reading GPU P2P access cache from /root/.cache/vllm/gpu_p2p_access_cache_for_0,1,2,3,4,5,6,7.json
INFO 10-12 13:49:44 custom_all_reduce_utils.py:234] reading GPU P2P access cache from /root/.cache/vllm/gpu_p2p_access_cache_for_0,1,2,3,4,5,6,7.json
(VllmWorkerProcess pid=52526) INFO 10-12 13:49:44 custom_all_reduce_utils.py:234] reading GPU P2P access cache from /root/.cache/vllm/gpu_p2p_access_cache_for_0,1,2,3,4,5,6,7.json
(VllmWorkerProcess pid=52524) INFO 10-12 13:49:44 custom_all_reduce_utils.py:234] reading GPU P2P access cache from /root/.cache/vllm/gpu_p2p_access_cache_for_0,1,2,3,4,5,6,7.json
(VllmWorkerProcess pid=52528) INFO 10-12 13:49:44 custom_all_reduce_utils.py:234] reading GPU P2P access cache from /root/.cache/vllm/gpu_p2p_access_cache_for_0,1,2,3,4,5,6,7.json
(VllmWorkerProcess pid=52525) INFO 10-12 13:49:44 custom_all_reduce_utils.py:234] reading GPU P2P access cache from /root/.cache/vllm/gpu_p2p_access_cache_for_0,1,2,3,4,5,6,7.json
(VllmWorkerProcess pid=52529) INFO 10-12 13:49:44 custom_all_reduce_utils.py:234] reading GPU P2P access cache from /root/.cache/vllm/gpu_p2p_access_cache_for_0,1,2,3,4,5,6,7.json
INFO 10-12 13:49:44 shm_broadcast.py:235] vLLM message queue communication handle: Handle(connect_ip='<IP_ADDRESS>', local_reader_ranks=[1, 2, 3, 4, 5, 6, 7], buffer=<vllm.distributed.device_communicators.shm_broadcast.ShmRingBuffer object at 0x7f29e92c7160>, local_subscribe_port=35329, remote_subscribe_port=None)
INFO 10-12 13:49:44 model_runner.py:879] Starting to load model /share/project/huggingface/models/Mistral-Large-Instruct-2407...
(VllmWorkerProcess pid=52527) INFO 10-12 13:49:44 model_runner.py:879] Starting to load model /share/project/huggingface/models/Mistral-Large-Instruct-2407...
(VllmWorkerProcess pid=52524) INFO 10-12 13:49:44 model_runner.py:879] Starting to load model /share/project/huggingface/models/Mistral-Large-Instruct-2407...
(VllmWorkerProcess pid=52529) INFO 10-12 13:49:44 model_runner.py:879] Starting to load model /share/project/huggingface/models/Mistral-Large-Instruct-2407...
(VllmWorkerProcess pid=52528) INFO 10-12 13:49:44 model_runner.py:879] Starting to load model /share/project/huggingface/models/Mistral-Large-Instruct-2407...
(VllmWorkerProcess pid=52526) INFO 10-12 13:49:44 model_runner.py:879] Starting to load model /share/project/huggingface/models/Mistral-Large-Instruct-2407...
(VllmWorkerProcess pid=52530) INFO 10-12 13:49:44 model_runner.py:879] Starting to load model /share/project/huggingface/models/Mistral-Large-Instruct-2407...
(VllmWorkerProcess pid=52525) INFO 10-12 13:49:44 model_runner.py:879] Starting to load model /share/project/huggingface/models/Mistral-Large-Instruct-2407...
Loading safetensors checkpoint shards:   0% Completed | 0/51 [00:00<?, ?it/s]
Loading safetensors checkpoint shards:   2% Completed | 1/51 [00:04<03:36,  4.33s/it]
Loading safetensors checkpoint shards:   4% Completed | 2/51 [00:08<03:25,  4.19s/it]
Loading safetensors checkpoint shards:   6% Completed | 3/51 [00:12<03:25,  4.28s/it]
Loading safetensors checkpoint shards:   8% Completed | 4/51 [00:16<03:17,  4.20s/it]
Loading safetensors checkpoint shards:  10% Completed | 5/51 [00:21<03:18,  4.31s/it]
Loading safetensors checkpoint shards:  12% Completed | 6/51 [00:26<03:18,  4.42s/it]
Loading safetensors checkpoint shards:  14% Completed | 7/51 [00:30<03:13,  4.40s/it]
Loading safetensors checkpoint shards:  16% Completed | 8/51 [00:34<03:06,  4.34s/it]
Loading safetensors checkpoint shards:  18% Completed | 9/51 [00:39<03:06,  4.45s/it]
Loading safetensors checkpoint shards:  20% Completed | 10/51 [00:43<02:59,  4.38s/it]
Loading safetensors checkpoint shards:  22% Completed | 11/51 [00:47<02:54,  4.36s/it]
Loading safetensors checkpoint shards:  24% Completed | 12/51 [00:51<02:46,  4.28s/it]
Loading safetensors checkpoint shards:  25% Completed | 13/51 [00:56<02:43,  4.30s/it]
Loading safetensors checkpoint shards:  27% Completed | 14/51 [01:00<02:40,  4.35s/it]
Loading safetensors checkpoint shards:  29% Completed | 15/51 [01:04<02:32,  4.23s/it]
Loading safetensors checkpoint shards:  31% Completed | 16/51 [01:08<02:24,  4.14s/it]
Loading safetensors checkpoint shards:  33% Completed | 17/51 [01:12<02:21,  4.17s/it]
Loading safetensors checkpoint shards:  35% Completed | 18/51 [01:17<02:20,  4.26s/it]
Loading safetensors checkpoint shards:  37% Completed | 19/51 [01:21<02:14,  4.21s/it]
Loading safetensors checkpoint shards:  39% Completed | 20/51 [01:25<02:08,  4.14s/it]
Loading safetensors checkpoint shards:  41% Completed | 21/51 [01:29<02:03,  4.10s/it]
Loading safetensors checkpoint shards:  43% Completed | 22/51 [01:33<01:58,  4.08s/it]
Loading safetensors checkpoint shards:  45% Completed | 23/51 [01:37<01:57,  4.19s/it]
Loading safetensors checkpoint shards:  47% Completed | 24/51 [01:40<01:38,  3.65s/it]
Loading safetensors checkpoint shards:  49% Completed | 25/51 [01:44<01:42,  3.93s/it]
Loading safetensors checkpoint shards:  51% Completed | 26/51 [01:48<01:38,  3.92s/it]
Loading safetensors checkpoint shards:  53% Completed | 27/51 [01:53<01:36,  4.03s/it]
Loading safetensors checkpoint shards:  55% Completed | 28/51 [01:57<01:35,  4.15s/it]
Loading safetensors checkpoint shards:  57% Completed | 29/51 [02:01<01:30,  4.11s/it]
Loading safetensors checkpoint shards:  59% Completed | 30/51 [02:05<01:27,  4.16s/it]
Loading safetensors checkpoint shards:  61% Completed | 31/51 [02:10<01:24,  4.20s/it]
Loading safetensors checkpoint shards:  63% Completed | 32/51 [02:14<01:20,  4.26s/it]
Loading safetensors checkpoint shards:  65% Completed | 33/51 [02:18<01:17,  4.33s/it]
Loading safetensors checkpoint shards:  67% Completed | 34/51 [02:23<01:13,  4.34s/it]
Loading safetensors checkpoint shards:  69% Completed | 35/51 [02:27<01:08,  4.30s/it]
Loading safetensors checkpoint shards:  71% Completed | 36/51 [02:32<01:05,  4.38s/it]
Loading safetensors checkpoint shards:  73% Completed | 37/51 [02:36<00:59,  4.27s/it]
Loading safetensors checkpoint shards:  75% Completed | 38/51 [02:40<00:55,  4.28s/it]
Loading safetensors checkpoint shards:  76% Completed | 39/51 [02:44<00:51,  4.32s/it]
Loading safetensors checkpoint shards:  78% Completed | 40/51 [02:49<00:48,  4.38s/it]
Loading safetensors checkpoint shards:  80% Completed | 41/51 [02:53<00:43,  4.39s/it]
Loading safetensors checkpoint shards:  82% Completed | 42/51 [02:57<00:39,  4.34s/it]
Loading safetensors checkpoint shards:  84% Completed | 43/51 [03:02<00:34,  4.27s/it]
Loading safetensors checkpoint shards:  86% Completed | 44/51 [03:06<00:30,  4.30s/it]
Loading safetensors checkpoint shards:  88% Completed | 45/51 [03:10<00:25,  4.19s/it]
Loading safetensors checkpoint shards:  90% Completed | 46/51 [03:14<00:21,  4.27s/it]
Loading safetensors checkpoint shards:  92% Completed | 47/51 [03:19<00:17,  4.31s/it]
Loading safetensors checkpoint shards:  94% Completed | 48/51 [03:23<00:12,  4.29s/it]
Loading safetensors checkpoint shards:  96% Completed | 49/51 [03:27<00:08,  4.32s/it]
Loading safetensors checkpoint shards:  98% Completed | 50/51 [03:32<00:04,  4.43s/it]
Loading safetensors checkpoint shards: 100% Completed | 51/51 [03:36<00:00,  4.33s/it]
Loading safetensors checkpoint shards: 100% Completed | 51/51 [03:36<00:00,  4.25s/it]

(VllmWorkerProcess pid=52528) INFO 10-12 13:53:21 model_runner.py:890] Loading model weights took 28.5822 GB
(VllmWorkerProcess pid=52529) INFO 10-12 13:53:21 model_runner.py:890] Loading model weights took 28.5822 GB
(VllmWorkerProcess pid=52527) INFO 10-12 13:53:21 model_runner.py:890] Loading model weights took 28.5822 GB
INFO 10-12 13:53:21 model_runner.py:890] Loading model weights took 28.5822 GB
(VllmWorkerProcess pid=52524) INFO 10-12 13:53:21 model_runner.py:890] Loading model weights took 28.5822 GB
(VllmWorkerProcess pid=52525) INFO 10-12 13:53:21 model_runner.py:890] Loading model weights took 28.5822 GB
(VllmWorkerProcess pid=52530) INFO 10-12 13:53:21 model_runner.py:890] Loading model weights took 28.5822 GB
(VllmWorkerProcess pid=52526) INFO 10-12 13:53:21 model_runner.py:890] Loading model weights took 28.5822 GB
INFO 10-12 13:53:23 distributed_gpu_executor.py:56] # GPU blocks: 54671, # CPU blocks: 5957
(VllmWorkerProcess pid=52526) INFO 10-12 13:53:25 model_runner.py:1181] Capturing the model for CUDA graphs. This may lead to unexpected consequences if the model is not static. To run the model in eager mode, set 'enforce_eager=True' or use '--enforce-eager' in the CLI.
(VllmWorkerProcess pid=52526) INFO 10-12 13:53:25 model_runner.py:1185] CUDA graphs can take additional 1~3 GiB memory per GPU. If you are running out of memory, consider decreasing `gpu_memory_utilization` or enforcing eager mode. You can also reduce the `max_num_seqs` as needed to decrease memory usage.
(VllmWorkerProcess pid=52525) INFO 10-12 13:53:25 model_runner.py:1181] Capturing the model for CUDA graphs. This may lead to unexpected consequences if the model is not static. To run the model in eager mode, set 'enforce_eager=True' or use '--enforce-eager' in the CLI.
(VllmWorkerProcess pid=52525) INFO 10-12 13:53:25 model_runner.py:1185] CUDA graphs can take additional 1~3 GiB memory per GPU. If you are running out of memory, consider decreasing `gpu_memory_utilization` or enforcing eager mode. You can also reduce the `max_num_seqs` as needed to decrease memory usage.
(VllmWorkerProcess pid=52528) INFO 10-12 13:53:25 model_runner.py:1181] Capturing the model for CUDA graphs. This may lead to unexpected consequences if the model is not static. To run the model in eager mode, set 'enforce_eager=True' or use '--enforce-eager' in the CLI.
(VllmWorkerProcess pid=52528) INFO 10-12 13:53:25 model_runner.py:1185] CUDA graphs can take additional 1~3 GiB memory per GPU. If you are running out of memory, consider decreasing `gpu_memory_utilization` or enforcing eager mode. You can also reduce the `max_num_seqs` as needed to decrease memory usage.
(VllmWorkerProcess pid=52530) INFO 10-12 13:53:25 model_runner.py:1181] Capturing the model for CUDA graphs. This may lead to unexpected consequences if the model is not static. To run the model in eager mode, set 'enforce_eager=True' or use '--enforce-eager' in the CLI.
(VllmWorkerProcess pid=52530) INFO 10-12 13:53:25 model_runner.py:1185] CUDA graphs can take additional 1~3 GiB memory per GPU. If you are running out of memory, consider decreasing `gpu_memory_utilization` or enforcing eager mode. You can also reduce the `max_num_seqs` as needed to decrease memory usage.
INFO 10-12 13:53:25 model_runner.py:1181] Capturing the model for CUDA graphs. This may lead to unexpected consequences if the model is not static. To run the model in eager mode, set 'enforce_eager=True' or use '--enforce-eager' in the CLI.
INFO 10-12 13:53:25 model_runner.py:1185] CUDA graphs can take additional 1~3 GiB memory per GPU. If you are running out of memory, consider decreasing `gpu_memory_utilization` or enforcing eager mode. You can also reduce the `max_num_seqs` as needed to decrease memory usage.
(VllmWorkerProcess pid=52527) INFO 10-12 13:53:25 model_runner.py:1181] Capturing the model for CUDA graphs. This may lead to unexpected consequences if the model is not static. To run the model in eager mode, set 'enforce_eager=True' or use '--enforce-eager' in the CLI.
(VllmWorkerProcess pid=52527) INFO 10-12 13:53:25 model_runner.py:1185] CUDA graphs can take additional 1~3 GiB memory per GPU. If you are running out of memory, consider decreasing `gpu_memory_utilization` or enforcing eager mode. You can also reduce the `max_num_seqs` as needed to decrease memory usage.
(VllmWorkerProcess pid=52529) INFO 10-12 13:53:25 model_runner.py:1181] Capturing the model for CUDA graphs. This may lead to unexpected consequences if the model is not static. To run the model in eager mode, set 'enforce_eager=True' or use '--enforce-eager' in the CLI.
(VllmWorkerProcess pid=52529) INFO 10-12 13:53:25 model_runner.py:1185] CUDA graphs can take additional 1~3 GiB memory per GPU. If you are running out of memory, consider decreasing `gpu_memory_utilization` or enforcing eager mode. You can also reduce the `max_num_seqs` as needed to decrease memory usage.
(VllmWorkerProcess pid=52524) INFO 10-12 13:53:25 model_runner.py:1181] Capturing the model for CUDA graphs. This may lead to unexpected consequences if the model is not static. To run the model in eager mode, set 'enforce_eager=True' or use '--enforce-eager' in the CLI.
(VllmWorkerProcess pid=52524) INFO 10-12 13:53:25 model_runner.py:1185] CUDA graphs can take additional 1~3 GiB memory per GPU. If you are running out of memory, consider decreasing `gpu_memory_utilization` or enforcing eager mode. You can also reduce the `max_num_seqs` as needed to decrease memory usage.
(VllmWorkerProcess pid=52524) INFO 10-12 13:53:46 custom_all_reduce.py:223] Registering 6195 cuda graph addresses
INFO 10-12 13:53:46 custom_all_reduce.py:223] Registering 6195 cuda graph addresses
(VllmWorkerProcess pid=52530) INFO 10-12 13:53:46 custom_all_reduce.py:223] Registering 6195 cuda graph addresses
(VllmWorkerProcess pid=52528) INFO 10-12 13:53:46 custom_all_reduce.py:223] Registering 6195 cuda graph addresses
(VllmWorkerProcess pid=52525) INFO 10-12 13:53:46 custom_all_reduce.py:223] Registering 6195 cuda graph addresses
(VllmWorkerProcess pid=52529) INFO 10-12 13:53:46 custom_all_reduce.py:223] Registering 6195 cuda graph addresses
(VllmWorkerProcess pid=52526) INFO 10-12 13:53:46 custom_all_reduce.py:223] Registering 6195 cuda graph addresses
(VllmWorkerProcess pid=52527) INFO 10-12 13:53:46 custom_all_reduce.py:223] Registering 6195 cuda graph addresses
(VllmWorkerProcess pid=52525) INFO 10-12 13:53:46 model_runner.py:1300] Graph capturing finished in 21 secs.
(VllmWorkerProcess pid=52527) INFO 10-12 13:53:46 model_runner.py:1300] Graph capturing finished in 20 secs.
(VllmWorkerProcess pid=52528) INFO 10-12 13:53:46 model_runner.py:1300] Graph capturing finished in 21 secs.
(VllmWorkerProcess pid=52524) INFO 10-12 13:53:46 model_runner.py:1300] Graph capturing finished in 20 secs.
(VllmWorkerProcess pid=52529) INFO 10-12 13:53:46 model_runner.py:1300] Graph capturing finished in 20 secs.
INFO 10-12 13:53:46 model_runner.py:1300] Graph capturing finished in 21 secs.
(VllmWorkerProcess pid=52526) INFO 10-12 13:53:46 model_runner.py:1300] Graph capturing finished in 21 secs.
(VllmWorkerProcess pid=52530) INFO 10-12 13:53:46 model_runner.py:1300] Graph capturing finished in 21 secs.
[rank0]:[E1012 13:56:04.572981385 ProcessGroupNCCL.cpp:1515] [PG 3 Rank 0] Process group watchdog thread terminated with exception: CUDA error: an illegal memory access was encountered
Compile with `TORCH_USE_CUDA_DSA` to enable device-side assertions.

Exception raised from c10_cuda_check_implementation at ../c10/cuda/CUDAException.cpp:43 (most recent call first):
frame #0: c10::Error::Error(c10::SourceLocation, std::string) + 0x96 (0x7f2ba2d77f86 in /root/miniconda3/envs/harness/lib/python3.10/site-packages/torch/lib/libc10.so)
frame #1: c10::detail::torchCheckFail(char const*, char const*, unsigned int, std::string const&) + 0x64 (0x7f2ba2d26d10 in /root/miniconda3/envs/harness/lib/python3.10/site-packages/torch/lib/libc10.so)
frame #2: c10::cuda::c10_cuda_check_implementation(int, char const*, char const*, int, bool) + 0x118 (0x7f2ba31cff08 in /root/miniconda3/envs/harness/lib/python3.10/site-packages/torch/lib/libc10_cuda.so)
frame #3: c10d::ProcessGroupNCCL::WorkNCCL::finishedGPUExecutionInternal() const + 0x56 (0x7f2b54d6b3e6 in /root/miniconda3/envs/harness/lib/python3.10/site-packages/torch/lib/libtorch_cuda.so)
frame #4: c10d::ProcessGroupNCCL::WorkNCCL::isCompleted() + 0xa0 (0x7f2b54d70600 in /root/miniconda3/envs/harness/lib/python3.10/site-packages/torch/lib/libtorch_cuda.so)
frame #5: c10d::ProcessGroupNCCL::watchdogHandler() + 0x1da (0x7f2b54d772ba in /root/miniconda3/envs/harness/lib/python3.10/site-packages/torch/lib/libtorch_cuda.so)
frame #6: c10d::ProcessGroupNCCL::ncclCommWatchdog() + 0x10c (0x7f2b54d796fc in /root/miniconda3/envs/harness/lib/python3.10/site-packages/torch/lib/libtorch_cuda.so)
frame #7: <unknown function> + 0xdbbf4 (0x7f2ba24c7bf4 in /root/miniconda3/envs/harness/bin/../lib/libstdc++.so.6)
frame #8: <unknown function> + 0x94ac3 (0x7f2c44da3ac3 in /usr/lib/x86_64-linux-gnu/libc.so.6)
frame #9: <unknown function> + 0x126850 (0x7f2c44e35850 in /usr/lib/x86_64-linux-gnu/libc.so.6)

Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

Same error I ran Qwen2-72B-Instruct

I encountered the same error as well.
Models: qwen2.5-32b-instruct
GPUs: 4xA30
[rank2]:[E1022 04:46:39.305424460 ProcessGroupNCCL.cpp:1515] [PG 3 Rank 2] Process group watchdog thread terminated with exception: CUDA error: an illegal memory access was encountered

I get the same error.


Errors on queries

I'm getting a weird bug that I have no idea how to resolve or even properly identify.
My prolog KB provides a clause add_item/2 that (ultimately) adds a new item to the knowledge base.
I call this in my python main method with prolog.query() for an initial item, everything works fine, I get back something and calling list() on the return gives me {}. Great. Doing the same with another item i2 right afterwards does the same.
But. When I do the query-call for i2 later, in the constructor method of a class of mine (where it ultimately should happen), it doesn't work. In a normal run, calling list() on the returned value kills the program with a segmentation fault. In debug mode, evaluating list() in the debugger shell prints No more messages and the program is being killed.
Any ideas what's going on here?

Note to the future:
Closing the issue since the issue is old.
Please provide a reproducer if the issue rears its head again.


Update selection when deselecting week in batch date edit

When selecting a week in the batch date edit header, the selected terms update to be consistent. When deselecting a week, this doesn’t happen yet.

Reassigning to @Coenego for review.

Coverage remained the same at 100.0% when pulling 7f0c3038bee8ff7daa9e48282d1760ecb422ff76 on bp323:issue-199 into 38e7bb03c9e48b623fedec7993cb0fa79765db84 on CUL-DigitalServices:master.


next-sass seems to not work with Next 7

I get the following when trying to launch my next server:
Error: Chunk.entrypoints: Use Chunks.groupsIterable and filter by instanceof Entrypoint instead

I've created a stripped down app to demonstrate the issue. I'm not a webpack 4 wizard, so have no clue how to fix it 😢. Any ideas on how to fix or workaround would be awesome, I really want to upgrade to next@7!
Just calling withSass in next.config.js seems to be enough to trigger the error, you don't even need to import a scss file.
Problem does not occur with next-css.

Just had to publish the new versions, moving parts, sorry for the delay 🙏

Thanks @timneutkens !

Is this solved? I used "@zeit/next-sass": "^0.2.0", and "next": "7.0.0", and I'm stuck here.


Fix import clash between Godot and system modules

like #25764. :p
Fix a bug like #24965 in branch 3.0.

Superseded by f4b3756e8.
Please use git cherry-pick -x <commit hash> to backport such changes instead of reimplementing them from scratch. That makes it easier to go back to the original commit, preserves author credits and date, and ensures that we do the same changes.

I tried.But Failed.
Can you do that as soon as possible？

I did already. :)


fix(transformer): arrow function transform alter </this>

Arrow function transform transforms this in <this> (JSX opening element), but was missing out transforming </this> (JSX closing element).

#3627  👈
main

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

Join @overlookmotel and the rest of your teammates on  Graphite

Currently, the arrow function plugin has almost no test cases, can you add a test for this change?

@Dunqing This has been merged this before I got a chance to add the test you requested.
To be honest, I don't think it's worthwhile adding tests at this stage for 2 reasons:
First, as noted in the code comments added in #3634, there are various problems with the transform at present, and some are not resolvable until TS transforms are modified to update the scope tree. So in my view, the best approach to testing is to later on solidify the implementation, and then enable the Babel conformance tests for arrow function transforms.
Secondly, if we do #3528, then we can remove the special handling of <this> in arrow function transform, as this as a JSX element name will just be a standard ThisExpression (https://github.com/oxc-project/oxc/issues/3528#issuecomment-2150843938). So tests that we add now for this will become redundant.
But if you disagree, that's fine - please just let me know, and I'll add one.


JVM crash due to EXCEPTION_ACCESS_VIOLATION in ConcurrentGCThread

Please provide a brief summary of the bug
The Swing application crashes sometimes after running a few minutes and other times after a few hours.
We have multiple users running the application but the crash occurs more often for a subset of users that have heavy profiles (more memory used, more data processing, more GC)
here are some of the hs_err file generated when crash happens
hs_err_pid23884.log

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffac3463e01, pid=23884, tid=17032
#
# JRE version: OpenJDK Runtime Environment Temurin-<IP_ADDRESS>+1 (<IP_ADDRESS>+1) (build <IP_ADDRESS>+1)
# Java VM: OpenJDK 64-Bit Server VM Temurin-<IP_ADDRESS>+1 (<IP_ADDRESS>+1, mixed mode, tiered, compressed oops, g1 gc, windows-amd64)
# Problematic frame:
# V  [jvm.dll+0x193e01]
#
# No core dump will be written. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
#   https://github.com/adoptium/adoptium-support/issues
#

---------------  S U M M A R Y ------------

Command Line: -Djava.io.tmpdir=C:\Users\markz\.tora\com.tora.g2.launchpad\bootstrapper\installations\TORA OEMS PROD\tmp -Dsun.awt.nopixfmt=true -Dsun.java2d.d3d=false -Dsun.java2d.noddraw=true -XX:+UseG1GC -XX:+HeapDumpOnOutOfMemoryError -XX:+PrintCommandLineFlags -XX:+PrintFlagsFinal -XX:+ResizeTLAB -XX:+ScavengeBeforeFullGC -XX:+UseCompressedOops -XX:+UseNUMA -XX:+UseStringDeduplication -XX:+UseTLAB -XX:MaxGCPauseMillis=100 -XX:MaxMetaspaceSize=384M -XX:MaxNewSize=2G -XX:NewSize=2G -XX:StringDeduplicationAgeThreshold=6 -Xlog:gc*::time,uptime,level,tags: -Xlog:gc*::time,uptime,level,tags: -Xms8G -Xmx16G -Xss2m -verbose:gc -XX:CompileCommand=exclude,java.swing.plaf.basic.BasicSplitPaneUI$BasicHorizontalLayoutManager::layoutContainer C:\Users\markz\.tora\com.tora.g2.launchpad\bootstrapper\installations\TORA OEMS PROD\versions\11.25.0\launchers\0430749e5ccb53eb0e10328c5de88346b3d5f82105ca9df66a03ed3cb5d34a9c.jar -cdist prod/config_gui/cdist_config_all.xml -forceCompression true -forceSSL true -language ENGLISH -launcher launchpad:bootstrapper -listenport 17700 -logmsg true -ping 3000 -title TTS -usageinfotoserver true -screenLocation 468,246

Host: Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz, 12 cores, 31G,  Windows 11 , 64 bit Build 22621 (10.0.22621.1344)
Time: Tue Apr  4 10:38:34 2023 Eastern Daylight Time elapsed time: 23414.169947 seconds (0d 6h 30m 14s)

---------------  T H R E A D  ---------------

Current thread (0x000001dd7d2fb000):  ConcurrentGCThread "G1 Conc#0" [stack: 0x0000001083c00000,0x0000001083d00000] [id=17032]

Stack: [0x0000001083c00000,0x0000001083d00000],  sp=0x0000001083cffaa8,  free space=1022k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V  [jvm.dll+0x193e01]

siginfo: EXCEPTION_ACCESS_VIOLATION (0xc0000005), reading address 0x0000000000000110

Register to memory mapping:

RIP=0x00007ffac3463e01 jvm.dll
RAX=0x0 is NULL
RBX=0x0421110040404129 is an unknown value
RCX=0x0000000800000009 is pointing into metadata
RDX=0x000000069d981420 is an oop:
[error occurred during error reporting (printing register info), id 0xc0000005, EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffac38dbc2d]

Please provide steps to reproduce where possible
I am not able to reproduce it but it seems to be related to user machine and higm memory usage\gc activity
Expected Results
no crash
Actual Results
the application crashes randomly
What Java Version are you using?
Temurin-<IP_ADDRESS>+1
What is your operating system and platform?
Windows 11
How did you install Java?
No response
Did it work before?
the crash did not occured when we used oracle jdk 8u121

Did you test with the latest update version?
No response
Did you test with other Java versions?
No response
Relevant log output
No response

@adriantoganel please upgrade 11.0.18 and send in crash logs if they occur.

Our customers, who are using JVM 11.0.21_9, have continued to report JVM crashes which exhibit this signature

Hi,

does not work for us as can be seen in the log files
There is a typo, the package start with javax not java (javax.swing.plaf.basic.BasicSplitPaneUI)

@adriantoganel Thank you for spotting that!! Can't see the forest for the trees sometimes!

hs_err_pid15064.log replay_pid15064.log
Our customers, who are using JVM 11.0.21_9, have continued to report JVM crashes which exhibit this signature.
Further, the fix in https://bugs.openjdk.org/browse/JDK-8304428 to use -XX:CompileCommand=exclude,java.swing.plaf.basic.BasicSplitPaneUI$BasicHorizontalLayoutManager::layoutContainer does not work for us as can be seen in the log files

Hi i have the same crash happening again and again, with the same problematic frame, can u please tell me how u fix it, I cant understand ur comment

Add -XX:CompileCommand=exclude,javax.swing.plaf.basic.BasicSplitPaneUI$BasicHorizontalLayoutManager::layoutContainer to your command line

hs_err_pid15064.log replay_pid15064.log
Our customers, who are using JVM 11.0.21_9, have continued to report JVM crashes which exhibit this signature.
Further, the fix in https://bugs.openjdk.org/browse/JDK-8304428 to use -XX:CompileCommand=exclude,java.swing.plaf.basic.BasicSplitPaneUI$BasicHorizontalLayoutManager::layoutContainer does not work for us as can be seen in the log files

Hi i have the same crash happening again and again, with the same problematic frame, can u please tell me how u fix it, I cant understand ur comment

Yes, my previous CompileCommand has java.swing... not the required javax.swing... .  Please use the JVM argument that @karianna suggests above


Bump omero-test-infra to OMERO 5.5

See https://travis-ci.org/sbesson/omero-plugins/builds/545627655 for an assessment of the impact on the existing plugins

omero-metadata fails but should be fixed by https://github.com/ome/omero-metadata/pull/20
omero-iviewer fails due to webpack issues independently of this PR
minimal-omero-client has not been updated to support OMERO 5.5 yet

see https://github.com/ome/minimal-omero-client/pull/42

Merging as the impact is minimal (and largely contained) and this is necessary to fix omero-mapr builds.


Split PR 982 up per feature

We will split up PR #982 into smaller PR's so we can review it more easily.
The features per portal are:

Devhub.near
[ ] #999
[ ] #1000
[ ] #1001

Accepted Terms and Conditions
Editor.jsx

[ ] #1002
Events Committee ( uses mostly the same components as Devhub. in PR #982 I removed the dropdown and simple MDE to use DevHub's. So these issues are the same as for Devhub.
[ ] #1002
[ ] #999
[ ] #1000
Infrstructure Committee
[ ] SimpleMDE, Dropdown, Feed
[ ] Rfp Dropdown, Rfp Feed and Rfp reference in the markdown editor

The remaining task is to split the infrastructure committee features into individual issues. This will allow us to track progress and close them with separate PRs.


BCDBFS Links

The idea is to be able to share files from your BCDB with other 3Bots without copying the data.
Use case

3bot A wants to share file /myfile.txt with 3bot B
3bot A will send the file link to 3bot B
3bot B will store the link in the specified directory (in this case it will be "/")
3bot B now has basic metadata of the file/dir and some info pointing to 3bot A
when 3bot B tries to read the file/dir content it will request it from 3bot A

Prerequisites

[ ] Threebot client to be able to comunicate with another 3bot given only the 3bot id
[ ] Address book and the communication layer should be working well.

tasks

[ ] implement Link model
[ ] add Links support to bcdbfs (reading from another 3bot)
[ ] implement actor to receive and send a link

check with kristof for client/server rpc model

requires threefoldtech/jumpscalex_threebot#50


Usercard command fix

Pull request checklist:

[ ] CHANGELOG.md was updated, if applicable

I'm not sure if changes like this really deserve a changelog entry. Thoughts?
Description
Minor bugfix:
Opening a usercard via the /usercard someone command will now respect the "Automatically close user popup" setting.

I'm not sure if changes like this really deserve a changelog entry. Thoughts?

Sure, I think this deserves a "Bugfix: [...]" entry. :smile:


borgs don't scream

About the PR

Borgs do not get that useless "scream" action
Why / Balance

Basically a bugfix
Technical details

Allows for ScreamAction in VocalComponent to be null to do add any actions on VocalSystem startup
Media

https://youtu.be/Teh6Uy1m6zg
Requirements

[X] I have read and am following the Pull Request and Changelog Guidelines.
[X] I have added media to this PR or it does not require an ingame showcase.

Changelog

:cl: pheenty

fix: Fixed borgs being given the scream action.

see #32329

see #32329

I've seen it, still doesn't hurt to add an option to block screaming but allow other emotes, if not for borgs then maybe for something else (pais?)


vmIdleTimeout has no effect

Version
Version 10.0.22000.739
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps
Into %userprofile%/.wslconfig add:
[wsl2] vmIdleTimeout=-1
in order to completely disable the timeout.
In Powershell run
wsl --shutdown
Start WSL by opening a Terminal.
Close the Terminal so that nothing is running.
Check the current state of the machine by running in powershell:
wsl --list --verbose
It should show STATE Running.
Expected Behavior
Check again, after for example 5 minutes.
It should show STATE Running.
Actual Behavior
Check again, after for example 5 minutes.
It shows the STATE Stopped.
Diagnostic Logs
#8642

I was thinking the same thing for most of today, but believe it or not, it appears to be working as intended.  The documentation wording on this feature is accurate, but confusing:

key
value
default
notes

vmIdleTimeout
number*
60000
The number of milliseconds that a VM is idle, before it is shut down. Only available for Windows 11.

Technically, it should say "the VM", because there's only one WSL2 virtual machine running.
The confusion is that this refers to the managed VM running WSL2 itself, not the WSL2 distribution/container/instance.
There are two timers that are in play here:

The first timer is how long a WSL instance is idle before it is terminated.  Think of this as a wsl --terminate <distro> that occurs when there are no more running processes in it other than init.  This is non-configurable, but #6782 is a feature request for the ability to configure it.  As far as I can tell, this is hard-coded at about 15 seconds.
This has been around since shortly after WSL1 was launched 6 years ago.  It occurs for both WSL1 and WSL2 instances.

The second timer is specific to the WSL2 managed (as in, we can't see it or interact with it, for the most part) VM.  This is a single shared VM, which is why I say it would be more accurate to call it *"the VM" in the docs.  Even after an instance is terminated, the WSL2 VM continues to run and consume memory.
A wsl --shutdown essentially terminates this virtual machine (and presumably some other activities).
You can see this by looking for several processes in the task manager:

Vmmem:  vmmem.exe
Virtual Machine Worker Process: vmwp.exe

These will show up when you first run a WSL2 instance (which starts the VM) and will go away when the VM is shutdown (either via vmIdleTimeout or wsl --shutdown)
You can also see the VM start up and shut down in the Event Viewer under Applications and Services Logs -> Microsoft -> Windows -> Hyper-V-Worker -> Admin.
The vmIdleTimeout is specific to the VM, and that timer starts once all WSL2 distributions/instances/containers have terminated.

So once you exit the last WSL2 VM, assuming no other processes are running in the background:
* A 15 second timer starts, after which the instance itself is terminated
* *Then*, once the last instance is terminated, the "idle" state timer begins.  60 seconds (by default) after this, the WSL2 VM will shut down.

So setting vmIdleTimeout=-1 will simply keep the VM, but not the instance, running.
Side note:  You can also watch the VM shut down if you turn on debugConsole=true.


feat(frontend): Created a first scoreboard component

Desktop Scoreboard
https://github.com/keep-starknet-strange/tsubasa/assets/37301269/cbd89411-333a-46b2-a5db-9244a3119dd7
Mobile Scoreboard
https://github.com/keep-starknet-strange/tsubasa/assets/37301269/1d1dd582-e9a1-46af-b1ba-f6c7f42a7b48
Still need to be done: animation when the score goes back when the animation of the goal text is finished

I thought I would not include it, as it is the same as the Goaaaaal one, let me know if you want me to add it


Error during build

Hi clip
I encountered an issue during the build process: "ImpersonateAnonymousToken' was not declared in this scope..." which made me wonder if it could be from the version of my compiler.
which compiler/version do you use?
For me I use : c++.exe (MinGW.org GCC-6.3.0-1) 6.3.0
Thanks in advance?

I tried to compile with the latest version 14.2.0 and it worked!


AWS Cloud Map custom attributes for instances

AWS Cloud Map provides a way to inject custom attributes when registering instances. These attributes can be used to discover-instances with filters that allows subsetting. One use-case for subsets is to configure traffic-routing in service-mesh context. For e.g. one can create a headless service and have all the pods be registered under Cloud Map service with labels as custom attributes.
Currently there is no support for injecting custom attributes in aws_sd.go. IIUC endpoint in external-dns maps to k8s-service and target maps to pod. However, target is a string making it unsuitable to support this use-case.

Is it bad idea to make target a struct with labels as a field?
I am wondering if anyone has looked at this use-case and have any thoughts.

To avoid major refactoring by changing target, I proceeded by adding a TargetLabels map to Endpoint struct. See https://github.com/kiranmeduri/external-dns/commit/ee17895807ae1cd774ebc3cdf4bb04c4f1ad5db2. If there is interest, I can polish it and open a PR. Please let me know.


Feature requests

First of all, very cool app, thanks! Can you please address a couple of things:

Hide/make inactive dictation button on aplite. It's not supposed to work anyway, having it clickable on aplite is just confusing.
Make vibration optional/configurable. I think it may be annoying for some people, I'd personally disabled it.

I've just done both, as well as chalk support. Thanks for the suggestions!


Lower priority: we should lint our codebase

Today github actions run the default github superlinter on all codebase at each CL. However we have never been able to pass the linter. So we should probably fix it at one point.

codebase linted as of #69.
lint lint_fix make recipes exit for make file to check and correct linting respectively.


Appstudio update mvp-test-component

Pipelines as Code configuration proposal

Pipelines as Code CI/mvp-test-component-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
5 seconds
init

✅ Succeeded
20 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
17 seconds
deprecated-base-image-check

✅ Succeeded
16 seconds
inspect-image

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
20 seconds
clair-scan

✅ Succeeded
12 seconds
sbom-json-check

✅ Succeeded
13 seconds
label-check

✅ Succeeded
15 seconds
optional-label-check

✅ Succeeded
7 seconds
show-summary


Merge cloud to master

With the announcement of 1.0, it might be a good idea to get back to working off master to reflect our new direction.

[ ] Branch legacy off current master
[ ] Update README.md to reflect 1.0 with updated content, Under Construction™
[ ] Update CI workflows, scripts to use legacy vs master
[ ] Update CI workflows, scripts to use master vs cloud
[ ] Rename branch protection rules
[ ] Remove dotfiles no longer relevant; general cleanup
[ ] Merge cloud into master (maintain website)

Any thoughts/objections @AndrewDryga

I think there are two more tasks to merge it:

[ ] Copy the new website folder to cloud before merging.
[ ] Configure release drafter for the cd pipeline to start building containers with tags

Other than that, we should be good.

I would name the legacy branch 0.7 for transparency rather than legacy so that people can find it if they want to

Was thinking this too. K. I may take a stab at this over the weekend since it'll be a big blocker for everyone.

Ended up going with legacy since that will age better in case need to cut a 0.8.


Use Window Scrollbars + Made Headers Sticky

@tiagobento @ge0ffrey This is the "use window as viewport + sticky headers" changes, using the absolute positioning system

@tiagobento In regard to (4), that is caused by the REST endpoint returning all the shifts instead of only the one visible. It is fixed in #110.

I am merging this, as it seems like Christopher's last commits fix most feedback. @Christopher-Chianelli if any of Tiago's feedback is not address, please open a jira to track it decently.
Potentially to track:

Date/Time ticks might need some z-index adjustment since they stay on top of the overlay layer when selecting a Blob (tested on the Spot Roster)

The titles of the Roster screens are not the same as the tables screens, I'd check the paddings. The Date/Time ticks might need a little padding too after some scroll down on the page.
I'd give the Spot names a little more contrast, I'm not a designer but setting it to a slightly larger and bold font might be better than leave it as is.

I'm assuming the overlapping that happens on the beginning of a lane is not related to this PR, right?

No, it's being handled in https://issues.jboss.org/browse/PLANNER-1094
Thanks for the feedback/review @tiagobento


RecordXWrapper in hiora.interruptibility

Encountering an import error in the ProcessedQNISQ notebook on line 6: from gym.envs.safety.cartpole.record_x_wrapper import RecordXWrapper
There isn't any cartpole module within safety, but there also isn't a record_x_wrapper class or module in any of the current modules located there.  Is this a custom branch/fork of gym, or am I missing something?

Yes, you concluded right. Sorry for confusing you! (I didn't expect that people would try and run the code.) Here you can find the RecordXWrapper in my fork of the Gym: https://github.com/rmoehn/gym/tree/interr-measure/gym/envs/safety/cartpole
Feel free to reach out again if you encounter more problems or are interested in anything.


feat(service-details): ability to manage networks

closes #1807

WIP, has some bugs that need fixing.

[ ] Bridge network name is not shown: Id of bridge network from service inspect does not match Id of bridge network returned by docker, we could possibly get this from services

[ ] Removing the bridge network doesn't work

[ ] Add network dropdown shows networks that a service cannot connect to or is already connected to: we should probably filter this

[ ] Reset changes doesn't work

[ ] Adding/removing the ingress network or adding/removing other networks while connected to the ingress network doesn't work: docker handles the ingress network, so options should be disabled in UI or we should give error message as to why it fails e.g. remove ports to remove the ingress network

Closed in favor of https://github.com/portainer/portainer/pull/3957


Add dotenv backend (#3)

Fixes #3
To be merged after CI PR and API change PR.

This contains a bunch of unrelated changes. Could you split it up into different PRs ?

It appears this way because I branched off another PR, not master.  It will look right after I merge master.


Pullrequest ms5611 multibus

This fixes the ms5611 on PX4v1 and supports all 4 bus combinations

Thanks!

Applied via cherry-pick, thanks!


feat(UI): accent colours

This PR simply adds support for personalised accent colours as seen in other userstyles.
Instead of always using green for the --color-brand-green users can now chose from all available Catppuccin colours. c:

Example with mauve as accent colour:

ah … Auto formatting also removed indents from empty lines as it seems. I'll pretend that this is intended and mark it as a feature. :^)

Thanks!


Update documentation for macOS, remove references to Sample Web UI that no longer exists

I'm new to Kythe and got tripped up a bit by the documentation being a bit out of date.

Thanks for the updates.
The linter is failing some format checks. Can you follow https://kythe.io/contributing/#linting-and-testing so the files get formatted correctly? I think clang-format in particular will change some files once you set up the commit hooks.

I can't seem to install the pre-commit hooks because I have core.hooksPath set on my machine. Is there away for me to manually run the checks? Could you share the results of the lint job showing the lint failures?

It also seems like some of these fail to run on macOS
./tools/git/commit-msg.sh
Error: Cannot find module "@commitlint/config-conventional" from "/Users/eamorde/Development/kythe"
    at resolveId (/private/var/tmp/_bazel_eamorde/7396ce93e4a02c32055c37ee57a28b26/execroot/io_kythe/bazel-out/darwin_arm64-fastbuild/bin/tools/git/commitlint.sh.runfiles/io_kythe/node_modules/.aspect_rules_js/@commitlint+resolve-extends@17.6.7/node_modules/@commitlint/resolve-extends/src/index.ts:131:14)
    at resolveConfig (/private/var/tmp/_bazel_eamorde/7396ce93e4a02c32055c37ee57a28b26/execroot/io_kythe/bazel-out/darwin_arm64-fastbuild/bin/tools/git/commitlint.sh.runfiles/io_kythe/node_modules/.aspect_rules_js/@commitlint+resolve-extends@17.6.7/node_modules/@commitlint/resolve-extends/src/index.ts:105:20)
    at /private/var/tmp/_bazel_eamorde/7396ce93e4a02c32055c37ee57a28b26/execroot/io_kythe/bazel-out/darwin_arm64-fastbuild/bin/tools/git/commitlint.sh.runfiles/io_kythe/node_modules/.aspect_rules_js/@commitlint+resolve-extends@17.6.7/node_modules/@commitlint/resolve-extends/src/index.ts:51:20
    at Array.reduce (<anonymous>)
    at loadExtends (/private/var/tmp/_bazel_eamorde/7396ce93e4a02c32055c37ee57a28b26/execroot/io_kythe/bazel-out/darwin_arm64-fastbuild/bin/tools/git/commitlint.sh.runfiles/io_kythe/node_modules/.aspect_rules_js/@commitlint+resolve-extends@17.6.7/node_modules/@commitlint/resolve-extends/src/index.ts:49:13)
    at resolveExtends (/private/var/tmp/_bazel_eamorde/7396ce93e4a02c32055c37ee57a28b26/execroot/io_kythe/bazel-out/darwin_arm64-fastbuild/bin/tools/git/commitlint.sh.runfiles/io_kythe/node_modules/.aspect_rules_js/@commitlint+resolve-extends@17.6.7/node_modules/@commitlint/resolve-extends/src/index.ts:25:19)
    at load (/private/var/tmp/_bazel_eamorde/7396ce93e4a02c32055c37ee57a28b26/execroot/io_kythe/bazel-out/darwin_arm64-fastbuild/bin/tools/git/commitlint.sh.runfiles/io_kythe/node_modules/.aspect_rules_js/@commitlint+load@17.7.2/node_modules/@commitlint/load/src/load.ts:56:33)
    at async main (/private/var/tmp/_bazel_eamorde/7396ce93e4a02c32055c37ee57a28b26/execroot/io_kythe/bazel-out/darwin_arm64-fastbuild/bin/tools/git/commitlint.sh.runfiles/io_kythe/node_modules/.aspect_rules_js/@commitlint+cli@17.7.2/node_modules/@commitlint/cli/src/cli.ts:214:17) {
  code: 'MODULE_NOT_FOUND'
}

Feel free to commit changed to my branch. Maintainers should have write access to my fork

/gcbrun

What's the current lint failure?

Looks like commitlintrc.js
Step #1: diff --git a/.commitlintrc.js b/.commitlintrc.js
Step #1: index 00e078c0a..03750f60e 100644
Step #1: --- a/.commitlintrc.js
Step #1: +++ b/.commitlintrc.js
Step #1: @@ -20,57 +20,60 @@ module.exports = {
Step #1:    rules : {
Step #1:      'scope-case' : [ 2, 'always', 'snake-case' ],
Step #1:      'scope-empty' : [ 1, 'never' ],
Step #1: -    'scope-enum' : [
Step #1: -      1, 'always',
Step #1: -      [
Step #1: -        'api',             // user-facing API (e.g. XRefService)
Step #1: -        'dev',             // developer tooling/scripting (e.g. linting)
Step #1: -        'example',         // example tools or docs (e.g. sample xref service)
Step #1: -        'extraction',      // compilation extraction
Step #1: -        'indexing',        // semantic analysis over compilations
Step #1: -        'post_processing', // serving data construction
Step #1: -        'schema',          // graph schema design
Step #1: -        'serving',         // server logic or data formats
Step #1: -        'tooling',         // CLI utilities (e.g. entrystream)
Step #1: +    'scope-enum' :
Step #1: +                 [
Step #1: +                   1, 'always',
Step #1: +                   [
Step #1: +                     'api',        // user-facing API (e.g. XRefService)
Step #1: +                     'dev',        // developer tooling/scripting (e.g. linting)
Step #1: +                     'example',    // example tools or docs (e.g. sample xref
Step #1: +                                   // service)
Step #1: +                     'extraction', // compilation extraction
Step #1: +                     'indexing',   // semantic analysis over compilations
Step #1: +                     'post_processing', // serving data construction
Step #1: +                     'schema',          // graph schema design
Step #1: +                     'serving',         // server logic or data formats
Step #1: +                     'tooling',         // CLI utilities (e.g. entrystream)
Step #1:
Step #1: -        // Language-specific scopes
Step #1: -        'cxx_common',
Step #1: -        'cxx_extractor',
Step #1: -        'cxx_indexer',
Step #1: -        'go_common',
Step #1: -        'go_extractor',
Step #1: -        'go_indexer',
Step #1: -        'java_common',
Step #1: -        'java_extractor',
Step #1: -        'java_indexer',
Step #1: -        'jvm_common',
Step #1: -        'jvm_extractor',
Step #1: -        'jvm_indexer',
Step #1: -        'rust_common',
Step #1: -        'rust_extractor',
Step #1: -        'rust_indexer',
Step #1: -        'typescript_common',
Step #1: -        'typescript_extractor',
Step #1: -        'typescript_indexer',
Step #1: -      ]
Step #1: -    ],
Step #1: -    'type-enum' : [
Step #1: -      2, 'always',
Step #1: -      [
Step #1: -        'build',
Step #1: -        'chore',
Step #1: -        'ci',
Step #1: -        'deprecation',
Step #1: -        'docs',
Step #1: -        'feat',
Step #1: -        'fix',
Step #1: -        'perf',
Step #1: -        'refactor',
Step #1: -        'release',
Step #1: -        'revert',
Step #1: -        'style',
Step #1: -        'test',
Step #1: -      ]
Step #1: -    ],
Step #1: +                     // Language-specific scopes
Step #1: +                     'cxx_common',
Step #1: +                     'cxx_extractor',
Step #1: +                     'cxx_indexer',
Step #1: +                     'go_common',
Step #1: +                     'go_extractor',
Step #1: +                     'go_indexer',
Step #1: +                     'java_common',
Step #1: +                     'java_extractor',
Step #1: +                     'java_indexer',
Step #1: +                     'jvm_common',
Step #1: +                     'jvm_extractor',
Step #1: +                     'jvm_indexer',
Step #1: +                     'rust_common',
Step #1: +                     'rust_extractor',
Step #1: +                     'rust_indexer',
Step #1: +                     'typescript_common',
Step #1: +                     'typescript_extractor',
Step #1: +                     'typescript_indexer',
Step #1: +                   ]
Step #1: +                 ],
Step #1: +    'type-enum' :
Step #1: +                [
Step #1: +                  2, 'always',
Step #1: +                  [
Step #1: +                    'build',
Step #1: +                    'chore',
Step #1: +                    'ci',
Step #1: +                    'deprecation',
Step #1: +                    'docs',
Step #1: +                    'feat',
Step #1: +                    'fix',
Step #1: +                    'perf',
Step #1: +                    'refactor',
Step #1: +                    'release',
Step #1: +                    'revert',
Step #1: +                    'style',
Step #1: +                    'test',
Step #1: +                  ]
Step #1: +                ],
Step #1:    },
Step #1:  }
Finished Step #1

https://github.com/kythe/kythe/pull/5956 should make the format diff smaller

/gcbrun

The .commintlint.js file is still unhappy, but I'll merge and fix it myself if the Presubmit passes.

Thanks!


⚠ ClamAV has degraded performance

In 5881b7d, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 627 ms

Resolved: ClamAV performance has improved in 1e94187.


[Feature]: ✨ Feature Request: Integrate Logits Processors from logits-processor-zoo into vLLM

🚀 The feature, motivation and pitch
Feature Request: Integrate Logits Processors from logits-processor-zoo into vLLM
Description
I am writing to request the integration of several advanced logits processors from the logits-processor-zoo into the vLLM framework. These processors provide enhanced control over the text generation process, enabling more sophisticated and context-aware outputs.
Proposed Logits Processors for Integration

GenLengthLogitsProcessor

Purpose: Adjusts the likelihood of the end-of-sequence (EOS) token based on the generated sequence length, encouraging or discouraging shorter or longer responses.
Use Cases: Controlling response length in chatbots, ensuring concise or detailed answers as needed.

MultipleChoiceLogitsProcessor

Purpose: Guides the model to select from predefined multiple-choice options by boosting the logits of the specified choices.
Use Cases: Implementing multiple-choice questions, surveys, or structured decision-making processes within generated text.

CiteFromPromptLogitsProcessor

Purpose: Boosts or diminishes the likelihood of tokens present in the prompt (and optionally the EOS token) to encourage the generation of similar tokens or to avoid repetition.
Use Cases: Enhancing relevance to the input prompt, avoiding redundancy, and maintaining context consistency.

ForceLastPhraseLogitsProcessor

Purpose: Forces the model to generate a specified phrase before finalizing its response, useful for adding references, disclaimers, or thank-you notes.
Use Cases: Ensuring consistent closing statements, adding required legal disclaimers, or enhancing user interaction with personalized messages.

Benefits of Integration

Enhanced Control: Provides developers with finer control over the text generation process, enabling tailored outputs for specific applications.
Improved User Experience: Facilitates the creation of more coherent, relevant, and contextually appropriate responses in various use cases.
Flexibility and Customization: Allows for the implementation of complex generation strategies without extensive modifications to the core model.

Implementation Suggestions

Modular Integration: Incorporate the logits processors as optional modules or plugins within vLLM, allowing users to enable or disable them based on their requirements.
Configuration Parameters: Provide configurable parameters for each logits processor (e.g., boost factors, choice lists, target phrases) to allow customization.
Documentation and Examples: Update the vLLM documentation to include usage examples and guidelines for integrating and configuring the new logits processors.

Example Use Case
from transformers import PreTrainedTokenizer
from vllm import VLLMModel
from logits_processor_zoo import GenLengthLogitsProcessor, MultipleChoiceLogitsProcessor

# Initialize tokenizer and model
tokenizer = PreTrainedTokenizer.from_pretrained('gpt-2')
model = VLLMModel.from_pretrained('gpt-2')

# Initialize logits processors
gen_length_processor = GenLengthLogitsProcessor(tokenizer=tokenizer, boost_factor=0.5, p=2)
multiple_choice_processor = MultipleChoiceLogitsProcessor(tokenizer=tokenizer, choices=["A", "B", "C", "D"], delimiter=".", boost_first_words=1.0)

# Generate text with logits processors
output = model.generate(
    prompt="What is the capital of France?\nA. Berlin\nB. Madrid\nC. Paris\nD. Rome",
    logits_processors=[gen_length_processor, multiple_choice_processor],
    max_length=50
)

print(tokenizer.decode(output, skip_special_tokens=True))

### Alternatives

_No response_

### Additional context

Additional Information
Repository Links:

[logits-processor-zoo](https://github.com/NVIDIA/logits-processor-zoo)
[vLLM Integration Directory](https://github.com/NVIDIA/logits-processor-zoo/tree/main/logits_processor_zoo/vllm)
Related Discussions:

### Before submitting a new issue...

- [X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the [documentation page](https://docs.vllm.ai/en/latest/), which can answer lots of frequently asked questions.

With https://github.com/vllm-project/vllm/pull/11150, you should be able to import those logits processors as needed.

With #11150, you should be able to import those logits processors as needed.

Thanks @DarkLight1337


Overriding a rule name (buck.type) to match its public, exported name?

Consider an API like the following for exposing rules to users:
__private_name = rule(...)

public_api = struct(
    rule01 = __private_name
)

The goal of an API like this is to just be easier to read and write; you don't need to know the public symbols coming out of a module and when applied consistently makes it a little easier to find things. It's nothing groundbreaking. Just me exploring the API design space.
So now when I write BUILD files I use public_api.rule01 to declare targets. Great.
But this falls down when querying target nodes. The buck.type of a rule is given by the name given to the global top-level rule, not based on what's exported from a module (which would be hard to understand/make sense of, in any case.) In other words, the following query fails:
buck cquery 'kind("public_api.rule01", ...)'

This works:
buck cquery 'kind("__private_name", ...)'

Which exposes the internal name from the module. This isn't necessarily specific to struct()-like APIs; a simple case like public_name = __private_name suffers from the same issue too, I think. The internal name is leaked through to the public user.
You can verify this with a cquery; in the following example the exported name of the rule for users is rust.binary, not __rust_binary:
austin@GANON:~/src/buck2-nix.sl$ buck cquery src/hello: --output-all-attributes
Build ID: ab0ce60d-bea1-458b-b886-5c02c610306d
Jobs completed: 1. Time elapsed: 0.0s.
{
  "root//src/hello:main (prelude//platform:default-632fe5438d4aecc1)": {
    "buck.type": "__rust_binary",
    "buck.deps": [
      "prelude//toolchains/rust:rust-stable (prelude//platform:default-632fe5438d4aecc1)"
    ],
    "buck.package": "root//src/hello:TARGETS",
    "buck.oncall": null,
    "buck.target_configuration": "prelude//platform:default-632fe5438d4aecc1",
    "buck.execution_platform": "prelude//platform:default",
    "name": "main",
    "default_target_platform": null,
    "target_compatible_with": [],
    "compatible_with": [],
    "exec_compatible_with": [],
    "visibility": [],
    "tests": [],
    "_toolchain": "prelude//toolchains/rust:rust-stable (prelude//platform:default-632fe5438d4aecc1)",
    "file": "root//src/hello/main.rs",
    "out": "hello"
  }
}

So the question is: would it be possible to allow a rule to specify its buck.type name in some manner so that queries and rule uses can be consistent? Perhaps just another parameter to rule() that must be a constant string? If that could work?
It's worth noting this is mostly a convenience so that a rule user isn't confused by the leaked name. I can keep the nice struct()-like API and have the __private_names follow a similar naming logic so that "translating" between the two isn't hard. Not that big a deal.
I can imagine this might be too deeply woven into the implementation to easily fix.

I think this seems like a fine improvement. Right now buck.type comes from some internal data that probably can't be changed (as it's used to lookup the rule impl function during analysis), but I don't see any reason why we couldn't just store a separate user-configurable (with current default) field on rules. We could even call it "kind" and then buck.kind would use it (and the kind() query function could match against it) and maybe we could then get buck.type to be back to the fully-qualified symbol (it used to be this, but to match buck1 behavior we switched it to just the local name of the symbol).


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/75684

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/75686

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.


Add preferences for UI system fonts and colours

Add a preference page for customisation of the UI fonts and colours. This includes things such as Models Tree fonts. Note - there is already a preference for the default font to use for diagram components.

It would also be nice to be able to select multiple objects (shift-click) and change the Appearance fonts/colours for all. It currently only does it for the first selected object. Of course, the format painter can be used to paste formats.

You can change multiple objects fonts and colours from the main menu under "Edit".


Failures starting 2024-05-20

My flow has started to fail with no changes from me. It is complaining about a duplicate name (I build 2 container images from 2 branches)
SBOM scan completed in: 8.888s
------------------------- Uploading workflow artifacts -------------------------
/tmp/sbom-action-GE46vC/***-nginx-certbot.spdx.json
Error: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
Post job cleanup.

I have attempted to add an id: ${{ env.BRANCH_NAME }} to make unique names but the above still occurs.
https://github.com/PipeItToDevNull/nginx-certbot/actions

I also have a potentially similar problem on a preview repo:
Run<EMAIL_ADDRESS>------------------------------ Running SBOM Action -----------------------------
/usr/bin/sh /home/runner/work/_temp/86c14a62-acb2-4ebd-9824-486a58c461dc -d -b /home/runner/work/_temp/86c14a62-acb2-4ebd-9824-486a58c461dc_syft v1.4.1
[debug] checking github for release tag='v1.4.1'
[debug] http_download(url=https://github.com/anchore/syft/releases/v1.4.1)
[info] fetching release script for tag='v1.4.1'
[debug] http_download(url=https://raw.githubusercontent.com/anchore/syft/v1.4.1/install.sh)
[debug] checking github for release tag='v1.4.1'
[debug] http_download(url=https://github.com/anchore/syft/releases/v1.4.1)
[info] using release tag='v1.4.1' version='1.4.1' os='linux' arch='amd64'
[debug] downloading files into /tmp/tmp.fgZr8JGzEF
[debug] http_download(url=https://github.com/anchore/syft/releases/download/v1.4.1/syft_1.4.1_checksums.txt)
[debug] http_download(url=https://github.com/anchore/syft/releases/download/v1.4.1/syft_1.4.1_linux_amd64.tar.gz)
[info] installed /home/runner/work/_temp/86c14a62-acb2-4ebd-9824-486a58c[46](https://github.com/cosimmetry/sketch/actions/runs/9181218908/job/25247435631#step:6:47)1dc_syft/syft
/opt/hostedtoolcache/syft/1.4.1/x64/syft scan ghcr.io/cosimmetry/sketch -o spdx-json
Executing Syft...
SBOM scan completed in: 217.16s
------------------------- Uploading workflow artifacts -------------------------
/tmp/sbom-action-gzIbTJ/cosimmetry-sketch.spdx.json
Found 1 artifact(s)
------------------- Attaching SBOMs to release: 'v0.4.6.-rc2' ------------------
Error: Resource not accessible by integration

Since v0.16 the action is making use of @actions/artifact@v2 as requested in #434 https://github.com/actions/toolkit/tree/main/packages/artifact#v2---whats-new
One of the (breaking) changes in v2 is name uniqueness. You might want to use the artifact-name option to ensure name uniqueness if you're creating multiple SBOM's in a single workflow.

I have attempted to add an id: ${{ env.BRANCH_NAME }} to make unique names but the above still occurs.

It shows a warning that it doesn't recognize that attribute, according to the documentation you probably want artifact-name: ${{ env.BRANCH_NAME }} instead (https://github.com/anchore/sbom-action?tab=readme-ov-file#naming-the-sbom-output)

@tlbraams Thanks for that information - I now beleive the issue I'm seeing is different enough, so I'll open another issues for it.

There is a known and I think correct change in behavior that previous releases would silently overwrite workflow assets with the same name. So, for example, if you run within a matrix job and you'd just randomly get one of the artifacts: whichever finished last. This was never the intended behavior, just an oversight.
Looking at the repo, it looks like you do indeed have a matrix job. The SBOM artifact name, at least for now, needs to be unique for each run, in other words make it based on the matrix somehow. I had to update the tests for this, see: here.
That said, I'm not sure if it's possible offhand, but we might be able to detect when run as part of a matrix build and include some uniqueness as part of the naming so you won't have to do this in the future.

Awesome, using the matrix strategy resolved this. Thanks for the investigation and guidance.

Looks like this is covered off by the linked docs update. So I'm gonna close this now. 👍


Update past embassy-sync split

I sure hope this is the last refactoring for a while...

Awesome, thanks :rocket:


Run number not explained

Hello, seems that the page is just copy of the original text from https://docs.microsoft.com/en-us/azure/devops/pipelines/build/options?view=azure-devops page, but the Run ID is not explained at all. It is not used in the exmaple format, it is not exmplained in the token table, it is not part of the yaml example.
How can I use the Run ID at all?
Please, fix this copy/pasted text to really explain what should be explained on this page.

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

ID: a57f8545-bb15-3a71-1876-3a9ec1a59b93
Version Independent ID: 28c87c8d-c28d-7493-0c7c-8c38b04fbcd7
Content: Run number - Azure Pipelines
Content Source: docs/pipelines/process/run-number.md
Product: devops
Technology: devops-cicd
GitHub Login: @andyjlewis
Microsoft Alias: alewis

trying shows that $(Build.BuildId) is filled in (with number like 194218)  while $(Release.ReleaseId) stays empty. That causes 404 in calls like Release GET,  but Build Get api call with BuildID number works fine. That makes me think that Run number/ID is a BuildID.

The explanation here (for the mysterious 'Run ID') may simply be that it's a typo.
Under Example the bullet Run ID: 752 should likely be Build ID: 752, as the value 752 is referred to lower under Tokens as the value for $(BuildID).

In Microsoft Team Foundation Server (TFS) 2018 and previous versions, runs are called builds.  I'll update the documentation line @JoeBrockhaus identified to say Build ID.


More mypy stuff...

Continuation of fixing Issue #85
After this PR, all scaaml/ is done except scaaml/intro

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

122 of 127 (96.06%)  changed or added relevant lines in 9 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 81.433%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

scaaml/capture/aes/acqktp.py
6
7
85.71%

scaaml/io/dataset.py
77
81
95.06%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
2364

Relevant Lines:
2903

💛  - Coveralls


issue about python pdb when launch a python code with deepspeed

My code demo.py is relative simple
abc = 1
deg = 2
import pdb; pdb.set_trace()

My shell command is deepspeed demo.py
In debug mode, certain part of whatever I type will be ignored. For example, when I type abc, it might receive ab.
Here is my environment information
Collecting environment information...
PyTorch version: 1.11.0+cu102
Is debug build: False
CUDA used to build PyTorch: 10.2
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.4 LTS (x86_64)
GCC version: (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Clang version: Could not collect
CMake version: version 3.16.3
Libc version: glibc-2.31

Python version: 3.8.13 (default, Mar 28 2022, 11:38:47)  [GCC 7.5.0] (64-bit runtime)
Python platform: Linux-5.4.0-104-generic-x86_64-with-glibc2.17
Is CUDA available: True
CUDA runtime version: 10.1.243
GPU models and configuration:
GPU 0: Tesla K80
GPU 1: Tesla K80
GPU 2: Tesla K80
GPU 3: Tesla K80
GPU 4: Tesla K80
GPU 5: Tesla K80
GPU 6: Tesla K80
GPU 7: Tesla K80

Nvidia driver version: 470.129.06
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.22.4
[pip3] torch==1.11.0
[pip3] torchvision==0.12.0
[conda] numpy                     1.22.4                   pypi_0    pypi
[conda] torch                     1.11.0                   pypi_0    pypi
[conda] torchvision               0.12.0                   pypi_0    pypi

Here is my deepspeed-related information
--------------------------------------------------
DeepSpeed C++/CUDA extension op report
--------------------------------------------------
NOTE: Ops not installed will be just-in-time (JIT) compiled at
      runtime if needed. Op compatibility means that your system
      meet the required dependencies to JIT install the op.
--------------------------------------------------
JIT compiled ops requires ninja
ninja .................. [OKAY]
--------------------------------------------------
op name ................ installed .. compatible
--------------------------------------------------
cpu_adam ............... [NO] ....... [OKAY]
cpu_adagrad ............ [NO] ....... [OKAY]
fused_adam ............. [NO] ....... [OKAY]
fused_lamb ............. [NO] ....... [OKAY]
 [WARNING]  please install triton==1.0.0 if you want to use sparse attention
sparse_attn ............ [NO] ....... [NO]
transformer ............ [NO] ....... [OKAY]
stochastic_transformer . [NO] ....... [OKAY]
 [WARNING]  async_io requires the dev libaio .so object and headers but these were not found.
 [WARNING]  async_io: please install the libaio-dev package with apt
 [WARNING]  If libaio is already installed (perhaps from source), try setting the CFLAGS and LDFLAGS environment variables to where it can be found.
async_io ............... [NO] ....... [NO]
utils .................. [NO] ....... [OKAY]
quantizer .............. [NO] ....... [OKAY]
transformer_inference .. [NO] ....... [OKAY]
--------------------------------------------------
DeepSpeed general environment info:
torch install path ............... ['/home/wgao/anaconda3/envs/deepspeed/lib/python3.8/site-packages/torch']
torch version .................... 1.11.0+cu102
torch cuda version ............... 10.2
torch hip version ................ None
nvcc version ..................... 10.1
deepspeed install path ........... ['/home/wgao/workspace/DeepSpeed/deepspeed']
deepspeed info ................... 0.6.6+36ad3119, 36ad3119, master
deepspeed wheel compiled w. ...... torch 1.11, cuda 10.2

Thanks

@gaow0007 This issue is related to running with multiple sub processes. When launching with deepspeed you can specify the number of ranks created via --num_gpus - if you don't specify this option it will default to the number of GPUs detected (in your case 8).
Try running your example with deepspeed --num_gpus 1 demo.py and you should see expected behavior. If you truly need to use pdb with multiple ranks, you can try wrapping the pdb calls in if int(os.getenv('LOCAL_RANK', '0')): statements or use forkedpdb as suggested here.

Noted with thanks.


python310Packages.mcstatus: 9.3.0 -> 10.0.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.mcstatus is: "Python library for checking the status of Minecraft servers"
meta.homepage for python310Packages.mcstatus is: "https://github.com/py-mine/mcstatus"
meta.changelog for python310Packages.mcstatus is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 9.4.2 with grep in /nix/store/wqfvgq5qyx96anmk85f10d1580mlh546-python3.10-mcstatus-9.4.2
found 9.4.2 in filename of file in /nix/store/wqfvgq5qyx96anmk85f10d1580mlh546-python3.10-mcstatus-9.4.2

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

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.minecraft_server
mcstatus
python310Packages.mcstatus
python39Packages.mcstatus

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wqfvgq5qyx96anmk85f10d1580mlh546-python3.10-mcstatus-9.4.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.mcstatus https://github.com/r-ryantm/nixpkgs/archive/b7e3e4b88927fab70c726f7460677560a5a6e8c1.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wqfvgq5qyx96anmk85f10d1580mlh546-python3.10-mcstatus-9.4.2
ls -la /nix/store/wqfvgq5qyx96anmk85f10d1580mlh546-python3.10-mcstatus-9.4.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

home-assistant-component-tests.minecraft_server

2 packages built:

mcstatus (python310Packages.mcstatus)
python39Packages.mcstatus

Maintainer pings
cc @fabaff for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.mcstatus is: "Python library for checking the status of Minecraft servers"
meta.homepage for python310Packages.mcstatus is: "https://github.com/py-mine/mcstatus"
meta.changelog for python310Packages.mcstatus is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 10.0.0 with grep in /nix/store/qg0m3xg66zwwar8ryvmghzd9mvmil976-python3.10-mcstatus-10.0.0
found 10.0.0 in filename of file in /nix/store/qg0m3xg66zwwar8ryvmghzd9mvmil976-python3.10-mcstatus-10.0.0

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

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.minecraft_server
mcstatus
python310Packages.mcstatus
python39Packages.mcstatus

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qg0m3xg66zwwar8ryvmghzd9mvmil976-python3.10-mcstatus-10.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.mcstatus https://github.com/r-ryantm/nixpkgs/archive/636ee08ae85b54d2bb55718ef94f7fcf858bcfbb.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qg0m3xg66zwwar8ryvmghzd9mvmil976-python3.10-mcstatus-10.0.0
ls -la /nix/store/qg0m3xg66zwwar8ryvmghzd9mvmil976-python3.10-mcstatus-10.0.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

home-assistant-component-tests.minecraft_server

2 packages built:

mcstatus (python310Packages.mcstatus)
python39Packages.mcstatus

Maintainer pings
cc @fabaff for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.mcstatus is: "Python library for checking the status of Minecraft servers"
meta.homepage for python310Packages.mcstatus is: "https://github.com/py-mine/mcstatus"
meta.changelog for python310Packages.mcstatus is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 10.0.1 with grep in /nix/store/d62s05xgxc8dgv4z9p5wrjrinq2b8pf2-python3.10-mcstatus-10.0.1
found 10.0.1 in filename of file in /nix/store/d62s05xgxc8dgv4z9p5wrjrinq2b8pf2-python3.10-mcstatus-10.0.1

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

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.minecraft_server
mcstatus
python310Packages.mcstatus
python39Packages.mcstatus

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/d62s05xgxc8dgv4z9p5wrjrinq2b8pf2-python3.10-mcstatus-10.0.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.mcstatus https://github.com/r-ryantm/nixpkgs/archive/44b82bbfa02ffa55164e2c547c6baeac8832f0be.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/d62s05xgxc8dgv4z9p5wrjrinq2b8pf2-python3.10-mcstatus-10.0.1
ls -la /nix/store/d62s05xgxc8dgv4z9p5wrjrinq2b8pf2-python3.10-mcstatus-10.0.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

home-assistant-component-tests.minecraft_server

2 packages built:

mcstatus (python310Packages.mcstatus)
python39Packages.mcstatus

Maintainer pings
cc @fabaff for testing.


Add support for BSD-riscv64 target to 1.1.1

Reviewed-by: Tomas Mraz<EMAIL_ADDRESS>Reviewed-by: Ben Kaduk<EMAIL_ADDRESS>Reviewed-by: Paul Dale<EMAIL_ADDRESS>(Merged from https://github.com/openssl/openssl/pull/17306)
(cherry picked from commit c2d1ad0e048dd3bfa60e6aa0b5ee343cc6d97a15)
(cherry picked from commit c9ede1ee2058f067274929e813e257394d0ef6bb)

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

24 hours has passed since 'approval: done' was set, but this PR has failing CI tests.  Once the tests pass it will get moved to 'approval: ready to merge' automatically, alternatively please review and set the label manually.

Hmm, should we update the second "cherry picked from" line to match the sha1 that is actually on the 3.0 branch?

Hmm, should we update the second "cherry picked from" line to match the sha1 that is actually on the 3.0 branch?

Yes. Such a trivial change can just be done during merge.

24 hours has passed since 'approval: done' was set, but this PR has failing CI tests. Once the tests pass it will get moved to 'approval: ready to merge' automatically, alternatively please review and set the label manually.

I see all-green on the checks.  I'd like to have someone else confirm before I push (or someone else could just push themselves, too), even though this change should be totally orthogonal to the CI...

I'd like to have someone else confirm before I push

All looks in order to me. I don't know why the bot is complaining about CI failures. Adding the ready-to-merge label

Pushed to 1.1.1.  Thanks for the backport and the review; closing

Pushed to 1.1.1.  Thanks for the backport and the review; closing


Should be able to select comboBox with placeHolders

Expected behavior
Should be able to select comboBox with placeHolders

Actual behavior
Unable to find the element
Version
commit - 51de58ab2c042b63be0e5d19a79450de0cd03acd

@sguptatw Where are you trying this?
Could you give steps to reproduce the issue?

In the above case Select a card type is not a placeholder. Its an option which is selected and disabled.
So selecting the combobox by id should work.