OpenUTAU miss catagorize SimpleENUNU model VBs as UTAU VBs.

Acknowledgement

[X] I have read Getting-Started and FAQ

🐛 Describe the bug
Hi, I want to inform about a recent bug/issue with OpenUTAU in the current build.

It's about OpenUTAU does no longer recognise SimpleENUNU models as ENUNUmodels.

It puts them as normal VB putting to the "classic"'s list which is a behaviour the old versions had.

Giving even the wrong render which SimpleEnunu only need ENUNU as the only assigned resampler/render.

This didn't occur with 0.1.129, since it's the version that the fork and server were released made by rokujyushi.
I also tried to re-install OU but the issue's still present.
Is there a solution or do I need to wait for an update? Or the compabilty is temporaly disable due of needed polishing/refinig/fixing?
Explains how to reproduce the bug
The Issue started when I updated to v<IP_ADDRESS>.
OS & Version
windows-x64
Logs
2023-06-27 22:08:02.564 +02:00 [INF] Logging initialized.
2023-06-27 22:08:02.650 +02:00 [INF] Microsoft Windows NT 10.0.22621.0
2023-06-27 22:08:02.651 +02:00 [INF] Microsoft Windows 10.0.22621 X64 X64
2023-06-27 22:08:02.651 +02:00 [INF] OpenUtau v<IP_ADDRESS> win10-x64
2023-06-27 22:08:02.652 +02:00 [INF] Data path = C:\Users*\OneDrive\Desktop\OpenUTAU <IP_ADDRESS>
2023-06-27 22:08:02.652 +02:00 [INF] Cache path = C:\Users*\OneDrive\Desktop\OpenUTAU <IP_ADDRESS>\Cache
2023-06-27 22:08:03.160 +02:00 [INF] Initializing application.
2023-06-27 22:08:03.269 +02:00 [INF] Initializing culture.
2023-06-27 22:08:03.303 +02:00 [INF] Initialized culture.
2023-06-27 22:08:03.303 +02:00 [INF] Initializing theme.
2023-06-27 22:08:03.308 +02:00 [INF] Initialized theme.
2023-06-27 22:08:03.308 +02:00 [INF] Initializing OpenUtau.
2023-06-27 22:08:03.312 +02:00 [INF] Searching singers.
2023-06-27 22:08:03.321 +02:00 [INF] Search all singers: 00:00:00.0086660
2023-06-27 22:08:03.360 +02:00 [INF] Search all plugins: 00:00:00.0475445
2023-06-27 22:08:03.361 +02:00 [INF] Search all legacy plugins: 00:00:00.0010443
2023-06-27 22:08:03.362 +02:00 [INF] Initialized OpenUtau.
2023-06-27 22:08:03.362 +02:00 [INF] Initializing audio.
2023-06-27 22:08:03.362 +02:00 [INF] ReleaseSourceTemp C:\Users*\OneDrive\Desktop\OpenUTAU <IP_ADDRESS>\Cache
2023-06-27 22:08:03.589 +02:00 [INF] Initialized audio.
2023-06-27 22:08:03.589 +02:00 [INF] Initialized application.
2023-06-27 22:08:03.589 +02:00 [INF] Framework initialization completed.
2023-06-27 22:08:03.658 +02:00 [INF] Creating main window.
2023-06-27 22:08:03.786 +02:00 [INF] Initialized main window component.
2023-06-27 22:08:03.856 +02:00 [INF] Main window checking Update.
2023-06-27 22:08:03.857 +02:00 [INF] Created main window.
2023-06-27 22:08:03.922 +02:00 [INF] SchedulePreRender
2023-06-27 22:08:03.980 +02:00 [INF] Publish notification Load project
2023-06-27 22:08:05.002 +02:00 [INF] Checking update at: https://github.com/stakira/OpenUtau/releases/tag/build/0.1.158
2023-06-27 22:08:05.002 +02:00 [INF] Checking appcast: https://github.com/stakira/OpenUtau/releases/download/build/0.1.158/appcast.win-x64.xml
2023-06-27 22:17:08.783 +02:00 [INF] Exiting.
2023-06-27 22:17:08.785 +02:00 [INF] Exited.
2023-06-27 22:17:49.853 +02:00 [INF] Logging initialized.
2023-06-27 22:17:49.933 +02:00 [INF] Microsoft Windows NT 10.0.22621.0
2023-06-27 22:17:49.934 +02:00 [INF] Microsoft Windows 10.0.22621 X64 X64
2023-06-27 22:17:49.934 +02:00 [INF] OpenUtau v<IP_ADDRESS> win10-x64
2023-06-27 22:17:49.934 +02:00 [INF] Data path = C:\Users*\OneDrive\Desktop\OpenUTAU <IP_ADDRESS>
2023-06-27 22:17:49.934 +02:00 [INF] Cache path = C:\Users*\OneDrive\Desktop\OpenUTAU <IP_ADDRESS>\Cache
2023-06-27 22:17:50.417 +02:00 [INF] Initializing application.
2023-06-27 22:17:50.500 +02:00 [INF] Initializing culture.
2023-06-27 22:17:50.531 +02:00 [INF] Initialized culture.
2023-06-27 22:17:50.531 +02:00 [INF] Initializing theme.
2023-06-27 22:17:50.536 +02:00 [INF] Initialized theme.
2023-06-27 22:17:50.536 +02:00 [INF] Initializing OpenUtau.
2023-06-27 22:17:50.546 +02:00 [INF] Searching singers.
2023-06-27 22:17:50.557 +02:00 [INF] Search all singers: 00:00:00.0102257
2023-06-27 22:17:50.588 +02:00 [INF] Search all plugins: 00:00:00.0442622
2023-06-27 22:17:50.589 +02:00 [INF] Search all legacy plugins: 00:00:00.0002720
2023-06-27 22:17:50.589 +02:00 [INF] Initialized OpenUtau.
2023-06-27 22:17:50.589 +02:00 [INF] Initializing audio.
2023-06-27 22:17:50.589 +02:00 [INF] ReleaseSourceTemp C:\Users*\OneDrive\Desktop\OpenUTAU <IP_ADDRESS>\Cache
2023-06-27 22:17:50.707 +02:00 [INF] Initialized audio.
2023-06-27 22:17:50.707 +02:00 [INF] Initialized application.
2023-06-27 22:17:50.708 +02:00 [INF] Framework initialization completed.
2023-06-27 22:17:50.762 +02:00 [INF] Creating main window.
2023-06-27 22:17:50.867 +02:00 [INF] Initialized main window component.
2023-06-27 22:17:50.936 +02:00 [INF] Main window checking Update.
2023-06-27 22:17:50.937 +02:00 [INF] Created main window.
2023-06-27 22:17:51.003 +02:00 [INF] SchedulePreRender
2023-06-27 22:17:51.061 +02:00 [INF] Publish notification Load project
2023-06-27 22:17:51.944 +02:00 [INF] Checking update at: https://github.com/stakira/OpenUtau/releases/tag/build/0.1.158
2023-06-27 22:17:51.945 +02:00 [INF] Checking appcast: https://github.com/stakira/OpenUtau/releases/download/build/0.1.158/appcast.win-x64.xml
2023-06-27 22:18:28.160 +02:00 [INF] undoGroup started
2023-06-27 22:18:28.160 +02:00 [INF] ExecuteCmd Change phonemizer
2023-06-27 22:18:28.160 +02:00 [INF] undoGroup ended
2023-06-27 22:18:28.160 +02:00 [INF] SchedulePreRender
2023-06-27 22:18:28.161 +02:00 [INF] Publish notification Pre-render notification.
2023-06-27 22:18:31.415 +02:00 [INF] undoGroup started
2023-06-27 22:18:31.416 +02:00 [INF] ExecuteCmd Change singer
2023-06-27 22:18:31.421 +02:00 [INF] undoGroup ended
2023-06-27 22:18:31.421 +02:00 [INF] SchedulePreRender
2023-06-27 22:18:31.421 +02:00 [INF] Publish notification Pre-render notification.
2023-06-27 22:19:44.210 +02:00 [INF] undoGroup started
2023-06-27 22:19:44.210 +02:00 [INF] ExecuteCmd Add part
2023-06-27 22:19:44.236 +02:00 [INF] undoGroup ended
2023-06-27 22:19:44.237 +02:00 [INF] SchedulePreRender
2023-06-27 22:19:44.238 +02:00 [INF] Publish notification Pre-render notification.
2023-06-27 22:19:44.251 +02:00 [INF] undoGroup started
2023-06-27 22:19:44.252 +02:00 [INF] Publish notification Phonemized
2023-06-27 22:19:44.645 +02:00 [INF] undoGroup ended
2023-06-27 22:19:44.645 +02:00 [INF] SchedulePreRender
2023-06-27 22:19:44.645 +02:00 [INF] Publish notification Pre-render notification.
2023-06-27 22:19:45.041 +02:00 [INF] undoGroup started
2023-06-27 22:19:45.141 +02:00 [INF] undoGroup ended
2023-06-27 22:19:45.141 +02:00 [INF] SchedulePreRender
2023-06-27 22:19:45.141 +02:00 [INF] Publish notification Pre-render notification.
2023-06-27 22:19:45.270 +02:00 [INF] undoGroup started
2023-06-27 22:19:45.295 +02:00 [INF] Publish notification Select expression dyn
2023-06-27 22:19:45.299 +02:00 [INF] Publish notification Select expression dyn
2023-06-27 22:19:45.299 +02:00 [INF] Publish notification Select expression pitd
2023-06-27 22:19:45.300 +02:00 [INF] Publish notification Select expression dyn
2023-06-27 22:19:45.300 +02:00 [INF] Publish notification Select expression clr
2023-06-27 22:19:45.301 +02:00 [INF] Publish notification Select expression dyn
2023-06-27 22:19:45.301 +02:00 [INF] Publish notification Select expression eng
2023-06-27 22:19:45.302 +02:00 [INF] Publish notification Select expression dyn
2023-06-27 22:19:45.302 +02:00 [INF] Publish notification Select expression vel
2023-06-27 22:19:45.366 +02:00 [INF] Publish notification Select expression dyn
2023-06-27 22:19:45.366 +02:00 [INF] Publish notification Select expression pitd
2023-06-27 22:19:45.367 +02:00 [INF] Publish notification Select expression clr
2023-06-27 22:19:45.367 +02:00 [INF] Publish notification Select expression eng
2023-06-27 22:19:45.367 +02:00 [INF] Publish notification Select expression vel
2023-06-27 22:19:45.368 +02:00 [INF] Publish notification Load part
2023-06-27 22:19:45.369 +02:00 [INF] undoGroup ended
2023-06-27 22:19:45.369 +02:00 [INF] SchedulePreRender
2023-06-27 22:19:45.369 +02:00 [INF] Publish notification Pre-render notification.
2023-06-27 22:19:45.409 +02:00 [INF] Created bitmap 1340, 60
2023-06-27 22:19:48.879 +02:00 [INF] undoGroup started
2023-06-27 22:19:48.894 +02:00 [INF] ExecuteCmd Add note
2023-06-27 22:19:49.035 +02:00 [INF] ExecuteCmd Change 1 notes duration
2023-06-27 22:19:49.036 +02:00 [INF] ExecuteCmd Change vibrato length
2023-06-27 22:19:49.036 +02:00 [INF] Publish notification Phonemized
2023-06-27 22:19:49.037 +02:00 [INF] Publish notification Phonemized
2023-06-27 22:19:49.645 +02:00 [INF] undoGroup ended
2023-06-27 22:19:49.645 +02:00 [INF] SchedulePreRender
2023-06-27 22:19:49.645 +02:00 [INF] Publish notification Pre-render notification.
2023-06-27 22:19:49.917 +02:00 [INF] undoGroup started
2023-06-27 22:19:49.918 +02:00 [INF] ExecuteCmd Add note
2023-06-27 22:19:50.001 +02:00 [INF] ExecuteCmd Change 1 notes duration
2023-06-27 22:19:50.001 +02:00 [INF] ExecuteCmd Change vibrato length
2023-06-27 22:19:50.002 +02:00 [INF] Publish notification Phonemized
2023-06-27 22:19:50.002 +02:00 [INF] Publish notification Phonemized
2023-06-27 22:19:50.309 +02:00 [INF] undoGroup ended
2023-06-27 22:19:50.309 +02:00 [INF] SchedulePreRender
2023-06-27 22:19:50.309 +02:00 [INF] Publish notification Pre-render notification.
2023-06-27 22:19:51.270 +02:00 [INF] undoGroup started
2023-06-27 22:19:51.349 +02:00 [INF] ExecuteCmd Change 1 notes duration
2023-06-27 22:19:51.350 +02:00 [INF] Publish notification Phonemized
2023-06-27 22:19:51.397 +02:00 [INF] ExecuteCmd Change 1 notes duration
2023-06-27 22:19:51.398 +02:00 [INF] Publish notification Phonemized
2023-06-27 22:19:51.437 +02:00 [INF] ExecuteCmd Change 1 notes duration
2023-06-27 22:19:51.438 +02:00 [INF] Publish notification Phonemized
2023-06-27 22:19:51.517 +02:00 [INF] ExecuteCmd Change 1 notes duration
2023-06-27 22:19:51.517 +02:00 [INF] Publish notification Phonemized
2023-06-27 22:19:51.965 +02:00 [INF] ExecuteCmd Change 1 notes duration
2023-06-27 22:19:51.966 +02:00 [INF] Publish notification Phonemized
2023-06-27 22:19:52.373 +02:00 [INF] undoGroup ended
2023-06-27 22:19:52.373 +02:00 [INF] SchedulePreRender
2023-06-27 22:19:52.373 +02:00 [INF] Publish notification Pre-render notification.
2023-06-27 22:19:54.222 +02:00 [INF] undoGroup started
2023-06-27 22:19:54.222 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:19:54.269 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:19:54.277 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:19:54.285 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:19:54.293 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:19:54.301 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:19:54.308 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:19:54.316 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:19:54.324 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:19:54.333 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:19:54.340 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:19:54.348 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:19:54.356 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:19:54.364 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:19:54.372 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:19:54.380 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:19:54.389 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:19:54.396 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:19:54.405 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:19:54.412 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:19:54.469 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:19:54.469 +02:00 [INF] undoGroup ended
2023-06-27 22:19:54.469 +02:00 [INF] SchedulePreRender
2023-06-27 22:19:54.469 +02:00 [INF] Publish notification Pre-render notification.
2023-06-27 22:21:02.565 +02:00 [INF] undoGroup started
2023-06-27 22:21:02.676 +02:00 [INF] ExecuteCmd Change 1 notes duration
2023-06-27 22:21:02.677 +02:00 [INF] Publish notification Phonemized
2023-06-27 22:21:02.716 +02:00 [INF] ExecuteCmd Change 1 notes duration
2023-06-27 22:21:02.717 +02:00 [INF] Publish notification Phonemized
2023-06-27 22:21:02.749 +02:00 [INF] ExecuteCmd Change 1 notes duration
2023-06-27 22:21:02.749 +02:00 [INF] Publish notification Phonemized
2023-06-27 22:21:02.773 +02:00 [INF] ExecuteCmd Change 1 notes duration
2023-06-27 22:21:02.773 +02:00 [INF] Publish notification Phonemized
2023-06-27 22:21:02.805 +02:00 [INF] ExecuteCmd Change 1 notes duration
2023-06-27 22:21:02.806 +02:00 [INF] Publish notification Phonemized
2023-06-27 22:21:02.877 +02:00 [INF] ExecuteCmd Change 1 notes duration
2023-06-27 22:21:02.878 +02:00 [INF] Publish notification Phonemized
2023-06-27 22:21:03.149 +02:00 [INF] ExecuteCmd Change 1 notes duration
2023-06-27 22:21:03.150 +02:00 [INF] Publish notification Phonemized
2023-06-27 22:21:03.245 +02:00 [INF] ExecuteCmd Change 1 notes duration
2023-06-27 22:21:03.246 +02:00 [INF] Publish notification Phonemized
2023-06-27 22:21:03.989 +02:00 [INF] undoGroup ended
2023-06-27 22:21:03.989 +02:00 [INF] SchedulePreRender
2023-06-27 22:21:03.989 +02:00 [INF] Publish notification Pre-render notification.
2023-06-27 22:21:04.741 +02:00 [INF] undoGroup started
2023-06-27 22:21:04.741 +02:00 [INF] ExecuteCmd Add pitch point
2023-06-27 22:21:04.741 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:04.868 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:04.877 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:04.884 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:04.892 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:04.901 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:04.908 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:04.917 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:04.925 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:04.932 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:04.940 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:04.949 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:04.957 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:04.973 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:04.981 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:04.988 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:05.013 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:05.125 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:05.125 +02:00 [INF] undoGroup ended
2023-06-27 22:21:05.125 +02:00 [INF] SchedulePreRender
2023-06-27 22:21:05.125 +02:00 [INF] Publish notification Pre-render notification.
2023-06-27 22:21:05.493 +02:00 [INF] undoGroup started
2023-06-27 22:21:05.493 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:05.557 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:05.565 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:05.573 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:05.581 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:05.589 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:05.597 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:05.605 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:05.641 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:05.642 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:05.645 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:05.653 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:05.661 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:05.716 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:05.725 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:05.725 +02:00 [INF] undoGroup ended
2023-06-27 22:21:05.725 +02:00 [INF] SchedulePreRender
2023-06-27 22:21:05.725 +02:00 [INF] Publish notification Pre-render notification.
2023-06-27 22:21:26.270 +02:00 [INF] undoGroup started
2023-06-27 22:21:26.270 +02:00 [INF] ExecuteCmd Change render setting
2023-06-27 22:21:26.270 +02:00 [INF] undoGroup ended
2023-06-27 22:21:26.270 +02:00 [INF] SchedulePreRender
2023-06-27 22:21:26.270 +02:00 [INF] Publish notification Pre-render notification.
2023-06-27 22:21:26.294 +02:00 [INF] Publish notification Phonemized
2023-06-27 22:21:29.262 +02:00 [INF] undoGroup started
2023-06-27 22:21:29.340 +02:00 [INF] undoGroup ended
2023-06-27 22:21:29.341 +02:00 [INF] SchedulePreRender
2023-06-27 22:21:29.341 +02:00 [INF] Publish notification Pre-render notification.
2023-06-27 22:21:29.494 +02:00 [INF] undoGroup started
2023-06-27 22:21:29.494 +02:00 [INF] Publish notification Select expression dyn
2023-06-27 22:21:29.495 +02:00 [INF] Publish notification Select expression pitd
2023-06-27 22:21:29.495 +02:00 [INF] Publish notification Select expression clr
2023-06-27 22:21:29.495 +02:00 [INF] Publish notification Select expression eng
2023-06-27 22:21:29.495 +02:00 [INF] Publish notification Select expression vel
2023-06-27 22:21:29.496 +02:00 [INF] Publish notification Load part
2023-06-27 22:21:29.496 +02:00 [INF] Publish notification Select expression eng
2023-06-27 22:21:29.496 +02:00 [INF] Publish notification Select expression vel
2023-06-27 22:21:29.590 +02:00 [INF] undoGroup ended
2023-06-27 22:21:29.590 +02:00 [INF] SchedulePreRender
2023-06-27 22:21:29.590 +02:00 [INF] Publish notification Pre-render notification.
2023-06-27 22:21:32.069 +02:00 [INF] undoGroup started
2023-06-27 22:21:32.070 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.276 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.284 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.292 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.300 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.308 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.316 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.332 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.340 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.349 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.357 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.365 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.373 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.389 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.421 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.429 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.436 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.444 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.453 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.461 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.653 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.661 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.669 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.678 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.685 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.693 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.701 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.708 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.716 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.725 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.732 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.740 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.749 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.756 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.764 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.772 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.781 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.788 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.797 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.805 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.813 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.820 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.828 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.836 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.853 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.869 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.876 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.901 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.924 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.956 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:32.972 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:33.012 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:33.077 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:33.158 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:33.189 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:33.333 +02:00 [INF] ExecuteCmd Move pitch point
2023-06-27 22:21:33.837 +02:00 [INF] undoGroup ended
2023-06-27 22:21:33.837 +02:00 [INF] SchedulePreRender
2023-06-27 22:21:33.837 +02:00 [INF] Publish notification Pre-render notification.
2023-06-27 22:22:02.222 +02:00 [INF] undoGroup started
2023-06-27 22:22:02.222 +02:00 [INF] ExecuteCmd Configure expressions
2023-06-27 22:22:02.223 +02:00 [INF] Publish notification Select expression dyn
2023-06-27 22:22:02.223 +02:00 [INF] Publish notification Select expression pitd
2023-06-27 22:22:02.224 +02:00 [INF] Publish notification Select expression clr
2023-06-27 22:22:02.225 +02:00 [INF] Publish notification Select expression eng
2023-06-27 22:22:02.225 +02:00 [INF] Publish notification Select expression vel
2023-06-27 22:22:02.225 +02:00 [INF] undoGroup ended
2023-06-27 22:22:02.225 +02:00 [INF] SchedulePreRender
2023-06-27 22:22:02.226 +02:00 [INF] Publish notification Pre-render notification.
2023-06-27 22:22:02.247 +02:00 [INF] Publish notification Phonemized
2023-06-27 22:22:02.247 +02:00 [INF] Publish notification Phonemized
2023-06-27 22:22:07.222 +02:00 [INF] undoGroup started
2023-06-27 22:22:07.308 +02:00 [INF] undoGroup ended
2023-06-27 22:22:07.308 +02:00 [INF] SchedulePreRender
2023-06-27 22:22:07.309 +02:00 [INF] Publish notification Pre-render notification.
2023-06-27 22:22:07.489 +02:00 [INF] undoGroup started
2023-06-27 22:22:07.491 +02:00 [INF] Publish notification Select expression dyn
2023-06-27 22:22:07.492 +02:00 [INF] Publish notification Select expression pitd
2023-06-27 22:22:07.493 +02:00 [INF] Publish notification Select expression clr
2023-06-27 22:22:07.495 +02:00 [INF] Publish notification Select expression eng
2023-06-27 22:22:07.496 +02:00 [INF] Publish notification Select expression vel
2023-06-27 22:22:07.497 +02:00 [INF] Publish notification Load part
2023-06-27 22:22:07.498 +02:00 [INF] Publish notification Select expression eng
2023-06-27 22:22:07.499 +02:00 [INF] Publish notification Select expression vel
2023-06-27 22:22:07.565 +02:00 [INF] undoGroup ended
2023-06-27 22:22:07.565 +02:00 [INF] SchedulePreRender
2023-06-27 22:22:07.565 +02:00 [INF] Publish notification Pre-render notification.
2023-06-27 22:22:09.461 +02:00 [INF] Publish notification Select expression eng
2023-06-27 22:22:11.063 +02:00 [INF] undoGroup started
2023-06-27 22:22:11.517 +02:00 [INF] ExecuteCmd Set phoneme expression eng
2023-06-27 22:22:11.581 +02:00 [INF] ExecuteCmd Set phoneme expression eng
2023-06-27 22:22:11.973 +02:00 [INF] undoGroup ended
2023-06-27 22:22:11.973 +02:00 [INF] SchedulePreRender
2023-06-27 22:22:11.973 +02:00 [INF] Publish notification Pre-render notification.
2023-06-27 22:22:25.647 +02:00 [INF] Exiting.
2023-06-27 22:22:25.648 +02:00 [INF] Exited.

Solution: delete the vb, reinstall the vb and choose "enunu" when installing.

Starting from 0.1.158, OpenUtau requires SimpleENUNU voicebank developers to declare their voicebank type when installing to prevent messing up with the other types in the future.

Ok Il'try.
Yes It works but I would add this, to make sure that SimpleEnunu models works, is to make sure that the model's config.yaml file in the extensions section as stated by rokujyushi in the SimpleEnunu-0.1.0+0.local.7-OpenUtau-0.1.0  release page:
extensions:
timing_editor: "%v/timing_auto_correct/enunu_timing_auto_correct.py"
wav_synthesizer: vocoder
acoustic_calculator: nnsvs
timing_calculator: nnsvs
ust_converter: built-in
Thank you very much for the help, and all possible SimpleEnunu models devs they must put this in the extensions's line or else they won't work in OU, thanks again keep the good work for OU looking forward for a possible Update when Ritsu's CrissCross singing styles would be able to use.


[#771] Resource listing improvements

in My Resources table:

Added Sharing Status column.
Added scrolling.

Can one of the admins verify this patch?

@hyi, @Castronova, @ironfroggy or @pkdash please review.

@mauriel133 You may want to update this to current develop.

@hyi, applied your suggestions now.

@hyi see if this is ready now for +1

+1


[ConstraintSolver] NFC: Add option to control early termination of shrinking phase

Currently we have a number of unsolved disjunctions hard-coded to 5,
which breaks some existing code by terminating shrinking too early.
This patch makes it a command-line option so users have control over
what that threshold can be.
Resolves: rdar://problem/33433595

@swift-ci please smoke test


Residential Demand Flexibility variables for 10 household technologies.

For Case Study 1. This is the continuation of #31 with all technologies considered and taking into account feedback and internal discussions within CS1.

@omnipotent12  thank you for including those variables
Just to be sure our understanding is correct:
"potential' is an hourly profile corresponding to the hourly amount of load that can be shifted?
I am not completely sure to understand what Limit is. nadia sait it is the maximum consumption of the equipment (if eg the air conditionning is at maximum power)?
Do we not need a variable for stating the maximum energy (MWh) that can be shifted?
We also need the 'return to 0 duration' , that we understood shoould be depending on uses (number of hours in which the 'shifting can be done, with a 0-energy balance'); How could wa neme this?
I also have a comment regarding the order of 'words'
In order to be consistant with what is done for other technologies, I would propose to change a bit the order
Potential|Electricity|Load Shifting|Residential|
Limit|Electricity|Load Shifting|Residential|
Normal Return Duration|Electricity|Load Shifting|Residential|
(last one the name probably needs to be improved)

I think that "Limit" and "Potential" is not very obvious... If I understand it correctly, this is basically upwards and downwards changes to the load by shifting in time?
Maybe "Maximum Curtailment" - and whatever is the opposite of Curtailment...

I think that "Limit" and "Potential" is not very obvious... If I understand it correctly, this is basically upwards and downwards changes to the load by shifting in time?
Maybe "Maximum Curtailment" - and whatever is the opposite of Curtailment...
@danielhuppmann, thanks for the idea! The changes have been implemented in the latest Committ.

"Maximum Dispatch" is clearer - @sandrinecharousset what do you think?

@danielhuppmann  @omnipotent12 I would not use the word curtailement regarding load shifting because we also model another kind of demand response which is called load curtailement. (load shifting consists in moving load from one time slice to another, with 0 balance regarding energy, while load curtailement means erasing some of the load, with a negative balance in energy, and constraints regarding the total amount of energy that can be curtailed

@omnipotent12 thank you for including those variables
Just to be sure our understanding is correct:
"potential' is an hourly profile corresponding to the hourly amount of load that can be shifted?
I am not completely sure to understand what Limit is. nadia sait it is the maximum consumption of the equipment (if eg the air conditionning is at maximum power)?
Do we not need a variable for stating the maximum energy (MWh) that can be shifted?
We also need the 'return to 0 duration' , that we understood shoould be depending on uses (number of hours in which the 'shifting can be done, with a 0-energy balance'); How could wa neme this?
I also have a comment regarding the order of 'words'
In order to be consistant with what is done for other technologies, I would propose to change a bit the order
Potential|Electricity|Load Shifting|Residential|
Limit|Electricity|Load Shifting|Residential|
Normal Return Duration|Electricity|Load Shifting|Residential|
(last one the name probably needs to be improved)

Thank you for the discussion @sandrinecharousset! Our understanding of the variables is the same, and I have implemented your suggested changes.
I would suggest we leave the maximum energy and return duration variables out of the nomenclature for now to reduce clutter and add them later if needed. Some potential variables (e.g. return duration) I see more as parameters assumed within the models that may not need to be exchanged and viewed on the Platform; they can instead perhaps define scenarios in CS1.

@omnipotent12 thank you for including those variables
Just to be sure our understanding is correct:
"potential' is an hourly profile corresponding to the hourly amount of load that can be shifted?
I am not completely sure to understand what Limit is. nadia sait it is the maximum consumption of the equipment (if eg the air conditionning is at maximum power)?
Do we not need a variable for stating the maximum energy (MWh) that can be shifted?
We also need the 'return to 0 duration' , that we understood shoould be depending on uses (number of hours in which the 'shifting can be done, with a 0-energy balance'); How could wa neme this?
I also have a comment regarding the order of 'words'
In order to be consistant with what is done for other technologies, I would propose to change a bit the order
Potential|Electricity|Load Shifting|Residential|
Limit|Electricity|Load Shifting|Residential|
Normal Return Duration|Electricity|Load Shifting|Residential|
(last one the name probably needs to be improved)

Thank you for the discussion @sandrinecharousset! Our understanding of the variables is the same, and I have implemented your suggested changes.
I would suggest we leave the maximum energy and return duration variables out of the nomenclature for now to reduce clutter and add them later if needed. Some potential variables (e.g. return duration) I see more as parameters assumed within the models that may not need to be exchanged and viewed on the Platform; they can instead perhaps define scenarios in CS1.

@omnipotent12 this makes sense (leaving return time out); It can be considered as model parameters

I think that "Limit" and "Potential" is not very obvious... If I understand it correctly, this is basically upwards and downwards changes to the load by shifting in time?
Maybe "Maximum Curtailment" - and whatever is the opposite of Curtailment...

@omnipotent12 @danielhuppmann
To my point of view, limit was not obvious but I think potential is not so bad (we always talk of load shifting potential....); maybe capacity could do it?

Good point @sandrinecharousset about the different meaning of curtailment.
How about a different structure:
Demand Response|Electricity|Curtailment|Potential|...
Demand Response|Electricity|Load Shifting|Potential|Increase|...
Demand Response|Electricity|Load Shifting|Potential|Reduction|...
Demand Response|Electricity|Curtailment|Actual|...
Demand Response|Electricity|Load Shifting|Actual|Increase|...
Demand Response|Electricity|Load Shifting|Actual|Reduction|...

Good point @sandrinecharousset about the different meaning of curtailment.
How about a different structure:
Demand Response|Electricity|Curtailment|Potential|...
Demand Response|Electricity|Load Shifting|Potential|Increase|...
Demand Response|Electricity|Load Shifting|Potential|Reduction|...
Demand Response|Electricity|Curtailment|Actual|...
Demand Response|Electricity|Load Shifting|Actual|Increase|...
Demand Response|Electricity|Load Shifting|Actual|Reduction|...

@danielhuppmann , Actual and Potential do not really make sense. In particular Actual load shifting does not exist. The idea is that there is an equipment that is consuming energy, it has one 'forecasted' consumption profile. This  profile can be changed (and these are the decisions taken by odels): either increase its capacity, thus increasing the load (this is the maximum dispatch, former limit), or you can decrease it in some limit (thus it is equivalent to virtual generation), which is what is meant by 'potential'. Within load shifting, the energy balance on a certain time period has to be zero (this is why we may need pther variables related to that 'time window', which we are thinking of leaving out of the nomenclature as they are more 'parameters'. The distinction 'actual' 'potential' thus is not needed. (the actual mode is not doing anything)

But how would you describe the difference between the planned load profile and the realized load? There should be a variable for that - if only to calculate how much a consumer is paid for the load-shifting...

Good point @sandrinecharousset about the different meaning of curtailment.
How about a different structure:
Demand Response|Electricity|Curtailment|Potential|...
Demand Response|Electricity|Load Shifting|Potential|Increase|...
Demand Response|Electricity|Load Shifting|Potential|Reduction|...
Demand Response|Electricity|Curtailment|Actual|...
Demand Response|Electricity|Load Shifting|Actual|Increase|...
Demand Response|Electricity|Load Shifting|Actual|Reduction|...

@danielhuppmann , Actual and Potential do not really make sense. In particular Actual load shifting does not exist. The idea is that there is an equipment that is consuming energy, it has one 'forecasted' consumption profile. This profile can be changed (and these are the decisions taken by odels): either increase its capacity, thus increasing the load (this is the maximum dispatch, former limit), or you can decrease it in some limit (thus it is equivalent to virtual generation), which is what is meant by 'potential'. Within load shifting, the energy balance on a certain time period has to be zero (this is why we may need pther variables related to that 'time window', which we are thinking of leaving out of the nomenclature as they are more 'parameters'. The distinction 'actual' 'potential' thus is not needed. (the actual mode is not doing anything)

@danielhuppmann why having demand response at the beginning? For me demand response is a category of 'technologies' suc as 'storage' 'fossils' 'res'; load shifting and load curtailment are specific demand-reponse 'technologies', then maximum dispatch and limit (the new name we are going to find for limit) are the variables defining the technology (such as capacity, maximum volume.... for generation/storage technologies)
In the results there will be some output variables defining the 'dispatch' of these 'units' that could be names 'Active power' (as shifting a load is from the point of view of the electricity system equivalent to generating energy, in some cases with negative emissions)

But how would you describe the difference between the planned load profile and the realized load? There should be a variable for that - if only to calculate how much a consumer is paid for the load-shifting...

This is in the 'demand' side of the variables. Sth. like Final Energy|....|Refrigeration
But we do not need to know the planned load for each specific use. We ony need to know what can be erased

Thanks for the discussion! I suggest we just add the variables we know we will need on the platform for the moment and revisit this if we find out others are necessary. Many potential variables may stay on the model side and not need to be exhanged/viewed on the platform.
I would put forth the following:
Maximum Reduction|Electricity|Load Shifting|Residential|<technology>
and
Maximum Dispatch|Electricity|Load Shifting|Residential|<technology>
The term Load Shifting can be juxtaposed with Curtailment if we end up differentiating, and we can add a Curtailment suite of variables then.
Sound good @sandrinecharousset, @danielhuppmann ?

t

this sounds good for me
I will add variables related to load curtailment as they are neede by the plan4eu model (but not -yet?- differentiated per technologies), as we need to include it (in some countries this is active, eg in france with a quite big volume of curtailment, and we can fill those variables from our expertise)

You don't like putting it under a broad "Demand Response" category?

You don't like putting it under a broad "Demand Response" category?

yes would make sense
Maximum Reduction|Electricity|Demand response|Load Shifting|Residential|
and
Maximum Dispatch|Electricity|Demand response|Load Shifting|Residential|
@omnipotent12 ?

You don't like putting it under a broad "Demand Response" category?

yes would make sense
Maximum Reduction|Electricity|Demand response|Load Shifting|Residential|
and
Maximum Dispatch|Electricity|Demand response|Load Shifting|Residential|
@omnipotent12 ?

This works for me too! @danielhuppmann does this preserve the spirit of what you proposed?

@danielhuppmann does this preserve the spirit of what you proposed?

I was thinking about having Demand Response as the top-level category, because dispatch and reduction are specifications of how demand responds...

I was thinking about having Demand Response as the top-level category, because dispatch and reduction are specifications of how demand responds...

Ok @danielhuppmann, I would propose the following then:
Demand Response|Maximum Reduction|Load Shifting|Electricity|Residential|<technology>
and
Demand Response|Maximum Dispatch|Load Shifting|Electricity|Residential|<technology>
The first three terms specify the type of demand response, and the last three terms specify the the sector.

@danielhuppmann all changes should be implemented, please let me know if anything else is needed. Thanks!


OTP 23.0 is not supported

It shows 23 instead of 23.0.
FYI, https://github.com/bright-u/brightu_umbrella/runs/674006771?check_suite_focus=true#step:4:12

YAML is interpreting 23.0 as the number 23, you need to wrap it in quotes: "23.0".

@ericmj Thank you.

It seems the pre-built package v1.10.3-otp-23.zip is not compatible with OTP 23.
https://github.com/bright-u/brightu_umbrella/runs/674142139#step:4:15

It is compatible but due to a bug you are using the system installed OTP when installing rebar and hex. This PR fixes the issue: https://github.com/actions/setup-elixir/pull/15

Got it, thank you. Just wait for the PR merged.


Type Mismatch

I followed the instruction, even i tried with your example but i still got the same error (i used Colab):
TypeError: Input 'y' of 'AddV2' Op has type float32 that does not match type float16 of argument 'x'.

There is  a mixed precision training test in tests, can you run it?
And have you change the file tensorflow-addons/text/crf.py according to readme?

There is a mixed precision training test in tests, can you run it?
And have you change the file tensorflow-addons/text/crf.py according to readme?

I did all the things. Could you try it for once? (Colab)
Thanks anyway!

is the error like this?
This is because current tensorflow-addons/crf calculate doesn't support mixed precison. So I mention in readme that ypu need to change a line in that file.

Currently these is a bug in tensorflow-addons.text.crf, which causes a dtype error when using miex precision. To correctly use mixed precison, you need to modify the line 488 of tensorflow_addons/text/crf.py to:
crf_fwd_cell = CrfDecodeForwardRnnCell(transition_params, dtype=inputs.dtype)

The file path in Colab is :  '/usr/local/lib/python3.6/dist-packages/tensorflow_addons/text/crf.py'
Or you can pip install -U tfa-nightly to use the nightly version, but I don't recommend this because it does a forced type transferation and may cause some problems.

I changed that line, still got this error (don't know whether i changed in correct way).
Anyways, i solved my problem by another approach. Thanks so much!


Is it possible to invoke provided Python functions in the JS script?

Hi @maurocchi, this feature is not implemented in PyMiniRacer yet. Would you be interested in contributing?

Hi Jean-Baptiste, currently I'm still in explorative mode, however thanks for the opportunity.

I'm starting to dig into how this might be implemented.

Hey @btashton, any news on this?

@maurocchi closing since no news from you. Let me know if you need any pointer on this!

https://github.com/tbodt/v8py/blob/4fe3eea9ac637e8dba365f215498a2f8fafd0c45/v8py/convert.cpp#L11
it has been implemented in this project, so that could be used as a reference point

https://github.com/tbodt/v8py/blob/4fe3eea9ac637e8dba365f215498a2f8fafd0c45/v8py/convert.cpp#L11
it has been implemented in this project, so that could be used as a reference point


added jiafie7

Related issue

What changes does this PR do?
Screenshots (If any)
Questions

Please follow alphabetical order.


Multithreading Refactor

Co-authored-by: Nate Martin<EMAIL_ADDRESS>

Superceded #72


data

I only have images and masks, how should I train them? Thank you.

please check our tutorial
https://github.com/bowang-lab/MedSAM/tree/LiteMedSAM#model-training

Hello, the dataset I annotated with labelme was not successfully converted, as shown below:
The JSON file for the single image annotated by labelme has been attached. I hope you can help me solve it.
人生海海海布里
@.***

------------------ 原始邮件 ------------------
发件人:                                                                                "bowang-lab/MedSAM"                                                                                @.>;
发送时间: 2024年1月18日(星期四) 凌晨1:04
@.>;
<EMAIL_ADDRESS>主题: Re: [bowang-lab/MedSAM] data (Issue #193)
please check our tutorial
https://github.com/bowang-lab/MedSAM/tree/LiteMedSAM#model-training
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


[STRATCONN-3100] TikTok Docs Update

Proposed changes
We've updated the TikTok destinations. This PR reflects the new state of the destination.
Merge timing

Depending on the rollout of the destination. Targeting September 18th.

@marinhero - just want to confirm new deploy date is looking like 9/25?

Hi @forstisabella! Yes, 9/25 is the accurate date. Thank you and @rvadera12 for addressing the suggestions 🙇🏽


Add g++-11 installation steps for Windows

@liznguyen12 can you confirm the steps in #433 actually work? If so, you can close this issue.


Align titles to other PyAnsys libraries

As title says. Align documentation headers to other PyAnsys libraries

Thank you @RobPasMue !


Receive "Error displaying widget"

Environment Information

mapwidget version: "^0.1.2"
Python version: 3.10.12
Operating System: macOS Version 13.5 (22G74) (on M1), Firefox 116.0.3 (64-bit)

Description
On repeating basic Leaflet map example (https://mapwidget.gishub.org/examples/leaflet/)
I receive a 'Error displaying widget' after attempting to display map
What I Did
On inspection of the Web Console, errors are populated regarding Error: Could not create a view for model id, or TypeError: class constructors must be invoked with 'new'
See screenshot:

Thank you for reporting. Did you install it using pip or conda?

I installed via poetry

If possible, try installing it using conda. Sometimes pip or poetry might have difficulty in getting the js libraries right.
https://mapwidget.gishub.org/installation/#install-from-conda-forge
This is a very common issue with ipylealfet. See https://github.com/jupyter-widgets/ipyleaflet/issues?q=error+displaying+widgets

Thanks. There must be something amiss with my poetry env.
For reference, on creating a fresh poetry env, with only jupyter and madwidget dependencies, all worked.

Great to hear that you sorted things out.


Can I use this, when we need to call await for job which is in same file

Can I use this, when we need to call await for job which is in same file?
Jobs:
 use_api:     runs-on: ubuntu-latest     steps:         run: |           sleep 20
next step is your await method

If this is between multiple jobs you can use needs syntax typically:
https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idneeds


Clarify Wayland support

The readme is not clear on whether Wayland is supported. It says:

To apply a keyboard layout in user-space:
# equivalent to `xkbcomp -w10 layout.xkb $DISPLAY`
xkalamine apply layout.yaml

This has limitations: it doesn’t work on Wayland and the keyboard layout doesn’t show up in the Gnome keyboard manager. Besides, on some distros, media keys might stop working.

Pretty clear so far. But then it says:

The proper way to install a keyboard layout on Linux is to modify directly the files in /usr/share/X11/xkb. This is where xkalamine comes in:
sudo xkalamine install layout.yaml

Does "the proper way" mean it works for Wayland too? At first I thought so, but I found it doesn't work so I'm guessing Wayland is not (yet) supported. In any case, can we reword this section to make it clear?

My current understanding is that a keyboard layout can only work on Wayland if it’s installed in /usr/share/X11/xkb :

layout entry in rules/{evdev,base}.xml
layout content in symbols/[locale]

And that’s what xklamine does — adding a type="kalamine" attribute to the {evdev,base}.xml index files, and KALAMINE::{BEGIN,END} marks in the symbols/[locale] files.
However, on recent Linux distros the type="kalamine" attribute breaks the layout index. This causes a few worrying bugs, among which the keyboard layout might not be seen by Wayland at all.
I’ve never seen any issue with Wayland once these attributes are removed, and that’s what #25 is about. I hope it’ll solve the issue once merged.

Oh, and it seems like installing an XKB layout in userspace is possible and works on Wayland as well. This would be the next step.

FYI, I have just created the following issue to track the "how to to install a layout in userspace" topic.
https://github.com/fabi1cazenave/kalamine/issues/29

This should be fixed by #25.


Error while installing LiteDB v5 in Vs2015

Hello,  I'm new to liteDB and o tried to install it on visual studio 2015 but am getting an error " failed to add reference to 'System.Runtime'. Please make sure that it is in the Global Assembly Cache. "
When I downgrade to 4x it installs successfully can anyone help me to fix that thank you

Install-Package System.Runtime -Version 4.3.1

System.Runtime package is a part of dotnet standard but not in dotnetFrameWork 4.6.you can install it with package manager cli.

Hello, I'm new to liteDB and o tried to install it on visual studio 2015 but am getting an error " failed to add reference to 'System.Runtime'. Please make sure that it is in the Global Assembly Cache. "
When I downgrade to 4x it installs successfully can anyone help me to fix that thank you
Install-Package System.Runtime -Version 4.3.1

Install-Package System.Runtime -Version 4.3.1

At first I had installed it but I had the save message that's because vs did not add System.Runtime In my references so I had To do it manually  and it worked out
Thank you


Add Custom Post Type support to outbox API

This add contents from all enabled post types into the outbox API output, instead of the previously hardcoded "post" type.

Thanks @blueset 🙂


HTTP header cache-control

I've noticed that the implementation of this polyfill differs from the implementation of EventSource by Google Chrome in the header of the request made to the SSE server.
When using the built-in Google Chrome EventSource implementation, the request does not include the cache-control HTTP header, whoever, when using the polyfill, this attribute is included.
The problem of this, in my case, was that my SSE server was not whitelisting this header, making all the SSE requests coming from clients using the polyfill to be rejected with a CORS error.
Is the cache-control attribute part of the EventSource specification? Should we omit it from the requests made with the polyfill?

I'm facing the same issue as well. I'm hoping to see this being acknowledged.


Renamed or deleted entities not removed from catalog

Expected Behavior

When an entity is renamed by changing the metadata.name property in a registered catalog-info.yaml file, the existing entity is renamed
When an entity is removed by removing the reference in a registered location file, the existing entity is removed

Current Behavior

in both cases above, the existing entity still exists in the catalog (database) after the ingestion loop has finished. In the renaming case a new entity with the new name has been added. It is also not possible to, via the UI, remove only the old/renamed entry without also remove the new entry, requiring the entity to be re-registered.
This seems like a known issue, and it seems that the area is currently being refactored, but I thought it might be worth having an issue to list/monitor that this currently doesn't work as I would expect
Possible Solution

In the ingestion loop, compare the existing list of entities in the database with the newly generated list of entities and delete the missing ones from the database
See @freben comment: https://github.com/backstage/backstage/blob/master/plugins/catalog-backend/src/ingestion/HigherOrderOperations.ts#L85

Steps to Reproduce

See description in expected behaviour section above.
Context

In our environment we auto-generate a fairly large amount of entities from an external source and then use a location entity to assist Backstage to consume the generated yaml-files. With the bug, we need to periodically delete all entities in the database from this location to prune orphaned/deleted entities.
Authors get confused when they rename entities and they end up with duplicate entries. Deleting the duplicate entry via the UI causes both entries to be removed from the catalog.

Your Environment

NodeJS Version (v12):
Operating System and Version (e.g. Ubuntu 14.04):
Browser Information:

This appears to be a duplicate of https://github.com/backstage/backstage/issues/3750 (albeit with a much more thorough description 😄 )

Great! I was a bit confused that I didn't find an issue about it, but apparently I just need to work no my google-fu a bit. Thank you!

Also, this is what we're literally this minute working on - look forward to improvements! :)


one entry in nonRenderableFiles: []

would be nice if string is supported in case of one entry + better error if the link to file is wrong

Please provide an error message that you're getting when the link to file is wrong.
Docs explain well how that works, but we should make sure the error is also helpful

Details not provided

@derberg I can provide some insight here. When you provide nonRenderableFiles options it is guess work (unless you done it a few time) whether it actually stop the file from being rendered.

better error if the link to file is wrong

And by this I think it means adding an error if no files where found, this would be useful for me a couple of time.

would be nice if string is supported in case of one entry

What is meant here is just instead of nonRenderableFiles: ["path"] to do nonRenderableFiles: "path". For me this is irrelevant though.

@jonaslagoni oh, so these are two different features, but yeah, thanks for clarification 😄

I'm closing it for now. There was no further interest in this, we can always reopen when needed


New loader

https://codepen.io/anon/pen/RBLoXo

Resolved in https://github.com/CryptoVerseCC/tokntalk/commit/12f7f050a51bfd17fd35bd6b1e62001dbd429c1b


Building TensorFlow Lite NNAPI with C/C++ for Android: runtime link error libnnapi_delegate.so not found

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): MacOS 10.15.4
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: Samsung Galaxy Fold, Samsung Galaxy S10, Oppo ... etc Android Devices
TensorFlow installed from (source or binary): source
TensorFlow version: latest (cloned 3 days ago)
Python version: 2.7
Installed using virtualenv? pip? conda?:
Bazel version (if compiling from source): 2.0.0
GCC/Compiler version (if compiling from source): Apple clang version 11.0.0 (clang-1<IP_ADDRESS>)
CUDA/cuDNN version:
GPU model and memory:

Describe the problem
I'm building TensorFlow Lite with C/C++ to run on Android devices. Building C, GPU delegate works well, but when I tried to link NNAPI delegate(libnnapi_delegate.so), library open fail on runtime.
Provide the exact sequence of commands / steps that you executed before running into the problem
Got nnapi_delegate.so from
bazel build -c opt --config=android_arm64 //tensorflow/lite/delegates/nnapi:nnapi_delegate

Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
Error Log
2020-03-26 15:37:26.311 20452-20452/com.example.hellolibs E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.example.hellolibs, PID: 20452
    java.lang.UnsatisfiedLinkError: dlopen failed: library "/Users/yonggyulee/Documents/GitHub/AI-Kit/tflite/c/hello-libs/app/src/main/cpp/../../../../distribution/tflite/lib/arm64-v8a/libnnapi_delegate.so" not found
        at java.lang.Runtime.loadLibrary0(Runtime.java:1016)
        at java.lang.System.loadLibrary(System.java:1669)
        at com.example.hellolibs.MainActivity.<clinit>(MainActivity.java:32)
        at java.lang.Class.newInstance(Native Method)
        at android.app.AppComponentFactory.instantiateActivity(AppComponentFactory.java:69)
        at androidx.core.app.CoreComponentFactory.instantiateActivity(CoreComponentFactory.java:41)
        at android.app.Instrumentation.newActivity(Instrumentation.java:1219)
        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3040)
        at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3292)
        at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78)
        at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108)
        at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1980)
        at android.os.Handler.dispatchMessage(Handler.java:106)
        at android.os.Looper.loop(Looper.java:214)
        at android.app.ActivityThread.main(ActivityThread.java:7168)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:494)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:975)

CMakeLists.txt
cmake_minimum_required(VERSION 3.4.1)

# configure import libs
set(distribution_DIR ${CMAKE_CURRENT_SOURCE_DIR}/../../../../distribution)

add_subdirectory("${CMAKE_CURRENT_SOURCE_DIR}/opencv")

add_library(lib_tflite SHARED IMPORTED)
set_target_properties(lib_tflite PROPERTIES IMPORTED_LOCATION
        ${distribution_DIR}/tflite/lib/arm64-v8a/libtensorflowlite_c.so)

add_library(lib_tflite_gpu SHARED IMPORTED)
set_target_properties(lib_tflite_gpu PROPERTIES IMPORTED_LOCATION
        ${distribution_DIR}/tflite/lib/arm64-v8a/libtensorflowlite_gpu_delegate.so)

add_library(lib_nnapi SHARED IMPORTED)
set_target_properties(lib_nnapi PROPERTIES IMPORTED_LOCATION
        ${distribution_DIR}/tflite/lib/arm64-v8a/libnnapi_delegate.so)

# build application's shared lib
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=gnu++11")

add_library(hello-libs SHARED
        hello-libs.cpp)

target_include_directories(hello-libs PRIVATE
        ${distribution_DIR}/tflite/include
        ${distribution_DIR}/tflite/include/tensorflow/lite/tools/make/downloads
        ${distribution_DIR}/tflite/include/tensorflow/lite/tools/make/downloads/flatbuffers/include
)

target_link_libraries(hello-libs
        android
        lib_tflite
        lib_tflite_gpu
        neuralnetworks
        lib_nnapi  # If i remove this line, there is no error, and everything including inference works well.
        opencv
        log)

Solved with static library. But NNAPI delegate is slower than CPU or GPU.

If the NNAPI delegate does not support some of the ops or parameter combinations in a model then it fallback on cpu for computing. This can cause it to execute slow performance than cpu.
See https://www.tensorflow.org/lite/performance/nnapi#use_supported_models_and_ops to know more.
I will close this issue since the original problem is solved. Thanks!


SCG search button is white on white

On the iPad and also  on some rocky (?), the google search button text does not display because it is white on white.
Why is this only one some platforms?

Added css for search-button


Add job for running Hadoop YARN unit tests on ARM64

This change add a for building and running unit tests of Hadoop YARN on
ARM64 server

recheck

Re-trigger the openlab check.


Feature request - Delay option.

Feature request for a flag to specify delay when two or more tasks should run in parallel. For case when two or more tasks has to be running simultaneously, but there has to be a delay before starting task number two.
Example: run postcss:dev script, wait for a 1000 ms and run start script. Then, keep both running in parallel.
"postcss:dev": "postcss --config postcss.config.js -o css/styles.css css/**/*.postcss --map --watch",
"start": "react-scripts-ts start",
"start:dev": "sh -ac '. ./.env.development;' && npm-run-all -p postcss:dev --delay=1000 start"

Without the delay, app will reload before the postcss gets compiled which leads to styles not loaded properly.

+1

Is there some progress on this feature?

If you need a delay, you should use https://github.com/sindresorhus/delay-cli
To the original example, here is my preferred solution:

have a prep-build script that does your initial CSS build
have a separate watch script that watches for changes and rebuilds your CSS based on that
have your dev script run the prep-build script, and then run all your watch scripts and your development server in parallel

Example at https://github.com/TehShrike/memorize-text-app/blob/3c5126f70b8485541f6d6e69dda6ec496fafa1b4/package.json#L12

Thank you, but i'm using it differently.
    "pretest:integration": "webdriver-manager update", "test:integration": "run-p test:integration:*", "test:integration:student": "run-s test:integration:student:*", "test:integration:student:desktop": "ng e2e student-integration --webdriver-update false", "test:integration:student:tablet": "ng e2e student-integration --webdriver-update false --protractorConfig test/integration/protractor-tablet.conf.js", "test:integration:student:mobile": "ng e2e student-integration --webdriver-update false --protractorConfig test/integration/protractor-mobile.conf.js", "test:integration:teacher": "ng e2e teacher-integration --webdriver-update false", "test:integration:preview": "ng e2e preview-integration --webdriver-update false",
It would be nice to set an interval between commands. Do you think thats possible?

If you're setting a delay between them, then they're not running in parallel :-x

Well, that's just not true. For example, start a server listening on a port and wait a few beats for the server to start. Then, start a client which connects to that server over the port and has a conversation. If the client starts before the server (possible due to variations in process startup), then the client will crash with no server endpoint. Solving this problem by waiting for a file or sleeping until the port is up and being used is the current best method (I use losf -ti tcp:<port> for this purpose). A delay would be nicer. Or, for my purposes a way to specify if a port is active, but that's not the original request (for a delay).

I would recommend making a CLI script that polls for a port to be open, that exits with a code 0 once the port is open, or exits with a non-0 exit code after some timeout period.  Then you can run your client like poll-for-port --port=8080 --timeout=5000 && node ./my-client-test-thingy.js
This functionality seems out of scope for npm-run-all

I have often recommended wait-on package.

This shouldn't be part of npm-run-all. There's already the native sleep on most OSs and you can use delay-cli if you want a cross-platform version. No need to add further options.


When searching for a workflowTemplate, the text box isn't autoselected

Summary
This is minor, but also really annoying when trying to run a bunch of workflows from the UI.

Go to /workflows
Click 'Submit new workflow'
Click in the 'select a workflow template' text area
Start typing

Issue: Your typing isn't refining the search.
I have to click again in the text dropdown for my typing to be effective.
Diagnostics
What Kubernetes provider are you using? EKS 1.1.9
What version of Argo Workflows are you running? 3.0 RC9

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

This is still an issue (3.1 RC 12)


MVP

Post routes for inventory

Recipe API -as noted in issue

Generating onto page (front end/recipes)

Saving Recipes to local storage

Would like to use templating engine

maybe handlebars.js

Needs to use

express.js
heroku
node.js
sequalize DB


Sub menus don't work with Wacom tablet

Graphic tablets have absolute cursor positioning, so I just tested, when I open second menu cursor jumps to the center, but immediately jumps back to where it was (because of absolute positioning of the tablet). So If you have a tablet you can't open second menus.
Demo:
https://fastupload.co/1085111
I think using radial menus with a tablet is very intuitive, so it would be nice to have pmenu support tablets. Maybe adding jump toggle to the config?

It is possible to open it, if you flick your pen quickly to the second menu, but if you are too slow it won't open. And if you click on spot it also doesn't open.

Another quick fix.
Just added a -w option for the Wacom-mode, which disables pointer warping.


SAK-40004 - Update Spring to latest release before 5.X

This update will help to track deprecations done before 5.X making more easy to port all sakai to 5.X

@deinok Open a new JIRA issue that says:
Spring upgrade from 4.x.x. to 4.x.x
put all the commits required for this change and submit a single PR
Please stop using SAK-40004

It's related to the port to JDK11

Core Team decided to close.


Auto watch not working

Autowatch is not running if the value is true

Not a bug - was an issue with my config file (oops)


Upgrade softflowd used by crawler to extended version and use Netflow V10

Upgrade the softflowd used by the crawler's fprobe plugin to a newer and extended version
and use Netflow V10 (IPFIX) instead of the previous Netflow V5. The benefit of IPFIX and the extended softflowd is that it now can detect which side initiated a TCP connection (not UDP or ICMP, though). We can use this information on the backend side to annotate initiators of a connection.
Signed-off-by: Stefan Berger<EMAIL_ADDRESS>

Codecov Report

Merging #297 into master will decrease coverage by 0.01%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master     #297      +/-   ##
==========================================
- Coverage   88.97%   88.95%   -0.02%
==========================================
  Files         114      114
  Lines        4345     4347       +2
==========================================
+ Hits         3866     3867       +1
- Misses        479      480       +1

Impacted Files
Coverage Δ

...rawler/plugins/systems/fprobe_container_crawler.py
81.43% <66.66%> (-0.27%)
:arrow_down:

Continue to review full report at Codecov.

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

codecov seems unhappy at test coverage of these changes. This blocking behaviour seems new. Do you wanna tackle this given the new flow probes you are currently working on?

I modified the test case a bit. Maybe we get some of the lost coverage back.

Codecov is good now. There was one build that failed for non-obivous reasons.


[wip] pipeline

This change is

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

This pull request introduces 1 alert when merging 5eaf988ee7b13cb23c947a57ac33d3833d1ac28c into 3013ba44b7bcc01bae81e296aa19ff6c61781aba - view on LGTM.com
new alerts:

1 for Syntax error

Comment posted by LGTM.com


FileLoader seems not to work in Meteor

When I use the fileLoader() function in my project, Meteor crash with this issue :

Error: ENOENT: no such file or directory, scandir '/imports/api/graphql/types/'

My code is pretty simple :
import path from 'path';
import { fileLoader, mergeTypes } from 'merge-graphql-schemas';

const types = fileLoader(path.join(__dirname, './'));

export default mergeTypes(types);

The /imports/api/graphql/types/ folder really exists and contains 2 JS files with graphql Type (I also tried with .graphql files).
If I import manually my 2 files, the project runs well :
import { mergeTypes } from 'merge-graphql-schemas';
import authorType from './authorType';
import postType from './postType';

const types = [authorType, postType];

export default mergeTypes(types);

Any ideas ?
Thanks.

@benjhoo Where is the fileLoader file located? __dirname will give you the current directory of where it's been executed from.
I believe you just need to fix the path that you are passing to the fileLoader. e.g lets assume your code snippet is located in /imports/startup/server then path.join(__dirname, './') would output /imports/startup/server/. Which I suspect isn't what you want.

Hi,
Wrong path was indeed the problem.
I though '/' was refering to the meteor project root, not the filesystem one.
Using path.join(/(.+)\.meteor/.exec(process.cwd())[1], __dirname) solved my problem.
Thank you.

@benjhoo Thanks! you save my day!


config/database.php 'options - database'

work only if I change the word 'database' for 'db'
laravel 6 php 7.2

@jampzo, let's go to slack. You can find link here

@jampzo, do you solve this problem?

yes @Smolevich thanks!
I changed the word database by db
options' => [
'db' => 'admin'
]
and it's working.


jquery-validate.bootstrap-tooltip.js

These changes works with bootstrap version 4.x.x

I don't think this fixes the issue you are likely seeing.  I'm guessing you are having an issue with Bootstrap v4 because they switched to popper.js as a dependency.  If you are still having issues, make sure to use the umd version of popper.js


Mandate importlib-metadata for Python 3.7

I think this should fix #34. I'm new to Poetry so please check I've done the right thing. This should mandate importlib-metadata (of any version 1.4 or newer) for Python 3.7.x only.

Can't replicate error described


The deleted blobs disappear after uploading the same blobs

Storage Explorer Version: 1.2.0
Platform/OS Version: Windows 10/MacOS High Sierra/Linux Ubuntu 16.04
Architecture: ia32/x64
Build Number: 20180622.2
Commit: d667aec0
Regression From: Not a regression
Steps to Reproduce:

Go to Subscription -> Storage Accounts.
Enable soft delete -> Open one blob container and upload one blob to it.
Delete the uploaded blob then make sure it displays under 'Deleted blobs'.
Upload the same blob again and check the deleted blobs.

Expected Experience:
The deleted blob in step2 still displays under 'Deleted blobs'.
Actual Experience:
The deleted blob in step2 disappears under 'Deleted blobs'.

If you upload a new blob with the same name of some deleted blob, the deleted blob and all its snapshots become deleted snapshots of the new uploaded blob. This is by design since this is the default behavior of the blob storage service.

This is a service behavior and it is very unlikely that a user upload blobs of different types with the same name. We will reconsider this if some one complains about it.


Issue #57 resolved

Hello ADS team,
This request is to review the code, regarding my task to fix issue #57. I have Implemented code to handle exceptions and integrated to CentOSBridgeVZAdapter.py and CentOSVZAdapter.py files and tested. I faced few issues while testing the code in bridge environment and resolved. Now the code was working fine and able to deploy the lab. I checked in the code to the ovpl repository with branch =fix-issue-#57=

This pull request is now managed with CodeReviewHub. Refresh.


Use correct jax/jaxlib constraints in recipe

Fixes #19

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

cc @fehiepsi

Thanks. Do you think that we should worry about the errors? It looks to me like we need to bump the version number in the checklist.

Thanks. Do you think that we should worry about the errors? It looks to me like we need to bump the version number in the checklist.

Yep correct. Will do that now.

Thanks. Do you think that we should worry about the errors?

Some of the errors I looked at seemed like random timeout error. Let's look at the results of this CI run.

@conda-forge-admin, please rerender

Thanks, @pierreglaser!


Overwriting queue-download

When queue-download gets a file with the same filename from the same host multiple times it overwrites the previous files. This is not a desired behaviour - qDup should automatically add a suffix if the downloaded file exists.
It's desired, though, to overwrite a file from a previous run - therefore the conflicts should be resolved within download queue, not checking the filesystem on each download.

I'm curious, what was the use case where you needed multiple copies of the same file?
When we use queue-download it means the file will be downloaded after the run-scripts or after cleanup-scripts if the file was queued during a cleanup script. If the file is changing between calls to queue-download then only the latest version will be downloaded. If we want to save the file multiple times then we can either use download to copy the file immediately or save a copy to with a unique-name and use queue-download on the copy.
Using download will still override the destination if it already exists in the hosts output folder. This was intentional because we would get the same default behavior if we used scp in the terminal.
What do you think about an option to avoid replacing a previously downloaded file?
If we decide the option should override existing files but not files from a previous download or queue-download then we will have to add some internal tracking.

In my case I've downloaded files /path/to/foo/file.txt and /path/to/bar/file.txt without using the second parameter to queue-download. Since by default both these are downloaded to $workdir/$host/file.txt one download overwrote the another.

Assuming you want to download everything below /path/to, you can define - queue-download: /path/to and you should see $workdir/$host/foo/file.txt and $workdir/$host/bar/file.txt on the qDup host machine


Cilium Operator dashboard doesn't work

Is there an existing issue for this?

[x] I have searched the existing issues

Version
equal or higher than v1.16.0 and lower than v1.17.0
What happened?
Hello. I installed Cilium using Helm. Two dashboards were installed successfully: Cilium Operator and Cilium Metrics, but only Cilium Metrics works.
There is an error: "Datasource ${DS_PROMETHEUS} was not found" when I open the Cilium Operator dashboard.

How can we reproduce the issue?
Install Cilium with helm with the following values
dashboards:
  enabled: true

operator:
  dashboards:
    enabled: true

Cilium Version
1.16.2
Kernel Version
doesn't matter
Kubernetes Version
doesn't matter
Regression
No response
Sysdump
No response
Relevant log output
No response
Anything else?
No response
Cilium Users Document

[ ] Are you a user of Cilium? Please add yourself to the Users doc

Code of Conduct

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

Thanks for the report @maxpain . I just tried this myself locally and I can't reproduce the behaviour you're reporting. I'm following the instructions at https://github.com/cilium/cilium/tree/main/examples/kubernetes/addons/prometheus . I'm not sure what I am doing differently from you, but I wonder whether it might help to restart the operator after applying the configuration?
$ make kind
...
$ make kind-install-cilium
...
$ cat dashboards.yaml
dashboards:
  enabled: true

operator:
  dashboards:
    enabled: true
$ cilium upgrade --chart-directory=/var/git/cilium/install/kubernetes/cilium --helm-values=/var/git/cilium/contrib/testing/kind-common.yaml --helm-values=/var/git/cilium/contrib/testing/kind-values.yaml --helm-values=dashboards.yaml --version=
🔮 Auto-detected Kubernetes kind: kind
✨ Running "kind" validation checks
✅ Detected kind version "0.22.0"
ℹ  Using Cilium version 1.17.0
🔮 Auto-detected cluster name: kind-kind
🔮 Auto-detected kube-proxy has been installed
$ kubectl patch -n kube-system configmap cilium-config --type merge --patch '{"data":{"prometheus-serve-addr":":9962"}}'
configmap/cilium-config patched
$ # (delete all cilium-agent pods to pick up the new config)
$ kubectl create -f examples/kubernetes/addons/prometheus/monitoring-example.yaml
namespace/cilium-monitoring created
serviceaccount/prometheus-k8s created
configmap/grafana-config created
configmap/grafana-cilium-dashboard created
configmap/grafana-cilium-operator-dashboard created
configmap/grafana-hubble-dashboard created
configmap/grafana-hubble-l7-http-metrics-by-workload created
configmap/prometheus created
clusterrole.rbac.authorization.k8s.io/prometheus created
clusterrolebinding.rbac.authorization.k8s.io/prometheus created
service/grafana created
service/prometheus created
deployment.apps/grafana created
deployment.apps/prometheus created
$ kubectl -n cilium-monitoring port-forward service/grafana --address <IP_ADDRESS> --address :: 3000:3000
Forwarding from <IP_ADDRESS>:3000 -> 3000
Forwarding from [::]:3000 -> 3000
Handling connection for 3000
...

I use VictoriaMetrics stack
https://github.com/VictoriaMetrics/helm-charts/blob/master/charts/victoria-metrics-k8s-stack/README.md

I see. I don't know how that works. Looking at the image, it seems like somehow there is a variable that is not being substituted correctly for the cilium-operator when deploying with that stack.
I would welcome you to share if you're able to find a solution to this problem. If something can be changed in Cilium that can make this integration easier for you, then you are welcome to submit a PR to improve that part of the tree.

@joestringer I found the problem. The Cilium Metrics dashboard has DS_PROMETHEUS=prometheus variable, while Cilium Operator doesn't:

@joestringer, we need to add the DS_PROMETHEUS variable to the Cilium Operator dashboard.

Hmm, interesting. When I search for the error, I see https://github.com/grafana/grafana/issues/10786 which reports that it is a feature request to be able to deploy variables during dashboard provisioning. It sounds like there's no official way to do this today, but there are workarounds.


Internationalization?

I tried installing https://github.com/solidusio/solidus_i18n and adjusting the language in the backend, but that did not do anything so far :/

Ah, if I offer only one language I need to set it in the config, the backend setting only works with multiple languages it seems...


Regression : Flutter Gallery fails to run with the latest Dart roll

This is the Dart side issue for https://github.com/flutter/flutter/issues/15368
This is a regression that is introduced when the latest Dart is rolled into flutter, resulting in a crash when flutter gallery is run
`The following NoSuchMethodError was thrown building
_OverlayEntry-[LabeledGlobalKey<_OverlayEntryState>#0e6f9](state: _OverlayEntryState#85633):
Class 'RenderStack' has no instance setter '_firstChild'.

Interesting dump from the dill file:
  abstract class _RenderStack&RenderBox&ContainerRenderObjectMixin extends box3::RenderBox implements obj::ContainerRenderObjectMixin<box3::RenderBox, sta::StackParentData> {
    [...]
    generic-covariant-impl generic-covariant-interface field box3::RenderBox _firstChild = null /* from file:///usr/local/google/home/jensj/code/nobackup/flutter/flutter/packages/flutter/lib/src/rendering/object.dart */;
    [...]
    method /* from file:///usr/local/google/home/jensj/code/nobackup/flutter/flutter/packages/flutter/lib/src/rendering/object.dart */ _insertIntoChildList(generic-covariant-impl box3::RenderBox child, {generic-covariant-impl box3::RenderBox after = null}) → void {
      [...]
      if(after.{core2::Object::==}(null)) {
        childParentData.{obj::ContainerParentDataMixin::nextSibling} = this.{obj::ContainerRenderObjectMixin::_firstChild};
        if(!this.{obj::ContainerRenderObjectMixin::_firstChild}.{core2::Object::==}(null)) {
          final sta::StackParentData _firstChildParentData = this.{obj::ContainerRenderObjectMixin::_firstChild}.{obj::RenderObject::parentData} as{TypeError} sta::StackParentData;
          _firstChildParentData.{obj::ContainerParentDataMixin::previousSibling} = child;
        }
        this.{obj::ContainerRenderObjectMixin::_firstChild} = child;
        this.{obj::ContainerRenderObjectMixin::_lastChild}.{core2::Object::==}(null) ?{box3::RenderBox} this.{obj::ContainerRenderObjectMixin::_lastChild} = child : null;
      }
      [...]
    }
    [...]
    abstract forwarding-stub set _firstChild(generic-covariant-impl box3::RenderBox _) → void;

_firstChild is a field
It is read before crashing
When trying to set it, it crashes
There's a forwarding stub on the setter

Thanks @jensjoha.  I think we've identified the problem and a fix is on the way.

Fixed by https://dart-review.googlesource.com/c/sdk/+/46061.


Workflow documentation

It might be useful to writeup a little something describing the workflow in developing algs for NEXT. That is, in the terminal

Use one tab to rsync up
docker_login in another tab, remove containers and docker-compose up
In another tab have the test script that points at the dev machine

I could write something up, does anyone think this could be useful?

+1. This was one of my biggest barriers when starting to develop.
Also, I'd point where to look for documentation on how to develop an algorithm (what functions, what classes, etc). Info.py has the required documentation (I think) but we should expose that and make it easy to find.

Work in progress: https://github.com/nextml/NEXT/wiki/Developer-Guide
Feedback appreciated


making setNativeProps covering more cases

Look in this Animated web implementation:
https://github.com/animatedjs/interactive-docs/blob/gh-pages/Animated.js#L955
they uses React.CSSPropertyOperations.setValueForStyles which allows to set a style. I think we need to use it with the internal react-web preprocessor instead of current setNativeProps implementation.
see also notes in https://github.com/gre/react-web/commit/91ab4100fbd81f49aced3ef151c63af8b324c2c0

Wrap setValueForStyles in setNativeProps now. https://github.com/taobaofed/react-web/blob/master/Libraries/Utilties/setNativeProps.web.js#L33

I think you also need to call extendProperties in order to get full React Native style feature (like transform style)
Also i'm not sure if the convertTransform is required now.
After that, we can enable back the Animated code (that I have commented out) and hopefully we should have functional and faster animations :)


[Task]: Use GCP-BOM to manage google cloud dependencies in sdks/java/extensions/ml

What needs to happen?
Currently https://github.com/apache/beam/blob/master/sdks/java/extensions/ml/build.gradle has hard coded cloud dependencies. We should use gcp-bom to manage these dependencies, in alignment with other beam modules.
Issue Priority
Priority: 2 (default / most normal work should be filed as P2)
Issue Components

[ ] Component: Python SDK
[X] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam YAML
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

There is at least a known breaking change from google-cloud-recommendations-ai needs to be resolved:
https://github.com/googleapis/google-cloud-java/commit/7c866001585563cd673b0bb33a567fd549cc483d changed return type of predictionServiceClient.predict.iterateAll from PredictionResult to Entry<String, Value>


Elevation

It would be nice if we could set elevation for the progress dialog(Like a Card())

There is still lots of work to be done of progress widget, it will come soon...


Simplified fix for infinite recursion in truncateDeep

Continues #202 and #207. Thanks to @omniroot and @jacobmarshall for getting this started.
I've simplified the implementation here to be more consistent with our handling of metaData objects in other parts of bugsnag-js and sidestep around some of the issues uncovered in the prior PRs. Also added a slightly more comprehensive test case.

You are literally Jesus 🙌


$store.set() not triggering the fetcher store

I have a fetcher that has a dependent value on another store.
const [createFetcherStore, createMutatorStore] = nanoquery({
    fetcher: async (...keys: (string | number)[]) => {
      const methodName = keys[0] as keyof Instance['notification'];
      if (methodName === 'get') {
        console.log('page no is...', keys[1]);
        return instance.notification.get({
          pageNo: keys[1] as number,
          limit: 3,
        });
      }
    },
  });

  const $currentPage = atom(1);
  const $notificationStore = createFetcherStore<Notification>([
    'get',
    $currentPage,
  ]);

I have a function in vanilla js loadMore()
    const loadMore = async () => {
     $currentPage.set($currentPage.get() + 1);
    };

I am trying to use these in vanilla js using the listen().
But calling loadMore() is not triggering the $notificationStore. Why?
Shouldn't the $currentPage store change trigger the $notificationStore ?

Hey there, @hemandev!
The reactivity on the library side works (and it's pretty thoroughly tested as well!). Vanilla or not, all framework libraries essentially wrap .listen with framework-specific memoization, like in @nanostores/react.
And, most probably, it's not a reactivity issue in nanostores as well, as the code that sets the Promise result value is extremely straightforward.
The issue with your code, as I think, lies in what instance.notification.get function returns, but without the actual implementation details I can't point to an exact issue.
Can you try to come up with an isolated reproduction case on Stackblitz?

Thanks for the quick response @dkzlv.
I was able to spin up a basic repro sandbox here. Would you mind taking a look?
https://codesandbox.io/p/sandbox/silly-chandrasekhar-ng2tkg
My expectation is that the subscribe() will get called with the new todo values on calling loadMore()

@hemandev Hm, yeah, the issue is in onNotify hook (if you comment it out and change $todo?.data for $todo.value?.data, all works as expected), but I don't know exactly why. I'll keep the issue open and see what my cause it either in query or in core.

Yeah, that did fix it.
Unfortunately, I was using onNotify to keep appending all the fetched todos to another store.
Let me see if I can figure another way to do it. Thanks again.

@hemandev onSet definitely works.

I tried with onSet first. But it was not getting triggered always. You can try in this same sandbox.
It calls twice, {loading: false}, {loading: true, data: }` and stops.
It never called the 3rd time with the resolved value.

@hemandev Ok, I managed to pinpoint the issue, but I don't know why that happens.
Both onNotify and onSet work, but you need to either use $todo.value in onNotify or destructure newValue from payload in onSet like in this example. For some reason using .get() breaks all of this thing, even though it's basically calling .value.

Yep, that is working 🎉


chore(npm): Update dependencies

Updates dependencies, no major breaking changes
Image changes seem related to resolution changes on IE SauceLabs not actual issues

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[UPDATE] Capes 1.5.3 (1.20.4 MAX)> Capes (1.20.5+)

CurseForge link
No response
CurseForge Mod Distribution
Unknown
Modrinth link
https://modrinth.com/mod/capes
Source/other link
No response
Mod file size
75.45 KiB
License
(any other license)
What it does
Crashes instanly on clicking the button in Skin Customization
Why should it be in the modpack
It already is
Why shouldn't it be in the modpack
Idk
Additional details
No response

Yep, will be done with the next update.

Thanks!


Refreshing vs Reloading

I have a single page checkout, each section of the checkout is a component and each component triggers a refresh on subsequent components when submitted.
For example checkout.twig contains:
{{ sprig('shop/_components/checkout/form-address.twig', {}, {'id': 'form-details'}) }}
{{ sprig('shop/_components/checkout/form-delivery.twig', {}, {'id': 'form-delivery'}) }}

Then form-address.twig contains:
<form
  sprig
  s-method="post"
  s-action="commerce/cart/update-cart"
  s-indicator="#form-details">
    {{ actionInput('commerce/cart/update-cart') }}
    [.. address fields ..]
 </form>

 {% if sprig.isRequest %}
  {% tag 'script' %}
    htmx.trigger('#form-delivery', 'refresh');
  {% endtag %}
{% endif %}

Finally form-delivery.twig contains:
<form
  sprig
  s-method="post"
  s-action="commerce/cart/update-cart"
  s-trigger="change"
  s-indicator="#form-delivery">
    {{ actionInput('commerce/cart/update-cart') }}
    [.. options that depend on what's submitted in form-address.twig ..]
</form>

I assumed that the refresh event was just reloading the component but if I submit form-address I get post data back from form-delivery component after it refreshes. So have I just misunderstood what the refresh event does?

Nope! It's my own fault. Of course I find it once I post a question!

No, your assumption sounds correct. I’m not quite following what is not working correctly, though. Can you please clarify?

I thought that might not be clear. So lets say form-delivery.twig has a field and some twig to display the value of the field when the form is submitted (checkout.twig and form-address.twig remain the same):
<form
  sprig
  s-method="post"
  s-action="commerce/cart/update-cart"
  s-trigger="change"
  s-indicator="#form-delivery">
    {{ tag('input', {
      type: 'hidden',
      name: 'selectDelivery',
      value: 1
    }) }}
</form>
{{ craft.app.request.param('selectMethod') }}

When the page is loaded nothing is displayed for form-delivery.
When form-details is submitted, it triggers a refresh on form-delivery and once it's reloaded a 1 is displayed.
Essentially it looks like the refresh method on the component is triggering the form.
(I should add this is Craft 3)

When a component is refreshed, all input fields are submitted as variables. From the docs:

The values of all input fields (including textarea and select fields) in the component will automatically become available as template variables.

https://putyourlightson.com/plugins/sprig#how-it-works
Coincidentally, I’m giving a Sprig training session tomorrow on component variables, see https://putyourlightson.com/sprig/training

Ah! Somehow I'd never noticed that detail. Thank you.
So just one question then @bencroker – from within my form-delivery component is there a way that I can tell if the form was submitted rather than the component refreshed?
I want to run some twig code after the form has been submitted but not when it's been refreshed.

The form will submit via a POST request, whereas a refresh with a GET request, so you could check against that.


Slight difference between isFQDN in Validator.js and IsFqdn in Validator?

Whilst looking at the source for IsFqdn in the C# project, I noticed a small difference where it tests for "--" at the end of the method.
In the Javascript function, validator.isFQDN it has:
part[part.length - 1] === '-'
but in the C# project, it has:
copy.EndsWith("--")
Should this instead be:
copy.EndsWith("-")
With only one hyphen?

I believe @ledbutter wrote the implementation for this method. @ledbutter maybe you could take a look @ this?
@s-moon, I wonder, are the tests the same? If yes, this is likely a non-issue.
(I will investigate further myself if noone else wants to - I am afk at the moment)

With or without the change to the double-hyphen, the tests ran perfectly. But, I don't believe there is specific test for that failure case, as far as I can see, so it would anyway.
Test cases on Validator.js match your C# version.


Remove the scale argument from Run

Now the given scale is ignored on gomobile-build mode, which I found was useful. On the contrary, I fond that the examples screen scale was too big for mobile browsers. It is not impossible to estimate the appropriate scale ahead, but the example code would be a little more complex
On browsers and mobiles, as we know the outside screen size, it would be enough to scale the game screen with the outer screen.
For gomobile-bind mode, Note that we'd need to pass the outside screen's size.

SetScreenScale should be still available on desktops if needed.

https://github.com/hajimehoshi/ebiten/issues/960 tries to break backward compatibility in v1. I think this is acceptable...

#943 would deprecate this scaling notions.


translate files of website.

I don't know if have any files I didn't translate, so please tell me if  have some files need to translate~

Thanks! I'll take a look for additional files once I merge all pull requests.


Bug Report: The "monster" (not to be mistaken with "monster-christmas") assets crash on any other song other than it's own.

I kind of discovered this over how lazy I am, I didn't want to draw over two PNG files of the same character I was going to mod into the game, so yeah, there's that. Correct me if this has already been fixed, I don't have the latest version.

Already fixed in the latest source/nightly.

Well.. he's called monster for a reason ¯_(ツ)_/¯


dotnet core support

Update to:

build against netstandard 1.3 (lowest version of net standard required)
build against net45
added csharpbuild.cmd (similar to cppbuild.cmd) to restore, build and run tests
corrected nuspec for multiple dotnet versions

Thanks! It would be good to get a review from @odeheurles or @billsegall on this.

The patch addresses something on the roadmap and I'd love to see it integrated.
I tried the following:
git clone git@github.com:real-logic/simple-binary-encoding.git
cd simple-binary-encoding
git fetch origin pull/456/head:dn
git checkout dn
gradlew
gradlew generatecsharpcodecs
cd csharp
csharpbuild.cmd
The build then proceeds until I see:
error : This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them.  For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is ..\packages\MSTest.TestAdapter.1.1.17\build\net45\MSTest.TestAdapter.props
Once I've opened the solution and built from there then csharpbuild.cmd works.
I think we can accept the PR and  look to fix the build script from clean checkout separately.
Bill.

Let me fix that, it should really work.

Now builds from clean checkout.

Thanks


[AutoRelease] t2-support-2022-10-28-96128(Do not merge)

https://github.com/Azure/sdk-release-request/issues/3320
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=1385

issue link:https://github.com/Azure/sdk-release-request/issues/3320


Errors installing dependencies for development

When installing the node_modules for this project, there were several errors thrown during the npm install:
npm WARN deprecated<EMAIL_ADDRESS>graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to<EMAIL_ADDRESS>as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained. Upgrade to<EMAIL_ADDRESS>npm WARN deprecated<EMAIL_ADDRESS>graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to<EMAIL_ADDRESS>as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated<EMAIL_ADDRESS>graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to<EMAIL_ADDRESS>as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated<EMAIL_ADDRESS>cross-spawn no longer requires a build toolchain, use it instead!
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g

Then, when bower install in run, this is thrown:
(node:8568) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.

Finally, gulp fails as well:
(node:8632) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
module.js:442
    throw err;
    ^

Error: Cannot find module 'gulp-include'
    at Function.Module._resolveFilename (module.js:440:15)
    at Function.Module._load (module.js:388:25)
    at Module.require (module.js:468:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/Users/edensg/Desktop/Desktop/GCVI/McCrae Day/styleguide/cutestrap/gulpfile.js:10:21)
    at Module._compile (module.js:541:32)
    at Object.Module._extensions..js (module.js:550:10)
    at Module.load (module.js:458:32)
    at tryModuleLoad (module.js:417:12)
    at Function.Module._load (module.js:409:3)

I'm not sure how much of this you have control over and how much is just a result of dependencies and their messiness. Would it worth trying other (older) node versions perhaps, or are there other things that should be installed (locally or globally)?

I think the four things I have installed globally are node, npm, bower, and kss-node (npm install -g kss). What OS are you on and what output do you get when you run $ node -v && npm -v && bower -v && kss-node --version?
I'm on OSX 10.11.4 and these are my results.
v5.11.0
3.8.6
1.4.1
2.1.0

I'm on OS X 10.11.5. Here are my results:
v6.2.0
3.8.9
1.7.9
The "kss-node" tool name is deprecated; use "kss" instead.

However, kss --version reveals I've got version 3.0.0-beta.12. I'll try uninstalling it and installing 2.1.0.

I managed to get it working, but I needed to install version 2 of kss, and I also needed to install gulp-include. These are things that could be included in the package.json.

#2 should fix this.

@EdenSG Thanks! Merged in your PR!

👍


Major Angular2 update

The version in your repository was creating a API_Service that produced like 100 errors in the typescript validator, when I tried to create a service for our api. So I improved it!
The main changes are (from big to small):

[X] Working with angular2 in the @angular/core and @angular/http namespace.
[X] A method getDefaultHeaders() to set headers on each API call.
[X] Returning an Observable<returnType> instead of the request.
[X] Set the default domain if the basePath is empty.
[X] Array of primitive types were reporting as 'array', as fixed here
[X] Also read (and use) the summary of calls.
[X] The api info can be empty, this should be checked before reading swagger.info.description
[X] Added a line of code on how to install this package right from the repository, but still use it as a globally installed command line tool.

This version is also available on NPM @svrooij/angular2-swagger-client-generator in my own namespace. Can you also update the non-namespaced version?

Hello Stephan, thank you for all your hard work on this repository/project.


tests: kernel: timer_api: align tick for duration period test

Add a k_usleep() in test_timer_duration_period test to align ticks
before starting the timer. This fixes some rare off-by-1 failures.
Signed-off-by: Daniel Leung<EMAIL_ADDRESS>

@dcpleung  was this fixing some open bug?

It is to fix the test on an internal platform, due to their weird clock driver.


[proposal]: move did providers to libs

After an internal discussion, we suggest moving our implemented did providers to libs and defining them as each their own package. This way, we can release and publish them to npm individually.

#186 will close this issue for did ebsi provider. Next up is moving the did key provider, but we opened a different issue at #185.


fix(e2e): fix BLS-related failures

Part of #3720
e2e tests require a method that generates a private key deterministically (from a secret). Without such method, is it not possible for the "tests" step of the e2e runner to recreate the node structure as it exists within the runner itself.
Manual nightly runs:

1st try
2nd try, after 53321d4

PR checklist

~[ ] Tests written/updated~
~[ ] Changelog entry added in .changelog (we use unclog to manage our changelog)~
~[ ] Updated relevant documentation (docs/ or spec/) and code comments~

I've reviewed and merged this. Had to fix a couple of tests in the crypto and encoding. @sergio-mena and @melekes please take a look at my commits and see if they made sense.