Internal Server Error for specific search

Current Behavior
When searching for NCIS, trying to open the season list returns "Internal Server Error", but only for the original show. All other NCIS's (and every other show I've tried so far) list the seasons just fine.

Steps to Reproduce (for bugs)

Open Elementum and search for NCIS in the TV Show search
Open NCIS: Los Angeles and it will list the seasons correctly
Open NCIS and it will return the error

Your Environment

Version used: 0.1.83

Operating System and version: Kodi 19.3 on Android TV 9

@mancalm Log file is required.
https://elementum.surge.sh/contribute/log/

@mancalm Log file is required. https://elementum.surge.sh/contribute/log/

2022-01-07 12:44:26.887 T:14597 WARNING : [plugin.video.elementum] 2022/01/07 12:44:25 [Recovery] 2022/01/07 - 12:44:25 panic recovered:
2022-01-07 12:44:26.891 T:14597 WARNING : [plugin.video.elementum] runtime error: invalid memory address or nil pointer dereference
2022-01-07 12:44:26.892 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/runtime/panic.go:212 (0xba23f28b)
2022-01-07 12:44:26.894 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/runtime/signal_unix.go:734 (0xba25b7b3)
2022-01-07 12:44:26.895 T:14597 WARNING : [plugin.video.elementum] /var/lib/jenkins/workspace/elementum/tmdb/season.go:300 (0xba9e7940)
2022-01-07 12:44:26.897 T:14597 WARNING : [plugin.video.elementum] /var/lib/jenkins/workspace/elementum/tmdb/season.go:197 (0xba9e6fef)
2022-01-07 12:44:26.899 T:14597 WARNING : [plugin.video.elementum] /var/lib/jenkins/workspace/elementum/tmdb/season.go:126 (0xba9e5f17)
2022-01-07 12:44:26.901 T:14597 WARNING : [plugin.video.elementum] /var/lib/jenkins/workspace/elementum/api/shows.go:397 (0xbab2d113)
2022-01-07 12:44:26.902 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/context.go:165 (0xbab4cf77)
2022-01-07 12:44:26.903 T:14597 WARNING : [plugin.video.elementum] /var/lib/jenkins/workspace/elementum/api/routes.go:42 (0xbab4cf54)
2022-01-07 12:44:26.904 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/context.go:165 (0xba77f107)
2022-01-07 12:44:26.905 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/logger.go:241 (0xba77f0e4)
2022-01-07 12:44:26.907 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/context.go:165 (0xba77fddf)
2022-01-07 12:44:26.908 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/recovery.go:99 (0xba77fdbc)
2022-01-07 12:44:26.909 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/context.go:165 (0xba7768eb)
2022-01-07 12:44:26.911 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/gin.go:489 (0xba7768c8)
2022-01-07 12:44:26.913 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/gin.go:445 (0xba77642b)
2022-01-07 12:44:26.916 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/net/http/server.go:2448 (0xba4d2b67)
2022-01-07 12:44:26.917 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/net/http/server.go:2887 (0xba4d3e77)
2022-01-07 12:44:26.918 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/net/http/server.go:1952 (0xba4cfd63)
2022-01-07 12:44:26.920 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/runtime/asm_arm.s:841 (0xba27cc23)
2022-01-07 12:44:26.921 T:14597 WARNING : [plugin.video.elementum]
2022-01-07 12:44:26.922 T:14597 WARNING : [plugin.video.elementum]
2022-01-07 12:44:28.008 T:14597 WARNING : Skipped 1 duplicate messages..
2022-01-07 12:44:28.008 T:14597 WARNING : [plugin.video.elementum] 2022/01/07 12:44:26 [Recovery] 2022/01/07 - 12:44:26 panic recovered:
2022-01-07 12:44:28.009 T:14597 WARNING : [plugin.video.elementum] runtime error: invalid memory address or nil pointer dereference
2022-01-07 12:44:28.010 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/runtime/panic.go:212 (0xba23f28b)
2022-01-07 12:44:28.011 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/runtime/signal_unix.go:734 (0xba25b7b3)
2022-01-07 12:44:28.012 T:14597 WARNING : [plugin.video.elementum] /var/lib/jenkins/workspace/elementum/tmdb/season.go:300 (0xba9e7940)
2022-01-07 12:44:28.015 T:14597 WARNING : [plugin.video.elementum] /var/lib/jenkins/workspace/elementum/tmdb/season.go:197 (0xba9e6fef)
2022-01-07 12:44:28.017 T:14597 WARNING : [plugin.video.elementum] /var/lib/jenkins/workspace/elementum/tmdb/season.go:126 (0xba9e5f17)
2022-01-07 12:44:28.018 T:14597 WARNING : [plugin.video.elementum] /var/lib/jenkins/workspace/elementum/api/shows.go:397 (0xbab2d113)
2022-01-07 12:44:28.019 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/context.go:165 (0xbab4cf77)
2022-01-07 12:44:28.020 T:14597 WARNING : [plugin.video.elementum] /var/lib/jenkins/workspace/elementum/api/routes.go:42 (0xbab4cf54)
2022-01-07 12:44:28.021 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/context.go:165 (0xba77f107)
2022-01-07 12:44:28.023 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/logger.go:241 (0xba77f0e4)
2022-01-07 12:44:28.024 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/context.go:165 (0xba77fddf)
2022-01-07 12:44:28.026 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/recovery.go:99 (0xba77fdbc)
2022-01-07 12:44:28.027 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/context.go:165 (0xba7768eb)
2022-01-07 12:44:28.028 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/gin.go:489 (0xba7768c8)
2022-01-07 12:44:28.030 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/gin.go:445 (0xba77642b)
2022-01-07 12:44:28.030 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/net/http/server.go:2448 (0xba4d2b67)
2022-01-07 12:44:28.032 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/net/http/server.go:2887 (0xba4d3e77)
2022-01-07 12:44:28.033 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/net/http/server.go:1952 (0xba4cfd63)
2022-01-07 12:44:28.034 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/runtime/asm_arm.s:841 (0xba27cc23)
2022-01-07 12:44:28.035 T:14597 WARNING : [plugin.video.elementum]
2022-01-07 12:44:28.036 T:14597 WARNING : [plugin.video.elementum]
2022-01-07 12:44:29.134 T:14597 WARNING : Skipped 1 duplicate messages..
2022-01-07 12:44:29.134 T:14597 WARNING : [plugin.video.elementum] 2022/01/07 12:44:28 [Recovery] 2022/01/07 - 12:44:28 panic recovered:
2022-01-07 12:44:29.136 T:14597 WARNING : [plugin.video.elementum] runtime error: invalid memory address or nil pointer dereference
2022-01-07 12:44:29.137 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/runtime/panic.go:212 (0xba23f28b)
2022-01-07 12:44:29.138 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/runtime/signal_unix.go:734 (0xba25b7b3)
2022-01-07 12:44:29.140 T:14597 WARNING : [plugin.video.elementum] /var/lib/jenkins/workspace/elementum/tmdb/season.go:300 (0xba9e7940)
2022-01-07 12:44:29.141 T:14597 WARNING : [plugin.video.elementum] /var/lib/jenkins/workspace/elementum/tmdb/season.go:197 (0xba9e6fef)
2022-01-07 12:44:29.146 T:14597 WARNING : [plugin.video.elementum] /var/lib/jenkins/workspace/elementum/tmdb/season.go:126 (0xba9e5f17)
2022-01-07 12:44:29.147 T:14597 WARNING : [plugin.video.elementum] /var/lib/jenkins/workspace/elementum/api/shows.go:397 (0xbab2d113)
2022-01-07 12:44:29.149 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/context.go:165 (0xbab4cf77)
2022-01-07 12:44:29.152 T:14597 WARNING : [plugin.video.elementum] /var/lib/jenkins/workspace/elementum/api/routes.go:42 (0xbab4cf54)
2022-01-07 12:44:29.155 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/context.go:165 (0xba77f107)
2022-01-07 12:44:29.156 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/logger.go:241 (0xba77f0e4)
2022-01-07 12:44:29.164 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/context.go:165 (0xba77fddf)
2022-01-07 12:44:29.168 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/recovery.go:99 (0xba77fdbc)
2022-01-07 12:44:29.170 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/context.go:165 (0xba7768eb)
2022-01-07 12:44:29.172 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/gin.go:489 (0xba7768c8)
2022-01-07 12:44:29.174 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/gin.go:445 (0xba77642b)
2022-01-07 12:44:29.174 T:16762    INFO : CPythonInvoker(21, /storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/addons/plugin.video.elementum/navigation.py): script successfully run
2022-01-07 12:44:29.352 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/net/http/server.go:2448 (0xba4d2b67)
2022-01-07 12:44:29.354 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/net/http/server.go:2887 (0xba4d3e77)
2022-01-07 12:44:29.355 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/net/http/server.go:1952 (0xba4cfd63)
2022-01-07 12:44:29.679 T:16762    INFO : Python interpreter stopped
2022-01-07 12:44:29.681 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/runtime/asm_arm.s:841 (0xba27cc23)
2022-01-07 12:44:29.687 T:14597 WARNING : [plugin.video.elementum]
2022-01-07 12:44:29.689 T:14597 WARNING : [plugin.video.elementum]
2022-01-07 12:44:29.694 T:16761   ERROR : GetDirectory - Error getting plugin://plugin.video.elementum/show/4614/seasons
2022-01-07 12:44:29.702 T:14538   ERROR : CGUIMediaWindow::GetDirectory(plugin://plugin.video.elementum/show/4614/seasons) failed
2022-01-07 12:44:31.734 T:16766    INFO : initializing python engine.
2022-01-07 12:44:32.957 T:14597 WARNING : [plugin.video.elementum]
2022-01-07 12:44:32.959 T:14597 WARNING : [plugin.video.elementum] 2022/01/07 12:44:29 [Recovery] 2022/01/07 - 12:44:29 panic recovered:
2022-01-07 12:44:32.973 T:14597 WARNING : [plugin.video.elementum] runtime error: invalid memory address or nil pointer dereference
2022-01-07 12:44:32.984 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/runtime/panic.go:212 (0xba23f28b)
2022-01-07 12:44:32.996 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/runtime/signal_unix.go:734 (0xba25b7b3)
2022-01-07 12:44:33.008 T:14597 WARNING : [plugin.video.elementum] /var/lib/jenkins/workspace/elementum/tmdb/season.go:300 (0xba9e7940)
2022-01-07 12:44:33.021 T:14597 WARNING : [plugin.video.elementum] /var/lib/jenkins/workspace/elementum/tmdb/season.go:197 (0xba9e6fef)
2022-01-07 12:44:33.025 T:14597 WARNING : [plugin.video.elementum] /var/lib/jenkins/workspace/elementum/tmdb/season.go:126 (0xba9e5f17)
2022-01-07 12:44:33.027 T:14597 WARNING : [plugin.video.elementum] /var/lib/jenkins/workspace/elementum/api/shows.go:397 (0xbab2d113)
2022-01-07 12:44:33.028 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/context.go:165 (0xbab4cf77)
2022-01-07 12:44:33.030 T:14597 WARNING : [plugin.video.elementum] /var/lib/jenkins/workspace/elementum/api/routes.go:42 (0xbab4cf54)
2022-01-07 12:44:33.031 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/context.go:165 (0xba77f107)
2022-01-07 12:44:33.033 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/logger.go:241 (0xba77f0e4)
2022-01-07 12:44:33.036 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/context.go:165 (0xba77fddf)
2022-01-07 12:44:33.037 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/recovery.go:99 (0xba77fdbc)
2022-01-07 12:44:33.038 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/context.go:165 (0xba7768eb)
2022-01-07 12:44:33.039 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/gin.go:489 (0xba7768c8)
2022-01-07 12:44:33.041 T:14597 WARNING : [plugin.video.elementum] /go/pkg/mod/github.com/gin-gonic/gin@v1.7.1/gin.go:445 (0xba77642b)
2022-01-07 12:44:33.042 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/net/http/server.go:2448 (0xba4d2b67)
2022-01-07 12:44:33.043 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/net/http/server.go:2887 (0xba4d3e77)
2022-01-07 12:44:33.044 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/net/http/server.go:1952 (0xba4cfd63)
2022-01-07 12:44:33.045 T:14597 WARNING : [plugin.video.elementum] /usr/arm-linux-androideabi/go/src/runtime/asm_arm.s:841 (0xba27cc23)
2022-01-07 12:44:33.046 T:14597 WARNING : [plugin.video.elementum]
2022-01-07 12:44:33.048 T:14597 WARNING : [plugin.video.elementum] [GIN] 2022/01/07 - 12:44:32 | 200 |   26.061833ms |       <IP_ADDRESS> | GET      "/show/17610/seasons?doresume=false"
2022-01-07 12:44:33.051 T:16766   ERROR : NEWADDON Unknown Video Info Key "dbtype"
2022-01-07 12:44:33.199 T:16766    INFO : Skipped 13 duplicate messages..
2022-01-07 12:44:33.199 T:16766    INFO : CPythonInvoker(22, /storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/addons/plugin.video.elementum/navigation.py): script successfully run
2022-01-07 12:44:33.698 T:16766    INFO : Python interpreter stopped
2022-01-07 12:44:43.289 T:16775    INFO : initializing python engine.
2022-01-07 12:44:44.478 T:14597 WARNING : [plugin.video.elementum] [GIN] 2022/01/07 - 12:44:44 | 200 |   17.473417ms |       <IP_ADDRESS> | GET      "/settings/plugin.video.elementum?doresume=false"
2022-01-07 12:44:44.485 T:16775    INFO : CPythonInvoker(23, /storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/addons/plugin.video.elementum/navigation.py): script successfully run
2022-01-07 12:44:44.924 T:16775    INFO : Python interpreter stopped
2022-01-07 12:44:44.934 T:16774   ERROR : GetDirectory - Error getting plugin://plugin.video.elementum/settings/plugin.video.elementum
2022-01-07 12:44:56.674 T:16817    INFO : initializing python engine.
2022-01-07 12:44:57.975 T:14597 WARNING : [plugin.video.elementum] INFO  api          ▶ Pastebin         Requesting http://<IP_ADDRESS>:65220/debug/bundle before uploading to pastebin
2022-01-07 12:44:58.000 T:14597 WARNING : [plugin.video.elementum] [GIN] 2022/01/07 - 12:44:57 | 200 |      33.334µs |       <IP_ADDRESS> | GET      "/info"
I used the log function in Elementum settings, is this enough?

@mancalm
same as https://github.com/elgatito/plugin.video.elementum/issues/843 and https://github.com/elgatito/plugin.video.elementum/issues/846
would be better to see whole log (when you upload log via elementym it gives you a link, or you can upload log file manually from file system).
but my guess that you use non-english locale in kodi and with new updates of kodi on some shows it gives some incorrect info that leads to crash.
you can disable "Show number of unwatched episodes in Shows/Seasons" ("Appearance" tab) as temporary solution.
(or change kodi locale to english, which is probably less convenient)

@mancalm
same as https://github.com/elgatito/plugin.video.elementum/issues/843 and https://github.com/elgatito/plugin.video.elementum/issues/846
would be better to see whole log (when you upload log via elementym it gives you a link, or you can upload log file manually from file system).
but my guess that you use non-english locale in kodi and with new updates of kodi on some shows it gives some incorrect info that leads to crash.
you can disable "Show number of unwatched episodes in Shows/Seasons" ("Appearance" tab) as temporary solution.
(or change kodi locale to english, which is probably less convenient)

You are right about me not using English locale. But disabling the number of unwatched episodes did the trick, thanks!

@mancalm which locale do you use?
i can't reproduce this bug with my "language".

@mancalm which locale do you use?
i can't reproduce this bug with my "language".

By locale you mean the language and region settings, right?
I use Portuguese and Portugal, respectively. However, I tried setting English and Central Europe and it didn't fix it...
I reproduced the bug in one Android TV (Phillips) and a Xiaomi Mi Box S, both had the same issue.

@mancalm
maybe you have some specific settings in elementum - could you please provide full log file?
https://elementum.surge.sh/contribute/log/
it will upload log and give you a link.
or you can manually copy it from system and remove all non-elementum info if you want. (your first log file does not have all the elementum related info).

@mancalm
maybe you have some specific settings in elementum - could you please provide full log file?
https://elementum.surge.sh/contribute/log/
it will upload log and give you a link.
or you can manually copy it from system and remove all non-elementum info if you want. (your first log file does not have all the elementum related info).

Now it seems I can't reproduce the bug any longer in either TV.
I enabled "Show number of unwatched episodes in Shows/Seasons" to get the error again since that's what seems to have fixed the problem in both TVs, but I can still open the seasons list.

@mancalm
could you please try to clear elementum's cache?
since elementum caches info about shows.
in settings on last tab - clear tmdb and trakt cache.

@mancalm
could you please try to clear elementum's cache?
since elementum caches info about shows.
in settings on last tab - clear tmdb and trakt cache.

Cleared search history, torrent history, cache, Trakt cache and TMDB cache and then searched for NCIS. It took a while to open the seasons list but still managed to do it, no error.

i guess you tried with "Portuguese and Portugal", right?
this is strange bug then. hard to chase it down :-(
thank you.

@mancalm Try to update to version 0.1.84.

i guess you tried with "Portuguese and Portugal", right?
this is strange bug then. hard to chase it down :-(
thank you.

Thank you for tour help!

@mancalm Try to update to version 0.1.84.

Did that and had to revert back to 0.1.83, with the new version the plugin wouldn't run.

@mancalm
there was small bug - https://github.com/elgatito/plugin.video.elementum/issues/859
new version should work.

@elgatito i guess this one also can be closed since user was not able to reproduce the bug (and i also was not able to) and you already make a fix that can potentially fix this issue (https://github.com/elgatito/elementum/commit/9666a30739463dfd5bcc1e532e13400673852e9c).
thanks for the fix!


LSP Node Client: (testing servers, proxy, other platforms support)

The default Microsoft's Node LSP Client depends & delegates directly to vscode extension host API: https://github.com/Microsoft/vscode-languageserver-node/tree/master/client
However, the fork here https://github.com/TypeFox/vscode-languageserver-node/tree/master/client - or npm vscode-base-languageclient  abstracts away vscode APIs - enabling it to be used in a Node environment to:

Test LSP servers.
Be used to proxy / route LSP messages to other servers.
Be integrated in other platforms / editors.
Allow remotable implementation - e.g. remote extension host API, enabling VSCode extensions to run remotely, on a devserver or docker container.

There's a big value in adopting such abstraction on the default LSP client as it keeps pace with LSP support and integration points.

@mostafaeweda I very much agree with what you have stated here. However, I am not sure what you are asking for in this issue. If you are asking for changes to the Microsoft/vscode-languageserver-node project, perhaps you should open an issue there instead? Or were you just trying to inform a wider audience about TypeFox's fork?

https://github.com/Microsoft/vscode-languageserver-node/issues/365


Add Arlo as medium and AZMVDNOW.gov as impossible

Arlo provides security cameras and cloud video storage of camera footage.

Thanks for your contribution!


Chris Henderson's Code Suggestions for CRL Linting Infrastructure

Thank you for making this PR! It definitely is a great way to collaborate on larger changes such as this.
All of these changes look ideal. And understood on LinterLookup - I'll handle that in a future commit.
We also probably need to discuss and figure out how we want to handle the situation with zcrypto. There's a couple of solutions we can take there, but I think none of them are ideal from my PoV.


Windows XP wallet

Id like to see a 32 bit build of the wallet that will run on XP

windows xp is unsupported. sorry.


VS Code extension doesn't work with v1.77.1 (March 2023)

Out of the blue, intellisense stopped working even though I installed the twind and deno extensions in VS Code. I tried it with VS Code v1.76 (February 2023) and it works perfectly
VS Code: 1.77.1
Deno: 1.32.3
Fresh: 1.1.5
Twind: 0.16.19
Initialized workspace and cached libraries: Yes

+1, extension is unusable for me at the moment

+1, same with me, works when I downgrade the version of vscode

Use @twind/preset-tailwind with Tailwind CSS IntelliSense and an empty tailwind.config.ts.

This is a separate VSCode Twind intellisense extension that I developed, which only supports v1. It is still a work in progress. If you're interested, feel free to check it out.


next can not be called on a TarFile object

Addendum #556 (commit 5143a76)

Huh, I'm not sure how that re-broke? But, thank you!


MarkerView with TouchableOpacity (and other Touchable) - onPress Not Triggering on Android

I have been using MapLibreGL.MarkerView successfully for some time, and the press events from child elements worked fine on both iOS and Android. However, after upgrading my project to Expo SDK 52, the MarkerView on Android no longer triggers the onPress event. Tapping the marker appears to do nothing, even though the same code worked prior to the upgrade.  I haven't fully tested on iOS yet.
Steps to Trigger Behavior

Create new project using Expo SDK 52.
Create a screen containing MabLibre map and a MapLibreGL.MarkerView containing TouchableOpacity element with onPress.
Run development build and tap marker.

Link to Minimal Reproducible Example
https://github.com/stharvey/maplibre-test
Expected Behavior
Tapping the marker should trigger the onPress callback and log "Marker clicked" to the console.
Actual Behavior
On Android, tapping the marker does nothing.
Environment

Platform: Android
OS version: Android 14
Device type: Pixel 6 Pro
Emulator or Simulator: Real device
Development OS: MacOS 15.1.1
@maplibre/maplibre-react-native Version: 10.0.0-alpha.28
react-native Version: 0.76.5
expo Version: 52.0.18

Thanks for the report, can you also reproduce with the latest beta version? Are you using the old or new architecture?

Sorry, I should have said - this is with the new architecture.
I haven't tried with new architecture disabled and I haven't tried with beta - I'll try now.

Here is what I have found from testing with old and new architecture on 10.0.0-alpha.28 and 10.0.0-beta.8:
10.0.0-alpha.28 with old architecture: no problem
10.0.0-alpha.28 with new architecture: error as described above
10.0.0-beta.8 with old architecture: no problem
10.0.0-beta.8 with new architecture: error as described above

Did you still only try on Android?

Yes, I'll try on iOS now

Apologies for the delay.  Yes I am seeing the same as above on iOS

I can't reproduce within your repository. You are build your dev client on EAS? Are you using the correct dev clients?
This is how I tried to reproduce:

Checkout your repo
Allow bare workflow build by removing the following keys from app.json:

eas
runtimeVersion
updates

Changepackage.json

Add these scripts:

  "build": "expo prebuild",
  "start": "expo start --dev-client",
  "android": "expo run:android",
  "ios": "expo run:ios"

  - Update version `"@maplibre/maplibre-react-native": "^10.0.0-beta.9",`
- Run `npm run android`

Everything works as expected.

I've also tried within our example app like this, which also works fine:

```tsx
import { MapView, MarkerView } from "@maplibre/maplibre-react-native";
import { StyleSheet, Text, TouchableOpacity } from "react-native";

import { sheet } from "../styles/sheet";

const styles = StyleSheet.create({
  touchable: {
    padding: 16,
    width: 128,
    backgroundColor: "white",
  },
});

export default function BugReport() {
  return (
    <MapView style={sheet.matchParent}>
      <MarkerView coordinate={[0, 0]}>
        <TouchableOpacity
          style={styles.touchable}
          onPress={() => console.log("Marker clicked")}
        >
          <Text>Touchable</Text>
        </TouchableOpacity>
      </MarkerView>
    </MapView>
  );
}

Thanks for taking the time to look into this.
Yes I'm using EAS and I'm building the dev client fresh from the repository linked above.
I'm a bit stumped now - I'm not sure what I should try next - do you have any ideas?

Yes I rebuilt the dev client for each architecture & version permutation.
I'll try building locally and let you know how it goes.

Thanks for clarifications!
If it works for you with the local build, you could also try eas --local and clearing caches on EAS.
It's yet unclear to me, how this could only happen with a EAS build.

Very strange.  I have built my repo locally to Android (@maplibre/maplibre-react-native ^10.0.0-beta.9) and I still experience the same issue.  When tapping the marker the onPress (i.e.  console.log("Marker clicked")) does not execute.

Yes, I get the console.log, very strange. I've only tested on emulator/simulator only. Are you testing on devices?

Yes I've only been testing on real devices

Could you verify, that it's working within emulator/simulator? Thanks!

Ah, yes it does work within simulator.

Have you been able to reproduce the issue on a real device?  Can I provide any further details?

I've been playing around with it and it works (including real devices) using onPressOut instead of onPress

Can confirm the event isn't riggered on Android device.

But I can't reproduce on iOS, not 100% sure if build correctly on new arch.
On Android we might have to do this migration: https://github.com/reactwg/react-native-new-architecture/discussions/154#discussioncomment-9097697.

Actually we might be experiencing this? If I press and drag in the Android emulator I can also reproduce the bug. https://github.com/facebook/react-native/issues/44610#issuecomment-2168252825


prometheus: 2.30.x

Checklist

[x] Checked the nixpkgs master branch
[x] Checked the nixpkgs pull requests

Project name
nix search name:
current version: 2.27.1
desired version: 2.30.3
Notify maintainers
maintainers: @benley @fpletz @globin @WilliButz @Frostman @kalbasit
Note for maintainers
Please tag this issue in your PR.
I'd be happy to contribute somehow, but the build process is kind of weird, so it's probably better for an experienced person to handle this.

Related: #141477

Update was done in the linked PR.


Copy to left section, Copy to right section

What feature do you want to get added on the base engine?
So lately I have been trying to chart Omission but I think a good feature would be to add a feature that lets you copy Left or right section so you don't have to copy a duel section and clear the left or right section.
To test your sight, and reliability, please select the option of what should NOT be requested.
6K+ and stage editor

no

alr nvm


Add a backend to download sources and primary jars and

The maven_jar in Bazel 0.15 doesn't accept source hashes yet even though the documentation indicates that it does.
Add an option to disable strict deps.

Can we split into two PRs?


Windows installation script does not install pixi

I am following the instructions in the README to install pixi on Windows, and the command closes the Powersehll windows, on both Powershell and Powershell with Admin Permissions. This is the output before the windows is closed:
PS C:\WINDOWS\system32> iwr -useb https://raw.githubusercontent.com/prefix-dev/pixi/main/install/install.ps1 | iex
This script will automatically download and install Pixi (latest) for you.
Getting it from this url: https://github.com/prefix-dev/pixi/releases/latest/download/pixi-x86_64-pc-windows-msvc.zip
The binary will be installed into 'C:\Users\STraversaro\AppData\Local\pixi\bin'

I manually removed the try/catch, and the error is:
Expand-Archive : .tmp is not a supported archive file format. .zip is the only supported archive file format.
At C:\Users\STraversaro\test2\install.ps1:35 char:5
+     Expand-Archive -Path $TEMP_FILE -DestinationPath $PIXI_DIR -Force
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (.tmp:String) [Expand-Archive], IOException
    + FullyQualifiedErrorId : NotSupportedArchiveFileExtension,Expand-Archive

Apparently [System.IO.Path]::GetTempFileName() returns a filename that ends with .tmp, and Expand-Archive does not like this.

Thanks for the issue! Fixed it in #152

Thanks for the fix!


Add Presto  inverse_weibull_cdf function

Resolves https://github.com/facebookincubator/velox/issues/5495
This is a follow up for https://github.com/facebookincubator/velox/pull/5760

@wills-feng : Please add the fuzzer output for this function.

There is a on-going discussion about if we need to keep the float test cases in unit test as the result may be different in different time/machine. So still keep it as Draft.
Fuzzer test result.
I20240419 10:19:37.930585 27386811 ExpressionFuzzerVerifier.cpp:183] inverse_weibull_cdf 4125611 100.00% 4424083
I20240419 10:19:37.930603 27386811 ExpressionFuzzerVerifier.cpp:196] ==============================> All stats sorted by number of times the function was chosen
I20240419 10:19:37.930619 27386811 ExpressionFuzzerVerifier.cpp:198] Format: functionName numTimesSelected proportionOfTimesSelected numProcessedRows
I20240419 10:19:37.930635 27386811 ExpressionFuzzerVerifier.cpp:202] inverse_weibull_cdf 4125611 100.00% 4424083
E20240419 10:19:37.930650 27386811 ExpressionFuzzerVerifier.cpp:373] Total iterations: 181904
E20240419 10:19:37.930665 27386811 ExpressionFuzzerVerifier.cpp:374] Total failed: 9420
[==========] Running 0 tests from 0 test suites.
[==========] 0 tests from 0 test suites ran. (0 ms total)
[  PASSED  ] 0 tests.

@aditi-pandit I refer to Presto Java code base to use round($f()) to avoid the different precision issue. Let me know what you think?

@Yuhta, @kagamiori, @kgpai : Please can you help with the review and merge. These are old PRs for the stats functions blocked because of the bugs in the boost library fixed by Jimmy. https://github.com/boostorg/math/pull/1007


Export in older version (0.25.2) and import in newer version (1.2) causes errors like 'avg', 'sum' is an invalid keyword argument for TableColumn

Export the dashboard in an older version and then import in a newer version. The import leads to errors like

'dict' object has no attribute '_sa_instance_state'
'sum' is an invalid keyword argument for TableColumn
'avg' is an invalid keyword argument for TableColumn

How to reproduce the bug

Export dashboard in older version
Import in newer version
Error with the aforementioned log

Hi @DhirajReddy, Could you detail which version of Superset from and to.

I am trying to export the dash boards in 0.25.5 version to version 1.2.
I know that 0.25.2 does not support the versioned export flag. Is there a way around that?

@DhirajReddy you will need to export and import using the same version of Superset. I recommend taking a backup of your metadata and upgrading your 0.25.5 version of Superset to 1.2.0 before exporting and reimporting into your target 1.2.0 instance.

@villebro thanks for the reply. I see that there is a superset db upgrade command, but how do I upgrade to specific version? can I use something like superset db upgrade:2.1

Since this isn't a bug, but rather a compatability/upgrading issue, and it's gone cold for upward of a year, I'll close this as "not planned". We're also not supporting the stated versions of Superset anymore, currently just 1.5.x and 2.0.x. @DhirajReddy if you are still facing this issue, ping me on Slack and we'll try to get you pointed in the right direction.

Hi @rusackas @DhirajReddy
Did we get a working solution for this issue?


Discord Server

I noticed that there is no Discord Server for this project. I think it would be very beneficial because it could be used for support and stuff, to keep the issues and stuff decluttered from repeated questions. If there is one already, please link me to it. Thanks!

I agree, if you need help to create and manage one. I can run it for you and give you administrator.

I don't think I have the time to manage a discord server. Discussions tab in GitHub should do the work.

Sadge, okay. It could reach more users, marketing-wise tbh.


Getting at Outside Context?

Hi Friends,
I'm trying to access a function {{#reverse}} inside of a list loop {{#badges.accepted}} like so:

      {{/badges.accepted}}```

It's not working, the `reverse` function is never called, and I think it's because it's trying to find a reverse attribute within the context of the `badges.accepted` loop.  Is there a way to access the outside context?  Something like (totally making this up) `{{#../reverse}}`?  I'm new to mustache, so this might not actually be a Hogan issue, but thought I'd check.  I looked for an IRC channel, or some other place to ask this, but couldn't find anything handy.

Thanks,
Chris

I think this is a bug with context lookup in the presence of dot syntax sections. Each segment should be pushed onto the context stack, not just the last one.

Hmmm, yeah I can get this to work fine outside of the loop.  I broke it down a bit to eliminate any outside dot syntax parts, and I'm still having issues.  The revised code:
    {{#badges}}

Pending

      {{#pending}}

      {{/pending}}

    {{/badges}}

Is this something that you guys think is a quick fix?  I have a potential work around, but if it's something you think you can fix quickly, that would be cool, as I think the nesting is a cleaner solution to my issue.  Either way...I'm good.  Thanks!

Could you give an example context object? (the first argument to render)

Ah, gotcha.  Reverse (and other helpers) are added here: https://github.com/cmcavoy/openbadges/blob/33-templates/lib/hogan-express.js  the actual reverse code is in this module: https://github.com/cmcavoy/openbadges/blob/33-templates/lib/router.js


TLS1.3: Add write client Certificate and CertificateVerify

Add write client CertificateVerify handler.
Preceding PRs: #5080, #5472
Status
IN DEVELOPMENT

Dirty work

ABI-API-checking FAIL due to #5472


run and debug error

Type: Bug
I made a file in java named 'pinap-copy' deleted it from files and made another file named 'Untitled-1' and typed the similar thing when I clicked run and debug it is showing 'pinap2 not found' why a file should depend on another file which is even deleted... I did not expect this to happen... vs code is very waste of time to download and waste of storage and internet too. VS code is worse than I thought it would be nice and better than BlueJ but I realized that bluej is only better than this.
VS Code version: Code 1.92.2 (fee1edb8d6d72a0ddff41e5f71a671c23ed924b9, 2024-08-14T17:29:30.058Z)
OS version: Windows_NT x64 10.0.22631
Modes:
|CPUs|AMD Ryzen 5 5500U with Radeon Graphics          (12 x 2096)|
|GPU Status|2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|7.33GB (1.09GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
Extensions (9)

Extension
Author (truncated)
Version

java
red
1.33.0

intellicode-api-usage-examples
Vis
0.2.8

vscodeintellicode
Vis
1.3.1

vscode-gradle
vsc
3.16.4

vscode-java-debug
vsc
0.58.0

vscode-java-dependency
vsc
0.24.0

vscode-java-pack
vsc
0.29.0

vscode-java-test
vsc
0.42.0

vscode-maven
vsc
0.44.0

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
vscaat:30438848
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonnoceb:30805159
asynctok:30898717
pythonregdiag2:30936856
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
f3je6385:31013174
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
dwnewjupytercf:31046870
impr_priority:31102340
refactort:31108082
pythonrstrctxt:31112756
flighttreat:31119336
wkspc-onlycs-c:31111717
wkspc-ranged-c:31123312
fje88620:31121564

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

thank you

It's not clear what the problem is, please spell it out step by step in detail


node tests on linux sometimes timeout without an obvious reason

+ npm install node-gyp-install
<EMAIL_ADDRESS>node_modules/node-gyp-install
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>+ ./node_modules/.bin/node-gyp-install
node-gyp-install http request https://nodejs.org/dist/v4.5.0/node-v4.5.0.tar.gz
node-gyp-install http 200 https://nodejs.org/dist/v4.5.0/node-v4.5.0.tar.gz

TIMEOUT: tools/run_tests/pre_build_node.sh [pid=1051]
FAILED: Some tests failed

https://grpc-testing.appspot.com/job/gRPC_pull_requests_linux/1320/testReport/junit/(root)/aggregate_tests/run_tests_node_linux_dbg/

Another timeout: https://grpc-testing.appspot.com/job/gRPC_portability_pull_requests_linux/6718/testReport/junit/(root)/aggregate_tests/run_tests_node_linux_dbg_native_default_node6_buildonly/


custom definitions not working

Hi, I'm attempting to follow the customization section in the FAQ by adding definitions. I cannot figure out why they are not being applied. I have confirmed that I have the latest settings package and it's copied into my config directory.
.config/sway/definitions.d/custom.conf
set $left h
set $down j
set $up k
set $right l

set $waybar_position bottom

.config/sway/config
# Default config for sway
#
# Copy this to ~/.config/sway/config and edit it to your liking.
#
# Read `man 5 sway` for a complete reference.

# styles - set the folder for your theme defination file
set $theme /usr/share/sway/themes/matcha-green

#theme variables
include $theme/definitions

# global variables
include /etc/sway/definitions

# user variables
include $HOME/.config/sway/definitions.d/*.conf

include /etc/sway/inputs/*
include /etc/sway/outputs/*

# enable modes
include /etc/sway/modes/*

# only enable this if every app you use is compatible with wayland
# xwayland disable

# include additional configs e.g. to autostart applications
include /etc/sway/config.d/*

# user config
include $HOME/.config/sway/config.d/*.conf

Note that this file from config.d is applied correctly.
config.d/01-user.conf
# input "*" equals all input methods
# to specify settings for a specific input method, use its identifier instead.
# query the connected input methods: `swaymsg -t get_inputs`

input * {
    # use capslock as win/super key
    # use both shift keys as capslock
    xkb_options caps:super,shift:both_capslock_cancel

}

what are you trying to achieve? the left/right/.. variables you set are only ever used in the "resize" mode and are identical in our /etc/sway/definitions ...
as for the waybar position: it doesn't respect the setting in sway. you have to put it into .config/waybar/config.jsonc:
{
    "include": [
        "/usr/share/sway/templates/waybar/config.jsonc"
    ],
    "position": "bottom"
}

Ah, so it probably is working fine. With left/right/etc I was trying to use hjkl for switching/moving windows. Knowing what you just mentioned I should be able to fix that.
As for bar position, that might warrant an update to docs and the README in definitions.d, that's where I got the info.
I'll close up this issue after I make sure I can get hjkl working. Thanks for your time.

I think adding this to config.d/ should fix ya up:
## Navigation // Move focus // $mod + ↑h ↓j ←k →l ##
$bindsym $mod+h focus left
$bindsym $mod+j focus down
$bindsym $mod+k focus up
$bindsym $mod+l focus right

## Navigation // Move focused window // $mod + Shift + ↑h ↓j ←k →l ##
$bindsym $mod+Shift+h move left
$bindsym $mod+Shift+j move down
$bindsym $mod+Shift+k move up
$bindsym $mod+Shift+l move right

might warrant an update to docs and the README in definitions.d
removed that and added a not about how it really works to the SUPPORT.md


Update unattended-installation.md

Docs Build status updates of commit a81f71f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Skype/SDN/articles/unattended-installation.md
:white_check_mark:Succeeded

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


In browser?

Hey
I'd like to use this in the browser as a standalone package? Is this possible?
Thanks

Yes, you can browserify it, or any sub-component you need.

OK. Never had much luck with browserify. I'm not that worried about backwards compatibility , so maybe using the new Streams API might be a place to start. And look at porting in stream parsers for image types. I'll have a look.

It would be nice if this was reopend to


Update New-TeamChannel.md

https://github.com/MicrosoftDocs/office-docs-powershell/issues/4252

Docs Build status updates of commit cd10895:
:clock10: Full build: the average full build time is 11 min(s) 46 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit cd10895:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/New-TeamChannel.md
:white_check_mark:Succeeded
View (teams-ps)

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

Docs Build status updates of commit 22141bd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/New-TeamChannel.md
:white_check_mark:Succeeded
View (teams-ps)

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


[luci] flutter engine builds timing out

There is no clear indication why engine builds are timing out, we need to start the Flutter LUCI playbook to provide instructions on how to debug those issues.
https://ci.chromium.org/p/flutter/builders/try/Linux Fuchsia/3249
This was actually caused by a timeout of one hour after triggering the tasks and the tasks having to wait ~50 minutes in the queue.

It seems very wrong that we're taking that long to schedule a build.
Can we just add more bots?

We added 10 more linux bots, we were on the limits because for linux we are using 1 + 4 extra drones.
I've been monitoring the tasks and they are back to less than 15 mins queue time in the worst case scenario.

CL for increasing collect timeout is now submitted


persistent queue connection on workers?

Is it possible to have a worker connect to a queue on startup and remain connected until ended?
it would make enqueuing downstream jobs much simpler as I could simply
queue.enqueue(queue, job1, args)
queue.enqueue(queue, job,2 args)
queue.enqueue(queue, job3, args)
queue.enqueue(queue, job4, args)
instead of connecting -> running async/parallel  -> disconnecting

ps. it seems like I could do this with an older version?
just simply a global queue.connect()  prior to starting the workers

This is exactly what all the examples do, IE: https://github.com/taskrabbit/node-resque/blob/master/examples/example.js#L103-L108, and works with the current version (we also test this in the test suite).  Are you not able to run the examples?

That works fine. My question is regarding enqueing from within a job. Currently I have to open a new connection to the queue from within the job which then means I have to end it after I'm done. If the number of tasks to be enqueued is large, it gets cumbersome to nest/promisify

Ah, I think I get what you are asking for.
You have 2 options:

use a queue defend outside the scope of the worker
use this.queueObject which is already set on the worker.  Within a job, this is the worker itself.

Thanks. using this.queueObject seems to do the trick.


updates to es6

What's this PR do?
Updates to ES6!
Where should the reviewer start?
Because babel and webpack were already added you'll just want to look through the code for non ES6isms.  Thankfully I think this was early enough on that all we had to deal with was a few vars.
How should this be manually tested?
No new features have been added. So loading the plugin the usual way(git pull, npm install, npm run build, Chrome-->extensions-->Load Unpacked Extension) and testing previous features should do.
Any background context you want to provide?
babel-core was added to the package.json do deal with some pesky npm warnings about incoming doom
What are the relevant tickets?
closes #3

removed for loop, added  _.forEach


Reduced Model Export

Is there any way to export the model so we can avoid converting the model each time?

Sure. You can just save it as any other Keras model:
from kito import reduce_keras_model
model_reduced = reduce_keras_model(model)
model_reduced.save(output_path)

Thank you for your fast answer.
This is a nice project. It reduced mi inference time from 120 to 50 seconds. Great job!


Remove logging code?

IMO Kemal shouldn't control logging output based on environment.  You might be interested in reading about "modern" style Linux daemons, in summary:

Log to STDOUT only.
Shutdown on TERM.
Reload config on HUP.
Don't fork or daemonize yourself.

If you want to disable logging, you should provide a -v verbose flag that instead will configure the logging level.  Commonly you can set default level to WARN, have "-v" go to INFO and have "-v -v" go to DEBUG.  If you stick with these rules, the init system (upstart/systemd) can control log output and provide process monitoring, automatic log rotation, etc.

@mperham i'm curious about this. For example how is sidekiq achieving this?

Sidekiq logs with a Logger but only to stdout.

I've started rewriting the CommonLogHandler and came to conclusion that reducing https://github.com/sdogruyol/kemal/blob/master/src/kemal/common_log_handler.cr#L8-L14 to STDOUT will definitely make things simpler.


⚠ Jenkins Plugins Artifactory has degraded performance

In dc45e3e, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1275 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 304162b after 12 minutes.


Feat/add middleware to check auth users  #18

Issue Fixed: #18
Feature(s)

jwt token verificattion
creates error if not authenticated

Note
@struckchure  please I will need help on how to get user from your api
so after you've merged all PR, I'll merge all codes, then will add the function to the routes

Conflicts, I knew it

Na why I talk say make you merge, so we go know what's up

Conflict fixed


I submitted two new files one of them is .txt

Awesome Job, I can see you are really getting this down. :)


Removing some NS prefixes from folders, files and documentation

Removing some NS prefixes from folders, files and documentation to fit with the new class names and make it easier to navigate the documentation and project structure.

@parkera Can I continue this work or if there a reason the NS prefixes were kept in the filenames and documentation?

Thanks, I think this is a good idea to make things clearer.
One note: things like class NSData should stay in NSData.swift, because we have both the class and the struct.

It would be good to merge this in fairly small chunks, so that we don't introduce too many merge conflicts. So if you want to merge this one then continue in other PRs, we can do that.

This PR has gone stale, unfortunately. Some of these renames have already happened in https://github.com/apple/swift-corelibs-foundation/pull/1058
@hartbit can you update this PR to fix any remaining issues? Or is it so stale you'd prefer to just close it?

@ianpartridge I forgot I had this PR :D I can have a look this evening!

I re-applied the PR on the latest master, co closing in favour of #1146


Enable --debug:full on coreclr

The coreclr F# does not generate a pdb file when a developer specified --debug:full
On the desktop --debug:full generates a windows format pdb.
With this PR --debug:full will generate a portable format pdb file from the coreclr version of the compiler.
It should be noted that: we cannot generate windows format pdbs on non windows machines, the libraries that support generation and use of windows pdb are windows only.
The recommended approach for developers is to use
<DebugType>portable</DebugType>

in project files, as this will produce the same result, with the desktop and coreclr F# compiler.  However, with this PR the result of full will be less surprising than before.
Kevin

Thanks @KevinRansom


Improve public IP requirement

Currently, bringing up Rivet will encode your public IP into the namespace config. This prevents certain containers from being brought up, since they'll try to be reached through a public IP, and fail.
A solution to allow the cluster to be brought up is to change the public_ip to <IP_ADDRESS> manually. This also doesn't let the full cluster work. Documentation for this could help, or adding a command to bolt to specify that it should set up on localhost.
However, I think there are still issues when it comes to running just on localhost, as you won't be able to use the hub after it starts. @nathan can you elaborate on the issues of using localhost?

Dev tunnels fixes this.


Compatibility with other file types

Great idea, never thought of this use of the &. Would it be possible to make it work with other file types like .php, .blade.php (https://marketplace.visualstudio.com/items?itemName=onecentlin.laravel-blade), ...? Thanks!

It is possible to support them by adding this check:
https://github.com/bancek/vscode-bem-expand/blob/master/src/expand.ts#L49
You can add and test it and create a pull request.

Your pull request has been merged. Thank you for your contribution. I've released a new version. It should appear on the Marketplace soon.

#8 maybe you want to take a look for my sugguestion


[MM-39162]:Remove collapsible from long status update in run overview

Summary

The post component we use in the run overview for status updates supports automatically collapsing long content, but this is undesirable on a page dedicated to viewing those status updates. Let's disable this functionality in this context:

JIRA: https://mattermost.atlassian.net/browse/MM-39162
Github: fixes https://github.com/mattermost/mattermost-server/issues/18597

Checklist

[x] Telemetry updated
[x] Gated by experimental feature flag
[x] Unit tests updated

Hello @srijit2002,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.
Per the Mattermost Contribution Guide, we need to add you to the list of approved contributors for the Mattermost project.
Please help complete the Mattermost contribution license agreement?
Once you have signed the CLA, please comment with /check-cla and confirm that the CLA check is green.
This is a standard procedure for many open source projects.
Please let us know if you have any questions.
We are very happy to have you join our growing community! If you're not yet a member, please consider joining our Contributors community channel to meet other contributors and discuss new opportunities with the core team.

@srijit2002, can I get you to sign the CLA so that we can get this review going and hopefully merged? Thanks!

Thanks for participating in Hacktoberfest! You can claim your sticker set here: https://get.printfection.com/hacktober21/4144583267 @srijit2002


[Transformer] Event for when transforming?

Hey! Is there an event I can hook into to know when the transformer updates the properties (for example x or y)?
I need to update an input field where I show the current value and I'm not sure how I would do it.
Something like transformer.on('transform', () => ...) maybe?
Not sure if #64 is related?
EDIT: Okay there is the transformchange event I've overlooked, sorry! Now I only need to figure out how I can transform the matrix to the specific properties like x, y or rotation.

Yep, the transformchange event is what you’re looking for!


Update README file

Update dependency management section

Coverage increased (+0.05%) to 91.002% when pulling 4c0282f22a5d7db25d61fb5e60fc7dc45414d5fb on SAP:read1 into 669ead6b4f03f82e804953d338452f1437286762 on cloudfoundry-incubator:master.


ATTRIBUTION is missing a license

The file src/nvcore/scanf.c has:

Copyright (c) 1990, 1993
The Regents of the University of California.  All rights reserved.

with a note "this code is derived from..." and a separate license.
The license appears to be the 3-clause/New-BSD, or 4-clause/BSD-old with removed advertising clause (judging by the missing item 3).

I've removed this dependency instead. That code was only necessary for old visual studio versions that didn't provide the vsscanf function. That function is not even used on this project, so removing it should be fairly safe.


How do you control the robot arm?

Hi, thanks much for sharing this low-cost solution and saw your demo video on X which is great.
Wonder did you use a local PC with GPU to implement the inference of imitation learning? Would it be possible to use a remote server with GPU to control the arm?
I've read through the readme, but not able to find how the algorithm communicates with the hardware, could you elaborate more on this?
Appreciated
Patrick

I've used my macbook directly to interface with the servos. In newer demos, I've used Raspberry Pis on the robot arms to connect them via ethernet to a central server.

I've used my macbook directly to interface with the servos. In newer demos, I've used Raspberry Pis on the robot arms to connect them via ethernet to a central server.

Thanks much for the reply, as for the Raspberry Pis& server combination you mentioned, how do you translate output of the algorithm(position control I guess?) to executable code for hardware? Do you use GPIO?
Bests:)


The ripple effect behaves strange when changing system theme without fully exit app in Android

The color of the ripple effect seems to remain at the light value when change the system theme to dark, which causes the ripple effect nearly undiscoverable.

Can you describe the steps here to observe this in a bit more detail?

untitled.webm
untitled2.webm
Please compare the ripple effects in the two video. The first one starts the app in dark mode, and the second starts the app in light mode and changes to dark mode manually, the ripple color of the two seems to be different. And they should be same.

Can you share the code you're using?  What colour are you expecting it to be?
I'm still not fully understanding what behaviour you're looking for, so a project and a description of the expected behaviour would help.
I'm guessing the colour might change based on system themes/colours, but it may be possible to influence this more explicitly...   One way likely is to do so with android platform styles...

I made a clean project with this packet referenced only. As you can see from the video, the ripple effect at 0:13 is different with the effect at 0:26. The only change I made is that I changed the system theme manually. Firstly I started the app with light mode and press the button in dark mode when I changed to dark, and secondly, I started the app with dark mode directly, and press the button.

https://github.com/user-attachments/assets/5b4529a2-1124-499a-a8fc-6ebdffda2a54
<ContentPage
    x:Class="Ripple.MainPage"
    xmlns="http://schemas.microsoft.com/dotnet/2021/maui"
    xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
    xmlns:mcb="http://schemas.microsoft.com/dotnet/2024/maui/contentbutton">
    <ScrollView>
        <VerticalStackLayout Padding="30,0" Spacing="25">
            <Image
                Aspect="AspectFit"
                HeightRequest="185"
                SemanticProperties.Description="dot net bot in a hovercraft number nine"
                Source="dotnet_bot.png" />

            <Label
                SemanticProperties.HeadingLevel="Level1"
                Style="{StaticResource Headline}"
                Text="Hello, World!" />

            <Label
                SemanticProperties.Description="Welcome to dot net Multi platform App U I"
                SemanticProperties.HeadingLevel="Level2"
                Style="{StaticResource SubHeadline}"
                Text="Welcome to
.NET Multi-platform App UI" />

            <Button
                x:Name="CounterBtn"
                Clicked="OnCounterClicked"
                HorizontalOptions="Fill"
                SemanticProperties.Hint="Counts the number of times you click"
                Text="Click me" />

            <mcb:ContentButton HeightRequest="80">
                <Grid BackgroundColor="Gray" ColumnDefinitions="*,*">
                    <Label
                        FontSize="30"
                        HorizontalTextAlignment="Center"
                        Text="Content1"
                        TextColor="{AppThemeBinding Dark=White,
                                                    Light=Black}" />
                </Grid>
            </mcb:ContentButton>
        </VerticalStackLayout>
    </ScrollView>
</ContentPage>

Thanks for the extra info, I think I understand a bit better what's going on here.  Interestingly this is also something happening in normal MAUI buttons (I just use the same methods that are there), but it's a bit inverted which seems to be due to me using MaterialCardView instead of MaterialButton.
Will do some thinking on this one.


depolying issue.

Repro steps:

Action: azureFunctions.deploy
Error type: Error
Error Message: Failed to deploy path that does not exist: /home/sai/GP-Infrastructure/Deployments/SEAsia/GP-Orders/ComosDb-Backups/BlobTrigger/bin/Release/netcoreapp2.1/publish
Version: 0.19.1
OS: linux
Product: Visual Studio Code
Product Version: 1.36.1
Language: en

Call Stack
Object.<anonymous> extension.bundle.js:288:13568
o extension.bundle.js:288:13149

@anjaneyulu-bods please add repro steps


While installing npm (npm install -g less) on Ubuntu

npm ERR! couldn't read package.json in .
npm ERR! Error installing .
npm ERR! Error: ENOENT, No such file or directory 'package.json'
npm ERR! Report this entire log at http://github.com/isaacs/npm/issues
npm ERR! or email it to<EMAIL_ADDRESS>npm ERR! Just tweeting a tiny part of the error will not be helpful.
npm not ok

Using an ancient version of npm. Please update to 1.0. Be sure to run the npm faq command for differences between npm 0.x and npm 1.x. ("Bundled" local installs are the default now, and required to be able to require() modules.)


Duplicate Price Labels

Bot should be sure to clean all Price labels before setting a new one to ensure a single Price label per bounty.

Seems like this issue isn't consistent. Will need to make it more robust

Its basically done here


cit constraint rules not working

the first rule prevents the following rules from being invoked

Could this effect the rule in usg
context="tei:usg[not(@type = 'geographic') and not(@type='socioCultural')]"
as well?

So, we have several contexts and one element in a document might be matching several rules, right?

tei:cit[not(@type = 'example')]
tei:cit[@type = 'translationEquivalent']
tei:cit[@type = 'translation']
tei:cit[@subtype = 'proverb']

So we could copy those rules which are now in tei:cit[not(@type = 'example')] to the other contexts - however, I feel duplicating the rules clutters the schema and makes it less readable.
Actually, I think, we have defined the same logic already in the <elementSpec> for <bibl> so probably we can remove it in the elementSpec for <cit>, couldn't we? For clarity we can leave an XML comment, for example.

Actually, I started a pull request which solves the problem. It was a syntax error I guess: https://github.com/acdh-oeaw/generic-dict-schema/pull/7
 <s:rule context="tei:cit/@type[not(. = 'example')]"> instead of
<s:rule context="tei:cit[not(@type = 'example')]">
That's why I asked if it concerns the rule in usg as well because it is the same syntax.
There is no error message or anything, simply the rules are not applied

Update:
my solution doesn't seem to work as wished.
While in usg the context MUST be defined as this context="tei:usg[not(@type = 'geographic') and not(@type='socioCultural')]", the first rule in cit <s:rule context="tei:cit[not(@type = 'example')]"> doesn't seem to work with <s:rule context="tei:cit/@type[not(. = 'example')]"> either. With the second version the subsequent rules are working, that's the only difference.

Actually, I think, we have defined the same logic already in the <elementSpec> for <bibl> so probably we can remove it in the elementSpec for <cit>, couldn't we? For clarity we can leave an XML comment, for example.

I would go for this!

I removed the first rule in cit as it is already included in the listBibl rule set (https://github.com/acdh-oeaw/generic-dict-schema/commit/9cfcf7378738c14c20486cb19e2940febdd9ee0f)


Address security alerts in package.json

Bootstrap and tar.  See: https://github.com/bcgov/greenlight/network/alerts

@swcurran can you please check whether the updates I made to GreenLight on Monday have addressed the security alerts and let me know?

@esune as of now, the security alert is still displayed for tar.  I made you an admin on the repo, so you should be able to see it.  Link above is still showing the issue.


NIFI-2457 removed old state file mechanism and fixed state reset logic

Reviewing...

I'm a +1 and will merge to master. My only comment is that we may want to call out in the release notes that we removed the auto-migration from the old state mechanism... probably an unlikely scenario, but someone with a lot of TailFile processors upgrading from pre-0.5.0 (when state management introduced) to 1.0.0 would likely want to first upgrade to some 0.x >=  5.0.0 then go to 1.0.0.


How to replay an object_  replay_buffer become types that support jax data

Please:
        replay_buffer = ReplayBuffer(env.observation_space, env.action_space,
                                     FLAGS.max_steps)

I want to pass it as an incoming parameter to the function：
agent, update_info = agent.update(batch, FLAGS.utd_ratio,replay_buffer)

But the update function requires jit acceleration
@partial(jax.jit, static_argnames='utd_ratio')
    def update(self, batch: DatasetDict, utd_ratio: int,replay_buffer):

        new_agent = self
        for i in range(utd_ratio):

            def slice(x):
                assert x.shape[0] % utd_ratio == 0
                batch_size = x.shape[0] // utd_ratio
                return x[batch_size * i:batch_size * (i + 1)]

            mini_batch = jax.tree_util.tree_map(slice, batch)
            print(replay_buffer)
            new_agent, critic_info = self.update_critic(new_agent, mini_batch,replay_buffer)

            pro=(critic_info['prios'])
            pro1=jnp.array([pro])
            indices=jnp.array(batch['indices'])
            replay_buffer.update_priorities(batch_indices=indices,batch_priorities=pro1)

        new_agent, actor_info = self.update_actor(new_agent, mini_batch)
        new_agent, temp_info = self.update_temperature(new_agent,
                                                       actor_info['entropy'])

        return new_agent, {**actor_info, **critic_info, **temp_info}

Error will be reported when I run directly
TypeError: Argument '<rl.data.replay_buffer.ReplayBuffer object at 0x7f0fd441ef70>' of type <class 'rl.data.replay_buffer.ReplayBuffer'> is not a valid JAX type

Thank you very much for your help!Thank you very much for your help!Thank you very much for your help!！！！！！

The ReplayBuffer is a class used for experience replay in reinforcement learning, and an object of this class is created as replay_buffer. I want to pass this replay_buffer object as an input parameter to a jit-accelerated update function, but the replay_buffer object does not support the data format of jax. How can I convert the replay_buffer to a data format that supports jax? Thank you for your help. Here is the general content of the ReplayBuffer class.
class ReplayBuffer(Dataset):
def init(self,
observation_space: gym.Space,
action_space: gym.Space,
capacity: int,
alpha:float = 0.6,
beta_start:float = 0.4,
beta_frames: float = 1e6,
next_observation_space: Optional[gym.Space] = None):
if next_observation_space is None:
next_observation_space = observation_space
    observation_data = _init_replay_dict(observation_space, capacity)
    next_observation_data = _init_replay_dict(next_observation_space,
                                              capacity)
    dataset_dict = dict(
        observations=observation_data,
        next_observations=next_observation_data,
        actions=np.empty((capacity, *action_space.shape),
                         dtype=action_space.dtype),
        rewards=np.empty((capacity, ), dtype=np.float32),
        dones=np.empty((capacity, ), dtype=bool),
    )

    super().__init__(dataset_dict)

    #self._size = 0
    self._capacity = capacity
    self._insert_index = 0
    self.alpha = alpha
    self.beta_start = beta_start
    self.beta_frames = beta_frames
    self.frame = 1
    self.capacity = capacity
    self.buffer = []
    self.pos = 0
    self.priorities = np.zeros((capacity,),dtype = np.float32)

def beta_by_frames(self, frame_idx):
    return min(1.0, self.beta_start + frame_idx * (1.0 - self.beta_start) / self.beta_frames)

def insert(self, data_dict: DatasetDict):
    state=data_dict['observations']
    next_state=data_dict['next_observations']
    assert state.ndim == next_state.ndim
    state = np.expand_dims(state, 0)
    next_state = np.expand_dims(next_state, 0)
    max_prio = self.priorities.max() if self.buffer else 1.0  # gives max priority if buffer is not empty else 1
    if len(self.buffer) < self.capacity:
        self.buffer.append((data_dict['observations'], data_dict['actions'], data_dict['rewards'] ,data_dict['next_observations'], data_dict['dones']))
    else:
        self.buffer[self.pos] = (data_dict['observations'], data_dict['actions'], data_dict['rewards'] ,data_dict['next_observations'], data_dict['dones'])

    self.priorities[self.pos] = max_prio
    self.pos = (self.pos + 1) % self.capacity  # lets the pos circle in the ranges of capacity if pos+1 > cap --> new posi = 0

def __len__(self) -> int:
    return self.buffer

def update_priorities(self, batch_indices, batch_priorities):
     for idx, prio in zip(batch_indices, batch_priorities):
        self.priorities[idx] = abs(prio)

def sample(self, batch_size)-> frozen_dict.FrozenDict:
    N = len(self.buffer)
    if N == self.capacity:
        prios = self.priorities
    else:
        prios = self.priorities[:self.pos]

    # calc P = p^a/sum(p^a)
    probs = prios ** self.alpha
    P = probs / probs.sum()

    # gets the indices depending on the probability p
    indices = np.random.choice(N, batch_size, p=P)
    samples = [self.buffer[idx] for idx in indices]

    beta = self.beta_by_frames(self.frame)
    self.frame += 1

    # Compute importance-sampling weight
    weights = (N * P[indices]) ** (-beta)
    # normalize weights
    weights /= weights.max()
    weights = np.array(weights, dtype=np.float32)
    observations, actions, rewards, next_observations, dones = zip(*samples)
    batch = {'observations': observations,
                     'actions': actions,
                        'rewards': rewards,
                        'next_observations': next_observations,
                        'dones': dones,
                        'indices': indices,
                        'weights': weights}
    #print(batch['weights'])
    for k,v in batch.items():
        batch[k] = np.array(v)
    return frozen_dict.freeze(batch)


Share link returns 500 "This Edge Function has crashed."

You likely have some automated error notifications, but just in case...
After successfully subscribing, I tried the "Email" share link, which took me to a 500 response at https://share.bingo/email?url=https%3A%2F%2Fbuttondown.email%2Fhotwireweekly&text=I%20just%20subscribed%20to%20Hotwire%20Weekly!
Body included:
500: INTERNAL_SERVER_ERROR
Code: EDGE_FUNCTION_INVOCATION_FAILED
ID: iad1::rt45f-1697476217194-dfa5de906c9b

Looking forward to the newsletters ❤

Thanks @ansonhoyt, I'm using Buttondown to manage the newsletter and it looks like Buttondown uses the share.bingo service to handle the share links 😅
I'll let them know and reference this issue, thank you!


Add files via upload

 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.:x: SheikMydheen sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@SheikMydheen , thank you for your contribution. Our SMEs have reviewed your PDFs and determined that this documentation already exists in our content set.
For future contributions, please consider creating the content in markdown. See our Contributor's guide for more information.


Seems that Artifact Registry username has changed

Today I've spotted the following behavior for docker-credential-gcr and docker-credential-gcloud:
$ echo "https://europe-west2-docker.pkg.dev" | docker-credential-gcr get
{"ServerURL":"https://europe-west2-docker.pkg.dev","Username":"_dcgcr__token","Secret":"REDACTED"}

$ echo "https://europe-west2-docker.pkg.dev" | docker-credential-gcloud get
{"Username":"_dcgcloud_token","Secret":"REDACTED"}

Here what I've got using different credentials and docker registry v2 API provided by Artifact Registry:
Issue:
#: U="_dcgcr__token", does not work
$ curl -u "${U}:${TOKEN}" https://europe-west2-docker.pkg.dev/v2/privategoogleprojectid/test/repo/manifests/test
{"errors":[{"code":"UNAUTHORIZED","message":"No valid credential was supplied."}]}

OK:
#: U="_dcgcloud_token", works like expected
$ curl -u "${U}:${TOKEN}" https://europe-west2-docker.pkg.dev/v2/privategoogleprojectid/test/repo/manifests/test
{
   "schemaVersion": 2,
   "mediaType": "application/vnd.docker.distribution.manifest.list.v2+json",
   "manifests": [
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 739,
         "digest": "sha256:b27f378865b05a9ea042435b4a256f37aaf6a92c445532ae8e4704c750a9d2e3",
         "platform": {
            "architecture": "amd64",
            "os": "linux"
         }
      }
   ]
}

Here's some info, false alarm due to properly compiled helper works like expected. The issue appears only of the helper was built without specifying its version (for example 2.1.6).
$ go build -ldflags "-X github.com/GoogleCloudPlatform/docker-credential-gcr/config.Version=2.1.6 -w -s" \
    -o docker-credential-gcr main.go
$ echo "https://europe-west2-docker.pkg.dev" |  ./docker-credential-gcr get
{"ServerURL":"https://europe-west2-docker.pkg.dev","Username":"_dcgcr_2_1_6_token","Secret":"REDACTED"}
$ curl -u "_dcgcr_2_1_6_token:REDACTED" https://europe-west2-docker.pkg.dev/v2/googleprojectid/test/repo/manifests/latest
{
   "schemaVersion": 2,
   "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
   "config": {
      "mediaType": "application/vnd.docker.container.image.v1+json",
      "size": 1138,
      "digest": "sha256:d64c396f90b6a35507dfed62d03d92e4a9c70b39a8fa5891c9992864fb2d47d5"
   },
   "layers": [
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 3374446,
         "digest": "sha256:63b65145d645c1250c391b2d16ebe53b3747c295ca8ba2fcb6b0cf064a4dc21c"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 5901486,
         "digest": "sha256:538c8f55312da22b96648ee2b3fa11e76fd8552a013058593e4928909b960921"
      }
   ]
}

Yes, you're correct about the need for the version in the username.  The check uses this:
"^dcgcr(?:[0-9]+_)*token$",


improve implementation

fix: remove open lib - use execPrm
chore(dev-deps): update & install best-practice dev-deps ✨
chore: revert to type module - alfy
chore(format): all project format 🥷

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Vaults not Combining ItemStackHandlers

Describe the Bug
Attempting to use item vaults and found that when extracting, chutes & funnels were unable to extract more than 20 stacks, even though upon breaking the vaults almost all (bar presumably the controller) still contained items. Comparators and Stockpile Switches both report the item vault as empty even when it is not.
Works properly when assembled into a minecart contraption (in that portable storage interfaces can be used to extract from all).
Reproduction Steps
I haven't been able to consistently reproduce it yet. I removed the vault completely and rebuilt it and the issue was still present, but building a new vault in a different location didn't reproduce. I'd been using the vaults in minecart contraptions, and using another mod to teleport the minecart they were attached to - both could plausibly have helped result in the error.
Expected Result
the vaults contain 20 stacks each, and I had 45, so I expected to extract 900 stacks rather than 20.
Screenshots and Videos
No response
Crash Report or Log
No response
Operating System
Windows 10
Mod Version
0.4.1
Minecraft Version
1.18.2
Other Mods
advancementfix-0.1.0
allium-0.2.2+1.18.2
architectury-4.5.76-fabric
badpackets-fabric-0.1.2
Botania-1.18.2-434-FABRIC
cardinal-components-api-4.1.4
carpet-extra-1.18.2-1.4.72
cc-restitched-1.100.8
chalk-2.0.1+1.18.2
chipped-1.2
cloth-config-6.2.62-fabric
Controlling-fabric-1.18.2-9.0+21
crawl-0.10.6
create-mc1.18.2_v0.4.1+637
DarkPaintings-Forge-1.18.2-10.0.3
ears-fabric-1.17-1.4.5_01
expanded-trident-enchanting-1.0.3
ExtendedDrawers-1.3.1+mc.1.18.2
extremesoundmuffler-3.27_fabric-1.18.x
fabric-carpet-1.18.2-1.4.69+v220331
fabric-language-kotlin-1.8.1+kotlin.1.7.0
farmers-delight-fabric-0.2.1
ferritecore-4.2.1-fabric
glassential-fabric-1.3.0
graphlib-0.2.4+1.18.2
half-doors-1.18.2-fabric-1.3.7
hexcasting-fabric-1.18.2-0.9.1
Incorporeal-3-fabric-1.18.2-4
indium-1.0.6+mc1.18.2
journeymap-1.18.2-5.8.5-fabric
kubejs-fabric-1802.5.4-build.516
lanterns-belong-on-walls-1.3.0-1.18.x
lazydfu-0.1.2
litematica-fabric-1.18.2-0.11.3
lithium-fabric-mc1.18.2-0.7.10
malilib-fabric-1.18.2-0.12.1
minihud-fabric-1.18.2-0.22.0
modmenu-3.2.3
MouseTweaks-fabric-mc1.18-2.22
notenoughcrashes-4.1.6+1.18.2-fabric
Patchouli-1.18.2-71.1-FABRIC
paucal-fabric-1.18.2-0.4.7
Paxi-1.18.2-Fabric-2.0
Pehkui-3.3.3+1.14.4-1.19.1
phosphor-fabric-mc1.18.x-0.8.1
qsl-1.1.0-beta.19_qfapi-1.0.0-beta.22_fapi-0.56.0_mc-1.18.2
rhino-fabric-1802.1.13-build.179
RoughlyEnoughItems-8.3.510
skiptransitions-1.3.2+1.18.x
sodium-fabric-mc1.18.2-0.4.1+build.15
tooltipfix-1.0.4-1.18
travelers-backpack-1.18.2-7.1.3
traverse-5.1.0
trinkets-3.3.1
tweakeroo-fabric-1.18.2-0.13.3
twigs-fabric-1.1.3-patch2+1.18.2
veinmining-fabric-0.0.13-1.18.2
wthit-fabric-4.11.0
youre-in-grave-danger-1.3.7
YungsApi-1.18.2-Fabric-2.0.8
YungsBetterDesertTemples-1.18.2-Fabric-1.2
Zoomify-1.6.0
Additional Context
Also potentially of note is that this bug occurred when using Quilt, rather than Fabric. I have yet to try and reproduce it in Fabric.

I can't reproduce either, let me know if a way is found.

okay, I successfully reproduced it with a new vault! I've got two pictures of the setup below, but basically it's a vault with glue sticking it together, a comparator reading its storage fill level, with the output being sent to a cart assembler with a controller rail underneath it.

After more testing it seems like the critical thing is that the vault form while it has a comparator reading from it.

Seems to work in my testing today, but I was getting really weird results last night. Can you test build 700?


UDP Double Bitrate When monitor it

Hi , i'm try to using tsp monitor , but when running the monitor , my bit rate will be double
what is the problem of my command?

Your command looks good. It simply displays that the TS bitrate is approximately 6.1 Mb/s all the time.
What is clear is that your command just receives multicast packets from the network. It does not send any packet. So, it will not change the stream on the network.
What you see is a obviously a measurement artifact.

What is this diagram?
How do you measure the bitrate? Which tool? With machine? Same as sender, receiver, other?
What is the correlation between the start/stop of the peak and your tsp command?

Your command looks good. It simply displays that the TS bitrate is approximately 6.1 Mb/s all the time.
What is clear is that your command just receives multicast packets from the network. It does not send any packet. So, it will not change the stream on the network.
What you see is a obviously a measurement artifact.

What is this diagram?
How do you measure the bitrate? Which tool? With machine? Same as sender, receiver, other?
What is the correlation between the start/stop of the peak and your tsp command?

I measure the bitrate by StreamXpert , sender and receiver at same Network but different machine , both of then are Server machine and Window10 1803 .

Not all udp source will be dobule bitrate after tsp monitor , i try three udp source (same software to send ) just one of them will be  double.

i try three udp source (same software to send ) just one of them will be double.

Do you mean that you try three different sources, that you run tsp bitrate monitor on each of them and you notice a double bitrate on only one of them?
Again, your tsp command does not send any packet, it just receives them. The only symptom that tsp exhibits on the network in your case is a multicast group add membership request for the specified group. So, you have to investigate how, in your network configuration, such an IGMP request may have the observed effect.
Do your three sources run from the same sender machine? Simultaneously or one after the other? On which machine does StreamXpert run? Same as sender? Same as tsp? How many other receivers do you have on the same LAN for each multicast group? What are the various multicast addresses and UDP ports?

i try three udp source (same software to send ) just one of them will be double.

Do you mean that you try three different sources, that you run tsp bitrate monitor on each of them and you notice a double bitrate on only one of them?
Again, your tsp command does not send any packet, it just receives them. The only symptom that tsp exhibits on the network in your case is a multicast group add membership request for the specified group. So, you have to investigate how, in your network configuration, such an IGMP request may have the observed effect.
Do your three sources run from the same sender machine? Simultaneously or one after the other? On which machine does StreamXpert run? Same as sender? Same as tsp? How many other receivers do you have on the same LAN for each multicast group? What are the various multicast addresses and UDP ports?

i use four machine  , three sender machine and one receiver (Run StreamXpert ) , just one double bitrate of them ,
it work after i change the sender machine  , it seem to be network setting problem , thanks you

I was passing by here...
@Morgan0328
Maybe You have another multicasts in the network with the same IP, but with different port.
For example You monitor <IP_ADDRESS>:5678, but You have MC like <IP_ADDRESS>:5679 . So in this case when You subscribe first, you will receive both streams => double bitrate.


Add Possibility to use built-in validators for primitive list elements

It would be very cool if I could apply the built in string Length validator to each element of IList<string> and the same goes for all built in validators

I think the RuleForEach method should do what you're after.

Exactly what I needed, but I can't find it in the docs https://github.com/JeremySkinner/FluentValidation/wiki

The docs aren't completely up to date and I don't really have time to work on them at the moment.

There should also be a way to test which list element has error. The following code throws argument exception during runtime:
validator.ShouldHaveValidationErrorFor(x => x.someList[0], foo)

Perform your assertion manually in this case by invoking Validate and checking the Errors collection on the result. The testhelper is just a shortcut for working with simple properties- for collections and complex properties the assertions need to be done manually.


The correct way of making own Argument Matchers

Hello!
I apologise in upfront if this is the wrong place to ask such kind of questions; Haven't found any suggestions where to do that in the contributing guide.
Anyways, Readme file states:

you are free to create your own custom RSpec::Matchers.

But no information of how this can be achieved is not given.
The only way I was able to find on my own is to monkey-patching RSpec::Mocks::ArgumentMatchers, but I sense I'm doing it wrong.
For example. say, I need anything_but(value) matcher, so I can use it in this way:
expect(something).to include hash: { with_value: anything_but(nil) }

class AnythingBut
  def initialize(*bad_values)
    @bad_values = bad_values
  end

  def ===(value)
    @bad_values.include?(value)
  end

  def description
    "anything_but(#{@bad_values.map(&:inspect).join(', ')})"
  end
end

module RSpec::Mocks::ArgumentMatchers
  def anything_but(*args)
    AnythingBut.new(*args)
  end
end

I believe a better way should exist and it would be so good if docs tell how.

The simplest way is to use RSpec::Matchers.define:
RSpec::Matchers.define :anything_but do |*bad_values|
  match { |value| bad_values.include?(value) }
end

Relevant docs: https://relishapp.com/rspec/rspec-expectations/v/3-6/docs/custom-matchers

The only issue I see with using RSpec::Matchers.define is that it can then be invoked like this, which doesn't read well:
expect(something).to anything_but(something_else)

@markaschneider then define it with wording that does read well:
RSpec::Matchers.define :be_anything_but do |*bad_values|
  match { |value| bad_values.include?(value) }
end

expect(something).to be_anything_but(something_else)


pylint, pep8 related issues fixed in pylti

Hi
In this PR I fixed all issues diagnose using pep8 and pylint. @carsongee I took pylintrc file from edx-plateform and placed here with little modification. Can you review it?
Thanks
#33

Coverage remained the same at 100.0% when pulling 3d3801aa00056a84a12bb58bf5467193e6bcb1cd on amir-qayyum-arbisoft:fix_pylint_issues into 9b8d6e8d3c6654195506de47a44e3bc83c43b45a on mitodl:master.

This will need a rebase, and I'd also prefer not to have a pylintrc at all unless we find reason to need one.  If we do, I'd rather we start with the default one: pylint --generate-rcfile and modify it to fit our needs rather than copying the edx-lint generated one from edx-platform.

Coverage remained the same at 100.0% when pulling d87905d965ae01e238b5629f563931de1de90d7a on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage remained the same at 100.0% when pulling d9731e4be070a4667b740e95453f6d7d8d6061cb on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

@carsongee  done with rebase and generating pylintrc file.

Coverage remained the same at 100.0% when pulling d9731e4be070a4667b740e95453f6d7d8d6061cb on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

I'm still seeing pylint errors:
************* Module pylti.common
W: 51, 0: Method 'authorize_request_token' is abstract in class 'OAuthDataStore' but is not overridden (abstract-method)
W: 51, 0: Method 'fetch_access_token' is abstract in class 'OAuthDataStore' but is not overridden (abstract-method)
W: 51, 0: Method 'fetch_request_token' is abstract in class 'OAuthDataStore' but is not overridden (abstract-method)
W: 51, 0: Method 'lookup_token' is abstract in class 'OAuthDataStore' but is not overridden (abstract-method)

These are all safe to disable under the class declaration for LTIOAuthDataStore since they are unused.  Also, there is no reason to check the pylintrc file into git since the default configuration is what we want for now.  So go ahead and just remove that file altogether.  With those two things we should be good to go.  You probably also want to make sure you have the latest version of pylint as they are always coming up with new things to check for.  I tested this with 1.4.3

@carsongee in the pylintrc file I commit it is generated plus customized. I have added a list of warning messages in disable option. So If I remove this file I need to put each disable message into code
disbale = { list of warning messages}
Second I am using pylint with version 1.0.1 it is the most stable version. I am on linux I installed it by following command
sudo apt-get install pylint

You should just be able to install pip, and run pip install --upgrade pylint, and as I mentioned, the messages didn't change at all with and without the RC file, so I don't think it is actually doing anything right now.  The default configuration file seems to be just fine for what we have here other than the message I posted which should be addressed locally, and not with the rcfile.

@carsongee i just updated pylint to 1.4.3, I am not able to reproduce warnings.. screenshots are attached

I don't know why you aren't seeing these.  The only thing I can think of is that pylint isn't seeing your virtual environment correctly and thus doesn't know that you are aren't implementing all the abstract methods.   Either way, the fix is easy by adding # pylint: disable=abstract-method to line 56 in common.py

Coverage remained the same at 100.0% when pulling d59407467b3fa59ea48fc13663dacb0bacb15416 on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage remained the same at 100.0% when pulling d59407467b3fa59ea48fc13663dacb0bacb15416 on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage remained the same at 100.0% when pulling 284fe58f3f38cc21d0cd3ac422bea5ead2617a8d on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage decreased (-20.14%) to 79.86% when pulling d5977d3cc1c1c236dd5d2283ea420f84c3f332ef on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage decreased (-20.14%) to 79.86% when pulling d5977d3cc1c1c236dd5d2283ea420f84c3f332ef on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage decreased (-20.14%) to 79.86% when pulling 28422dbb6f9e67f29c324a57a76ab659e0376971 on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage decreased (-20.14%) to 79.86% when pulling 28422dbb6f9e67f29c324a57a76ab659e0376971 on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage decreased (-20.14%) to 79.86% when pulling b8f0fac745f6a0158ff0428f92e26e59ba7eab92 on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage decreased (-20.14%) to 79.86% when pulling 8cf0ca7f40cd0d5e98650f5a705ad3cd8ae652c1 on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage decreased (-20.14%) to 79.86% when pulling 8cf0ca7f40cd0d5e98650f5a705ad3cd8ae652c1 on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

You'll need to figure out how to get the coverage back to 100%.  I don't know why half of the tests don't appear to be getting run, but you'll definitely want to figure that out.

@carsongee  I am working on it

Coverage decreased (-20.14%) to 79.86% when pulling f2f5cc23d95a2a545bfc556acb5ba201ca8039c9 on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage decreased (-20.14%) to 79.86% when pulling f2f5cc23d95a2a545bfc556acb5ba201ca8039c9 on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage decreased (-20.17%) to 79.83% when pulling 9f0182bc602090340d6ac85787069382c9922655 on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

@carsongee i am working on this PR, please give me some time
Thanks

Coverage remained the same at 100.0% when pulling ee5068b062f56982952741f6af9e22e6e0889488 on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage remained the same at 100.0% when pulling ee5068b062f56982952741f6af9e22e6e0889488 on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage remained the same at 100.0% when pulling 694149c4bcdbac2363233139ea415b9a8556dc44 on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage remained the same at 100.0% when pulling 4b4468c714f436d6720fd16462bc0babff86843a on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage remained the same at 100.0% when pulling 7ea19ccd752c371f5701b73b8688a93fd684cd63 on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage remained the same at 100.0% when pulling 7ea19ccd752c371f5701b73b8688a93fd684cd63 on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage remained the same at 100.0% when pulling 7ea19ccd752c371f5701b73b8688a93fd684cd63 on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage remained the same at 100.0% when pulling 19dd51609e3431f4e51677bef17e7eab0338de73 on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage remained the same at 100.0% when pulling 2e21c89c36097b954c0ac7803e9b5f45673bfe8a on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage remained the same at 100.0% when pulling 2e21c89c36097b954c0ac7803e9b5f45673bfe8a on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage remained the same at 100.0% when pulling 2e21c89c36097b954c0ac7803e9b5f45673bfe8a on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage remained the same at 100.0% when pulling 181a9fc9fa5e80c8f49ff9b22c929901daa7699b on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage remained the same at 100.0% when pulling 181a9fc9fa5e80c8f49ff9b22c929901daa7699b on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

@carsongee done with changes and fixed coverage issues,
Added logging-format-interpolation in RC file because i think .format() is ok to use.
http://stackoverflow.com/questions/5082452/python-string-formatting-vs-format
their are some messages like multiple arguments, multiple params , I thing messages like it should be add into RC file. What do you say?

string format is better for everything but logging, which is what that pylint message is telling you.  For logging, the format should be log.debug('Hello %s, how are you %s', name, 'today') otherwise you are making an extra function call that is not needed.

Coverage remained the same at 100.0% when pulling bed79b51fcff0210908e7ab19eec57e1785130af on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage remained the same at 100.0% when pulling bed79b51fcff0210908e7ab19eec57e1785130af on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Just to address your other comment, for multiple arguments and multiple params, those shouldn't be added to the RC file as we should strive to write functions that don't need that many arguments.  We are stuck for the most part right now with what we have, but if we added a new function tomorrow, I would want it to fit into the pylint defaults.  That is the reason for just doing local disable messages there.

@carsongee done with all changes on your feedback. Now it is giving me code-duplication warning between 2 classes test_flask and test_common , is this ok?

Coverage remained the same at 100.0% when pulling 0dd531f65b3517c24a5f2bbf820616ef20dbc3da on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage remained the same at 100.0% when pulling 0dd531f65b3517c24a5f2bbf820616ef20dbc3da on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage decreased (-5.76%) to 94.24% when pulling 16684c2454675cee1efb20c049590d14117bbf30 on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage remained the same at 100.0% when pulling 989fc2b5776fd69300052cf0432908691fd404ce on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage remained the same at 100.0% when pulling 9318a3efcc097304f0bba80540371cad2c92b7ff on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage remained the same at 100.0% when pulling e7efc7810e2e01d621fafcedc126935827ad55b9 on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage remained the same at 100.0% when pulling 87db980a7545ea5e857c347167e8977cd4a79c9b on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage remained the same at 100.0% when pulling ed37757ff09abcec07a446f3fa7332498573cc3d on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

Coverage remained the same at 100.0% when pulling 927355ef33e53677c91339357e767287427e0e6f on amir-qayyum-arbisoft:fix_pylint_issues into a8af2c877484b4ea30a288b07290344f71a0431a on mitodl:master.

@carsongee done with removing invalid-name and fixing issues, Thanks

excellent, this looks good. :birthday:


[Feature Request]: Expand ImageTemplate removal

Description
Once #1726 is merged, we should consider bumping up the image template removal a bit:
There is a similar logic for the DevOps Self-Hosted construct here.
There are 2 main differences compared to the implementation in #1726 (Remove-ImageTemplate.ps1):

The script filters for image template not in status new or running
The script filters all found image template essentially for the prefix. Main reason being - If I run the script multiple times, or something about the pipeline fails or anything, the full image template name will be lost.

Agree, and I suggest to leverage the new namePrefix output of the image template module for the second point

With the current logic the template is removed - but only if nothing goes wrong. And as the name is different on every run you'd need to update stuff manually

Moved back to needs triage to suggest its closure given this won't be relevant with the new dependencies approach.


feat: Uniform way of closing popup window

@Fildo7525 Any updates?

I want to make a patch for exporting the keymaps to config. However, I do not have time now.

Shall we convert this to a draft?