Cannot install GPFlow: Scipy==1.4.1 installation fails

Build issue
Cannot install GPFlow.
Scipy==1.4.1 installation fails

To reproduce
At a freshly installed and activated venv: pip install gpflow
Stack trace, or error message
Collecting gpflow
  Using cached gpflow-2.7.1-py3-none-any.whl (372 kB)
  Using cached gpflow-2.7.0-py3-none-any.whl (372 kB)
  Using cached gpflow-2.6.5-py3-none-any.whl (446 kB)
Collecting deprecated
  Using cached Deprecated-1.2.13-py2.py3-none-any.whl (9.6 kB)
Collecting lark>=1.1.0
  Using cached lark-1.1.5-py3-none-any.whl (107 kB)
Collecting multipledispatch>=0.6
  Using cached multipledispatch-0.6.0-py3-none-any.whl (11 kB)
Collecting numpy
  Using cached numpy-1.24.2-cp311-cp311-win_amd64.whl (14.8 MB)
Collecting packaging
  Using cached packaging-23.0-py3-none-any.whl (42 kB)
Collecting scipy
  Using cached scipy-1.10.1-cp311-cp311-win_amd64.whl (42.2 MB)
Requirement already satisfied: setuptools>=41.0.0 in c:\users\matthew.rowles\documents\gpflow\gpflow\lib\site-packages (from gpflow) (65.5.0)
Collecting tabulate
  Using cached tabulate-0.9.0-py3-none-any.whl (35 kB)
Collecting tensorflow-probability>=0.12.0
  Using cached tensorflow_probability-0.19.0-py2.py3-none-any.whl (6.7 MB)
Collecting typing-extensions
  Using cached typing_extensions-4.5.0-py3-none-any.whl (27 kB)
Collecting gpflow
  Using cached gpflow-2.6.4-py3-none-any.whl (446 kB)
  Using cached gpflow-2.6.3-py3-none-any.whl (445 kB)
  Using cached gpflow-2.6.2-py3-none-any.whl (445 kB)
  Using cached gpflow-2.6.1-py3-none-any.whl (444 kB)
  Using cached gpflow-2.6.0-py3-none-any.whl (443 kB)
  Using cached gpflow-2.5.2-py3-none-any.whl (383 kB)
  Using cached gpflow-2.5.1-py3-none-any.whl (381 kB)
  Using cached gpflow-2.4.0-py3-none-any.whl (334 kB)
  Using cached gpflow-2.3.1-py3-none-any.whl (287 kB)
  Using cached gpflow-2.3.0-py3-none-any.whl (286 kB)
  Using cached gpflow-2.2.1-py3-none-any.whl (271 kB)
  Using cached gpflow-2.2.0-py3-none-any.whl (271 kB)
  Using cached gpflow-2.1.5-py3-none-any.whl (260 kB)
  Using cached gpflow-2.1.4-py3-none-any.whl (255 kB)
  Using cached gpflow-2.1.3-py3-none-any.whl (254 kB)
  Using cached gpflow-2.1.2-py3-none-any.whl (253 kB)
  Using cached gpflow-2.1.1-py3-none-any.whl (247 kB)
  Using cached gpflow-2.1.0-py3-none-any.whl (231 kB)
Collecting scipy==1.4.1,>=0.18.0
  Using cached scipy-1.4.1.tar.gz (24.6 MB)
  Installing build dependencies ... /

# snip
# >9999 lines of output
#
:\Program Files (x86)\Windows Kits\10\\include\10.0.19041.0\\winrt -IC:\Program Files (x86)\Windows Kits\10\\include\10.0.19041.0\\cppwinrt -IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.34.31933\include -IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.34.31933\ATLMFC\include -IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\VS\include -IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\ucrt -IC:\Program Files (x86)\Windows Kits\10\\include\10.0.19041.0\\um -IC:\Program Files (x86)\Windows Kits\10\\include\10.0.19041.0\\shared -IC:\Program Files (x86)\Windows Kits\10\\include\10.0.19041.0\\winrt -IC:\Program Files (x86)\Windows Kits\10\\include\10.0.19041.0\\cppwinrt -IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.34.31933\include -IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.34.31933\ATLMFC\include -IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\VS\include -IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\ucrt -IC:\Program Files (x86)\Windows Kits\10\\include\10.0.19041.0\\um -IC:\Program Files (x86)\Windows Kits\10\\include\10.0.19041.0\\shared -IC:\Program Files (x86)\Windows Kits\10\\include\10.0.19041.0\\winrt -IC:\Program Files (x86)\Windows Kits\10\\include\10.0.19041.0\\cppwinrt /Tc_configtest.c /Fo_configtest.obj
        error:
        [end of output]

        note: This error originates from a subprocess, and is likely not a problem with pip.
      error: legacy-install-failure

      Encountered error while trying to install package.

      numpy

      note: This is an issue with the package mentioned above, not pip.
      hint: See above for output from the failure.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

(gpflow) C:\gpflow>

Expected behavior
GPFlow installs
System information

GPflow version: Don't know. Didn't get that far.
GPflow installed from: "pip install gpflow"
TensorFlow version: Don't know. Didn't get that far.
Python version: Python 3.11.2
Operating system: Windows 10 08.30.21

Additional context
Installation was carried out in a fresh venv.

At present, we can't support Python 3.11, as Tensorflow doesn't support it yet.  Please try again with Python version 3.7 - 3.10

You might want to update the installation requirements in the readme. It currently says you support Python >= 3.7.


how to open?

I have windows 10 but i don't know how to open the app.
Pls help me.
Thanks

I think you might be trying to download the source code.
You need the compiled exe version, there is a download under "releases" under the "<> Code" Section.
or you can Ctrl+F for "releases".
Hope this helps!

@thaAndrex the installer is located in releases. https://github.com/martynasS/magic-home-desktop/releases/


Set image quality output

How to set image quality output ?

The only way to do it is to extend the behavior code and change the phpthumb related code as you wish.


[Device Support Request] TS011F MS-104BZ (Zigbee + RF) _TZ3000_pmz6mjyu

Is your feature request related to a problem? Please describe.
Clusters 0xE000 and 0xE001 are logged as warnings and can't be accessed:
2022-01-07 18:31:37 WARNING (MainThread) [zigpy.zcl] Unknown cluster 57344
2022-01-07 18:31:37 WARNING (MainThread) [zigpy.zcl] Unknown cluster 57345
2022-01-07 18:31:37 WARNING (MainThread) [zigpy.zcl] Unknown cluster 57344
2022-01-07 18:31:37 WARNING (MainThread) [zigpy.zcl] Unknown cluster 57345
2022-01-07 18:31:37 WARNING (MainThread) [zigpy.zcl] Unknown cluster 57344
2022-01-07 18:31:37 WARNING (MainThread) [zigpy.zcl] Unknown cluster 57345
2022-01-07 18:31:37 WARNING (MainThread) [zigpy.zcl] Unknown cluster 57344
2022-01-07 18:31:37 WARNING (MainThread) [zigpy.zcl] Unknown cluster 57345

Access to 0xE001 is needed to configure Rocker / Reset switch behavior.
Describe the solution you'd like
Force Rocker switch behavior to be able to toggle both physical switches at the same time. Right now, if I press both physical switches at the same time only one light is toggled and the other one is ignored.
Device signature - this can be acquired by removing the device from ZHA and pairing it again from the add devices screen. Be sure to add the entire content of the log panel after pairing the device to a code block below this line.
{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice: 142>, manufacturer_code=4098, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x010a",
      "in_clusters": [
        "0x0000",
        "0x0003",
        "0x0004",
        "0x0005",
        "0x0006",
        "0xe000",
        "0xe001"
      ],
      "out_clusters": [
        "0x000a",
        "0x0019"
      ]
    },
    "2": {
      "profile_id": 260,
      "device_type": "0x010a",
      "in_clusters": [
        "0x0003",
        "0x0004",
        "0x0005",
        "0x0006",
        "0xe000",
        "0xe001"
      ],
      "out_clusters": []
    },
    "242": {
      "profile_id": 41440,
      "device_type": "0x0061",
      "in_clusters": [],
      "out_clusters": [
        "0x0021"
      ]
    }
  },
  "manufacturer": "_TZ3000_pmz6mjyu",
  "model": "TS011F",
  "class": "zigpy.device.Device"
}

Additional context
My device seems to be an updated version of MS-104BZ with both Rocker and Reset switches support.
https://www.moeshouse.com/products/2-gang-tuya-zigbee-3-0-smart-light-switch-module-2mqtt-setup-available

I've tried adding the following quirk:
"""Tuya TS011F Switches."""

from zigpy.profiles import zha
from zigpy.zcl.clusters.general import (
    Basic,
    GreenPowerProxy,
    Groups,
    Identify,
    OnOff,
    Ota,
    Scenes,
    Time,
)

from zhaquirks.const import (
    DEVICE_TYPE,
    ENDPOINTS,
    INPUT_CLUSTERS,
    MODEL,
    OUTPUT_CLUSTERS,
    PROFILE_ID,
)
from zhaquirks.tuya import (
    TuyaSwitch,
    TuyaZBE000Cluster,
    TuyaZBExternalSwitchTypeCluster,
    TuyaZBOnOffAttributeCluster,
)

class Tuya_2G_Switch(TuyaSwitch):
    """Tuya 2 gang light switch."""

    signature = {
        MODEL: "TS011F",
        ENDPOINTS: {
            # <SimpleDescriptor endpoint=1 profile=260 device_type=266
            # input_clusters=[0, 3, 4, 5, 6, 57344, 57345]
            # output_clusters=[10, 25]>
            1: {
                PROFILE_ID: zha.PROFILE_ID,
                DEVICE_TYPE: zha.DeviceType.ON_OFF_PLUG_IN_UNIT,
                INPUT_CLUSTERS: [
                    Basic.cluster_id,
                    Identify.cluster_id,
                    Groups.cluster_id,
                    Scenes.cluster_id,
                    OnOff.cluster_id,
                    TuyaZBE000Cluster.cluster_id,
                    TuyaZBExternalSwitchTypeCluster.cluster_id,
                ],
                OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
            },
            # <SimpleDescriptor endpoint=2 profile=260 device_type=266
            # input_clusters=[3, 4, 5, 6, 57344, 57345]
            # output_clusters=[]>
            2: {
                PROFILE_ID: zha.PROFILE_ID,
                DEVICE_TYPE: zha.DeviceType.ON_OFF_PLUG_IN_UNIT,
                INPUT_CLUSTERS: [
                    Identify.cluster_id,
                    Groups.cluster_id,
                    Scenes.cluster_id,
                    OnOff.cluster_id,
                    TuyaZBE000Cluster.cluster_id,
                    TuyaZBExternalSwitchTypeCluster.cluster_id,
                ],
                OUTPUT_CLUSTERS: [],
            },
            # <SimpleDescriptor endpoint=242 profile=41440 device_type=97
            # input_clusters=[]
            # output_clusters=[33]>
            242: {
                PROFILE_ID: 41440,
                DEVICE_TYPE: 97,
                INPUT_CLUSTERS: [],
                OUTPUT_CLUSTERS: [GreenPowerProxy.cluster_id],
            },
        },
    }
    replacement = {
        ENDPOINTS: {
            1: {
                PROFILE_ID: zha.PROFILE_ID,
                DEVICE_TYPE: zha.DeviceType.ON_OFF_LIGHT,
                INPUT_CLUSTERS: [
                    Basic.cluster_id,
                    Identify.cluster_id,
                    Groups.cluster_id,
                    Scenes.cluster_id,
                    TuyaZBOnOffAttributeCluster,
                    TuyaZBE000Cluster,
                    TuyaZBExternalSwitchTypeCluster,
                ],
                OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
            },
            2: {
                PROFILE_ID: zha.PROFILE_ID,
                DEVICE_TYPE: zha.DeviceType.ON_OFF_LIGHT,
                INPUT_CLUSTERS: [
                    Identify.cluster_id,
                    Groups.cluster_id,
                    Scenes.cluster_id,
                    TuyaZBOnOffAttributeCluster,
                    TuyaZBE000Cluster,
                    TuyaZBExternalSwitchTypeCluster,
                ],
                OUTPUT_CLUSTERS: [],
            },
        },
    }

But unfortunately 0xE001 cluster isn't correct, since apparently 0xD030 attribute doesn't exist...
2022-01-07 21:20:10 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [29, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0xb27b>, 1, 260, 57345, b'\x18\x90\x010\xd0\x86', 0, 175, 255, 49, 44, 152, 0, -49]
2022-01-07 21:20:10 DEBUG (MainThread) [zigpy.zcl] [0xb27b:1:0xe001] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=144 command_id=Command.Read_Attributes_rsp>
2022-01-07 21:20:10 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0xb27b>, ep: 1, profile: 0x0104, cluster_id: 0xe001, data: b'18900130d086'
2022-01-07 21:20:10 DEBUG (MainThread) [homeassistant.components.zha.api] Read attribute for: cluster_id: [57345] cluster_type: [in] endpoint_id: [1] attribute: [53296] manufacturer: [None] response: [None] failure: [{53296: <Status.UNSUPPORTED_ATTRIBUTE: 134>}],

How can I list the available cluster attributes and their possible values?

I think your quirk is working OK but i cant see is it loaded OK but you is having it in the log.
The device is responding with <Status.UNSUPPORTED_ATTRIBUTE: 134> = it have getting one request of one attribute but its have not suport for that attribute.
Reason for that can being that the device is not having it implanted or its using it in one other way that we is knowing.
First look in Z2M how they have implanted the same device and if they is asl using the "normal" tuya attribute or is using some more magic.

I think your quirk is working OK but i cant see is it loaded OK but you is having it in the log.
The device is responding with <Status.UNSUPPORTED_ATTRIBUTE: 134> = it have getting one request of one attribute but its have not suport for that attribute.
Reason for that can being that the device is not having it implanted or its using it in one other way that we is knowing.
First look in Z2M how they have implanted the same device and if they is asl using the "normal" tuya attribute or is using some more magic.

Yes, the quirk is OK, but the 0xE001 cluster (TuyaZBExternalSwitchTypeCluster) is missing attributes to configure the external switch, since 0xD030 isn't supported.
How can I list the supported attributes for the 0xE001 cluster?

The cluster and its attribute is implanted in https://github.com/zigpy/zha-device-handlers/blob/b0bbbfb6b1f267b7d87d833b1ba5a5b0b127a9a1/zhaquirks/tuya/init.py#L885-L900.
And the finding is documented here: https://github.com/zigpy/zigpy/discussions/823#discussioncomment-1539469.
If you is finding more attributes and commands please help documenting them so we can using them in all devices that is supporting it.
I have some tuya plugs that is not supporting this attributes but its no problem ZHA is only logging not supported and the system and the device is working normal but we cant getting one device supporting attributes that is not implanted in the device firmware only tuya can do that.

The cluster and its attribute is implanted in https://github.com/zigpy/zha-device-handlers/blob/b0bbbfb6b1f267b7d87d833b1ba5a5b0b127a9a1/zhaquirks/tuya/init.py#L885-L900.
And the finding is documented here: https://github.com/zigpy/zigpy/discussions/823#discussioncomment-1539469.
If you is finding more attributes and commands please help documenting them so we can using them in all devices that is supporting it.
I have some tuya plugs that is not supporting this attributes but its no problem ZHA is only logging not supported and the system and the device is working normal but we cant getting one device supporting attributes that is not implanted in the device firmware only tuya can do that.

The thing is I don't know how to find out more cluster attributes...
I've searched but I couldn't find any documentation about it.
From what you say the only possibility is that Tuya reveals that information, right?
Isn't there any way of reading all attribute identifiers and checking which ones are suported?

Zigbee have command for reporting attribute that is supported but its only working if the device is good made and tuya devices is normally not certified and have not implanted or making only half so its not working.
Then i and other user is finding new function we os trying documenting them and then getting it implanted in the system so we can using it.
The best is reading if the manufacturer is writing if the function is supported but its not the same its working in the real life with tuya and many other manufacturers.
Bet is using one tuya ZBGW and sniffing the communication and doing changs and see what is being sent and using the information for the findings. Last sniff findings is undocumented min and max for tuya dimmer switches one user was doing :-)))
Normally Z2M is having the most findings implanted and need looking for the device in there git and then what function its using.

This model supports power on behavior ( https://www.zigbee2mqtt.io/devices/MS-104BZ.html )
I can help testing if someone can add this attribute in the quirk :-)
Thanks

All found functions in implanted in the quirk:
https://github.com/zigpy/zha-device-handlers/blob/dcee551996a0a9e388b6afb1e054dada46897ee5/zhaquirks/tuya/__init__.py#L827-L857
So you shall having one TuyaZBOnOffAttributeCluster and the attribute  {0x8002: ("power_on_state", PowerOnState) that you can read and writing.
Its working on my LIDL 3Plug 4 USB strip.

PS: its only working if your device have the quirk loaded or you must adding it to the quirk.

Yes. Sorry. Didn't have the quirk loaded. All good, I managed to set another power on state. Thanks

Hi,
I also got one device with one gang:

How can I help for a quirk for this one?
Device signature:
{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice: 142>, manufacturer_code=4098, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x0009",
      "in_clusters": [
        "0x0000",
        "0x0004",
        "0x0005",
        "0x0006"
      ],
      "out_clusters": [
        "0x000a",
        "0x0019"
      ]
    }
  },
  "manufacturer": "_TZ3000_zmy1waw6",
  "model": "TS011F",
  "class": "zigpy.device.Device"
}

It is working well by default, the only thing I need is the power_on_state attribute, that I need to change in cluster...

You can trying this quirk i have adding your device signature but i have not testing it.
Renaming it without the .txt and putting in in your (configured) local quirk folder and restarting HA and look if the system is loading the quirk for the device.
ts011f.py.txt

I just added the last part to existing ts011f.py. This one:
class Tuya_1G_Switch(TuyaSwitch):
    """Tuya 1 gang light switch with RF433."""

    signature = {
        MODEL: "TS011F",
        ENDPOINTS: {
            # <SimpleDescriptor endpoint=1 profile=260 device_type=9
            # input_clusters=[0, 4, 5, 6,]
            # output_clusters=[10, 25]>
            1: {
                PROFILE_ID: zha.PROFILE_ID,
                DEVICE_TYPE: zha.DeviceType.MAIN_POWER_OUTLET,
                INPUT_CLUSTERS: [
                    Basic.cluster_id,
                    Groups.cluster_id,
                    Scenes.cluster_id,
                    OnOff.cluster_id,
                ],
                OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
            },
        },
    }
    replacement = {
        ENDPOINTS: {
            1: {
                PROFILE_ID: zha.PROFILE_ID,
                DEVICE_TYPE: zha.DeviceType.ON_OFF_LIGHT,
                INPUT_CLUSTERS: [
                    Basic.cluster_id,
                    Groups.cluster_id,
                    Scenes.cluster_id,
                    TuyaZBOnOffAttributeCluster,
                ],
                OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
            },
        },
    }

Because there was some changes to the 2 gang quirk and didn't know if will break something...

And YES, it's working and I can change the power on state.
Thanks a lot!

Looks great !!
Only one thing: Changing DeviceType can making problems with devices so shall not being made in the quirk. If you need making it then do in HA with custom setting.
Then you is having one working quirk can you doing on PR for adding it so other user can using it  2 ?

I didn't change DeviceType. I have this version https://github.com/zigpy/zha-device-handlers/blob/dev/zhaquirks/tuya/ts011f.py
In your quirk was changed 😃

I was only adding the GPP version but in the end it shall being corrected sooner or later before users is getting problems with there devices.
Can you making one PR for you device ??

Are there any special requests for PR?

I have posting one PR #1347 that adding your device.
I have also renaming the quirk so it fitting with the other tuya quirk and changing the device type so its not being changed and making problems with devices.
If you can testing the quirk from the PR it wold being great (you must deleting your privies local quirk so only one for your device is on the local quirk folder) it wold being great for getting it merged in ZHA.

I'm testing the new quirk. The 1G switch is working, but I have to reconfigure my 2G switches because of the new device type for 2G switch in PR quirk.
Why did you changed the device type for 2G switch from ON_OFF_LIGHT to ON_OFF_PLUG_IN_UNIT, but for 1G you let ON_OFF_LIGHT? Physically, they are the same device types, and their main field of application is for light switches.

Sorry but both shall having the original device type and i was missing fixing the new one.
I think you dont need reconfigure or somthing then using the new quirk then its loading and using the stored information from the device before the quirk is applayed.

I have 2G switches configured with the quirk before your latest PR, where the device type was set to ON_OFF_LIGHT, so the entites were in light domain:

So, the final device type will be ON_OFF_LIGHT (I think is better) or ON_OFF_PLUG_IN_UNIT?

HA is thinking its new eternities then the device type is changed.
The 2 "old" eremites is out grayed and can being deleted.
If you is changing back the 2 "new" is being grayed out and can being deleted,
If you like have it with one light icon you can changing it from the device card by clicking on the eateries and then upper right the wheel and then icon and selecting the icon you like to having.

It's not about the icon, I'm also using these entities in automations. But this is not a problem, I'll change them there also.
What I want it to know is what device type is correct for those devices, because you said "both shall having the original device type and i was missing fixing the new one."
The original is this?
https://github.com/zigpy/zha-device-handlers/blob/23a166902e50d5c32019e0d4d32a968715041bb6/zhaquirks/tuya/ts011f.py#L81-L88
...or the new one from the PR?

Updated and is braking your automatons one more time :-((

All good. Working all devices (1G and 2G) with the latest commit, all as switches now.
Thank you! 👍

Great !!
And the quirk is more "tuya standard" by naming and also have the original device types so not getting problem later with devices and must redoing then and braking automation for users.
Thanks for good testing and finding the bad copy and past coding i was doing !!


Human lymphoid organ single cell dataset integration (used in tutorial notebook)

Hello, thank you for creating this great tool!
I'd like to add a dataset to your scRNA-seq reference for lymph node but want to make sure my integration process is consistent with yours. Could you post the code used to integrate the three published scRNA-seq datasets?
Also, I noticed the Park (2020) study identified fibroblasts, but I do not see them in your integrated single cell reference data - were these excluded?

Hi @chsher
Could you please provide me with your email so that I can put you in touch with Hamish King who performed the integration?
In general, the integration was performed according to the procedure described in the methods section here: https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>8125v1.full

Since this issue is more about our paper than the cell2location package I will move it to discussions.


pulseaudio after reboot

Hi, I have an application that runs in a container that restarts after rebooting the whole system. However, the pulseaudio socket created in /tmp no longer works after rebooting. In addition, I don't want to login the computer after rebooting. I want everything to work just by pressing the power button on the computer. What should I do to make pulseaudio work in such a case?
I also tried to mount the user socket in /run/user/1000/pulse into container. This works before rebooting. However, after rebooting, the directory /run/user/1000/pulse became empty. I guess this problem relates to container mount binding, but not sure what happened exactly.

In general your setup should just work.
x11docker requests a new pulseaudio socket on every restart. However, maybe the pulseaudio server is not already running when you start x11docker? It should be started automatically after login (or auto-login), and x11docker must start afterwards.
If the issue is elsewhere, you could try --pulseaudio=tcp that does not use a socket but a TCP connection. (x11docker also needs option --network to allow TCP connections.)

In general your setup should just work. x11docker requests a new pulseaudio socket on every restart. However, maybe the pulseaudio server is not already running when you start x11docker? It should be started automatically after login (or auto-login), and x11docker must start afterwards. If the issue is elsewhere, you could try --pulseaudio=tcp that does not use a socket but a TCP connection. (x11docker also needs option --network to allow TCP connections.)

I  think because docker has root privilege, a container restarts before user login and certainly before pulseaudio server starts.
The way I restart a container is through docker run --restart always so the container will restart just after the docker daemon starts.
I guess I will have to make pulseaudio run system wide if I don't want to login.
And the container must start afterwards...but how to make sure this?

The way I restart a container is through docker run --restart always

x11docker always drops the container after use so --restart=always is not possible. Or don't you use x11docker at all for your setup?

I guess I will have to make pulseaudio run system wide if I don't want to login.
And the container must start afterwards...but how to make sure this?

Check the systemd service files. You could start a system wide pulseaudio with a systemd service and add a line like After=pulseaudio.service do the docker service.

Or don't you use x11docker at all for your setup?

Yes, I am using my own image as I don't need everything in x11docker. I was struggling about playing sound in a container until I found your wiki. It is very well written, thanks!

Check the systemd service files. You could start a system wide pulseaudio with a systemd service and add a line like After=pulseaudio.service do the docker service.

This way looks promising, I will give it a try.

Closing for now. If you need further help, just ask.


A11y_AzureExtensionsforVSCode_AzureFuction_DefaultScreen_ColorContrast :The color contrast ratio of keyboard focus on several controls such as "Azure serverless community library" is less than 3:1.

“Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”
GitHub Tags:#A11y_Azure Extensions for VS Code;#Azure Tools for VS Code;#A11yTCS;#A11yWCAG2.1;#MAC;#FTP;#Benchmark;#ColorContrast;#A11ySev2:#WCAG1.4.11;
Environment Details:
Application Name: Azure Extensions for VS Code
Application Version: 1.48.0-insider
Commit: cfbd1999769f4f08dce29629fb92fdc0fac53829
Date: 2020-08-06T05:40:40.871Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.6.0
Operating system: macOS Catalina Version 10.15.6 (19G73)
Screen Reader: VoiceOver
Repro Steps:

Open Visual studio code
Click on extension button and search for "Azure Functions"
Click on install and move to the "Azure" button, the "Default Screen" will appear.
Navigate to several controls such as "Azure serverless community library" using keyboard and verify if the color contrast ratio of keyboard focus is less than 3:1 or not.

Actual:
The several controls such as "Azure serverless community library" has keyboard focus color contrast ratio of 1.5:1 which is less than the standard color contrast ratio of 3:1 which is not appropriate as the users with low vision will have difficulty in understanding the navigation on the screen.
Expected:
The keyboard focus color contrast ratio of "Azure serverless community library" control should be greater than or equal to 3:1.
User Impact:
If the color contrast ratio of the keyboard focus for the contents present on the screen is less than 3:1 then the users with low vision will have difficulty in understanding the keyboard navigation for the controls on the screen.
Attachment link for Reference:

This issue should be filed in the VS Code repo: https://github.com/Microsoft/vscode
Our extension has no control over the theming of links in markdown. For example, you can reproduce the same behavior without our extension. Create a "test.md" file, add markdown for a link, and open the markdown's preview.

Logged bug in VS Code- https://github.com/microsoft/vscode/issues/104553
As per the C & AI bug process assigning the bug to the Product Owner. Please assign this bug back to the tester once the "External" issue has been resolved and changes are pushed to the environment that will be available for bug verification.

Actually I think you selected the wrong colors. This is what I see:


fix: update @asyncapi/optimizer to 1.0.3 version and others

This PR is a clone of https://github.com/asyncapi/cli/pull/1503 created just to pass the frozen automerge mechanism.

I suppose workflow is not able to setup a clean install properly @aeworxet.

Error: node_modules/@types/lodash/common/object.d.ts(1026,46): error TS1005: '?' expected.
Error: node_modules/@types/lodash/common/object.d.ts(1031,46): error TS1005: '?' expected.
Error: node_modules/@types/lodash/common/object.d.ts(1041,46): error TS1005: '?' expected.

is due to this issue
https://github.com/DefinitelyTyped/DefinitelyTyped/issues/69932
I changed
-    "typescript": "4.6.4"
+    "typescript": "^4.6.4"  //  <-- added a caret

and tests started passing.
Does this change break anything?

Does this change break anything?

It should not as ^ is used for backward compatible releases.

Asked just in case. It might had been hard-locked on that version for a reason. :shrug:

/rtm


Drop @lbrycast as a default subscribed channel

and remove it from lbry.tv homepage

@jessopb can you do this today?

nm


Fix tag action

Resolves #429
Preview link

The functionality looks fine on both near.social and near.org! Just one issue, can we make this

reflect the tag clicked?

yeah I was trying to do it yesterday but couldn’t get it working, will try again today, have some new ways in mind.

hey @ailisp it should work now.


Added /uptime and /start-time for all components. Addressed comments and fixed tests from pull request 12389.

Addresses #12298. Added /uptime and /start-time for all components. Addressed comments and verified tests pass from pull request 12389 (Closed that request because the history of that PR got messy). Tested /uptime and /start-time endpoints on my local machine. See the attached images

Codecov Report
Attention: Patch coverage is 16.66667% with 30 lines in your changes are missing coverage. Please review.

Project coverage is 61.68%. Comparing base (59551e4) to head (2ea97f3).
Report is 23 commits behind head on master.

Files
Patch %
Lines

...t/broker/api/resources/PinotBrokerHealthCheck.java
0.00%
7 Missing :warning:

...ller/api/resources/PinotControllerHealthCheck.java
0.00%
7 Missing :warning:

...inot/minion/api/resources/HealthCheckResource.java
0.00%
7 Missing :warning:

...inot/server/api/resources/HealthCheckResource.java
0.00%
7 Missing :warning:

...apache/pinot/minion/MinionAdminApiApplication.java
0.00%
2 Missing :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master   #12512      +/-   ##
============================================
- Coverage     61.75%   61.68%   -0.07%
  Complexity      207      207
============================================
  Files          2436     2449      +13
  Lines        133233   133539     +306
  Branches      20636    20690      +54
============================================
+ Hits          82274    82376     +102
- Misses        44911    45083     +172
- Partials       6048     6080      +32

Flag
Coverage Δ

custom-integration1
<0.01% <0.00%> (-0.01%)
:arrow_down:

integration
<0.01% <0.00%> (-0.01%)
:arrow_down:

integration1
<0.01% <0.00%> (-0.01%)
:arrow_down:

integration2
0.00% <0.00%> (ø)

java-11
34.94% <0.00%> (-26.77%)
:arrow_down:

java-21
61.57% <16.66%> (-0.06%)
:arrow_down:

skip-bytebuffers-false
61.66% <16.66%> (-0.08%)
:arrow_down:

skip-bytebuffers-true
61.53% <16.66%> (+33.80%)
:arrow_up:

temurin
61.68% <16.66%> (-0.07%)
:arrow_down:

unittests
61.68% <16.66%> (-0.07%)
:arrow_down:

unittests1
46.85% <ø> (-0.04%)
:arrow_down:

unittests2
27.68% <16.66%> (-0.06%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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

Do we want uptime in seconds, or in a more human readable format?

Do we want uptime in seconds, or in a more human readable format?

@Jackie-Jiang Xiang in the old PR here was inclined towards returning just a number. I am okay either way

ForwardIndexHandlerTest.testAddOtherIndexForForwardIndexDisabledColumn() is a flaky test. There is an existing open issue - #11928

as inclined towards returning just a number. I am okay either way - don't have a strong preference

I prefer epoch value, UI side can decide how to show it.

Thanks for adding this feature @suyashpatel98 !


How to register as user/applicant ?

On the demo site you have an account for a demo applicant - but where could a real applicant register for such an account. Whereever I try, my default role is always recruiter - and even this should be made clear: Register as an applicant. Or: Register as a recruiter.

This will set the hidden role field in the registration form to "user"
http://yawik.org/demo/de/auth/register/user
This will set the hidden role field in the registration form to "recruiter"
http://yawik.org/demo/de/auth/register/recruiter


Add support for Laravel 11

Hi there,
I think I fixed support for Laravel 11. The most important changes are:

upgraded brick/varexporter version
updated 1 test to reflect changes introduced by Laravel 11 regarding floating point types
updated automated github tests
fixed some small typo's and added info about how to run composer tests

Thank you @dreammonkey! I'm gonna check and merge this on Monday.

@mathieutu haha good you are remembering me! 😁
https://github.com/laracraft-tech/laravel-schema-rules/releases/tag/v1.4.0

And it's already tried, and it works great, thanks!


code for data_loader

Hello! I am very interested for your pretty work. But when I read the code at train_cmdsr.py, I found that the data_loader file did not exist. Could you please upload it? Thanks.

Thanks for reminding us of that. We have uploaded data_loader.py.


wire:click doesnt work for me

I have this button but doesnt work for me.
I have a Module its name is Chat and its inside this module
<button class="btn btn-primary btn-block mb-4" wire:click="createNewChat"> + Create a new Chat </button>

@falahatiali Can you provide the component class and view file source code, please?

@mhmiton yes of course:
my project is inside Chat module.

            <button class="btn btn-primary btn-block mb-4" wire:click.prevent="createNewChat"> + Create a new Chat </button>

            @foreach($chats as $chat)
                {{ $chat->title ?? 'New Chat' }}

            @endforeach

    ```

    ```
    class Home extends Component
{
    public $chats = [];

    public $selectedChat;

    public function mount()
    {
        $this->chats = Chat::query()->get();
    }

    public function selectChat(int $chatId)
    {
        $this->selectedChat = Chat::query()->find($chatId);
    }

    public function createNewChat()
    {
        dd($this);
    }
    public function render()
    {
        return view('chatgpt::livewire.home');
    }
}

    ```

@falahatiali This seems to work. But, it is pretty difficult to find out this issue in this way. So, you can feel free to join with me in discord, so I will try to find out this issue on your pc or source code.
This is my discord id - mhmiton#8254


Keystore is loaded for each passive STS login

Describe the issue:
According to the implementation at [1], it loads the keystore from the file system for each and every login. This could cause a high resource usage. The info log is moved to debug with https://github.com/wso2-extensions/identity-inbound-auth-sts/pull/134, but a better solution to this needs to be implemented.
[1] https://github.com/wso2-extensions/identity-inbound-auth-sts/blob/6dde60db4049633f5cc341309d8eb40ee22660e4/components/org.wso2.carbon.identity.sts.passive/src/main/java/org/wso2/carbon/identity/sts/passive/custom/provider/CustomCryptoProvider.java#L70
How to reproduce:
Login to a passive STS application. The following log will be written for each login.
INFO {org.wso2.carbon.identity.sts.passive.custom.provider.CustomCryptoProvider} - Loading keystore...

Expected behavior:
It should load the keystore once and keep in the cache
Environment information

Product Version: IS 5.11.0 and later

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


prettier dependency and config files

Fix: #22
Prettier should now work and the coding style rules should be the same for everyone.

LGTM


Profile page background

The little tab when you open up a profile page has a fully transparent background, making the text from the channel/dm's clip through and making it hard to read peoples descriptions, about me etc.

This is not a bug, but a feature so i labeled it Enhancement, i can make it a bit darker if you want though


Update Config Documentation

https://github.com/caffeinated/modules/issues/355

Looks good, however, would you mind changing Local and Custom to all lowercase, just so it fits in with the rest of the code base? Once updated I'll merge 👍

Changed to lower case


Semantic model symbol returns empty for constant references

Description:
Semantic model symbol function returns empty for constant references.
Steps to reproduce:

Have the following code

public const TIME_DELTA_START = "TIME_DELTA_START";
public type TimeDeltaStart [TIME_DELTA_START, int];

public type Human record {|
    string HumanName;
    int age = 25;
    KeyAlgorithm algo;
|};
public type KeyAlgorithm RSA;
public const RSA = "RSA";

Get symbol of TIME_DELTA_START in TimeDeltaStart.
Get symbol of KeyAlgorithm in Human record.
Get symbol of RSA in KeyAlgorithm type.
All the above will return null.

Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

The issue here is that when you use a constant when defining a type, it is used as a type. For that usage, we internally create a new typedef with a finite type. When symbol entering the above type defs, it resolves the given constant refs and gets a finite type as the resolved type. We lose the access to the constant symbol.


Empty data from streamsearch not handled properly

When parsing incoming data for multipart uploads, streamsearch sometimes calls the callback with empty data, but busboy changes its internal state by using an invalid byte from the data parameter. In our case, busboy throws Malformed part header on a valid request.
Example consecutive write calls that makes streamsearch callback with empty data:

\r\n
--d1bf46b3-aa33-4061-b28d-6c5ced8b08ee\r\n
Content-Type: application/gzip\r\nContent-Encoding: gzip\r\nContent-Disposition: form-data; name=batch-1; filename=batch-1; filename*=utf-8''batch-1\r\n\r\n

@mscdex any plans on fixing this? do you need more information about this?


Describe Workflow (& other RPCs) with an empty Run ID problems post-run-deletion

Expected Behavior
If you call describe workflow, or get history, etc passing an empty run ID - you should always get results as long as any workflow with the provided workflow ID exists.
Actual Behavior
If you have deleted a run which was continued / reset from a previous run with the same ID, subsequent calls of the kind described above will fail with not found.
Steps to Reproduce the Problem

Start a workflow and have it continue-as-new, or reset it
Complete the new instance
Delete it
Make one of the relevant RPCs with an empty run ID

Specifications

Version: 1.21
Platform: Linux / sqlite

Thank you for reporting this issue. This is a known issue in Temporal 1.21 and is being addressed in a future release.
The issue is caused by the fact that when a workflow is continued or reset, a new run ID is generated, and the old run ID is associated with the new run. However, when a run is deleted, the old run ID is removed from the database, even if the new run is still active. This leads to the "not found" error when you try to query the workflow history using the old run ID.
For now, you can work around this issue by providing the correct run ID when querying the workflow history. You can get the correct run ID by using the DescribeWorkflowExecution API call with the workflow ID and a specific run ID.
For more information on how to use the DescribeWorkflowExecution API call, please refer to the Temporal documentation: https://docs.temporal.io/docs/typescript/client-api/

Thank you for reporting this issue. We appreciate your help in making Temporal better!
This behavior is expected. You can find further details and how to work around this in the Workflow Execution Documentation.
The documentation explains that when a workflow is continued or reset, Temporal creates a new workflow execution with the same workflow ID but a different run ID. This means that even after deleting the new execution, the information about the previous executions with the same workflow ID still exists in Temporal.
If you need to access information about all executions with the same workflow ID, including the deleted ones, you can use the ListWorkflowExecutions API call.
Let me know if you have any further questions.

Thank you for reporting this issue. We understand the behavior you're experiencing is unexpected.
It seems like the issue arises due to the deletion of a continued/reset workflow run while using an empty run ID in API calls. This is not the intended behavior.
We have documented this as a known issue in Temporal Issue Tracker.
We are actively working on a fix for this and will update you once it's available. In the meantime, as a workaround, you can use the workflow ID and the run ID of the workflow run you want to inspect instead of using an empty run ID.
Please let us know if you have any further questions.

Thank you for reporting this issue. I understand that when you call describe workflow, get history, etc. with an empty run ID after deleting a continued/reset workflow run, you're encountering a "not found" error.
This behavior is a known issue, and it's being addressed in Temporal issue #4350.
In the meantime, you can work around this issue by explicitly specifying the run ID of the workflow you're interested in. You can retrieve the list of runs for a given workflow ID using the list_workflow_executions API, which is described in Temporal's Workflow Service API documentation.


Flicker and changes to window layout on loclist update

When locationlist is already opened, and g:neomake_open_list=2 the window layout flickers or even changes on subsequent async updates to the list.
Expected behavior
After the inital change of layout when the list opens, no further changes (or flicker) of the window layout (until the window is completely empty and closes)
Steps to reproduce
Let g:neomake_open_list=2. Open some multi-window layout. Run :Neomake repeatedly in the same window/buffer.

Cannot reproduce / need more info.
I have tried the following with a minimal vimrc:
set runtimepath+=$PWD
let g:neomake_logfile = '/tmp/neomake.log'
let g:neomake_open_list = 2

:let maker = {'exe': 'bash', 'args': ['-c', 'echo 1:1:$RANDOM; sleep 5; echo 1:2:$RANDOM'], 'errorformat': '%E%m'}
:let maker2 = {'exe': 'bash', 'args': ['-c', 'echo 2:1:$RANDOM; sleep 3; echo 2:2:$RANDOM'], 'errorformat': '%E%m'}
:call neomake#Make(1, [maker, maker2])

First the results from maker2 get added, then maker.
Running it several times does not change that (and previous jobs/make runs get aborted).

I use the clint maker as defined in https://github.com/tweekmonster/nvimdev.nvim/blob/master/autoload/nvimdev.vim
and run :Neomake on every BufWritePost.
The issue seems to be that :Neomake immediately closes the location window, instead of giving the linter some time to update it. Is this indended behavior? Perhaps there should be an option to set a timeout before closing the window.

Still cannot reproduce it using:
set runtimepath+=~/src/neomake
set runtimepath+=~/.vim/plugged/nvimdev.nvim/
set runtimepath+=~/.vim/plugged/vim-qf/
let g:neomake_logfile = '/tmp/neomake.log'

let g:neomake_open_list = 2

augroup my_neomake
  autocmd! BufWritePost * Neomake
augroup END

(tried it with and without vim-qf which might interfere here)
The log:
15:52:38 [D +16.1] [6.-:1] Running makers: lint.
15:52:38 [D      ] Skipping User autocmd NeomakeCountsChanged: no hooks.
15:52:38 [V      ] [6.6:1] Starting async job: ['/home/daniel/Vcs/neovim/src/clint.py', '--suppress-errors=/home/daniel/Vcs/neovim/tmp/errors/src/nvim/event/process.c.json', 'src/nvim/event/process.c'].
15:52:38 [D      ] [6.6:1] cwd: /home/daniel/Vcs/neovim.
15:52:38 [D +0.18] [6.6:1] stderr: lint: ['src/nvim/event/process.c:24:  /*-style comment found, it should be replaced with //-style.  /*-style comments are only allowed inside macros.  Note that you should not use /*-style comments to document macros itself, use doxygen-style comments for this.  [readability/old_style_comment] [5]', 'src/nvim/event/process.c:278:  /*-style comment found, it should be replaced with //-style.  /*-style comments are only allowed inside macros.  Note that you should not use /*-style comments to document macros itself, use doxygen-style comments for this.  [readability/old_style_comment] [5]', 'src/nvim/event/process.c:286:  Inner expression should be aligned as opening brace + 1 (+ 2 in case of {)  [whitespace/alignment] [2]', 'Total errors found: 3', ''].
15:52:38 [D      ] [6.6:1] exit: lint: 1.
15:52:38 [D      ] [6.6:1] lint: processing 4 lines of output.
15:52:38 [D      ] [6.6:1] Creating location list.
15:52:38 [D      ] [6.6:1] Processing 3 entries.
15:52:38 [D      ] File-level errors cleaned in buffer 1.
15:52:38 [D      ] Reusing sign: id=5000, type=neomake_warn, lnum=286.
15:52:38 [D      ] Reusing sign: id=5001, type=neomake_err, lnum=278.
15:52:38 [D      ] Reusing sign: id=5002, type=neomake_err, lnum=24.
15:52:38 [D      ] Skipping User autocmd NeomakeCountsChanged: no hooks.
15:52:38 [D      ] Handling location list: executing lwindow.
15:52:38 [D      ] [6.6:1] lint: completed with exit code 1.
15:52:38 [D      ] [6.6:1] Cleaning jobinfo.
15:52:38 [D      ] Skipping User autocmd NeomakeJobFinished: no hooks.
15:52:38 [D      ] Cleaning old signs in buffer 1: {}.
15:52:38 [D      ] Handling location list: executing lwindow.
15:52:38 [D      ] Skipping User autocmd NeomakeFinished: no hooks.
15:52:38 [D      ] [6.-:-] Cleaning make info.

The location list opens once and I can notice no closing/flicker when it gets refilled.
When adding redraw | sleep 1 after the setloclist() that cleans it in https://github.com/neomake/neomake/blob/991a6faed3c388a3f41bb6ce4307915a7f7b902a/autoload/neomake.vim#L1226 I will be empty for a second.. maybe that corresponds to what you are seeing in some way though?
But emptying/creating the location list should happen just before filling it, so I speculate that some autocommand is interfering here on your side?!

Are you using g:nvimdev_autorun_neomake = 1?
Do you have Neomake multiple times in au BufWritePost?

No, once. Also it happens when invoking manually :Neomake so should be unrelated to autocommands. I have none that triggers on qf/loc events, no other plugins than neomake that should care about the loclist but I'll double-check later.

There have been changes in this regard, so I assume it might have been fixed.
Otherwise, please re-open and provide logging output for when it happens.
Also note that nvimdev has received several fixes lately.


Support non-string variables

The latest schema for porter.yaml supports a new template format, ${bundle.parameters.NAME}, that allows Porter to inject non-string values into a mixin field, such as a number or boolean.
The terraform mixin is assuming that all variables were defined as strings, which causes the wrong value to be printed for vars when translated to a CLI call
terraform destroy -auto-approve -input=false -var address_space=<IP_ADDRESS>/24 -var create_aad_groups=%!s(bool=false) -var shared_storage_quota=%!s(int=50) -var tre_id=tk20a

In the example above, shared_storage_quota was specified as an integer, and create_aad_groups a bool, so we are seeing a Go string replacement error printed out
The error seems to be originating from this line, though we should look for more go format strings with %s used.
https://github.com/getporter/terraform-mixin/blob/f8d1d35afcb875d5e65a637396109afb727d7d47/pkg/terraform/uninstall.go#L30

Fixed by #101


Automatically select dark or light theme

Instead of editing the CSS to add an include, automatically select the dark or light theme.
It can probably be keyed based on the window element with a specific attribute like:
window[lwthemetextcolor="bright"]

...for dark mode
and
window:not([lwthemetextcolor="bright"])

...for light mode.
There might need to be more matches; I didn't test this for native light/dark themes, only the switch in customize.

That would certainly be useful, but at this point we already have 3 theme variants (and there will be more, because of different GNOME versions), as well as a few extra options like client-side decorations settings and symbolic icons, which means some options would have to be enabled in the CSS file anyway. Besides, switching those built-in themes currently breaks too much of existing code and it wouldn't be possible to switch between different variants without restarting Firefox anyway, because that theme relies on GTK styles for popup menus, text colors in some places, icon colors, etc. I just tested it and it doesn't seem to work for native theme variants, window doesn't have any attribute indicating current GTK theme variant either. So for now I'm not gonna implement this, maybe in the future if we manage to make it more config-less (assuming it's possible to detect or ditch GTK styles).
By the way, our existing config evolved recently, thanks to issue #14 it's possible to preserve theme configuration between updates by saving it to the customChrome.css file, so I think it became slightly less annoying.


Update fs2-core to 2.0.0

Updates co.fs2:fs2-core from 1.0.5 to 2.0.0.
Release Notes/Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention @scala-steward in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "co.fs2", artifactId = "fs2-core" } ]

labels: semver-major

Codecov Report

Merging #1153 into master will decrease coverage by 0.09%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master    #1153     +/-   ##
=========================================
- Coverage   80.61%   80.51%   -0.1%
=========================================
  Files          54       54
  Lines        1016     1016
  Branches       32       32
=========================================
- Hits          819      818      -1
- Misses        197      198      +1

Impacted Files
Coverage Δ

core/src/main/scala/io/finch/Endpoint.scala
72.57% <0%> (-0.58%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 42c4a2d...24ccdad. Read the comment docs.


How to get the resolved rename range, or should we drop range?

Testing #48409
After resolving a rename location, there is no direct way to get the returned range. It's possible for extension author to save the range somewhere and retrieve it in provideRenameEdits, but this seems cumbersome.
This API naming pattern is similar to CompletionItemProvider but work in the reverse way. Originally I thought it would resolve the range for the returned edit from provideRenameEdits.
I think an alternative might be
resolveRenamePlaceholder?(document: TextDocument, position: Position, token: CancellationToken): ProviderResult<string>;

The range is not being used by VS Code anyway. Dropping it would make it clear it's the extension author's responsibility to provide range in provideRenameEdits. He can run document.getText(range) to get the placeholder text.
@mjbvz Also what's your thoughts since you are testing this too?

Yes, I also did not understand how range was used when first trying to implement the API. Maybe the resolved rename context (range and placeholder) should be passed on provideRenameEdits, like we do for CompletionContext

save the range somewhere and retrieve it in provideRenameEdits, but this seems cumbersome.

Why would you want that? The language brain should be able to compute the range of symbol at a position, even two times in a row. The resolve-call is only to support the UI so that it can decide how to position the input-widget. I don't see a reason to feed that range back to the provider.

Talked to @kieferrm and we believe part of the confusion might be the name. We figure we can tackle this in two steps

For April: rename the resolveRenameLocation-function to prepareRename
For later ( and optionally) pass the result of rename to the provideRenameEdits-function.

The latter should only be needed when computing the location/range (or some other yet unknown piece of information) is very expensive and shouldn't be repeated. Then we can use the XYZContext-trick.


Create Zx

 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.

Hi
@Alan-yly
We are grateful for your efforts in helping improve this open-source project during your personal time.
Welcome to join OpenMMLab Special Interest Group (SIG) private channel on Discord, where you can share your experiences, ideas, and build connections with like-minded peers. To join the SIG channel, simply message moderator— OpenMMLab on Discord or briefly share your open-source contributions in the #introductions channel and we will assist you. Look forward to seeing you there! Join us ：https://discord.gg/UjgXkPWNqA
If you have a WeChat account，welcome to join our community on WeChat. You can add our assistant ：openmmlabwx. Please add "mmsig + Github ID" as a remark when adding friends：）
Thank you again for your contribution❤


Core: standardize the use of Clock

Upstream https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/issues/1364
Standardize the use of Clock in the codebase, rather than constructs like Instant.now() which cannot be mocked easily. The Clock could be provided centrally.
Acceptance criteria

[x] No use of new Date(), Instant.now() or similar in runtime code.
[x] Single instance of Clock in shared context, also used for mocking.
[ ] ADR

Tasks

[x] Create Single instance of Clock in shared context
[x] Replace use of new Date(), Instant.now() or similar in runtime code, with shared Clock

Two PRs were merged upstream, ADR PR is still outstanding


Update 2.1 to March Release

Intermittent #1449 failures for osx

Ready for review.

Ready for review.


Replace Upcoming listing w/ a weekly highs and lows temperature graph and an aligned table for other data

I've changed the interface for Upcoming forecast to a more dense and glanceable tabular and graphical format.  Find attached a screenshot belo.  I wonder if I should

keep the old UI and add the graph as an optional UI (enable via variable)
keep the old UI, but make the new one default (revert via variable)
get rid of the old UI and go with the new one

I haven't pushed the relevant changes upstream yet.

The tabular/graphical format is much better.  I would keep the old UI, but make the new UI the default.


Question of supplemenent document

First of all, I was impressed by the great research.
I would like to implement and use these models myself, but I do not know how to do it.
Did you label the fog point separately by making such an image?
I'd like to hear a specific explanation.
Also, what should I do if I want to use those models?
In addition, I wonder if LiDAR-Only SSD used 2D Detector or 3D Detector. If there is a ref code, can you tell me?
I'll wait for your answer. Thank you in advance.

@Youngsplace0913: Where did you find this image? I can't find it in the supplementary materials.


chore: upgrade dependencies in superchain image

The Debian 10 image uses Python 3.7 which was causing failures elsewhere due to required minimum python 3.8. Debian 10 is also ten months out of security support so upgrading it seemed like the right decision here. This change also updates Node to 16 due to Node 14 being EOL.

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

The image tagging also needs to be updated...

Superseded by #4195


Call MobileAds.initialize on background thread

The Google Ads team now recommends calling MobileAds.initialize on a background thread to avoid ANRs.
Currently, this Plugin calls MobileAds.initialize on the UI thread.
https://github.com/googleads/googleads-mobile-flutter/blob/8e0834ee7f9b8f0ac1b886c5b3cae8937835c605/packages/google_mobile_ads/android/src/main/java/io/flutter/plugins/googlemobileads/GoogleMobileAdsPlugin.java#L349
https://github.com/googleads/googleads-mobile-flutter/blob/8e0834ee7f9b8f0ac1b886c5b3cae8937835c605/packages/google_mobile_ads/android/src/main/java/io/flutter/plugins/googlemobileads/FlutterMobileAdsWrapper.java#L39

Hi @blaugold, thanks for flagging. I've shared this with engineering to determine next steps.

Is there any workaround we can do on the flutter side while this lib is not updated? Can we call MobileAds.initialize in another Isolate safely?

Hi @Gilianp, we have a PR in the works https://github.com/googleads/googleads-mobile-flutter/pull/1165 that will be included in the next version. Please see until it's submitted

Hi @Gilianp, we have a PR in the works #1165 that will be included in the next version. Please see until it's submitted

Thanks @malandr2 , I will wait the next update!

I saw that this is implemented on the example folder:
<meta-data
    android:name="com.google.android.gms.ads.flag.OPTIMIZE_AD_LOADING"
    android:value="true" />

https://github.com/googleads/googleads-mobile-flutter/pull/1172/files#diff-ff9e788ea8dece69ea4d0ca791b99ba327608e161b3f5b4aa0c94245e3012652
This shouldn't be added into the plugin android manifest too ?
Otherwise everyone will have to implement this manually.

Hi @marcellocamara, those flags are optional. They are needed if you're not calling MobileAds.initialize on a background thread. When the google_mobile_ads plugin adds the background thread functionality, these flags will no longer be needed in our samples. See https://developers.google.com/admob/android/optimize-initialization#update_your_manifest_file for more details

This has been resolved in https://github.com/googleads/googleads-mobile-flutter/pull/1179 and will be included in the next release .5.2.0

@LTPhantom thanks
is that, seems there is InitializationStatus return, or related,
so the (my) app shouldn't await MobileAds.instance.initialize()?
thanks


Update docs on workflows to add new label changes

Labels were changed as mentioned in a new post (https://medium.com/filecoin-plus/ldn-label-update-part-1-label-consolidation-ae2691c78702). We need to update the docs to reflect that change.
Docs file affected: https://github.com/FilecoinPlus/docs/blob/main/docs/reference/processes-and-workflows.md

From the post, the list of changes seem to be:

Changed from
Changed to

Bot: Ready To Sign
ready to sign

bot:reviewNeeded
governance review needed

Efil+
efil+

issue:TotalDcReached
total datacap reached

state: Validated
validated

state:Granted
granted

state:StartSignDatacap
start sign datacap

status:Granted
granted

status:StartSignDatacap
start sign datacap

Error labels
error


Update web-frameworks.md

Line 200: Changed the message displayed in browser to: Hello World! I'm using Flask. as per example ( see line 173 )

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

@mattwojo - can you take a look? Thanks.

@mattwojo - can you take a look? Thanks.

Thanks @vikrambhogiraju!

Thanks @vikrambhogiraju!


Weird cursor jumps

Challenge Use Spans for Inline Elements has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
This issue has been going on for the last couple of challenges. The cursor jumps around when trying to start the challenge. I will click where I want to type. The cursor will be a few spaces back from where I clicked, so I try to type something. my input appears a line below where I clicked. Its not until I click, type something, and delete it that everything works as it should. Not a huge issue or anything, but distracting.

+1

Happens to me too.

@TheCodeJones @Brayn7 @techtolentino @Will-Campbell
Thanks for confirming this. Unfortunately I have not been able to reproduce this. Could you help us with below information to get started in resolving this:

Location : Where are you located (region) ?
Can you have any GIF recordings/Screenshots anything that can help us understand this better.
Can you check your console for any errors?

On your browser open the Dev Tools (Press F12) and go to the Console tab.
Refresh the page, and try to reproduce the error.
Post the screenshot of the console and network tabs.

Any other information that you could provide.
Sincere apologies for the inconvenience, and thanks for your patience and help in resolving this.

/cc @FreeCodeCamp/issue-moderators

This is a known issue with Code Mirror, the software we use to edit code for our challenges.  This occurs when there are long lines of code and they wrap.  There are supposed to be fixes in newer versions of Code Mirror.
Ref: https://github.com/codemirror/CodeMirror/issues/1862

@SaintPeter Thanks! So I guess we are blocked by this.

+1

+1

This manifested for me as seemingly not being able to click or move the cursor (even using arrow keys) to the last line of my code.

So will this be fixed here soon if it's related to that Code Mirror bug?
I switched from my Surface to PC (where font size/scaling is all default) and tried all my browsers trying to fix it until I saw this thread.
I narrowed it down to occurring when the pre-filled code in the code box is long enough that a scroll bar is added (to the code box). Because it starts happening to me from "Add Placeholder Text to a Text Field" where the scroll bar appears. Just having lines of code that wrap don't seem to cause it because lines wrapped in the lessons prior to this one.
When the scroll bar is there I can't click certain parts of the code (on this stage it's very evident because I can't click where I need to to add the required code). The cursor jumps to some weird place instead. Arrow keys can't even get me where I need to go as mentioned above.
The easiest way I've found to get around this bug is just to click somewhere it lets me and hit the spacebar so I've typed something... then I can correctly click anywhere in the code.
It's not a show stopper, easy to get around, but between this and #3204 I've lost a couple hours on bugs in this code editor and I'm not very far in. I'm a bit worried of what's to come.

Please follow the codemirror issue here https://github.com/codemirror/CodeMirror/issues/1862

@Kahldris thank you for mentioning how you get around it. I didn't think to try anything like that.

+1

Tried @Kahldris suggestion of zooming in and out (ctrl + "+", ctrl + "0") as a temporary fix which allowed me to get past this.

Started on "Use Spans for Inline Elements". It skips over the text that I need to edit to move on . . . can't do anything about it.

@smartestprimate  worked for me too, thanks!

+1

This issue is still a thing, apparently.


How to Get Rows Updated when executing Insert Command

I am trying to insert a record in to table using select statement and I want to know how many records inserted. I am not able to get the results using cursor. Is there any other ways to get number of records affected in ODBC

#16 has been merged and released. Does this help your use case?

We need some additional work on odbc-safe and odbc crates, but looks like all work here is done, thanks


Update kubernetes dependencies

Description
Changes proposed in this pull request:

Upgrade kubernetes dependencies to v1.20.11 because
The large block of replacements for kubernetes dependencies is due to the fact that kubernetes sets some requirements to version v0.0.0

 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.

/retest

/remove-hold

/hold

/remove-hold

Looks like I am not code owner of all three files.


Example incorrect

Describe the Change You Would Like
In your example, you say that out::message should return an object:
[
  {
    "target": "target0",
    "action": "task",
    "object": "package",
    "status": "success",
    "value": {
      "status": "uninstalled",
      "version": ""
    }
  }
]

When I try this from Puppet Enterprise, the console reports the error:
Plan output

{
  "msg" : "'out::message' parameter 'message' expects a String value, got ResultSet",
  "kind" : "bolt/plan-failure",
  "details" : {
    "class" : "Bolt::PAL::PALError"
  }
}

This suggests there are differences or changes that need to be highlighted in the documentation.
The section of documentation I refer to is: https://puppet.com/docs/bolt/latest/writing_plans.html#using-outmessage-to-debug-a-plan

plan website::test(
TargetSpec $targets
) {
$check_mysql = run_task('package', $targets, "Check for MySQL", {'action' => 'status', 'name' => 'mysql'})
out::message($check_mysql)
}

The specific line: out::message($check_mysql)
Thanks

Hello! That's probably because the version of PE you have is using an older version of Bolt from before we had added outputting objects instead of just strings. You can see which version of Bolt is running in PE here, and see the documentation for debugging using out::message in PE here which indicates to pass out::message a string.

@lucywyman ,
Thank you for your reply. You closed it before I had a chance to reply. I am pretty sure this is not the case. I am running the very latest version of PE (2019.8.4).
Plan
plan base_windows::testplan (
  TargetSpec $targets,
  Optional[String] $contents = undef,
  String $filename,
){
  $targets.apply_prep

  $apply_results = apply($targets, '_catch_errors' => true) {
    class { 'base_windows::testpp':
      filename => $filename,
      contents => $contents,
    }
  }

  #return $apply_results

   $apply_results.each |$result| {
    $target = $result.target.name
    #notice( "testplan result: ${target}, ${result}")

    if $result.ok {
      notice("${target} returned a value: ${result.value}")
      out::message("${target} returned a value: ${result.value}")
    } else {
      notice( "${target} errored with a message: ${result.error.message}")
      out::message( "${target} errored with a message: ${result.error.message}")
    }
  }
}

Error in PE console:
Plan output

{
  "msg" : "Evaluation Error: Unknown function: 'value'. (file: /opt/puppetlabs/server/data/orchestration-services/code/environments/development/modules/base_windows/plans/testplan.pp, line: 42, column: 51)",
  "kind" : "bolt/plan-failure",
  "details" : {
    "class" : "Bolt::PAL::PALError"
  }
}

(line 42 = notice("${target} returned a value: ${result.value}"))
Thanks

@woter1832 The apply function returns ApplyResult objects, which have a different set of functions than Result objects. You can see the available functions here: https://puppet.com/docs/bolt/latest/bolt_types_reference.html#applyresult

Oh, I see, that's a very understandable mistake! That's because ApplyResult objects don't have a value() function - you might want report() or to_data() (data type reference here). We should definitely catch folks calling value() on that and either return the report or error and say you probably mean report. I'll reopen this for that work!


react-data-grid dependency issue

When I try to add the react-data-grid widget to the developer version (rc3), this error shows:

It seems the import argument:
import * as ReactDataGrid from "react-data-grid";
in the widget.tsx is trying to look for the react-data-grid package under "client" rather than widget's own directory.

@yiweima I think the issue here is that you did not yet run npm install within the widget folder. This is different from the other sample widgets where the rest work out of the box, but this is actually the point of this sample to show how you can create a widget that has a third-party dependency installed via NPM.


HWKAPM-862 : Fix SVG diagrams when using browser zoom

@ammendonca Looks good to me - just checking, I still get the issue on the service UI where the bottom chart goes outside the scope of the card - is that still to be fixed?

That's unrelated to this issue (although being evidenced more when using browser zoom), I'll try to fix it in a separate PR.

@ammendonca Ok good. Thanks!


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.4.133",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3ecd228c636ee17c14662729737fa07242a93cb0"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "3ecd228c636ee17c14662729737fa07242a93cb0",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "mISDN: fix possible use-after-free in HFC_cleanup()\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.4.133 by commit 3ecd228c636ee17c14662729737fa07242a93cb0. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001356


Added Korean language support

For #11
Added koKR.js for korean. Uses shortened weekday abbreviations with full month names.

Same problem from #24 .

The problem has been addressed


Is there a way to have the split change just visibility of the as-split-area and not resize their contents?

I'm  trying to use this for a split between a before-and-after image comparison.
Something like the splitter seen on this page; https://topazlabs.com/

Hi @ramonjsantiago,
Your case is interesting,
this is not the purpose of this library but I will see if I can code an example using current version..

I ended up doing this by hand instead of using angular-split.
My Use Case is this; A top panel with a non-resizeable ESRI map, a bottom panel with Google Street View that does need to resize.
I was able to make the top panel's contents not-resize, but then I also need all events to be passed to the ESRI map.

Yes I understand, that's a better solution to code it than twist angular-split to your usecase..


Add api-documentation for trip plugin

hi @morganherlocker,
i heard that you're maintaining the api-documentation so i didnt just want to push something to the branch :) this is an issue to not forgot to write an api-doc for the trip plugin.
Here's what I already wrote and what might be reusable:
========================
osrm.trip
Calculates a short roundtrip that visits every given coordinates
Parameters

coordinates Array<Array<Number>> The point to match as a latitude, longitude array.

Examples
var osrm = new OSRM('berlin-latest.osrm');
var options = {
    coordinates: [[52.542648,13.393252], [52.543079,13.394780], [52.542107,13.397389]]};
osrm.trip(options, function(err, response) {
    if(err) throw err;
});

Returns TripResult.

This is perfect @chaupow. I'll add this to the source comments.

TODO: This needs to be picked up again when documentjs based docs get merged.

Going to close this since our API doc (https://github.com/Project-OSRM/node-osrm/blob/develop/API.md#osrmtrip) has this. Let's discuss documentation.js push at https://github.com/Project-OSRM/node-osrm/issues/149


Improve error handling when parse plist file

The error is mis-leading. The plist file may exisits but in a format that we cannot parse(such as binary plist) leads to error like invalid byte sequence in UTF-8.
We need to handle this properly and output the correct error so user won't confuse.

Checklist

[ ] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[ ] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context

Description

I signed it!

Also it looks like you need to run bundle exec rubocop -a or manually get rid of some whitespace.


Fixing metrodr check in precheck script while validating CSI configmap

This PR fixes the bug in the check for 2.6.1 metrodr system as listed in the issue : https://github.ibm.com/ProjectAbell/abell-tracking/issues/36551

Test results:
Kept the check for metrodr 2.8.0 system as no metrodr 2.6.1 system was available for testing
======================================================================================
                        ****** Verify Presence of CSI Configmap ******
======================================================================================

INFO: Verify presence of CSI configmap if it is a 2.8.0 MetroDR setup
INFO:   ✅ CSI Configmap with required values present on 2.8.0 metrodr setup

========================================================================================
Healthcheck for IBM Storage Fusion HCI cluster completed at 2024-05-15 +0530 01:38:51 AM
========================================================================================

@anushkajaiswal22 but we need check working on 2.6 too

@ganshug do we have any setup available for 2.6.1 currently to test this?


updated app.properties

Description
Updated app.properties file
All pull requests should be related to open issues. Indicate the issue(s) bellow and remove this line:
Fixes #12
How Has This Been Tested?
Please describe in detail how you tested your changes.
Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code etc.
Screenshots (if applicable, else remove this line / section)
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have added necessary inline code documentation
[ ] I have added tests that prove my fix is effective and that this feature works
[ ] New and existing unit tests pass locally with my changes

Done.


Limit chrono version to avoid test failure

Chrono 0.4.32 introduced a breaking change which cause our tests to fail. Avoid using the new version until chrono is fixed.
Pre-review checklist

[ ] I have split my patch into logically separate commits.
[ ] All commit messages clearly explain what they change and why.
[ ] I added relevant tests for new features and bug fixes.
[ ] All commits compile, pass static checks and pass test.
[ ] PR description sums up the changes and reasons why they should be introduced.
[ ] I have provided docstrings for the public items that I want to introduce.
[ ] I have adjusted the documentation in ./docs/source/.
[ ] I added appropriate Fixes: annotations to PR description.

Closing, succeeded by #918

Closing, succeeded by #918

I think you meant https://github.com/scylladb/scylla-rust-driver/pull/919 instead. Anyway, #919 was merged, so I'll actually close #918 (this PR) right now.


Fallback to the vpn-shoot pod if cluster is not reconciled

How to categorize this PR?

/area networking
/area operations
/kind bug
/priority normal
What this PR does / why we need it:
Fallback to the vpn-shoot pod if cluster is not reconciled
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
With #2251 the vpn health check was made to rely on the label type on the tunnel pod, but this health checks is failing for cluster that are still not reconciled with gardener v1.6.x.
Release note:

The health check for the tunnel pod is now falling back to the `vpn-shoot` pod if no pod labeled with `type=tunnel` is found.

/title [rel-v1.6] Fallback to the vpn-shoot pod if cluster is not reconciled


The rows of textarea be unchanged by JQ in IE

We want to change the rows of textarea by jquery in IE browser, but textarea‘s height  can not take effect in time.We need to click on this textarea to get the focus, then it's height can be changed. So how would we go about solving this problem？

Steps to reproduce:

Open this url http://getbootstrap.com/css/#textarea
Find the textarea control and open DevTools
Change rows attribute , but it dose not work

Platform: Windows 7, iE 11.0.9600, Bootstrap 3.3.7

For "how-to" type questions (rather than feature requests and bug reports) please use StackOverflow or similar. See https://github.com/twbs/bootstrap/blob/master/CONTRIBUTING.md#using-the-issue-tracker


vite-plugin-istanbul SSR is not supported?

when i use vite-plugin-istanbul in SSR project,Some dom will be lost, How should I handle this problem?

Hi @sunnywanggit, thanks for the issue.
An issue with Nuxt was just resolved #63  and released as version v4.0.0-rc.1.
And from the text you provided there is not anything I can use to reproduce the issue.
Please provide a repository with a project i can run or at least provide the setup you have and what errors/expected case you have.
Thank you

WoW, thank you very much, v4.0.0-rc.1. solved my problem.


Update Readme.md Introduction - no 'database' option in sample code

The database option is in no way necessary, but I guess it can't hurt to have it in the example.


Consider using sbt-mima to mechanically verifying we're not breaking bincompat.

I had a look and didn't see this mentioned in any issue, pull request or mailing list thread.
Thoughts?

I've not personally setup sbt-mima before, and I'm not intimate with sbt's build, but I'm willing to have a go at this, but I guess with precompiled what-not I'll hit complications..

The problem is that with 0.13 codebase the boundary between internal implementation vs API is blurred, so we occasionally do break the bincompat. For 1.0 code base I really hope we can do MIMA or publish API JAR so compatibility is enforced by the type system.

I understand, but doesn't that mean just adding exceptions as a part of the relevant pull request?

You're right, and we can time-box and try it, but ultimately, if we had X hours I think the effort would be better spent on modularizing 1.0 code base.

So from the conversation on gitter, we don't want to do this until 1.0, as it'll be more of a burden to maintain and workaround in 0.13, given the legacy state of 0.13.
So I've pushed out what I was working on https://github.com/dwijnand/sbt/tree/add-sbt-mima, and labeled this for 1.0, as I think we should have this done by the first final 1.0 release.


Missing cursor icon.

On these divs:

If you hover your mouse over the twitter ones, they're a pointer (finger-clickable icon).  If you hover over ours, they're a text-input bar.
Hint: These should be links, not div/spans (especially as they're primary purpose is the "link" outward to load content/etc.").

@Watercrystal


UseNativeDriver is now a required prop for Animated

See the React dev blog. Currently this is an annoying warning but might actually break something in the future
https://reactnative.dev/blog/2017/02/14/using-native-driver-for-animated
repro steps:

Use the component in debug mode
Observe annoying warnings

Looks like there's an underlying issue which needs fixing first:
https://github.com/react-native-community/react-native-modal/issues/163

This is what worked for me.
`
import React, { useEffect, useRef } from "react";
import {  Animated, StyleSheet, View, } from 'react-native'
const Ball = (props)=>{
const position = useRef(new Animated.ValueXY(0, 0)).current;
useEffect(() => {
Animated.spring(position, {
toValue: { x: 200, y: 500},
friction: 1,
useNativeDriver: true,
}).start();
}, []);
return (
    <Animated.View style={{  transform: position.getTranslateTransform()  }}>
        <View style={styles.ball}/>
    </Animated.View>
)

}
const styles = StyleSheet.create({
ball: {
height: 60,
width: 60,
borderRadius: 30,
borderWidth: 30,
backgroundColor: '#3a78cf',
color: 'blue',
},
});
export default Ball
`

This is what worked for me.
`
import React, { useEffect, useRef } from "react";
import {  Animated, StyleSheet, View, } from 'react-native'
const Ball = (props)=>{
const position = useRef(new Animated.ValueXY(0, 0)).current;
useEffect(() => {
Animated.spring(position, {
toValue: { x: 200, y: 500},
friction: 1,
useNativeDriver: true,
}).start();
}, []);
return (
    <Animated.View style={{  transform: position.getTranslateTransform()  }}>
        <View style={styles.ball}/>
    </Animated.View>
)

}
const styles = StyleSheet.create({
ball: {
height: 60,
width: 60,
borderRadius: 30,
borderWidth: 30,
backgroundColor: '#3a78cf',
color: 'blue',
},
});
export default Ball
`

To hide this warning
import {LogBox} from 'react-native';

LogBox.ignoreLogs(['Animated.event now requires a second argument for options']);

Context:
By default there is used {nativeDriver: false} so our code will work.
There is patch in neact-native-gifted-chat that was described in.
https://github.com/FaridSafi/react-native-gifted-chat/issues/2124
https://github.com/FaridSafi/react-native-gifted-chat/issues/1924
There is patch for this lib
https://github.com/FaridSafi/react-native-gifted-chat/issues/1825#issuecomment-718463680


Update Dockerfile and config.py to align with renamed sample.config.toml

This commit updates the Dockerfile and config.py to reference the newly renamed configuration file (from config.toml to sample.config.toml).

For me I modify the docker-compose.yml to add a link to config.toml with volume
  devika-backend-engine:
    build:
      context: .
      dockerfile: devika.dockerfile
    expose:
      - 1337
    ports:
      - 1337:1337
    environment:
      - OLLAMA_HOST=http://IP_OLLAMA_SERVER:11434
    healthcheck:
      test: ["CMD-SHELL", "curl -f http://localhost:1337/ || exit 1"]
      interval: 5s
      timeout: 30s
      retries: 5
      start_period: 30s
    volumes:
      - /srv/docker-data/devika/config.toml:/home/nonroot/devika/config.toml
      - devika-backend-dbstore:/home/nonroot/devika/db
    networks:
      - devika-subnetwork

and It's normal, https://github.com/stitionai/devika/pull/197 replace it by sample.config.toml.
So you need to create config.toml before launch docker build.
And my modification to docker-compose.yaml permit to modify the config whitout reconstruct the docker image

@rohittp0 Yes. It make sense.


Fix Start-PSBuild -SMAOnly with the latest dotnet cli

dotnet starts to error out because runtime is passed
I was trying to find a good place in the docs to document Start-PSBuild -SMAOnly, but cannot find it. @SteveL-MSFT do you have suggestions?

Fixes #3924

@vors we should probably have comment based help

Yes, probably that's the right way to go about it.
Does this PR need any changes?


Refactor CLI client

Sorry about the giant diff.
Refactor the library.

Introduce a new class, hca.util.SwaggerClient, that manages a
Swagger API connection client and dynamically generates the client
bindings and CLI parser for any Swagger API given to it. The only
user of this class is currently hca.dss.DSSClient.

The class takes only the Swagger definition URL as its
configuration, and caches the API definition in the user config
directory after the first run. This allows dynamic configuration of
API endpoints and other API parameters. Any higher level commands
that should be added on top of the API bindings can be defined as
methods in hca.util.SwaggerClient subclasses, and added to the
commands attribute.

In the new class, enable a new transport subroutine. It is a wrapper
around Requests, as before, but now it allows explicit, idiomatic
control over pagination, streaming, and authentication.

The new class enables better autodoc generation. Run make docs;
open _build/html/index.html to see the updated autodocs.

Remove code generation machinery.

Connects to https://github.com/HumanCellAtlas/data-store/issues/468
Connects to https://github.com/HumanCellAtlas/data-store/issues/531
Fixes #36, #56, #60

@Bento007, I have added a test case for the paginator.


Refactoring

Hi, sorry if this is a silly question, but I'm trying to port Navigation into a project on Net Framework 4.8. I'm using vs2022 and resharper, not sure what it's about, but I see a lot of warnings like:
"CS8603 Possible null reference return."
"CS8625 Cannot convert null literal to non-nullable reference type."
etc...
it looks very like some of the code needs refactoring, is this true or am I missing something?
And one more thing, it looks like some of the Handlers won't be able to be compiled on nf4.8. Because they require version C# 9.0 or later. So I'm not sure if the library is ready to run on older versions of .net

You get these warnings because they are enabled for your project, just remove this line:
<Nullable>enable</Nullable>
But yes, some refactoring would be nice :) For example, I don't quite understand why we need IIconElement.cs since we do get/set in each control separately 🤔

But yes, some refactoring would be nice :) For example, I don't quite understand why we need IIconElement.cs since we do get/set in each control separately 🤔

I use IIconElement to confirm that the element using the interface correctly implements all assumptions of the element with the Icon. And since different elements extends different classes, we can't just use inheritance.


added copy resource bag to user zone to async task

…ask improvement

Pull Request Checklist:

[ ] Positive Test Case Written by Dev

[ ] Automated Testing

[ ] Sufficient User and Developer Documentation

[ ] Passing Jenkins Build

[ ] Peer Code review and approval

Positive Test Case

[Enter positive test case here]

METRIC
VALUE

https://sonarqube.cuahsi-workstation.com:9000/dashboard?id=hydroshare-4104

METRIC
VALUE

https://sonarqube.cuahsi-workstation.com:9000/dashboard?id=hydroshare-4104

@hyi - finished my review.  There are a few smaller comments.  Overall this is ready to go once you respond.

@hyi - finished my review.  There are a few smaller comments.  Overall this is ready to go once you respond.

@sblack-usu I have addressed your comments. See if everything looks good to you now.

@sblack-usu I have addressed your comments. See if everything looks good to you now.


add UBSAN test for clang-3.4 R-dev

Make it easier to do UBSAN test for R packages. sanitizers is a package to show how this test work.
Here is the result on Travis CI which passed on normal build, but failed on UBSAN build.

Closed for not being stable for now.


Back navigation on modules page in documentation does not remember scroll position

Environment
Documentation
Reproduction
This error happens on a mobile phone using Firefox

go to the modules page: https://nuxt.com/modules
scroll down to one of the lower modules
go to a module page (for instance, go to the "lodash" module)
use the back button, or back-guesture
see that your scroll position is now at "eslint" (the first module in the list) and not at "lodash".

Describe the bug
After navigating back to the modules page, your original scroll position is not remembered.
Additional context
This is on my mobile phone. I did not try on desktop.
Logs
No response

Transferring to (currently) private https://github.com/nuxt/nuxt.com repo to track there.


West Australia open data

[X] My submission is formatted according to the guidelines in the contributing guide
[X] My addition is ordered alphabetically
[X] My submission has a useful description
[X] The description does not have more than 100 characters
[X] The description does not end with punctuation
[X] Each table column is padded with one space on either side
[X] I have searched the repository for any relevant issues or pull requests
[X] Any category I am creating has the minimum requirement of 3 items
[X] All changes have been squashed into a single commit

I think these city data are not related to each other:
https://ckan.multimediagdansk.pl/en vs https://data.wa.gov.au/
West Australia doesn't exist on list of APIs.

No problem. I'm glad we managed to clarify it. :)


parent child example incorrect mapping

Expected Behavior
That there is an index created with a parent child relationship using the join field.
Current Behavior
When running create_index! and error is returned.

Elasticsearch::Transport::Transport::Errors::BadRequest` ([400] {"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"Root mapping definition has unsupported parameters:  [author : {type=text}] [text : {type=text}] [title : {type=text}] [join_field : {type=join, relations={question=answer}}]"}],"type":"mapper_parsing_exception","reason":"Failed to parse mapping [_doc]: Root mapping definition has unsupported parameters:  [author : {type=text}] [text : {type=text}] [title : {type=text}] [join_field : {type=join, relations={question=answer}}]","caused_by":{"type":"mapper_parsing_exception","reason":"Root mapping definition has unsupported parameters:  [author : {type=text}] [text : {type=text}] [title : {type=text}] [join_field : {type=join, relations={question=answer}}]"}},"status":400})

Steps to Reproduce

Copy question.rb, answer.rb and parent_and_child_searchable.rb from the examples folder on this repository to a Rails <IP_ADDRESS> project
In Rails console: require "parent_and_child_searchable"
In Rails console: create an question and answer
In Rails console: ParentChildSearchable.create_index!
Watch everything explode

Context (Environment)
Using Rails <IP_ADDRESS> and 6.2
Tried using Elasticsearch 7.6.2 and 7.5.2 same result for both versions
Ruby 2.6.0
gems:
elasticsearch-rails 7.1.1
elasticsearch-model 7.1.1

Hi @MarkerDave,
Thanks for reporting this, I'll be working on this library soon after the release of the Elastic stack 7.11 and I'll take a look at this issue.
Cheers!


Added warren to lib/domains/us/kyschools

@void0xA First stage of verification passed, official domain is warrencountyschools.org as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision. Proof of domain ownership: https://www.warrencountyschools.org/greenwood/Content/63272


Target directory path

The instructions are not clear to what you mean by "Target directory path"

Target directory path
This is the path where the symlink will be created. The target
directory should not exist and will be newly created.

When I try to create a link to folder (win11), I get an error message. I'd appreciate some celerity.
There is no demo; would you please add one?

I am currently occupied, so a demo will be not available for quite some time.
Anyhow, as stated in the description and out of caution:

Please note that this Plugin is in early development and may not work as expected. Furthermore, creating symlinks and junctions can be dangerous and may lead to data loss. Please use this Plugin with caution.

Creating a symlink across folders on the same drive is pretty straightforward: You select a folder where data is that you want in your obsidian (source) and a folder name where the data should be stored in your vault (target). As long as source exists, target is a valid folder name and within the same drive it should work. Across volumes it is more difficult as you would need to create non-junction symlinks on windows which require admin privileges or dev-mode. I wouldn't recommend using Obsidian in either one of them.


Is there a way to tokenize LitInt as hex representation?

E.g. instead of 66u32 you get 0x42u32?
For my use case it would make the proc. macro output more human readable and therefore improve debugability.

You can emit the hex representation with
let hex = syn::Lit::new(Literal::from_str(&format!("0x{:X}", 66u32)).unwrap());
quote!{
    #hex
}

which yields
0x42

Thanks a lot for the info - it works really well!
However, I think a more user friendly API might be useful.

I think this API is fine as is for this use case.


Implement popular articles

Add a section to the sidebar of the article page. Along with related articles from #173 and the recent articles from #642 we could implement a popular ones as well.
see the popular section on this site.

fixed in https://github.com/richwklein/agingdeveloper/commit/bc06c636b6a7eb79a0f20b1b52992bb068ddbbdc


Fixing pkg->cmd call by moving helmpath under /pkg

When downloader package moved to under /pkg, helmpath functions got called still from it, while it is under /cmd. This commit fixes the issue by moving helmpath after the downloader to have only cmd->pkg and pkg->pkg calls.

Thank you for noticing that. It's something we've been talking about fixing since we moved the downloader library.

Perhaps this should live under pkg/helm/helmpath similar to pkg/helm/portforwarder? This client package is only relevant to users of the helm client, so the same argument could be applied here as well.

I agree with @bacongobbler on that one. We probably should put it under pkg/helm since it is very specifically client-oriented logic.

Thanks for the review! I am preparing the move right now.
To be complete: downloader and resolver package also uses helmpath. Although these are also fully client related, they live outside of pkg/helm.


Readme spelling error

Under how to play "alegraic" should be algebraic.

Thanks! Resolved in https://github.com/nickzuber/chs/commit/37cfb7c5cf0bb9ae3baccce093c5509b9f3b4718


RFC : Parameters utility

Key information

RFC PR: (leave this empty)
Related issue(s), if known:

https://github.com/awslabs/aws-lambda-powertools-typescript/issues/484

https://github.com/awslabs/aws-lambda-powertools-typescript/issues/165

Area: Parameters
Meet tenets: Yes
Approved by: ''
Reviewed by: ''

Summary

Implementation/porting of a Parameters utility already implemented in Python.
Motivation

Features parity across Powertools languages, prioritized based on community demand.
I am keeping the sections below empty for now to allow us to think it throught, but I am keen on hearing our community's ideas, wishlists, desired UX, etc.
Proposal

User Experience

Drawbacks

Rationale and alternatives

Unresolved questions

Just for info purposes, there is a development branch that I started about 10 months ago with an initial implementation of the utility that matches the Python version of the time, plus unit tests.
As I mentioned I haven't been working on this for a long while, I have just rebased today to incorporate the current project structure. Maybe this can be used as a PoC reference for a future implementation. In case we want to go in a different direction I'm also happy to discard it.

The first public beta for the utility has been released in v1.7.0<EMAIL_ADDRESS>on npm).
We are eager to hear your feedback, so feel free to open an issue if you encounter any bug or open a discussion here or on Discord if you have questions or doubts.