[ACR] Improve az acr repository command group

Fixes https://github.com/Azure/azure-cli/issues/4057
This PR refactors/improves az acr repository command group. Existing commands should be able to run without breaking but parameter/help messages are replaced with new commands.

This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines

[x] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

Command Guidelines

[x] Each command and parameter has a meaningful description.
[x] Each new command has a test.

(see Authoring Command Modules)

View a preview at https://prompt.ws/r/Azure/azure-cli/5635
This is an experimental preview for @microsoft users.

Help messages from az acr repository delete -h
Command
    az acr repository delete: Delete a repository or image in a container registry.

Arguments
    --name -n [Required]: The name of the container registry. You can configure the default registry
                          name using `az configure --defaults acr=<registry name>`.
    --image             : The name of the image to delete. For example, 'hello-world:latest' or
                          'hello-world@sha256:abc123'.
    --password -p       : The password used to log into a container registry.
    --repository        : The name of the repository to delete. For example, 'hello-world'.
    --resource-group -g : Name of resource group. You can configure the default group using `az
                          configure --defaults group=<name>`.
    --username -u       : The username used to log into a container registry.
    --yes -y            : Do not prompt for confirmation.

Global Arguments
    --debug             : Increase logging verbosity to show all debug logs.
    --help -h           : Show this help message and exit.
    --output -o         : Output format.  Allowed values: json, jsonc, table, tsv.  Default: json.
    --query             : JMESPath query string. See http://jmespath.org/ for more information and
                          examples.
    --verbose           : Increase logging verbosity. Use --debug for full debug logs.

Examples
    Delete a repository from a container registry.
        az acr repository delete -n MyRegistry --repository hello-world

    Delete an image by tag. This deletes the manifest referenced by 'hello-world:latest', all other
    tags referencing the manifest, and any associated layer data.
        az acr repository delete -n MyRegistry --image hello-world:latest

    Delete an image by sha256 based manifest digest. This deletes all tags referencing the manifest
    and any associated layer data.
        az acr repository delete -n MyRegistry --image hello-world@sha256:abc123

Help messages from az acr repository untag -h
Command
    az acr repository untag: Untag an image in a container registry.

Arguments
    --image   [Required]: The name of the image to untag. For example, 'hello-world:latest'.
    --name -n [Required]: The name of the container registry. You can configure the default registry
                          name using `az configure --defaults acr=<registry name>`.
    --password -p       : The password used to log into a container registry.
    --resource-group -g : Name of resource group. You can configure the default group using `az
                          configure --defaults group=<name>`.
    --username -u       : The username used to log into a container registry.

Examples
    Untag an image from a repository. This does not delete the manifest referenced by the tag or any
    associated layer data.
        az acr repository untag -n MyRegistry --image hello-world:latest

/cc @SteveLas @sajayantony @mmacy

@sajayantony In reply to https://github.com/Azure/azure-cli/issues/4057#issuecomment-368154591
We have warnings when data will be deleted but no warning otherwise. The following are warnings for existing commands:
>az acr repository delete -n MyRegistry --repository python --tag latest
This command is deprecated. The new command for this operation is 'az acr repository untag --name MyRegistry --image python:latest'.

>az acr repository delete -n MyRegistry --repository python --tag latest --manifest
This command is deprecated. The new command for this operation is 'az acr repository delete --name MyRegistry --image python:latest'.
This operation will delete the manifest 'sha256:a0cfbb00e64b5700a69d5fe91669a842cc50443b317dab53c930a1b296586cdb' and all the following images: 'python:latest'.
Are you sure you want to continue? (y/n):

>az acr repository delete -n MyRegistry --repository python --manifest sha256:a0cfbb00e64b5700a69d5fe91669a842cc50443b317dab53c930a1b296586cdb
This command is deprecated. The new command for this operation is 'az acr repository delete --name MyRegistry --image python@sha256:a0cfbb00e64b5700a69d5fe91669a842cc50443b317dab53c930a1b296586cdb'.
This operation will delete the manifest 'sha256:a0cfbb00e64b5700a69d5fe91669a842cc50443b317dab53c930a1b296586cdb' and all the following images: 'python:latest'.
Are you sure you want to continue? (y/n):

LGTM.  Will wait for approvals from your stakeholders before merging.

@djyou who else should review?

@sptramer @mmacy @sajayantony Could you please take a look if they look good to you? Thanks.
Command
    az acr repository untag: Untag an image in a container registry.
        This command does not delete the manifest referenced by the tag or any associated layer
        data.

Arguments
    --image  [Required]: The name of the image to untag in the format of 'repository:tag'.
    --name -n          : The name of the container registry. You can configure the default registry
                         name using `az configure --defaults acr=<registry name>`.  Default: doyou-
                         rg.
    --password -p      : The password used to log into a container registry.
    --resource-group -g: Name of resource group. You can configure the default group using `az
                         configure --defaults group=<name>`.  Default: doyou-rg.
    --username -u      : The username used to log into a container registry.

Examples
    Untag an image from a repository.
        az acr repository untag -n MyRegistry --image hello-world:latest

Command
    az acr repository delete: Delete a repository or image in a container registry.

Arguments
    --image            : The name of the image to delete in the format of 'repository:tag' or
                         'repository@sha256'.
    --name -n          : The name of the container registry. You can configure the default registry
                         name using `az configure --defaults acr=<registry name>`.  Default: doyou-
                         rg.
    --password -p      : The password used to log into a container registry.
    --repository       : The name of the repository to delete.
    --resource-group -g: Name of resource group. You can configure the default group using `az
                         configure --defaults group=<name>`.  Default: doyou-rg.
    --username -u      : The username used to log into a container registry.
    --yes -y           : Do not prompt for confirmation.

Examples
    Delete a repository from a container registry.
        az acr repository delete -n MyRegistry --repository hello-world

    Delete an image by tag. This deletes the manifest referenced by 'hello-world:latest', all other
    tags referencing the manifest, and any associated layer data.
        az acr repository delete -n MyRegistry --image hello-world:latest

    Delete an image by sha256-based manifest digest. This deletes all tags referencing the manifest
    and any associated layer data.
        az acr repository delete -n MyRegistry --image hello-world@sha256:abc123

 az acr repository delete should have the --image argument read:
The name of the image to delete. May include a tag in the format 'name:tag' or hash in the format 'name@hash'.

It's either a tag or a sha256. hash doesn't indicate what hash it is. name doesn't indicate what name it is (registry name, repository name, etc.).

If images absolutely require a tag to be deleted, that seems weird to me. It doesn't default to :latest if no tag is provided?

I think that is reasonable since all docker rmi does this as well.
Can the confirmation output the fully qualified image?

@sptramer I am still not sure about the name:hash string but have updated to what you suggested. Please let me know if you have more comments. Thanks.

This has to be renamed as digest if it isn't already - <image@digest>https://docs.docker.com/engine/reference/commandline/images/

:+1: docs look good

@tjprescott @derekbekoe Could you please merge this? Thanks!


[BUG] Philips Hue Motion sensor outdoor SML002, On/Off not working and Occupancy acts like On/Off

Hey Guys,
Just got a Philips Hue SML002, that's the outdoor version, motion detector.
But there's more it also reports illumination, temperature, battery and occupancy.
So I paired it with Home assistant, 2021.2.3. works like a charm.
But:
The Motion detector On/Off part does not work at all. (the one with the running man as icon).
And the Occupancy part acts like the On/Off part, detects motion and resets after 10 seconds.
So I googled my findings and indeed there are others who encountered the same problems, but no solution
and the strange thing is I cant find a submitted issue, I think clearly a bug. So hereby....
My log file while connecting:
There is also a 'polling' of sorts in the log file from my light.lamp_achter_woonkamer, dont know what it means..
Oh and the Detector has IEEE: 00:17:88:01:06:48:cc:ed
[0x0000:zdo] ZDO request ZDOCmd.Mgmt_Permit_Joining_req: [60, <Bool.false: 0>]
[0x511a:11:0x0000] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=60 command_id=Command.Report_Attributes>
[0x511a:11:0x0000] ZCL request 0x000a: [[Attribute(attrid=1, value=)]]
[0x511a:11:0x0000] Attribute report received: app_version=66
[0x5719:1:0x0000] ZCL deserialize: <ZCLHeader frame_control= manufacturer=4447 tsn=57 command_id=Command.Report_Attributes>
[0x5719:1:0x0000] ZCL request 0x000a: [[Attribute(attrid=65281, value=<TypeValue type=CharacterString, value=!�(!�C!>)]]
[0x5719:1:0x0000] Attribute report received: 65281=!�(!�C!
[0x5719:1:0x0001] Voltage mV: [Min]:2820 < [RAW]:3015 < [Max]:3100, Battery Percent: 69.5
[0x1D33:1:0x0b04]: async_update
[0x810C:1:0x0b04]: async_update
[0x1d33:1:0x0b04] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=202 command_id=Command.Read_Attributes_rsp>
[0x810c:1:0x0b04] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=204 command_id=Command.Read_Attributes_rsp>
Device 0x5026 (00:17:88:01:06:48:cc:ed) joined the network
[0x5026] Requesting 'Node Descriptor'
Tries remaining: 2
[0x5026] Extending timeout for 0xce request
Device 0x5026 (00:17:88:01:06:48:cc:ed) joined the network
Skip initialization for existing device 00:17:88:01:06:48:cc:ed
Device 0x5026 (00:17:88:01:06:48:cc:ed) joined the network
Skip initialization for existing device 00:17:88:01:06:48:cc:ed
[0x5026:zdo] ZDO request ZDOCmd.Device_annce: [0x5026, 00:17:88:01:06:48:cc:ed, 128]
[0x5026] Node Descriptor: NodeDescriptor(byte1=2, byte2=64, mac_capability_flags=128, manufacturer_code=4107, maximum_buffer_size=89, maximum_incoming_transfer_size=63, server_mask=0, maximum_outgoing_transfer_size=63, descriptor_capability_field=0)
[0x5026] Discovering endpoints
Tries remaining: 3
[0x5026] Extending timeout for 0xd0 request
[0x5026] Discovered endpoints: [2, 1]
[0x5026:2] Discovering endpoint information
Tries remaining: 3
[0x5026] Extending timeout for 0xd2 request
[0x5026:2] Discovered endpoint information: SizePrefixedSimpleDescriptor(endpoint=2, profile=260, device_type=263, device_version=0, input_clusters=[0, 1, 3, 1030, 1024, 1026], output_clusters=[25])
[0x5026] Extending timeout for 0xd4 request
[0x5026:2:0x0000] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=212 command_id=Command.Read_Attributes_rsp>
[0x5026:2] Manufacturer: Philips
[0x5026:2] Model: SML002
[0x5026:1] Discovering endpoint information
Tries remaining: 3
[0x5026] Extending timeout for 0xd6 request
[0x5026:1] Discovered endpoint information: SizePrefixedSimpleDescriptor(endpoint=1, profile=49246, device_type=2128, device_version=2, input_clusters=[0], output_clusters=[0, 3, 4, 6, 8, 768, 5])
Checking quirks for Philips SML002 (00:17:88:01:06:48:cc:ed)
Considering <class 'zhaquirks.philips.sml002.PhilipsSML002'>
Found custom device replacement for 00:17:88:01:06:48:cc:ed: <class 'zhaquirks.philips.sml002.PhilipsSML002'>
device - 0x5026:00:17:88:01:06:48:cc:ed entering async_device_initialized - is_new_join: True
device - 0x5026:00:17:88:01:06:48:cc:ed has joined the ZHA zigbee network
0x5026: started configuration
0x5026:ZDO: 'async_configure' stage succeeded
[0x5026] Extending timeout for 0xd8 request
[0x5026] Extending timeout for 0xda request
[0x5026] Extending timeout for 0xdc request
[0x5026:1:0x0000]: bound 'basic' cluster: Status.SUCCESS
[0x5026:1:0x0000]: finished channel configuration
[0x5026] Extending timeout for 0xde request
[0x5026:1:0x0006]: bound 'on_off' cluster: Status.SUCCESS
[0x5026:1:0x0006]: finished channel configuration
[0x5026] Extending timeout for 0xe0 request
[0x5026:1:0x0008]: bound 'level' cluster: Status.SUCCESS
[0x5026:1:0x0008]: finished channel configuration
[0x5026] Extending timeout for 0xe2 request
[0x5026:1:0x0006]: bound 'on_off' cluster: Status.SUCCESS
[0x5026:1:0x0006]: finished channel configuration
[0x5026] Extending timeout for 0xe4 request
[0x5026:1:0x0005]: bound 'scenes' cluster: Status.SUCCESS
[0x5026:1:0x0005]: finished channel configuration
[0x5026] Extending timeout for 0xe6 request
[0x5026:zdo] ZDO request ZDOCmd.NWK_addr_req: [60:a4:23:ff:fe:0b:51:f4, 0, 0]
[0x5026:1:0x0300]: bound 'light_color' cluster: Status.SUCCESS
[0x5026:1:0x0300]: finished channel configuration
[0x5026] Extending timeout for 0xe9 request
[0x5026:1:0x0000]: 'async_configure' stage succeeded
[0x5026:1:0x0006]: 'async_configure' stage succeeded
[0x5026:1:0x0008]: 'async_configure' stage succeeded
[0x5026:1:0x0006]: 'async_configure' stage succeeded
[0x5026:1:0x0005]: 'async_configure' stage succeeded
[0x5026:1:0x0300]: 'async_configure' stage succeeded
[0x5026:2:0x0001]: bound 'power' cluster: Status.SUCCESS
[0x5026] Extending timeout for 0xeb request
[0x5026:2:0x0402]: bound 'temperature' cluster: Status.SUCCESS
[0x5026] Extending timeout for 0xed request
[0xa47b:1:0x0000] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=103 command_id=Command.Report_Attributes>
[0xa47b:1:0x0000] ZCL request 0x000a: [[Attribute(attrid=1, value=), Attribute(attrid=65506, value=)]]
[0xa47b:1:0x0000] Attribute report received: app_version=64, 65506=22
[0x5026:2:0x0406]: bound 'occupancy' cluster: Status.SUCCESS
[0x5026] Extending timeout for 0xef request
[0x5026:2:0x0001] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=235 command_id=Command.Configure_Reporting_rsp>
[0x5026:2:0x0001]: reporting 'battery_voltage' attr on 'power' cluster: 3600/10800/1: Result: '[[ConfigureReportingResponseRecord(status=140, direction=0, attrid=32)]]'
[0x5026] Extending timeout for 0xf1 request
[0x5026:2:0x0402] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=237 command_id=Command.Configure_Reporting_rsp>
[0x5026:2:0x0402]: reporting 'measured_value' attr on 'temperature' cluster: 30/900/50: Result: '[[ConfigureReportingResponseRecord(status=0)]]'
[0x5026:2:0x0402]: finished channel configuration
[0x5026] Extending timeout for 0xf3 request
[0xa5c4:1:0x0000] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=98 command_id=Command.Report_Attributes>
[0xa5c4:1:0x0000] ZCL request 0x000a: [[Attribute(attrid=1, value=)]]
[0xa5c4:1:0x0000] Attribute report received: app_version=80
[0x5026:2:0x0406] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=239 command_id=Command.Configure_Reporting_rsp>
[0x5026:2:0x0406]: reporting 'occupancy' attr on 'occupancy' cluster: 0/900/1: Result: '[[ConfigureReportingResponseRecord(status=0)]]'
[0x5026:2:0x0406]: finished channel configuration
[0x5026] Extending timeout for 0xf5 request
[0x5026:2:0x0001] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=241 command_id=Command.Configure_Reporting_rsp>
[0x5026:2:0x0001]: reporting 'battery_percentage_remaining' attr on 'power' cluster: 3600/10800/1: Result: '[[ConfigureReportingResponseRecord(status=0)]]'
[0x5026:2:0x0001]: finished channel configuration
[0x5026] Extending timeout for 0xf7 request
[0x5026:2:0x0000]: bound 'basic' cluster: Status.SUCCESS
[0x5026:2:0x0000]: finished channel configuration
[0x5026:2:0x0400]: bound 'illuminance' cluster: Status.SUCCESS
[0x5026] Extending timeout for 0xf9 request
[0x5026:2:0x0019]: bound 'ota' cluster: Status.TABLE_FULL
[0x5026:2:0x0019]: finished channel configuration
[0x5026:2:0x0400] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=249 command_id=Command.Configure_Reporting_rsp>
[0x5026:2:0x0400]: reporting 'measured_value' attr on 'illuminance' cluster: 30/900/1: Result: '[[ConfigureReportingResponseRecord(status=0)]]'
[0x5026:2:0x0400]: finished channel configuration
[0x5026:2:0x0001]: 'async_configure' stage succeeded
[0x5026:2:0x0402]: 'async_configure' stage succeeded
[0x5026:2:0x0406]: 'async_configure' stage succeeded
[0x5026:2:0x0000]: 'async_configure' stage succeeded
[0x5026:2:0x0400]: 'async_configure' stage succeeded
[0x5026:2:0x0019]: 'async_configure' stage succeeded
0x5026: completed configuration
0x5026: stored in registry: ZhaDeviceEntry(name='Philips SML002', ieee='00:17:88:01:06:48:cc:ed', last_seen=1614885852.804855)
[0x5026] Extending timeout for 0xfb request
[0x5026:2:0x0003] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=251 command_id=Command.Default_Response>
[0x5026:2:0x0003]: executed 'trigger_effect' command with args: '(2, 0)' kwargs: '{}' result: [64, <Status.UNSUP_CLUSTER_COMMAND: 129>]
0x5026: started initialization
0x5026:ZDO: 'async_initialize' stage succeeded
[0x5026:1:0x0000]: initializing channel: from_cache: False
[0x5026:1:0x0000]: finished channel configuration
[0x5026:1:0x0006]: initializing channel: from_cache: False
[0x5026] Extending timeout for 0xfd request
[0x5026:1:0x0008]: initializing channel: from_cache: False
[0x5026:1:0x0008]: finished channel configuration
[0x5026:1:0x0006]: initializing channel: from_cache: False
[0x5026:1:0x0006]: finished channel configuration
[0x5026:1:0x0005]: initializing channel: from_cache: False
[0x5026:1:0x0005]: finished channel configuration
[0x5026:1:0x0300]: initializing channel: from_cache: False
[0x5026:1:0x0300]: finished channel configuration
[0x5026:2:0x0001]: initializing channel: from_cache: False
[0x5026] Extending timeout for 0xff request
[0x5026:2:0x0402]: initializing channel: from_cache: False
[0x5026] Extending timeout for 0x01 request
[0x5026:2:0x0406] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=0 command_id=Command.Report_Attributes>
[0x5026:2:0x0406] ZCL request 0x000a: [[Attribute(attrid=0, value=)]]
[0x5026:2:0x0406] Attribute report received: occupancy=0
[0x5026:1:0x0006] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=253 command_id=Command.Read_Attributes_rsp>
[0x5026:1:0x0006]: finished channel configuration
[0x5026:2:0x0406]: initializing channel: from_cache: False
[0x5026] Extending timeout for 0x04 request
[0x5026:1:0x0000]: 'async_initialize' stage succeeded
[0x5026:1:0x0006]: 'async_initialize' stage succeeded
[0x5026:1:0x0008]: 'async_initialize' stage succeeded
[0x5026:1:0x0006]: 'async_initialize' stage succeeded
[0x5026:1:0x0005]: 'async_initialize' stage succeeded
[0x5026:1:0x0300]: 'async_initialize' stage succeeded
[0x5026:2:0x0001] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=255 command_id=Command.Read_Attributes_rsp>
[0x5026] Extending timeout for 0x06 request
[0x5026:2:0x0001] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=1 command_id=Command.Report_Attributes>
[0x5026:2:0x0001] ZCL request 0x000a: [[Attribute(attrid=33, value=)]]
[0x5026:2:0x0001] Attribute report received: battery_percentage_remaining=200
[0x5026:2:0x0402] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=1 command_id=Command.Read_Attributes_rsp>
[0x5026:2:0x0402]: finished channel configuration
[0x5026:2:0x0000]: initializing channel: from_cache: False
[0x5026:2:0x0000]: finished channel configuration
[0x5026:2:0x0400]: initializing channel: from_cache: False
[0x5026] Extending timeout for 0x08 request
[0x5026:2:0x0406] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=4 command_id=Command.Read_Attributes_rsp>
[0x5026:2:0x0406]: finished channel configuration
[0x5026:2:0x0019]: initializing channel: from_cache: False
[0x5026:2:0x0019]: finished channel configuration
[0x5026:2:0x0400] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=2 command_id=Command.Report_Attributes>
[0x5026:2:0x0400] ZCL request 0x000a: [[Attribute(attrid=0, value=)]]
[0x5026:2:0x0400] Attribute report received: measured_value=21598
[0x5026:2:0x0001] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=6 command_id=Command.Read_Attributes_rsp>
[0x5026:2:0x0001]: finished channel configuration
[0x5026:2:0x0400] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=8 command_id=Command.Read_Attributes_rsp>
[0x5026:2:0x0400]: finished channel configuration
[0x5026:2:0x0001]: 'async_initialize' stage succeeded
[0x5026:2:0x0402]: 'async_initialize' stage succeeded
[0x5026:2:0x0406]: 'async_initialize' stage succeeded
[0x5026:2:0x0000]: 'async_initialize' stage succeeded
[0x5026:2:0x0400]: 'async_initialize' stage succeeded
[0x5026:2:0x0019]: 'async_initialize' stage succeeded
0x5026: power source: Battery or Unknown
0x5026: completed initialization
[0x5026:2:0x0402] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=3 command_id=Command.Report_Attributes>
[0x5026:2:0x0402] ZCL request 0x000a: [[Attribute(attrid=0, value=)]]
[0x5026:2:0x0402] Attribute report received: measured_value=2179
[0x5026:2:0x0406] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=4 command_id=Command.Report_Attributes>
[0x5026:2:0x0406] ZCL request 0x000a: [[Attribute(attrid=0, value=)]]
[0x5026:2:0x0406] Attribute report received: occupancy=1
[0x1D33:1:0x0b04]: async_update
[0x810C:1:0x0b04]: async_update
[0x1d33:1:0x0b04] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=13 command_id=Command.Read_Attributes_rsp>
[0x810c:1:0x0b04] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=15 command_id=Command.Read_Attributes_rsp>
[0x12f2:1:0x0000] ZCL deserialize: <ZCLHeader frame_control= manufacturer=4447 tsn=76 command_id=Command.Report_Attributes>
[0x12f2:1:0x0000] ZCL request 0x000a: [[Attribute(attrid=65281, value=<TypeValue type=CharacterString, value=!�(!�C!S>)]]
[0x12f2:1:0x0000] Attribute report received: 65281=!�(!�C!S
[0x12f2:1:0x0001] Voltage mV: [Min]:2820 < [RAW]:3015 < [Max]:3100, Battery Percent: 69.5
light.lamp_achter_woonkamer: polling current state
[0xb2a8:1:0x0006] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=17 command_id=Command.Read_Attributes_rsp>
[0xb2a8:1:0x0008] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=19 command_id=Command.Read_Attributes_rsp>
[0xB2A8:1:0x0008]: received attribute: 0 update with value: 77
[0xb2a8:1:0x0300] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=21 command_id=Command.Read_Attributes_rsp>
[0x5026:2:0x0406] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=5 command_id=Command.Report_Attributes>
[0x5026:2:0x0406] ZCL request 0x000a: [[Attribute(attrid=0, value=)]]
[0x5026:2:0x0406] Attribute report received: occupancy=0
[0x5026:2:0x0400] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=6 command_id=Command.Report_Attributes>
[0x5026:2:0x0400] ZCL request 0x000a: [[Attribute(attrid=0, value=)]]
[0x5026:2:0x0400] Attribute report received: measured_value=18293
[0xd9a3:1:0x0000] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=66 command_id=Command.Report_Attributes>
[0xd9a3:1:0x0000] ZCL request 0x000a: [[Attribute(attrid=1, value=), Attribute(attrid=65506, value=)]]
[0xd9a3:1:0x0000] Attribute report received: app_version=64, 65506=22
[0x5026:2:0x0400] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=7 command_id=Command.Report_Attributes>
[0x5026:2:0x0400] ZCL request 0x000a: [[Attribute(attrid=0, value=)]]
[0x5026:2:0x0400] Attribute report received: measured_value=18293
[0x23d0:1:0x0000] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=77 command_id=Command.Report_Attributes>
[0x23d0:1:0x0000] ZCL request 0x000a: [[Attribute(attrid=1, value=)]]
[0x23d0:1:0x0000] Attribute report received: app_version=80
[0xafd5:11:0x0000] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=91 command_id=Command.Report_Attributes>
[0xafd5:11:0x0000] ZCL request 0x000a: [[Attribute(attrid=1, value=)]]
[0xafd5:11:0x0000] Attribute report received: app_version=66
[0x1D33:1:0x0b04]: async_update
[0x810C:1:0x0b04]: async_update
[0x1d33:1:0x0b04] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=25 command_id=Command.Read_Attributes_rsp>
[0x810c:1:0x0b04] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=27 command_id=Command.Read_Attributes_rsp>
[0xb2a8:1:0x0000] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=29 command_id=Command.Report_Attributes>
[0xb2a8:1:0x0000] ZCL request 0x000a: [[Attribute(attrid=1, value=)]]
[0xb2a8:1:0x0000] Attribute report received: app_version=80
[0x5026:2:0x0406] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=8 command_id=Command.Report_Attributes>
[0x5026:2:0x0406] ZCL request 0x000a: [[Attribute(attrid=0, value=)]]
[0x5026:2:0x0406] Attribute report received: occupancy=1
[0x5026:2:0x0400] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=9 command_id=Command.Report_Attributes>
[0x5026:2:0x0400] ZCL request 0x000a: [[Attribute(attrid=0, value=)]]
[0x5026:2:0x0400] Attribute report received: measured_value=20685
[0x5026:2:0x0406] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=10 command_id=Command.Report_Attributes>
[0x5026:2:0x0406] ZCL request 0x000a: [[Attribute(attrid=0, value=)]]
[0x5026:2:0x0406] Attribute report received: occupancy=0
[0x1D33:1:0x0b04]: async_update
[0x810C:1:0x0b04]: async_update
[0x1d33:1:0x0b04] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=32 command_id=Command.Read_Attributes_rsp>
[0x810c:1:0x0b04] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=34 command_id=Command.Read_Attributes_rsp>
[0xcbff:1:0x0000] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=19 command_id=Command.Report_Attributes>
[0xcbff:1:0x0000] ZCL request 0x000a: [[Attribute(attrid=1, value=)]]
[0xcbff:1:0x0000] Attribute report received: app_version=80
and the device signature:
{
"node_descriptor": "NodeDescriptor(byte1=2, byte2=64, mac_capability_flags=128, manufacturer_code=4107, maximum_buffer_size=89, maximum_incoming_transfer_size=63, server_mask=0, maximum_outgoing_transfer_size=63, descriptor_capability_field=0)",
"endpoints": {
"1": {
"profile_id": 49246,
"device_type": "0x0850",
"in_clusters": [
"0x0000"
],
"out_clusters": [
"0x0000",
"0x0003",
"0x0004",
"0x0005",
"0x0006",
"0x0008",
"0x0300"
]
},
"2": {
"profile_id": 260,
"device_type": "0x0107",
"in_clusters": [
"0x0000",
"0x0001",
"0x0003",
"0x0400",
"0x0402",
"0x0406"
],
"out_clusters": [
"0x0019"
]
}
},
"manufacturer": "Philips",
"model": "SML002",
"class": "zhaquirks.philips.sml002.PhilipsSML002"
}
Regards
Frank

on_off is not a real entity, should be disabled. it is a client cluster so at best it might generate a zha_event, although I don't know if anyone have tried. I guess the idea was to bind the on/off cluster directly to a light and control it. Same as ikea motion sensors.
Occupancy does act as on/off, it is either occupied or not.

Hello Adminiuga,
I understand, but I have also Aqara motion sensors, the 'on/off' function is defined as motion detected, (the run icon) resets after 1 minute. and also the occupancy is triggered and resets after 10 minutes (the house icon). So I expected The philips would act the same. and yes tried the zha_event and I got nothing..
So not a bug, but by design ?

One IKEA motion sensor is in Zigbee one "on/off controller" that using cluster 0x0006 and sending one "on with off XX seconds" (time depends of the setting inn the device and is in the "payload" of the command) to one group of lights. ZHA is reading the device type and making the "motion".
Aqara is one occupation sensor sending attribute occupation or no occupation on one cluster (No standard but zigbee is using  0x0406 (Occupancy) for it but Xiaomi) and cant controlling lights.
Some "creative persons" have making one virtual On/Off cluster that is not working to steering light then the coordinator and host system is off line = "bad magic".
The Philips HUE have 2 endpoints one for lights with clusters one on/off =x0006 and one for HA eith cluster 0x0406 (Occupancy) so in HA you is getting one motion and one occupancy = wot clusters the sensor is having and HA is using them.
The philips hue On/Off cluster need being bonded o one group for sending the on/off command and your coordinator need being member of that group.
You shall not triggering your automation on both only one of the functions.
If you dont like have both you can hiding it in HA.

I see the same clusters with the indoor SML001 sensor.
Is there somewhere this could be documented? As is, it's a bit of a confusing experience to have a cluster that doesn't seem to activate at all. Otherwise, I think this can be closed.

Me too on the outdoor sensor. Probably going to just connect it back to hue rather than diy setup

i have this issue to on SML001

please let me know if there are any logs or information needed to make progress

One IKEA motion sensor is in Zigbee one "on/off controller" that using cluster 0x0006 and sending one "on with off XX seconds" (time depends of the setting inn the device and is in the "payload" of the command) to one group of lights. ZHA is reading the device type and making the "motion".
Aqara is one occupation sensor sending attribute occupation or no occupation on one cluster (No standard but zigbee is using 0x0406 (Occupancy) for it but Xiaomi) and cant controlling lights. Some "creative persons" have making one virtual On/Off cluster that is not working to steering light then the coordinator and host system is off line = "bad magic".
The Philips HUE have 2 endpoints one for lights with clusters one on/off =x0006 and one for HA eith cluster 0x0406 (Occupancy) so in HA you is getting one motion and one occupancy = wot clusters the sensor is having and HA is using them. The philips hue On/Off cluster need being bonded o one group for sending the on/off command and your coordinator need being member of that group.
You shall not triggering your automation on both only one of the functions. If you dont like have both you can hiding it in HA.

I think there might be a solution here, but the broken english is breaking my brain.
i dont understand.
i cant find any documentation to help either.

After randomly clicking things...
I think i fixed it or at least got it working better.
Go to Device Page in HA.
Manage Clusters
Select Cluster : OnOff
Select Cluster Attribute : off_wait_time
Enter Value : 1
Click "SET ZIGBEE ATTRIBUTE"
now the motion sensor (on_off)  resets to OFF after 1 minute.

battery still shows 100%  (its not full)  batteries are old.
this is not perfect fix. im not smart enough to fix this myself.

workaround stopped working. deleted post

The on_off sensor should be disabled:

Then, the occupancy binary sensor can/should be changed to "Show as: Motion":

If you want to change the timeout for the occupancy/motion sensor, go to "Manage Clusters", select the OccupancyCluster, and select pir_o_to_u_delay (id: 0x0010) for the attribute.
Then click the "Get Zigbee attribute" button and wave in front of the sensor (to make it wake up) and see the current occupancy/motion timeout. It should be set to 0 by default.
A value equal or less than 10 is the default "10 seconds timeout" these sensors have.
You can enter another number in that field and then click "Set Zigbee attribute" and wave in front of the sensor again (make sure to leave the "Manufacturer Code Override" field empty).
If you set it to 20 for example, you have a 20 seconds timeout.

The on_off sensor should be disabled:
Then, the occupancy binary sensor can/should be changed to "Show as: Motion":
If you want to change the timeout for the occupancy/motion sensor, go to "Manage Clusters", select the OccupancyCluster, and select pir_o_to_u_delay (id: 0x0010) for the attribute. Then click the "Get Zigbee attribute" button and wave in front of the sensor (to make it wake up) and see the current occupancy/motion timeout. It should be set to 0 by default. A value equal or less than 10 is the default "10 seconds timeout" these sensors have. You can enter another number in that field and then click "Set Zigbee attribute" and wave in front of the sensor again (make sure to leave the "Manufacturer Code Override" field empty). If you set it to 20 for example, you have a 20 seconds timeout.

Thanks for the pretty pictures but i would prefer the code get fixed rather than a workaround.
Plus...
Occupancy does nothing, even after setting it up with your instructions.
does not change with motion, ever.  ive paired 3 motion sensors yesterday dozens of times.
just did it again using your instructions.  never changes.
On_off DID detect motion but took 5 minutes to reset. was unable to change the cluster value for it
5 min reset on this sensor, with its location, is not useful.
Illuminance reads wrong.  78 lux, if paired while face down in the carpet. 26 lux face up! never changes
battery reads wrong.  says 100%. its actually 29% according to the hue hub.
temp doesnt change
this device handler is broken.
ive moved my hue motion sensors back to the hue hub, they work better with home assistant than this
and they work better on the hue hub than the smartthings hub they were connected to before yesterday.
hue hub does local communication with home assistant too so. screw it.  progress.  they operate local now.
again,  i would prefer the code get fixed than ME making janky changes to have it work "good enough"

The on_off sensor should be disabled:
Then, the occupancy binary sensor can/should be changed to "Show as: Motion":
If you want to change the timeout for the occupancy/motion sensor, go to "Manage Clusters", select the OccupancyCluster, and select pir_o_to_u_delay (id: 0x0010) for the attribute. Then click the "Get Zigbee attribute" button and wave in front of the sensor (to make it wake up) and see the current occupancy/motion timeout. It should be set to 0 by default. A value equal or less than 10 is the default "10 seconds timeout" these sensors have. You can enter another number in that field and then click "Set Zigbee attribute" and wave in front of the sensor again (make sure to leave the "Manufacturer Code Override" field empty). If you set it to 20 for example, you have a 20 seconds timeout.

Thanks for the pretty pictures but i would prefer the code get fixed rather than a workaround.
Plus... Occupancy does nothing, even after setting it up with your instructions. does not change with motion, ever. ive paired 3 motion sensors yesterday dozens of times. just did it again using your instructions. never changes.
On_off DID detect motion but took 5 minutes to reset. was unable to change the cluster value for it 5 min reset on this sensor, with its location, is not useful. Illuminance reads wrong. 78 lux, if paired while face down in the carpet. 26 lux face up! never changes battery reads wrong. says 100%. its actually 29% according to the hue hub. temp doesnt change
this device handler is broken.
ive moved my hue motion sensors back to the hue hub, they work better with home assistant than this and they work better on the hue hub than the smartthings hub they were connected to before yesterday. hue hub does local communication with home assistant too so. screw it. progress. they operate local now.
again, i would prefer the code get fixed than ME making janky changes to have it work "good enough"

I understand being frustrated but let’s try not to blast the folks that spend their free time trying to help you.

im not frustrated.
ive fixed my issue by going to the hub.
im not good with words.  i dont know how to say the things above "nicer"
im not even sure what ISNT nice above to make you say that.
words are not my thing.  im confused now

Online stuff in all caps is interpreted as yelling… just FYI here is an article: https://www.cnn.com/2018/07/23/us/all-caps-typography-history-tweets-trnd/index.html
And the last paragraph wasn’t necessary in general. Not the end of the world but we try to stay cordial in general.

Online stuff in all caps is interpreted as yelling… just FYI here is an article: https://www.cnn.com/2018/07/23/us/all-caps-typography-history-tweets-trnd/index.html
And the last paragraph wasn’t necessary in general. Not the end of the world but we try to stay cordial in general.

are you effing serious?  it WAS the caps?
i was trying to be funny.
im out.  unsub. i cant handle people that cant hand CAPITOL LETTERS.


Remove OCS CPU telemetry metric rules

The feature of gathering metrics for OCS telemetry is dropped due to better
alternatives available to achieve the same. Thus, reverting the addition of rules.
This PR needs to be backported to the 4.7 branches, as the rules will be unrequired there and will consume Prometheus bandwidth if not removed.
Signed-off-by: Anmol Sachan<EMAIL_ADDRESS>

/retest

/retest

/cherrypick release-4.7

/cherrypick release-4.7

This will need a BZ to be backported to 4.7.

This will need a BZ to be backported to 4.7.


List images inside a Docker Registry v2

The frontend shall list images inside a repository stored in a Docker Registry v2.

:+1: I need it

+1, Does it actually work ? I can't make this ui work and I'm using the registry:2 image

@catuss-a This is a planned feature, so it is not working right now.

@kwk Yeah I figured it out on another issue, thanks for the feedback!

distribution/registry:master has an /v2/_catalog end point returning a json list of all repositories.
https://github.com/docker/distribution/blob/master/docs/spec/api.md#listing-repositories

@so0k Yes, I know it has this but thank you for coming here and posting.

+1

+1

+1

+1

+1

@kwk could you outline what needs to be done to make d-r-f v2 aware?

@goern We were using v1 in production for a long time and so I could only spend my time on v1. Now that v2 is here to stay, and so many people are demanding support for it I can finally confirm that I'm working on support for v2 actively. So rather than sketching out the details what needs to be done, expect something in the near future.

even better :) thx for that!

Looking forward to the v2 update !

+1

See ef70220d0b79d4d3382718b0c6fb0725ee9b5f83 for a basic implementation. More to come

Is the fact that this has yet to be implemented the reason why I'm getting redirected to the homepage whenever I click on a repository at the moment?

@Herrad No, but you should take a look at the example_setup folder to see a basic setup if you have any troubles. Also, notice that currently the only scheme supported is the one of namespace/repo while just repois not supported ATM.

That sounds like my problem. Thanks a lot for getting back to me.

+1

+1

+1

By now we can list images inside a V2 registry. We don't support images without a namespace yet, but there's a PR for this if I'm not mistaken.


Can't run script from build phases

Hi, I'm not specialist in bash and can't run swiftgen script:

I've installed swiftgen with cocoapods
Then I pasted the following script in build phase:

if which swiftgen >/dev/null; then
  swiftgen storyboards "$PROJECT_DIR/my_project_name" --output "$PROJECT_DIR/Constants/Storyboards.swift"
  swiftgen images "$PROJECT_DIR/my_project_name" --output "$PROJECT_DIR/Constants/Images.swift"
else
  echo "warning: SwiftGen not installed, download it from https://github.com/AliSoftware/SwiftGen"
fi

I received error:warning: SwiftGen not installed, download it from https://github.com/AliSoftware/SwiftGen

As I understand, I should add somewhere root path to swiftgen $PODS_ROOT/SwiftGen/bin/swiftgen ?
Could you help me, please, what am I doing worng? See my screenshots to get the full picture:
pic1
pic2
pic3

As I understand, I should add somewhere root path to swiftgen $PODS_ROOT/SwiftGen/bin/swiftgen?

That's exactly it.

@AliSoftware where is the place, please?

Instead of swiftgen whwn invoking each command,  so that it knows where to find the binary .

if which swiftgen >/dev/null; then
"$PODS_ROOT/SwiftGen/bin/swiftgen" storyboards "$PROJECT_DIR/airportla" --output "$PROJECT_DIR/Constants/Storyboards.swift"
"$PODS_ROOT/SwiftGen/bin/swiftgen" images "$PROJECT_DIR/airportla" --output "$PROJECT_DIR/Constants/Images.swift"
else
echo "warning: SwiftGen not installed, download it from https://github.com/AliSoftware/SwiftGen"
fi

You should probably remove the if which too (and the else and fi) to only keep the invocation lines. The purpose of that if which swiftgen test in s to check if the binary named swftgen is installed system-wide and warn if it isn't installed but in the context in f a CocoaPods installation by design it's not installed system-wide but local to your project so that test is useless.

Thanks a lot! It works :+1:

Next time please ask those kind of help on StackOverflow, the GitHub issue tracker is for actual bugs in SwiftGen, not for a helpdesk :wink:


[TOPIC-GPIO]  gpio: Update rv32m1 gpio driver to use new gpio api

Updates the rv32m1 gpio driver and all associated boards to use new
device tree compatible gpio configuration flags. Implements new port
get/set/clear/toggle and pin_interrupt_configure functions recently
added to the gpio api.
Assumes the gpio api layer handles translating logical flags to physical
flags.
Stops quietly reconfiguring pinmuxes to gpio mode. The pinmux must now
be configured explicitly in the board's pinmux.c or in the application.
Tested with:

samples/basic/blinky
samples/basic/button
tests/drivers/gpio/gpio_api_1pin

On boards:

rv32m1_vega_ri5cy

Passes most, but not all of the 2-pin test.

@MaureenHelm
The topic branch has been rebased. Could you please rebase this PR against it?

@pabigot and @mnkp from the API meeting: @MaureenHelm would like to merge this as-is and follow-up as described here. Could you approve?


[dataprotection] Add support for MUA for CMK operations

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command

az dataprotection backup-vault update ... --cmk-*
General Guidelines

[x] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[x] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[x] My extension version conforms to the Extension version schema

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

dataprotection

/azp run


Using metal and n_gpu_layers produces no tokens

I'm running the example script with a few different models:
use llama_cpp_rs::{
    options::{ModelOptions, PredictOptions},
    LLama,
};

pub fn llama_predict() -> Result<String, anyhow::Error> {

    // metal seems to give really bad results
    let model_options = ModelOptions {
          //n_gpu_layers: 1,
        ..Default::default()
    };

    // let model_options = ModelOptions::default();

    let llama = LLama::new(
        "models/mistral-7b-instruct-v0.1.Q4_0.gguf".into(),
        &model_options,
    )
    .unwrap();

    let predict_options = PredictOptions {
        //top_k: 20,
        // top_p: 0.1,
        // f16_kv: true,

        token_callback: Some(Box::new(|token| {
            println!("token: {}", token);
            true
        })),
        ..Default::default()
    };

    // TODO: get this working on master. Metal support is flakey.
    let response = llama
        .predict(
            "what are the national animals of india".into(),
             predict_options,
        )
        .unwrap();
    println!("Response: {}", response);
    Ok(response)
}

#[cfg(test)]
mod tests {
    use super::*;
    #[test]
    fn test_llama_cpp_rs() -> Result<(), anyhow::Error> {
        let response = llama_predict()?;
        println!("Response: {}", response);
        assert!(!response.is_empty());
        Ok(())
    }
}

When not using metal (not using n_gpu_layers) the models generate tokens ex:
token: ind
token: ian
token:  national
token:  animal
token:  is
token:  t
token: iger
token:
Response: indian national animal is tiger
Response: indian national animal is tiger

When I use n_gpu_layers it does not generate tokens, ex:
llama_new_context_with_model: n_ctx      = 512
llama_new_context_with_model: freq_base  = 10000.0
llama_new_context_with_model: freq_scale = 1
llama_new_context_with_model: kv self size  =   64.00 MiB
llama_build_graph: non-view tensors processed: 740/740
llama_new_context_with_model: compute buffer total size = 76.07 MiB
llama_new_context_with_model: max tensor size =   102.54 MiB
count 0
token:
token:
token:
token:
...
Response:
Response:

Is this a known behavior?

Is llama.cpp actually using Metal? I tried this and noticed (only after enabling some debug logging) that in fact the file ggml-metal.metal could not be found (it needs to be placed in the current working directory). After this the basic example works just fine for me (and actually uses the GPU) with a Mixtral GGUF model.

I copied over the necessary metal files, otherwise I would get an error. After copying the files I encountered the no generated tokens issue.

Is llama.cpp actually using Metal? I tried this and noticed (only after enabling some debug logging) that in fact the file ggml-metal.metal could not be found (it needs to be placed in the current working directory). After this the basic example works just fine for me (and actually uses the GPU) with a Mixtral GGUF model.

AFAIK it does: https://github.com/ggerganov/llama.cpp?tab=readme-ov-file#metal-build

llama-cpp-python requires the user to specify CMAKE_ARGS when during pip install: https://llama-cpp-python.readthedocs.io/en/latest/install/macos/
Do users need to do something similar during cargo install for this crate?

Reading through here, it seems like llama.cpp needs to be built with specific flags in order for metal support to work: https://github.com/ggerganov/llama.cpp/pull/1642


[11.x] Add  --only to stub publish command

it adds --only option to stub:publish command
user can pass a list of comma-separated categories

cast
class
console
enum
event
job
listener
mail
notification
model
observer
policy
provider
request
resource
rule
scope
test
trait
view
factory
seeder
migration
controller
middleware

Example
php artisan stub:publish --only=model,controller

if --only was given no value then it will be ignored and all stubs will be published
Would need help with
Where to place the categories? should it be in the option description for example?

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


stack overrides the mintty-0.1.3 default requirement for Win32-2.13.1, causing build errors

On Windows, ansi-terminal depends on package mintty to detect MinTTY terminals. The current version of mintty (version 0.1.3), by default, depends on Win32-2.13.1 or greater (mintty flag Win32-2-13-1 is set by default).
Win32 is one of the libraries that ships with GHC. GHC 8.10.7 ships with Win32-<IP_ADDRESS> and GHC 9.0.1 ships with Win32-<IP_ADDRESS>.
On Stackage, snapshots lts-18.17 (GHC 8.10.7) and nightly-2021-11-19 (GHC 9.0.1) include versions of Win32 before version 2.13.1. The stack tool assumes that it is the snapshot version that is required and the .cabal file is mistaken, reporting:
WARNING: Ignoring mintty's bounds on Win32 (>=2.13.1); using Win32-<IP_ADDRESS>.
Reason: trusting snapshot over cabal file dependency information.

Ignoring mintty's bounds on Win32 causes stack build to fail with errors like:
mintty       > [1 of 1] Compiling System.Console.MinTTY
mintty       >
mintty       > src\System\Console\MinTTY.hs:31:1: error:
mintty       >     Could not find module `System.Console.MinTTY.Win32'
mintty       >     Use -v (or `:set -v` in ghci) to see a list of the files searched for.
mintty       >    |
mintty       > 31 | import qualified System.Console.MinTTY.Win32 as Win32 (isMinTTY, isMinTTYHandle)
mintty       >    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
mintty       >

The alternative solutions are:

Specify a version of Win32 that is 2.13.1 or greater as an extra-dep in the relevant stack.yaml. This causes stack to assume that the cabal file dependency is to be trusted.
Specify a version of mintty before 0.1.3 in the relevant .cabal file. However, mintty-0.1.3 was released to fix a bug that would make isMinTTY incorrectly return False on recent versions of MinTTY. Specifiyng mintty < 0.1.3 will prompt stack to suggest an extra-dep.
Unset the mintty flag Win32-2-13-1. This will cause mintty to depend on versions of Win32 before 2.13.1.

See also discussion in #114.

Here are the related upstream issues:
https://github.com/RyanGlScott/mintty/issues/4
https://github.com/commercialhaskell/stackage/pull/6304
So I would expect it to work on nightly-2021-11-19; are you saying it doesn't?

My mistake - I meant to refer to nightly-2021-11-15 (not -19) (now corrected). I see that this is now fixed in nightly-2021-11-19.

It seems like the problem crept back:

https://github.com/commercialhaskell/stack/issues/6111
https://github.com/commercialhaskell/stackage/pull/6962


fix: ci xcode version needs to be updated

Overview

Fixes #
Checklist
My PR contains...

[ ] No code changes (changes to documentation, CI, metadata, etc.)
[ ] Bug fixes (non-breaking change which fixes an issue)
[ ] Improvements (misc. changes to existing features)
[ ] Features (non-breaking change which adds functionality)

My changes...

[ ] are breaking changes
[ ] are not breaking changes
[ ] If yes to above: I have updated the documentation accordingly

Documentation

[ ] My changes do not require a change to the project documentation
[ ] My changes require a change to the project documentation
[ ] If yes to above: I have updated the documentation accordingly

Tests

[ ] My changes can not or do not need to be tested
[ ] My changes can and should be tested by unit and/or integration tests
[ ] If yes to above: I have added tests to cover my changes
[ ] If yes to above: I have taken care to cover edge cases in my tests

Code Coverage

Total Project Coverage
92.53%
:white_check_mark:

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

v1.2.7
GitHub release

Your semantic-release bot :package::rocket:


chore(docker-compose): commented some code

:tada: This PR is included in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Illegal instruction (core dumped)

When I try to render the video by your docker image, it gave me this error
[in#1 @ 0x55d6426a5400] Error opening input: Invalid data found when processing input
Error opening input file pipe:.
Error opening input files: Invalid data found when processing input
Illegal instruction (core dumped)

Use the default config
    os.system(
        f"vspipe -c y4m inference_batch.py --arg source='{f}' - | ffmpeg -y -i '{f}' -thread_queue_size 100 -i pipe: -map 1 -map 0 -map -0:v -max_interleave_delta 0 -scodec copy -crf 10 -preset slow '{mux_path}'"
    )

Only updated the engine path, and the code doesn't execute this far, it looks failed at clip = core.ffms2.Source(source=video_path, cache=False)
    clip = core.trt.Model(
        clip,
        engine_path="/workspace/tensorrt/sudo_RealESRGAN2x_Dropout_3.799.042_opset16_fp16.engine",
        # tilesize=[854, 480],
        overlap=[0, 0],
        num_streams=4,
    )

Here is the complete log.
root@07db24560f0e:/workspace/tensorrt# python main.py
Processing /workspace/tensorrt/input/test2.mp4
ffmpeg version N-112456-g90d327d607 Copyright (c) 2000-2023 the FFmpeg developers
  built with gcc 13.2.1 (GCC) 20230801
  configuration: --extra-cflags='-fopenmp -lcrypto -lz -ldl -static-libgcc -I/opt/cuda/include' --extra-cxxflags='-fopenmp -lcrypto -lz -ldl -static-libgcc' --extra-ldflags='-fopenmp -lcrypto -lz -ldl -static-libgcc -L/opt/cuda/lib64' --extra-libs='-lstdc++ -lcrypto -lz -ldl -static-libgcc' --pkg-config-flags=--static --toolchain=hardened --disable-debug --disable-shared --disable-ffplay --enable-static --enable-gpl --enable-gray --enable-nonfree --enable-openssl --enable-iconv --enable-libxml2 --enable-libmp3lame --enable-libfdk-aac --enable-libvorbis --enable-libopus --enable-libtheora --enable-libvpx --enable-libx264 --enable-libx265 --enable-libwebp --enable-libspeex --enable-libaom --enable-libvidstab --enable-libkvazaar --enable-libfreetype --enable-fontconfig --enable-libfribidi --enable-libass --enable-libsoxr --enable-libopenjpeg --enable-libdav1d --enable-librav1e --enable-libsrt --enable-libsvtav1 --enable-libdavs2 --enable-libxavs2 --enable-libvmaf --enable-cuda-nvcc --enable-vapoursynth --enable-libopenh264 --enable-optimizations --enable-cuda-llvm --enable-nvdec --enable-nvenc --enable-cuvid --enable-cuda --enable-pthreads --enable-runtime-cpudetect --enable-lto
  libavutil      58. 27.100 / 58. 27.100
  libavcodec     60. 30.102 / 60. 30.102
  libavformat    60. 15.100 / 60. 15.100
  libavdevice    60.  2.101 / 60.  2.101
  libavfilter     9. 11.100 /  9. 11.100
  libswscale      7.  4.100 /  7.  4.100
  libswresample   4. 11.100 /  4. 11.100
  libpostproc    57.  2.100 / 57.  2.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/workspace/tensorrt/input/test2.mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 512
    compatible_brands: isomiso2avc1mp41
    encoder         : Lavf58.45.100
  Duration: 00:00:09.98, start: 0.000000, bitrate: 28709 kb/s
  Stream #0:0[0x1](und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 1920x1080, 28521 kb/s, 59.94 fps, 59.94 tbr, 979001.00 tbn (default)
    Metadata:
      handler_name    : VideoHandler
      vendor_id       : [0][0][0][0]
  Stream #0:1[0x2](eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 317 kb/s (default)
    Metadata:
      handler_name    : #Mainconcept MP4 Sound Media Handler
      vendor_id       : [0][0][0][0]

[in#1 @ 0x55d6426a5400] Error opening input: Invalid data found when processing input
Error opening input file pipe:.
Error opening input files: Invalid data found when processing input
Illegal instruction (core dumped)

Just wanna mention it is prolly not on ur side i have the Same without the core dumped msg, It is most likely an issue on how the docker image was compiled. I tried complying it on my own but it errors so it might be outdated.

This error message suggests that you use an outdated cpu with not all instruction sets needed. Rebuild the image from scratch with DOCKER_BUILDKIT=1 docker build --no-cache -t styler00dollar/vsgan_tensorrt:latest .  instead of downloading it and it will most likely resolve cpu related compatibility issues. I use a 7950x to compile the depenencies in docker and it seems like lacking avx support on other cpus is the reason. On my side, Arch and Windows 10 work fine.
Since I have no way to verify or recreate this problem myself, I will not support it. I need at least one confirmation that rebuilding the docker image from scratch works properly, then I can just close the issue.

OK, since I'm using the "outdated" i3900k which doesn't support AVX 512, I tried to build the docker image myself. And the original Dockerfile doesn't work due to some updated package versions. I have created a new pr for this.

I was suspecting some sort of AVX instruction set, but this seems to confirm AVX512 then.

due to some updated package versions.

Yeah, that happens all the time. I often do adjustments prior to building since versions can change. That's why I like to upload my docker images to dockerhub so others don't have to bother.

I have created a new pr for this.

My pc is currently not in a working state  due to boot problems so I can't test it myself right now, but it looks good, thanks. I will just merge it in.
Does this mean you got it working by rebuilding the docker from scratch? If yes, would you mind to upload the image to dockerhub? I would then link it in the readme while I don't have a way to build it myself. Building the docker on a cpu that does not support AVX512 should be the easiest way to disable it for now.

Hi, it works if I rebuild the docker from scratch. And here is the dockerhub link https://hub.docker.com/r/chin39/vsgan_tensorrt/.

Hi, it works if I rebuild the docker from scratch. And here is the dockerhub link https://hub.docker.com/r/chin39/vsgan_tensorrt/.

Could u link the docker file u used to build or did u use the github one styler updated ? Cause i get to a point at around 70/176 and it crashes. Retrying now from scratch will see if it works.
ERROR: failed to solve: process "/bin/sh -c apt-get update && apt-get install -y --no-install-recommends   cuda-12-1   cuda-cudart-12-1   cuda-compat-12-1 &&   rm -rf /var/lib/apt/lists/*" did not complete successfully: exit code: 100

@Anon1337Elite  Hi, I am using the https://github.com/styler00dollar/VSGAN-tensorrt-docker/blob/main/Dockerfile since my PR has been merged. Does it have more error messages above? It should have some details rather than just exit code.

@Anon1337Elite Hi, I am using the https://github.com/styler00dollar/VSGAN-tensorrt-docker/blob/main/Dockerfile since my PR has been merged. Does it have more error messages above? It should have some details rather than just exit code.
BTW, "/bin/sh -c apt-get update && apt-get install -y --no-install-recommends cuda-12-1 cuda-cudart-12-1 cuda-compat-12-1 && rm -rf /var/lib/apt/lists/*" may be affected by your network, could you try to rerun again?

Thanks it worked the 3rd time.

Added relevant information into readme. Thanks.

Tried to build the docker on an old intel quad-core cpu and it worked. I will try to keep avx and non-avx docker images updated.


Angular 9 is this supports? if yes then pls share reference code

Hi
i was install npm in angular 9 project but there is having one issue
contextmenu: true,
giving error is
error TS2345: Argument of type '{ center: [number, number]; zoomControl: false; zoom: number; contextmenu: boolean; contextmenuWidth: number; contextmenuHeight: number; contextmenuItems: { text: string; callback: (e: any) => void; }[]; }' is not assignable to parameter of type 'MapOptions'.
Object literal may only specify known properties, and 'contextmenu' does not exist in type 'MapOptions'.
157       contextmenu: true,
          ~~~~~~~~~~~~~~~~~

plz give me any working reference with angular 9

I was facing the same issue, what I did was separating the markerOptions object declaration, and passing the object to the marker on its creation time. Like this: ( I am using angular 8 )
let options : any = {
    riseOnHover:true,
    icon:icon,
    contextmenu: true,
    contextmenuWidth: 140,
    contextmenuItems: [{
         text: 'Marker item',
     }]
  };
  let marker : L.Marker = L.marker([address.lat,address.lng],options);

I am using Angular 14/15.  How would this work with typescript since there is no type definitions available?

Found solution on my own.  Where I import 'leaflet-contextmenu', I manually added the type definition called leaflet-contextmen.d.ts with the following content:
declare namespace L {
interface ContextMenuItem {
text: string;
index?: number
callback?: (ev: ContextMenuItemClickEvent) => void;
}
interface MapOptions {
    contextmenu: boolean;
    contextmenuItems: ContextMenuItem[]
}

interface MarkerOptions {
    contextmenu: boolean;
    contextmenuItems: ContextMenuItem[]
}

interface ContextMenuItemClickEvent {
    latlng: LatLng;
    layerPoint: Point;
    containerPoint: Point;
    relatedTarget: Marker | Path | undefined;
}

}
Now, I am able to declare those options, compile and the plugin works.  Tested in react with TS, it should work with Angular too.


prevent move-only types from being cast incorrectly

It appears that conditional casts require a check of the type's metadata at runtime. There's no reason for us to permit that at this time, since all such conditional casts are going to fail, unless its the identity cast. That is, a move-only type is currently only a subtype of itself.

[x] ban as? and is casts of move-only values
[x] ensure as! of move-only values are statically an error too.
[x] get a warning emitted explaining the impossibility of a cast like anyValue as! MO when emitting said error.

@swift-ci please smoke test and merge


Deploying Index.html succeeds however isn't served due to case sensitive file system

If a site is deployed and the index page is Index.html instead of index.html everything looks to have deployed correctly however Azure will just return 404 when navigating to the static web app. After discussing with @anthonychu on Twitter this is due to file system being case sensitive and the check for index.html is not case sensitive.
To Reproduce
Steps to reproduce the behavior:

Have a repo with an Index.html instead of index.html
Deploy the site using GitHub Actions
Attempt to view your deployed site and Azure just returns 404

Expected behavior
GitHub action should error and block deployment but give a meaningful error message
Additional context
See https://twitter.com/tomaustin700/status/1457373532070031363

We are also running into this issue. Some of our CSS files were referenced using the wrong casing and failed to load. This really should be address since URLs should be case insensitive.

URL paths are supposed to be case sensitive. It matters for things like SEO scoring, routing, etc.

URL paths are supposed to be case sensitive. It matters for things like SEO scoring, routing, etc.

Yes, it is more of my opinion that they should be case insensitive. However, in this case, maybe there needs to be an option in Azure to say whether you want to use case-insensitive matching or not.

I agree it should be a configuration option.

Is there any update on providing an option for case-insensitive URLs?

Hi folks, as @miwebst indicated above, the case insensitivity is quite important and I think it's the generally accepted convention (https://www.w3.org/TR/WD-html40-970708/htmlweb.html), what is the use case for case insensitivity and what prevents you from having case sensitive files? Would love to better understand the use case regarding why this is needed

Hi @thomasgauvin, in my case it was just a mistake however the fact that the deployment succeeded was more of an issue. If case sensitivity is required then I feel like the deployment should fail if any files don't match the required casing.

Thanks @tomaustin700, that's a good point

Hi folks, as @miwebst indicated above, the case insensitivity is quite important and I think it's the generally accepted convention (https://www.w3.org/TR/WD-html40-970708/htmlweb.html), what is the use case for case insensitivity and what prevents you from having case sensitive files? Would love to better understand the use case regarding why this is needed and why your architecture leads to URL references that are not case-sensitive

Very straight forward use case.   Much of the web has operated in a case-insensitive manner for URLs, regardless of what "spec" may say.   IIS was case-insensitive and powered large portions of the website.   Kestrel is also case-insensitive if deployed on a Windows host.
Many web sites are case-insensitive.   For example, if I go to https://microsoft.com/AZURE it works the same as https://microsoft.com/azure
Think about it from a human behavior.    If you have a URL that someone is going to type in, do you expect they will follow case sensitivity?   I mean how many people still type "www." before a domain if you tell them to go to something like "expedia.com"
By forcing case-sensitivity we are looking at only from a machine-focused mindset and not a human mindset.
While case-sensitive should remain the default, there should be a config option to disable case-sensitivity.


Unable to use jsonl files for fine-tuning

I am trying to use a jsonl file for fine tuning with optimum neuron using a trainium instance. I get this error:
File "/usr/local/lib/python3.10/site-packages/optimum/neuron/hf_argparser.py", line 44, in parse_args_into_dataclasses
assert extension in ["csv", "json", "txt"], "train_file should be a csv, a json or a txt file."    outputs = super().parse_args_into_dataclasses(*args, **kwargs)AssertionError
:   File "/usr/local/lib/python3.10/site-packages/transformers/hf_argparser.py", line 338, in parse_args_into_dataclasses
train_file should be a csv, a json or a txt file.    assert extension in ["csv", "json", "txt"], "train_file should be a csv, a json or a txt file."
AssertionError: train_file should be a csv, a json or a txt file.
main()  File "/opt/ml/code/run_clm.py", line 241, in main    main()  File "/opt/ml/code/run_clm.py", line 241, in main    obj = dtype(**inputs)  File "", line 15, in init

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!


MINOR: Improve AuthorizerIntegrationTest

This is another round in my effort to clean up some of the integration tests and improve build time. This patch improves the authorizer integration tests in the following ways:

We use a separate principal for inter-broker communications. This ensures that ACLs set in the test cases do not interfere with inter-broker communication. We had two test cases (testCreateTopicAuthorizationWithClusterCreate and testAuthorizationWithTopicExisting) which depend on topic creation and were timing out because of inter-broker metadata propagation failures. The timeouts were treated as successfully satisfying the expectation of authorization. So the tests passed, but not because of the intended reason.
Previously GroupAuthorizerIntegrationTest was inheriting all of the tests from AuthorizerIntegrationTest. This seemed like overkill since the ACL evaluation logic is essentially the same.

Totally this should take about 5-10 minutes off the total build time and make the authorizer integration tests a little more resilient to problems with inter-broker communication.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

retest this please

Before:

After:

retest this please

retest this please

retest this please

retest this please


opening white holes when values change

maybe do this directly in systems that change values?
this would be all the update_x systems and in commands..

or i'm thinking about doing it manually? so everything gets an open_target and then you'd need an op that outputs 1 whenever its input is changed.. loll

only thing left now is the dragging.. i mean, we can go hacky here.. when mouse (or an arrow key) is pressed see drag modes and selected entities and only do this in edit..

i feel clean :3


how to sample images with a trained model

Thank you for providing this neat code!!!
I have trained your model on CIFAR-10, but I don't know how to get samples. Is there any function or script to generate samples with a trained model?

Sorry for the late reply. If you check line 499 of DeepLearning/my_sngan.py, you may notice the method eval_sampling randomly generates image samples and save the generated images to a sprite image file. You may also add one line to return the x_gen_value, which contains the generated images in numpy array format.
Note that this method is called in line 88-90 of my_test_cifar.py, so perhaps the simplest way is to comment out line 83-87 and line 91-94 in my_test_cifar.py, decrease the indentation of line 88-90, and run the file. In this case, the file would avoid the training phase and directly do the sampling. Please also note that my code by default uses the latest saved model in the ckpt_folder defined at line 522 of DeepLearning/my_sngan.py (which should be FLAGS.DEFAULT_OUT + filename + subfolder).
Please feel free for any further question. Thanks for your interest.

Sorry for the late reply. If you check line 499 of DeepLearning/my_sngan.py, you may notice the method eval_sampling randomly generates image samples and save the generated images to a sprite image file. You may also add one line to return the x_gen_value, which contains the generated images in numpy array format.
Note that this method is called in line 88-90 of my_test_cifar.py, so perhaps the simplest way is to comment out line 83-87 and line 91-94 in my_test_cifar.py, decrease the indentation of line 88-90, and run the file. In this case, the file would avoid the training phase and directly do the sampling. Please also note that my code by default uses the latest saved model in the ckpt_folder defined at line 522 of DeepLearning/my_sngan.py (which should be FLAGS.DEFAULT_OUT + filename + subfolder).
Please feel free for any further question. Thanks for your interest.

It works. Thanks a lot!


Ability to unregister a shortcut via the shortcut's keys

Description

This PR adds a new method for unregistering a shortcut via the key combination it's set to, rather than its ID if user do not or cannot keep track of the ID when registering the shortcut for whatever reason.
Motivation and Context

Continuing my Push-to-talk endeavors described in #118, our electron app works off a main thread and a helper thread. We try to keep the main thread light, and thus keeping track of IDs for shortcuts is not ideal. We could send the registered IDs back to the helper thread, but it already keeps track of a mapping from shortcut name -> key, and ideally that should be all the information that's necessary for iohook to identify a shortcut.
Additionally, this method is provided as a convenience if one does not want to build a system for tracking IDs of shortcuts they have created.
This system is also partially inspired by electron's globalShortcut module, which also allows for unregistering a shortcut via the key codes it tracks.
How Has This Been Tested?

Tested in our app, but a test case is provided.
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Clear and commented code, thanks ! LGTM.

Fixed, thank you!

LGTM?

Thanks!

You're welcome. I'll merge that this sunday or ASAP.

Awesome, thank you!


Can we use celery as PUB/SUB?

I'm wondering whether we can use celery+rabbitmq as PUB/SUB and what modifications need to be done to achieve this? Thank you.

Hey there Fadi :)
If you mean to use celery/rabbitmq as a backbone pub/sub (instead of Kafka, Redis, Postgres L/N), then yes there's a way - though it's not as straightforward as we'd like.
Fastapi-ws-PubSub uses Broadcaster as an adapter to the backbone pub-sub.
You can rather easily implement a celery/rabbitmq adapter there, see the implementations here
The challenge would be to make broadcaster aware of your new backend (since the importing the backends is hardcoded here)
Unfortunately it seems that the maintainers of broadcaster are not responsive - so you might find a hard time getting your pull request there.
A hack you can use (Which I'm not a fan of) is to create a Broadcaster instance and override its  self._backend.
And of course you can fork broadcaster and do as you wish...
Hope this helps. :)

Closing this issue as this should be addressed by encode/broadcaster


Could you offer a script to reproduce face attribute acc？

This is a great work, but when I reproduced the celeba test set, I couldn't reach 91.77 in the paper, I could only reach 90.04, and I checked the test code. Can you provide your test acc code? Looking forward to your reply. Thank you.

Hi,
Our work is currently under review. We will share all our scripts once our work is published. You can star the repo to stay updated.
Thanks !


extractWithoutRootDirectory() fails if destination is .

If you pass . (the current working directory) as the destination to the Distill::extractWithoutRootDirectory() method, extracting the archive fails with a message like this:
rmdir: failed to remove ‘.’: Invalid argument

The reason for this is, for example, explained here.

@xabbuh thanks for opening the issue! Working on it...

@raulfraile Thank you. I thought that calling realpath() on the path that is passed to rmdir() would suffice. However, that led to other issues (probably due to the fact that the current working directory does not exist any more after the removal). Maybe we need to switch the working directory first in those cases.

@xabbuh yes, I'm working with that approach, the working directory needs to be changed first

@xabbuh it should be fixed in the fix/current_dir branch. Do you have any comments about https://github.com/raulfraile/distill/commit/eb8fed8e356923d212c0aef2da02e6272ebe78dd?

@raulfraile Do we need some special handling in case there is no parent directory?

@xabbuh would that happen only if you are in the root directory or is there any other situation? Anyway, I think we should handle gracefully and throw an error

I think this will only happen when you are in the root directory.

@raulfraile This fix does not work as is. I think the issue is the check if ('.' === $path). Imho this needs to be either if ('.' === basename($path) or something like if (getcwd() === realpath($path)).

@xabbuh thanks for your suggestions! Now I throw an exception when you are in the root directory and I use getcwd() === realpath($path) to check if the target directory is the same as the current directory

Commit: https://github.com/raulfraile/distill/commit/5fa7ce1d837953eb26247a4160586c023ae88023

@raulfraile I can confirm that this fixes the root issue.

@raulfraile I see one issue with the proposed solution: When using the Symfony installer, the user would have to change directories after installing Symfony in the current directory because the current working directory does not exist anymore. What do you think about extracting the archive to a temporary subdirectory instead and moving contents up after the extraction succeeded?


Forgotten password and user name. Cannot use the app. Any way of fixing this?

Prerequisites

[x] Are you running Taskboard with the same requirements as describe in README.md?
[x] Did you perform a cursory search to see if your bug or enhancement is already reported?
[ ] Are you sure your problem come from the Taskboard project and not your environment ? Google is your friend :)

Description
[Short description of problem here]
Steps to Reproduce

[First Step]
[Second Step]
[Other Steps...]

Expected behavior:
[Describe expected behavior here]
Actual behavior:
[Describe observed behavior here]
-- If you recived an error, place it here.

-- Separate them if you have more than one.

Additional information

Problem started happening recently, didn't happen in an older version of Aurora: [Yes/No]
Problem can be reliably reproduced, doesn't happen randomly: [Yes/No]

Screenshots and GIFs

Installed AddOns:
[List of installed addons which may conflict with the Aurora skin]

Please provide links to retrieve usernames and password

You could certainly lookup usernames in the DB, but there is no way to recover your password as they are hashed.
I may need to add a "forgot password" utility, but that is a far future thing.

Thanks for responding Matthew.
The App has just got the required simplicity I am after, but it does not play well with my mac.
I will follow your work monitoring on progress, but for now I will have to use Trello.
Wishing you well,
Margaretha

On 7 Jan 2020, at 05:30, Matthew Ross<EMAIL_ADDRESS>wrote:
You could certainly lookup usernames in the DB, but there is no way to recover your password as they are hashed.
I may need to add a "forgot password" utility, but that is a far future thing.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/kiswa/TaskBoard/issues/483?email_source=notifications&email_token=AG2SAU5RGJGTDEMQW65FR6TQ4OBFFA5CNFSM4KCTMNWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIGQJAY#issuecomment-571278467, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG2SAU5P6WSZGALMKYNFHW3Q4OBFFANCNFSM4KCTMNWA.


Fails to download the model from Huggingface

Hi. For several days now, when I try to download a model, I get the following error.
I saw that one user wrote about this before me, but I still have this error.

that link doesn't contain the diffusers model, it contains only ckpts, so simply copy the ckpt link and put it  in "CKPT_LINK", make sure you remove the link above.
https://huggingface.co/hakurei/waifu-diffusion-v1-4/resolve/main/wd-1-4-anime_e1.ckpt
https://huggingface.co/hakurei/waifu-diffusion-v1-4/resolve/main/wd-1-4-anime_e2.ckpt
yaml : https://huggingface.co/hakurei/waifu-diffusion-v1-4/blob/main/wd-1-4-anime_e1.yaml

that link doesn't contain the diffusers model, it contains only ckpts, so simply copy the ckpt link and put it in "CKPT_LINK", make sure you remove the link above. https://huggingface.co/hakurei/waifu-diffusion-v1-4/resolve/main/wd-1-4-anime_e1.ckpt https://huggingface.co/hakurei/waifu-diffusion-v1-4/resolve/main/wd-1-4-anime_e2.ckpt
yaml : https://huggingface.co/hakurei/waifu-diffusion-v1-4/blob/main/wd-1-4-anime_e1.yaml

I tried to copy a link, I got this

wd1.4 is v2, but I'm not sure if v2-512 or v2-768, choose one in the dropdown menu

Nope, try both, still error with both

nope, still error with both

choose v2-512 and see


use cosmossdk.io/errors

This PR uses cosmossdk.io/errors, and will reduce the size of diffs
when upgrading to sdk 47.

So is the only reason for this PR to "reduce the size of diffs" for SDK v47? Just keep it in the 47 branch if so. No need to bring this minor change before then IMO

that's the reason for it.  It doesn't add features but does improve maintainability a lot.
merge or not as you wish ser (close if not desired)

Closing as it will be done in the v47 PR (v15)


Progress indicator focus, hover, active states; and text color

addresses first comment in this issue thread: https://github.com/IBM/carbon-components-react/issues/2071#issuecomment-475410016

all states have text-01 color
focus state is visually bottom border only
transitions so the border looks nice :)

@laurenmrice thanks! changes applied


Add a warning about API functions

Recently I was messing around with createJestConfig API function to add some additional config props for the CI environment on a project I'm currently working on. However I've stumbled upon a lot of weird problems when certain props from craco.config.js were simply not visible to Jest. After tedious debugging session I've discovered a rather simple reason for that - my craco.config.js file exports a config function, which apparently is not supported by createJestConfig and that fact is neither documented, not reported as an error.
I don't know if this is intentional or not, but I figured that it would be good to at least mention that fact in the API's documentation.

Hi @mdziekon
Yes this is intentional since the createJestConfig function accept the config object that will be used for the run, it doesn't read the config from the craco.config.js file.
I don't mind merging this PR but it would be even better if instead of adding additional documentation the createJestConfig, createDevServerConfigProviderProxy, createWebpackDevConfig and createWebpackProdConfig would throw an exception when the provided config is a function instead of an object.
Would you mind updating your PR to do this instead of adding additional documentation?

@patricklafrance I agree that an additional validator is also a nice thing to have, therefore I've added it to all API functions your mentioned. However, I do not agree that this should replace the documentation piece, simply because it's better to know about this upfront rather than being surprised by it once we first run any tool that consumes these configs. Or, in other words, principle of least surprise applies to these validators.

Thanks @mdziekon
Sounds good, i'll merge it as is.
Thanks

Released in<EMAIL_ADDRESS>


Does HAXM/QEMU allow GPU or PCI passthrough?

Hi Team,
Does the HAXM/QEMU combo allow PCIe passthrough or Graphics Acceleration? I'm using a windows host, and would like to run nvidia-docker/minikube containers against a linux VM. Some guidance on whether this is possible using the HAXM/QEMU combo on windows would be helpful, and if so some information to get started would be good.
Thanks for the info.

The key is how to prevent host using the pass through devices while assigned to guest. In Linux/KVM, you have vfio-pci. In Windows, you need a pci bus level driver which controls how host access the attached device. It's feasible and I know some scenarios do similar tricks. However since Windows is not open sourced, customizing kernel behavior has lots work to do. You can choose Discrete Device Assignment from Hyper-V DDA for PCI device passthrough, however QEMU/HAXM can't provide alternative solution on Windows at this moment.

Ok, great. Thanks for the info. Looks like I'll be dual booting for now.

When it will be added?

When it will be added?
I'm afraid at this moment we can only reply on Windows implementation, like DDA. It's quite difficult for 3rd party vendor to modify Windows kernel to prevent OS accessing GPU. In Linux world things are simple, just enable VT-d and unbind the device from host usage.

I don't need to passthrough GPU. I need to bypass custom real PCI device, which is not used by Windows.

I don't need to passthrough GPU. I need to bypass custom real PCI device, which is not used by Windows.

GPU is also a PCI device. Of course with a non-GPU PCI device, you do need worry OS will access it unconditionally, however you need some mechanism so that generic device enumeration won't touch the device, but pass through to QEMU right? Even windows doesn't use it, the pci/acpi driver will still enumerate it and build device/driver stack.
Have you checked this?
https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/plan-for-deploying-devices-using-discrete-device-assignment
This is far beyond HAXM scope. QEMU may need implement it with a PCI lower bus filter driver, and some framework like vfio-pci on Linux.

@coxuintel : does DDA work on Windows 10 pro or not ?

I'm not quiet sure about this. MSDN documented "Applies to: Microsoft Hyper-V Server 2016, Windows Server 2016, Windows Server 2019, Microsoft Hyper-V Server 2019".
https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/deploying-graphics-devices-using-dda
You may follow this thread see if can get formal response from Microsoft:
https://social.technet.microsoft.com/Forums/en-US/4069f3cf-559d-4f87-9247-25076535707f/windows-10-virtual-machines-and-dda-for-gpus?forum=win10itprovirt

hello. thanks. what are the hardware requisites to enable the DDA on Windows server 2016 or 2019 ?

@coxuintel : thanks. what are the hardware requisites to enable the DDA on Windows server 2016 or 2019 ?

I thought it depends on Windows as well.

ok but what are the hardware`s ones ?
Il ven 15 mag 2020, 10:27 Colin Xu<EMAIL_ADDRESS>ha scritto:

@coxuintel https://github.com/coxuintel : thanks. what are the hardware
requisites to enable the DDA on Windows server 2016 or 2019 ?
I thought it depends on Windows as well.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/intel/haxm/issues/220#issuecomment-629104198, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFYNCYISIMFVNF6CKKNCELRRT4GHANCNFSM4H6WQTEQ
.


Added option to set anywhere for the verify method

I have been working on an implementation where the signed xml would contain another signature signed by a different key. Because this signature was returned first by the find method the verify method would fail due to the key not being correct. By not searching on all the subelements this second signature can be easily ignored.

[Current coverage][cc-pull] is 94.29%

Merging [#58][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master        #58   diff @@
==========================================
  Files             2          2
  Lines           491        491
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            463        463
  Misses           28         28
  Partials          0          0

Powered by Codecov. Last updated by [25e9488...bd79bd5][cc-compare]
[cc-base-branch]: https://codecov.io/gh/kislyuk/signxml/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/kislyuk/signxml/compare/25e9488765865f7c8055ecb1bf8884d09e795e2b...bd79bd555339955e504d17dd54e8353918fb7193?src=pr
[cc-pull]: https://codecov.io/gh/kislyuk/signxml/pull/58?src=pr

I don't think this is the right way to solve the problem of ambiguity as to which signature to verify. I would prefer to throw an error by default if multiple signatures are found, and have a flag that allows multiple signatures in the document and a method to iterate over them. Also we could figure out a way to identify the signature you want, and switch to breadth-first search over the element tree.

Continuing in #59


feat: Added neon theme

This theme has bright colors that works well with dark backgrounds.
Description

Fixes #
Type of change

[ ] Bug fix (added a non-breaking change which fixes an issue)
[x] New feature (added a non-breaking change which adds functionality)
[ ] Updated documentation (updated the readme, templates, or other repo files)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

[ ] Tested locally with a valid username
[ ] Tested locally with an invalid username
[ ] Ran tests with composer test
[ ] Added or updated test cases to test new features

Checklist:

[x] I have checked to make sure no other pull requests are open for this issue
[x] The code is properly formatted and is consistent with the existing code style
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

Screenshots

You are most welcome. 🎉


Panic when Invalid Struct is Registered

Without this, an invalid struct can be partially registered in tests or in workers, which can lead to weird failure when activities are missing but unknown as to why they are missing.
Combines with #360 for solving #356.

I don't have good tests for this. Where/how should I test this?