App crash after kill the application. (Agora 6.0.0 and  6.1.0)

I use agora_rtc 6.1.0, try with both flutter 3.3 and 3.7
platform ios 16.1.0, 16.1.1, 16.2, 16.3
After initializing the agora engine (opening the camera), then swiping the app (kill app) the crash pop-up was shown.
This is the error log from Xcode.

[2023-01-27 10:30:24.272] [958] [debug] [iris_rtc_engine_impl.cc:114] api name RtcEngine_setupLocalVideo params {"canvas":{"uid":0,"view":0}}
[2023-01-27 10:30:24.273] [958] [debug] [iris_rtc_engine_impl.cc:132] ret 0 result {"result":0}
[2023-01-27 10:30:24.284] [958] [debug] [iris_rtc_engine_impl.cc:114] api name RtcEngine_leaveChannel params {"options":null}
[2023-01-27 10:30:24.285] [958] [debug] [iris_rtc_engine_impl.cc:132] ret 0 result {"result":0}
[2023-01-27 10:30:24.285] [958] [debug] [iris_rtc_engine_impl.cc:114] api name RtcEngine_release params {"sync":false}
[2023-01-27 10:30:24.285] [958] [debug] [iris_rtc_engine_impl.cc:233] IrisRtcEngineImpl __release
[2023-01-27 10:30:24.285] [958] [debug] [iris_rtc_device_manager_impl.cc:36] IrisRtcDeviceManagerImpl Release
[2023-01-27 10:30:24.285] [958] [debug] [iris_rtc_device_manager_wrapper.cc:791] IDeviceManagerWrapper Release
[2023-01-27 10:30:24.285] [958] [debug] [iris_rtc_media_player_impl.cc:43] IrisMediaPlayerImpl Release
[2023-01-27 10:30:24.285] [958] [debug] [iris_rtc_media_player_wrapper.cc:39] IMediaPlayerWrapper release
[2023-01-27 10:30:24.285] [958] [debug] [iris_rtc_spatial_audio_engine_impl.cc:214] IrisLocalSpatialAudioEngineImpl Release
[2023-01-27 10:30:24.285] [958] [debug] [iris_rtc_spatial_audio_engine_wrapper.cc:388] ILocalSpatialAudioEngineWrapper release
[2023-01-27 10:30:24.285] [958] [debug] [iris_rtc_media_recoder_impl.cc:26] IrisMediaRecoderImpl Release
[2023-01-27 10:30:24.285] [958] [debug] [iris_rtc_media_recoder_wrapper.cc:37] IMediaRecoderWrapper Release
[2023-01-27 10:30:24.285] [958] [debug] [iris_rtc_music_center_impl.cc:31] IrisMusicCenterImpl Release
[2023-01-27 10:30:24.285] [958] [debug] [iris_rtc_music_center_wrapper.cc:28] IrisMusicContentCenterWrapper release
[2023-01-27 10:30:24.285] [958] [debug] [iris_rtc_engine_wrapper.cc:8191] IRtcEngineWrapper release
[2023-01-27 10:30:24.291] [958] [debug] [iris_rtc_engine_impl.cc:132] ret 0 result {"result":0}
[2023-01-27 10:30:24.291] [958] [debug] [iris_rtc_engine_impl.cc:49] IrisRtcEngineImpl Destroy
[2023-01-27 10:30:24.291] [958] [debug] [iris_rtc_music_center_impl.cc:21] IrisMusiImpl Destroy
[2023-01-27 10:30:24.291] [958] [debug] [iris_rtc_media_recoder_impl.cc:15] IrisMediaRecoderImpl Destroy
[2023-01-27 10:30:24.291] [958] [debug] [iris_rtc_spatial_audio_engine_impl.cc:203] IrisLocalSpatialAudioEngineImpl Destroy
[2023-01-27 10:30:24.291] [958] [debug] [iris_rtc_media_player_impl.cc:28] IrisMediaPlayerImpl Destroy
[2023-01-27 10:30:24.291] [958] [debug] [iris_rtc_device_manager_impl.cc:25] IrisRtcDeviceManagerImpl Destroy
[2023-01-27 10:30:32.879] [958] [debug] [iris_rtc_engine_impl.cc:79] IrisRtcEngineImpl Initialize
[2023-01-27 10:30:32.880] [958] [debug] [iris_logger.cc:92] /var/mobile/Containers/Data/Application/92013E3E-734C-4C52-A7E7-39FAEF8261D6/Library/Caches/agora-iris.log
[2023-01-27 10:30:32.880] [958] [debug] [iris_logger.cc:92] /var/mobile/Containers/Data/Application/92013E3E-734C-4C52-A7E7-39FAEF8261D6/Library/Caches/agora-iris.log
[2023-01-27 10:30:32.880] [958] [debug] [iris_logger.cc:92] /var/mobile/Containers/Data/Application/92013E3E-734C-4C52-A7E7-39FAEF8261D6/Library/Caches/agora-iris.log
[2023-01-27 10:30:32.882] [958] [debug] [iris_rtc_engine_impl.cc:112] api name RtcEngine_initialize params {"context":{"appId":"08735b01","channelProfile":1}}
[2023-01-27 10:30:32.940] [958] [debug] [iris_rtc_device_manager_impl.cc:29] IrisRtcDeviceManagerImpl Initialize
[2023-01-27 10:30:32.940] [958] [debug] [iris_rtc_media_player_impl.cc:32] IrisMediaPlayerImpl Initialize
[2023-01-27 10:30:32.940] [958] [debug] [iris_rtc_spatial_audio_engine_impl.cc:207] IrisLocalSpatialAudioEngineImpl Initialize
[2023-01-27 10:30:32.940] [958] [debug] [iris_rtc_media_recoder_impl.cc:19] IrisMediaRecoderImpl Initialize
[2023-01-27 10:30:32.940] [958] [debug] [iris_rtc_music_center_impl.cc:25] IrisMusicPlayerImpl Initialize
[2023-01-27 10:30:32.940] [958] [debug] [iris_rtc_engine_impl.cc:132] ret 0 result {"result":0}
[2023-01-27 10:30:32.941] [958] [debug] [iris_rtc_engine_impl.cc:114] api name RtcEngine_setAppType params {"appType":4}
[2023-01-27 10:30:32.941] [958] [debug] [iris_rtc_engine_impl.cc:132] ret 0 result {"result":0}
[2023-01-27 10:30:32.941] [958] [debug] [iris_rtc_engine_impl.cc:114] api name RtcEngine_registerEventHandler params {"event":10760404816}
[2023-01-27 10:30:32.941] [958] [debug] [iris_rtc_engine_impl.cc:132] ret 0 result {"result":0}
[2023-01-27 10:30:32.941] [958] [debug] [iris_rtc_engine_impl.cc:114] api name RtcEngine_setClientRole params {"options":null,"role":2}
[2023-01-27 10:30:32.942] [958] [debug] [iris_rtc_engine_impl.cc:132] ret 0 result {"result":0}
[2023-01-27 10:30:32.942] [958] [debug] [iris_rtc_engine_impl.cc:114] api name RtcEngine_setChannelProfile params {"profile":1}
[2023-01-27 10:30:32.942] [958] [debug] [iris_rtc_engine_impl.cc:132] ret 0 result {"result":0}
[2023-01-27 10:30:32.944] [958] [debug] [iris_rtc_engine_impl.cc:114] api name RtcEngine_enableVideo params {}
[2023-01-27 10:30:32.944] [958] [debug] [iris_rtc_engine_impl.cc:132] ret 0 result {"result":0}
[2023-01-27 10:30:32.944] [958] [debug] [iris_rtc_engine_impl.cc:114] api name RtcEngine_startPreview2 params {"sourceType":0}
[2023-01-27 10:30:32.947] [958] [debug] [iris_rtc_engine_impl.cc:132] ret 0 result {"result":0}
2023-01-27 10:30:32.948552+0700 Runner[958:107484] dnssd_clientstub write_all(27) DEFUNCT
2023-01-27 10:30:32.948596+0700 Runner[958:107484] dnssd_clientstub deliver_request ERROR: write_all(27, 103 bytes) failed
2023-01-27 10:30:32.948677+0700 Runner[958:107484] dnssd_clientstub write_all(27) DEFUNCT
2023-01-27 10:30:33.285423+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:33.285689+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:33.348711+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:33.349042+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:33.410678+0700 Runner[958:106563] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:33.411271+0700 Runner[958:106563] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:33.477572+0700 Runner[958:107259] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:33.478837+0700 Runner[958:107259] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:33.541770+0700 Runner[958:106563] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:33.542051+0700 Runner[958:106563] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:33.612859+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:33.613740+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:33.679481+0700 Runner[958:106563] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:33.680567+0700 Runner[958:106563] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:33.749685+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:33.750276+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:33.814349+0700 Runner[958:106563] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:33.814873+0700 Runner[958:106563] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:33.881179+0700 Runner[958:107259] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:33.881798+0700 Runner[958:107259] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:33.944811+0700 Runner[958:106563] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:33.945075+0700 Runner[958:106563] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.014130+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.014855+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
[2023-01-27 10:30:34.070] [958] [debug] [iris_rtc_engine_impl.cc:112] api name RtcEngine_joinChannelWithUserAccount params {"channelId":"1c234190-8e94-11ed-801e-65027a9d3b82UcqqfMw0r9fUg3Imr72OwbG9X7C2","options":null,"token":"0060U9Nj","userAccount":"1c234190-8e94-11ed-801e-65027a9d3b82"}
2023-01-27 10:30:34.077913+0700 Runner[958:107259] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.078068+0700 Runner[958:107259] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
[2023-01-27 10:30:34.086] [958] [debug] [iris_rtc_engine_impl.cc:132] ret 0 result {"result":0}
2023-01-27 10:30:34.087064+0700 Runner[958:103859] flutter: Join channel success
2023-01-27 10:30:34.140622+0700 Runner[958:107259] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.140815+0700 Runner[958:107259] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.209784+0700 Runner[958:107259] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.209919+0700 Runner[958:107259] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.272918+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.273008+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.339668+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.339758+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.409765+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.409857+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
[2023-01-27 10:30:34.476] [958] [info] [rtc_engine_event_handler.cc:53] channel 1c234190-8e94-11ed-801e-65027a9d3b82UcqqfMw0r9fUg3Imr72OwbG9X7C2 uid<PHONE_NUMBER>
2023-01-27 10:30:34.477023+0700 Runner[958:103859] flutter: local user<PHONE_NUMBER> joined
2023-01-27 10:30:34.477289+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.477392+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
[2023-01-27 10:30:34.492] [958] [debug] [iris_rtc_engine_impl.cc:114] api name RtcEngine_setupLocalVideo params {"canvas":{"uid":0,"view":4450823456}}
[2023-01-27 10:30:34.493] [958] [debug] [iris_rtc_engine_impl.cc:132] ret 0 result {"result":0}
2023-01-27 10:30:34.542216+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.542311+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.608488+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.608633+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.678186+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.678327+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.746699+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.747185+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.813567+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.814157+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.880509+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.880991+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.947318+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:34.947782+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.013708+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.014180+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.080511+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.080963+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.146919+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.147379+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.214032+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.214547+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.279387+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.279995+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.346986+0700 Runner[958:107259] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.347399+0700 Runner[958:107259] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.414233+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.414750+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.477752+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.478033+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.544816+0700 Runner[958:107259] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.545113+0700 Runner[958:107259] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.613459+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.613926+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.680930+0700 Runner[958:107259] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.681275+0700 Runner[958:107259] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.745913+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.746274+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.813612+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.814059+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.868619+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.868848+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.934898+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:35.935299+0700 Runner[958:107262] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:36.001670+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:36.001935+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:36.069341+0700 Runner[958:107259] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:36.069537+0700 Runner[958:107259] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
[2023-01-27 10:30:36.124] [958] [debug] [iris_rtc_engine_impl.cc:114] api name RtcEngine_setupLocalVideo params {"canvas":{"uid":0,"view":0}}
[2023-01-27 10:30:36.125] [958] [debug] [iris_rtc_engine_impl.cc:132] ret 0 result {"result":0}
[2023-01-27 10:30:36.127] [958] [debug] [iris_rtc_engine_impl.cc:114] api name RtcEngine_leaveChannel params {"options":null}
2023-01-27 10:30:36.134324+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
2023-01-27 10:30:36.134470+0700 Runner[958:107260] Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatibility mapping behavior in the near future.
[2023-01-27 10:30:36.135] [958] [debug] [iris_rtc_engine_impl.cc:132] ret 0 result {"result":0}
[2023-01-27 10:30:36.135] [958] [info] [rtc_engine_event_handler.cc:1316] channel 1c234190-8e94-11ed-801e-65027a9d3b82UcqqfMw0r9fUg3Imr72OwbG9X7C2 uid<PHONE_NUMBER>
[2023-01-27 10:30:36.135] [958] [debug] [iris_rtc_engine_impl.cc:114] api name RtcEngine_unregisterEventHandler params {"event":10760404816}
[2023-01-27 10:30:36.135] [958] [debug] [iris_rtc_engine_impl.cc:132] ret 0 result {"result":0}
[2023-01-27 10:30:36.139] [958] [debug] [iris_rtc_engine_impl.cc:114] api name RtcEngine_release params {"sync":false}
[2023-01-27 10:30:36.139] [958] [debug] [iris_rtc_engine_impl.cc:233] IrisRtcEngineImpl __release
[2023-01-27 10:30:36.139] [958] [debug] [iris_rtc_device_manager_impl.cc:36] IrisRtcDeviceManagerImpl Release
[2023-01-27 10:30:36.139] [958] [debug] [iris_rtc_device_manager_wrapper.cc:791] IDeviceManagerWrapper Release
[2023-01-27 10:30:36.139] [958] [debug] [iris_rtc_media_player_impl.cc:43] IrisMediaPlayerImpl Release
[2023-01-27 10:30:36.139] [958] [debug] [iris_rtc_media_player_wrapper.cc:39] IMediaPlayerWrapper release
[2023-01-27 10:30:36.139] [958] [debug] [iris_rtc_spatial_audio_engine_impl.cc:214] IrisLocalSpatialAudioEngineImpl Release
[2023-01-27 10:30:36.139] [958] [debug] [iris_rtc_spatial_audio_engine_wrapper.cc:388] ILocalSpatialAudioEngineWrapper release
[2023-01-27 10:30:36.139] [958] [debug] [iris_rtc_media_recoder_impl.cc:26] IrisMediaRecoderImpl Release
[2023-01-27 10:30:36.139] [958] [debug] [iris_rtc_media_recoder_wrapper.cc:37] IMediaRecoderWrapper Release
[2023-01-27 10:30:36.139] [958] [debug] [iris_rtc_music_center_impl.cc:31] IrisMusicCenterImpl Release
[2023-01-27 10:30:36.139] [958] [debug] [iris_rtc_music_center_wrapper.cc:28] IrisMusicContentCenterWrapper release
[2023-01-27 10:30:36.139] [958] [debug] [iris_rtc_engine_wrapper.cc:8191] IRtcEngineWrapper release
[2023-01-27 10:30:36.266] [958] [debug] [iris_rtc_engine_impl.cc:132] ret 0 result {"result":0}
[2023-01-27 10:30:36.266] [958] [debug] [iris_rtc_engine_impl.cc:49] IrisRtcEngineImpl Destroy
[2023-01-27 10:30:36.266] [958] [debug] [iris_rtc_music_center_impl.cc:21] IrisMusiImpl Destroy
[2023-01-27 10:30:36.266] [958] [debug] [iris_rtc_media_recoder_impl.cc:15] IrisMediaRecoderImpl Destroy
[2023-01-27 10:30:36.266] [958] [debug] [iris_rtc_spatial_audio_engine_impl.cc:203] IrisLocalSpatialAudioEngineImpl Destroy
[2023-01-27 10:30:36.266] [958] [debug] [iris_rtc_media_player_impl.cc:28] IrisMediaPlayerImpl Destroy
[2023-01-27 10:30:36.266] [958] [debug] [iris_rtc_device_manager_impl.cc:25] IrisRtcDeviceManagerImpl Destroy
2023-01-27 10:30:43.879965+0700 Runner[958:103559] No windows have a root view controller, cannot save application state
2023-01-27 10:30:43.880453+0700 Runner[958:103559] [SceneConfiguration] Info.plist contained no UIScene configuration dictionary (looking for configuration named "(no name)")
libc++abi: terminating with uncaught exception of type std::__1::bad_function_call: std::exception
terminating with uncaught exception of type std::__1::bad_function_call: std::exception
(lldb)

Duplicated https://github.com/AgoraIO-Extensions/Agora-Flutter-SDK/issues/868.

This fix has landed the main branch.

This fix has landed the main branch.

The problem was solved, Thank you.

@alsherby-foundation  When i tried to add your dependency
  agora_rtc_engine:     git:       url: git@github.com:AgoraIO-Extensions/Agora-Flutter-SDK.git       ref: main
Git error. Command: git clone --mirror git@github.com:AgoraIO-Extensions/Agora-Flutter-SDK.git /Users/neosoft/Downloads/flutter/.pub-cache/git/cache/Agora-Flutter-SDK-d4fc8d6467a577324d81f2142fa65f13c414eca4
stdout:
stderr: Cloning into bare repository '/Users/TEST/Downloads/flutter/.pub-cache/git/cache/Agora-Flutter-SDK-d4fc8d6467a577324d81f2142fa65f13c414eca4'...
Host key verification failed.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
exit code: 128

@alsherby-foundation When i tried to add your dependency
 agora_rtc_engine: git: url: git@github.com:AgoraIO-Extensions/Agora-Flutter-SDK.git ref: main
Git error. Command: git clone --mirror git@github.com:AgoraIO-Extensions/Agora-Flutter-SDK.git /Users/TEST/Downloads/flutter/.pub-cache/git/cache/Agora-Flutter-SDK-d4fc8d6467a577324d81f2142fa65f13c414eca4 stdout: stderr: Cloning into bare repository '/Users/TEST/Downloads/flutter/.pub-cache/git/cache/Agora-Flutter-SDK-d4fc8d6467a577324d81f2142fa65f13c414eca4'... Host key verification failed. fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists. exit code: 128

Please make sure your dependency look like this (don't forget the tab space)

I'm having the same issue with   agora_uikit: ^1.

1.1

We're also seeing this when using the Unity SDK (v4.1). Appears reliably.


Minor docs formatting - clean up whitespace

Minor clean up

Misc Whitespace fixes (prettier formatting) on docs - will merge in once CI runs.


Getting an error

Internal Server Error (500)
    Request Method:
    POST

    Request URL:
  http://<IP_ADDRESS>:8080/pdf/c3310e0f1022982599e1f765c3f0da10ef4f2c64/data

(ArgumentError) comparison of Float with nil failed

@SourcingMogul Can you send me an email with the PDF that's causing this problem? A link works best, but if that's not possible, send it to me directly, not via Github, since Github strips out attachments). If it's sensitive and you can't, I understand too, of course.

Here is the link:
https://www.usenix.org/system/files/tech-schedule/srecon15_attendeelist.pdf
On Fri, Mar 20, 2015 at 5:01 PM, Jeremy B. Merrill<EMAIL_ADDRESS>
wrote:

@SourcingMogul https://github.com/SourcingMogul Can you send me an
email with the PDF that's causing this problem? A link works best, but if
that's not possible, send it to me directly, not via Github, since Github
strips out attachments). If it's sensitive and you can't, I understand too,
of course.
—
Reply to this email directly or view it on GitHub
https://github.com/tabulapdf/tabula/issues/294#issuecomment-84198705.

@SourcingMogul Sadly, that link is behind some sort of paywall. Maybe you can host it elsewhere or email it to me directly, not via Github? (Github strips out PDF attachments.)

Closed for inactivity.


Enhance Hamburger Menu with Smooth Transition on Mobile Devices

I’ve noticed that the hamburger menu on mobile devices opens and closes abruptly, and its position is not ideal. I propose adding a smooth transition effect to enhance user experience and make navigation feel more polished. Please assign me this task. Thank you!

sure


Don't fmt unsafe blocks to span multiple lines.

Problem
A subjective one for you.
Say you have this code:
let a = my_unconstrained_fn();
And then the compiler warns you to wrap it in an unsafe block:
let a = unsafe {  my_unconstrained_fn() };
This is nice and still on one line.
But then the formatter spills it over 3 lines, and I can understand why, but I feel like it hurts readability when these unsafe blocks span lines when they don't need to.
let a = unsafe {
    my_unconstrained_fn()
};

As I've seen a lot of one line unsafe blocks. Feel free to reopen if you can provide a test case for the formatter which displays this behavior


fix titles add in Cloudly at the beginning

this doesn't look so good with the "Amazon" in the title does it?
http://cloudly.dracon.biz/aws/i-15349ef2/

done


failed to run custom build command for aws-lc-sys v0.21.2

Problem
error: failed to run custom build command for `aws-lc-sys v0.21.2`

Caused by:
  process didn't exit successfully: `C:\Users\me\AppData\Local\Temp\cargo-installZPq3k0\release\build\aws-lc-sys-a9c626b05d91a93d\build-script-main` (exit code: 101)
  --- stdout
  cargo:rerun-if-env-changed=AWS_LC_SYS_NO_PREFIX
  cargo:rerun-if-env-changed=AWS_LC_SYS_INTERNAL_BINDGEN
  cargo:rerun-if-env-changed=AWS_LC_SYS_EXTERNAL_BINDGEN
  cargo:rerun-if-env-changed=AWS_LC_SYS_NO_ASM
  cargo:rerun-if-env-changed=AWS_LC_SYS_CFLAGS
  cargo:rerun-if-env-changed=AWS_LC_SYS_PREBUILT_NASM
  cargo:rerun-if-env-changed=AWS_LC_SYS_C_STD
  cargo:rustc-cfg=x86_64_pc_windows_msvc
  cargo:rerun-if-env-changed=AWS_LC_SYS_CMAKE_BUILDER
  cargo:rerun-if-env-changed=AWS_LC_SYS_STATIC
  default_for Target: 'x86_64-pc-windows-msvc'
  cargo:rerun-if-env-changed=AWS_LC_SYS_STATIC
  cargo:rerun-if-env-changed=CMAKE

  --- stderr
  Missing dependency: cmake
  thread 'main' panicked at C:\Users\me\.cargo\registry\src\index.crates.io-6f17d22bba15001f\aws-lc-sys-0.21.2\builder/main.rs:315:40:
  called `Result::unwrap()` on an `Err` value: "Required build dependency is missing. Halting build."
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: failed to compile `dioxus-cli v0.6.0-alpha.2`, intermediate artifacts can be found at `C:\Users\me\AppData\Local\Temp\cargo-installZPq3k0`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.

Steps To Reproduce
Steps to reproduce the behavior:

Windows 11 without cmake and nasm
cargo install dioxus-cli --version "0.6.0-alpha.2"

Expected behavior

Screenshots

Environment:

Dioxus version: 0.6.0-alpha.2
Rust version:    1.81.0
OS info:         Windows 11
App platform:

Questionnaire

[ ] I'm interested in fixing this myself but don't know where to start
[ ] I would like to fix and I have a solution
[ ] I don't have time to fix this right now, but maybe later

related: #2666

Netwide Assembler (NASM) must be installed for win11
https://www.nasm.us/pub/nasm/releasebuilds/2.16.03/win64/
Inside its shell install cli
https://github.com/DioxusGrow/dioxus_translator?tab=readme-ov-file#quick-start

Is the team decided to add environmental dependency?
If so, they would have to update this page... https://dioxuslabs.com/learn/0.5/getting_started

hmm, I understood. this issue should be closed at the same time the docs is updated.

I have installed NASM, but when I execute cargo install dioxus-cli, I still get the above error, and the system is also Windows 11, has this problem been solved?

maybe you are missing cmake command in you path.  you can execute
scoop install cmake

to install cmake on windows or some similar commod deps on your operation system


Capitalizes "GitHub" on getting-started-roslyn-analyzers

looked for an existing issue but couldn't find one. per contributing guidelines, not opening an issue given the change is so small

@helizabethwhite : Thanks for your contribution! The author, @gregvanl, has been notified to review your proposed change.

Merging typo fix
@helizabethwhite Thank you.


[Feature Request]

🚀 Feature
Is it possible to allow users to custom-edit the configuration file of the model? Because the current iPad already has 16G of memory now, and I want to try whether a larger model can run.
Want to try whether some 8B models can run?

This problem can be achieved by rebuilding the SDK  with a different larger model. We recommend start enabling these models on python, then change https://github.com/mlc-ai/mlc-llm/blob/main/ios/MLCChat/mlc-package-config.json to include these models


Update user stories in Developer Guide

add more stories

Coverage remained the same at 92.159% when pulling d74805960b2ecaf5335e3ac4fde55ec45a72d27a on khooroko:Update_User_Stories into 0b1134e3eb34a7859bfb58eed7a2d75a54069d14 on CS2103AUG2017-T17-B1:master.

Coverage remained the same at 92.159% when pulling 25579d9caad5bf5afa60e6e6427b11817c0e5150 on khooroko:Update_User_Stories into 0b1134e3eb34a7859bfb58eed7a2d75a54069d14 on CS2103AUG2017-T17-B1:master.


Feature/workflow add source control to path

Workflows now have source control (ex. github.com/) in the path. Also has a migration script to add the new source control information existing database.

I tested the migration locally on the staging database and it seems to be working.

Coverage increased (+0.2%) to 71.279% when pulling 5c6b0c73187c10f2253c34d11b0b1f30821cc0cf on feature/workflow-add-source-countrol-to-path into 6d32c7e370a553c5e08c54628c89b8952ad2bf6d on develop.

Coverage increased (+0.009%) to 71.111% when pulling 805c93c114a1d3df47cd714e8447ad8669acd0fa on feature/workflow-add-source-countrol-to-path into 6d32c7e370a553c5e08c54628c89b8952ad2bf6d on develop.

This is passing now if people want to take another look at it.


XenServer Machinery

This merge request implements the XenServer machinery. The machinery communicates to a XenServer instance through the XenAPI library, which uses an HTTP(S) XML RPC interface. The machinery supports the following functions:

Starting and stopping VMs: start() and stop()
Checking the power state of a VM: _status()
Listing available VMs: list()
Reverting a VM to a previous state

The XenServer machinery supports two methods of VM restoration:

Memory and disk snapshots
Disk resetting on boot

Memory and disk snapshots require that the VM has the Xen guest tools installed, which may not be possible in some environments. Therefore, the machinery also supports launching VMs that have their disks reset on boot, which is configured on a per VM basis in the XenServer instance.
The documentation has also been updated to include XenServer related configuration and usage.

Great work! specially since newer versions of esxi (free) don't have API.

It looks good to me, but it would be good to have some proper testing. For significant contributions, please also remember to check out this http://cuckoofoundation.org/contribute.

Signing the agreement shouldn't be problem. I'll take a look at it tomorrow.
As far as testing, I tested the machinery against a XenServer instance that I already had running with multiple VMs and different configurations. Beyond that, are you looking for anything formal?

No, not formal, but it's generally good to have feedback from other users so that they can verify the setup and configuration procedures as well as perhaps reveal issues that only different installations might raise.

ameily:
I spun this up on my i7 box. Here's my notes:
o The documentation doesn't mention installing xenapi. Gave me an error - 'pip install xenapi' fixed it
o The configuration section was confusing. I entered machine=xen and wondered why it was failing (machine=xenserver for those wondering)
o When choosing to use VM disk resetting (Boot from disk section), it should mention that the VM must be shut down before executing the commands on XenServer
o Maybe it was the machine I had running XenServer, but suspending, resuming, restarting, and ejecting disks from the vm through XenCenter was sluggish (~1 minute for each command)
o There were times when the cuckoo job would hang and cuckoo.py had to be restarted to resume. Probably a cuckoo thing and not a Xen thing

Thanks for the feedback @wealthychef! I've clarified spots of my documentation that you pointed out. Specifically, I modifed the Installation Preparing the Host -> Requirements and Preparing the Guest -> Saving the Virtual Machine -> Booting from Disk sections. Could you please review it and make sure it good to go?
Also, I'd like to confirm that the hanging issue you are seeing is not the XenServer machinery. I tested the machinery locally again and found that the XenAPI is not thread safe. I've fixed this limitation with my recent commits. My guess is that you were either seeing this issue or you did not specify a runtime timeout for the samples. Can you please retest and verify that the issue is not with the XenServer machinery?

I checked out the documentation and it looks like the ambiguities were addressed. I also re-ran my previous tests to attempt to get cuckoo to 'hang', but it ran smoothly through everything I threw at it. Thanks for the quick response!

Unless @jekil has some issues with it, I'm ok for merging.

@botherder ok for me

@ameily thanks a lot for this contribution, it is really high-quality code.

Hi. Now I am using Ubuntu with Xen hypervisor. Could I use the XenServer machinery? Or how could II modify it? The xen hypervisor does not have a XenServer URL.

The stock Xen hypervisor is not compatible with the XenServer machinery. However, you should be able to use the libvirt machinery.

Thank you! Just to be sure, I should modify the machinery=xen in the cuckoo.conf, right?


Inclusion of AB13HD method for L-infinity norm computation of Descriptor Systems

The function AB13HD (available, e.g., here) written by @VasileSima4  and Matthias Voigt is currently not included in this repository.
However, AB13HD is needed for computing the L-infinity norm, when the E matrix (in an EABCD-system) is singular. The function AB13DD, that is currently available, assumes that E is nonsingular.
Is it possible to include AB13HD into the SLICOT-Reference repository? In this way it would also be automatically available e.g. to julia users via SLICOT_jll.
Can we just open a pull-request with the code from this link or is further testing/documentation needed?

I will do some further testing of AB13HD in the next few weeks, and then add it to the SLICOT-Reference repository.
Vasile Sima


Updated script for direct deployment

Added a socket file. The gunicorn server will listen at both the given port and the socket file.

@manu-chroma I trust that what you've done here is good, however please keep on eye on the build server to make sure that it builds the way you want.

Looking good, Manvendra :sunglasses:
https://travis-ci.org/cltk/cltk_api/builds/117078226

@kylepjohnson Haha. When I made this PR, the travis CI had been enabled on this repo but the .travis file hadn't been added to the repo. That was the reason why the build was failing.


Manual Integration with "Define Manually" increases peak areas massively

Basic information

My operating system: Windows 10 Enterprise

My MZmine version: 3.2.8 Portable

Edit: I now also tested on the non-portable version and with mzML files (converted with MSConvert), same problem in both cases

What happened
Hello,
the issue i am experiencing is with the manual integration of a feature in a specific dataset with the "define manually" function in an aligned feature list.
After manual integration the peak areas increase by magnitudes (e.g. from 9.6E3 to 7.0E7). They do this even if i don´t set new integration borders but just open up the dialogue and click ok leaving everything as it is.
Neither before or after manual integration the peak areas match with the areas reported in the vendor´s software (Thermo Freestyle), which wouldn´t be too bad. However, usually in the large dataset i am trying to integrate, there is always a few features that need manual integration and then are not comparable to the automatically integrated features anymore.
The height value doesn´t seem to be affected by this and matches with the values in the vendor´s software.
My workflow is

import Thermo RAW data (centroid, negative ion mode)
Mass Detection (Centroid, noise level: 3E3)
GridMass (MinHeight: 4.9E3, m/z tol: 0.08, min-max width time: 0.1-1.1min, smoothing time 0.05, smoothing m/z: 0.05, false+ int sim ratio: 0.4, false+ ignore times 0-0)
Align (m/z tol: 0.08 or 200ppm (weight 80), RT tol: 0.11 (weight 20))
Feature List Blank Substraction (at least in 3/6 blanks, 150% for exception)
Peak Finder (Int.Tol: 40%, m/z tol: 0.08, RT tol: 0.1, min data pts: 1)

However, the problem of areas increasing massively when integrating manually already occurs after GridMass if done on a single file´s feature.
The MZmine file as well as the log can be found here (they are too big for github):
https://uppsalauniversitet-my.sharepoint.com/:f:/g/personal/stefan-lukas_ruchti_7587_student_uu_se/Eo_XR0ribiFKo8Sqpe4IuTMBKj49noFg_K_Niv5VSz_dsg?e=K9afOS

Sorry for the late reply.
This issue should be fixed in the latest dev build already. You can try it here: https://github.com/mzmine/mzmine3/releases/tag/Development-release

Hey, thank you so much for getting back to me.
I deinstalled the old mzmine and downloaded both the portable and the non-portable version of the dev build.
I tried to recreate the problem described above but this time i run into an error earlier on. When i try to move the Integration-Start-Line or the Integration-End-Line there is an Error message poping up (see attached screenshot). This happens in both versions and doesn't allow me to integrate manually. The values for areas won't change even if i ignore the error messages and continue to click "ok".
It also already occurs on the feature lists i get after GridMass.
Do you have an idea on how to get around this?
All the Best and thanks again
Stefan
mzmine_0_0.log

Hi Stefan,
i cant reproduce that with my own files. Does the project yu uploaded produce the issue? If yes for which feature in which feature list?

Hey Steffen,
i wasn't using the uploaded files when writing my last post but when retrying with the uploaded files, i noticed what provoked the error.
I was trying to make the integration window wider when i got the error message and i am quite sure now that it gave me the error because the new limit for integration was at a point where the intensity was lower than the one defined by GridMass. When i try to make the window smaller it always works and when i adjust the GridMass intensity to a lower value i can also go in both direction (make integration range bigger and smaller)
Thank you so much for your help. I think this is solved :)
Best
Stefan


Extraneous  symbol from Salsa

Testing #12598

This issue was moved to Microsoft/TypeScript#11230

@dbaeumer what do you think about filtering this out? Per @mhegazy's comments.

@waderyan: we can do this. However I want to understand why this is in in the first place since we ask for symbols for a specific document.

Tried a work around on our end but there is more broken. See https://github.com/Microsoft/TypeScript/issues/11230#issuecomment-250429110

Fixed it for 1.7.


Live Share duplicates my existing MS account with a long email alias

Steps to Reproduce:

Log into Settings Sync with Microsoft account
Login into Live Share with Microsoft account

Expected: Live Share uses existing email account.
Actual: Live Share adds a new account entry using my long email alias (firstname.lastname@…).

This is likely because the LiveShare extension doesn't provide the profile scope... but I'm wondering what other options there are in your JWT claims... maybe we can have a better fallback ordering here:
https://github.com/microsoft/vscode/blob/f8b17200c1318f0b58090445cc1a6338da426e4e/extensions/microsoft-authentication/src/AADHelper.ts#L572

This should be fixed now because we force having the profile scope.


Random Featured Project

Created function to retrieve random project index and replaced hardcoded project with random.

@reginawang3495 I think we may have merged in a bug with this PR; see this version of the prod homepage, with the incorrect image for the project

Oh shoot, I’ll fix that rn


pull request for e2e test at 11/12/2016 10:15:09

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

Details

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


(Bug report) Incorrect thermalization using IME relaxation with zeeman-liouv basis

First of all, thank you for developing Spinach, it has been a great tool for me to learn about spin dynamics.
While I was using your software, I think I might have found a minor mistake in the way the unit_state is calculated for the 'zeeman-liouv' basis.
The problem arose when using relaxation.m which calls thermalize.m to get the relaxation superoperator. I was using the 'IME' relaxation type as shown on image 1 and 2.

The problem is that after applying the IME correction the relaxation superoperator does not yield zero when applied to the thermal equilibrium, which as far as I understand it should. This can be seen on image 3.

I believe the root of the problem is that a normalization is applied to the unit_state, which should be omitted (see image 4).

When I do the calculation without this last part, the result is much closer to zero, as seen on image 5.

Of course, I do not know if this is just some mistake I made, but I thought you might want to know about the issue, in case it is something that should be fixed.
Best regards, Filip Vestergaard Jensen

Thanks - investigating...

OK, I agree that that particular unit state inside thermalize() should be normalised differently. It cannot be done globally inside unit_state() though because all sorts of observables would then become thermodynamically inconsistent between formalisms, not to mention the fact that the norm of the unit state would depend on the presence of observer spins... thinking about the best way to proceed.

OK, check the latest commit - should be solved now. I made the thermaliser formalism-specific and also fixed a related bug (see relaxation.m changes) wherein the relaxation superoperator starts damping the unit state in zeeman-liouv formalism in certain circumstances.

Makes sense, thank you very much.
Best regards, Filip


Missing C library: kernel32

$ ./Setup configure
Configuring ansi-terminal-<IP_ADDRESS>...
Setup.exe: Missing dependency on a foreign library:

Missing C library: kernel32
This problem can usually be solved by installing the system package that
provides this library (you may need the "-dev" version). If the library is
already installed but in a non-standard location then you can use the flags
--extra-include-dirs= and --extra-lib-dirs= to specify where it is.

I found that if I remove the "extra-libraries: kernel32" line, the package does configure OK. Is kernel32 not guaranteed to be available on all Windows machines? It seems redundant to mention it in the .cabal file, if it is always present, and actively harmful to mention it if it causes setup to fail.

I don't know much about Windows. If the consensus of Windows developers is that the dependency should be removed, I'm happy to accept a pull request.


keep aspect-ratio of view

I might just not see it, but is there any way to implement a dynamically sized view that keeps its aspect-ratio?
Best Regards

I don't see why not - can you give an example? You provide the width and height of the view in many cases, so if you do your own calculations with that aspect-ratio and feed in the correct sizes, it should just work.


Two licenses of piptools

piptools has:

https://github.com/pypa/pipenv/blob/master/pipenv/patched/piptools/LICENSE (BSD)
https://github.com/pypa/pipenv/blob/master/pipenv/patched/piptools/LICENSE.txt (MIT)

Upstream only has https://github.com/jazzband/pip-tools/blob/master/LICENSE (BSD).

Thanks for the heads up. I think one of these is a pip license from when they had pip vendored. Will have to check when it first got added but I’m guessing it was some failure in the vendoring toolchain that renamed it to this in the parent folder. I’ve been out of town for a family emergency but will look into this before we cut another release — should be in the next few days (8.1 if we stay consistent)


x/net/ipv4: all cmsg tests fail on FreeBSD 12 kernel running COMPAT_FREEBSD32

See https://build.golang.org/log/5fff7e020d3329af198bcae137b22c124a7a7f31
:: Running /tmp/workdir/go/bin/go with args ["/tmp/workdir/go/bin/go" "test" "-short" "golang.org/x/net/..."] and env ["PATH=/tmp/workdir/go/bin:/bin:/sbin:/usr/bin:/usr/local/bin" "PWD=/" "HOME=/" "RC_PID=24" "WORKDIR=/tmp/workdir" "GOROOT_BOOTSTRAP=/tmp/workdir/go1.4" "GO_BUILDER_NAME=freebsd-386-12_0" "GOARCH=386" "GOHOSTARCH=386" "GOROOT=/tmp/workdir/go" "GOPATH=/tmp/workdir/gopath" "GOPROXY=http://<IP_ADDRESS>:30156" "TMPDIR=/tmp/workdir/tmp" "GOCACHE=/tmp/workdir/gocache"] in dir /tmp/workdir/gopath/src/golang.org/x/net
--- FAIL: TestPacketConnReadWriteMulticastUDP (0.00s)
    multicast_test.go:102: read udp <IP_ADDRESS>:27889: short buffer
--- FAIL: TestPacketConnReadWriteMulticastICMP (0.00s)
    multicast_test.go:204: read ip <IP_ADDRESS>: short buffer
--- FAIL: TestPacketConnConcurrentReadWriteUnicastUDP (0.00s)
    readwrite_test.go:250: read udp <IP_ADDRESS>:22658: short buffer
    readwrite_test.go:250: read udp <IP_ADDRESS>:22658: short buffer
    readwrite_test.go:250: read udp <IP_ADDRESS>:22658: short buffer
--- FAIL: TestPacketConnConcurrentReadWriteUnicast (0.01s)
    --- FAIL: TestPacketConnConcurrentReadWriteUnicast/UDP (0.00s)
        --- FAIL: TestPacketConnConcurrentReadWriteUnicast/UDP/ToFrom (0.00s)
            readwrite_test.go:377: read udp <IP_ADDRESS>:60170: short buffer
            readwrite_test.go:377: read udp <IP_ADDRESS>:60170: short buffer
            readwrite_test.go:377: read udp <IP_ADDRESS>:60170: short buffer
            readwrite_test.go:377: read udp <IP_ADDRESS>:60170: short buffer
            readwrite_test.go:377: read udp <IP_ADDRESS>:60170: short buffer
            readwrite_test.go:377: read udp <IP_ADDRESS>:60170: short buffer
            readwrite_test.go:377: read udp <IP_ADDRESS>:60170: short buffer
            readwrite_test.go:377: read udp <IP_ADDRESS>:60170: short buffer
            readwrite_test.go:377: read udp <IP_ADDRESS>:60170: short buffer
        --- FAIL: TestPacketConnConcurrentReadWriteUnicast/UDP/Batch (0.00s)
            readwrite_test.go:409: short buffer
            readwrite_test.go:409: short buffer
            readwrite_test.go:409: short buffer
            readwrite_test.go:409: short buffer
            readwrite_test.go:409: short buffer
            readwrite_test.go:409: short buffer
            readwrite_test.go:409: short buffer
            readwrite_test.go:409: short buffer
    --- FAIL: TestPacketConnConcurrentReadWriteUnicast/IP (0.00s)
        --- FAIL: TestPacketConnConcurrentReadWriteUnicast/IP/ToFrom (0.00s)
            readwrite_test.go:377: read ip <IP_ADDRESS>: short buffer
            readwrite_test.go:377: read ip <IP_ADDRESS>: short buffer
        --- FAIL: TestPacketConnConcurrentReadWriteUnicast/IP/Batch (0.00s)
            readwrite_test.go:409: short buffer
            readwrite_test.go:409: short buffer
            readwrite_test.go:409: short buffer
            readwrite_test.go:409: short buffer
            readwrite_test.go:409: short buffer
            readwrite_test.go:409: short buffer
            readwrite_test.go:409: short buffer
            readwrite_test.go:409: short buffer
            readwrite_test.go:409: short buffer
--- FAIL: TestPacketConnReadWriteUnicastUDP (0.00s)
    unicast_test.go:65: read udp <IP_ADDRESS>:21928: short buffer
--- FAIL: TestPacketConnReadWriteUnicastICMP (0.00s)
    unicast_test.go:141: read ip <IP_ADDRESS>: short buffer
--- FAIL: TestRawConnReadWriteUnicastICMP (0.00s)
    unicast_test.go:232: read ip <IP_ADDRESS>: short buffer
FAIL
FAIL	golang.org/x/net/ipv4	0.018s

Reopen: at least the fix needs to identify the running kernel version.


Upgrade GBIF dependencies

With significant work on Pipelines, the Registry etc, the IPT is now using fairly old versions of GBIF API, DWC API, GBIF Common etc.
Upgrade these to current versions.

See #1533 for an upgrade of dwca-io.

Solving #1346 first might help remove some of the old dependencies.

Motherpom should be updated too


refactor: workflow cleanup

This PR closes #91 .
The changes in this PR are:

Change all "premir" by "primir" (in rules, output files, scripts and test files)
Change rule names to make them more meaningful
Update expected output as some output file names have changed.
Update cluster.json to match rule names and remove unused configuration.

In this push, some extra changes have been add:

log files now match the rule name
Output file names are build to be found together (i.e all the alignments start by alignments, all segemehl outputs start by segemehl, so on and so forth).
All 4 snakefiles have been lint with snakefmt -l 80
The {sample} wildcard has been removed from some output files as they will already be stored in the sample directory.

As a suggestion, some script names should be changed by the same reason as this comment was made.
As a detail, rule headers could also be modified (some of them) to be more specific.


Required updates are very unclear

Near the top of the page it says:

A ClickOnce application periodically reads its deployment manifest file to see whether updates to the application are available. If available, the new version of the application is downloaded and run.

But further down:

Make updates required
There may be occasions when you want to require users to run an updated version of your application [...] In this case, you would want to mark your update as required and prevent users from running the earlier version.

Well, that sounds like what happens anyway, according to the first section. What is a non-required update, when the first section makes it sound like new versions are always downloaded and run, at least if the application has recently checked for the presence of new versions?
I think the missing link here (discovered by experimentation) is that if you don't make updates required, the user is presented with a choice about upgrading:

I think this page needs rephrasing. Add something about the user by default being given a choice whether to upgrade -- unless the update is marked as required.

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

ID: 2af9ac7e-1011-df44-6232-89136459646e
Version Independent ID: c2dcd806-769a-87a9-8228-15bf5398ad6c
Content: Choosing a ClickOnce Update Strategy - Visual Studio (Windows)
Content Source: docs/deployment/choosing-a-clickonce-update-strategy.md
Product: visual-studio-windows
Technology: vs-ide-deployment
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

Updating doc. Fix should be live by EOD today, 1/27/23


add back RL

What does this PR do?
Adding back RL
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

later this will be merged without squash eventually in the command line to keep the contributions...

Hello @Borda! Thanks for updating this PR.

In the file pl_bolts/models/rl/common/cli.py:

Line 30:121: E501 line too long (121 > 120 characters)

In the file tests/datamodules/test_experience_sources.py:

Line 313:30: W504 line break after binary operator
Line 314:52: W504 line break after binary operator


Unexpected token for when using new .vue files

Hello,
Currently trying use a single-file Vue component for one of my views, but I get some errors when Browserify gets to work.
It's blank right now...
<template>

Home

Profiles

Lorem ipsum dolor sit amet, consectetur adipisicing elit. Natus tempore excepturi ipsa dolore provident hic delectus maxime officia fuga culpa, praesentium ullam sapiente deleniti veniam quam doloremque ut vel aliquam?

</template>

This gives me the following error...
Browserify Failed!: Unexpected token

/resources/assets/js/views/ProfilesView.vue:1
<template>
^
ParseError: Unexpected token

After looking at your Hacker News example (https://github.com/vuejs/vue-hackernews), I do think I have everything spelt correctly so can't see why it's throwing this error?
Any ideas?

You need to use correct build setup - for browserify you need vueify.

Thanks @yyx990803, must have overlooked that somewhere in the docs.

Using vueify and still experiencing this issue:  http://stackoverflow.com/questions/39667838/third-party-vue-component-throwing-unexpected-token-error-when-importing


Add rememberBreakpoint to Silk

This could be used to toggle code with logic, as an additional path besides component styling.
val breakpoint = rememberBreakpoint()
if (breakpoint >= Breakpoint.MD) {
   ... show this only on desktop ...
}

So this could be tricky - it doesn't seem like there's a good way to compare sizes of different units.
In other words, I can easily get the "px" value of the current window, but I have no idea if users defined their breakpoints as "px", "em", "rem", or some other relevant user size.
It could be easier to force breakpoints to always be "px" values but looking at this for example: https://chakra-ui.com/docs/features/responsive-styles it seems like using font-size related sizes may not be uncommon?

Here's an interesting article on the topic: https://medium.com/zoosk-engineering/to-em-or-not-to-em-that-is-the-media-query-question-22f4a65e9747
Feels like breakpoints should either be px OR em. Maybe I can force breakpoints to be one or the other behind the scenes, or a sealed class to limit to only those two types, which may allow this feature to work (assuming I can at least convert between em and px in javascript)

Looking ugly...
https://stackoverflow.com/questions/10463518/converting-em-to-px-in-javascript-and-getting-default-font-size

Maybe this, which lets you convert from px to em in code:
https://stackoverflow.com/a/12241338/17966710

OK, got this to work...

Restricted breakpoint values to "px", "em", and "rem" units (for now)
Ensured we can convert all breakpoint units to "px"
Used "window.getComputedStyle(document.body).getValueProperty("font-size") for "em" and "rem" values

Hopefully this is not fragile, I guess we'll see

Added a windows resize event listener which takes advantage of these new constraints to produce breakpoint state


Does Rester support HTTP Basic Auth?

Hello, great library by the looks of it.
I read that formal authentication system is not yet supported. My API uses HTTP Basic Auth, which is essentially a header in the request. This is supported by Rester, right?

So sorry for such a late response. Yes, you could add a header to the rest call -
"headers":{
"content-type":"application/json;"
}


Do you have some example of implementation?

Hi again,
I'm stuck with the integration when I need to run flask and webpack etc.
Can't see were to start..
I saw in your livetv mining project that you got separate frontend/backend, is it easier?

Hi @askz,
Sorry for replying you so late. (I‘m on vacation)
In my opinion, both ways (split frontend/server or not) have specific difficulties. The case you choose  depends on the product environment. For my project livetv_mining, it deploys on AWS Free Tier server and free server performance is poor. So I had to use split case(and other subplan) to save CPU work time.
In real life, many internet companies choose the popular solution: RESTAPI ＋ iOS ＋ Android ＋ Web and more traditional companies choose integration all on server.
So my suggestion is that: If you are a beginner about Flask, you can start from tutorial: flasky (py3 version). If you have use experience about Flask, you can learn how to split frontend/server immediately. The examples I refer to are vue-hackernews-2.0 webpack2.0, vuejs-templates webpack1.0 and webpack official document.
Would it help you to smooth learning curve ?

Thank you.
I was really wondering why you did that package (flask-vue) and on the other having a vue project with splitted front/back.
I will definitely check the split solution !
Cheers!

Simple put, I had a flask/vue project which should be deployed inner & outer net in the meantime.
When you visit website in outer net, the best way to save net flow is using CDN for scripts resource. When you visit website in inner net, the visitor can not get resource stored outer network. At the same time, the developers need to deploy project easy and configurable.
So I package the flask-vue and it can config project to use CDN or Local files.


[enhancement] can we support the following functions?

Hello, Can we add support for the following functions? I use them for C/C++ on vscode. It will be pretty handy for me if they are available in Lua also.

SpaceBeforeFunctionOpenParenthesis
SpaceBeforeOpenSquareBracket
SpaceBeforeLambdaOpenParenthesis
SpaceWithinExpression

SpaceBeforeFunctionOpenParenthesis
Before Formatting:
function ff()
end

After Formatting:
function ff ()
end

SpaceBeforeOpenSquareBracket
Before Formatting:
details["names"] = "ashok"

After Formatting:
details ["names"] = "ashok"

SpaceBeforeLambdaOpenParenthesis
Before Formatting:
local details ={}

After Formatting:
local details = {}

SpaceWithinExpression
Before Formatting:
i?"true":"false";
i>0

After Formatting:
i ? "true" : "false";
i > 0

Thank You,
ashok.

If you want these features implemented, you can demonstrate how each option is formatted

sure, give me some time I will get back on this.

I updated the desired formatting in the description of the issue.

SpaceBeforeLambdaOpenParenthesis and SpaceWithinExpression is default action

only SpaceBeforeFunctionOpenParenthesis and SpaceBeforeOpenSquareBracket need support

option SpaceBeforeFunctionOpenParenthesis for lua, it is divided into function definition, function call, lambda definition.
should I divide into three options?

option SpaceBeforeFunctionOpenParenthesis for lua, it is divided into function definition, function call, lambda definition. should I divide into three options?

funtion call and defination need not be differentiated IMO.

feature has been completed
following option can use.
space_before_function_open_parenthesis = true
space_before_open_square_bracket = true
wait sumneko next update and release

:+1:

yes

:+1:
I tried to use it in vain :( and here is how I set them up after I upgraded the version to 3.5.0. I also tried to refer to the documentaion but didnt find a mention of these two params there.

can you pls guide me on this configuration?

it work,if use .editorconfig.

maybe, in vscode setting, you can set "true" instead of true

this can be a misunderstanding. I will try to fix that

It's my mistake, when set default config, you need restart vscode.

if use .editorconfig. it can work?

I use your settings:

if use .editorconfig. it can work?

how do I use this? is it any difference from the settings that I am already using. Copy pasting them below for reference.
    "Lua.format.defaultConfig": {
        "align_call_args": "true",
        "space_before_function_open_parenthesis": "true",
        "space_before_open_square_bracket": "true"
    },
    "[lua]": {
        "editor.defaultFormatter": "sumneko.lua"
    },

see https://github.com/sumneko/lua-language-server/wiki/Code-Formatter

Is there any progress?

Doesnt work :( , Here is the full .editorconfig for your reference. FYI I am trying to format by using the format selection key.  Sorry for the delay, I was not feeling well this week.
root = true

[*]
indent_style = space
indent_size = 2
charset = utf-8
trim_trailing_whitespace = true
insert_final_newline = true

[Makefile]
indent_style = tab
indent_size = 8

[*.py]
indent_style = space
indent_size = 4

"Lua.format.defaultConfig": {
    "align_call_args": "true",
    "space_before_function_open_parenthesis": "true",
    "space_before_open_square_bracket": "true"
},
"[lua]": {
    "editor.defaultFormatter": "sumneko.lua"
},

you can try my plugin https://marketplace.visualstudio.com/items?itemName=CppCXY.emmylua-codestyle
the .editorconfig copy from https://github.com/CppCXY/EmmyLuaCodeStyle/blob/master/lua.template.editorconfig

you can try my plugin https://marketplace.visualstudio.com/items?itemName=CppCXY.emmylua-codestyle the .editorconfig copy from https://github.com/CppCXY/EmmyLuaCodeStyle/blob/master/lua.template.editorconfig

works good :+1: the formatting is also auto applied on a return key, just what I was looking for. Thank you very much. Its been pleasure working with you.

About space_before_function_open_parenthesis: would love to see this setting applied not only to round but to curly brackets as well. So foo {} is formatted to foo{} when this setting is false. By default, there is always a space between function name and curly brackets.

About space_before_function_open_parenthesis: would love to see this setting applied not only to round but to curly brackets as well. So foo {} is formatted to foo{} when this setting is false. By default, there is always a space between function name and curly brackets.

new issue please


Add ledis cache support

This PR adds a new cache provider ledis which have been implemented in go-chi/cache but not supported.
For those Gitea instances which have lower memory but want to cache last commit information, it's a better case than memory or redis.

Codecov Report

Merging #16035 (2b5b5b6) into main (256b1a3) will increase coverage by 0.01%.
The diff coverage is 60.00%.

@@            Coverage Diff             @@
##             main   #16035      +/-   ##
==========================================
+ Coverage   44.08%   44.09%   +0.01%
==========================================
  Files         682      682
  Lines       82384    82424      +40
==========================================
+ Hits        36316    36346      +30
- Misses      40157    40165       +8
- Partials     5911     5913       +2

Impacted Files
Coverage Δ

modules/setting/cache.go
44.44% <33.33%> (-2.44%)
:arrow_down:

modules/cache/cache.go
38.55% <100.00%> (ø)

modules/queue/queue_channel.go
95.00% <0.00%> (-1.67%)
:arrow_down:

modules/task/task.go
60.29% <0.00%> (-1.53%)
:arrow_down:

modules/queue/workerpool.go
53.81% <0.00%> (-1.15%)
:arrow_down:

modules/queue/unique_queue_disk_channel.go
48.63% <0.00%> (+1.36%)
:arrow_up:

modules/log/file.go
75.39% <0.00%> (+1.58%)
:arrow_up:

modules/git/command.go
89.81% <0.00%> (+1.85%)
:arrow_up:

models/task.go
39.06% <0.00%> (+3.82%)
:arrow_up:

modules/charset/charset.go
75.75% <0.00%> (+4.04%)
:arrow_up:

... and 1 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 256b1a3...2b5b5b6. Read the comment docs.

What is ledis? Some kind of redis fork?

I am slightly concerned that this is adding another different level dB to the system.
It would not be difficult to add a leveldb caching provider using our current leveldb by looking at this code nor should it be difficult to switch our leveldb provider over to the rdb that is in here but we shouldn't have two leveldbs.
Interestingly in the dependencies for this rdb is a mmap implementation - which (if we were happy to add - I think this is a cgo dependency) could be used in go-git for its commit-graph reader and some other places in gitea.

What is ledis? Some kind of redis fork?
It's a pure golang k/v database which have a redis similiar interface but stored all data into disk. It's based on go leveldb.

@zeripath The cache interface requires Incr and something other feature which needs some work based on leveldb. I don't think we need to create a new one since go-chi/cache have implemented that.

I've just understood the reasoning behind this.
Is it really the case that the memory cache just grows without limit? That's kinda crazy.
Is there any limit on this cache?

I've just understood the reasoning behind this.
Is it really the case that the memory cache just grows without limit? That's kinda crazy.
Is there any limit on this cache?

If the cache haven't given a timeout when set, it will always be kept in memory.

Ok this absolutely needs fixing. I just don't understand why anyone would write a cache that's not size limited in some way...
Are the redis and ledis caches at least size limited in some way?

Ok this absolutely needs fixing. I just don't understand why anyone would write a cache that's not size limited in some way...
Are the redis and ledis caches at least size limited in some way?

The cache library derived from macaron middlewares and as I know there is no size limit for all these implementations.

o_O
Then this just swaps the problem of memory for one of disk space and is not much better.

Ok.
I think we need to change the memory one to be a wrapper around an lru. If you get a cache hit just check if it's already expired and delete it if so.
That's probably the simplest thing to do - as although that means that the cache may contain expired data that data is likely not to be hot anyway and is more likely to get thrown out in an lru cache.
There's probably a library out there that has this kind of wrapping already.
For the ledis and redis caches - we can't be the first to have to do this surely? There has to be a way of limiting these caches.

Ok redis has volatile-lru, volatile-ttl and allkeys-lru options. I think therefore Redis is a configuration issue for redis users - as long as our implementation is setting expires correctly.
(Likely we should not be recommending allkeys-lru if they're using redis for queues.)
We should check that sessions have an expire set on them too.

Ledis lib looks stale as zeripath pointed out :/

The ledis project seems not active anymore. Should we give it up?


[WIP] Adds PennyLane QAOA Module Tutorial

WARNING: This tutorial will not run until PRs: https://github.com/PennyLaneAI/pennylane/pull/775, https://github.com/PennyLaneAI/pennylane/pull/774, and https://github.com/PennyLaneAI/pennylane/pull/777 are merged, and a new version of PennyLane is released. The tutorial in this PR is currently statically rendered for feedback purposes, and can be merged when the outlined conditions are met.
Title:
Adds a tutorial that outlines all of the new functionality in the PennyLane QAOA module by walking the user through a basic example of QAOA for MinVertexCover.
Summary:

Walks the user through the MinVertexcover problem
Defines cost and mixer Hamiltonians
Defines the QAOA layer
Repeatedly applies the QAOA layer
Optimizes the circuit and visualizes the results

Relevant references:
Possible Drawbacks:
Related GitHub Issues:

Hey @Lucaman99, you can make this PR against the dev branch, which is pinned to the GitHub master version of PennyLane :) Once the PRs are merged, it should build correctly

Thanks so much for the reviews @glassnotes @ixfoduap! I'll incorporate these changes ASAP!

@Lucaman99: you can now convert this tutorial into an executable one (it should be as simple as changing the filename to begin with tutorial_, and updating the TOC in demonstrations.rst).
It should work fine, since the PennyLaneAI:dev branch uses the GitHub master of PennyLane to build :) (@glassnotes @ixfoduap this will cause the plots to render)

Awesome, when might this be ready to publish and share?

Hey everyone! Sorry for the delay, the past couple weeks have been incredibly busy at school. I'm in the process of addressing these comments/TODOs, as well as writing the code for the Hamiltonian arithmetic section. Hopefully this will all be done this week 🙂

@Lucaman99, just two small comments:

Don't forget to make the tutorial executable! I just had a check, and there is still no output.

We recently re-arranged our demonstration pages, so there will be quite a significant merge conflict :) You will need to overwrite demonstrations.rst from master, and move the thumbnail for this demo to demos_basics.rst in the 'Applications' section.

🤔 Hmmmm, I'm not sure why the probability distributions look so weird. I ran it a few times locally and it seems to work fine. I'll keep digging!

Looks awesome @Lucaman99! Just a few minor comments, but otherwise the results are great and I think this is ready to be merged in.

I could not figure out how to comment about it in the review, but there is a .DS_Store in there that should be removed.


core: remove always connected flag

This flag was added when we didn't have the notion of a component, and therefore it was required for the FTP server implementation. I believe we should be able to remove it now.
Fixes #2076.

Oh, if it works like that, it's even nicer!

The FTP server test fails. That's expected. It'll be removed and replaced with a system test anyway.


ValidationError during eole predict: Extra inputs not permitted for PredictConfig

Hello guys, Iʻve just updated Eole NLP to the latest version (0.0.3). When trying to run inference using eole predict, I now get a validation error related to the PredictConfig. The error suggests there's an issue with a dummy_load parameter, though this parameter is not explicitly defined in my configuration file:
(TY-EN) ubuntu@ip-172-31-3-172:~/TY-EN/LLM$ eole predict -c tower-inference.yaml -src promptized-test.en -output test.ty
Traceback (most recent call last):
  File "/home/ubuntu/TY-EN/TY-EN/bin/eole", line 33, in <module>
    sys.exit(load_entry_point('eole', 'console_scripts', 'eole')())
  File "/home/ubuntu/TY-EN/eole/eole/bin/main.py", line 39, in main
    bin_cls.run(args)
  File "/home/ubuntu/TY-EN/eole/eole/bin/run/predict.py", line 42, in run
    config = cls.build_config(args)
  File "/home/ubuntu/TY-EN/eole/eole/bin/run/__init__.py", line 42, in build_config
    config = cls.config_class(**config_dict)
  File "/home/ubuntu/TY-EN/TY-EN/lib/python3.10/site-packages/pydantic/main.py", line 193, in __init__
    self.__pydantic_validator__.validate_python(data, self_instance=self)
pydantic_core._pydantic_core.ValidationError: 1 validation error for PredictConfig
dummy_load
  Extra inputs are not permitted [type=extra_forbidden, input_value=True, input_type=bool]
    For further information visit https://errors.pydantic.dev/2.8/v/extra_forbidden

Command used:
eole predict -c tower-inference.yaml -src promptized-test.en -output test.ty
My config file for inference:
model_path: ["finetune/merged"]

# Inference settings
seed: 42
max_length: 512
batch_type: tokens
batch_size: 512
world_size: 1
gpu_ranks: [0]

# Transforms
transforms: ['huggingface_tokenize']
transforms_configs:
  huggingface_tokenize:
    huggingface_model: "Unbabel/TowerInstruct-7B-v0.2"
    max_length: 512

# Generation settings
compute_dtype: fp16
top_k: 50
top_p: 0.9
beam_size: 6
min_length: 10
temperature: 0.7
n_best: 1
src: None

# Logging
report_time: true

yes there has been some patches since 0.0.3
just git pull et if necessary resintall using pip install -e .

Hi Vince, I successfully reinstalled eole-0.0.3 with pip install -e . yet itʻs still throwing the same error.


Update README.md

added missing linux-headers to components install step

realized this may need a little context. I just did a clean pmbootstrap install and linux-headers arent there. This ensures a user will be able to follow the steps without issue.

This is indeed missing. Thanks for checking this out and sending the patch!


The Truth shall set you free

I have reqeuested my DCMA info be remover there Times, then had Lumen CopyRight my Datas AND creative Commerce. I have had the army investigate my husbands Abandonement , CPS's lies and I AM begging for help... I haven't seen my babies for 14 weeks.  I dont even have change...

James D Houser
12-23-94
E4
Email was JamesandRachelh@ g mail
I reported fraud on this acc.
Emails now are
Jameshouser249
Octocat was his acct
And A TON more
My babies are 4 and 2.. PLEASE  help guys
He has cheated and lied...
Corruption is só deep
Please Email or call me
915 465 6008
MajesticSunandmoon@gmail


Stack Variable Resolution

Sometimes https://github.com/Vector35/dwarf_import/blob/43e4f673bd51bdafd2c2ebcf4f2a5cadad2a2a2c/bridge.py#L118 needs to be + instead of -.  We should try to detect and resolve that.

Closing in favor of https://github.com/Vector35/binaryninja-api/issues/4473


Controls ValidationErrorTemplate disappear after unloading then reloading (Caliburn.Micro)

Whenever my validated View is deactivated then reactivated (closing then reopening a popup, switching between tabs, etc) I lose all pre-existing error templates on my validating controls.
The validation still persists in the ViewModel.
I've tried:

Resetting and re-validating the Validator (Reset, ValidateAll)
Refreshing the ViewModel and raising notifications on the property.
Removing all rules, then re-applying them.
Invoking OnErrorsChanged() on the property from NotifyWarningErrorInfoAdapter.

To no avail.
The only thing that returns the ErrorTemplate is taking the property value out of the error condition then re-entering it to the condition.

It seems to be a XAML/Binding issue.
After placing all the validating Views inside AdornerDecorator the adorners now persist over deactivations.


[bug] Multiple providers bound to one "name", and associated issues

Spec: open-feature/spec@a4ffec3
See: https://github.com/open-feature/dotnet-sdk/issues/126
The spec allows a single instance of a provider to be bound to multiple names (even if it didn't allow this, any naive implementation would probably allow it to happen). We either need to prevent it or specify how it should work. We may want to specify that providers that are still bound to any client name are not shut down.  - @toddbaert
I consider this a spec bug personally, because it constitutes a problematic ambiguity in the spec. - @toddbaert
cc @justinabrahms
Quote from @kinyoklion :+1:

Basic case.
var provider1 = new TestProvider();

openFeature.SetProvider("a",  provider1);

// Call init on provider1?

openFeature.SetProvider("a",  new TestProvider());

// Call shutdown on provider 1?

// Call init on new provider.

Two Names Scenario 1.
var provider = new TestProvider();

openFeature.SetProvider("a", provider);

// Call init on provider?

openFeature.SetProvider("b", provider);

// Provider already has init called. Do we call it again?

Two Names Scenario 2.
var provider1 = new TestProvider();

openFeature.SetProvider("a", provider1);
openFeature.SetProvider("b", provider1);

openFeature.SetProvider("b",  new TestProvider());

// We don't want to shutdown provider1, because it is still registered to "b".

cc @lopitz @lukas-reining

@benjiro FYI I moved this from the dotnet-sdk repo.

I totally agree.
Also found that and implemented it in the JS SDK the way that this does not happen for the case between named and unnamed providers.
But scenario 2 is not handled by the JS SDK now, I will fix that @toddbaert.

I totally agree. Also found that and implemented it in the JS SDK the way that this does not happen for the case between named and unnamed providers. But scenario 2 is not handled by the JS SDK now, I will fix that @toddbaert.

Let's wait for now to build some consensus, just so that you dont implement something that you have to change. Do you agree with the solution I've vaguely proposed?

Yes I totally agree with that @toddbaert, this is fixing at least the shutdown for me.
I already did that, was just 3 lines of code and a test.
Will add the PR and we can merge it or change it once we have concencus what do you think?

Yes I totally agree with that @toddbaert, this is fixing at least the shutdown for me. I already did that, was just 3 lines of code and a test. Will add the PR and we can merge it or change it once we have concencus what do you think?

For now maybe add the PR here for reference.

Reading the spec a bit more, I think <IP_ADDRESS> and <IP_ADDRESS> technically addresses these concerns, though the non-normative helper-text could be improved.

Thanks Todd.
I agree with what's been stated:
basic:

yes call init there
yes, call shutdownthere

2 names:

call init when set
if already init'd, don't do it again

2 names 2:

don't shut down p1

I think this is taken care of with https://github.com/open-feature/spec/pull/193. Please re-open if you disagree, @benjiro


add "destructure variable declaration" assist(s)

Particularly for records, a destructuring assist would be handy and I expect commonly used but it would be interesting to explore lists, maps and objects too.
Records
For example,
(int, int) f() => (0,1);

m() {
  var r = f();
}

could become
(int, int) f() => (0,1);

m() {
  var (f1, f2) =  f();
}

And,
point() => (x: 1, y: 2);

z() {
  var r = point();
}

might become:
point() => (x: 1, y: 2);

z() {
  var (:x, :y) = point();
}

It gets interesting if the record declaration is accessed.
For example, I'd expect no assist in this case:
(int, int) f() => (0,1);

m() {
  var r = f();
  print(r);
}

but,
(int, int) f() => (0,1);

m() {
  var r = f();
  print(r.$1);
  print(r.$2);
}

could reasonably become:
(int, int) f() => (0,1);

m() {
  var (f1, f2) = f();
  print(f1);
  print(f2);
}

Maps
Map<String,int>  f() => {'x': 1};

m() {
  var r = f();
}

could become
Map<String,int>  f() => {'x': 1};

m() {
  var {} =  f();
}

(But note, they'll need to do something to {} since map patterns can't be empty.)
Lists
List<int> f() => [];

m() {
  var r = f();
}

could become
List<int> f() => [];

m() {
  var [] = f();
}

(Or var [...] = f();)
Objects
In a simple case we might take something like
class A {
  int a;
  A(this.a);
}

f() => A(1);

m() {
  var o = f();
}

to:
class A {
  int a;
  A(this.a);
}

f() => A(1);

m() {
  var A(:a) = f();
}

but this doesn't scale if A has a lot of fields.
Maybe better to start w/
var A() = f();
and possibly go better if fields are accessed.
class A {
  int a, b, c;
  A(this.a, this.b, this.c);
}

f() => A(1, 2, 3);

m() {
  var o = f();
  print('${o.a} ${o.b}');
}

could become
class A {
  int a, b, c;
  A(this.a, this.b, this.c);
}

f() => A(1, 2, 3);

m() {
  var A(:a, :b) = f();
  print('$a $b');
}

I'm not convinced that the non-record cases carry their weight, but I do agree that an assist to destructure a record is worth considering. If we add this, we should focus on records for a first cut and then consider the others as enhancements to the base functionality.

/fyi @leafpetersen

Basic records support landed w/ cae0bfa66f63890e282f6c35515ef063c5eb01ab.
There's an open question of whether a field name suggestion should be a linked edit (https://dart-review.googlesource.com/c/sdk/+/295381/comment/6c626001_ad74fd62/) which I'll return to.  Also, I wonder if we should add wildcards as additional suggestions for positional fields?
That is, we might add _ after $1 here:

@bwilkerson?

I like the idea of offering a wildcard pattern here, it's a reasonable choice.
We should also consider suggesting wildcard patterns in code completion.

I like this idea, especially for record and object patterns.  I'm not quite as convinced by the map and list use cases.
Is there a way that we could make it available even if there's no pre-existing variable declaration?  I.e. if I have:
class A {
  int a;
  A(this.a);
}

f() => A(1);

m() {
  f();
}

it would be nice if I could put the cursor on the f(); statement and trigger an assist that changes it to var A(:a) = f();

Is there a way that we could make it available even if there's no pre-existing variable declaration?

Currently the expectation is that you'd do this in two steps, introducing the local variable first.

I do like the idea of supporting this in one go though. Maybe we could add something like "Assign value to a new destructured pattern variable" to the already existing assist?
(Word-smithing welcome.)
(FWIW @bwilkerson, @scheglov: this is another example of micro vs. macro edits as discussed earlier today.)

After some thinking and an informal poll of folks, I'd like to go ahead with a simple conversion for Object patterns that
class A {
  int a;
  A(this.a);
}

f() => A(1);

m() {
  var o = f();
}

that produces
class A {
  int a;
  A(this.a);
}

f() => A(1);

m() {
  var A() = f();
}

with the caret inside the new declaration (A( < caret > )) assuming that folks will use code completion to fill in the fields they care about. (Note that completion improvements are being tracked in: https://github.com/dart-lang/sdk/issues/52058.)


Scheduled updates updating blocks on other layers

@JustTalDevelops do you happen to remember exactly what the issue is here?


Ready to make public and release?

I based a lot of the infrastructure on ravwojdyla/pyspark_gcs.
Currently the code doesn't have the version number anywhere in it (same as pyspark_gcs). That does make it slightly less of a hassle to make new releases. I was planning on setting up GitHub actions for PyPI deployment upon release.
@ravwojdyla did you want to check things over to see if the package looks good to you?
Repo is not public yet.

Closing as now released and public, but feel free to continue discussion.

setup long_description

I think using the following lines in setup.cfg will actually allow us to use the README for the long_description in a declarative way:
long_description = file: README.md
long_description_content_type = text/markdown; charset=UTF-8

@dhimmel good to see that setup won't have that extra custom logic regarding readme.

If we think there's a need to install dev requirements via conda, perhaps we can switch to a requirements-dev.txt, but for now I was just using venv locally since the dependencies are light.

That plus you can't install the dev dependencies without installing the package itself.


LoaderInstance::CreateInstance, no support found for requested extension: XR_KHR_opengl_enable

./hello_xr -g OpenGL -ff Hmd -vc Stereo -bm AlphaBlend -s View running bug found,  logs are:
[18:05:17.377][Info   ] Press any key to shutdown...
[18:05:17.378][Info   ] Available Layers: (0)
Error [GENERAL | xrCreateInstance | OpenXR-Loader] : LoaderInstance::CreateInstance, no support found for requested extension: XR_KHR_opengl_enable
Error [GENERAL | xrCreateInstance | OpenXR-Loader] : xrCreateInstance failed
Segmentation fault (core dumped)

That sounds like an OpenXR runtime issue, specifically that the runtime doesn't support for OpenGL applications. Which OpenXR runtime is this with?

Thanks, you are right., runtime should be set correctly and like this:
export XR_RUNTIME_JSON=/home/xxxxxxxx/monado/build_install/share/openxr/1/openxr_monado.json


codeowners

Codecov Report

Merging #256 (f6672cc) into main (801561f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #256   +/-   ##
=======================================
  Coverage   54.67%   54.67%
=======================================
  Files         228      228
  Lines       27905    27905
=======================================
  Hits        15257    15257
  Misses      12648    12648

Flag
Coverage Δ

gsagh
42.09% <ø> (ø)

integration
42.28% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[Project] Enhance Transactions CSV export

[x] Deprecate "v1" export completely

[x] Check if there is activity?
[x] Disable it on frontend asap

[x] Repair asap CSV export (when filtered by collective) in the Host Report panel
Make sure that truncation is smarter and better communicated to the user:
https://github.com/opencollective/opencollective/issues/6414

[x] When clicking export, the Frontend should do an API query to count transactions and estimate a generation time

[x] If it's an important number (e.g.: > 10,000 results, warn the users and communicate a rough estimation)
[x] If it's a too important number (e.g.: > 100,000 results, decline the request)

[ ] When exporting, we should ensure it's a direct download without proxy or unnecessary buffer. That's not the case today when clicking the button, see: fetchCSVFileFromRESTService
[ ] Any low hanging fruit to improve speed and performance?

Let user pick columns and entries they want exported:
https://github.com/opencollective/opencollective/issues/6243

[ ] Can we add email to the list?

[x] Amina amending designs to clear up the checkbox option hellness
[ ] Leo to continue, though at the eng meetup this week

[ ] released 🎉
[ ] need a release post and documentation check

Feedback issue: https://github.com/opencollective/opencollective/issues/6693


feat: added s3 utils

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


Update datasource.js for grafana 4

Update _.all to _.every as the newer version of lodash has changed the term. This fixes error seen with Timely Standalon and Grafana >4.2.
The .all alias was removed from the .every function call in lodash > version 4. .every has existed since lodash 0.1.0 and is functionally equivalent, so this change is backward compatible and safe. https://lodash.com/docs/3.10.1#every

@alerman  - this looks good, thanks for the PR.


HIV Guidance Document - Modify Zotero citations so they're compatible with GitHub markdown

See #47 for details