Error attempting to Configure Chime_TTS

System Health details
System Information

version
core-2024.11.3

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.12.4

os_name
Linux

os_version
6.6.54-haos

arch
x86_64

timezone
America/New_York

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

HACS Data
ok

GitHub API Calls Remaining
4993

Installed Version
2.0.1

Stage
running

Available Repositories
1497

Downloaded Repositories
18

Home Assistant Cloud

logged_in
true

subscription_expiration
February 22, 2025 at 7:00 PM

relayer_connected
true

relayer_region
us-east-1

remote_enabled
true

remote_connected
true

alexa_enabled
true

google_enabled
true

cloud_ice_servers_enabled
true

remote_server
us-east-1-5.ui.nabu.casa

certificate_status
ready

instance_id
16998a41d9224c818c351f3349a01f9b

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 13.2

update_channel
stable

supervisor_version
supervisor-2024.11.4

agent_version
1.6.0

docker_version
27.2.0

disk_total
62.3 GB

disk_used
13.7 GB

healthy
true

supported
true

host_connectivity
true

supervisor_connectivity
true

ntp_synchronized
true

virtualization
kvm

board
ova

supervisor_api
ok

version_api
ok

installed_addons
Terminal & SSH (9.16.0), File editor (5.8.0), Studio Code Server (5.17.3), Z-Wave JS UI (3.18.0), Home Assistant Google Drive Backup (0.112.1), Samba share (12.3.2), Portainer (2.24.1), Mosquitto broker (6.4.1), Zigbee2MQTT (1.42.0-2), NGINX Home Assistant SSL proxy (3.11.1), Piper (1.5.2), ESPHome Device Compiler (2024.11.3), Ring-MQTT with Video Streaming (5.8.0)

Dashboards

dashboards
5

resources
6

views
7

mode
storage

Recorder

oldest_recorder_run
December 7, 2024 at 4:32 PM

current_recorder_run
December 15, 2024 at 6:36 PM

estimated_db_size
611.08 MiB

database_engine
sqlite

database_version
3.45.3

![2024-12-15_18-40-49](https://github.com/user-attachments/assets/4db0d7fb-9aeb-435b-bdd3-9269e240c8e2)
Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Describe the issue
After updating to version v1.2.0 I am attempting to Configure and getting 500 Internal Server Error (screenshot attached).
Reproduction steps

Go to Integrations
Click Chime-TTS
Click Configure
...

Debug logs
2024-12-15 18:47:27.768 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hass_agent which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-12-15 18:47:27.769 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration variable which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-12-15 18:47:27.770 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration watchman which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-12-15 18:47:27.771 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration homeseer which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-12-15 18:47:27.772 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration kia_uvo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-12-15 18:47:27.772 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-12-15 18:47:27.773 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration huesyncbox which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-12-15 18:47:27.774 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alarmo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-12-15 18:47:27.774 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ge_home which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-12-15 18:47:27.775 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration o365 which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-12-15 18:47:27.776 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration multiscrape which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-12-15 18:47:27.776 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration chime_tts which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-12-15 18:47:27.777 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration battery_notes which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-12-15 18:47:27.778 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-12-15 18:47:29.571 WARNING (MainThread) [homeassistant.components.lovelace] Lovelace is running in storage mode. Define resources via user interface
2024-12-15 18:47:33.079 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'o365' uses `async_config_entry_first_refresh`, which is only supported for coordinators with a config entry and will stop working in Home Assistant 2025.11 at custom_components/o365/helpers/setup.py, line 73: await email_coordinator.async_config_entry_first_refresh(), please create a bug report at https://github.com/RogerSelwyn/O365-HomeAssistant/issues
2024-12-15 18:47:33.275 WARNING (ImportExecutor_0) [slixmpp.stringprep] Using slower stringprep, consider compiling the faster cython/libidn one.
2024-12-15 18:47:33.547 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to load_default_certs with args (<ssl.SSLContext object at 0x7f71c8d0e650>, <Purpose.SERVER_AUTH: _ASN1Object(nid=129, shortname='serverAuth', longname='TLS Web Server Authentication', oid='<IP_ADDRESS>.<IP_ADDRESS>.1')>) inside the event loop by integration 'harmony' at homeassistant/components/harmony/data.py, line 118: connected = await self._client.connect() (offender: /usr/local/lib/python3.12/ssl.py, line 713: context.load_default_certs(purpose)), please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+harmony%22
For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#load_default_certs
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
    handle._run()
  File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 783, in async_setup_locked
    await self.async_setup(hass, integration=integration)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 546, in async_setup
    await self.__async_setup_with_context(hass, integration)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 635, in __async_setup_with_context
    result = await component.async_setup_entry(hass, self)
  File "/usr/src/homeassistant/homeassistant/components/harmony/__init__.py", line 28, in async_setup_entry
    await data.connect()
  File "/usr/src/homeassistant/homeassistant/components/harmony/data.py", line 118, in connect
    connected = await self._client.connect()

2024-12-15 18:47:34.346 WARNING (SyncWorker_32) [hyundai_kia_connect_api.HyundaiBlueLinkApiUSA] hyundai_kia_connect_api - Unable to get vehicle location: {'errorSubCode': 'IDM_PIN_607', 'systemName': 'IDM', 'functionName': 'validatePIN', 'errorSubMessage': 'Your pin has been locked permanently, please input security questions and answers to update the pin.', 'errorMessage': 'Your pin has been locked permanently, please contact the call center.', 'errorCode': 401, 'serviceName': 'CheckCustomerUserPin'}
2024-12-15 18:47:38.024 WARNING (MainThread) [homeassistant.components.vesync.fan] Humidifier - Unknown device type - Classic300S
2024-12-15 18:47:43.453 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esp32devkitv1 @ <IP_ADDRESS>: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='<IP_ADDRESS>', port=6053))]: [Errno 113] Connect call failed ('<IP_ADDRESS>', 6053) (SocketAPIError)
2024-12-15 18:47:44.246 ERROR (MainThread) [homeassistant.components.automation] Platform automation does not generate unique IDs. ID notification_alexa_command_remote already exists - ignoring automation.notification_alexa_command_remote
2024-12-15 18:47:44.247 ERROR (MainThread) [homeassistant.components.automation] Platform automation does not generate unique IDs. ID notification_power_ups_monitor_change already exists - ignoring automation.notification_power_ups_monitor_change
2024-12-15 18:47:44.254 ERROR (MainThread) [homeassistant.components.automation] Platform automation does not generate unique IDs. ID notification_add-on_monitoring already exists - ignoring automation.notification_add_on_monitoring
2024-12-15 18:47:44.992 WARNING (ImportExecutor_0) [homeassistant.components.media_player.const] MEDIA_TYPE_MUSIC was used from hass_agent, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaType.MUSIC instead, please report it to the author of the 'hass_agent' custom integration
2024-12-15 18:47:49.960 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hass_agent' calls media_source.async_resolve_media without passing an entity_id at custom_components/hass_agent/media_player.py, line 301: play_item = await media_source.async_resolve_media(self.hass, media_id), please create a bug report at https://github.com/hass-agent/HASS.Agent-Integration/issues
2024-12-15 18:47:54.152 ERROR (MainThread) [custom_components.multiscrape.sensor] MultiScrape TwinBridges # MultiScrape Twin Bridges Notification # Unable to scrape data: Could not find a tag for given selector
Consider using debug logging and log_response for further investigation.
2024-12-15 18:47:54.156 ERROR (MainThread) [custom_components.multiscrape.entity] MultiScrape TwinBridges # MultiScrape Twin Bridges Notification # full_text # Unable to extract data from HTML
2024-12-15 18:48:08.394 DEBUG (MainThread) [custom_components.chime_tts.helpers.helpers] ╔════════════════════════════════════════╗
2024-12-15 18:48:08.394 DEBUG (MainThread) [custom_components.chime_tts.helpers.helpers] ║ Chime TTS Version v1.2.0 Configuration ║
2024-12-15 18:48:08.394 DEBUG (MainThread) [custom_components.chime_tts.helpers.helpers] ╚════════════════════════════════════════╝
2024-12-15 18:48:08.395 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 477, in _handle_request
    resp = await request_handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 567, in _handle
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 210, in forwarded_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 86, in ban_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware
    response = await handler(request)
               ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle
    result = await handler(request, **request.match_info)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 81, in with_admin
    return await func(self, request, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 262, in post
    return await super().post(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 74, in wrapper
    return await method(view, request, data, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 77, in post
    return await self._post_impl(request, data)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 84, in _post_impl
    result = await self._flow_mgr.async_init(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 342, in async_init
    result = await self._async_handle_step(flow, flow.init_step, data)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 517, in _async_handle_step
    result: _FlowResultT = await getattr(flow, method)(user_input)
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/chime_tts/config_flow.py", line 102, in async_step_init
    QUEUE_TIMEOUT_KEY: self.get_data_key_value(QUEUE_TIMEOUT_KEY, user_input, QUEUE_TIMEOUT_DEFAULT),
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/chime_tts/config_flow.py", line 271, in get_data_key_value
    dicts = [dict(self.config_entry.options), dict(self.config_entry.data)]
                  ^^^^^^^^^^^^^^^^^
AttributeError: 'ChimeTTSOptionsFlowHandler' object has no attribute 'config_entry'

Diagnostics dump
No response

Thank you, I will add a fix in the next release

This is now working, thank you.  However, I'm not getting the fallback TTS working.  I will open a separate Issue


Set up a canary

Set up a canary to alert me if the site ever goes down or breaks.

I added a canary to my personal AWS account:
https://github.com/philipmw/my-synthetics-canaries/commit/ad7fbf2d0667b9fb795936aafd1f20cb71cf77e8


Refactoring codebase from using BitcoinSLogger as a mixin trait -- re…

…factoring BitcoinSLogger as abstract class

Coverage decreased (-0.05%) to 90.317% when pulling 89fbf35d78046b7ed21fd93fec05bb57cba023bb on Christewart:refactor_logger into 7bcc8e57463bd77398045c52d75e65bbc7a70a17 on bitcoin-s:master.


:memo: Fill in config.properties documentation

Problem Statement
Some properties in config.properties aren't documented.
Solution
Add documentation for OKTA_PROFILE and OKTA_BROWSER_AUTH.

@slancio do these docs make sense to you? I was inspired by your change to catch up on docs I forgot to add.

The docs make sense but I'm confused about OKTA_PROFILE.  I'm using an old version that I distributed to my engineers and the profile names are in the format aws_account/aws_role/okta_username(company_email)_source.  Does this "random profile name" change that was implemented change that behavior?

@slancio good point. Random isn’t really the word. It’s more accurate to say they’re generated.
OKTA_PROFILE is intended to support external tools like Terraform where you need a specifically named profile instead of a generated profile name.
It also allows this tool to be used with boto3 or other downstream AWS SDKs that can use named profiles. I’ve personally used it with Java, Python, PowerShell, and Haskell programs in this way.

We use terraform with this a lot and the advice that we give is to either set the AWS_PROFILE/AWS_DEFAULT_PROFILE envvars to the generated profile name (because that name does not change) or to pass terraform the --profile flag that it supports.
As long as the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY envvars are clear, the envvar suggestion should work in any language using the standard libraries for working with AWS.

Neat! I didn’t know that. I’ve been so focused on the Okta side of this, that I haven’t dug into Terraform much yet. I didn’t realize it had —profile switch support on the CLI!

Sorry, i mispoke about profile switch support (i thought it did) hence the edit.   envvar and in terraform config only.

This makes sense to me!


consider supporting nested objects?

for instance:
{
fname: 'Stewart',
lname: 'Robinson',
addr1: '124 H Street',
addr2: '#81',
city: 'Murray',
state: 'UT',
postalCode: '84107',
contact:  { type: 'im', client: 'skype', user: 'sfrobins' }
}
I can find no way to get meteor kitchen to accept the contact object as a member of the parent JSON object.

Yes you can, example collection definition:
{
  "name": "myCollection",
  "fields": [
    { "name": "fname", "title", "First name" },
    { "name": "lname", "title", "Last name" },
    { "name": "contact.type", "title", "Type" },
    { "name": "contact.client", "title", "Client" },
    { "name": "contact.user", "title", "Username" }
  ]
}

Let me know if it helps.

It works...  Thank you!  I tried that about a month ago and came to the conclusion that it did not work.  My bad...


Add rest interface for regrounding

Please let me know if this works and whether it needs to be moved to any particular older branch or release.

Thanks @kwalcock! I'll try it from the branch now.


[spi_device] Assertion error after tx underflow occurs

@eunchan
In this test, I do want to test TX underflow and this error happens. Can you check if it's expected?

"../src/lowrisc_prim_all_0.1/rtl/prim_pulse_sync.sv", 54: tb.dut.u_txf_underflow.SrcPulseCheck_M: started at<PHONE_NUMBER>6ps failed at<PHONE_NUMBER>6ps
Offending '(!src_active_flag)'
UVM_ERROR @<PHONE_NUMBER>6 ps: (prim_pulse_sync.sv:54) [ASSERT FAILED] SrcPulseCheck_M

Waves:

/mnt/disks/filestores/opentitan-shared/users/weicai/scratch/underflow/spi_device-sim-vcs/0.spi_device_fifo_underflow_overflow/latest/

cc: @jeoongp

@eunchan @jeoongp can you take a look at this when you have a chance?

Since overflow/underflow are special cases, I will disable these SVAs when I test them. Hence we could keep the SVAs.

closing via #15740


Can't edit cell - TypeError: "x" is read-only

When editing a cell it returns the following error:
Firefox - TypeError: "x" is read-only
Chrome - Cannot assign to read only property 'x' of object '#'
Where x is the dataField of the table.
I have reduced table to bare minimum with no luck. The tables 'data' field is connected to a state value which recieves information from a GraphQL through Apollo client. I even assigned the data to a seperate var but still throwing error.
When I create a dummy var array in the render it works fine.
ERROR:
Uncaught TypeError: Cannot assign to read only property 'quantity' of object '#'
at utils.js:42
at Array.reduce ()
at Object.set (utils.js:33)
at Store.edit (index.js:41)
at CellEditWrapper.handleCellUpdate (wrapper.js:105)
at EditingCell.beforeComplete (editing-cell.js:149)
at EditingCell.handleKeyDown (editing-cell.js:174)
at HTMLUnknownElement.callCallback (react-dom.development.js:100)
at Object.invokeGuardedCallbackDev (react-dom.development.js:138)
at Object.invokeGuardedCallback (react-dom.development.js:187)
at Object.invokeGuardedCallbackAndCatchFirstError (react-dom.development.js:201)
Code

I even assigned the data to a seperate var but still throwing error.

yes, correct, you probably need a deeply copy might be work.
And also make sure the data props is JavaScript Array and every row object is plan object.

Thanks Allen. If I declare the array as [] first then assign it to the apollo data it works fine. Thanks for your prompt response and your work on this great component.

Thanks Allen. I copied the receiving Apollo data using JSON.parse(JSON.stringify(this.props.fetchData)) and assigned it to the table and it's working now. Thanks for your prompt response and keep up the good work.

Thanks Allen. I copied the receiving Apollo data using JSON.parse(JSON.stringify(this.props.fetchData)) and assigned it to the table and it's working now. Thanks for your prompt response and keep up the good work.

i am fetching the data from api then i am using redux slice to store the data and the pasing the data to the table through props i am passig the data to table


Cannot launch lxc VM for Ubuntu Xenial and Trusty

Required information

Distribution: Ubuntu
Distribution version: 20.04
lxc info

config: {}
api_extensions:
- storage_zfs_remove_snapshots
- container_host_shutdown_timeout
- container_stop_priority
- container_syscall_filtering
- auth_pki
- container_last_used_at
- etag
- patch
- usb_devices
- https_allowed_credentials
- image_compression_algorithm
- directory_manipulation
- container_cpu_time
- storage_zfs_use_refquota
- storage_lvm_mount_options
- network
- profile_usedby
- container_push
- container_exec_recording
- certificate_update
- container_exec_signal_handling
- gpu_devices
- container_image_properties
- migration_progress
- id_map
- network_firewall_filtering
- network_routes
- storage
- file_delete
- file_append
- network_dhcp_expiry
- storage_lvm_vg_rename
- storage_lvm_thinpool_rename
- network_vlan
- image_create_aliases
- container_stateless_copy
- container_only_migration
- storage_zfs_clone_copy
- unix_device_rename
- storage_lvm_use_thinpool
- storage_rsync_bwlimit
- network_vxlan_interface
- storage_btrfs_mount_options
- entity_description
- image_force_refresh
- storage_lvm_lv_resizing
- id_map_base
- file_symlinks
- container_push_target
- network_vlan_physical
- storage_images_delete
- container_edit_metadata
- container_snapshot_stateful_migration
- storage_driver_ceph
- storage_ceph_user_name
- resource_limits
- storage_volatile_initial_source
- storage_ceph_force_osd_reuse
- storage_block_filesystem_btrfs
- resources
- kernel_limits
- storage_api_volume_rename
- macaroon_authentication
- network_sriov
- console
- restrict_devlxd
- migration_pre_copy
- infiniband
- maas_network
- devlxd_events
- proxy
- network_dhcp_gateway
- file_get_symlink
- network_leases
- unix_device_hotplug
- storage_api_local_volume_handling
- operation_description
- clustering
- event_lifecycle
- storage_api_remote_volume_handling
- nvidia_runtime
- container_mount_propagation
- container_backup
- devlxd_images
- container_local_cross_pool_handling
- proxy_unix
- proxy_udp
- clustering_join
- proxy_tcp_udp_multi_port_handling
- network_state
- proxy_unix_dac_properties
- container_protection_delete
- unix_priv_drop
- pprof_http
- proxy_haproxy_protocol
- network_hwaddr
- proxy_nat
- network_nat_order
- container_full
- candid_authentication
- backup_compression
- candid_config
- nvidia_runtime_config
- storage_api_volume_snapshots
- storage_unmapped
- projects
- candid_config_key
- network_vxlan_ttl
- container_incremental_copy
- usb_optional_vendorid
- snapshot_scheduling
- container_copy_project
- clustering_server_address
- clustering_image_replication
- container_protection_shift
- snapshot_expiry
- container_backup_override_pool
- snapshot_expiry_creation
- network_leases_location
- resources_cpu_socket
- resources_gpu
- resources_numa
- kernel_features
- id_map_current
- event_location
- storage_api_remote_volume_snapshots
- network_nat_address
- container_nic_routes
- rbac
- cluster_internal_copy
- seccomp_notify
- lxc_features
- container_nic_ipvlan
- network_vlan_sriov
- storage_cephfs
- container_nic_ipfilter
- resources_v2
- container_exec_user_group_cwd
- container_syscall_intercept
- container_disk_shift
- storage_shifted
- resources_infiniband
- daemon_storage
- instances
- image_types
- resources_disk_sata
- clustering_roles
- images_expiry
- resources_network_firmware
- backup_compression_algorithm
- ceph_data_pool_name
- container_syscall_intercept_mount
- compression_squashfs
- container_raw_mount
- container_nic_routed
- container_syscall_intercept_mount_fuse
- container_disk_ceph
- virtual-machines
- image_profiles
- clustering_architecture
- resources_disk_id
- storage_lvm_stripes
- vm_boot_priority
- unix_hotplug_devices
- api_filtering
- instance_nic_network
- clustering_sizing
- firewall_driver
- projects_limits
- container_syscall_intercept_hugetlbfs
- limits_hugepages
- container_nic_routed_gateway
- projects_restrictions
- custom_volume_snapshot_expiry
- volume_snapshot_scheduling
- trust_ca_certificates
- snapshot_disk_usage
- clustering_edit_roles
- container_nic_routed_host_address
- container_nic_ipvlan_gateway
- resources_usb_pci
- resources_cpu_threads_numa
- resources_cpu_core_die
- api_os
- container_nic_routed_host_table
- container_nic_ipvlan_host_table
- container_nic_ipvlan_mode
- resources_system
- images_push_relay
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
- tls
environment:
  addresses: []
  architectures:
  - x86_64
  - i686
  certificate: |
    -----BEGIN CERTIFICATE-----
    MIIB9zCCAX2gAwIBAgIQU3bmUn7ogbX2pOjlALWf7TAKBggqhkjOPQQDAzA0MRww
    GgYDVQQKExNsaW51eGNvbnRhaW5lcnMub3JnMRQwEgYDVQQDDAtyb290QHVwdG93
    bjAeFw0xOTEwMjEyMDMzMzRaFw0yOTEwMTgyMDMzMzRaMDQxHDAaBgNVBAoTE2xp
    bnV4Y29udGFpbmVycy5vcmcxFDASBgNVBAMMC3Jvb3RAdXB0b3duMHYwEAYHKoZI
    zj0CAQYFK4EEACIDYgAEzZhp2YHDbTeZIhdxUaKj6JZ5Cpqi2K4qzAdZ243TIo6r
    Ojzh9Q+7Ux9ZUBAXDuzDQEjpN2rSMzFLXxjy6PUUqn+ukSzNGERQYKKv3Rx2qKFs
    3zgt3WGTP/CPvf0fHTY6o1QwUjAOBgNVHQ8BAf8EBAMCBaAwEwYDVR0lBAwwCgYI
    KwYBBQUHAwEwDAYDVR0TAQH/BAIwADAdBgNVHREEFjAUggZ1cHRvd26HBMCoAguH
    BAqpKAEwCgYIKoZIzj0EAwMDaAAwZQIwDBSN4Xu1B8zP0oU3qDnvdltOmf95EBLf
    s9CJwiovmwxAuyaFwIYJyGC/pWYH35uHAjEAwlIPBWQzs2qjP0L3Z+JI54al2N1N
    iACdzozxVE9eHgGFNOTMppNbBpeKo4tudOab
    -----END CERTIFICATE-----
  certificate_fingerprint: 6aaceb8d2e522b490ee1d95bf2a31be73f1ed8bcf503709e55f630f1b7be0c58
  driver: lxc
  driver_version: 4.0.2
  firewall: xtables
  kernel: Linux
  kernel_architecture: x86_64
  kernel_features:
    netnsid_getifaddrs: "true"
    seccomp_listener: "true"
    seccomp_listener_continue: "true"
    shiftfs: "false"
    uevent_injection: "true"
    unpriv_fscaps: "true"
  kernel_version: 5.4.0-29-generic
  lxc_features:
    cgroup2: "true"
    mount_injection_file: "true"
    network_gateway_device_route: "true"
    network_ipvlan: "true"
    network_l2proxy: "true"
    network_phys_macvlan_mtu: "true"
    network_veth_router: "true"
    seccomp_notify: "true"
  os_name: Ubuntu
  os_version: "20.04"
  project: default
  server: lxd
  server_clustered: false
  server_name: uptown
  server_pid: 2687
  server_version: "4.1"
  storage: zfs
  storage_version: 0.8.3-1ubuntu12

Issue description
Appropriate lxd vm Images are not found for Ubuntu Xenial or Trusty, but are found on Bionic and later.   This may just come down to an image streams issue, but I wanted to file an issue here for tracking this symptom in case others hit it.
Steps to reproduce
# ubuntu bionic VMs are able to launch
lxc launch ubuntu-daily:bionic dev-vm-b --vm
Creating dev-vm-b
Starting dev-vm-b

# Ubuntu Xenial and Trusty VM images are not present
lxc launch ubuntu-daily:xenial dev-vm-x --vm
Creating dev-vm-x
Error: Failed instance creation: The requested image couldn't be found
csmith@uptown:~$ lxc launch ubuntu-daily:trusty dev-vm-t --vm
Creating dev-vm-t
Error: Failed instance creation: The requested image couldn't be found

output of client with --debug

csmith@uptown:~$ lxc launch --debug ubuntu-daily:trusty dev-vm-b --vm
DBUG[05-20|09:56:53] Connecting to a local LXD over a Unix socket
DBUG[05-20|09:56:53] Sending request to LXD                   method=GET url=http://unix.socket/1.0 etag=
DBUG[05-20|09:56:53] Got response struct from LXD
DBUG[05-20|09:56:53]
	{
		"config": {},
		"api_extensions": [
			"storage_zfs_remove_snapshots",
			"container_host_shutdown_timeout",
			"container_stop_priority",
			"container_syscall_filtering",
			"auth_pki",
			"container_last_used_at",
			"etag",
			"patch",
			"usb_devices",
			"https_allowed_credentials",
			"image_compression_algorithm",
			"directory_manipulation",
			"container_cpu_time",
			"storage_zfs_use_refquota",
			"storage_lvm_mount_options",
			"network",
			"profile_usedby",
			"container_push",
			"container_exec_recording",
			"certificate_update",
			"container_exec_signal_handling",
			"gpu_devices",
			"container_image_properties",
			"migration_progress",
			"id_map",
			"network_firewall_filtering",
			"network_routes",
			"storage",
			"file_delete",
			"file_append",
			"network_dhcp_expiry",
			"storage_lvm_vg_rename",
			"storage_lvm_thinpool_rename",
			"network_vlan",
			"image_create_aliases",
			"container_stateless_copy",
			"container_only_migration",
			"storage_zfs_clone_copy",
			"unix_device_rename",
			"storage_lvm_use_thinpool",
			"storage_rsync_bwlimit",
			"network_vxlan_interface",
			"storage_btrfs_mount_options",
			"entity_description",
			"image_force_refresh",
			"storage_lvm_lv_resizing",
			"id_map_base",
			"file_symlinks",
			"container_push_target",
			"network_vlan_physical",
			"storage_images_delete",
			"container_edit_metadata",
			"container_snapshot_stateful_migration",
			"storage_driver_ceph",
			"storage_ceph_user_name",
			"resource_limits",
			"storage_volatile_initial_source",
			"storage_ceph_force_osd_reuse",
			"storage_block_filesystem_btrfs",
			"resources",
			"kernel_limits",
			"storage_api_volume_rename",
			"macaroon_authentication",
			"network_sriov",
			"console",
			"restrict_devlxd",
			"migration_pre_copy",
			"infiniband",
			"maas_network",
			"devlxd_events",
			"proxy",
			"network_dhcp_gateway",
			"file_get_symlink",
			"network_leases",
			"unix_device_hotplug",
			"storage_api_local_volume_handling",
			"operation_description",
			"clustering",
			"event_lifecycle",
			"storage_api_remote_volume_handling",
			"nvidia_runtime",
			"container_mount_propagation",
			"container_backup",
			"devlxd_images",
			"container_local_cross_pool_handling",
			"proxy_unix",
			"proxy_udp",
			"clustering_join",
			"proxy_tcp_udp_multi_port_handling",
			"network_state",
			"proxy_unix_dac_properties",
			"container_protection_delete",
			"unix_priv_drop",
			"pprof_http",
			"proxy_haproxy_protocol",
			"network_hwaddr",
			"proxy_nat",
			"network_nat_order",
			"container_full",
			"candid_authentication",
			"backup_compression",
			"candid_config",
			"nvidia_runtime_config",
			"storage_api_volume_snapshots",
			"storage_unmapped",
			"projects",
			"candid_config_key",
			"network_vxlan_ttl",
			"container_incremental_copy",
			"usb_optional_vendorid",
			"snapshot_scheduling",
			"container_copy_project",
			"clustering_server_address",
			"clustering_image_replication",
			"container_protection_shift",
			"snapshot_expiry",
			"container_backup_override_pool",
			"snapshot_expiry_creation",
			"network_leases_location",
			"resources_cpu_socket",
			"resources_gpu",
			"resources_numa",
			"kernel_features",
			"id_map_current",
			"event_location",
			"storage_api_remote_volume_snapshots",
			"network_nat_address",
			"container_nic_routes",
			"rbac",
			"cluster_internal_copy",
			"seccomp_notify",
			"lxc_features",
			"container_nic_ipvlan",
			"network_vlan_sriov",
			"storage_cephfs",
			"container_nic_ipfilter",
			"resources_v2",
			"container_exec_user_group_cwd",
			"container_syscall_intercept",
			"container_disk_shift",
			"storage_shifted",
			"resources_infiniband",
			"daemon_storage",
			"instances",
			"image_types",
			"resources_disk_sata",
			"clustering_roles",
			"images_expiry",
			"resources_network_firmware",
			"backup_compression_algorithm",
			"ceph_data_pool_name",
			"container_syscall_intercept_mount",
			"compression_squashfs",
			"container_raw_mount",
			"container_nic_routed",
			"container_syscall_intercept_mount_fuse",
			"container_disk_ceph",
			"virtual-machines",
			"image_profiles",
			"clustering_architecture",
			"resources_disk_id",
			"storage_lvm_stripes",
			"vm_boot_priority",
			"unix_hotplug_devices",
			"api_filtering",
			"instance_nic_network",
			"clustering_sizing",
			"firewall_driver",
			"projects_limits",
			"container_syscall_intercept_hugetlbfs",
			"limits_hugepages",
			"container_nic_routed_gateway",
			"projects_restrictions",
			"custom_volume_snapshot_expiry",
			"volume_snapshot_scheduling",
			"trust_ca_certificates",
			"snapshot_disk_usage",
			"clustering_edit_roles",
			"container_nic_routed_host_address",
			"container_nic_ipvlan_gateway",
			"resources_usb_pci",
			"resources_cpu_threads_numa",
			"resources_cpu_core_die",
			"api_os",
			"container_nic_routed_host_table",
			"container_nic_ipvlan_host_table",
			"container_nic_ipvlan_mode",
			"resources_system",
			"images_push_relay"
		],
		"api_status": "stable",
		"api_version": "1.0",
		"auth": "trusted",
		"public": false,
		"auth_methods": [
			"tls"
		],
		"environment": {
			"addresses": [],
			"architectures": [
				"x86_64",
				"i686"
			],
			"certificate": "-----BEGIN CERTIFICATE-----\nMIIB9zCCAX2gAwIBAgIQU3bmUn7ogbX2pOjlALWf7TAKBggqhkjOPQQDAzA0MRww\nGgYDVQQKExNsaW51eGNvbnRhaW5lcnMub3JnMRQwEgYDVQQDDAtyb290QHVwdG93\nbjAeFw0xOTEwMjEyMDMzMzRaFw0yOTEwMTgyMDMzMzRaMDQxHDAaBgNVBAoTE2xp\nbnV4Y29udGFpbmVycy5vcmcxFDASBgNVBAMMC3Jvb3RAdXB0b3duMHYwEAYHKoZI\nzj0CAQYFK4EEACIDYgAEzZhp2YHDbTeZIhdxUaKj6JZ5Cpqi2K4qzAdZ243TIo6r\nOjzh9Q+7Ux9ZUBAXDuzDQEjpN2rSMzFLXxjy6PUUqn+ukSzNGERQYKKv3Rx2qKFs\n3zgt3WGTP/CPvf0fHTY6o1QwUjAOBgNVHQ8BAf8EBAMCBaAwEwYDVR0lBAwwCgYI\nKwYBBQUHAwEwDAYDVR0TAQH/BAIwADAdBgNVHREEFjAUggZ1cHRvd26HBMCoAguH\nBAqpKAEwCgYIKoZIzj0EAwMDaAAwZQIwDBSN4Xu1B8zP0oU3qDnvdltOmf95EBLf\ns9CJwiovmwxAuyaFwIYJyGC/pWYH35uHAjEAwlIPBWQzs2qjP0L3Z+JI54al2N1N\niACdzozxVE9eHgGFNOTMppNbBpeKo4tudOab\n-----END CERTIFICATE-----\n",
			"certificate_fingerprint": "6aaceb8d2e522b490ee1d95bf2a31be73f1ed8bcf503709e55f630f1b7be0c58",
			"driver": "lxc",
			"driver_version": "4.0.2",
			"firewall": "xtables",
			"kernel": "Linux",
			"kernel_architecture": "x86_64",
			"kernel_features": {
				"netnsid_getifaddrs": "true",
				"seccomp_listener": "true",
				"seccomp_listener_continue": "true",
				"shiftfs": "false",
				"uevent_injection": "true",
				"unpriv_fscaps": "true"
			},
			"kernel_version": "5.4.0-29-generic",
			"lxc_features": {
				"cgroup2": "true",
				"mount_injection_file": "true",
				"network_gateway_device_route": "true",
				"network_ipvlan": "true",
				"network_l2proxy": "true",
				"network_phys_macvlan_mtu": "true",
				"network_veth_router": "true",
				"seccomp_notify": "true"
			},
			"os_name": "Ubuntu",
			"os_version": "20.04",
			"project": "default",
			"server": "lxd",
			"server_clustered": false,
			"server_name": "uptown",
			"server_pid": 2687,
			"server_version": "4.1",
			"storage": "zfs",
			"storage_version": "0.8.3-1ubuntu12"
		}
	}
Creating dev-vm-b
DBUG[05-20|09:56:53] Connecting to a remote simplestreams server
DBUG[05-20|09:56:53] Connected to the websocket: ws://unix.socket/1.0/events
DBUG[05-20|09:56:53] Sending request to LXD                   method=POST url=http://unix.socket/1.0/instances etag=
DBUG[05-20|09:56:53]
	{
		"architecture": "",
		"config": {},
		"devices": {},
		"ephemeral": false,
		"profiles": null,
		"stateful": false,
		"description": "",
		"name": "dev-vm-b",
		"source": {
			"type": "image",
			"certificate": "",
			"alias": "trusty",
			"server": "https://cloud-images.ubuntu.com/daily",
			"protocol": "simplestreams",
			"mode": "pull"
		},
		"instance_type": "",
		"type": "virtual-machine"
	}
Error: Failed instance creation: The requested image couldn't be found

As it is right now, this is a stream issue, there are no combined_disk1-img or combined_disk-kvm-img metadata for any of those.


Remove useless -D_ENDIAN from MPE/iX-gcc config [1.0.2]

Merged.  bb868bbc4605b1e4c8591a943dbba4cf3ca0a26c


Add WeightedSwitchController

Closes #96, #93

Will be nice to make a release in a couple of days) This changes will really support our daily work)

Thank you very much for this contribution! we greatly appreciate contributions and encourage to build the DSL in collaboration with its users and community.
Remember when sending pull requests to also send updates on user guide documentation. I think this new controller would be worth a new user guide section.

I am merging it as is as to speed up its release and tune some things for consistency with rest of dsl.

did you fix all things you comment or not?)
I was ready to fix

I merged your latests PR and we are tuning some things in implementation before release.
Remember when submitting a PR to execute mvn clean install or at least mvn clean validate to verify that styles match, since the PR have failed on CI due to styling issues (we already corrected them locally), but that this into consideration for the future :).


Is it possible to get an extended example?

Hello,
first of all great work! I am really liking your plugin.
Since i am not too familiar with the shopify api nor strapi, would it be possible to get an extended example on how to setup the Shopify Context (https://github.com/Shopify/shopify-api-node/blob/main/docs/getting_started.md#set-up-context) within Strapi and how to do a REST (https://github.com/Shopify/shopify-api-node/blob/main/docs/usage/rest.md) and/or GRAPHQL (https://github.com/Shopify/shopify-api-node/blob/main/docs/usage/graphql.md) request, also within a Strapi controller?
Thank you so very much

example rest call from strapi controller:
    async count(ctx) {
        let productCount;
        try {
            const shopifyService = strapi.service('plugin::shopify.shopify');
            const restClient = await shopifyService.getClientRest(ctx)
            productCount = await restClient.get({
                path: '/admin/api/2022-01/products/count.json',
            });
        } catch (error) {
            ctx.throw(500,error)
        }
        ctx.send(productCount.body)
    },


Don't know how to build task 'default'

When sending test data to coveralls, from the CLI (using bundle exec coveralls push), the following error is raised:
rake aborted!
Don't know how to build task 'default' (See the list of available tasks with `rake --tasks`)
/home/sylvain/.rvm/gems/ruby-2.6.5@fab-manager/gems/rake-13.0.1/exe/rake:27:in `<top (required)>'
/home/sylvain/.rvm/gems/ruby-2.6.5@fab-manager/bin/ruby_executable_hooks:24:in `eval'
/home/sylvain/.rvm/gems/ruby-2.6.5@fab-manager/bin/ruby_executable_hooks:24:in `<main>'
(See full trace by running task with --trace)

Version installed: 0.18.0
Rails version: <IP_ADDRESS>
Ruby version: 2.6.5

After investigating, it was my fault.
I was missing require 'rails/test_unit/railtie' in config/application.rb (see this answer on SO).
Sorry for bothering, I'm closing the issue.


Appveyor: this-time-for-sure-rocky

Install GAX-related wrappers via pip to work around #1972.

@daspecster I'm thinking to cancel the Travis build and just merge in order to poke Appveyor:
https://ci.appveyor.com/project/dhermes/gcloud-python/

https://ci.appveyor.com/project/dhermes/gcloud-python/build/1.0.487.master

@daspecster woohoo!  We have a real test failure (rather than a build failure) on Appveyor:
======================================================================
FAIL: test_read_from_cli_info (gcloud.test__helpers.Test__get_default_service_project_id)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "C:\projects\gcloud-python\gcloud\test__helpers.py", line 223, in test_read_from_cli_info
    self.assertEqual('test-project-id', project_id)
AssertionError: 'test-project-id' != None

yay! This looks familiar too!

@daspecster do we have an issue open for that?

Nope, but there is now!


PCSCF returns "504 Server Time-Out" when using SIPp UE during registration

Hello Herlesupreet, good day
I am trying to register in IMS after establishing the PDU session towards PCSCF. However, once PCSCF sends AAR to PCRF and AAA is received, after 3 seconds PCSCF replies "504 Server Time-Out" to UE. This is the packet capture:

20231114f.zip
PCSCF logs are here:
4(44) NOTICE:

I believe SIP REGISTER is sent with wrong SIP Request URI. Rather than sip:<IP_ADDRESS> it should be sip:ims.mnc001.mcc001.3gppnetwork.org

Hello Herlesupreet,
thanks! after changing it from IP to domain and adjusting From/To from IP to domain as well, REGISTER has reached up to S-CSCF and 401 is sent back to UE
I am using SIPp and I need to work on the xml files to be able to process the 401 and re submit the REGISTER with authentication data, but that's a different story. Thanks for all your support!


Libvirt: Enable security profile feature

Add the security profile feature to handle CVM guest type for nested case and pass the security profile to the lisa platform.
Add launch security configuration to the cloud-hypervisor platform with type "sev" that will generate the xml to launch guest CVM.
Change cloud-hypervisor schema in libvirt, use kernel parameter to determine local or remote kernel file.

USAGE:
requirement:
      core_count: 1
      memory_mb: 1000
      features:
        items:
          - type: Security_Profile
            security_profile: "cvm"
      cloud-hypervisor:
        disk_img: ""
        disk_img_format: ""
        kernel:
          path: ""
          is_remote_path: True
        cloud_init:
          extra_user_data: ""
        disk_img_resize_gib: 25

@gamora12 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement
@microsoft-github-policy-service agree company="Microsoft"


FIX 16705 the flag "started" of RaftClusterInstance is false even though the cluster is started

https://github.com/apache/kafka/pull/15938

@chia7712  plz review it


Add option for collapsing breadcrumbs on mobile devices

See: https://design-system.service.gov.uk/components/breadcrumbs/#collapsing-breadcrumbs-on-mobile-devices

@paulrobertlloyd could you already do this by passing in a class, maybe?
render GovukComponent::Breadcrumbs.new(breadcrumbs: {
  'Level one': '/level-one/',
  'Level two': '/level-one/level-two/',
  'Level three': '/level-one/level-two/level-three'
}, classes: "govuk-breadcrumbs--collapse-on-mobile")

Yup, just a question of making it a more explicit option (like it is in the Nunjucks macro)

Ah yes, +1 for that! I was also unsure from the documentation/code whether you need to also include govuk-breadcrumbs when passing in classes, or whether they just add additional classes (like the Nunjucks version)?


Suggestion: Adopt the j2c v1 backend API (and get automatic prefixes for free)

Hi, @porsager I just notice this thanks to @JAForbes' tweet.
Would you mind adopting the j2c backend API? The general idea is that, rather than having your functions return strings, you pass a backend that accumulates them. So for example
export function selectorBlock(selector, style) {
  return selector + '{'
    + stylesToCss((typeof style === 'string' ? stringToObject(style) : style))
    + '}'
}

would become
export function selectorBlock(selector, style, backend) {
  backend.rule(selector)
  stylesToCss((typeof style === 'string' ? stringToObject(style) : style))
  backend._rule()
}

and
function propToString(style, k) {
  return (vendorRegex.test(k) ? '-' : '')
  + camelCaseToHyphen(k) + ':' + style[k] + ';'
}

would become
function emitDecl(style, k, backend) {
  backend.decl((vendorRegex.test(k) ? '-' : '') + camelCaseToHyphen(k), style[k])
}

The main advantage here is that it allows one to write plugins that decorate the backend, like this prefixing plugin that no one uses currently because I've yet to publish j2c v1 that uses the same architecture.
The prefix plugin supports more than one prefix per browser (FF and Edge have some properties that are exclusively available with a webkit prefix), is IIRC 3KB mingzipped and uses feature detection rather than a list of properties/selectors, etc... like autoprefixer and the inline style prefixer.
The architecture makes it trivial to turn one rule into many (e.g. flex-direction => -webkit-box-direction + -webkit-box-orient) without causing the allocation of extra objects.
Edit I can't English tonight...
Edit2: here's the full feature list: https://github.com/j2css/j2c/tree/3039875258bd69f04a16c51b69ca71361b5d5560/plugins/prefix-browser#features
Edit3: here's the full backend (sink) API.

Hi @pygy
That looks interesting.. I'm a bit behind with various stuff, so I hope its ok if I first take some time to look closer and grok this later on the week?

@porsager sure take your time :-)

Adding some clarifications, because there are j2c specific bits in the docs.
When you are ready, start here:
The backend/filter API provides a PostCSS-like system without a need to materialize the AST. Your engine calls it like this:
backend.init()
  backend.atrule('@-webkit-media', 'media', 'screen', 'rule' /*takes a block of rules*/)
    backend.rule('.foo')
      backend.decl('color', 'red')
    backend._rule()
  backend._atrule()
result = backend.done()

Which becomes with the default j2c backend the following string.
@-webkit-media screen {
  .foo {
    color: red;
  }
}

Plugins take the form of a decorator function that takes the backend as argument and return an object with a subset of the backend method:
function autoPxPlugin(next) { // next is the backend so far
  return {
    decl(prop, value) {
      next.decl(
        prop,
        needsPx(prop, value) ? value + 'px' : value
      )
  }
}

function needsPx(prop, value){
  // left as an exercise for the reader
}

The plugins are baked in when the lib is initialized:
const plugins = [autoPxPlugin]

const backend = plugins.reduce(
  (backend, plugin) => Object.assign({}, backend, plugin(backend),
  sink // the bare backend
)

The err() method allows one to display errors in context (try to add or remove a letter from an at-rule in the prefix-plugin playground), and the raw() method inserts raw text into the buffer. Not sure how useful they would be for bss.
Here's the default j2c sink:
let buf, err

const sink = {
  init: function () {buf=[], err=[]},
  done: function () {
    if (err.length != 0) throw new Error('j2c error(s): ' + JSON.stringify(err,null,2) + ', in context:\n' + buf.join(''))
    return buf.join('')
  },
  err: function (msg) {
    err.push(msg)
    buf.push('/* +++ ERROR +++ ' + msg + ' */\n')
  },
  raw: function (str) {buf.push(str, '\n')},
  atrule: function (rule, kind, param, takesBlock) {
    buf.push(rule, param && ' ', param, takesBlock ? ' {\n' : ';\n')
  },
  // close atrule
  _atrule: function () {buf.push('}\n')},
  rule: function (selector) {buf.push(selector, ' {\n')},
  // close rule
  _rule: function () {buf.push('}\n')},
  decl: function (prop, value) {buf.push(prop, ':', value, ';\n')}
}

Provided you are inserting rules using insertRule() may have to monitor the nesting level and insert when it reaches 0 when either _rule() or _atrule() are called (assuming it is possible for a single call to generate more than one rule).

Hi @pygy .. Sorry for not getting back sooner.
bss already does automatic vendor prefixes and eg. px suffixing, but it is also browser only, relying on dom vendor prefix detection to do it.
I've been trying to wrap my head around this, and if I get it right implementing this would mainly be a benefit when generating actual stylesheets outside the browser for eg. SSR right?
I have some ideas for how to make SSR possible with bss, and they might fit well with the j2c backend api, but I also need to do a bit more, such as enabling the function calling style of writing css which bss provides.
I might be misunderstanding some things, so if it's easier to discuss on gitter we can also continue there ;)

@porsager The prefix plugin is client-side only at the moment, for SSR, I have a PostCSS adapter that creates a PostCSS AST out of what you feed it, applies PostCSS plugins and walks the resulting tree to call the next part of the backend...
I had missed the vendor prefix detection in bss... AFAICS, it only prefixes properties. The prefix plugin linked above also prefixes values (keywords, functions, properties as values (transition: , will-change:, ...), selectors (pseudo elements, ...), and at-rules (the rules themselves and their parameters where needed e.g. @media (min-resolution: 2dppx) to whatever the browser supports (-webkit-min-resolution: 2) or min-resolution: 192dpi). It also translates the final flexbox spec to the older variants, sometimes expanding one shortcut property to multiple ones.
I may have missed some things, the full feature list is in the readme.
For gitter, sure, the j2c channel would seem appropriate unless you have one for bss (porsager/bss returns a 404)
https://gitter.im/j2css/j2c


Remove unintended negative

Changing "cannot" to "can" in hopes of fixing a typo. This issue could also have been fixed by changing "...users are given access..." to "...users are not given access...", but I wanted to try to avoid the double negative.

Learn Build status updates of commit 04796eb:
:bulb: Validation status: suggestions

File
Status
Preview URL
Details

power-platform/guidance/adoption/environment-strategy.md
:bulb:Suggestion

Details

power-platform/guidance/adoption/environment-strategy.md

Line 104, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 159, Column 6: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@MrCarney Thanks for helping improve our docs.


Page navigation in page objects: how to await next page

I am having trouble understanding the documentation in regards to the page model.
What I want to do
Similiar to the proposal in the Selenium Wiki (with Java Example), I want to create page objects with a method in the constructor to wait for the page to be fully loaded.
Example
Let's consider the following test code: I instantiate my first page with testcafe in the constructor and then perform an action.
test("I search for a product code", async (testcafe) => {
    const navBar = await new Navigation(testcafe)
    await navBar.search("ddd")
})

The Navigation page object looks like this:
export default class Navigation {
    constructor(testcafe) {
        this.testcafe = testcafe
    }

    get searchInput() {
        return Selector(".SearchBar-queryInput")
    }

    async search(searchTerm) {
        await this.testcafe
            .typeText(this.searchInput, "high heels")
            .expect(this.searchInput.value)
            .eql(
                "high heels",
                "Navigation search input: The search term doesn't show on the input."
            )
        await this.testcafe.pressKey("enter")
        // THIS LINE IS THE BIG PROBLEM
        // Pressing Enter will lead me to the next page. But how do I properly
        // await the next page to be fully loaded?
        const plp = await new PLP(this.testcafe)
    }
}

The next page's page object is this:
export default class PLP {
    constructor(testcafe) {
        this.testcafe = testcafe
        // This should throw an error: this element can't exist
        this.nonexisting = Selector(".thiselementcantexist")
    }

    async awaitFullyLoaded() {
        // This should throw an error: this element can't exist
        await Selector(".thiselementcantexist")
    }
}

How can I wait in the first class (Navigaton) for PLP to be fully loaded? Instantiating the next page's constructor with const plp = await new PLP(this.testcafe) does not cause testcafe to await the page elements. (Which is what I think was outlined here on the testcafe documentation actually.)
The below doesn't work either, it passes falsely.
const plp = new PLP(this.testcafe)
await plp.awaitFullyLoaded()

Similiarly, even doing it straight and dirty in the search method doesn't work:
await this.testcafe.pressKey("enter")
await Selector(".thiselementcantexist")

Hi @rick-schubert!
You can't mark a class constructor as an async function, it's a language-level limitation. So you could you a class constructor and an async method (you already tried it) and (optionally) static async method which calls constructor internally (IMHO it's a bit better) to create a page object and asynchronously wait for its loading:
class Page () {
    constructor () {
        // do stuff
    }

    async waitForLoading () {

    }

    static async create () {
        const page = new Page();
        await page.waitForLoading();
        return page;
    }
}

For loading condition you could check if some element exists on the page.

Hi @AndreyBelym , thank you very much for this answer! I haven't used static class methods before, your solutions looks like a really good trick though. Thank you!


TanStack react query v5 marks queryKey as required

This makes adding additional query options annoying as it forces overriding the query key that gets set in the generated code.
This only appears to affect queries and not mutations.

This was released in 6.19.1 can you test @leniency please?

Yup all good now, thanks!

Still happens, any fix?

Not many changes since 6.22.1 so look through the commits and see if you can spot it: https://github.com/anymaniax/orval/compare/v6.22.1...master

The genereted code is different
(6.30.0) query?: UseQueryOptions<Awaited<ReturnType<typeof getDomainValues>>, TError, TData>;
(6.22.1) query?: Partial<UseQueryOptions<Awaited<ReturnType<typeof getDomainValues>>, TError, TData>>;

@anymaniax I don't see any commit between 6.22.1 and 6.23.0 that would affect this Partial not being generated?  @Maxim-Mazurok @codebutler @soartec-lab

@melloware
So you want to know the reason why Partial is no longer generated?
if me question is correct, I'll search into it. and, I will also make corrections if possible.
I also read this as well.

Yes I don't see what changed that would cause this between 6.22.1 and 6.23.0.

@maapteh @ruiaraujo012
Hi, I checked the operation using PetStore, and the source code was generated with Partial existing as intended.
export const getListPetsQueryOptions = <TData = Awaited<ReturnType<typeof listPets>>, TError = AxiosError<Error>>(params?: ListPetsParams, options?: { query?:Partial<UseQueryOptions<Awaited<ReturnType<typeof listPets>>, TError, TData>>, axios?: AxiosRequestConfig}
) => {

using orval version is bellow:
$ npm list --depth=0 | grep orval
+--<EMAIL_ADDRESS>
I also checked the source code, but could not find any part that would reproduce the problem.
If possible, could you please share the minimal OpenAPI definition file?

@maapteh @ruiaraujo012 @melloware
Hi, I checked the operation using PetStore, and the source code was generated with Partial existing as intended.
export const getListPetsQueryOptions = <TData = Awaited<ReturnType<typeof listPets>>, TError = AxiosError<Error>>(params?: ListPetsParams, options?: { query?:Partial<UseQueryOptions<Awaited<ReturnType<typeof listPets>>, TError, TData>>, axios?: AxiosRequestConfig}
) => {

using orval version is bellow:
$ npm list --depth=0 | grep orval
+--<EMAIL_ADDRESS>
I also checked the source code, but could not find any part that would reproduce the problem.
If possible, could you please share the minimal OpenAPI definition file?

You're right, I tried again with v6.23.0, and it worked, it created the Partial.
I don't know what happened here, but it's working. Sorry for wasting your time.

@ruiaraujo012
it's okay. thank you for retry. I'm glad it went well 🙌

I thought this would be an easy one. But not. When i isolate the package from my pnpm monorepo and only install what is used in the setup for this generating and just use my own open-api yaml and the petstore yaml from your codebase i do see the Partial.
https://github.com/maapteh/orval-maybe-bug/blob/main/src/api/index.ts#L159
so there it is correct :(

@maapteh
Thank you for checking too.
Is it okay to conclude that this is not a bug and end the discussion on this issue? And if you have any problems, could you open a new issue by sharing your OpenAPI definition and generated codebase?

Yes i will ask some extra eyes in our monorepo, the weird thing is that when i run pnpm why i do see the correct versions :(

found the cullprit.
  const hasQueryV5 = true /* query.version === 5 || isQueryV5(
    context.packageJson,
    outputClient
  ); */

The V5 version detection was always false. When i override it to true i saw the Partial. Now i have to look why in a pnpm monorepo it cant not find the correct version which has been set in the workspace root.

Created at #1144

I had the same issue when running Orval in a npm workspace that had react-query as a peerDependency. It would be nice if it correctly detected that.

@tlrobinson you can specify which version you want in the config too now

@tlrobinson you can specify which version you want in the config too now
Could you show an example? I don't see this version option mentioned anywhere in the docs or examples.

I am facing the same issue. I have a PNPM Workspace, which uses Orval to generate the hooks for my frontend package based on the OpenAPI spec of the backend package. Since the generation runs on the Workspace level and not in my frontend package itself, I assume this version check is failing.

something like this
 module.exports = {
   petstore: {
     output: {
       ...
       override: {
         query: {
           version: the version you want
         },
       },
     },
     ...
   },
 };


[k8s] Add tcpReset=Enable (service object) support

applicable only on Standard LoadBalancer

yep, this should be supported


chore: update releasing process

Description
Update releasing process to not have so many images.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] Refactor/improvement

How Has This Been Tested?
N/A
Checklist
N/A

:tada: This PR is included in version 1.8.2-beta.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Added 2 sub commands for gmail push notification

@jonparrott
Thanks for the comments!
It's WIP and I'm still not sure we should merge this, but thanks.

No worries, I didn't know you weren't ready for review!

@tmatsuo, how about now?

@webmaven Yeah, possibly we can merge similar stuff, but now we provide command line access from gcloud SDK (alpha components), so I would rather not merge this.


Python error while compiling openxr

Hi, I'm trying to compile openXR but I've this error in visual studio :  'dispatch_generator.py'
Severity	Code	Description	Project	File	Line	Suppression State
Error	MSB3073	The command "python C:\Users\yushi\Documents\Projets\simulateur\En cours\Openxr\OpenXR-MotionCompensation\XR_APILAYER_NOVENDOR_motion_compensation\framework\dispatch_generator.py
:VCEnd" exited with code 2.	XR_APILAYER_NOVENDOR_motion_compensation	C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets	150
I've checked path to open XR SDK souce, mixed reality and SDK and seems OK.
Python is correctly installed.
any idea what's wrong ?
Thanks !

Your log shows you are trying to compile OpenXR-MotionCompensation. Did you file this issue in the wrong GitHub??

Hi, I solved this issue by suppression the whitespace int the path of the folder ('En_cours').
But now I've a second issue when executing the python script :
It's a Type 1 error. Seems an issue line 402 of the python script :
registry.apiGen(AutomaticSourceGeneratorOptions(
conventions       = conventions,
filename          = 'dispatch.gen.cpp',
directory         = cur_dir,
apiname           = 'openxr',
profile           = None,
versions          = featuresPat,
emitversions      = featuresPat,
defaultExtensions = 'openxr',
addExtensions     = None,
removeExtensions  = None,
emitExtensions    = extensionsPat))
Any idea ?
Could be a issue with my SDK version ?

Clearly not a VDXR issue (you are literally trying to compile a different project).
Closing.


Multi-file backup format

Is your feature request related to a problem? Please describe.
Backup times could be improved by writing to a multiple backup files concurrently. This would require a new backup format that is a folder with multiple files.
Describe the solution you'd like
Write backup streams concurrently to multiple out streams. Utilize JournalEntry's sequence number for merging the files into one continuous stream, during restoring. Restore overhead could be mitigated by chunking large enough continuous entries together in the same stream.
Urgency
Not urgent. Good for taking backups on large namespaces.

Looks like Rocks DB already have this improvement
When the metadata are stored in RocksDB, Alluxio 2.9 added support to checkpointing with multiple threads. alluxio.master.metastore.rocks.parallel.backup=true will turn on multi-threaded checkpointing and make the checkpointing a few times faster(depending how many threads are used). alluxio.master.metastore.rocks.parallel.backup.threads controls how many threads to use. alluxio.master.metastore.rocks.parallel.backup.compression.level specifies the compression level, where smaller means bigger file and less CPU consumption, and larger means smaller file and more CPU consumption.


Fixes #3641. CheckBox.State -> CheckBox.CheckState

Fixes

Fixes #3641

Proposed Changes/Todos

[x] State -> CheckedState
[x] OnToggled() -> AdvanceCheckState()
[x] Improve API docs
[x] Update migration guide

Pull Request checklist:

[x] I've named my PR in the form of "Fixes #issue. Terse description."
[x] My code follows the style guidelines of Terminal.Gui - if you use Visual Studio, hit CTRL-K-D to automatically reformat your files before committing.
[x] My code follows the Terminal.Gui library design guidelines
[x] I ran dotnet test before commit
[x] I have made corresponding changes to the API documentation (using /// style comments)
[x] My changes generate no new warnings
[x] I have checked my code and corrected any poor grammar or misspellings
[x] I conducted basic QA to assure all features are working

Love it! I think this is much clearer ♡


net/frr: Added BGP Network Import-Check

This adds a checkbox to enable frr's BGP Network Import-Check, as I had requirement in my own setup for this.
Reason
Until including frr 7.3, all defined networks were announced. Starting frr 7.4 (released July 2020) only routes present in the routing tables are announced. See frr documentation at: https://docs.frrouting.org/en/latest/bgp.html#networks
To not change default behavior in future frr releases again, I have added if-else to explicitly enable or disable the functionality based on the setting in OPNsense GUI.
There might be requirements - or expectations from users like myself - that all defined networks are announced. Therefore I also added a clarification with existing 'Network' help text.
Impact
For existing and new environments there will be no change. "Network Import-Check" is enabled in frr by default in current releases where this code is part of. The config setting will just explicitly enable the same in the config file.
Screenshot
Change looks like:

Config
Config generated when enabled:
root@OPNsense:~ # cat /usr/local/etc/frr/bgpd.conf
[...]
router bgp 64511
 no bgp ebgp-requires-policy
 bgp network import-check
 neighbor <IP_ADDRESS> remote-as 64512

Config generated when disabled:
root@OPNsense:~ # cat /usr/local/etc/frr/bgpd.conf
[...]
router bgp 64511
 no bgp ebgp-requires-policy
 no bgp network import-check
 neighbor <IP_ADDRESS> remote-as 64512

@mimugmail @fichtner I've read the new release is due tomorrow. Any change to get this merged before? I have other PRs also pending for a review, but not sure who's the best person to ask for?

To me it would be cleaner leaving default to 0 where 0 doesnt Touch config. This wouldnt break anything

I was at the same point - and I've decided to go with the "touch config" approach. The reason being that until including frr version 7.3, this config setting was disabled (0) by default. Starting frr 7.4 (released in July 2020) they changed its default to enabled.
To prevent any major issues in dropping routes whenever frr project feels like changing the default again, I thought it might be best idea to control it from a OPNsense standpoint and be on the safe side.
Just to explain my reasoning. If anyone disagrees and better using the default as you suggested, I'm fine to change it.

For further context 7.4 has been included for over two years now (apart from being released at that year as well) so we might as well make this explicit as suggested here. Up to @mimugmail
Building of releases wraps up 1-2 days before patchday so it's difficult to include non-bugfix changes for multiple reasons... ;)

Merged, thanks!


QE Server setup tweaks for jenkins slave

Moving user tasks from qe server playbook into new ansible role for jenkins slave playbook to reuse it.

@dahorak Does this change match what we have agreed on today?


[WebJobs/EventHubs] Verify that we have correct processing strategy default

We use balanced right now. For a large partition count, sometimes, it takes a while to grab ownership of the partition with messages. It might be an expected behavior but we need to verify.

Now we do.


External dependencies in integrations test

The integrations test should not have external dependency unless it is absolutely unavoidable.
It creates unnecessary external dependencies that lead to flaky tests.
        util_test.go:1464: Error downloading zip: Get https://github.com/che-samples/web-nodejs-sample/archive/master.zip: dial tcp: lookup github.com on [::1]:53: read udp [::1]:52934->[::1]:53: read: connection refused

The example app should be stored with tests, and then copied into a temp directory using helper.CopyExample
These are some of the test scenarios that are unnecessary cloning GitHub repos.
https://github.com/openshift/odo/blob/10826cc3f43c74ebadd917c3c53e9b40d6853aa6/tests/integration/devfile/utils/utils.go#L38
https://github.com/openshift/odo/blob/10826cc3f43c74ebadd917c3c53e9b40d6853aa6/tests/integration/devfile/docker/cmd_docker_devfile_url_test.go#L48
https://github.com/openshift/odo/blob/2086305a0caaaf603b90a4fb9139ebb0453f3a10/tests/integration/devfile/cmd_devfile_url_test.go#L53
https://github.com/openshift/odo/blob/12801e01b47dc5b4a08e3b30b346417540e5b385/tests/integration/devfile/cmd_devfile_delete_test.go#L51
/assign @maysunfaisal
/assign @yangcao77
/area testing

One of the PR review feedback was to clone the project, but I'll add it back since its creating flakes

Though the first log trace in OP
 util_test.go:1464: Error downloading zip: Get https://github.com/che-samples/web-nodejs-sample/archive/master.zip: dial tcp: lookup github.com on [::1]:53: read udp [::1]:52934->[::1]:53: read: connection refused

is from utils_test.go acc to PR https://github.com/openshift/odo/pull/3019 and is used to extract a downloaded project. @EnriqueL8 can you pls look at the disabled flake acc to PR #3019?
I can tackle the other integration tests like @kadel pointed out in the rest of the OP.

One of the PR review feedback was to clone the project, but I'll add it back since its creating flakes

hmm :-( Sorry for the confusion. Unless it is is really necessary for the test we should try to avoid any external dependencies like this.

Though the first log trace in OP
 util_test.go:1464: Error downloading zip: Get https://github.com/che-samples/web-nodejs-sample/archive/master.zip: dial tcp: lookup github.com on [::1]:53: read udp [::1]:52934->[::1]:53: read: connection refused

is from utils_test.go acc to PR #3019 and is used to extract a downloaded project. @EnriqueL8 can you pls look at the disabled flake acc to PR #3019 and assign yourself as well?

I forgot to include this one in the list.
/assign @EnriqueL8

ping @kadel :man_shrugging:


not working with nextjs app

Hello, first congrats on the cool lib. For those who use themes UI looks to be very simple and easy to use.
I'm trying to use this modal lib with nextjs, but when I install it and try to import returns errors that are not found:

How can I fix this?

hey @daniloab , sorry I haven't used this library in a long time but I took a brief look at this. It seems theme-ui has gotten quite a few updates, including depending on a version of @mdx-js/react that seems to break nextjs due to something with esm. I wasn't getting the erorr you got, but after some tinkering I got it to work. Please check out this example here https://codesandbox.io/s/react-modal-nextjs-x5j48f
Try to match the dependency versions of that example in package.json. Hopefully this helps!


Upgrade rspec-rails to 4.0.0

This makes rspec Rails 6 compatible, so failed screenshots are working again.
Before:

After:

These were previously saved as blank images, now they work as expected.

Finally! 💯


[logs][config] Strictly limit vector override to the logs-agent

What does this PR do?
Strictly limit the scope of vector.logs.(enabled|url) to the the logs agent.
Motivation
Prevent vector overrides to interfere with other agents that share the logs sending logic.
Additional Notes
N/A
Possible Drawbacks / Trade-offs
N/A
Describe how to test/QA your changes
Ensure vector.logs.(enabled|url) are effective with and only with the logs agent.
Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the config template has been updated.

Indeed having that feature for the serverless agent might be desirable in the near future.


Drop use of VIRTUAL_ENV=${Python_ROOT_DIR} workaround

Hi!
In the latest uv release, we no longer support this for using the system Python. You can see some more context at https://github.com/astral-sh/uv/issues/3765 and https://github.com/inventree/InvenTree/pull/7317.

Ah interesting, this fails with

error: the argument '--python ' cannot be used with '--system'

I presume that means you do not need the global system flag.


Tab navigation order is wrong

🛠 Fixes issue(s)

👨💻 Change(s) proposed

✔ Checklist (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

📷 Screenshots

@Sharmavedant17 thanks I will have a look at it later

Thanks for contributing @Sharmavedant17 :muscle:


BMDB: Operator/debug CLI

We want a CLI to talk to a BMDB, first to at least query per-machine state, and export that state to some somewhat machine-parsable format.
This is expected to be used when troubleshooting the BMDB in production, but also as a stopgap measure for integrating the BMDB in some deployments (eg. exporting machine information to spreadsheets, etc).

We now have webug as a read-only debug tool. We still should have a CLI for mutating the state, but that's probably gonna be written as we realize what kind of operations we need to perform. Until then, we'll probably mostly use webug and manual SQL surgery.


Android: add all compile deps to the module.ceylon, not just app-compat

The compile dependencies being present in app.gradle depend on the activities chosen, and since we leave the Java activities alone and they are compiled by the Ceylon compiler, we need those modules in the Ceylon module descriptor too.
I assume we should also do something about the APT deps, for example if you have apt deps like:
  apt 'com.jakewharton:butterknife-compiler:8.1.0'

You should add this to .ceylon/config:
[compiler]
apt=com.jakewharton.butterknife-compiler/8.1.0

APT deps should not go in the module.ceylon.

How should I transform names? The first : is simply replaced with a -, and what's after the second (and removed) : becomes the module version?

I think so.

This should be fixed.

compile dependencies are added to module.ceylon iff the Ceylon module needs to be created
apt dependencies are added to config every time the user clicks on "Configure Ceylon in this module"

Verified.


Stable version

Remove SNAPSHOT and clean up cross-compiling.  We're all good on Scala 2.11 now.
I did notice some of the stock unit tests from the original alexandru/shade project did not pass, which is a concern, but I'll leave that to the author. :-)

:+1:

@gzoller, @lloydmeta - thanks for your patience guys. I have upgraded dependencies, upgraded Scala versions and released version 1.7.0 to Maven Central.
I am not merging this pull request, because I wanted to keep the Scala 2.10 cross compilation for now.
This project, while fairly usable and complete, it's badly maintained. Mostly because the projects I've been working on have had no need for Memcached. Plus I'm busy, including other personal projects. I will try keeping its dependencies up to date, but as you can see, there can be delay.
So if you are interested, I can make you maintainers, provide commit rights, etc.


URL changes to actual URL and removes localhost while recording

The URL is overwritten while recording tests while navigating to sites(with a link click)

Start the server and start recording
java -jar wiremock-jre8-standalone-2.28.0.jar --enable-browser-proxying --https-port 8888 --proxy-all="https://www.eclipse.org" --record-mappings
Do the proxy setting as mentioned in link: I have done the browser configs as mentioned in screenshots:
https://masonm.github.io/wiremock/docs/proxying
Go to Site https://localhost:8888, the home page opens which is fine
Navigate to some link : Projects
Notice the change in URL to remove the word localhost, it is not going via localhost

Is there any steps i am missing.
PS: This works on some websites(Spring.io) and does not work on some sites.
Thanks

This isn't an issue with WireMock - it's simply that eclipse.org links are all absolute i.e. https://www.eclipse.org/projects/ rather than just /projects/.
This means that regardless of whether you load the homepage from localhost or anywhere else, you'll always go to the actual eclipse.org site when you click that link.
You can work around this using browser proxying however. You'll need to follow the instructions about importing and trusting WireMock's CA cert and start WireMock like this:
java -jar wiremock-jre8-standalone-2.28.0.jar --root-dir eclipse-recording --enable-browser-proxying --record-mappings

Configure your system proxy to use WireMock - localhost:8080 in this case.
Do some browsing.
Then stop WireMock and start it this way for playback:
java -jar wiremock-jre8-standalone-2.28.0.jar --root-dir eclipse-recording --enable-browser-proxying


Add contribution guide

I need contribution guide in this repo.
You can see the sample contribution guide from this pull request
https://github.com/mazipan/vue-currency-filter/pull/5/files
Thanks for your help 🎉🎉🎉

done, check PR :) #3


blast-bin: init at 2.13.0

Description of changes
NCBI BLAST is one of the most basic and important tools for bioinformatics.
I have been trying to build it from the source on darwin for over a year, but it is too hard to build with Nix on darwin.
The configure file and other scripts depend heavily on the build environment.
I have provided a precompiled binary for darwin, as I don't think I will be able to build it for a while. I would like to build it from source someday, but I believe there is great value in having a working one available from nixpkgs.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

1 package built:

blast

Result of nixpkgs-review pr 224345 run on aarch64-darwin 1

1 package built:

blast

@wegank
Thank you for your suggestion.
I have added a new blast-bin derivation to blast/bin.nix.

Binaries for x86_64-linux and aarch64-linux are available.
I will add them in a few hours since I can't work on Linux for a while now.

I have added binaries for x86_64-linux and aarch64-linux.
It works correctly on my x86_64-linux and aarch64-darwin machines.

Result of nixpkgs-review pr 224345 run on aarch64-linux 1

1 package built:

blast-bin


docs wrong

in the section Update the code is states that the event prcessing stops when a key is pressed, this is not the case - there is an await call to stop processing after 30s
// Wait for 30 seconds for the events to be processed
await Task.Delay(TimeSpan.FromSeconds(30));

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

ID: c4c6d63e-95f5-de2c-972b-4da5fe71a6a6
Version Independent ID: 338bbd1b-d86d-ff48-0b8a-1d48cb9547f2
Content: Quickstart: Send or receive events using .NET - Azure Event Hubs
Content Source: articles/event-hubs/event-hubs-dotnet-standard-getstarted-send.md
Service: event-hubs
GitHub Login: @spelluru
Microsoft Alias: spelluru

@spelluru
Thanks for your feedback! We will investigate and update as appropriate.

Thanks @digitalbanana for the feedback. Appreciate it.
Fixed the issue. #please-close


Make header labels more accurate

The current, somewhat-confusing labels:

Rules

Display the month when viewing a week that is entirely in the current year
Display the the month+year when viewing a previous/future year
When viewing a week that spans multiple years, display the label in the format of {Short Month} {Short Year} - {Short Month} {Short year}

Acceptance Criteria

[ ] All labels follow the above rules
[ ] Unit test(s) provided that validate each rule

Here is a reference table for all scenarios:

Today
Week In View
Heading label
Someday Week label
Someday Month label

1/8/25
1/5/25 - 1/11/25
January
1.5-11
January

12/30/24
1/5/25 - 1/11/25
January 2025
1.5-11
January

12/30/24
12/29/24 - 1/4/25
Dec 24 - Jan 25
12.29 - 1.4
December

Context
Since Compass is a minimal calendar, this should help us minimize the text on the screen while also making it clear what dates the user is currently viewing
Implementation Guidance
To confirm how it looks in the UI, you can hard-code the today value to in useToday.ts like so:
const today = dayjs("2024-01-04");

I'll be working on this one.


[GLUTEN-4668][CH] Merge two phase hash-based aggregate into one aggregate in the spark plan when there is no shuffle

What changes were proposed in this pull request?
Merge two phase hash-based aggregate into one aggregate in the spark plan when there is no shuffle:
Examples:
 HashAggregate(t1.i, SUM, final)
                |                  =>    HashAggregate(t1.i, SUM, complete)
 HashAggregate(t1.i, SUM, partial)

now this feature only support for CH backend.
Close #4668.
(Fixes: #4668)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

@liujiayi771 @lgbo-ustc please help to review, thanks.

@liujiayi771 @lgbo-ustc @ulysses-you @PHILO-HE @rui-mo    please help to review again, thanks.

Could you add some description for the motivation of this PR? It is a usual case for partial + final without shuffle between? Thanks.

Updated, please review again, thanks.  @ulysses-you @rui-mo

lgtm if test pass, cc @rui-mo if you have other comments

LGTM

===== Performance report for TPCH SF2000 with Velox backend, for reference only ====

query
log/native_4669_time.csv
log/native_master_02_20_2024_c3614f866_time.csv
difference
percentage

q1
30.14
34.24
4.108
113.63%

q2
25.53
24.42
-1.113
95.64%

q3
38.43
38.78
0.350
100.91%

q4
39.99
38.03
-1.960
95.10%

q5
83.15
70.83
-12.318
85.19%

q6
36.19
7.23
-28.954
19.99%

q7
118.82
82.68
-36.140
69.58%

q8
100.31
85.38
-14.929
85.12%

q9
132.51
126.15
-6.357
95.20%

q10
50.64
43.25
-7.387
85.41%

q11
23.49
20.79
-2.704
88.49%

q12
23.02
26.48
3.458
115.02%

q13
47.66
44.88
-2.782
94.16%

q14
13.86
18.88
5.022
136.24%

q15
33.06
29.18
-3.884
88.25%

q16
15.84
15.42
-0.425
97.32%

q17
106.42
102.55
-3.871
96.36%

q18
154.83
149.13
-5.702
96.32%

q19
20.37
12.57
-7.793
61.74%

q20
34.01
26.34
-7.670
77.45%

q21
226.46
225.83
-0.630
99.72%

q22
13.84
13.68
-0.158
98.86%

total
1368.56
1236.72
-131.840
90.37%


Prepare for 14.1.1 Release

🎈 Release
Preparation for 14.1.1 release.
Comparison to 14.1.0: https://github.com/gazebosim/sdformat/compare/sdformat14_14.1.0...sdf14

Needed by <PR(s)>
Checklist

[ ] Asked team if this is a good time for a release
[ ] There are no changes to be ported from the previous major version
[ ] No PRs targeted at this major version are close to getting in
[ ] Bumped minor for new features, patch for bug fixes
[ ] Updated changelog
[ ] Updated migration guide (as needed)
[ ] Link to PR updating dependency versions in appropriate repository in gazebo-release (as needed):

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

I have a fix for brew CI in https://github.com/gazebosim/sdformat/pull/1389 if you want to wait for that

Thanks @scpeters. I've merged that and updated the changelog.


Field values

This PR resolves issue #2091 and #1979.
Note that this PR contains changes from PR #2377. That means:

This PR could be reviewed for functions now.
Code of this PR should be reviewed after PR #2377 is merged.
This PR should be merged after PR #2377 is merged.

converting this to a draft since it is dependent on #2377

On hold pending completion of variable selector, #2400

@StasJ, @sgpearse, @clyne  please review ASAP.

One last thing - it looks like the color-mapped variable is written to the file by default.  We may want to check it in our variable selection list.  Or we could just not write the color mapped variable values unless the user selects that variable.

One last thing - it looks like the color-mapped variable is written to the file by default. We may want to check it in our variable selection list. Or we could just not write the color mapped variable values unless the user selects that variable.

Agreed. Furthermore, if you do the color mapped variable  from the multi-variable selector it will be output twice.

~The code looks good, but I can't seem to be able to write VaporFlow.txt, or select another file to write to. Is anyone else experiencing this?~
~1) Start up vapor, and import one of Leigh's MayControl files~
~2) Reduce the streamline grid to 1x1x1~
~3) Select 'dbz' and then press "Write to file" and nothing will happen~
I found vaporFlow.txt. It looks like the first letter of the file is being set to lower case.
When I try to select a new file, I cannot enter a new filename, only select existing files. The PFileSelector does not seem to be using its complimentary VWidget (VFileSelector).

Scott, can you remove that file and try to output again see if you experience problems? On my Ubuntu system it is capital V instead of a small v. If it still doesn't work, then I'll need to look more closely.

One last thing - it looks like the color-mapped variable is written to the file by default. We may want to check it in our variable selection list. Or we could just not write the color mapped variable values unless the user selects that variable.

One last thing - it looks like the color-mapped variable is written to the file by default. We may want to check it in our variable selection list. Or we could just not write the color mapped variable values unless the user selects that variable.

Agreed. Furthermore, if you do the color mapped variable from the multi-variable selector it will be output twice.

I have address this issue in 9c2aa5fc203f0a7bc6c2cab04ab96d33df9eee02 so that no duplicate output anymore. I kept the behavior that the color mapping value is always output, since I feel that's a value calculated already, why not output it too?

One last thing - it looks like the color-mapped variable is written to the file by default. We may want to check it in our variable selection list. Or we could just not write the color mapped variable values unless the user selects that variable.

One last thing - it looks like the color-mapped variable is written to the file by default. We may want to check it in our variable selection list. Or we could just not write the color mapped variable values unless the user selects that variable.

Agreed. Furthermore, if you do the color mapped variable from the multi-variable selector it will be output twice.

I have address this issue in 9c2aa5f so that no duplicate output anymore. I kept the behavior that the color mapping value is always output, since I feel that's a value calculated already, why not output it too?

Sounds good to me.

Scott, can you remove that file and try to output again see if you experience problems? On my Ubuntu system it is capital V instead of a small v. If it still doesn't work, then I'll need to look more closely.

I see the capital V now.  But I seem to be unable to perform multiple writes.  I'm on OSX, using the DUKU dataset right now.  I can help test with other configurations.
Case 1

Delete VaporFlow.txt
Create a default flow renderer, and write VaporFlow.txt with the first variable in the list (P in DUKU's case)
Note the file's timestamp
Wait a minute and try to write the file again, and the timestamp does not update

Case 2

Delete VaporFlow.txt
Create a default flow renderer, and write VaporFlow.txt with the first variable in the list (P in DUKU's case)
Delete VaporFlow.txt again
Write VaporFlow.txt again, but it does not seem to write

Scott, can you remove that file and try to output again see if you experience problems? On my Ubuntu system it is capital V instead of a small v. If it still doesn't work, then I'll need to look more closely.

I see the capital V now. But I seem to be unable to perform multiple writes. I'm on OSX, using the DUKU dataset right now. I can help test with other configurations.
Case 1
1. Delete VaporFlow.txt

2. Create a default flow renderer, and write VaporFlow.txt with the first variable in the list (P in DUKU's case)

3. Note the file's timestamp

4. Wait a minute and try to write the file again, and the timestamp does not update

Case 2
1. Delete VaporFlow.txt

2. Create a default flow renderer, and write VaporFlow.txt with the first variable in the list (P in DUKU's case)

3. Delete VaporFlow.txt again

4. Write VaporFlow.txt again, but it does not seem to write

I observe the behavior you reported too. It seems in some occasions clicking the "Write To File" button alone isn't enough to trigger a paint event. Something else needs to change to trigger a paint event, for example, if you rotate the scene. I.e., after you rotate the scene, and then click on that button, the output function is called. I think it's a bug, but probably out of the scope of this PR.

I think it's a bug, but probably out of the scope of this PR.

No problem - I'll make a ticket and accept the PR.


Initial implementation of BotCommands and BotListener

PR update:

Install using python setup install
Run examples

commands_example.py, ok
external_events.py, ok
listener_example.py, ok
simple_cmd_cli.py

status, start and stop, ok
We are still checking how we can run the other commands


Hint to buy Crownstones on getting the app

Expected
A way / direction to get the actual hardware required to be used with the app. For example at one of the first screens.
Actual
No hints at all.
Steps to reproduce

Install app
Look at screen.

Configuration

App version: <IP_ADDRESS>

Checks
Make sure the following boxes are checked before submitting the issue - thanks!

[x] Check that you can login through https://cloud.crownstone.rocks/

This has been added to the app


Fixed unable to set seat model

Patch for https://github.com/wiremod/wire/pull/1750

Found more issues.


Add Go Lang Client Generation

Any Plans to Add Go Lang Client Generation to NSwag Studio?

Probably not yet : There are already a lot of suggested languages here (js, dart...) and adding a language means understanding the language and maintaining the code after the feature has been created, so I wouldn't expect anything soon.


Make WhereFilter Protocol more structured and add WhereFilterCompiler

Resolves #102

Description

Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have signed the CLA
[ ] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have run changie new to create a changelog entry

We will instead be promoting call_parameter_sets on the to the protocol level. @plypaul will be opening a PR for this soon.


Cannot connect to Oracle Db

System information:

Operating system (distribution) and version -> WIN 10
DBeaver version -> 21.0.3

Connection specification:

Database name and version -> Oracle
Driver name -> oracle.jdbc.OracleDriver

Seems it is server-side issue. Please, check connection preferences
https://stackoverflow.com/questions/10786782/ora-12514-tnslistener-does-not-currently-know-of-service-requested-in-connect-d

The problem is our connection uses service_name but on Dbeaver there is no slot where we can edit the service_name.

@uslss Is there a way to edit the service name in Dbeaver>?

@techlock77 in your screenshot, you are connecting via service name (orcl). If you actually want to use SID instead of service name, change that combo to SID and orcl will be interpreted as SID instead of service name.


Does not work on some websites

I think the bookmarklet does not work on some websites, due to cross-origin script constraints. I don't know if this can be fixed for the bookmarklet, but do believe that if the script were incorporated in the ARC toolkit extension it would function @ferllings

Bookmarklet doesn't work with CSP, at least in Firefox https://bugzilla.mozilla.org/show_bug.cgi?id=866522 .


remove insomnia logo png

trying to reduce bundle size and insomnia-core-logo.png is 454kb, replaces with svg

I was trying to install insomnia-electron-bin through AUR and I think this change causes the following problem:


Add support for scalar operation on bignums

Adds support for scalar operations on bignums, and also introduces more macros to avoid code duplication.
It would be better to have more generic impls for Ratio (and Complex), but that would take significantly more code, so it's left as a future extension.
Fixes #333.

Hi, thanks.
Loose thoughts:

This should be an optional feature
The existing arithmetic operation impls are based on elements that are cheap to clone. They are really not very good implementations for bignums, lots of unnecessary cloning of the elements.

We can use this for example:
 /// Perform elementwise
 #[doc=$doc]
 /// between `self` and reference `rhs`,
 /// and return the result (based on `self`).
 ///
 /// If their shapes disagree, `rhs` is broadcast to the shape of `self`.
 ///
 /// **Panics** if broadcasting isn’t possible.
 impl<'a, A, S, S2, D, E> $trt<&'a ArrayBase<S2, E>> for ArrayBase<S, D>
     where A: Clone + $trt<A, Output=A>,
           S: DataMut<Elem=A>,
           S2: Data<Elem=A>,
           D: Dimension,
           E: Dimension,
 {
     type Output = ArrayBase<S, D>;
     fn $mth(mut self, rhs: &ArrayBase<S2, E>) -> ArrayBase<S, D>
     {
         self.zip_mut_with(rhs, |x, y| {
             *x = x.clone() $operator y.clone();
         });
         self
     }
 }

For bignums we should not clone both operands. It requires some work. It's a bit unsatisfactory indeed, we want to base the array's Add impl for scalars on by value operations, but more general ones on by reference implementations.


[BD-46] feat: added translations English strings in FormAutosuggest component

Description
Paragon supports i18n, we should ensure all default English strings in the Form autosuggest component are marked for translation with react-intl.
Deploy Preview
Include a direct link to your changes in this PR's deploy preview here (e.g., a specific component page).
Merge Checklist

[ ] If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Netlify deploy preview, if applicable.
[ ] Does your change adhere to the documented style conventions?
[ ] Do any prop types have missing descriptions in the Props API tables in the documentation site (check deploy preview)?
[ ] Were your changes tested using all available themes (see theme switcher in the header of the deploy preview, under the "Settings" icon)?
[ ] Were your changes tested in the example app?
[ ] Is there adequate test coverage for your changes?
[ ] Consider whether this change needs to reviewed/QA'ed for accessibility (a11y). If so, please add wittjeff and adamstankiewicz as reviewers on this PR.

Post-merge Checklist

[ ] Verify your changes were released to NPM at the expected version.
[ ] If you'd like, share your contribution in #show-and-tell.
[ ] 🎉 🙌 Celebrate! Thanks for your contribution.

Thanks for the pull request, @PKulkoRaccoonGang!
When this pull request is ready, tag your edX technical lead.

@PKulkoRaccoonGang 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.

:tada: This PR is included in version 20.18.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket: