Conflicting Packages in Laravel 11: Your requirements could not be resolved to an installable set of packages

I am trying to install this larafirebase package but it have been giving me this error below
$ composer require kutia-software-company/larafirebase
./composer.json has been updated
Running composer update kutia-software-company/larafirebase
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires kutia-software-company/larafirebase * -> satisfiable by kutia-software-company/larafirebase[1.0.0, ..., 1.3.8].
    - kutia-software-company/larafirebase[1.0.0, ..., 1.2.0] require illuminate/support ~5.6.0|~5.7.0|~5.8.0|^6.0|^7.0|^8.0 -> found illuminate/support[v5.6.0, ..., v5.8.36, v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27] but these were not loaded, likely because it conflicts with another require.
    - kutia-software-company/larafirebase[1.3.0, ..., 1.3.2] require illuminate/support ^7.0|^8.0 -> found illuminate/support[v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27] but these were not loaded, likely because it conflicts with another require.
    - kutia-software-company/larafirebase[1.3.3, ..., 1.3.5] require illuminate/support ^7.0|^8.0|^9.0 -> found illuminate/support[v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.16] but these were not loaded, likely because it conflicts with another require.
    - kutia-software-company/larafirebase[1.3.6, ..., 1.3.8] require illuminate/support ^7.0|^8.0|^9.0|^10.0 -> found illuminate/support[v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.48.23] but these were not loaded, likely because it conflicts with another require.

You can also try re-running composer require with an explicit version constraint, e.g. "composer require kutia-software-company/larafirebase:*" to figure out if any version is installable, or "composer require kutia-software-company/larafirebase:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

I have used the package in Laravel 9 and 10 and it works perfectly. This is the first time I am trying it with Laravel 11.
Please, check if you can give a solution to this.

Please check the description of release 1.3.8, thanks!
https://github.com/kutia-software-company/larafirebase/releases/tag/1.3.8


public images are not shown

Required information

Distribution: ubuntu
Distribution version: 16.04
The output of "lxc info" (local):

config:
  core.https_address: '[::]:8443'
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
- network_dns_search
- container_nic_routed_limits
- instance_nic_bridged_vlan
- network_state_bond_bridge
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
- tls
environment:
  addresses:
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - '[fd42:ab1:40db:d5aa::1]:8443'
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  architectures:
  - x86_64
  - i686
  certificate: |
    -----BEGIN CERTIFICATE-----
   ...
    -----END CERTIFICATE-----
  certificate_fingerprint: 07e02b9e349d037ba57f2365675fe9ce173cf9590003af9f45e6545368b79918
  driver: lxc
  driver_version: 4.0.2
  firewall: xtables
  kernel: Linux
  kernel_architecture: x86_64
  kernel_features:
    netnsid_getifaddrs: "false"
    seccomp_listener: "false"
    seccomp_listener_continue: "false"
    shiftfs: "false"
    uevent_injection: "false"
    unpriv_fscaps: "true"
  kernel_version: 4.15.0-106-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"
    pidfd: "true"
    seccomp_notify: "true"
  os_name: Ubuntu
  os_version: "18.04"
  project: default
  server: lxd
  server_clustered: false
  server_name: troulwn0103
  server_pid: 28510
  server_version: "4.2"
  storage: dir
  storage_version: "1"

The output of "lxc info" (remote) say https://lxdhub.invalid:

 config:
  core.https_address: '[::]:8443'
  core.trust_password: true
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
- network_dns_search
- container_nic_routed_limits
- instance_nic_bridged_vlan
- network_state_bond_bridge
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
- tls
environment:
  addresses:
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  architectures:
  - x86_64
  - i686
  certificate: |
    -----BEGIN CERTIFICATE-----
    ...
    -----END CERTIFICATE-----
  certificate_fingerprint: a3f32526f0e1c5692ac3d522ad8c95804d14761ddf7fd20f6f5cd283b4644f0a
  driver: lxc
  driver_version: 4.0.2
  firewall: xtables
  kernel: Linux
  kernel_architecture: x86_64
  kernel_features:
    netnsid_getifaddrs: "false"
    seccomp_listener: "false"
    seccomp_listener_continue: "false"
    shiftfs: "false"
    uevent_injection: "false"
    unpriv_fscaps: "true"
  kernel_version: 4.15.0-20-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"
    pidfd: "true"
    seccomp_notify: "true"
  os_name: Ubuntu
  os_version: "18.04"
  project: default
  server: lxd
  server_clustered: false
  server_name: lxdhub-dev-0
  server_pid: 1479
  server_version: "4.2"
  storage: dir
  storage_version: "1"

Issue description
When adding the above given remote:
lxc remote add remote https://lxdhub.invalid:8443 --accept-certificate --public

I can query all public images:
$ lxc query remote/1.0/images
[
	"/1.0/images/12932120efc160c3dffcf903956ae0ad266dedfb146e2e3ae5622962d74552b1",
	"/1.0/images/2d7eddf1f4e8115e332512d66367d1e13b32de53c248aac34590f265a63e09ed",
	"/1.0/images/352b60d42c1bc81b91aaa7fb6c70848285b1818fbc7f1e0754e2eca0671ff270",
	"/1.0/images/3fddda7e68f96ee1422371ab15043d2f0fe2758602f4079fe4955ef3be18121e",
	"/1.0/images/f86ae8351f565e70b6fcc7e105bb0b8a0efc4345cd09b3094e0dbcca547e3ea4",
	"/1.0/images/fbe10319394e090d1351903b800a957fc18f9f842757822c7d95a793ab52e947"
]

But lxc image ls remote: does not show any images
$ lxc image ls remote:
+-------+-------------+--------+-------------+--------------+------+------+-------------+
| ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION | ARCHITECTURE | TYPE | SIZE | UPLOAD DATE |
+-------+-------------+--------+-------------+--------------+------+------+-------------+

Steps to reproduce

sudo snap install lxd on remote (add some images, make them public)
sudo snap install lxd locally
Add remote locally, run lxc image ls remote:

Can you show 'lxc query remote/1.0/images?recursion=1'

stgraber@castiana:~/data/code/lxc/lxc (stgraber/master)$ lxc remote add test https://<IP_ADDRESS>:8443 --public
Certificate fingerprint: c974d10ce6f4c1c148eacfe1275616fb1045407a3c7a5810d0b2d150a45227f9
ok (y/n)? y
stgraber@castiana:~/data/code/lxc/lxc (stgraber/master)$ lxc image list test:
+--------+--------------+--------+------------------------------------+--------------+-----------+--------+------------------------------+
| ALIAS  | FINGERPRINT  | PUBLIC |            DESCRIPTION             | ARCHITECTURE |   TYPE    |  SIZE  |         UPLOAD DATE          |
+--------+--------------+--------+------------------------------------+--------------+-----------+--------+------------------------------+
| alpine | 01fbab8a11e3 | yes    | Alpine edge amd64 (20200618_13:00) | x86_64       | CONTAINER | 4.12MB | Jun 18, 2020 at 2:42pm (UTC) |
+--------+--------------+--------+------------------------------------+--------------+-----------+--------+------------------------------+
stgraber@castiana:~/data/code/lxc/lxc (stgraber/master)$

Thought it might be version related so tried against a 4.0, 3.0 and 2.0 server, same result on all, works fine.

Thank you for the fast answer!
$ lxc query 'remote/1.0/images?recursion=1'
[
	{
		"aliases": [],
		"architecture": "i686",
		"auto_update": false,
		"cached": true,
		"created_at": "2020-06-10T12:52:30+02:00",
		"expires_at": "1970-01-01T01:00:00+01:00",
		"filename": "rlx_0.0.7-buster_+local_rlx-i386-lxd.tar.gz",
		"fingerprint": "12932120efc160c3dffcf903956ae0ad266dedfb146e2e3ae5622962d74552b1",
		"last_used_at": "2020-06-10T14:00:35.86261982+02:00",
		"profiles": [
			"default"
		],
		"properties": {
			"description": "rlx +local buster",
			"os": "debian",
			"release": "stable"
		},
		"public": false,
		"size": 85545436,
		"type": "container",
		"uploaded_at": "2020-06-10T14:00:35.794665885+02:00"
	},
	{
		"aliases": [],
		"architecture": "i686",
		"auto_update": false,
		"cached": false,
		"created_at": "2020-04-05T21:40:01+02:00",
		"expires_at": "1970-01-01T01:00:00+01:00",
		"filename": "",
		"fingerprint": "2d7eddf1f4e8115e332512d66367d1e13b32de53c248aac34590f265a63e09ed",
		"last_used_at": "2020-05-01T08:44:30.033245511+02:00",
		"profiles": [
			"default"
		],
		"properties": {
			"description": "rlx +local stretch",
			"os": "debian",
			"release": "stable"
		},
		"public": true,
		"size": 97230765,
		"type": "container",
		"uploaded_at": "2020-05-01T08:44:29.817007173+02:00"
	},
	{
		"aliases": [
			{
				"description": "",
				"name": "rlx-iccore/unstable"
			}
		],
		"architecture": "i686",
		"auto_update": false,
		"cached": false,
		"created_at": "2020-03-16T12:59:10+01:00",
		"expires_at": "1970-01-01T01:00:00+01:00",
		"filename": "rlx_0.0.5-stretch_+local_rlx-iccore-i386-lxd.tar.gz",
		"fingerprint": "352b60d42c1bc81b91aaa7fb6c70848285b1818fbc7f1e0754e2eca0671ff270",
		"last_used_at": "2020-03-18T13:05:56.676616+01:00",
		"profiles": [
			"default"
		],
		"properties": {
			"description": "rlx +local stretch",
			"os": "debian",
			"release": "stable"
		},
		"public": false,
		"size": 96279124,
		"type": "container",
		"uploaded_at": "2020-03-17T09:26:06.078013414+01:00"
	},
	{
		"aliases": [],
		"architecture": "x86_64",
		"auto_update": true,
		"cached": false,
		"created_at": "2020-06-10T02:00:00+02:00",
		"expires_at": "2023-04-26T02:00:00+02:00",
		"filename": "ubuntu-18.04-server-cloudimg-amd64-lxd.tar.xz",
		"fingerprint": "3fddda7e68f96ee1422371ab15043d2f0fe2758602f4079fe4955ef3be18121e",
		"last_used_at": "0001-01-01T00:36:12+00:34",
		"profiles": [
			"default"
		],
		"properties": {
			"architecture": "amd64",
			"description": "ubuntu 18.04 LTS amd64 (release) (20200610.1)",
			"label": "release",
			"os": "ubuntu",
			"release": "bionic",
			"serial": "20200610.1",
			"type": "squashfs",
			"version": "18.04"
		},
		"public": false,
		"size": 187986728,
		"type": "container",
		"update_source": {
			"alias": "18.04",
			"certificate": "",
			"image_type": "",
			"protocol": "simplestreams",
			"server": "https://cloud-images.ubuntu.com/releases"
		},
		"uploaded_at": "2020-06-14T21:02:22.512722894+02:00"
	},
	{
		"aliases": [],
		"architecture": "i686",
		"auto_update": true,
		"cached": true,
		"created_at": "2020-06-10T14:35:17+02:00",
		"expires_at": "1970-01-01T01:00:00+01:00",
		"filename": "rlx_0.0.8-buster_+local_rlx-iccore-i386-lxd.tar.gz",
		"fingerprint": "f86ae8351f565e70b6fcc7e105bb0b8a0efc4345cd09b3094e0dbcca547e3ea4",
		"last_used_at": "2020-06-17T13:49:21.634468284+02:00",
		"profiles": [
			"default"
		],
		"properties": {
			"description": "rlx +local buster",
			"os": "debian",
			"release": "stable"
		},
		"public": false,
		"size": 104414759,
		"type": "container",
		"update_source": {
			"alias": "rlx-iccore/i386/0.0.8-buster-unstable",
			"certificate": "-----BEGIN CERTIFICATE-----\...-----END CERTIFICATE-----\n",
			"image_type": "",
			"protocol": "lxd",
			"server": "https://lxdhub.invalid:8443"
		},
		"uploaded_at": "2020-06-17T09:07:04.746116125+02:00"
	},
	{
		"aliases": [
			{
				"description": "",
				"name": "lxdhub/latest"
			}
		],
		"architecture": "x86_64",
		"auto_update": false,
		"cached": false,
		"created_at": "2020-01-07T18:31:44+01:00",
		"expires_at": "1970-01-01T01:00:00+01:00",
		"filename": "lxdhub-img.tar.gz",
		"fingerprint": "fbe10319394e090d1351903b800a957fc18f9f842757822c7d95a793ab52e947",
		"last_used_at": "2020-03-18T15:13:13.565364641+01:00",
		"profiles": [
			"default"
		],
		"properties": {
			"description": "lxdhub v1.10.5 (2020-01-22 12:19)"
		},
		"public": false,
		"size": 499515547,
		"type": "container",
		"uploaded_at": "2020-03-16T11:00:55.832692651+01:00"
	}
]

Oh, as it turns out you're never actually testing against your image server, lxc query would be lxc query remote:/1.0/images?recursion=1 which would fail as lxc query isn't supported against public-only servers.

I'll send a fix for lxc query so it properly errors out in such cases.

Can you show lxc image list remote: --debug? Though I'm pretty sure that particular API call will indeed show no results, consistently with what you've seen in lxc image list.

$ lxc image ls remote: --debug
DBUG[06-22|08:42:24] Connecting to a remote public LXD over HTTPs
DBUG[06-22|08:42:24] Sending request to LXD                   method=GET url=https://lxdhub.invalid:8443/1.0 etag=
DBUG[06-22|08:42:24] Got response struct from LXD
DBUG[06-22|08:42:24]
	{
		"config": null,
		"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",
			"network_dns_search",
			"container_nic_routed_limits",
			"instance_nic_bridged_vlan",
			"network_state_bond_bridge"
		],
		"api_status": "stable",
		"api_version": "1.0",
		"auth": "untrusted",
		"public": false,
		"auth_methods": [
			"tls"
		],
		"environment": {
			"addresses": null,
			"architectures": null,
			"certificate": "",
			"certificate_fingerprint": "",
			"driver": "",
			"driver_version": "",
			"firewall": "",
			"kernel": "",
			"kernel_architecture": "",
			"kernel_features": null,
			"kernel_version": "",
			"lxc_features": null,
			"os_name": "",
			"os_version": "",
			"project": "",
			"server": "",
			"server_clustered": false,
			"server_name": "",
			"server_pid": 0,
			"server_version": "",
			"storage": "",
			"storage_version": ""
		}
	}
DBUG[06-22|08:42:24] Sending request to LXD                   method=GET url="https://lxdhub.invalid:8443/1.0/images?recursion=1" etag=
DBUG[06-22|08:42:25] Got response struct from LXD
DBUG[06-22|08:42:25]
	[]
+-------+-------------+--------+-------------+--------------+------+------+-------------+
| ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION | ARCHITECTURE | TYPE | SIZE | UPLOAD DATE |
+-------+-------------+--------+-------------+--------------+------+------+-------------+

And here is a raw curl to the remote api which definitly lists the available images:
$ curl -k https://lxdhub.invalid:8443/1.0/images | jq
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   423  100   423    0     0    816      0 --:--:-- --:--:-- --:--:--   816
{
  "type": "sync",
  "status": "Success",
  "status_code": 200,
  "operation": "",
  "error_code": 0,
  "error": "",
  "metadata": [
    "/1.0/images/cdec3b23ebeea6a192a6e1c125b8e29a67c27b87d065aca83ef253fa7bb03e61",
    "/1.0/images/ce03565c60ee195b0a6fbbfcbc95c8903b13b9cbcc2796854c2e95046445f519",
    "/1.0/images/12932120efc160c3dffcf903956ae0ad266dedfb146e2e3ae5622962d74552b1",
    "/1.0/images/f86ae8351f565e70b6fcc7e105bb0b8a0efc4345cd09b3094e0dbcca547e3ea4"
  ]
}

@brauner why did you close this issue as the lxc query was not actually the problem :wink:

Just saw that the actual request:
curl -k "https://lxdhub.invalid:8443/1.0/images?recursion=1" | jq
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   108  100   108    0     0    199      0 --:--:-- --:--:-- --:--:--   199
{
  "type": "sync",
  "status": "Success",
  "status_code": 200,
  "operation": "",
  "error_code": 0,
  "error": "",
  "metadata": []
}

What does the recursion mean?

Right so it's a server side bug.
I'm guessing that server isn't actual LXD but something trying to implement its REST API.
?recursion=1 is supported by all LXD REST collections and is a way to get all objects in the collection without having to do individual GET requests on them.

It is an lxd instance here is it's lxc info:
config:
  core.https_address: '[::]:8443'
  core.trust_password: true
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
- network_dns_search
- container_nic_routed_limits
- instance_nic_bridged_vlan
- network_state_bond_bridge
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
- tls
environment:
  addresses:
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  architectures:
  - x86_64
  - i686
  certificate: |
    -----BEGIN CERTIFICATE-----
    ...
    -----END CERTIFICATE-----
  certificate_fingerprint: a3f32526f0e1c5692ac3d522ad8c95804d14761ddf7fd20f6f5cd283b4644f0a
  driver: lxc
  driver_version: 4.0.2
  firewall: xtables
  kernel: Linux
  kernel_architecture: x86_64
  kernel_features:
    netnsid_getifaddrs: "false"
    seccomp_listener: "false"
    seccomp_listener_continue: "false"
    shiftfs: "false"
    uevent_injection: "false"
    unpriv_fscaps: "true"
  kernel_version: 4.15.0-20-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"
    pidfd: "true"
    seccomp_notify: "true"
  os_name: Ubuntu
  os_version: "18.04"
  project: default
  server: lxd
  server_clustered: false
  server_name: lxdhub-dev-0
  server_pid: 1479
  server_version: "4.2"
  storage: dir
  storage_version: "1"

When I run this on the server side system:
$ curl -k https://localhost:8443/1.0/images?recursion=1 | jq
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   108  100   108    0     0   3600      0 --:--:-- --:--:-- --:--:--  3724
{
  "type": "sync",
  "status": "Success",
  "status_code": 200,
  "operation": "",
  "error_code": 0,
  "error": "",
  "metadata": []
}

And
$ curl -k https://localhost:8443/1.0/images | jq
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   423  100   423    0     0  15107      0 --:--:-- --:--:-- --:--:-- 15107
{
  "type": "sync",
  "status": "Success",
  "status_code": 200,
  "operation": "",
  "error_code": 0,
  "error": "",
  "metadata": [
    "/1.0/images/cdec3b23ebeea6a192a6e1c125b8e29a67c27b87d065aca83ef253fa7bb03e61",
    "/1.0/images/ce03565c60ee195b0a6fbbfcbc95c8903b13b9cbcc2796854c2e95046445f519",
    "/1.0/images/12932120efc160c3dffcf903956ae0ad266dedfb146e2e3ae5622962d74552b1",
    "/1.0/images/f86ae8351f565e70b6fcc7e105bb0b8a0efc4345cd09b3094e0dbcca547e3ea4"
  ]
}

This behaviour also happened on my local system.

If I however run the request against the unix socket I get a different result (I have some public images locally as well):
$ curl --unix-socket /var/snap/lxd/common/lxd/unix.socket http://unix.socket/1.0/images\?recursion\=1 | jq
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  8996    0  8996    0     0   675k      0 --:--:-- --:--:-- --:--:--  627k
{
  "type": "sync",
  "status": "Success",
  "status_code": 200,
  "operation": "",
  "error_code": 0,
  "error": "",
  "metadata": [
   // lots of images here ...
  ]
}

I would suspect that this call does not return objects for some reason: https://github.com/lxc/lxd/blob/master/lxd/images.go#L1005

Hmm, could be one of the security checks hitting when it shouldn't... Will take a look.

Seems to be working fine here.
stgraber@castiana:~/data/code/lxc/lxd (lxc/master)$ lxc launch ubuntu:20.04 f1 -c security.nesting=true
Creating f1
Starting f1
stgraber@castiana:~/data/code/lxc/lxd (lxc/master)$ lxc exec f1 bash
root@f1:~# snap refresh
2020-06-22T13:17:37Z INFO Waiting for automatic snapd restart...
snapd 2.45.1 from Canonical✓ refreshed
lxd 4.2 from Canonical✓ refreshed
root@f1:~# snap list
Name    Version   Rev    Tracking         Publisher   Notes
core18  20200427  1754   latest/stable    canonical✓  base
lxd     4.2       15564  latest/stable/…  canonical✓  -
snapd   2.45.1    8140   latest/stable    canonical✓  snapd
root@f1:~# lxc config set core.https_address :8443
If this is your first time running LXD on this machine, you should also run: lxd init
To start your first instance, try: lxc launch ubuntu:18.04

root@f1:~# curl -k https://localhost:8443/1.0/images
{"type":"sync","status":"Success","status_code":200,"operation":"","error_code":0,"error":"","metadata":[]}
root@f1:~# lxc image copy images:alpine/edge local: --public
Image copied successfully!
root@f1:~# curl -k https://localhost:8443/1.0/images
{"type":"sync","status":"Success","status_code":200,"operation":"","error_code":0,"error":"","metadata":["/1.0/images/a07b6c615e4f568d99e8174f6745fab6e3edd6e73a3c6f60e646c30290bd610f"]}
root@f1:~# curl -k https://localhost:8443/1.0/images?recursion=1
{"type":"sync","status":"Success","status_code":200,"operation":"","error_code":0,"error":"","metadata":[{"auto_update":false,"properties":{"architecture":"amd64","description":"Alpine edge amd64 (20200622_13:00)","os":"Alpine","release":"edge","serial":"20200622_13:00","type":"squashfs"},"public":true,"expires_at":"1970-01-01T00:00:00Z","profiles":["default"],"aliases":[],"architecture":"x86_64","cached":false,"filename":"","fingerprint":"a07b6c615e4f568d99e8174f6745fab6e3edd6e73a3c6f60e646c30290bd610f","size":4326264,"update_source":{"alias":"alpine/edge","certificate":"","protocol":"simplestreams","server":"https://images.linuxcontainers.org","image_type":""},"type":"container","created_at":"2020-06-22T00:00:00Z","last_used_at":"0001-01-01T00:00:00Z","uploaded_at":"2020-06-22T13:18:26.225308109Z"}]}
root@f1:~#

Yes your example works for me as well, strange ...

Now I can reproduce it. Run:
lxc image import file.tar.gz remote: --alias whatever
ssh lxdhub.invalid
lxc image edit whatever  # change public from false to true

After this the images are not visible anymore, currently rebuilding lxd from source to get some more logs in GetImage

More than one image matches

Error from: https://github.com/lxc/lxd/blob/86d1735addd7fc393bcdeae0c5630b133c4151a9/lxd/db/images.go#L509

This check is wrong: https://github.com/lxc/lxd/blob/86d1735addd7fc393bcdeae0c5630b133c4151a9/lxd/db/images.mapper.go#L78
It will always return all public images if public is true even if the fingerprint is also given, so if there is more than one public image it will fail.


AppCompatSeekBar - settiing Enabled and Thumb in axml has no effect

Xamarin.Android Version (eg: 6.0): <IP_ADDRESS>
Operating System & Version (eg: Mac OSX 10.11): Windows 10
Support Libraries Version (eg: 23.3.0): Xamarin.Android.Support.Design <IP_ADDRESS>
Describe your Issue: Setting Enabled or Thumb (drawable) in axml on AppCompatSeekBar has no effect. Setting these in code works.
Steps to Reproduce (with link to sample solution if possible):
Create project.
Include Xamarin.Android.Support.Design <IP_ADDRESS> NuGet
Create layout (axml) containing AppCompatSeekBar.
Set Enabled to false in axml (e.g. android:Enabl;ed="false")
Set thumb drawable to a drwabled in axml (e.g. android:thumb="@drawable/ic_menu_camera"
Build and run
SeekBar still enabled and still has default thumb.
In code, set the Enabled property to false; and set thumb drawable [e.g. SetThumb(ContextCompat.GetDrawable(Activity, Resource.Drawable.ic_menu_camera)); ]
Build and run
SeekBar still disabled and thumb changed.
Include any relevant Exception Stack traces, build logs, adb logs:

@EnglishDave could you please provide a sample that demonstrates the issue you are experiencing please.
Regards

No response received, unable to reproduce, closing issue.  Please open a new issue if you have more information.


Support embedding mediamtx in other Go binaries

Describe the feature
Hi! I'm working on a video project that, for various reasons, is required to ship as a single statically-linked Go binary. I'd love to use MediaMTX (by forking and calling core.New) but as things currently stand I'd have to package up MediaMTX adjacent to my binary. As far as I can tell, there are only two things standing in the way of this being possible:

All of MediaMTX's code is in an internal subdirectory. I assume that means at some point somebody thought it was a bad idea to support MediaMTX in other Go binaries, so we can have a discussion about that.
There's a go generate step to create a VERSION file and download HLS.js and mediamtx-rpicamera. There probably exist workarounds for this, such as running this step as part of the process of publishing new package versions and including them in the tagged releases.

Would love to hear your thoughts!

Hello,

All of MediaMTX's code is in an internal subdirectory. I assume that means at some point somebody thought it was a bad idea to support MediaMTX in other Go binaries, so we can have a discussion about that.

This was already discussed in #533. We won't expose a public interface since that would mean guaranteeing its backward compatibility. Just fork the server and move what you need into the pkg folder.

There's a go generate step to create a VERSION file and download HLS.js and mediamtx-rpicamera. There probably exist workarounds for this, such as running this step as part of the process of publishing new package versions and including them in the tagged releases.

We need to run a pre-compilation process as lots of project do. While some compilers allow to define pre-processing stages that are executed automatically (like Meson and Maven), the Go compiler requires a manual command, that is go generate, that has to be run before go build. Running it does not influence the ability to embed the server into another executable (after you have moved what you need into the pkg folder).


info box with elevation, surface, max_speed

current features
Currently the elevation diagram has the following features:

shows the elevation along the current route as a line graph
hovering the graph shows the x/y values (distance/elevation) in a popup window, it also shows the 'segment length' and the 'type', but this information only really makes sense when path details are shown (see below)

hovering the graph also shows the current position as a popup positioned on the route that is displayed on the map

dragging the cursor in x-direction above the diagram selects an x-range and the map is zoomed to the corresponding part of the route. Clicking the diagram again removes the selection and the map is zoomed out to show the entire route again.

there is an error icon on the right y-axis of the diagram that can be used to select an elevation value (shown as horizontal line in the diagram). All parts of the route that are above this elevation are highlighted in red:

there is a 'Legend' label that displays the legend when we hover over it:

For elevation this makes no sense, because we should rather show it unconditionally or even do not show it at all since it has only one entry. When path details are shown it is useful however.

when path details are enabled there two arrow buttons are shown that can be used to switch between the shown path details:

The y-axis always shows the elevation, regardless of the selected path detail. The value of the selected path detail (here: road_class) is visualized by the coloring underneath the elevation line graph. The popup window's type and segment length fields now make sense and show the value of the path detail and the length of the corresponding route segment. The path detail value is also shown by the popup on the map. The legend is now useful (compared to the case when we only show elevation), but it might become too large when there are too many values:

However, we only use eight different colors for the graph coloring anyway.

some path details are not enum-like (like road_class or surface), but the value is numeric (like average_speed or time). In this case the path detail value is visualized using a linear color gradient (from blue to red) while the y-axis still shows the elevation:

The legend is disabled for numeric values, but it would be useful to show the value range.
missing features
a few things that could be improved (even without changing the entire concept):

use all available space in x-direction
allow zooming the graph (otherwise elevation details are hard to resolve for longer routes)

I did a proof of concept here: https://github.com/graphhopper/graphhopper-maps/tree/heightgraph
The path details are shown for hard-coded values (surface, road_environment, average_speed) and we can switch between the different route alternatives as well (this was easy to do thanks to Janek's nice app architecture :))


In a rust project, edit Cargo.toml not auto reload rust-analyzer

What did you expect to happen?
When I modify Cargo.toml, such as add a new trait, it can auto reload rust-analyzer to auto complete the new trait.
What actually happened?
Nothing happend.
Describe your attempts to resolve the issue
I tried modify Cargo.toml in other editor, such as vim and vanilla Emacs by doom:sandbox ,it work as expected.
Then I tried vanilla Doom , it not work.
Steps to reproduce

Open a termal, cargo new rust-demo;
Open Emacs, and open src/main.rs, then it will open a rust-analyzer server;
Open Cargo.toml file, and add some thing to [dependencies], such as:

[package]
name = "rust-demo"
version = "0.1.0"
edition = "2018"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
rand = "0.8.4"

There nothing happend.
If you open that file in other editor, such vim, change the 0.8.4 to 0.9.4, it worked as expect, will throw an error like this:

LSP :: rust-analyzer failed to load workspace: Failed to read Cargo metadata from Cargo.toml file /Users/jadestrong/Documents/JadeStrong/rust-in-action/rust-demo/Cargo.toml, cargo 1.55.0 (32da73ab1 2021-08-23): Failed to run `cargo metadata --manifest-path /Users/jadestrong/Documents/JadeStrong/rust-in-action/rust-demo/Cargo.toml`: `cargo metadata` exited with an error:     Updating `ustc` index
error: failed to select a version for the requirement `rand = "^0.9.4"`
candidate versions found which didn't match: 0.8.4, 0.8.3, 0.8.2, ...
location searched: `ustc` index (which is replacing registry `crates-io`)
required by package `rust-demo v0.1.0 (/Users/jadestrong/Documents/JadeStrong/rust-in-action/rust-demo)`
perhaps a crate was updated and forgotten to be re-vendored?

Reverting buffer ‘Cargo.toml’.

Here is doom/info :

generated    Oct 14, 2021 12:01:35
system       MacOS 11.6 Darwin 20.6.0 x86_64 ns
emacs        28.0.50 master 988428df7 ~/.emacs.d/ -> ~/.emacs.d/
doom         3.0.0-alpha HEAD -> develop 68c533697 2021-10-07 03:11:03 +0200 ~/.doom.d/ -> ~/dotfiles/home/.doom.d/
shell        /usr/local/bin/fish
features     ACL GLIB GMP GNUTLS JPEG JSON LIBXML2 MODULES NATIVE_COMP NOTIFY KQUEUE NS PDUMPER PNG RSVG THREADS TIFF TOOLKIT_SCROLL_BARS ZLIB
traits       gui server-running envvar-file custom-file
custom       warning-suppress-types warning-suppress-log-types safe-local-variable-values rime-librime-root rime-inline-ascii-trigger default-input-method
modules      :input (&user chinese2) :completion company ivy :ui deft doom doom-quit hl-todo modeline ophints (popup +defaults) vc-gutter vi-tilde-fringe window-select workspaces :editor (evil +everywhere) file-templates fold format multiple-cursors rotate-text snippets word-wrap :emacs dired electric ibuffer undo vc :checkers syntax :tools docker editorconfig (eval +overlay) lookup lsp magit make taskrunner :os macos :lang data emacs-lisp json (javascript +lsp) lua (markdown +grip) nix (org +pretty +dragndrop +pandoc +roam2 +present) plantuml (python +lsp) (rust +lsp) sh (web +lsp) :config (default +bindings +smartparens)
packages     (js-doc) (react-snippets) (evil-matchit) (pinyinlib) (leetcode :recipe (:host github :repo jadestrong/leetcode.el)) (insert-translated-name :recipe (:host github :repo manateelazycat/insert-translated-name)) (company-tabnine :recipe (:host github :repo TommyX12/company-tabnine)) (citre :recipe (:host github :repo universal-ctags/citre :files (*.el))) (eslintd-fix)

System Information
https://pastebin.com/FLQMHu51

I just tested it again and it works fine. IMO this can be closed.


FALCON-2272 Check if extension is enabled during an update of an extension job

Please paste the exact commands you used to dev test this one.


currentOffset and initialOffset null in CustomDragLayer, causing flickering in DragAround: Custom Drag Layer example

Hi all, React DnD is great, thanks for all your hard work.
Describe the bug
The Drag Around: Custom Drag Layer example says that using a custom drag layer will get rid of the flickering that can happen with a native drag layer. However, the example is still flickering for me, in both Chrome and Firefox. It's hard to see if you don't disable the rotation in the custom drag layer, but if you comment out the rotation you'll see it right away.
To Reproduce
Steps to reproduce the behavior:

Go to http://react-dnd.github.io/react-dnd/examples/drag-around/custom-drag-layer
Drag around the box that says "Drag me around"
See a flicker right when you drop, where the box disappears for a simple frame.
If you're having trouble seeing it, add an endDrag method to the implementation in DraggbleBox.tsx and put a breakpoint in it. When that breakpoint gets hit, you'll see the one frame where the box isn't drawn.

Expected behavior
Dragging an element around, with a Custom Drag Layer, shouldn't have any flickering.
Desktop (please complete the following information):

OS X 10.13.3 (High Sierra)
Chrome 73.0.3683.86 and Firefox 62.0
React Dnd v7.3.2

Additional context
Near as I can tell, the flicker is happening when CustomDragLayer renders after a drop occurs. There's a call to render where initialOffset and currentOffset are both null, and yet isDragging is true. This causes the style for the layer item to include {display: none}, which is what makes it flicker. You can hack a fix by doing something like this:
let cachedInitialOffset: XYCoord | undefined
let cachedCurrentOffset: XYCoord | undefined

const CustomDragLayer: React.SFC<CustomDragLayerProps> = props => {
	const { item, itemType, isDragging } = props

	if (!isDragging || props.currentOffset !== null) {
		cachedInitialOffset = props.initialOffset
		cachedCurrentOffset = props.currentOffset
	}

	const newProps = Object.assign({}, props, {
		currentOffset: cachedCurrentOffset,
		initialOffset: cachedInitialOffset,
	})

	function renderItem() {
		switch (itemType) {
			case ItemTypes.BOX:
				return <BoxDragPreview title={item.title} />
			default:
				return null
		}
	}

	if (!isDragging) {
		return null
	}
	return (

{renderItem()}

	)
}

But that's of course not a real solution. Thanks for looking at this!

Thanks! That solutions did save my day


Change chain ticker and supply

Is it possible to have prefunded accounts with a different ticker/coin ?

prefunded_accounts: '{"0x25941dC771bB64514Fc8abBce970307Fb9d477e9": {"balance": "10ETH"}, "0x4107be99052d895e3ee461C685b042Aa975ab5c0": {"balance": "1ETH"}}'

Like what if I want to spawn my own private blockchain and change ticker or supply? hence avoid calling it ETH

No. This is an ethereum package. If you want something else, you will have to fork this project.
This project focuses on Ethereum.


Project files missing

There are files referenced in the Visuals project that are missing from the repository, e.g. bingNews.ts, heatMapPlugin.ts, etc.

does this cause any build issues? or just shows as invalid references when you open up the reference file?

Just invalid references, I don't think it causes any build issues.
On Sep 10, 2015 3:13 PM, "Sachin Patney"<EMAIL_ADDRESS>wrote:

does this cause any build issues? or just shows as invalid references when
you open up the reference file?
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/PowerBI-visuals/issues/88#issuecomment-139397414
.


Customize concept display in value set expansion

Specific concepts for value set expansion dose not have specific display defined in ValueSet.compose.include.concept.display node.
I created the following value set which include specific code system (claim-type) with some fixed concepts; however the value set contains concept with different display other than that in code system as following
http://hapi.fhir.org/baseR4/ValueSet/claim-type-hanan
{
"resourceType": "ValueSet",
"id": "claim-type-hanan",
"meta": {
"versionId": "1",
"lastUpdated": "2021-01-07T15:03:03.761+00:00",
"source": "#wPBdpTmIQ459VzHp",
"profile": [
"http://hl7.org/fhir/StructureDefinition/shareablevalueset"
]
},
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode": "fm"
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode": "trial-use"
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
"valueInteger": 2
}
],
"url": "http://hl7.org/fhir/ValueSet/claim-type-hanan",
"identifier": [
{
"system": "urn:ietf:rfc:3986",
"value": "urn:oid:2.16.840.1.113883.4.642.3.558"
}
],
"version": "4.0.1",
"name": "ClaimTypeCodes",
"title": "Claim Type Codes",
"status": "draft",
"experimental": false,
"date": "2019-11-01T09:29:23+11:00",
"publisher": "Financial Management",
"contact": [
{
"telecom": [
{
"system": "url",
"value": "http://hl7.org/fhir"
}
]
}
],
"description": "This value set includes Claim Type codes.",
"immutable": true,
"copyright": "HL7 Inc.",
"compose": {
"include": [
{
"system": "http://terminology.hl7.org/CodeSystem/claim-type",
"concept": [
{
"code": "institutional",
"display": "InPatient"
},
{
"code": "oral",
"display": "Dental"
},
{
"code": "pharmacy",
"display": "Pharmacy"
},
{
"code": "professional",
"display": "OutPatient"
},
{
"code": "vision",
"display": "Optical"
}
]
}
]
}
}
however in expansion result I got the display as it was in code system; it should be the one specified in value set declaration ?
the expansion result:
{
"resourceType": "ValueSet",
"status": "active",
"compose": {
"include": [
{
"system": "http://terminology.hl7.org/CodeSystem/claim-type",
"concept": [
{
"code": "institutional",
"display": "InPatient"
},
{
"code": "oral",
"display": "Dental"
},
{
"code": "pharmacy",
"display": "Pharmacy"
},
{
"code": "professional",
"display": "OutPatient"
},
{
"code": "vision",
"display": "Optical"
}
]
}
]
},
"expansion": {
"identifier": "19614ac1-e151-4dcc-ab94-c927be3f25ea",
"timestamp": "2021-01-07T15:07:22+00:00",
"total": 5,
"offset": 0,
"parameter": [
{
"name": "offset",
"valueInteger": 0
},
{
"name": "count",
"valueInteger": 1000
}
],
"contains": [
{
"system": "http://terminology.hl7.org/CodeSystem/claim-type",
"code": "institutional",
"display": "Institutional"
},
{
"system": "http://terminology.hl7.org/CodeSystem/claim-type",
"code": "oral",
"display": "Oral"
},
{
"system": "http://terminology.hl7.org/CodeSystem/claim-type",
"code": "pharmacy",
"display": "Pharmacy"
},
{
"system": "http://terminology.hl7.org/CodeSystem/claim-type",
"code": "vision",
"display": "Vision"
},
{
"system": "http://terminology.hl7.org/CodeSystem/claim-type",
"code": "professional",
"display": "Professional"
}
]
}
}
Expected behavior
As mentioned in Fhir website the following node have the provided meaning
ValueSet.compose.include.concept.display: The text to display to the user for this concept in the context of this valueset. If no display is provided, then applications using the value set use the display specified for the code by the system.
Environment:

HAPI FHIR 5.3.0-SNAPSHOT

@jamesagnew
I case no one is working on this; I would like to work on it.

@jamesagnew
I case no one is working on this; I would like to work on it.

This issue has been resolved in Hapi Fhir version 5.3


Updated Chinese Localizations

I haven't been supporting this since 1.4.4, but I just forgot to close this PR xD


Added more plugin tests

This adds more plugin tests and a new way to create Prism instances inside a JSDOM VM.
It also fixes that Copy to Clipboard did not update the copied text if the text of the code element changed.
This can technically be seen as a fix for #1965.

Also, I just named the tests files basic-functionality for lack of a better name. Suggestions for a better pattern are very welcome.

Shit, I forgot about this.
I resolved the merge conflicts and addressed all review comments.
I fixed the usage of after by adding a util function called reusablePrismDom. The idea is that this function creates a Prism DOM and registers a cleanup function for the DOM. It's called reusable because the DOM instance is intended to be used by multiple it tests.
I also updated JSDom. JSDom 16 added support for createRange which drastically simplifies Keep Markup tests.


null is not an object RNDeliverer.setupStreamer

In RNDelivererModule.java haven't any method
Please check

As it is specified in the readme the android part is not done yet.


export: not working (local + network) on IE since 1.1.1

after choosing Export Csv no download window is presented, it's impossible to download the file.
It's working on Chrome.

@tgdriph3 Please name database and table query


Correct Variable Names in Synapse Notebook Example

Resolves #61641
The snippet declares two variables called account_name and container_name - but on the next line refers to them as blob_account_name and blob_container_name causing an error when executing.

@simondmorias : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ruixinxu - Hi, would you review the proposed revision to your article? Thanks.

#sign-off


Add Inference of SWE-bench for Data Interpreter

Features
Add Inference of SWE-bench for Data Interpreter

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 81.86%. Comparing base (e783e5b) to head (4ca6007).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##           swebench_di    #1026   +/-   ##
============================================
  Coverage        81.86%   81.86%
============================================
  Files              246      246
  Lines            13722    13722
============================================
  Hits             11233    11233
  Misses            2489     2489

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


I'm trying to build this premake5 project with cmake generator

Here is the project:
https://github.com/SpartanJ/eepp
I cloned premake-cmake into premake/premake-cmake directory and added this line into premake5.lua:
require "premake.premake-cmake.cmake"
Now it's possible for me to use the make generator with premake5 cmake.
It successfully generated the cmake build scripts. But when I actually invoke cmake it immediately fails with this error:
$ cmake -B build -S make/linux
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
CMake Error at eepp-maps.cmake:149 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:x86_64-debug>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:52 (include)

CMake Error at eepp-maps.cmake:149 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:x86-debug>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:52 (include)

CMake Error at eepp-maps.cmake:149 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:arm64-release>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:52 (include)

CMake Error at eepp-maps.cmake:149 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:x86-release>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:52 (include)

CMake Error at eepp-maps.cmake:149 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:x86_64-release>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:52 (include)

CMake Error at eepp-maps.cmake:149 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:arm64-debug>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:52 (include)

CMake Error at eepp-physics.cmake:153 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:x86-release>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:54 (include)

CMake Error at eepp-physics.cmake:153 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:arm64-release>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:54 (include)

CMake Error at eepp-physics.cmake:153 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:x86_64-release>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:54 (include)

CMake Error at eepp-physics.cmake:153 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:arm64-debug>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:54 (include)

CMake Error at eepp-physics.cmake:153 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:x86_64-debug>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:54 (include)

CMake Error at eepp-physics.cmake:153 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:x86-debug>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:54 (include)

CMake Error at eepp-shared.cmake:601 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:x86_64-debug>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:57 (include)

CMake Error at eepp-shared.cmake:601 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:x86_64-debug>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:57 (include)

CMake Error at eepp-shared.cmake:601 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:x86_64-release>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:57 (include)

CMake Error at eepp-shared.cmake:601 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:x86_64-release>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:57 (include)

CMake Error at eepp-shared.cmake:601 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:x86-release>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:57 (include)

CMake Error at eepp-shared.cmake:601 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:x86-release>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:57 (include)

CMake Error at eepp-shared.cmake:601 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:x86-debug>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:57 (include)

CMake Error at eepp-shared.cmake:601 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:x86-debug>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:57 (include)

CMake Error at eepp-shared.cmake:601 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:arm64-release>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:57 (include)

CMake Error at eepp-shared.cmake:601 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:arm64-release>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:57 (include)

CMake Error at eepp-shared.cmake:601 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:arm64-debug>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:57 (include)

CMake Error at eepp-shared.cmake:601 (add_custom_command):
  Error evaluating generator expression:

    $<CONFIG:arm64-debug>

  Expression syntax not recognized.
Call Stack (most recent call first):
  CMakeLists.txt:57 (include)

CMake Error at ecode-macos-helper-static.cmake:1 (add_library):
  No SOURCES given to target: ecode-macos-helper-static
Call Stack (most recent call first):
  CMakeLists.txt:39 (include)

CMake Generate step failed.  Build files cannot be regenerated correctly.

Please help.

I wonder if the '-' is problematic.

I don't know. This is not my project and the Premake build script is not written by me.

and added this line into premake5.lua: require "premake.premake-cmake.cmake"

A less intrusive way it to write that in premake5-system.lua (see https://premake.github.io/docs/System-Scripts/)

CMake Error at eepp-maps.cmake:149 (add_custom_command):
Error evaluating generator expression:
$<CONFIG:x86_64-debug>

Investigating the issue.

Investigating the issue.

Thank you.

Hyphen is indeed problematic in config/platform name.
Just pushed https://github.com/Jarod42/premake-cmake/commit/1871a3caa5a4d4b9561d15b02dc23c3e4c6a26bb
which should replace unsupported char by '_'

pre/postbuild commands has also been fixed.
Given project has even pushed some commits to add this generator.


Any plans for a .d.ts file for TypeScript projects?

First off this is a great project, it wraps knex just enough.
I am using this project in a project written in TypeScript. Is there a definition file or plans to create a definition file for the Objection.js library? Thanks.

We are using typescript in one of our projects at Vincit, and we have written some typings for that project, but we are not any good at it :smile:. If you have, or want to write, the typings I would be happy to accept a pull request.

Ha, I am not any good at it either. I've started one here https://github.com/dotDeeka/objection-d-ts that I can reference in my project. If I actually get it right I will certainly submit a PR for it.

Hoping to use this in a Typescript project one day, will keep an eye on this issue! Would go along well with the amazing documentation so far.

The typings, if and when added should be referenced from project.json
see: http://www.typescriptlang.org/docs/handbook/typings-for-npm-packages.html
also this may be of interest:
https://blogs.msdn.microsoft.com/typescript/2016/06/15/the-future-of-declaration-files/

Thanks for this great project!
Any progress on this issue?

Not on my part. @dotDeeka ?

No not really @koskimas . I have that repo in my account I've been using, I'm pretty sure its no where near complete. If anyone out there is interested in trying to make it more complete I'd certainly accept a PR, or even give what I have to someone if they're serious about owning it?

+1

Hello,
is there some new news about it?

@4nxiety There hasn't been anyone willing to own that part and keep updating typings when project evolves.

oh damn :/

@dotDeeka, @koskimas: my PR that adds typings, #239, is ready for review.

Fixed by #255

Awesome @mceachen, thanks for stepping up on this.

#272 is merged to master. @koskimas can you close this issue?

Any chance we'll get this as part of 0.7 ?


that newline drives me insane

You should make pull request here - https://github.com/zsh-users/prezto. For more information checkout this issue https://github.com/sorin-ionescu/prezto/issues/1239


Upper-Level Staff Update & ID Name Fix

ID Name Corrections: assisexecboard -> assistexecboard
Updated Upper-Level Staff
Added Internal Affairs Section
Changed zevante "Internal Affairs" to "Assistant Admin Officer"
Added OxElmonxO as Assistant Server Liaison
Changed "Updated" date.


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 15:42:29 on 2023.08.10
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 4, errors out: 0
Original problem ID: 35252
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=35252

Problem has been resolved in 15m 0s at 15:57:29 on 2023.08.10
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 35252


What additional Reporting fields will be needed for Q1 of 2024?

Context: For the first year of OBPS we may need to include extra data fields in the Reporting app. These will only be necessary for the 2024 reporting year.
This is because for Q1 of 2024 (Jan - Mar 31) Industry will still be paying carbon tax. Then the carbon tax exemption starts April 1 2024. The business area will need a way to calculate emissions/production data for those first 3 months. How will we do this?
Goal of this ticket:
[] Confirm with B.A. what specific fields will be required just for the 2024 Reporting year to deal that first quarter

Blocked by #50

Current understanding: For compliance report
Full Year Production data for 2024
April - Dec Production data for 2024 <this is the only additional data requested for 2024.

Update: now that we know the answer, we need to ensure this is part of the reporting fields artifact that business area is working on currently

Closing this ticket as we believe this has been answered. Follow-up ticket to be created to capture next steps.


Monetary contribution

I really like face-api.js
great job
How could I contribute economically? Some "Patreon"
Paypal?
I do not have much way to contribute economically but happy to do it.
I appreciate your response very much.
VERY Thank you

Hi, I really appreciate your offering! There is no need to do so no worries, also I don't have Patreon :)


NavigationView control "API in action" crashes when you enable PaneFooter visible.

Describe the bug

NavigationView control "API in action" crashes when you enable PaneFooter visible.
Steps to reproduce the bug

Steps to reproduce the behavior:

Go to NavigationView control
Scroll down to API in action control and enable PaneFooter

Expected behavior

For the setting to enable
Actual behavior

Crash
Screenshots

Version Info

Gallery version (found on Settings page):

<IP_ADDRESS>
Windows 10 version:

[ ] Insider Build (xxxxx)
[x] May 2020 Update
[x] November 2019 Update (18363)
[ ] May 2019 Update (18362)
[ ] October 2018 Update (17763)
[ ] April 2018 Update (17134)
[ ] Fall Creators Update (16299)
[ ] Creators Update (15063)
[ ] Anniversary Update (14393)

Device form factor:

[x] Desktop
[ ] Mobile
[ ] Xbox
[ ] Surface Hub
[ ] IoT

Additional context

Fixed in Microsoft.UI.Xaml v2.4.2. XAML Controls Gallery will need to get updated to version 2.4.2 to fix.
https://github.com/microsoft/microsoft-ui-xaml/pull/2395


Create Item Acquistion Hitbox/Object

Create an object that can be collided with that can grant an item upgrade, toggling the upgrade in the player character.

Added the ability to set the item acquisition boxes as temporary.


Update contributor ladder and contributor role

This PR adds onboarding/off-boarding guide for team members and also clarifies maintainer roles regarding governance and roadmap.

/cc @tuminoid @Rozzii


Discussion

Interested in discussing about work opportunities at Elicit. Interested in helping out with product engineering as I have spent lots of time analysing research studies manually. I am not presently using other relevant social channels so chatting here for time savings.

@jungofthewon @goodgravy @stuhlmueller @reppertj @stuhlmueller
I didn't notice any activity on this for a week now, tagging you all for visibility. I have a lot of great technology, research, business & communications experience that would be really helpful for the team. I have done a lot of independent non paid work which has helped me develop a useful skillset.
I also identify as a humanitarian. I get a-long pretty easily with others in team environments. I am interested in helping out remotely, hybridly or in person depending on team needs.
I am wanting to travel more while working on humanitarian works, continuing to learn & contributing to tech products.
I am also up to share more about myself over Zoom or possibly another channel. I like making new friends also so up for team building exercises prior to interviewing if you all want to try something like that.

@reppertj You're welcome. I submitted an application previously. I lost access to the email account used to apply, this has been my constant dilemma with applying to technology jobs while living temporarily domestic nomadically in a low resource situation due to circumstances partially out of my control.
Due to present circumstances for best results it would be better to arrange interviews via messaging vs the normal application process if possible? This should also save your team time. I have also found that many application processes are inefficient due to team interviews requiring resharing resume, application information via speech.
I have many years of technology work experience, have worked as a freelancer, consultant, founder, & employee in multiple company types. I can also share past work references, examples. I fully understand the problem domain due to spending lots of time analysing research papers, conducting quantitative, & qualitative research independently.


【代码迁移】任务14：Investigating Wit, Creativity, and Detectability of Large Language Models in Domain-Specific Writing Style Adaptation of Reddit's Showerthoughts

test结果输出如下：


upgrade prometrix and other dependencies

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


FileNotFoundError: [Errno 2] No such file or directory: '...\lib\site-packages\products_crawler\spider_configs\supreme.json'

[x] set include_package_data to true in setup.cfg

v0.1.3 still not work

fixed in v0.1.4


Add swagger API docs to demo project

Coverage remained the same at 97.065% when pulling 5330e0cfb190c6cab0a12364939dfe6f8180b6b9 on demo-site-swagger into 37375461df148eda5cda9ce558c3ad3b2087894b on master.


add igs-seevetal

Scool URL: http://www.igs-seevetal.de/
If you look at this page (http://www.igs-seevetal.de/index.php/kontakt) you can see that @igs-seevetal.de is used for the E-Mails.

@GameDevDummy Pull request merged. Thank you!


Google docs changed their bolding CSS from font-weight: bold; to font-weight: 700

Here's another version of this I've been running into today: Instead of inline styles, Google is now adding class names and a style block at the top of the page, but it's changing those class names on every download.
So bold text might be span.c0 or span.c1 or something else entirely. It's insane.

Figured out my issue. I was using the v2 Drive API (via Tarbell) which generates that style element in the page on each download. The v3 API gets inline styles.


How to use jest flow-types in tests

After running flow-typed install and getting package flow-typed/npm/jest_v21.x.x.js, how are we supposed to use these types? The names that flow check requires are not resolving
For example, this fails with the following messages:
Missing type annotation for TArguments AND Cannot resolve name TArguments
export const fn = jest.fn(...args: TArguments): TReturn => {
    ...
};

Here's an untyped boilerplate example of what I am having issues with:
// @flow
// fetch mock
export const fn = jest.fn(() => (url, params) => {
  console.log(params);
  console.log(url);
  return new Promise(resolve => resolve({ ok: true, status: 200 }));
});

export default jest.mock('../../src/shared/fetch', fn);

And here are the errors flow is giving me:
Error ------------------------------------------------------------------------------------------------- untitled.js:3:19

Missing type annotation for `TArguments`.

                        v-------------------------------
   3| export const fn = jest.fn(() => (url, params) => {
   4|   console.log(params);
   5|   console.log(url);
   6|   return new Promise(resolve => resolve({ ok: true, status: 200 }));
   7| });
      -^

Error ------------------------------------------------------------------------------------------------- untitled.js:3:19

Missing type annotation for `TReturn`.

                        v-------------------------------
   3| export const fn = jest.fn(() => (url, params) => {
   4|   console.log(params);
   5|   console.log(url);
   6|   return new Promise(resolve => resolve({ ok: true, status: 200 }));
   7| });
      -^

What does your code look like without the flow typings? The stuff you're trying to add typings to.

@GAntoine I updated the issue with a block of example code

If you're willing to provide a basic repo to repro, that'd be useful. :-)

same issue +1

Provide a repro repo kthxbai. 😉

I managed to reproduce it on flow's website by putting the jest library definition from the repo into the editor, and adding an exported jest.fn() at the bottom:
Try It

@spudly this happens because you need to annotate what mock function is going to return.
export const mockFn = jest.fn<$ReadOnlyArray<string>, string>();

@sobolevn,
I think that's the answer we were looking for. This can probably be closed now.

@sobolevn solution doesn't work for me
I'm getting babel parser errors: "Unexpected token"
My babel config:
"babel": {
    "presets": [
      "flow",
      [
        "env",
        {
          "targets": {
            "node": "8.10.0"
          }
        }
      ]
    ]
  },

@cortopy where did you set that config? (.babelrc?)

@mloureiro in package.json. I don't have a .babelrc

@cortopy I had the same parsing error as you when using the provided example, but was able to move the type annotations to the left-hand-side of the assignment to get a version that worked 🙂
export const mockFn: ($ReadOnlyArray<string>) => string = jest.fn();

@thejettdurham that seems to work. Thanks!!


Sending of byte data when No data (text or bitmap) selected

Describe the bug
Byte data is being sent when no data(text or byte date) is selected
To Reproduce
Click on send button without selecting anything
Expected behavior
check should be placed before emitting data.
A dialog or prompt should be shown to user to select data
Logs
 2019-04-06 12:13:03.154 19300-19300/com.nilhcem.blenamebadge I/MessagePresenter: ByteData: [77616E67000000000400000000000000,<PHONE_NUMBER>0000000000000000000000,<PHONE_NUMBER>00E304060C0D0300000000,<PHONE_NUMBER>0000000000000000000000, 001E3121033B67430D18133E7F9C082A, 9CFFFFFFFF7F003CC64260EEF3E1D88C,<PHONE_NUMBER>03060F0B0A010000000810, F8ECFEFA0AB000000000000000000000]
Screenshots

Smartphone Info:
|Device         |Nokia 6.1|
|Android Version| Android 9.0  |
Would you like to work on the issue?

yes .

That is supposed to happen. If send is clicked when no data is selected, a default bitmap appears on the device. I have a physical BLE device and have tested this on that. Please close the issue as it is not relevant.

I agree with default message (text or bitmap) shouldn't separate Test button should be placed for users (To avoid confusion) . I didn't select any data and its sending default . User should be notified .
Make Test Button for showing default message. Show user Default Bitmap will be shown

Not needed. That will make the UI more clustered. When the user presses preview without entering any data, the default bitmap is shown. That's enough indication what will be shown when send is pressed.

ok then . closing this issue


[rx-recompose-next] not working while multiple subscribers subscribed to single createEventHandler

const eventHandler$ = createEventHandler();

const subscriptionA$ = eventHandler$
  .map(x => x + 2)
  .do(x => console.log('A', x))
  .subscribe();

const subscriptionB$ = eventHandler$
  .map(x => x * 2)
  .do(x => console.log('B', x))
  .subscribe();

eventHandler$(3);

// Outputs:
// B 6

It only runs on the last subscriber, Is this an expected result?

Good catch! Fixed on on rx-recompose-next branch, will be part of next pre-release.


save input from the users and send another message

First of all I must say that the project is amazing!!
I need to send a message, then save the input that comes from the user, then send another message and again save the input. How can I do this?

hi @Kalebu , I also wondered how can we log API request or in general if I am calling an API through a library then what is a general practise , How can we log API request response.... like sqlalchemy with sqlite3 ?

Hi @jay-patel-cognoai, Are you talking about logging the hook response or heyoo methods response ?
If its hook, It already included in the hook on how to log it
    data = request.get_json()
    logging.info("Received webhook data: %s", data)

But if you're talking about specific heyoo message like send_message, they do return a json response by default so you can easily log the response like this;
>>> r = messenger.send_message('hi there', '34xxxx')
>>> print(r)

You can then save the log whenever you want whether to log file, text file, or database or Are you also suggesting we should include API Response logging by default to the library right ?

Just wanted to know do libraries ever use any kind of database for their internal functioning.

Well it depends on the design choices of a particular library, For heyoo we don't
I will mark this issue #20  as resolved


Rails upgrade 4.2.2

Upgraded Rails & JQuery in order to mitigate against the vulnerabilities:

https://groups.google.com/forum/#!topic/rubyonrails-security/bahr2JLnxvk
https://groups.google.com/forum/#!topic/ruby-security-ann/7VlB_pck3hU
https://groups.google.com/forum/#!topic/ruby-security-ann/XIZPbobuwaY

You are go for merge! :+1:


better solutions for 2148 and 2147

Moved fixupUrl to core utils and gave it a more descriptive name since it now has broader visibility.
Disabled AJAX caching globally which likely fixes other IE weirdness.

fixupUri broke the help video eventing.  See https://github.com/codecombat/codecombat/commit/92f070eccaae62dce2ac597e452933e83dd75247.
Where else does removeScheme need to be used?

How does this fix #2159?

Sorry should be 2147.
The general case where we need to strip the scheme is that we are storing a URL in the database and need to be able to use it either from HTTP or HTTPS connections.  Running through IE testing I did run into errors with cross scheme/mixed content, though which of those are from the DB and which are hard coded I cant say at this point.

Hrm, that isn't good.  So lets not make it easy to do that in other places.  How do you guys feel about disabling the AJAX caching globally?

Removing the protocol broke the video player eventing.  It's not necessarily a common problem, or related to caching.
I wouldn't disable ajax caching globally without better understanding the impact.  I also wouldn't disable it globally for non-IE browsers without a clear benefit to other browsers.  Do you know what the global effects would be, and how we'd test this change?

Looking at what this changes in chrome.  Primarily the behavior of /db/thang.type I think this is going to be a problem.  sigh


Improve MiniTimeline

Related #2503
have a threshold for when to use mini-map
There is only1 spans -> not show mini timeline

There are 2 ~ 14 spans -> mini timeline's height is 'num of spans × 5px'

There are more spans -> height is 75px

Add slider to improve UX
Before

After

This PR is WIP yet, because I need to write unit tests.

Looks like all good improvements to me from looking at the screenshots. Great work!

PS for messaging trace, there's often a long gap between producer and consumer. I always wondered if we could pinch the timeline together in cases like this...

I love the way you care so much about details <3
ons. 24. apr. 2019, 04:05 skrev Adrian Cole<EMAIL_ADDRESS>
PS for messaging trace, there's often a long gap between producer and
consumer. I always wondered if we could pinch the timeline together in
cases like this...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-zipkin/pull/2529#issuecomment-486038682,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXOYAQRB4OIGROQDQ55YADPR656JANCNFSM4HHWH46A
.

PTAL 🙇

are all the images still same?

Yes

thanks very much!


Not Finding Limelight Audio Files

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I remove or skip any mandatory* field

Checklist

[X] I'm reporting a broken site
[X] I've verified that I'm running yt-dlp version 2022.10.04 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
USA
Provide a description that is worded well enough to be understood
I periodically visit pages for learningstrategies.com to download audio and/or video such as this one: https://www.learningstrategies.com/manifestationmindfest/phase3
Attempting to use yt-dlp nets me the errors below instead of downloading the content.
From my own investigation, the audio files are usually compatible with the limelight extractor, so I manually use Chrome Devtools to find channel and media ids (the former often contains groups of the later) and use commands like yt-dlp "limelight:channel:<id>" and yt-dlp "limelight:media:<id>".  I'm able to get by with this but it's very tedious because of two quirks:

Recently, I found yt-dlp "limelight:channel:<id>" not to be working, forcing me to use individual media ids.
yt-dlp defaults to a format for live streaming video.  It's a minor inconvenience now that I know about it, but it requires me to use the arg "-f Mp3-2 / Mp3-1 / Mp3-0"

I hope I was clear enough, and thank you in advance.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vUF', 'https://www.learningstrategies.com/manifestationmindfest/phase3']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2022.10.04 [4e0511f] (win32_exe)
[debug] Python 3.8.10 (CPython 64bit) - Windows-10-10.0.19044-SP0
[debug] Checking exe version: ffmpeg -bsfs
[debug] Checking exe version: ffprobe -bsfs
[debug] exe versions: none
[debug] Optional libraries: Cryptodome-3.15.0, brotli-1.0.9, certifi-2022.09.24, mutagen-1.45.1, sqlite3-2.6.0, websockets-10.3
[debug] Proxy map: {}
[debug] Loaded 1690 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: 2022.10.04, Current version: 2022.10.04
yt-dlp is up to date (2022.10.04)
[debug] [generic] Extracting URL: https://www.learningstrategies.com/manifestationmindfest/phase3
[generic] phase3: Downloading webpage
WARNING: [generic] Falling back on generic information extractor
[generic] phase3: Extracting information
[debug] Looking for Brightcove embeds
[debug] Looking for embeds
[debug] Identified a limelight embed
[debug] Identified a limelight:channel embed
[debug] Identified a limelight:channel_list embed
[download] Downloading playlist: Manifestation Mindfest Phase 3
[generic] Playlist Manifestation Mindfest Phase 3: Downloading 3 videos of 3
[download] Downloading video 1 of 3
ERROR: 'dict' object has no attribute 'startswith'
Traceback (most recent call last):
  File "yt_dlp\YoutubeDL.py", line 1477, in wrapper
  File "yt_dlp\YoutubeDL.py", line 1876, in __process_iterable_entry
  File "yt_dlp\YoutubeDL.py", line 1609, in process_ie_result
  File "yt_dlp\utils.py", line 735, in sanitize_url
AttributeError: 'dict' object has no attribute 'startswith'

[download] Downloading video 2 of 3
ERROR: 'dict' object has no attribute 'startswith'
Traceback (most recent call last):
  File "yt_dlp\YoutubeDL.py", line 1477, in wrapper
  File "yt_dlp\YoutubeDL.py", line 1876, in __process_iterable_entry
  File "yt_dlp\YoutubeDL.py", line 1609, in process_ie_result
  File "yt_dlp\utils.py", line 735, in sanitize_url
AttributeError: 'dict' object has no attribute 'startswith'

[download] Downloading video 3 of 3
ERROR: 'dict' object has no attribute 'startswith'
Traceback (most recent call last):
  File "yt_dlp\YoutubeDL.py", line 1477, in wrapper
  File "yt_dlp\YoutubeDL.py", line 1876, in __process_iterable_entry
  File "yt_dlp\YoutubeDL.py", line 1609, in process_ie_result
  File "yt_dlp\utils.py", line 735, in sanitize_url
AttributeError: 'dict' object has no attribute 'startswith'

[download] Finished downloading playlist: Manifestation Mindfest Phase 3

The Limelight extractor is confused by the new generic arrangements for extracting embedded links and needs to be fixed. In particular its interface that is supposed to return a list of embedded URLs doesn't, which causes the error 'dict' object has no attribute 'startswith'.
yt-dl still gets an adequate result:
$ youtube-dl -v -F 'https://www.learningstrategies.com/manifestationmindfest/phase3'
[debug] System config: ['--prefer-ffmpeg']
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', '-F', 'https://www.learningstrategies.com/manifestationmindfest/phase3']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2021.06.06
[debug] Python version 3.5.2 (CPython) - Linux-4.4.0-210-generic-i686-with-Ubuntu-16.04-xenial
[debug] exe versions: avconv 4.3, avprobe 4.3, ffmpeg 4.3, ffprobe 4.3
[debug] Proxy map: {}
[generic] phase3: Requesting header
WARNING: Falling back on generic information extractor.
[generic] phase3: Downloading webpage
[generic] phase3: Extracting information
[download] Downloading playlist: Manifestation Mindfest Phase 3
[generic] playlist Manifestation Mindfest Phase 3: Collected 1 video ids (downloading 1 of them)
[download] Downloading video 1 of 1
[limelight] a4dcc1326e7e4dfda6b1cbe1bec7ca54: Downloading PlaylistService getPlaylistByMediaId JSON
[limelight] a4dcc1326e7e4dfda6b1cbe1bec7ca54: Downloading PlaylistService getMobilePlaylistByMediaId JSON
[limelight] a4dcc1326e7e4dfda6b1cbe1bec7ca54: Downloading m3u8 information
[info] Available formats for a4dcc1326e7e4dfda6b1cbe1bec7ca54:
format code           extension  resolution note
Mp3-0                 mp3        unknown
Mp3-1                 mp3        unknown
HttpLiveStreaming-64  mp4        unknown      64k , 30.0fps (best)
[download] Finished downloading playlist: Manifestation Mindfest Phase 3
$

The best format (HttpLiveStreaming-64) for the problem URL has a small blank video attached to the audio. To get the mp3 formats and avoid the AV format, use -f "[ext=mp3]" or -f "[ext!=mp4]".
For devs:

The LimelightBaseIE._extract_embed_urls() method extracts a list of entries (ie, dicts), not a list of URL strings. Its logic wasn't changed from the perhaps confusingly named 2017-era _extract_urls().
The method contains a nested function which presumably ought be reverted as below

-        def smuggle(url):
-            return smuggle_url(url, {'source_url': url})
+        def smuggle(a_url):
+            return smuggle_url(a_url, {'source_url': url})

The method is called once for each of its 3 derived classes, returning the same result each time, but only the first call is valid (for the problem URL). If the result can be handled differently according to the IE class, the method needs to be specialised to each of the derived classes, or otherwise behave differently in each case. If not, all but one of the derived classes need a dummy routine, or perhaps the routine to be set to False or None and filtered out by the generic processing.
The method might return a limelight:channelList:... URL that should be limelight:channel_list:...:

-            kind, video_id = mobj.group('kind'), mobj.group('id')
+            kind, video_id = mobj.group('kind').replace('channelList', 'channel_list'), mobj.group('id')
5. The extraction results have `video_ext` set for all formats, even the mp3 formats that only have audio; `acodec` and `vcodec` aren't set, but perhaps they're old hat.


Patient dashboard

Right! Thanks for the clarification!
From: "Adam M. Holmes"<EMAIL_ADDRESS>Reply-To: projecttacoma/bonnie<EMAIL_ADDRESS>Date: Wednesday, September 21, 2016 at 2:50 PM
To: projecttacoma/bonnie<EMAIL_ADDRESS>Cc: Lizzie DeYoung<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [projecttacoma/bonnie] Patient dashboard (#570)
@holmesie commented on this pull request.

In app/assets/javascripts/models/patient_dashboard_patient.js.coffeehttps://github.com/projecttacoma/bonnie/pull/570:

   result = 'FALSE'

 value = result

 if 'specificsRationale' of @patientResult && populationKey of @patientResult['specificsRationale']

   specific_value = @patientResult['specificsRationale'][populationKey][criteriaKey]

   if specific_value == false && value == 'TRUE'

     result = 'SPECIFICALLY FALSE'

   else if specific_value == true && value == 'FALSE'

     result = 'SPECIFICALLY TRUE'

else

 result = ''

result

@returns {String} describes if the patient is passing

patientStatus: ->

I'm not sure what you mean, status is populated using the @passes instance variable, which itself is initialized/updated using the result of this function.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/projecttacoma/bonnie/pull/570, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALCbt4nNqSFBZqUXOXuT7Iq-ao4qAhCBks5qsXyTgaJpZM4J1x2v.

Patient Dashboard has been integrated into the master branch of Bonnie. This PR was kept to maintain track of comments. It is no longer needed.


Limiting Tags field

Hey There,
I was wondering, if there is a way to limit how many tags can be added to an item?
I've looked through the code, maybe I missed something but I found no possibility to do so.
Cheers,
David

Hi @pixeleet, I saw you submitted a pull request for this, but @boutell had mentioned it needing some adjustments. Did you get a chance to update it?

To my understanding it's already merged ;)
https://github.com/punkave/apostrophe/pull/159
2015-02-21 5:02 GMT+01:00 benirose<EMAIL_ADDRESS>
Hi @pixeleet https://github.com/pixeleet, I saw you submitted a pull
request for this, but @boutell https://github.com/boutell had mentioned
it needing some adjustments. Did you get a chance to update it?
—
Reply to this email directly or view it on GitHub
https://github.com/punkave/apostrophe/issues/157#issuecomment-75354546.

Great!