[HOLD][$250] Migrate BaseVideoChatButtonAndMenu.js to function component

Class Component Migration
Filenames

[ ] src/components/VideoChatButtonAndMenu/BaseVideoChatButtonAndMenu.js

type: React.Component
has state values: true
has refs: true
has context: false
lifecycle methods: componentDidMount,componentWillUnmount

Task

We currently have some class components in our codebase that we would like to refactor to a function component.
Here's a link with some general advice on how to refactor a class component to a function component: https://react.dev/reference/react/Component#alternatives
If you need additional guidance, please ask in #expensify-open-source
Test for any regressions and verify that there are no breaking changes

Heads up! The pricing for this issue has been adjusted based on the scope of the work and the fact that no complex bug investigations or proposal are required.

I'd love to work on this.

I would like to work on this!

I would like to work on this.

I would love to work on this. Can i get this assigned?

@puneetlath Who is going to be the winner?

Looks like @s-alves10 has 3 active issues assigned currently. So let's go with @neonbhai since they are the earliest poster who isn't currently working on any issues for us.

@neonbhai Any update on the PR?

@neonbhai will you be able to raise a PR in the next 48 hours? If not, I'll go ahead and assign someone else. Just let us know. Thanks!

Hey @mollfpr @puneetlath yes. the PR is almost done. I'm just collecting the testing screenshots. The PR will be up in 24 hours!

Great!

Hi @mollfpr @puneetlath, Please review the PR!

@mollfpr let me know when you think you'll be done reviewing.

Hi @puneetlath it has been 2+ weeks since the PR was merged! Can I please get paid on upwork?

Oh, weird, sorry about that! Usually an automation runs to let me know it's time to pay.

Upwork contracts sent. Sorry again for the delay!

All paid. Thanks everyone!


Fix #2023: Fix CopyOnWriteArrayList type parameter bound.

Review by @sjrd

Did you check that we don't have any other collection taking Array[E]s that would also need fixing?

No, I will check.

It was the only one.

LGTM

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/2430/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/3152/
Test PASSed.


Unable to add Yeelight W1 lights with the setup wizard.

I'm having issues adding my Yeelight W1's to my hypderhdr setup. They show up fine but according to the logs things start going wrong with a write error. I included the log down below.
2024-05-06T09:51:16.836Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:225) setBackLightEnabled: 1
2024-05-06T09:51:16.986Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T09:51:16.987Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T09:51:18.203Z [FLATBUFSERVER] (FlatBufferClient.cpp:92) Socket Closed
2024-05-06T09:51:18.204Z [MUXER0] Removed source priority 150
2024-05-06T09:51:18.204Z [MUXER0] Set visible priority to 255
2024-05-06T09:51:18.204Z [HYPERHDR0] New priority[255], previous [150]
2024-05-06T09:51:18.204Z [HYPERHDR0] No source left -> switch LED-Device off
2024-05-06T09:51:18.204Z [SMOOTHING0] Clearing queued colors before: disabling
2024-05-06T09:51:18.204Z [SMOOTHING0] Smoothing queue is cleared
2024-05-06T09:51:18.204Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:225) setBackLightEnabled: 0
2024-05-06T09:51:18.520Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T09:51:18.520Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T09:51:18.520Z [LEDDEVICE0_YEELIGHT] Device 'yeelight' is disabled due to an error: 'All Yeelights in error - stopping device!'
2024-05-06T09:51:18.520Z [COMPONENTCTRL0] LED device: disabled
2024-05-06T09:51:18.521Z [LEDDEVICE0_YEELIGHT] (LedDeviceYeelight.cpp:1220) Stop MusicModeServer
2024-05-06T09:51:18.521Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:392) Stopping retry timer
2024-05-06T09:51:18.521Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:247) Enable the device
2024-05-06T09:51:18.521Z [LEDDEVICE0_YEELIGHT] (LedDeviceYeelight.cpp:1206) The music mode server is running at <IP_ADDRESS>:44294
2024-05-06T09:51:18.555Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:64) Switch on
2024-05-06T09:51:18.899Z [FLATBUFSERVER] (FlatBufferServer.cpp:138) New connection from ::ffff:<IP_ADDRESS>

This extremely truncated logs tells us only:
2024-05-06T09:51:16.987Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T09:51:18.520Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T09:51:18.521Z [LEDDEVICE0_YEELIGHT] (LedDeviceYeelight.cpp:1206) The music mode server is running at <IP_ADDRESS>:44294

3 different IPs. Cant do anything about it

Sorry about that, I only copied the yellow and red lines and figured that was enough. Here is everything I could get from the log. It seems to repeat the same loop of errors.
2024-05-06T10:15:26.975Z [MUXER0] Priority 150 is now active
2024-05-06T10:15:26.976Z [MUXER0] Set visible priority to 150
2024-05-06T10:15:26.976Z [HYPERHDR0] New priority[150], previous [255]
2024-05-06T10:15:26.976Z [HYPERHDR0] New source available -> switch LED-Device on
2024-05-06T10:15:26.976Z [HYPERHDR0] Components are disabled: ignoring switching LED-Device on
2024-05-06T10:15:26.976Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:225) setBackLightEnabled: 1
2024-05-06T10:15:42.388Z [FLATBUFSERVER] (FlatBufferClient.cpp:92) Socket Closed
2024-05-06T10:15:42.388Z [MUXER0] Removed source priority 150
2024-05-06T10:15:42.388Z [MUXER0] Set visible priority to 255
2024-05-06T10:15:42.388Z [HYPERHDR0] New priority[255], previous [150]
2024-05-06T10:15:42.388Z [HYPERHDR0] No source left -> switch LED-Device off
2024-05-06T10:15:42.388Z [SMOOTHING0] Clearing queued colors before: disabling
2024-05-06T10:15:42.389Z [SMOOTHING0] Smoothing queue is cleared
2024-05-06T10:15:42.389Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:225) setBackLightEnabled: 0
2024-05-06T10:45:22.387Z [WEBSOCKET] (WebSocketClient.cpp:188) send close: 1000
2024-05-06T10:46:29.277Z [WEBSOCKET] (WebSocketClient.cpp:39) New connection from ::ffff:<IP_ADDRESS>
2024-05-06T10:46:37.202Z [WEBSOCKET] (HyperAPI.cpp:957) log streaming activated for client ::ffff:<IP_ADDRESS>
2024-05-06T10:46:54.203Z [WEBSOCKET] (HyperAPI.cpp:966) log streaming deactivated for client  ::ffff:<IP_ADDRESS>
2024-05-06T10:46:58.858Z [COMPONENTCTRL0] (ComponentController.cpp:73) Enabling HyperHDR instance: recovering previuosly saved component states
2024-05-06T10:46:58.858Z [MUXER0] Register new input 'System/VIDEOGRABBER' with priority 240 as inactive
2024-05-06T10:46:58.858Z [COMPONENTCTRL0] Video capture device: enabled
2024-05-06T10:46:58.858Z [SMOOTHING0] Clearing queued colors before: enabling
2024-05-06T10:46:58.858Z [SMOOTHING0] Smoothing queue is cleared
2024-05-06T10:46:58.858Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:297) Previous line repeats 22 times
2024-05-06T10:46:58.858Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:247) Enable the device
2024-05-06T10:46:58.858Z [LEDDEVICE0_YEELIGHT] (LedDeviceYeelight.cpp:1206) The music mode server is running at <IP_ADDRESS>:34679
2024-05-06T10:46:58.859Z [COMPONENTCTRL0] HyperHDR: enabled
2024-05-06T10:46:58.877Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:64) Switch on
2024-05-06T10:47:00.456Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: '(-5001) invalid params'
2024-05-06T10:47:00.958Z [LEDDEVICE0_YEELIGHT] Ignoring Yeelight error when turning off music mode
2024-05-06T10:47:01.518Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: '(-5001) invalid params'
2024-05-06T10:47:02.019Z [LEDDEVICE0_YEELIGHT] Ignoring Yeelight error when turning off music mode
2024-05-06T10:47:02.572Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: '(-5001) invalid params'
2024-05-06T10:47:03.073Z [LEDDEVICE0_YEELIGHT] Ignoring Yeelight error when turning off music mode
2024-05-06T10:47:03.761Z [COMPONENTCTRL0] LED device: enabled
2024-05-06T10:47:05.292Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:47:05.292Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:47:06.828Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:47:06.828Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:47:08.363Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:47:08.363Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:47:16.805Z [FLATBUFSERVER] (FlatBufferServer.cpp:138) New connection from ::ffff:<IP_ADDRESS>
2024-05-06T10:47:17.041Z [MUXER0] Register new input 'webos@::ffff:<IP_ADDRESS>/FLATBUFSERVER' with priority 150 as inactive
2024-05-06T10:47:17.041Z [MUXER0] Priority 150 is now active
2024-05-06T10:47:17.041Z [MUXER0] Set visible priority to 150
2024-05-06T10:47:17.041Z [HYPERHDR0] New priority[150], previous [255]
2024-05-06T10:47:17.041Z [LEDDEVICE0_YEELIGHT] Device 'yeelight' is disabled due to an error: 'All Yeelights in error - stopping device!'
2024-05-06T10:47:17.041Z [HYPERHDR0] New source available -> switch LED-Device on
2024-05-06T10:47:17.042Z [SMOOTHING0] Clearing queued colors before: enabling
2024-05-06T10:47:17.042Z [SMOOTHING0] Smoothing queue is cleared
2024-05-06T10:47:17.042Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:392) Stopping retry timer
2024-05-06T10:47:17.042Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:247) Enable the device
2024-05-06T10:47:17.042Z [LEDDEVICE0_YEELIGHT] (LedDeviceYeelight.cpp:1206) The music mode server is running at <IP_ADDRESS>:34679
2024-05-06T10:47:17.042Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:64) Switch on
2024-05-06T10:47:17.042Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:225) setBackLightEnabled: 1
2024-05-06T10:47:17.042Z [COMPONENTCTRL0] LED device: disabled
2024-05-06T10:47:25.179Z [COMPONENTCTRL0] LED device: enabled
2024-05-06T10:47:26.510Z [FLATBUFSERVER] (FlatBufferServer.cpp:138) New connection from ::ffff:<IP_ADDRESS>
2024-05-06T10:47:26.732Z [FLATBUFSERVER] (FlatBufferClient.cpp:92) Socket Closed
2024-05-06T10:47:26.732Z [MUXER0] Removed source priority 150
2024-05-06T10:47:26.732Z [MUXER0] Set visible priority to 255
2024-05-06T10:47:26.732Z [HYPERHDR0] New priority[255], previous [150]
2024-05-06T10:47:26.732Z [HYPERHDR0] No source left -> switch LED-Device off
2024-05-06T10:47:26.732Z [SMOOTHING0] Clearing queued colors before: disabling
2024-05-06T10:47:26.732Z [SMOOTHING0] Smoothing queue is cleared
2024-05-06T10:47:26.732Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:225) setBackLightEnabled: 0
2024-05-06T10:47:26.847Z [MUXER0] Register new input 'webos@::ffff:<IP_ADDRESS>/FLATBUFSERVER' with priority 150 as inactive
2024-05-06T10:47:26.847Z [MUXER0] Priority 150 is now active
2024-05-06T10:47:26.847Z [MUXER0] Set visible priority to 150
2024-05-06T10:47:26.847Z [HYPERHDR0] New priority[150], previous [255]
2024-05-06T10:47:26.847Z [HYPERHDR0] New source available -> switch LED-Device on
2024-05-06T10:47:26.847Z [SMOOTHING0] Clearing queued colors before: enabling
2024-05-06T10:47:26.847Z [SMOOTHING0] Smoothing queue is cleared
2024-05-06T10:47:26.848Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:225) setBackLightEnabled: 1
2024-05-06T10:47:26.990Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:47:26.990Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:47:28.525Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:47:28.525Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:47:30.094Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:47:30.094Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:47:30.094Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:297) Disable the device
2024-05-06T10:47:30.094Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:90) Switch off
2024-05-06T10:47:30.094Z [LEDDEVICE0_YEELIGHT] (LedDeviceYeelight.cpp:1220) Stop MusicModeServer
2024-05-06T10:47:30.094Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:247) Enable the device
2024-05-06T10:47:30.095Z [LEDDEVICE0_YEELIGHT] (LedDeviceYeelight.cpp:1206) The music mode server is running at <IP_ADDRESS>:39623
2024-05-06T10:47:30.095Z [COMPONENTCTRL0] LED device: disabled
2024-05-06T10:47:30.197Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:64) Switch on
2024-05-06T10:47:35.433Z [WEBSOCKET] (HyperAPI.cpp:957) log streaming activated for client ::ffff:<IP_ADDRESS>
2024-05-06T10:47:38.089Z [COMPONENTCTRL0] LED device: enabled
2024-05-06T10:47:39.750Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:47:39.750Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:47:41.491Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:47:41.491Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:47:43.383Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:47:43.383Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:47:43.384Z [LEDDEVICE0_YEELIGHT] Device 'yeelight' is disabled due to an error: 'All Yeelights in error - stopping device!'
2024-05-06T10:47:43.384Z [COMPONENTCTRL0] LED device: disabled
2024-05-06T10:47:46.405Z [LEDDEVICE0_YEELIGHT] The LED device is not ready... trying to reconnect (try 1/60).
2024-05-06T10:47:46.405Z [LEDDEVICE0_YEELIGHT] (LedDeviceYeelight.cpp:1206) The music mode server is running at <IP_ADDRESS>:39623
2024-05-06T10:47:46.405Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:64) Switch on
2024-05-06T10:47:55.547Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:392) Stopping retry timer
2024-05-06T10:47:55.547Z [COMPONENTCTRL0] LED device: enabled
2024-05-06T10:47:56.850Z [FLATBUFSERVER] (FlatBufferClient.cpp:92) Socket Closed
2024-05-06T10:47:56.850Z [MUXER0] Removed source priority 150
2024-05-06T10:47:56.850Z [MUXER0] Set visible priority to 255
2024-05-06T10:47:56.850Z [HYPERHDR0] New priority[255], previous [150]
2024-05-06T10:47:56.850Z [HYPERHDR0] No source left -> switch LED-Device off
2024-05-06T10:47:56.850Z [SMOOTHING0] Clearing queued colors before: disabling
2024-05-06T10:47:56.850Z [SMOOTHING0] Smoothing queue is cleared
2024-05-06T10:47:56.850Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:225) setBackLightEnabled: 0
2024-05-06T10:47:57.081Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:47:57.081Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:47:57.762Z [FLATBUFSERVER] (FlatBufferServer.cpp:138) New connection from ::ffff:<IP_ADDRESS>
2024-05-06T10:47:57.889Z [MUXER0] Register new input 'webos@::ffff:<IP_ADDRESS>/FLATBUFSERVER' with priority 150 as inactive
2024-05-06T10:47:57.889Z [MUXER0] Priority 150 is now active
2024-05-06T10:47:57.889Z [MUXER0] Set visible priority to 150
2024-05-06T10:47:57.889Z [HYPERHDR0] New priority[150], previous [255]
2024-05-06T10:47:57.889Z [HYPERHDR0] New source available -> switch LED-Device on
2024-05-06T10:47:57.889Z [SMOOTHING0] Clearing queued colors before: enabling
2024-05-06T10:47:57.889Z [SMOOTHING0] Smoothing queue is cleared
2024-05-06T10:47:57.889Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:225) setBackLightEnabled: 1
2024-05-06T10:47:58.609Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:47:58.609Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:48:00.171Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:48:00.171Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:48:00.171Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:297) Disable the device
2024-05-06T10:48:00.171Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:90) Switch off
2024-05-06T10:48:00.171Z [LEDDEVICE0_YEELIGHT] (LedDeviceYeelight.cpp:1220) Stop MusicModeServer
2024-05-06T10:48:00.171Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:247) Enable the device
2024-05-06T10:48:00.171Z [COMPONENTCTRL0] LED device: disabled
2024-05-06T10:48:00.171Z [LEDDEVICE0_YEELIGHT] (LedDeviceYeelight.cpp:1206) The music mode server is running at <IP_ADDRESS>:41887
2024-05-06T10:48:00.383Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:64) Switch on
2024-05-06T10:48:08.570Z [COMPONENTCTRL0] LED device: enabled
2024-05-06T10:48:10.252Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:48:10.252Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:48:11.966Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:48:11.966Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:48:13.677Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:48:13.677Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:48:13.678Z [LEDDEVICE0_YEELIGHT] Device 'yeelight' is disabled due to an error: 'All Yeelights in error - stopping device!'
2024-05-06T10:48:13.678Z [COMPONENTCTRL0] LED device: disabled
2024-05-06T10:48:16.829Z [LEDDEVICE0_YEELIGHT] The LED device is not ready... trying to reconnect (try 1/60).
2024-05-06T10:48:16.829Z [LEDDEVICE0_YEELIGHT] (LedDeviceYeelight.cpp:1206) The music mode server is running at <IP_ADDRESS>:41887
2024-05-06T10:48:16.829Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:64) Switch on
2024-05-06T10:48:25.593Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:392) Stopping retry timer
2024-05-06T10:48:25.593Z [COMPONENTCTRL0] LED device: enabled
2024-05-06T10:48:27.293Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:48:27.293Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:48:28.951Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:48:28.951Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:48:30.652Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:48:30.653Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:48:30.654Z [LEDDEVICE0_YEELIGHT] Device 'yeelight' is disabled due to an error: 'All Yeelights in error - stopping device!'
2024-05-06T10:48:30.654Z [COMPONENTCTRL0] LED device: disabled
2024-05-06T10:48:33.804Z [LEDDEVICE0_YEELIGHT] The LED device is not ready... trying to reconnect (try 1/60).
2024-05-06T10:48:33.804Z [LEDDEVICE0_YEELIGHT] (LedDeviceYeelight.cpp:1206) The music mode server is running at <IP_ADDRESS>:41887
2024-05-06T10:48:33.804Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:64) Switch on
2024-05-06T10:48:42.178Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:392) Stopping retry timer
2024-05-06T10:48:42.178Z [COMPONENTCTRL0] LED device: enabled
2024-05-06T10:48:43.809Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:48:43.809Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:48:45.598Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:48:45.598Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:48:47.300Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:48:47.300Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:48:47.300Z [PERFORMANCE] [INSTANCE0: FPS = 25.35, processed = 1532], [LED0: FPS = 0.11, send = 7, processed = 559, dropped = 551]
2024-05-06T10:48:47.300Z [LEDDEVICE0_YEELIGHT] Device 'yeelight' is disabled due to an error: 'All Yeelights in error - stopping device!'
2024-05-06T10:48:47.300Z [COMPONENTCTRL0] LED device: disabled
2024-05-06T10:48:47.300Z [PERFORMANCE] [INSTANCE0: FPS = 25.35, processed = 1532]
2024-05-06T10:48:47.786Z [FLATBUFSERVER] (FlatBufferServer.cpp:138) New connection from ::ffff:<IP_ADDRESS>
2024-05-06T10:48:47.786Z [FLATBUFSERVER] (FlatBufferClient.cpp:92) Socket Closed
2024-05-06T10:48:47.786Z [MUXER0] Removed source priority 150
2024-05-06T10:48:47.786Z [MUXER0] Set visible priority to 255
2024-05-06T10:48:47.786Z [HYPERHDR0] New priority[255], previous [150]
2024-05-06T10:48:47.786Z [HYPERHDR0] No source left -> switch LED-Device off
2024-05-06T10:48:47.786Z [SMOOTHING0] Clearing queued colors before: disabling
2024-05-06T10:48:47.786Z [SMOOTHING0] Smoothing queue is cleared
2024-05-06T10:48:47.787Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:225) setBackLightEnabled: 0
2024-05-06T10:48:47.787Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:297) Disable the device
2024-05-06T10:48:47.910Z [MUXER0] Register new input 'webos@::ffff:<IP_ADDRESS>/FLATBUFSERVER' with priority 150 as inactive
2024-05-06T10:48:47.910Z [MUXER0] Priority 150 is now active
2024-05-06T10:48:47.910Z [MUXER0] Set visible priority to 150
2024-05-06T10:48:47.910Z [HYPERHDR0] New priority[150], previous [255]
2024-05-06T10:48:47.910Z [HYPERHDR0] New source available -> switch LED-Device on
2024-05-06T10:48:47.910Z [SMOOTHING0] Clearing queued colors before: enabling
2024-05-06T10:48:47.910Z [SMOOTHING0] Smoothing queue is cleared
2024-05-06T10:48:47.910Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:225) setBackLightEnabled: 1
2024-05-06T10:48:47.910Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:392) Stopping retry timer
2024-05-06T10:48:47.910Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:247) Enable the device
2024-05-06T10:48:47.910Z [LEDDEVICE0_YEELIGHT] (LedDeviceYeelight.cpp:1206) The music mode server is running at <IP_ADDRESS>:41887
2024-05-06T10:48:47.910Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:64) Switch on
2024-05-06T10:48:56.020Z [COMPONENTCTRL0] LED device: enabled
2024-05-06T10:48:56.893Z [FLATBUFSERVER] (FlatBufferClient.cpp:92) Socket Closed
2024-05-06T10:48:56.894Z [MUXER0] Removed source priority 150
2024-05-06T10:48:56.894Z [MUXER0] Set visible priority to 255
2024-05-06T10:48:56.894Z [HYPERHDR0] New priority[255], previous [150]
2024-05-06T10:48:56.894Z [HYPERHDR0] No source left -> switch LED-Device off
2024-05-06T10:48:56.894Z [SMOOTHING0] Clearing queued colors before: disabling
2024-05-06T10:48:56.894Z [SMOOTHING0] Smoothing queue is cleared
2024-05-06T10:48:56.894Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:225) setBackLightEnabled: 0
2024-05-06T10:48:57.656Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:48:57.656Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:48:57.704Z [FLATBUFSERVER] (FlatBufferServer.cpp:138) New connection from ::ffff:<IP_ADDRESS>
2024-05-06T10:48:58.021Z [MUXER0] Register new input 'webos@::ffff:<IP_ADDRESS>/FLATBUFSERVER' with priority 150 as inactive
2024-05-06T10:48:58.021Z [MUXER0] Priority 150 is now active
2024-05-06T10:48:58.021Z [MUXER0] Set visible priority to 150
2024-05-06T10:48:58.021Z [HYPERHDR0] New priority[150], previous [255]
2024-05-06T10:48:58.021Z [HYPERHDR0] New source available -> switch LED-Device on
2024-05-06T10:48:58.021Z [SMOOTHING0] Clearing queued colors before: enabling
2024-05-06T10:48:58.021Z [SMOOTHING0] Smoothing queue is cleared
2024-05-06T10:48:58.021Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:225) setBackLightEnabled: 1
2024-05-06T10:48:59.189Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:48:59.189Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:49:00.720Z [LEDDEVICE0_YEELIGHT] write Error [<IP_ADDRESS>]: _tcpMusicModeServer: (5) Network operation timed out
2024-05-06T10:49:00.720Z [LEDDEVICE0_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: 'Failed to get stream socket'
2024-05-06T10:49:00.720Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:297) Disable the device
2024-05-06T10:49:00.720Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:90) Switch off
2024-05-06T10:49:00.720Z [LEDDEVICE0_YEELIGHT] (LedDeviceYeelight.cpp:1220) Stop MusicModeServer
2024-05-06T10:49:00.720Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:247) Enable the device
2024-05-06T10:49:00.721Z [LEDDEVICE0_YEELIGHT] (LedDeviceYeelight.cpp:1206) The music mode server is running at <IP_ADDRESS>:37832
2024-05-06T10:49:00.721Z [COMPONENTCTRL0] LED device: disabled
2024-05-06T10:49:00.931Z [LEDDEVICE0_YEELIGHT] (LedDevice.cpp:64) Switch on

I'm confused. The W1 should be "natively" supported and shows up in the yeelight wizard instantly. Any pointers to what I can try to resolve this?

As I have already written, I do not have such a lamp and it is up to the community whether they want support for such devices. In v20, a user-generated and user-tested patch was provided.
Additionally, <IP_ADDRESS> indicates some non-standard virtual network interface is being used, so supporting something like this is also up to the users. In the past, this sometimes caused problems with other devices. But this is a non-standard configuration.

Curious issue. I know these lights can be used over LAN directly so i'll have to try some things. Thanks for the help.

I saw something similar in the past. There are 2 possible workaround: one require code recompiling and the second one to provide an option ofr a docker https://github.com/awawa-dev/HyperHDR/issues/580 But it's up to users to create & test PR because I dont have such setup and something could easily break up for the standard network configuration (without docker).

Got it working by removing one of my dockers that was using a bridge instead of host network. Specifically the "watchtower" docker. I think this one can be marked as done.


feat: display labels on execution detail page

TL;DR
This PR adds the spec labels to the execution details page
Type

[ ] Bug Fix
[X] Feature
[ ] Plugin

Are all requirements met?

[X] Code completed
[X] Smoke tested
[X] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

This is great, thank you. A few items I would like to see:

Updated color, yellow is too prominent, update to a secondary color like grey.

Overflow states:

what happens when a single label is very long?
what happens when you have 3+ rows of labels?

Empty state, what happens when there are no labels?

Interactions, are these intended to be clickable or copyable?

Here's what it looks like with more(both longer and more rows)

Here's an updated version with the info color set on the Chip.

Empty state, the column doesn't show. Would you prefer the --- behaviour instead?
Also, there is no functionality on the Chips. If someone wants to add something later(like copy to clipboard), I think it should be trivial. Do you think this is ok?

Empty state, the column doesn't show. Would you prefer the --- behaviour instead?
Also, there is no functionality on the Chips. If someone wants to add something later(like copy to clipboard), I think it should be trivial. Do you think this is ok?

Yes, I would prefer the --- behavior for the empty state for consistency and discovery. Otherwise this looks good to me. Thank you for your contribution!

Ok, done.


How to access iterator value in range

I am following the creation of a new theme, and I have a very simple use case to show last three blog posts on the home page.
{{- range first 3 .Data.Pages -}}
{{- if eq .Type "blog"}}

{{ .Title }}

Lorem ipsum

Read more

{{- end -}}
{{- end }}

Now this code works till the point where I am able to get the title and permalink for my posts, but I want to have separate classes for the
 based on their order. So first section should have style1 and second should have style2. Third will then have style3. Is there a way in which I can say that based on the index where the iterator is at, add dynamic classes?
Also, what will be a good way to set and access header images for my posts?

Please use http://discuss.gohugo.io/ for questions/troubleshooting. Also see  Hugo Documentation.

@bep Just a heads up to change the URL for your forum responses (if you haven't already).


[RNG-124]: Add fixed increment PCG generators.

Adds a single Long argument constructor to:
AbstractPcg6432
PcgXshRr32
PcgXshRs32
PcgRxsMXs64
Adds RandomSource:
PCG_XSH_RR_32_OS
PCG_XSH_RS_32_OS
PCG_RXS_M_XS_64_OS
OS = One Sequence

Coverage increased (+0.003%) to 99.508% when pulling ad8052e6eff0a81b28f493c8da789129f0ddde29 on aherbert:improvement-RNG-124 into a07fc4377bacbd5868728390ac3c2cd9855a7981 on apache:master.


s/Env/Log/

Closes #167

@purrgrammer can you open the equivalent issue in Kollect so we don't forget?


write template for static

Description
The Static edge Template For Using With Route
Relevant Information

[ ] auth/register
[ ] auth/login
[ ] auth/verify-email
[ ] auth/reset-password
[ ] auth/forgot-password
[ ] auth/two-factor-challenge
[ ] as inertia-vue
[ ] as inertia-react
[ ] as inertia-svelte

some of auth/login has write but need auth/register to register user but that i need more time to add template.

look like it has corrupt publish with yarn


Improve TestIfPerformanceCountersAreCollected to remove 1min delay

Can we change the test so it doesn't depend on 60 seconds perf counter collection interval?

Tests have been sped up from 70 second sleep to only 6 or 7 seconds taken by counter creation/init.


This issue is similar to https://github.com/Azure/azure-cli/issues/28678.
Other CDN tests have the same issue https://github.com/Azure/azure-cli/pull/30409#issuecomment-2513719578. These tests were skipped by https://github.com/Azure/azure-cli/pull/30492.


[issue #1400]do disk space detection in another thread

What is the purpose of the change
work for this issue, add a thread to do disk space detection
Brief changelog
add another ScheduledExecutorService to do disk space detection
Verifying this change
XXXX

Coverage increased (+0.2%) to 50.727% when pulling 0597823ff7a9f33ffc571d86dfabd342c63b260b on qqeasonchen:dev_bing into 90ae1167981ad586e84dd433c08395aeb92a4111 on apache:develop.


Intergrating Airtable API with Next.js serverless functions

Article checklist
Pre-submission checks
Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net(2766)

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.(anyone new to using Airtable can understand perfectly)

[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images(I added my own image)

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.(3%)
[x] Have you checked your article for readability? - Tool: Hemmingway(Grade 5)
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[x] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?(I tried to rebuild the whole application myself after completing the article)
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?(I have added the source code and live demo for the application)

This closes #2955

Upon running your article through our 3rd party plagiarism checker it seemed to raise a few flags and the % was higher than we typically accept. Please see attached PDF - and revisit the article to ensure we are contributing wholly unique and original content. Be sure to see our resources page to see more info on plagiarism and what is considered as such.
Intergrating Airtable API with Next.js serverless functions #3487.pdf

hey @WanjaMIKE most of the plagiarism error was because of the code. Both the examples are todo apps built using next.js and tailwind css. Should I change the example in my article?

Hey @katungi I have changed the content acc to the suggestions by @WanjaMIKE
Please review it

Hi @giridhar7632 several issues were raised during the review process. Could you work more on the article, specifically, fix grammar errors, sentence structure, formatting  - then open a new PR when its really ready. Thanks


DS Crash: Redstone related?

https://pastebin.com/ZmwUmbNH
Server just crashed with the above. The setup that caused is:
Timer->redstone dust->AA atomic reconstructor->redstone dust->redstone repeater (4 ticks)->redstone repeater (4 ticks)->redstone dust->piston.
This is on the Undiscovered modpack.

And another one. After MCediting out the redstone, replacing everything. The moment redstone is placed down, server crashes.
https://pastebin.com/1dNwXQLp

Update: I believe this is related to trying to push (with a piston) a contentTweaker added block that is tool level 3 (obsidian level), at the same time it was being changed {(Via AA atomic reconstructor with mining lens) via redstone pulse.
This is the block in question:
var osmaticSteelOre = VanillaFactory.createBlock("osmaticsteelore", <blockmaterial:rock>); osmaticSteelOre.setToolLevel(3); osmaticSteelOre.setToolClass("pickaxe"); osmaticSteelOre.register();

It's the Piston. I see the issue. If there's no mobility flag set on the representation it breaks.

And the infinite loop is caused by the repeaters. I'm not sure if this is true everywhere, but in this modpack, if you place a piston down and power it against a block it can't move (e.g. obsidian), then remove the redstone, the redstone is still active, which feeds back into the repeater(s) and cause the loop, which crashes.


Document the Pod Ready++ feature

Closes: #9107
Xref: kubernetes/kubernetes#64057

FYI the sig-release team had no idea this got in, it did not have a kubernetes/features PR, and apparently doesn't have release notes. Please with with @nickchase and check with @jberkus about how this could have been better.

/lgtm
/approve


update type to childBuilder methods

Co-authored-by: Peh099<EMAIL_ADDRESS>Objective

Update type to childBuilder methods, because not always guaranteed that the children entities will be in an array-like container.
Issue: #7229

Solution
Use an iterator type instead of forcing someone to use a slice.

There are a number of other methods on this trait that accept this as a parameter: can we update those too?

Okay, yes we can. Thank you very much.


URLs are not recognized if capital letters present (HTTPS://, Https://, example.Com)

Steps to Reproduce
Go to bsky.social. Make a post and type on various lines:

https://cnn.com
cnn.com
https://cnn.COM
Https://cnn.com
HTTPS://cnn.com
CNN.COM
cnn.Com

OBSERVED BEHAVIOR: 1, 2, and 3 are recognized as URLs and become blue links. 4-7 are not.
EXPECTED BEHAVIOR: All of these should be recognized as valid URLs, because they are. The components in which the capital letters occur are not case sensitive:

RFC 1035 states non-IDN domain names are case insensitive;
RFC 3490 presents a more complex case model for IDN domain names, but does not modify pure ASCII domain names;
RFC 1738 §2.1 states that URL schemes such as http:// must be lowercase, BUT also states that clients (such as the bluesky app) should accept other cases as "equivalent" to lower case.

Attachments
Examples in this thread
https://bsky.app/profile/testaccountgoaway.bsky.social/post/3lavuyyxke22z
What platform(s) does this occur on?
Android, Web (Desktop)
Device Info
Firefox 130.0.1 on Ubuntu Linux, bluesky app on Android 13
What version of the app are you using?
Android app version is 1.93.0
Additional Information
Impact: This is really frustrating on Android because I use the Google "GBoard" keyboard, which likes to capitalize random things without me meaning to.

I will take a look at this

This looks like a problem with Atproto. The issue is that Atproto first checks if the link starts with "http" or not. If not, then Atproto will check if the top-level domain (.com, .net, ...) is valid. Unfortunately, the list of top-level domains that Atproto uses is from an npm package called tlds (https://www.npmjs.com/package/tlds). If you look at the code of this package, it lowercases all the top-level domains, so the URLs you mentioned will be considered invalid.
https://github.com/bluesky-social/atproto/blob/c34426fc55e8b9f28d9b1d64eab081985d1b47b5/packages/api/src/rich-text/detection.ts#L45-L48
I have created a PR to fix that issue in Atproto here: https://github.com/bluesky-social/atproto/pull/3002


next: "class" does not exist in type PortalProps

Describe the bug
npm check, along with VSCode type hints are saying that <SheetPrimitive.Portal> does not have type "class". Though, the sheet-portal.svelte component is passing a class to the SheetPrimitive component.
Reproduction
Exact code of the sheet-portal code
<script lang="ts">
	import { Dialog as SheetPrimitive } from 'bits-ui';
	import { cn } from<EMAIL_ADDRESS>
	type $$Props = SheetPrimitive.PortalProps;

	interface Props {
		class?: $$Props['class'];
		children?: import('svelte').Snippet;
		[key: string]: any;
	}

	let { class: className = undefined, children, ...rest }: Props = $props();
</script>

<SheetPrimitive.Portal class={cn(className)} {...rest}>
	{@render children?.()}
</SheetPrimitive.Portal>

Logs
Object literal may only specify known properties, and '"class"' does not exist in type 'PortalProps'.

System Info
System:
    OS: Windows 10 10.0.19045
    CPU: (16) x64 AMD Ryzen 7 7800X3D 8-Core Processor
    Memory: 21.64 GB / 31.15 GB
  Binaries:
    Node: 20.17.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.9.0 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.12.2 - C:\Program Files\nodejs\pnpm.CMD
  Browsers:
    Edge: Chromium (128.0.2739.79)
    Internet Explorer: 11.0.19041.4355

Severity
annoyance

You shouldn't have a sheet-portal.svelte component anymore. It looks like that is leftover in your code from the Svelte 4 version that can be removed. We intentionally don't remove things because we don't want to overwrite specific customizations/custom components.


ARROW-4597: [C++] Targets for system Google Mock shared library are missing

Codecov Report

Merging #3673 into master will increase coverage by 0.85%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3673      +/-   ##
==========================================
+ Coverage   87.77%   88.62%   +0.85%
==========================================
  Files         689      560     -129
  Lines       84021    75024    -8997
  Branches     1081        0    -1081
==========================================
- Hits        73746    66488    -7258
+ Misses      10160     8536    -1624
+ Partials      115        0     -115

Impacted Files
Coverage Δ

cpp/src/arrow/csv/column-builder.cc
95.39% <0%> (-1.98%)
:arrow_down:

go/arrow/math/uint64_amd64.go

go/arrow/memory/memory_avx2_amd64.go

js/src/enum.ts

go/arrow/array/builder.go

js/src/Arrow.node.ts

js/src/schema.ts

go/arrow/type_traits_boolean.go

js/src/ipc/node/writer.ts

js/src/visitor/vectorloader.ts

... and 120 more

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 aa765aa...8114887. Read the comment docs.


REPL possibility?

Would there be any way we could create a REPL environment by storing / parsing global set variables etc?
(as well is there a way to set process.argv as global?)

If you set env.MY_ENV_VAR, it will be automatically set to process.env.MY_ENV_VAR.
MY_ENV_VAR can be a string or number, or function or object...
const { evalCode } = await createRuntime({
  allowFetch: true, // inject fetch and allow the code to fetch data
  allowFs: true, // mount a virtual file system and provide node:fs module
  env: {
    MY_ENV_VAR: 'env var value'
  },
})

Within any program, you can also do globalThis.ANY_VAR = 'ANYTHING'
REPL will not simply possible, because of the nature of how things work with wasm & quickjs.
If the custom code is executed in the sandbox, the host system is basically blocked, until the code execution is completed.
To have some kind of REPL, you will need to rebuild the behavior of the event loop. QuickJS itself does not have an event loop like in node.js.
In general, I wonder, if QuickJS is the right choice for you at all - maybe something like wasmer fits better for your needs?

@sebastianwessel - I was curious if possibly use of babel could be applied here if option for stdin could be used.
And I think this project is exactly what I need - just wondering how far it can be pushed. (If that makes sense)....
10 years ago this whole project wouldn't have been possible but look at things now ;)

@sebastianwessel - as for repl inquiry too. Just as "fetch" can be injected etc as adapter. If we could inject other things into context as said outside function. Could we not block execution that way etc...? Either call function / return string or throw error if not string or function...?

@sebastianwessel - to do this we need a way to tell if QuickJSUseAfterFree / or waiting for dispose... To avoid lifetime messages etc...
Example of how we could do this (tho need a flag to wait for next run - not implemented):
let evalCode;
const nodeJS = async (code, outputCallback, errorCallback, processArgs=[]) => {

  const fetchAdapter = async (url, param) => {
  const res = await fetch(url, { ...param, mode: "cors" });
  return {
    status: res.status,
    ok: res.ok,
    statusText: res.statusText,
    json: async () => await res.json(),
    text: async () => await res.text(),
    formData: () => res.formData(),
    headers: res.headers,
    type: res.type,
    url: res.url,
    blob: async () => await res.blob(),
    bodyUsed: res.bodyUsed,
    redirected: res.redirected,
    body: res.body,
    arrayBuffer: async () => await res.arrayBuffer(),
    clone: () => res.clone(),
  };
};

   const quickJS = (await import("https://esm.sh/@sebastianwessel/quickjs@1.3.0")).quickJS
await import("https://esm.sh/typescript")
await import("https://esm.sh/@hazae41/symbol-dispose-polyfill");
  ///console.log(quickJS)
  const { createRuntime } = await quickJS('https://esm.sh/@jitl/quickjs-wasmfile-release-sync');

   if(!evalCode){
   evalCode = await createRuntime({
    allowFetch: false,
    allowFs: false,
    transformTypescript: true,
    fetchAdapter,
    env: {
      MY_ENV_VAR: 'env var value',
    },
    console: {
      log: (...message) => outputCallback(message),
      info: (...message) => outputCallback(message),
      warn: (...message) => outputCallback(message),
      error: (...message) => outputCallback(message),
    }
  });
   }

  try {
    const res = await evalCode.evalCode(code);
    console.log(res)
      //console.log(nodefs)
    return  res
  } catch (e) {

  }
};

const delay = (ms) => new Promise(resolve => setTimeout(resolve, ms));
const evalInRuntime = async (code) => {
  try {
    const res = await nodeJS(code);

    return res;
  } catch (e) {
    console.error(e.message);
  }
};

// Example REPL usage:
(async () => {
 //await initializeRuntime();
//
  let res =  await evalInRuntime(`let val = 10;`);

  res =  await evalInRuntime("val += 20;");

  res =  await evalInRuntime("return val");
  console.log("Result:", res);
})();

Even if it is wip, you can try this with this branch:
https://github.com/sebastianwessel/quickjs/pull/32
see example/basic for usage

@sebastianwessel - is this example of how I did this any use to you?

^ running all in the browser. Using a stdin - via my Termino.js library... Multi turn steps etc.. Using old / current version of library.


HL7 Serializer does not provide metadata for item errors and warnings

When submitting a report to RS, data is processed and errors and warnings are provided by the serializers and then placed in the JSON response to the user.  The CSV Serializer was updated correctly to provide metadata about errors and warnings that include the index (the report row number that had the problem) and an optional tracking ID.  However, the HL7 Serializer was not updated to provide this metadata and hence creates an inconsistency issue with these messages
This is a sample result from the Submissions history API for an HL7 submission.  Note the missing metadata.
 "warnings": [
        {
            "scope": "item",
            "index": null,
            "trackingId": null,
            "type": "warning",
            "message": "Report 1: Invalid field 'OBX-17-2' ('equipment_model_name'); please refer to the Department of Health and Human Services' (HHS) LOINC Mapping spreadsheet for acceptable values."
        },
        {
            "scope": "item",
            "index": null,
            "trackingId": null,
            "type": "warning",
            "message": "Report 1: Timestamp for ORC-15 - order_test_date should provide more precision. Should be formatted as YYYYMMDDHHMM[SS[.S[S[S[S]+/-ZZZZ"
        },

Acceptance criteria:

The HL7 serializer reports errors and warnings that includes the index for a given message.
The HL7 serializer reports errors and warnings that includes the tracking ID if available for a given message.  Note tracking IDs are optional.
The HL7 serializer reports error and warning message that do not include the report number.  Note that including a report number here not only is redundant to the provided index, but will affect our ability to later consolidate similar messages.

Hey team! Please add your planning poker estimate with ZenHub @jimduff-usds @whytheplatypus @jh765 @TurkeyFried @smythe5


Make range selection dynamic

Overview
As it stands, the get_file method, when collecting data from the given sheet, pulls everything in the range A1:Z1000, even though data is loaded in rows of 10. This is functional, but it's far from the best solution.
Issue
While it's unlikely that the contents of a file would exceed 500,000,000 characters, thereby exceeding the target range and leaving out any excess data, it's common sense to have something in place that would work with any amount of data. What's more is there's no reason to load in rows of only 10 and not 26, which is the base number of columns in Google Sheets.
Solution
When designing a solution, speed and efficiency must be kept in mind, which is why I'd lean towards firstly increasing upload block size to 26 - there's no reason to increase total array size and not use empty space; it would allow for faster upload times and less requests.
Along with that, as new rows are automatically appended as needed, all that would need to happen is a quick read from the r dict in get_file for the number of rows, and that value would be passed to the d call right after.

Implemented in e0f9bebcf4abe440aab23eb798931d52162e479e. The solution grabs row count from the sheet response in the first part of client.get, and uses that to determine range when pulling data. It will always be 1000 on anything under that row count, as it is the default and there's no reason to remove rows, but it will scale accordingly past that point.


[Bug] react-native-rename not working with expo inject project that generated from ignite cli

Log:
Something went wrong:  TypeError: Cannot read property 'replace' of undefined
at /Users/user/Desktop/MyApp/node_modules/react-native-rename/lib/index.js:98:42
The current app name in app.json of the expo injected app is different from the project generated from react-native-cli.
Please fix it.

Just add root "name" element in app.json
ex
{
  "name": "TravelApp", <-----
  "expo": {
    "name": "TravelApp",
    ...
    }
}

Hope it helps

Tks


[resolves #185] docker:stop cannot reliably stop/kill containers

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/wildfly-camel-pullreq/230/
Test PASSed.


Add linting

I'm working with limited internet access for the next couple weeks so I would appreciate it if we could hold off on merging this until after that. I'd like to give it a closer review. Ideally @redtoad would also take a look; as the main author, he should have final say about coding conventions and other stuff like this (or at least more final than me).

I'd like to see this split into multiple commits, probably one commit for each of the individual checks that are getting added. E.g. the first commit would contain only the configuration for black and the formatting changes introduced by it, the next commit would contain only the configuration for the various pre-commit hooks and any changes introduced by those, and so on. (The order doesn't matter, but since black probably makes the most extensive changes I'd personally do that one first.)

Thanks! Should be good to go once we wrap up the remaining threads.


Custom period

Fix for #1972.
Coverts custom periods into a start time (with end being today)

Merge logic into utils._interval_to_timedelta

@ValueRaider From what I can see it would only be called then if the interval is 5d, 1wk, 1mo, 3mo: where the original code for utils._interval_to_timedelta is fine. It would also then only be run if repair is True. Could you explain why you want these changes?

It's good coding practice: avoid duplicate logic.

It would also then only be run if repair is True

Huh? You are allowed to add another call to _interval_to_timedelta.

@ValueRaider done


cc-check: Always run all tests

Change "cc-check" so that it always runs all commands before erroring.
Previously, it would fail on first error, but this could mask the real
reason for failure. For example, on a system with nesting and vhost
disabled, "cc-check" would fail with a nesting error. But the nesting
check is not strictly required (#281) whereas vhost definitely is which
lead to confusing results for users.
"cc-check" will now run all tests and display an error message at the end
if any errors were found in the set of tests run.
Fixes #638.
Signed-off-by: James O. D. Hunt<EMAIL_ADDRESS>

LGTM

Again, coverall is stuck - the report is here: https://coveralls.io/jobs/29737580 (successful).


fix: Probot on kube doesn't work in prod builds

SSIA

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please ask for approval from tumido after the PR has been reviewed.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/approve
self merging, manifests need fixing

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: tumido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [tumido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


fix dependency for WordNet

not optimal (using local jar files instead of proper maven dependencies), but works

we better switch to dkpro similarity


[Improvement] Use of methods marked @VisibleForTesting in production code

What would you like to be improved?
This occurs in several places:
KerberosClient.java -  KerberosName.resetDefaultRealm();
HiveCatalogOperations.java - KerberosName.resetDefaultRealm();
KerberosClient.java - KerberosName.resetDefaultRealm();
PaimonConfig.java - ' new ConfigBuilder(PaimonCatalogPropertiesMetadata.PAIMON_METASTORE)' and  new ConfigBuilder(PaimonCatalogPropertiesMetadata.WAREHOUSE) and  new ConfigBuilder(PaimonCatalogPropertiesMetadata.URI)
BaseCatalogPropertiesMetadata.java - BaseCatalog.CATALOG_OPERATION_IMPL
IcebergPropertiesConverter.java - with GRAVITINO_ICEBERG_CATALOG_URI, GRAVITINO_ICEBERG_CATALOG_WAREHOUSE, ICEBERG_CATALOG_BACKEND_HIVE and GRAVITINO_ICEBERG_CATALOG_URI
IcebergPropertiesConverter.java -gravitinoProperties.get(IcebergPropertiesConstants.GRAVITINO_ICEBERG_CATALOG_WAREHOUSE); and with ICEBERG_CATALOG_TYPE and
How should we improve?
Either @VisiubleForTesting should be removed or the code not be called in production code.

@justinmclean  Hi. Does the fact that it shouldn't be called mean that you want me to remove the corresponding code?

You'll need to look at each one and see if it does need to be used. In most cases, I'd guess the @VisibleForTesting annotation should be removed as the method is used in non-testing code and the code is needed.

@justinmclean Do you mind if I try it ?

@jerryshao What do you think about the removal of KerberosName.resetDefaultRealm()? It's marked @VisibleForTesting so I assume we shouldn't be calling it, but there might be a good reason I'm unaware of.

I'm not so sure about this, maybe @yuqi1129 can better answer this.

@yuqi1129 what do you think?

I have confirmed that KerberosName.resetDefaultRealm() can be removed as it has no impact on the logic in fact. As for other codes, If they are used in production code, I believe we can remove the annotation VisibleForTesting to solve the problem.

@yuqi1129 please review the PR and leave the comments on the PR, thanks.


Add hex encode/decode fast path

Add a fast path for hex encode/decode.
Tasks:

[x] Finalize changes
[ ] Correctness test cases covering all new paths
[ ] Assert test with fast path
[ ] Assert test without fast path
[x] Perf test
[x] Releases

Performance change so far:

Encode fast path is about 80% faster
Decode fast path is about 90% faster

O2.hexfastO2.masterO2.130O2.124O2.113O2.102python
test-hex-decode.js3.9<IP_ADDRESS>1.4211.8814.77
test-hex-encode.js5.2910.1014.3813.6913.8813.861.52

Footprint change:

Fast path enabled: +1.3kB over master on x64 (most of it lookup tables)
Fast path disabled: no change over master on x64


Consider transitioning next release to 64 Bit

As reported by opennoms in https://github.com/lightningnetwork/lnd/issues/4811, as Lightning Node database grows in size, variant depending upon usage, eventually it will reach a point where it is too large for 32 bit process to handle.  For some reason this threshold on the file size is around 1GB in size.  Once the threshold is past, compaction requires running on a 64 bit platform.
Prior to hitting the limits, the database can be compacted following guidance opennoms has summarized here
https://openoms.gitbook.io/lightning-node-management/lnddatabasecompaction

The 64bit lite version of Raspberry Pi OS is available here
https://downloads.raspberrypi.org/raspios_lite_arm64/images/raspios_lite_arm64-2020-08-24/

I cant figure out has 64bit came out of beta or not?
If it did (which I doubt), why is it not available on the main download section.
Switching to 64bit for the guide is good plan.

That's a good input, thanks @lucasmoten. I actually considered switching to the 64bit Ubuntu server image, but it's quite a pain to setup the most basic things.
Will have a look at the Raspi OS 64bit for the next larger overhaul.

Anxiously waiting for the tutorial to upgrade Raspi OS to 64bit. Hope I don't need to close any of my channels to perform this upgrade.

I've successfully transitioned to the 64bit Ubuntu Server. I am in the process of writing the necessary changes that need to happen to achieve a successful installation of all parts.

That's a good input, thanks @lucasmoten. I actually considered switching to the 64bit Ubuntu server image, but it's quite a pain to setup the most basic things.
Will have a look at the Raspi OS 64bit for the next larger overhaul.

this would be amazing... not only that but also how to transition from a 32bit running system to a 64bit one, is it a simple case of setting up a second node and copying over the .lnd folder? Be GREAT to have a guide as simple as the rest of your wonderful guide!!

Yes, the transition only means that to build a new 64 bit system and copy the lnd folder over to the new node.
Would make sure everything works on the new system by creating (and disposing) an empty wallet first.
Also make sure to not run the lnd database on two places at the same time.
sudo system stop lnd
sudo systemctl disable lnd

before copying the folder over to stop it from restarting.
An lnd node is not active until unlocked with the password.
The latest (v1.7) release of the RaspiBlitz is running with the 64bit Raspberry OS: https://downloads.raspberrypi.org/raspios_arm64/images/ without any issues so far.
See the thread: https://github.com/rootzoll/raspiblitz/issues/1199

Yes, the transition only means that to build a new 64 bit system and copy the lnd folder over to the new node.
Would make sure everything works on the new system by creating (and disposing) an empty wallet first.
Also make sure to not run the lnd database on two places at the same time.
sudo system stop lnd
sudo systemctl disable lnd

before copying the folder over to stop it from restarting.
An lnd node is not active until unlocked with the password.
The latest (v1.7) release of the RaspiBlitz is running with the 64bit Raspberry OS: https://downloads.raspberrypi.org/raspios_arm64/images/ without any issues so far.
See the thread: rootzoll/raspiblitz#1199

According to docs.lightning.engineering, copying the lnd folder between different architectures is untested and should be avoided:
https://docs.lightning.engineering/lightning-network-tools/lnd/safety#migrating-a-node-to-a-new-device
Are you sure this will work?

@JssDWt from 32bit arm to 64bit arm (as the situation was the same with my raspiblitz nodes) I have done it multiple times without any problems.

This node has accomplished this feat https://www.reddit.com/r/TheLightningNetwork/comments/n45gsr/cornelius_is_now_64bit_i_feel_like_i_just_did/

I'm still on 32 bit. Curious, what practical advantages does the 64 bit upgrade bring for our use case, besides the ability to handle larger channel.db files?
I'm not afraid of the upgrade, but trying to understand if it's worth it. There's still room in my channel.db :)

I can tell you that my node has had its channel.db grow about 10GB in less than a week. At this rate I'm going to have to upgrade in a few months or risk losing my node. I'll probably be following the link that I posted before sooner rather than later.
I believe Raspbian has only had a 64bit version for a short time and it is still in beta https://www.raspberrypi.org/forums/viewtopic.php?t=275370
There are 64bit OSes for the RPi such as DietPi.

I can tell you that my node has had its channel.db grow about 10GB in less than a week. At this rate I'm going to have to upgrade in a few months or risk losing my node. I'll probably be following the link that I posted before sooner rather than later.

Maybe you could try this ... I don't think it fixes everything, but it should get a bit better.
 1043 ; If set to true, then we'll prune a channel if only a single edge is seen as
 1044 ; being stale. This results in a more compact channel graph, and also is helpful
 1045 ; for neutrino nodes as it means they'll only maintain edges where both nodes are
 1046 ; seen as being live from it's PoV.
 1047
 1048 routing.strictgraphpruning=true

Just finished upgrading to Raspberry OS 64-Bit (Buster).
Bitcoin Core and LND running smooth, I even managed to migrate to LiT thanks to the new tutorial.
Only issue is Electrs, it's not building. I opened an issue in their project explaining better: https://github.com/romanz/electrs/issues/457
I'd like to share something I did: the 1 TB SSD I had running somehow decreased it's speed to ~12 MB/sec. I even tested it with the SATA cable on my desktop and the speed was still the same, so I went to the "Update External Drive" page in the Bonus Section. I checked my office (and my pocket) and realised I had 2 extra SSDs with 512 GB capacity each and no money to buy a good quality 1 TB new drive, so I wrote a shell script to sync half of the files from the old drive to each new drive and then create symbolic links to those files in the second new one, making everything look like it's only in one place, but physically spread in two drives. It worked, but bitcoind accused the DB was corrupted, so I had to reindex everything. It didn't consume internet data, but took 5 days to reindex. Anyway, it saved me a few bucks and I'm happy it worked.
Another thing is that  Raspy couldn't power both SSDs at the same time, fortunately I also had in my office an externally powered USB 3.0 hub. Speeds tested, got ~300 MB/s in each.
If anyone could check the issue I opened to Electrs, any help is welcome.

I'd like to share something I did: the 1 TB SSD I had running somehow decreased it's speed to ~12 MB/sec.

Have you tried $ sudo fstrim -v /dev/sdX or just $ sudo fstrim -av?
# not getting much bang because cron does this all the time
$ sudo fstrim -va
/mnt/ssd: 0 B (0 bytes) trimmed on /dev/mapper/ssd
/mnt/old_boot: 204 MiB (213933056 bytes) trimmed on /dev/mmcblk0p1
/boot: 211.5 MiB (221756928 bytes) trimmed on /dev/sda1
/mnt/old_root: 0 B (0 bytes) trimmed on /dev/mapper/old_root

It's a bit tricky because many drives (typically if connected via USB) need some extra massaging to accept the SCSI commands over USB. See my post here: https://github.com/rootzoll/raspiblitz/issues/1805#issuecomment-892380571
There's also a systemd script that triggers fstrim once per week:
/usr/lib/systemd/system/fstrim.service
/usr/lib/systemd/system/fstrim.timer

I believe you turn that on via sudo systemctl enable fstrim.timer.

Have you tried $ sudo fstrim -v /dev/sdX or just $ sudo fstrim -av?

Thank you for answering.
 I connected the drive to the SATA cable in my desktop and the command took a few minutes to execute as follows:
~$ sudo fstrim -v /media/linus/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/
/media/linus/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/: 444,9 GiB<PHONE_NUMBER>20 bytes) trimmed

Anyway, speed is still mediocre, although it's 3x what it used to be:
$ sudo hdparm -t --direct /dev/sdc

/dev/sdc:
 Timing O_DIRECT disk reads: 100 MB in  3.00 seconds =  33.33 MB/sec

Anyway, speed is still mediocre, although it's 3x what it used to be

@raelschiffler I assume it's just worn down beyond repair then. How much free space? I'm very curious if speeds would go up massively once more data is deleted and you fstrim again. Theory suggests there could be a big speed increase, but SSD controllers are weird and unpredictable in practice.
Maybe even reformat the drive (mkfs.ext4 /dev/sdc) if you already migrated all the data to the new disks ...

@xanoni YOU WERE RIGHT!!!!
Formatting and re-fstrimming recovered the normal speed!
Now how can I use the scheduled fstrim if the enclosure does not support it?

CAN YOU BELIEVE IT TRIMMED ALMOST 1TB???
$ sudo fstrim -v /media/linus/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
[sudo] password for linus:
/media/linus/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: 937,9 GiB<PHONE_NUMBER>008 bytes) trimmed

I managed to allow the enclosure to trim the drive by following https://www.glump.net/howto/desktop/enable-trim-on-an-external-ssd-on-linux tutorial.
Very easy, anyone should try to avoid speed and data loss using a raspy.

Very easy, anyone should try to avoid speed and data loss using a raspy.

Yeah man, trim / unmap / discard is a bit of trouble with USB-connected drives (not sure why the Linux Kernel doesn't automatically do this for popular devices), but it is very much worth it!
I suggest RaspiPi adds udev settings/configuration/scripts at least for the recommended SSDs (SanDisk, Samsung, ...).

I think the original topic of this issue has been taken care of with the recent update to RaspiBolt v3. I'm closing this issue, but feel free to reopen it if you think it's still unsolved.


alxnet, googlenet do not convergence when using default initializer

When I use my own data set to play with alexnet and googlenet in the example/image-classifications, it seems that both models will not convergence when using the default initializer in train_model.py:
(   initializer =  mx.init.Xavier(factor_type="in", magnitude=2.34) )
However when I use mx.init.Normal() as the initializer, then the alexnet do convergence.
Is it possible to let user specific initializer when run example models, or set  mx.init.Normal() as the default initializer when playing with the example model ? Otherwise the user experience is bad when playing with these example models.

this is a old issuse

https://github.com/dmlc/mxnet/issues/826

try inception

I suggest to modify the example codes to make new users start easily. The code modification should be straightforward, e.g. provide get_initializer() for each example model and pass it as an argument to train_model.fit

@javelinjs  good idea

@realbns2008 Could you make a PR for this issue?

ok i will make a PR

This issue is closed due to lack of activity in the last 90 days. Feel free to reopen if this is still an active issue. Thanks!


Dropdown inside a Sidebar not overlaying correctly

A dropdown in a sidebar menu doesn't appear correctly outside of the sidebar.  Instead the dropdown menu adds a scrollbar to the sidebar.
http://jsfiddle.net/d0798fgd/

right but when you multiple item in the sidebar you cannot scroll .

@Trouche You can use Popup inside Menu.Item instead.

Setting the following solved the problem.
		.ui.vertical.sidebar.menu {
			overflow: visible !important;
		}

Thank you.


fixed images on Android

Method loadData  doesn't allow to load images with "file://" urls from application internal storage.
With method loadDataWithBaseURL images do load.
Also method  loadDataWithBaseURL works fine with RTL text
So I believe it is better to use loadDataWithBaseURL

this was already introduced with https://github.com/christopherdro/react-native-html-to-pdf/pull/77 ,but seems to be removed in https://github.com/christopherdro/react-native-html-to-pdf/commit/e33b86fb8ce71f5c090e620ddd3dc08a2f694ee2

@christopherdro  can you merge this please?

I can also confirm this fix solves the problem.
@christopherdro merging this would be very helpful and I believe it would fix issues such as  #182 or #144, thanks

Fix release in v0.9.0


[Feature] At present, the metadata pushed by the metadata center does not have an expiration date. When using Nacos as the metadata center, there is still a quantity limit. After switching to Redis as the metadata center, it was found that there is no expiration TTL setting

Pre-check

[X] I am sure that all the content I provide is in English.

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Apache Dubbo Component
Java SDK (apache/dubbo)
Descriptions
At present, the metadata pushed by the metadata center does not have an expiration date. When using Nacos as the metadata center, there is still a quantity limit. After switching to Redis as the metadata center, it was found that there is no expiration TTL setting
Also, the Jedis version is too low. Spring defaults to Jedis version 5.0.x, but it's still 3.x. Can we upgrade it
Related issues
No response
Are you willing to submit a pull request to fix on your own?

[ ] Yes I am willing to submit a pull request on my own!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

We can set TTL for it. But we need a mechanism to refresh it.
You can upgrade it in 3.3.x

We can set TTL for it. But we need a mechanism to refresh it.我们可以为它设置 TTL。但我们需要一种机制来刷新它。
You can upgrade it in 3.3.x您可以在 3.3.x 中升级它

Currently, the Redis metadata center implementation class of 3.3.0 is being used, but there is no TTL code available. We will continue to monitor future updates

We can set TTL for it. But we need a mechanism to refresh it.
You can upgrade it in 3.3.x

Currently, the Redis metadata center implementation class of 3.3.0 is being used, but there is no TTL code available. We will continue to monitor future updates

Would you like to contribute for it:)

hello，I think I can solve it, can it be assigned to me, thanks

We can set TTL for it. But we need a mechanism to refresh it.我们可以为它设置TTL。但是我们需要一种机制来刷新它。
You can upgrade it in 3.3.x您可以在 3.3.x 中升级它

Currently, the Redis metadata center implementation class of 3.3.0 is being used, but there is no TTL code available. We will continue to monitor future updates目前，正在使用 Redis 元数据中心实现类 3.3.0，但没有可用的 TTL 代码。我们将继续关注未来的更新

Would you like to contribute for it:)你愿意为它做出贡献吗：）

hello，I think I can solve it, can it be assigned to me, thanks

We can set TTL for it. But we need a mechanism to refresh it.我们可以为它设置TTL。但是我们需要一种机制来刷新它。
You can upgrade it in 3.3.x您可以在 3.3.x 中升级它

Currently, the Redis metadata center implementation class of 3.3.0 is being used, but there is no TTL code available. We will continue to monitor future updates目前，正在使用 Redis 元数据中心实现类 3.3.0，但没有可用的 TTL 代码。我们将继续关注未来的更新

Would you like to contribute for it:)你愿意为它做出贡献吗：）

hello，I think I can solve it, can it be assigned to me, thanks

Please go ahead

我们可以为其设置TTL。但我们需要一个机制来刷新它。
您可以在3.3.x中升级它

目前正在使用3.3.0的Redis元数据中心实现类，但没有可用的TTL代码。我们将继续关注未来的更新

hello when would you need to use metadata expiration?

我们可以为其设置TTL。但我们需要一个机制来刷新它。
您可以在3.3.x中升级它

目前正在使用3.3.0的Redis元数据中心实现类，但没有可用的TTL代码。我们将继续关注未来的更新

hello when would you need to use metadata expiration?

I want to know the specific scenario😊

我们可以为其设置TTL。但我们需要一个机制来刷新它。
您可以在3.3.x中升级它

目前正在使用3.3.0的Redis元数据中心实现类，但没有可用的TTL代码。我们将继续关注未来的更新

hello when would you need to use metadata expiration?

I want to know the specific scenario😊

I don't know what the logic is now.
After long-term use, the data will be more and more, and many data have expired.
I hope that unnecessary data can be automatically eliminated.


Improve error messages when ECS task failed to start

The current error message is not enough.
ECS Container task failed to start due to temporary AWS issues: stopCode=TaskFailedToStart, stoppedReason=Task failed to start, containerExitCode=null
Please retry workflow tasks. Refer https://docs.digdag.io/workflow_definition.html#retrying-failed-tasks-automatically for detail.
ECS error codes are available on https://docs.aws.amazon.com/AmazonECS/latest/userguide/stopped-task-error-codes.html

So, this PR improves error messages when ECS task failed to start.

will fix CI failure.
Fix PyIT.verifyLogWithDuplicateModuleError for expected error message.


Update "Some of this information is wrong" content on the verified page

 Update "Some of this information is wrong" content on /verified page


Adding a status circle on right bottom

Would a feature that could show status based on, for example, online/offline/busy/away be a good idea as a part of the library?
Refer below image :

While I guess that having some kind of status indicator would be of use for some cases, I find it a little to specific for a general purpose library like this one. But you could always just subclass CircleImageView to add that functionality.


No tests found when running npm run test:unit

Version
3.0.0-rc.3
Reproduction link
https://github.com/hajarrashidi/Vue-test-utils-example
Steps to reproduce
Windows 10 cmd:
vue create app
cd app
npm run test:unit
What is expected?
To run jest unit tests
What is actually happening?
When i create a project with vue create and run test i get errors. Not what i expect from a new project.

Maybe has something to do with testMatch being wrong in windows
testMatch: C:\Users\hajar.rashidi\repos\Vue-test-utils-example\app(tests\unit***.spec.(js|jsx|ts|tsx)|**_tests_*.(js|jsx|ts|tsx)) - 0 matches
Image
https://imgur.com/lW9IMZO

This may be a Jest bug: https://github.com/facebook/jest/issues/6546

This is a dup of #1686 , see if that workaround helps you


typo detection points to wrong position and should probably not trigger in inherit

The little ^ is at the wrong position and this should probably not be nitted at all.
See https://github.com/NixOS/nixpkgs/pull/113405#issuecomment-780798227
When evaluating attribute ‘gambit’:
warning: attribute-typo
A likely typo in `git-version` argument was found, did you mean `version`?
Near /home/hotpi/src/nixpkgs2/pkgs/development/compilers/gambit/build.nix:25:10:
|
25 |   inherit src version git-version;
|          ^                                                                                See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/attribute-typo.md

agpl3 is a deprecated license, check if project uses agpl3Plus or agpl3Only and change meta.license accordingly.

Near pkgs/development/haskell-modules/generic-builder.nix:640:19:

────────────────────
    |
640 |   meta = { inherit homepage license platforms; }
    |                   ^
────────────────────

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/unclear-gpl.md

another example of the ^ being wrong.

builtins.unsafeGetAttrPos currently returns the location of end of the inherit token for all inherited attributes. We would need to fix Nix or get the data from rnix somehow.


[Nice-To-Have] integrate salt efforts upstream

It would be nice to integrate some of our work, if possible, for deployment on openSUSE, upstream. So that we can make people aware that openSUSE is also supported for salt deployments of kubernetes not just Red Hat distros and Debian.

also, we might want to look at this, since it seems the link above points to a part of the repo they will move out to https://github.com/kubernetes/kube-deploy

closing this based on this card. deployments will, most probably, follow upstream and upstream uses mostly containerized solutions. https://trello.com/c/TjCTCAhN/189-upstream-future-of-salt-stack-based-provisioning


[voe] Add new extractor

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] Searched the bugtracker for similar pull requests
[x] Read adding new extractor tutorial
[x] Read youtube-dl coding conventions and adjusted the code to meet them
[x] Covered the code with tests (note that PRs without tests will be REJECTED)
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[ ] Improvement
[x] New extractor
[ ] New feature

Description of your pull request and other information
Extracts m3u8 with regex, then let's ytdl handle the rest
Resolves #29232.

JanzenJohn commented Apr 22, 2023:

the PR does not seem to work for me because the url they redirect me to "scatch176duplicities.com" is not recognized (but seems to be just a voe.sx mirror)


Adv code run into some kind of problem

The program threw the exceptions saying that it cannot find certain output and result file, how should i solve this

The bug look like this and there's no pth within the file

@TheOnlylight, It seems that there're no data in the data/ folder. Due to the copyright, we only list sample data in the repo. You should follow the descript of the dataset and preprocess script to prepare the dataset and put them in the data/ folder.


fix input on example from source-target to source-tag

Summary of PR changes
I didn't do a version bump since this was just a readme change.
PR Requirements

[X] For major, minor, or breaking changes, at least one of the commit messages contains the appropriate +semver: keywords.

See the Incrementing the Version section of the repository's README.md for more details.

[X] The action code does not contain sensitive information.

NOTE: If the repo's workflow could not automatically update the README.md, it should be updated manually with the next version.  For javascript actions, if the repo's workflow could not automatically recompile the action it should also be updated manually as part of the PR.

It the CI failing because I forked this? I didn't have permission to branch in here so I forked it.


About Page: Youtube Webinar embedded link not working

https://hub.aashe.org/about/
The actual URL to the webinar on our Youtube page is correct, not sure why the embedded info isn't.

@rerb , is this something we can fix fairly quickly? Should it get added to the Contractor list?


chore(deps): update dependency ts-loader to v8.0.4

This PR contains the following updates:

Package
Type
Update
Change

ts-loader
devDependencies
patch
8.0.3 -> 8.0.4

Release Notes

TypeStrong/ts-loader
v8.0.4
Compare Source

Uses existing instance if config file is same as already built solution - thanks @sheetalkamat

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

Available now for Enterprise: Renovate Pro with real-time webhook handling and priority job queue.

PR has been edited
:construction_worker: This PR has received other commits, so Renovate will stop updating it to avoid conflicts or other problems. If you wish to abandon your changes and have Renovate start over you may click the "rebase" checkbox in the PR body/description.

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

v5.4.5
GitHub release

Your semantic-release bot :package::rocket:


Paket.Restore.targets seems to break intellisense

Description
I have a project structure like this:
Sln\Sln.sln
Sln\src\Test.Proj1\Test.Proj1.fsproj
Sln\src\Test.Proj2\Test.Proj2.fsproj

Proj1 is a library.  It has no references to anything other than FSharp.Core.  It was created with dotnet new classlib -lang F#, and targets net461.
Proj2 is an app, also created with dotnet new console -lang F#.  It has a ProjectReference to ..\..\Test.Proj1\Test.Proj1.fsproj, and similarly targets net461.
My dotnet --info:
C:\Users\ben\proj\scratch\test-ionide\20171026-paket
λ  dotnet --info
.NET Command Line Tools (2.0.2)

Product Information:
 Version:            2.0.2
 Commit SHA-1 hash:  a04b4bf512

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.15063
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.0.2\

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.0
  Build    : e8b8861ac7faf042c87a5c2f9f2d04c98b69f28d

dotnet restore on the solution works, as does dotnet build.  However, when I open the project in Ionide, the intellisense features fail, and the following is shown in the editor:

Similarly, MSBuild <IP_ADDRESS>001 builds the projects with no problem.  But Visual Studio 2017 (15.4.1 with Visual F# 4.1) intellisense fails, showing this in the editor:

Repro steps
Please provide the steps required to reproduce the problem

mkdir 20171026-paket; mkdir 20171026-paket\src; mkdir 20171026-paket\src\Test.Proj1; mkdir 201721026-paket\src\Test.Proj2

cd 20171026-paket, dotnet new sln

cd src\Test.Proj``, dotnet new classlib -lang F#`

cd ..\Test.Proj2, dotnet new console -lang F#

cd ..\..\, dotnet sln add src\Test.Proj1\Test.Proj1.fsproj, dotnet sln add src\Test.Proj2\Test.Proj2.fsproj

Edit both project files and change <TargetFramework>...</TargetFramework> to <TargetFramework>net461</TargetFramework>

Edit Test.Proj2.fsproj with these lines:

<ItemGroup>
  <ProjectReference Include="..\..\Test.Proj1\Test.Proj1.fsproj" />
</ItemGroup>

Edit Test.Proj2\Test.Proj2.fs to refer to something in Test.Proj1.  I used the following to keep it simple:

// Learn more about F# at http://fsharp.org

[<EntryPoint>]
let main argv =
    argv |> ignore
    printfn "%A from F#!" <| Test.Proj1.Say.hello "Ben"
    0 // return an integer exit code

From solution dir, run dotnet restore; dotnet build and note successful build.

Open solution dir in Code+Ionide; observe successful load

Download Paket bootstrapper like so (using PowerShell; iwr is equivalent to curl):  iwr https://github.com/fsprojects/Paket/releases/download/5.119.8/paket.bootstrapper.exe -OutFile .paket\paket.bootstrapper.exe

Run boostrapper.

Run .paket\paket.exe convert-from-nuget; observe that the Paket.Restore.targets file is created in .paket\, and also that the <Import Project="..\..\.paket\Paket.Restore.targets" /> line is inserted into both Test.Proj1.fsproj and Test.Proj2.fsproj.

Close Code.

From solution dir, run dotnet restore; dotnet build.  Observe successful build.

Open solution folder in Code, open the Test.Proj2.fs file; wait for language service to respond; observe intellisense errors in editor as shown in description.

Bonus Steps

Comment out <Import Project="..\..\.paket\Paket.Restore.targets" /> lines in both project files.

Close Code

From solution dir run dotnet restore; dotnet build.  Observe successful build.

Open in Code; wait for language service response; observe intellisense failure.  I don't know how to explain this part because paket should be out of the picture.

intellisense-failure.zip
Expected behavior
Intellisense in both Code+Ionide and Visual F# should work in the presence of the Paket.Restore.targets import.
Here is the DEBUG output from the F# language service:
[10:38:06 DEBUG] RES (011) <- {project} in 904 ms: Kind={"error"}
Data={"Code":1,"Message":"MSBuild failed with exitCode 1 Working Directory: 'd:\\Users\\ben\\proj\\scratch\\test-ionide\\20171026-paket\\src\\Test.Proj2' Exe Path: 'dotnet' Args: 'msbuild d:\\Users\\ben\\proj\\scratch\\test-ionide\\20171026-paket\\src\\Test.Proj2\\Test.Proj2.fsproj /p:SkipCompilerExecution=true /p:ProvideCommandLineArgs=true /p:CopyBuildOutputToOutputDirectory=false /p:UseCommonOutputDirectory=true /t:_Inspect_FscArgs /p:_Inspect_FscArgs_OutFile=C:\\Users\\ben\\AppData\\Local\\Temp\\tmpB86E.tmp.FscArgs.txt /p:DesignTimeBuild=true /t:_Inspect_GetResolvedProjectReferences /p:_Inspect_GetResolvedProjectReferences_OutFile=C:\\Users\\ben\\AppData\\Local\\Temp\\tmpB87F.tmp.GetResolvedProjectReferences.txt /t:_Inspect_GetProperties /p:_Inspect_GetProperties_OutFile=C:\\Users\\ben\\AppData\\Local\\Temp\\tmpB880.tmp.GetProperties.txt /nologo /verbosity:quiet'\r\nLog: \r\nwriting helper target file in 'd:\\Users\\ben\\proj\\scratch\\test-ionide\\20171026-paket\\src\\Test.Proj2\\obj\\Test.Proj2.fsproj.proj-info.targets'\r\nC:\\Program Files\\dotnet\\sdk\\2.0.2\\Sdks\\Microsoft.NET.Sdk\\build\\Microsoft.PackageDependencyResolution.targets(165,5): error : Assets file 'C:\\Users\\ben\\proj\\scratch\\test-ionide\\20171026-paket\\src\\Test.Proj2\\obj\\project.assets.json' doesn't have a target for '.NETFramework,Version=v4.6.1/win7-x86'. Ensure that restore has run and that you have included 'net461' in the TargetFrameworks for your project. You may also need to include 'win7-x86' in your project's RuntimeIdentifiers. [d:\\Users\\ben\\proj\\scratch\\test-ionide\\20171026-paket\\src\\Test.Proj2\\Test.Proj2.fsproj]\r\n\r\n","AdditionalData":{}}
[10:38:06 ERROR] Project loading failed, MSBuild failed with exitCode 1 Working Directory: 'd:\Users\ben\proj\scratch\test-ionide\20171026-paket\src\Test.Proj2' Exe Path: 'dotnet' Args: 'msbuild d:\Users\ben\proj\scratch\test-ionide\20171026-paket\src\Test.Proj2\Test.Proj2.fsproj /p:SkipCompilerExecution=true /p:ProvideCommandLineArgs=true /p:CopyBuildOutputToOutputDirectory=false /p:UseCommonOutputDirectory=true /t:_Inspect_FscArgs /p:_Inspect_FscArgs_OutFile=C:\Users\ben\AppData\Local\Temp\tmpB86E.tmp.FscArgs.txt /p:DesignTimeBuild=true /t:_Inspect_GetResolvedProjectReferences /p:_Inspect_GetResolvedProjectReferences_OutFile=C:\Users\ben\AppData\Local\Temp\tmpB87F.tmp.GetResolvedProjectReferences.txt /t:_Inspect_GetProperties /p:_Inspect_GetProperties_OutFile=C:\Users\ben\AppData\Local\Temp\tmpB880.tmp.GetProperties.txt /nologo /verbosity:quiet'
Log:
writing helper target file in 'd:\Users\ben\proj\scratch\test-ionide\20171026-paket\src\Test.Proj2\obj\Test.Proj2.fsproj.proj-info.targets'
C:\Program Files\dotnet\sdk\2.0.2\Sdks\Microsoft.NET.Sdk\build\Microsoft.PackageDependencyResolution.targets(165,5): error : Assets file 'C:\Users\ben\proj\scratch\test-ionide\20171026-paket\src\Test.Proj2\obj\project.assets.json' doesn't have a target for '.NETFramework,Version=v4.6.1/win7-x86'. Ensure that restore has run and that you have included 'net461' in the TargetFrameworks for your project. You may also need to include 'win7-x86' in your project's RuntimeIdentifiers. [d:\Users\ben\proj\scratch\test-ionide\20171026-paket\src\Test.Proj2\Test.Proj2.fsproj]

Actual behavior
Intellisense fails in products that otherwise function properly.
Known workarounds
None.

@Krzysztof-Cieslak @enricosada I don't think this is a paket issue, or is it?

I wasn't 100% sure this was paket, but it seemed like my best guess because it was the variable that determined whether this behavior manifested or not (i.e., this only happened with paket projects).  What confuses me is that the behavior lingers after removing paket from a project.

I can't reproduce in mono with that zip for what it's worth.


Mixtral hanging if the first prompt is "too long"

Prerequisites
Please answer the following questions for yourself before submitting an issue.

[x] I am running the latest code. Development is very rapid so there are no tagged versions as of now.
[x] I carefully followed the README.md.
[x] I searched using keywords relevant to my issue to make sure that I am creating a new issue that is not already open (or closed).
[x] I reviewed the Discussions, and have a new bug or useful enhancement to share.

Expected Behavior
I was trying to make Mixtral chat completion work with llama-cpp-python (either directly in Python and Server) independently of the given prompt.
I defined two kinds of prompt:
SHORT_PROMPT
{
  "messages": [
{"role": "system", "content": "This is a short prompt."},
{"role": "user", "content": "This is a short prompt."}
]
}

LONG_PROMPT
{
  "messages": [
{"role": "system", "content": "This is a long prompt. This is a long prompt. This is a long prompt. This is a long prompt. This is a long prompt. This is a long prompt. This is a long prompt. This is a long prompt. This is a long prompt. This is a long prompt. This is a long prompt. "},
{"role": "user", "content": "This is a long prompt. This is a long prompt. This is a long prompt. This is a long prompt. This is a long prompt. This is a long prompt. This is a long prompt. This is a long prompt. This is a long prompt. This is a long prompt. "}
]
}

I would expect that the model answers something independently of what prompt I give.
Current Behavior
If I

Start the server
Send the SHORT_PROMPT (or any other short prompt)  and wait for result
Send the LONG_PROMPT and wait for result
everything is ok (= the model answers quickly)

If I

Start the server
Send the LONG_PROMPT and wait for result
It hangs seemingly forever, with gpu utilization at 0% (see below)

If I send exponentially longer prompts each time, it sometime hangs at ~1200 characters (json structure included), other times at ~3000.
I tried:

Waiting for about 20/30m.
I tried by sending a request to the server or using the UI at localhost:8123/docs, same result.
Also instantiating Lama() from llama-cpp-python directly in python, using the same parameters, same results.
Using stream=True, nothing is sent back while it hangs
Changing context size to 2000. Seems not to change much.

When process hangs:
top:
 PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
2668867 user      20   0  111,8g  42,6g  41,7g S 100,3  33,9   0:45.34 python3

+-----------------------------------------------------------------------------+
| NVIDIA-SMI 525.147.05   Driver Version: 525.147.05   CUDA Version: 12.0     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA RTX A6000    Off  | 00000000:01:00.0  On |                  Off |
| 36%   66C    P2    85W / 300W |  22124MiB / 49140MiB |      4%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   1  NVIDIA RTX A6000    Off  | 00000000:4B:00.0 Off |                  Off |
| 30%   57C    P2    86W / 300W |  19902MiB / 49140MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

Environment and Context

Physical (or virtual) hardware you are using, e.g. for Linux:

AMD Ryzen Threadripper 3960X 24-Core Processor
GPU: 2x A6000 49Gb
Linux redacted 5.15.0-91-generic #101-Ubuntu SMP Tue Nov 14 13:30:08 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Steps to Reproduce

Installed llama-cpp-gpu with CMAKE_ARGS="-DLLAMA_CUBLAS=on" pip install 'llama-cpp-python[server]'  --upgrade --force-reinstall --no-cache-dir
I run the server with  ``python3 -m llama_cpp.server  --n_gpu_layers 35 --model "<my_model_fodler>/mixtral-8x7b-instruct-v0.1.Q6_K.gguf" --host <IP_ADDRESS> --port 8123 --n_ctx 30000"
See Current behaviour.

Failure Logs
No log is produced since the process hangs indefinitely.
Example environment info:

llama-cpp-python$ python3 --version
Python 3.10.12

llama-cpp-python$ pip list | egrep "llama|uvicorn|fastapi|sse-starlette|numpy"
fastapi                   0.105.0
llama_cpp_python          0.2.24
numpy                     1.26.2
sse-starlette             1.8.2
uvicorn                   0.24.0.post1

@edoardogiacomello
If you are still facing same issues in latest version. Can you paste the output from the llama.cpp that appears when you start the server or use directly. Before you send any request at all, Similar to following:
llm_load_print_meta: LF token         = 13 '<0x0A>'
llm_load_tensors: ggml ctx size       =    0.38 MiB
llm_load_tensors: using CUDA for GPU acceleration
llm_load_tensors: system memory used  = 25962.90 MiB
llm_load_tensors: VRAM used           = 4772.97 MiB
llm_load_tensors: offloading 5 repeating layers to GPU
llm_load_tensors: offloaded 5/33 layers to GPU

Tried your example on my machine, i could not reproduce it.

I tried again today with the old package and the problem persisted. However, upgrading to the latest version of llama-cpp-python seems to have solved the issue, I'll keep doing more tests as soon as I can.
Current package versions:
fastapi                   0.108.0
llama_cpp_python          0.2.27
numpy                     1.26.3
sse-starlette             1.8.2
uvicorn                   0.25.0

Thank you!


Support revoke for sdh

Enacted some feedback and added some more tests. This won't pass CI until after updating to do chaining.

new one coming soon


Support xunlei(迅雷) authentication

docs:http://dev.open-api-auth.xunlei.com/platform?m=Developer&op=docPage&segment=introduce

@seriouszyx @Steve0x2a

I'll work on this, but the current problem is that I can't create XUNLEI applications without real name authentication, and  can't find the real name authentication portal.

I will contact xunlei company
获取 Outlook for iOShttps://aka.ms/o0ukef

发件人: Steve0x2a @.>
发送时间: Saturday, January 22, 2022 12:34:34 PM
收件人: casdoor/casdoor @.>
抄送: Jianle Chen @.>; Author @.>
主题: Re: [casdoor/casdoor] Support xunlei(迅雷) authentication (Issue #435)
I'll work on this, but the current problem is that I can't create XUNLEI applications without real name authentication, and can't find the real name authentication portal.
―
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcasdoor%2Fcasdoor%2Fissues%2F435%23issuecomment-1019046952&data=04|01||c1c5ddcd5f534e9b2f9f08d9dd607e10|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637784228763536999|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=22U5f%2FfVHSZf1k9N7Ypg4r4Og8yf3yWeQietLpbRMZw%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAEHBFI7TCRLAP3Z46G3AZHLUXIXVVANCNFSM5MPWGA5Q&data=04|01||c1c5ddcd5f534e9b2f9f08d9dd607e10|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637784228763536999|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=uK6CvEk9HRXcj8g0CmA1QyA2i3yQ6GS63V58hRQL62c%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01||c1c5ddcd5f534e9b2f9f08d9dd607e10|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637784228763536999|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=vJit0Nj%2BzrvOiExtl6TsSQNCVA1mT%2FyyJNVSfU0mKt0%3D&reserved=0 or Androidhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01||c1c5ddcd5f534e9b2f9f08d9dd607e10|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637784228763536999|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=lseb9YS8wG2DE0SoPrr38hWyhdLMOyUODbmt1e3Yn3o%3D&reserved=0.
You are receiving this because you authored the thread.Message ID: @.***>

@qq690712575 Xunlei has replied to me with the relevant information: to apply for the application, you need to send an email to Xunlei Business and get permission. So I don't think Casdoor's Xunlei support is a high priority.
If you could provide us with an application to test, it might speed up the process a lot.

low-priority, closed.


Memory Leak issues

Hi guys,
according to this blog post https://vuejs.org/v2/cookbook/avoiding-memory-leaks.html, it looks like "glide" instance is not properly destroyed on component destroy.
I guess the simple solution is to add this :
beforeDestroy() {
   if (this.glide) this.glide.destroy()
}

Do you want a PR for that ?

А ведь утечка-то есть... Антон, хотя б последний файл-то замердж (c beforeDestroy()). В SPA раз 5 релоадишь компонент и начинает тупить с каждым разом всё больше... (

@dfabreguette-ap , I saw your PR . As @antonreshetov didn't merged it ( he probably not gonna continue working on vue-glide ) , is it safe too use your repository for glide ? or can i simply use
 beforeDestroy() {
   if (this.glide) this.glide.destroy()
}

in my component were vue-glide is imported??

There is no memory leakage. When a component is created, a new Glide.js instance is created and assigned to a local variable. When the component is destroyed, all local variables will also be destroyed, so there is no need to call Glide.js destroy method.

Alright, thx !


Add 10.1371/journal.pcbi.1005283

Add neurotransmitter expression info to insert_worm.py and attach Evidence with the author, title, DOI (below) and one or more URLs. Any other info available for the Evidence is desired.
Machine readable data is attached to the document on the web and is available here: http://journals.plos.org/ploscompbiol/article/file?type=supplementary&id=info:doi/10.1371/journal.pcbi.1005283.s004
DOI: 10.1371/journal.pcbi.1005283
Child of #274
related to #293 (overlap in the data source)

Still needs an update to the data sources page.

I'm going to hold off on that until the data spreadsheet here https://docs.google.com/spreadsheets/d/1kCxOOKu1wAREa9VbBiWVVHh-GEC3kJk0A3YVEipPKcc/edit#gid=0 has been cloned and put in the openworm public folder so I can link to it there rather than my own copy.
Incidentally, I don't think I can label or self-assign issues.


Translate language names

Translate and add full names of languages to settings

:tada: This issue has been resolved in version timeclicker_client-v1.10.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket: