text:
No ui router for win (module 'noice.ui.win' not found) when running :checkhealth

Describe the bug
Title, happens only when running checkhealth
Which version of Neovim are you using?
Gui(specify which GUI client you are using)? Nightly? Version?
Nightly 0.9.0
To Reproduce
Steps to reproduce the behavior:

Open neovim
Run :checkhealth

Expected Behavior
No error message
Screenshots

Noice Log

Noice log

Thu Oct  6 03:59:39 2022
...opt/nvim-notify/lua/notify/service/buffer/highlights.lua:153: Invalid buffer id: 4
stack traceback:
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:102: in function <.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:101>
[C]: in function 'nvim_buf_get_option'
...opt/nvim-notify/lua/notify/service/buffer/highlights.lua:153: in function 'set_opacity'
...acker/opt/nvim-notify/lua/notify/service/buffer/init.lua:45: in function '_create_highlights'
...acker/opt/nvim-notify/lua/notify/service/buffer/init.lua:38: in function 'set_notification'
.../pack/packer/opt/nvim-notify/lua/notify/service/init.lua:73: in function 'replace'
...vim/site/pack/packer/opt/nvim-notify/lua/notify/init.lua:212: in function 'notify'
...ite/pack/packer/opt/noice.nvim/lua/noice/view/notify.lua:125: in function '_notify'
...ite/pack/packer/opt/noice.nvim/lua/noice/view/notify.lua:151: in function <...ite/pack/packer/opt/noice.nvim/lua/noice/view/notify.lua:128>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:82: in function 'display'
.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:91: in function <.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:75>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:34: in function ''
vim/_editor.lua: in function ''
vim/_editor.lua: in function <vim/_editor.lua:0>
Thu Oct  6 04:03:24 2022
...opt/nvim-notify/lua/notify/service/buffer/highlights.lua:153: Invalid buffer id: 4
stack traceback:
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:102: in function <.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:101>
[C]: in function 'nvim_buf_get_option'
...opt/nvim-notify/lua/notify/service/buffer/highlights.lua:153: in function 'set_opacity'
...acker/opt/nvim-notify/lua/notify/service/buffer/init.lua:45: in function '_create_highlights'
...acker/opt/nvim-notify/lua/notify/service/buffer/init.lua:38: in function 'set_notification'
.../pack/packer/opt/nvim-notify/lua/notify/service/init.lua:73: in function 'replace'
...vim/site/pack/packer/opt/nvim-notify/lua/notify/init.lua:212: in function 'notify'
...ite/pack/packer/opt/noice.nvim/lua/noice/view/notify.lua:125: in function '_notify'
...ite/pack/packer/opt/noice.nvim/lua/noice/view/notify.lua:151: in function <...ite/pack/packer/opt/noice.nvim/lua/noice/view/notify.lua:128>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:82: in function 'display'
.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:91: in function <.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:75>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:34: in function ''
vim/_editor.lua: in function ''
vim/_editor.lua: in function <vim/_editor.lua:0>
Thu Oct  6 04:03:29 2022
...m/site/pack/packer/opt/nui.nvim/lua/nui/popup/border.lua:440: Invalid buffer id: 8
stack traceback:
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:102: in function <.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:101>
[C]: in function 'nvim_open_win'
...m/site/pack/packer/opt/nui.nvim/lua/nui/popup/border.lua:440: in function '_open_window'
...vim/site/pack/packer/opt/nui.nvim/lua/nui/popup/init.lua:252: in function 'show'
...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:143: in function <...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:134>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:82: in function 'display'
.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:91: in function <.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:75>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:29: in function <...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:22>
Thu Oct  6 04:03:29 2022
...vim/site/pack/packer/opt/nui.nvim/lua/nui/utils/init.lua:129: Invalid buffer id: 7
stack traceback:
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:102: in function <.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:101>
[C]: in function 'nvim_buf_set_option'
...vim/site/pack/packer/opt/nui.nvim/lua/nui/utils/init.lua:129: in function 'set_buf_options'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:156: in function 'render'
...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:145: in function <...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:134>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:82: in function 'display'
.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:91: in function <.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:75>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:29: in function <...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:22>
Thu Oct  6 04:03:29 2022
...vim/site/pack/packer/opt/nui.nvim/lua/nui/utils/init.lua:129: Invalid buffer id: 7
stack traceback:
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:102: in function <.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:101>
[C]: in function 'nvim_buf_set_option'
...vim/site/pack/packer/opt/nui.nvim/lua/nui/utils/init.lua:129: in function 'set_buf_options'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:156: in function 'render'
...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:145: in function <...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:134>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:82: in function 'display'
.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:91: in function <.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:75>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:29: in function <...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:22>
Thu Oct  6 04:03:29 2022
...vim/site/pack/packer/opt/nui.nvim/lua/nui/utils/init.lua:129: Invalid buffer id: 7
stack traceback:
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:102: in function <.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:101>
[C]: in function 'nvim_buf_set_option'
...vim/site/pack/packer/opt/nui.nvim/lua/nui/utils/init.lua:129: in function 'set_buf_options'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:156: in function 'render'
...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:145: in function <...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:134>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:82: in function 'display'
.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:91: in function <.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:75>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:29: in function <...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:22>
Thu Oct  6 04:03:29 2022
...vim/site/pack/packer/opt/nui.nvim/lua/nui/utils/init.lua:129: Invalid buffer id: 7
stack traceback:
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:102: in function <.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:101>
[C]: in function 'nvim_buf_set_option'
...vim/site/pack/packer/opt/nui.nvim/lua/nui/utils/init.lua:129: in function 'set_buf_options'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:156: in function 'render'
...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:145: in function <...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:134>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:82: in function 'display'
.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:91: in function <.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:75>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:29: in function <...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:22>
Thu Oct  6 04:03:29 2022
...vim/site/pack/packer/opt/nui.nvim/lua/nui/utils/init.lua:129: Invalid buffer id: 7
stack traceback:
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:102: in function <.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:101>
[C]: in function 'nvim_buf_set_option'
...vim/site/pack/packer/opt/nui.nvim/lua/nui/utils/init.lua:129: in function 'set_buf_options'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:156: in function 'render'
...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:145: in function <...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:134>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:82: in function 'display'
.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:91: in function <.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:75>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:29: in function <...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:22>
Thu Oct  6 04:03:29 2022
...vim/site/pack/packer/opt/nui.nvim/lua/nui/utils/init.lua:129: Invalid buffer id: 7
stack traceback:
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:102: in function <.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:101>
[C]: in function 'nvim_buf_set_option'
...vim/site/pack/packer/opt/nui.nvim/lua/nui/utils/init.lua:129: in function 'set_buf_options'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:156: in function 'render'
...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:145: in function <...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:134>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:82: in function 'display'
.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:91: in function <.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:75>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:29: in function <...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:22>
Thu Oct  6 04:03:31 2022
...m/site/pack/packer/opt/nui.nvim/lua/nui/popup/border.lua:440: Invalid buffer id: 8
stack traceback:
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:102: in function <.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:101>
[C]: in function 'nvim_open_win'
...m/site/pack/packer/opt/nui.nvim/lua/nui/popup/border.lua:440: in function '_open_window'
...vim/site/pack/packer/opt/nui.nvim/lua/nui/popup/init.lua:252: in function 'show'
...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:143: in function <...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:134>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:82: in function 'display'
.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:91: in function <.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:75>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:29: in function <...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:22>
Thu Oct  6 04:03:31 2022
...vim/site/pack/packer/opt/nui.nvim/lua/nui/utils/init.lua:129: Invalid buffer id: 7
stack traceback:
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:102: in function <.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:101>
[C]: in function 'nvim_buf_set_option'
...vim/site/pack/packer/opt/nui.nvim/lua/nui/utils/init.lua:129: in function 'set_buf_options'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:156: in function 'render'
...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:145: in function <...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:134>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:82: in function 'display'
.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:91: in function <.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:75>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:29: in function <...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:22>
Thu Oct  6 04:03:31 2022
...vim/site/pack/packer/opt/nui.nvim/lua/nui/utils/init.lua:129: Invalid buffer id: 7
stack traceback:
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:102: in function <.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:101>
[C]: in function 'nvim_buf_set_option'
...vim/site/pack/packer/opt/nui.nvim/lua/nui/utils/init.lua:129: in function 'set_buf_options'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:156: in function 'render'
...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:145: in function <...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:134>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:82: in function 'display'
.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:91: in function <.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:75>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:29: in function <...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:22>
Thu Oct  6 04:03:32 2022
...m/site/pack/packer/opt/nui.nvim/lua/nui/popup/border.lua:440: Invalid buffer id: 8
stack traceback:
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:102: in function <.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:101>
[C]: in function 'nvim_open_win'
...m/site/pack/packer/opt/nui.nvim/lua/nui/popup/border.lua:440: in function '_open_window'
...vim/site/pack/packer/opt/nui.nvim/lua/nui/popup/init.lua:252: in function 'show'
...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:143: in function <...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:134>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:82: in function 'display'
.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:91: in function <.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:75>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:29: in function <...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:22>
Thu Oct  6 04:03:32 2022
...vim/site/pack/packer/opt/nui.nvim/lua/nui/utils/init.lua:129: Invalid buffer id: 7
stack traceback:
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:102: in function <.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:101>
[C]: in function 'nvim_buf_set_option'
...vim/site/pack/packer/opt/nui.nvim/lua/nui/utils/init.lua:129: in function 'set_buf_options'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:156: in function 'render'
...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:145: in function <...m/site/pack/packer/opt/noice.nvim/lua/noice/view/nui.lua:134>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:82: in function 'display'
.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:91: in function <.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:75>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:107: in function 'try'
...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:29: in function <...im/site/pack/packer/opt/noice.nvim/lua/noice/ui/init.lua:22>
Wed Oct 12 17:07:39 2022
...ite/pack/packer/opt/noice.nvim/lua/noice/view/notify.lua:165: E11: Invalid in command-line window;  executes, CTRL-C quits
stack traceback:
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:119: in function <.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:118>
[C]: in function 'nvim_win_close'
...ite/pack/packer/opt/noice.nvim/lua/noice/view/notify.lua:165: in function 'hide'
.../site/pack/packer/opt/noice.nvim/lua/noice/view/init.lua:90: in function 'display'
.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:91: in function <.../pack/packer/opt/noice.nvim/lua/noice/message/router.lua:75>
[C]: in function 'xpcall'
.../site/pack/packer/opt/noice.nvim/lua/noice/util/call.lua:124: in function 'try'
...site/pack/packer/opt/noice.nvim/lua/noice/util/hacks.lua:91: in function 'cmd'
...hare/nvim/site/pack/packer/opt/hop.nvim/lua/hop/init.lua:264: in function 'get_input_pattern'
...hare/nvim/site/pack/packer/opt/hop.nvim/lua/hop/init.lua:495: in function 'hint_char1'
/home/amaanq/.config/nvim/lua/plugins/hop.lua:49: in function </home/amaanq/.config/nvim/lua/plugins/hop.lua:48>

I assume you enabled debug=true? That;s what you get for events coming in that we dont support.
Debug message. disable debug to disable it.

oops, sorry! that was it, i had accidentally left it on :) thanks!

authors: amaanq folke


text:
How can I disable whichkey for everything but ctrl-r?

I only want to use  functionality in insert mode, which gives me a pop up of register contents. How can I disable everything else in which-key but that?

If that's all you were going to use from Which-Key then you may only need this (tversteeg/registers.nvim)[https://github.com/tversteeg/registers.nvim]

Agree, you don't need which-key for just registers

source: gharchive/issue

authors: folke grddavies sdemura

license_type: permissive

license_source: github-api


text:
easee unavailable

Question
After updating HA to latest version my charger is unavailable.
What version of the integration are you using?
version": "0.9.44",
Anything in the logs that might be useful for us?
Denne feilen stammer fra en tilpasset integrasjon.

Logger: homeassistant
Source: custom_components/easee/controller.py:421
Integration: Easee EV Charger (documentation, issues)
First occurred: 13:47:21 (152 occurrences)
Last logged: 16:18:08

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/config/custom_components/easee/controller.py", line 421, in refresh_sites_state
    charger_data.state = site_state.get_charger_state(charger_id, raw=True)
  File "/usr/local/lib/python3.10/site-packages/pyeasee/site.py", line 128, in get_charger_state
    return ChargerState(charger_data["chargerState"], raw)
  File "/usr/local/lib/python3.10/site-packages/pyeasee/charger.py", line 56, in __init__
    data = {
TypeError: 'NoneType' object is not a mapping

Additional information
I have tried restart HA and uninstall and install the component with no luck.

This is the same issue as: https://github.com/fondberg/easee_hass/issues/208

Solved in https://github.com/fondberg/easee_hass/pull/210

license: MIT


text:
pyftsubset: Dotted I doesn't get subset

I don't know if this was reported or I am doing something wrong but.
I'm using pyftsubset to subset some characters from an otf font (I don't believe it matters which font) but one character (dotted I) is not getting subset:
https://www.fileformat.info/info/unicode/char/0130/index.htm
the only way the character would be subset is if I do --unicodes='*', but that is not what I want... I if do --unicodes=U+0130 it just doesn't get through (
everything else works)
What is interesting is that I've tried to run the command with --verbose
pyftsubset font.otf --output-file=newfont.otf --unicodes=U+0130 --verbose
Text: ''
Unicodes: [304]
Glyphs: []
Gids: []
maxp pruned
cmap pruned
post pruned
CFF  pruned
GPOS pruned
GSUB pruned
kern dropped
name pruned
Added .notdef to subset
Closing glyph list over 'GSUB': 2 glyphs before
Glyph names: ['.notdef', 'Idotaccent']
Glyph IDs:   [0, 259]
Closed glyph list over 'GSUB': 2 glyphs after
Glyph names: ['.notdef', 'Idotaccent']
Glyph IDs:   [0, 259]
Retaining 2 glyphs
head subsetting not needed
hhea subsetting not needed
maxp subsetting not needed
OS/2 subsetting not needed
cmap subsetted
post subsetted
CFF  subsetted
GPOS subsetted
GSUB subsetted
hmtx subsetted
name subsetting not needed
OS/2 Unicode ranges pruned: [2]
CFF  pruned
GPOS pruned
GSUB pruned
Input font: 109192 bytes: font.otf
Subset font:   1096 bytes: newfont.otf

And it looks ok, but if I type the character in with the font it doesn't get shown, like there is no glyph for it while if I try it on the original (input) font it works ok. Am I missing something?

This aspect is not implemented in the subsetter.

@behdad should there be an issue to track this?

I already fixed it.

authors: O7JaniB behdad miguelsousa

repo: fonttools/fonttools

license: mit

license_source: bigquery


text:
[ttLib] add rsb attribute to _TTGlyph

As discussed in #1074.
More than happy to add a test if needed.

well, it's good that we have some tests already
See https://travis-ci.org/fonttools/fonttools/jobs/288179180#L2939
sometime a glyf Glyph does not have xMax (empty glyphs).
replace self._glyph.xMax with self.glyph._xMax if hasattr(self._glyph, "xMax") else 0 or similar.

@anthrotype thanks, I've forced pushed the fix

Hm, I wonder... When the xMax is 0 because the glyph has no contours nor components, its right side bearing is also equal to 0, or is it equal to the advance width?
Also, I think this won't work with CFF charstrings, does it? The latter don't have xMax or other bbox attributes

I'm fairly sure this implementation of rsb is not correct when lsb != xMin.

I don't think CFF charstrings have an .lsb attr even...

@justvanrossum Good point. I'll take a look now.

Like @anthrotype, I'm not super convinced of this addition. It's a higher level bit of info, which suggests it should also work with charstrings, which it cannot.

@justvanrossum @anthrotype Thank you for both raising your valid concerns. Yeah, side-bearings seem to be a concept of font editors.
Closing.

Actually, I was wrong, CFF-based fonts still must have an hmtx table, so the glyph objects do have an lsb attribute. That said, the main reason that the glyph object carries the lsb around is so it can calculate an x offset for drawing a TT glyph to a pen.

source: gharchive/pull-request

authors: anthrotype justvanrossum m4rc1e


text:
[interpolatable] Return master indices instead of names

Using names to refer to masters is weird. Return the index and the user can look up the name.
This changes the API in two ways:

test and test_gen do not accept a names parameter anymore. If needed I can put it back there unused.
master, master1, master2 in the problem reports are now indices, not names. If this is undesirable, I can add separate master_idx, master1_idx, master2_idx instead. Maybe that's better.

Nevermind. I'll make a non-breaking change.

PTAL!


text:
Pushing sequential packages doesn't show the name of a package currently being deployed

Is your feature request related to a problem? Please describe.
Deploying a large number of packages can take a long time. Using pushPackageDirectoriesSequentially set to true makes all packages to be deployed one by one. When we have more than 40 packages inside sfdx-project.json, it's easy to get lost which package is currently being deployed.
What are you trying to do
I would like to see the name of a package currently being deployed.
Describe the solution you'd like
Instead of seeing the following console output:
*** Pushing with SOAP API v54.0 ***
DEPLOY PROGRESS | ████████████████████████████████████████ | 251/251 Components
*** Pushing with SOAP API v54.0 ***
DEPLOY PROGRESS | ████████████████████████████████████████ | 3453/3453 Components
*** Pushing with SOAP API v54.0 ***
DEPLOY PROGRESS | ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ | 0/2345 Components

I would like to see this for example:
*** Pushing pkg-x with SOAP API v54.0 ***
DEPLOY PROGRESS | ████████████████████████████████████████ | 251/251 Components
*** Pushing pkg-y with SOAP API v54.0 ***
DEPLOY PROGRESS | ████████████████████████████████████████ | 3453/3453 Components
*** Pushing pkg-z with SOAP API v54.0 ***
DEPLOY PROGRESS | ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ | 0/2345 Components

Describe alternatives you've considered
I can only wait & count packages, which one is currently deployed, and compare it with order in a sfdx-project.json file.

Marking this as help wanted in case you or anyone else wants to add this feature.
How I see this should work:
1st scenario: no pushPackageDirectoriesSequentially defined, only one pkg:
nothing changes, you know there's only one pkg to deploy.
2nd scenario: pushPackageDirectoriesSequentially is set to true, multiple pkg will be deployed:
the output should look like what @pznmc suggest so it's clear to the user which pkg is being deployed:
*** Pushing pkg-x with SOAP API v54.0 ***
DEPLOY PROGRESS | ████████████████████████████████████████ | 251/251 Components
*** Pushing pkg-y with SOAP API v54.0 ***
DEPLOY PROGRESS | ████████████████████████████████████████ | 3453/3453 Components
*** Pushing pkg-z with SOAP API v54.0 ***
DEPLOY PROGRESS | ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ | 0/2345 Components

technical details
There's a variable in force:source:push to detect if it's doing a sequential deploy, use it to detect which msg to render:
https://github.com/salesforcecli/plugin-source/blob/main/src/commands/force/source/push.ts#L80
you'll need to update the getVersionMessage func to accept a pkg name (string) as an argument and return the correct msg:
https://github.com/salesforcecli/plugin-source/blob/main/src/commands/force/source/push.ts#L108
https://github.com/salesforcecli/plugin-source/blob/main/src/deployCommand.ts#L234
Also use this.project.getSfProjectJson().getUniquePackageNames() to get the pkg names in the order they are defined.
The library that deploys the source returns a "Component Set` of metadata per pkg, the order of the component sets returned will be the same as you have pkgs defined in the project so you can rely on that to assign the each pkg name to a component set here
https://github.com/salesforcecli/plugin-source/blob/main/src/commands/force/source/push.ts#L90
1st componentSet corresponds to the 1st pkg returned by getUniquePackageNames(), etc.
feel free to post here if you have any questions.

repo: forcedotcom/cli


text:
Unable to Deploy or Retrieve data/files from the org through VS Code

Summary:
For my authorized org for a given project, when I right click on my project/lwc/apex class, and select Deploy source to org, a pop up comes up stating that the command is running but it keeps running forever but nothing gets deployed.
Steps To Reproduce:
Authorize an org.
Right click any component/project that you wish to deploy and click SFDX : Deploy source to org.
The pop up comes us saying Running SFDX: Deploy Source to Org and it run forever.
In the command-line output as well, it doesn't indicates that the deployment has started but it is in pending state for a long time.
Expected result
It should deploy my selected changes to my authorized org.
Actual result
The command/action hangs and runs forever and nothing gets deployed.
Salesforce Extension Version in VS Code: 57.6.0
SFDX CLI Version: @salesforce/cli/2.16.7 win32-x64 node-v20.8.1
OS and version: Windows 10
VS Code version: 1.94.1 ( user setup)

@Radha-4235 from the error I see your CLI install is trying to import an imcompatible version of ansi-escapes (we use v4, latest ones are ESM which cause the error you see).
Can you try do a full uninstall of the CLI then install it again?:
https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_uninstall.htm


text:
force:org:list Cannot read property 'getUsername' of undefined

Summary
force:org:list fails.
$ sfdx force:org:list
ERROR running force:org:list:  Cannot read property 'getUsername' of undefined

Steps To Reproduce:

Update cli

$ sfdx update
sfdx-cli: Updating CLI from 7.53.0-839fc82926 to 7.56.1-2773b53bf5... done
sfdx-cli: Updating CLI... done
warning "@oclif/plugin-autocomplete > @oclif/command@1.5.19" has unmet peer dependency "@oclif/plugin-help@^2".
sfdx-cli: Updating plugins... done

sfdx force:org:list

Actual result
ERROR running force:org:list:  Cannot read property 'getUsername' of undefined
Additional information
Feel free to attach a screenshot.
SFDX CLI Version(to find the version of the CLI engine run sfdx --version):
sfdx-cli/7.56.1-2773b53bf5 linux-x64 node-v10.15.3
SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core)
@oclif/plugin-autocomplete 0.1.5
@oclif/plugin-commands 1.2.3 (core)
@oclif/plugin-help 2.2.3 (core)
@oclif/plugin-not-found 1.2.3 (core)
@oclif/plugin-plugins 1.7.9 (core)
@oclif/plugin-update 1.3.9 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-trust 3.0.7 (core)
analytics 1.7.1 (core)
generator 1.1.2 (core)
salesforcedx 48.12.1
├─ @salesforce/sfdx-plugin-lwc-test 0.1.5
├─ salesforcedx-templates 48.10.0
└─ salesforce-alm 48.12.0
sfdx-cli 7.56.1 (core)
OS and version:
Distributor ID:	LinuxMint
Description:	Linux Mint 19.1 Tessa
Release:	19.1
Codename:	tessa
4.15.0-20-generic

Looks like a regression from the org:list updates.  We'll fix this asap.  It will help us greatly if you could run the command again appending --dev-debug and post the stack trace.  Thanks in advance!

Hello @shetzel
thanks for your quick reply.
  sfdx:core TRACE Setup child 'OrgListCommand' logger instance +0ms
  sfdx:force:org:list init version: @oclif/command@1.5.19 argv: [] +0ms
  sfdx:OrgListCommand INFO Running command [OrgListCommand] with flags [{"loglevel":"warn"}] and args [{}] +0ms
  sfdx:core TRACE Setup child 'AuthInfo' logger instance +0ms
  sfdx:core TRACE Setup child 'crypto' logger instance +0ms
  sfdx:crypto DEBUG retryStatus: undefined +0ms
  sfdx:core TRACE Setup child 'keyChain' logger instance +1ms
  sfdx:keyChain DEBUG platform: linux +0ms
  sfdx:AuthInfo INFO Updated auth info for username: aspectworks@jenkins.com +0ms
ERROR running force:org:list:  Cannot read property 'getUsername' of undefined
*** Internal Diagnostic ***

TypeError: Cannot read property 'getUsername' of undefined
    at contents.reduce (/home/ondrej/.local/share/sfdx/node_modules/salesforce-alm/dist/lib/org/orgListUtil.js:25:25)
    at Array.reduce (<anonymous>)
    at Function.readLocallyValidatedMetaConfigsGroupedByOrgType (/home/ondrej/.local/share/sfdx/node_modules/salesforce-alm/dist/lib/org/orgListUtil.js:24:36)
Outer stack:
    at Function.wrap (/home/ondrej/.local/share/sfdx/node_modules/salesforce-alm/node_modules/@salesforce/command/node_modules/@salesforce/core/lib/sfdxError.js:151:27)
    at OrgListCommand.catch (/home/ondrej/.local/share/sfdx/node_modules/salesforce-alm/node_modules/@salesforce/command/lib/sfdxCommand.js:255:67)
******

Workaround with docker:
docker run --rm -t -e \"TERM=xterm-256color\" -v /home/ondrej/.sfdx:/root/.sfdx salesforce/salesforcedx:7.54.4-slim sfdx force:org:list
Just change the path /home/ondrej/.sfdx to your .sfdx directory.

Seems to be fixed in 7.58.2-937f666ed4


text:
Sm/timeout id in sfdx error

What does this PR do?
throws an sfdxError with data property for id on timeout.
I'm making a separate WI for SDR to use error/messages from core rather than its own framework.
What issues does this PR fix or reference?
@W-10978703@
for QA...SDR is emitting error.code 1 for backward compatibility.  I think the logic on plugin-source should set incompletes to 69 based on the mdapi status...but that's worth verifying

The failing NUTs passed locally when I ran them.  Manual testing looked good as well.

authors: mshanemc shetzel

repo: forcedotcom/source-deploy-retrieve


text:
Haskell-FibonacciNo

Pull Request Type
What kind of change does this PR introduce?
[ ] Solved an issue/task
added fibonacci.hs

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out our forkcommitmerge.io website repository. The repository contain real issues that you can help to resolve or create some of your own if you see any bugs or want to add new features to the site, etc. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!

authors: izumigoto nikohoffren

repo: fork-commit-merge/fork-commit-merge


text:
removing 404

http://coq-blog.clarus.me/beginning-of-verification-for-the-parsing-of-smart-contracts.html is 404

OK, thanks for the fix!

repo: formal-land/coq-of-ocaml


text:
3.0.0-next.3 => @3.0.0-next.4 - focus jumping to end of input on edit

Bug report
This is admittedly will be a half-hearted bug report - but since it's on the next/beta branch I figured you'd want it reported anyways. I've been unable to reproduce in one of your codebox sandboxes - but am experiencing within our app and have been able to narrow it down to this release below.
https://github.com/formium/formik/compare/formik@3.0.0-next.3...formik@3.0.0-next.4
I've taken a look at the source and cannot discern anything that stands out.
Current Behavior
Type: "Brooks was here"
Move cursor to after "Brooks"
Type: "hello"
Result is: "Brooksh was hereello"
Expected behavior
Should be: "Brookshello was here"

Reproducible example

Suggested solution(s)

Additional context
We are using the new FastField component as recommended. Will continue to try to reproduce in a sandbox and attach here if narrowed down.
Your environment

Software
Version(s)

Formik

React

TypeScript

Browser

npm/Yarn

Operating System

This was a user error (me) - after refactoring all our formik fields to utilize the new apis and removing the function call inside of <Form> i.e.
<Form>{((props) => {

}))}
</Form>

the issue went away. Very happy with the refactor - if I could just get isDirty working, I'd be thrilled. Closing this issue

I noticed the same, this bug wasn't on 3.0.0-next.7 versoin but occured again on v3.0.0-next.8

authors: followbl valstu

repo: formium/formik


text:
How can I add for example 'input-lg' bootstrap class to my input?

I would like to use input with 'input-lg' bootstrap class, can I override somewhere?
Thanks.

Yes!
http://angular-formly.com/#/example/custom-types/custom-templates
http://angular-formly.com/#/example/custom-types/extending-types

Going to go ahead and close this. If you have further questions, please see http://help.angular-formly.com

Thanks @benoror!

authors: attilacsanyi benoror kentcdodds


text:
Error "has no properties in common with type 'FormlyFieldConfig'" with Angular 4.4

I'm submitting a ...  (check one with "x")
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[x] support request

Current behavior
I just copied the instructions from the README 1:1 into my application and started the app. The complete error message is:
ERROR in .../ui/src/app/routes/users/users/users.component.ts (17,5): Type '{ className: string; fieldGroup: ({ className: string; key: string; type: string; templateOptions...' has no properties in common with type 'FormlyFieldConfig'.

Expected behavior
Expected to get a form ;)
Minimal reproduction of the problem with instructions
As i said, just copied the instructions from the README
Please tell us about your environment:

Ubuntu 16.04.3 LTS
npm 5.4.0

Angular version:
4.4.0-RC.0
Language:
Typescript: 2.5.2

Args, solved it myself, sorry still learning angular2+/typescript. Error was the type definition for userFields. Instead of
userFields: FormlyFieldConfig = ...

it should be
userFields: FormlyFieldConfig[] = ...

Maybe this should be reflected in the README

repo: formly-js/ng-formly


text:
test: fix failing tests due to hardcoded pkg versions

Fix failing tests on main due to hardcoded package versions.

@colevscode this fixes the failing tests on main. I don't think we need a changeset or a version bump.

repo: formspree/formspree-js


text:
评论开启出错

当我开启disqus评论

他就这样

然后我hexo d部署上去直接GG，访问网站404
不清楚是什么情况。望解答

缩进不合格，请通过一个好的编辑器检查你的配置文件并严格按照文档配置。
On Sat, Nov 4, 2017 at 4:57 PM, 初遇 notifications@github.com wrote:

当我开启disqus评论
[image: 2]
https://user-images.githubusercontent.com/30603407/32403956-fc9095ca-c180-11e7-8258-19fcb65555d2.png
他就这样
[image: 1]
https://user-images.githubusercontent.com/30603407/32403945-d8e1234c-c180-11e7-91ff-827b7b52fb41.png
然后我hexo d部署上去直接GG，访问网站404
不清楚是什么情况。望解答
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/forsigner/fexo/issues/100, or mute the thread
https://github.com/notifications/unsubscribe-auth/AP1d4zUP0E07frkvy7F-e9psT-K0M5cGks5szCbngaJpZM4QR8Jo
.

--
Send From My Google Mail
Contact Me:
Twitter:@PotatoOnline
Facebook:Find"Yang Yuguang" (yang.yuguang.73@facebook.com)
QQ:920337808

authors: ChaBug kmahyyg

repo: forsigner/fexo


text:
Initial Review

Descriptions:
Add PR descriptions here
Fix:
Add fix/changes here

LGTM 👍

authors: cs-shivaji-kolape swapnil-spryiq


text:
Incorrect order of record @ids for Reset Scenario

https://github.com/fortinet-fortisoar/solution-pack-phishing-email-response/blob/2e79e6f820f7e4823d15ae7c8674caa848abd64e/playbooks/02 - Use Case - Phishing Email Response/Scenario - Generate Phishing Email Alert.json#L133C117-L133C117

Issue is not reproducible the the latest version of the soc simulator solution pack


text:
Client generated ID's

I am having a problem adding a new record when the responsibility is on the client to generate the ID. I have the following body of a POST request:
{
    "data": {
        "type": "markers",
        "id": "pace_avg",
        "attributes": {
          "name": "Average Pace",
          "abbrev": "avg pace",
          "desc": "the average pace achieved during the session",
          "type": "exercise",
          "sub_type": "linear-sport"
        }
    }
}

The error I get back is a 400 "the request body is invalid". The spec says that client generated ID's "may" be supported but if it does not then the error should be 403. Having looked at the code I think the aim is to support this -- although having an id in the URL causes a different error -- but I wanted to check that that is the case.
In my case I'm importing data and this client generated scheme is unique (hence no UUID, etc.).

Ok the problem seems to be related to inflection. It's almost surely user error but I'm unsure how to correct. In JSON-API's index.js#parseCreate it has identified the "type" as "marker" which is fine but in the contextRequest it is defined as "markers".

So is this a bug or not?

No. I had some bad data that was the underlying cause.

repo: fortunejs/fortune-json-api


text:
fix small_test()

Fixes #
Checklist

[x] I have read the Contribution & Best practices Guide and my PR follows them.
[x] My branch is up-to-date with the Upstream master branch.
[x] I have added necessary documentation (if appropriate)

Changes proposed in this pull request:

fix small_test() to align with https://github.com/fossasia/query-server/blob/master/app/scrapers/generalized.py#L37

@vaibhavsingh97 Is something more needed on this PR?

@cclauss Please follow best practices, Please open issue and then send PR. Rest looks good

Done.

@dgarvit Please review this proposed change.

repo: fossasia/query-server


text:
@@["!Here's Gaa To Watch!"]#!! Laois vs Offaly Live Coverage Free On final Gaa 08 June 2024 #

Laois v Offaly: Everything You Need To Know About The Joe McDonagh Cup Final
Laois v Offaly: Everything You Need To Know About The Joe McDonagh Cup Final
Finn Duffy
🔴➤ ►🌍📺📱👉 gaa finle
🔴➤ ►🌍📺📱👉 gaa finle
By Finn Duffy
Jun 08, 2024 12:15 PM
Share this article
Facebook Share
Twitter Share
Twitter Share
Twitter Share
Twitter Share
Laois are set to take on their neighbours Offaly this weekend in the final of the Joe McDonagh Cup as both sides look to grab hurling's second-tier competition and promotion to the provincial championships. Here's everything you need to know about this years Joe McDonagh Cup final Laois v Offaly.
The two sides began their championship campaign against each other in Portlaoise in April, with the O'Moore County getting the better of the Faithful County despite Offaly holding a 0-21 to 0-15 lead with less than 20 minutes to go. Laois midfielder Paddy Purcell would grab two late goals, including one in the last minute, to win his side the match 2-21 to 0-24.
READ HERE: The 10 Best Hurlers In Ireland Under The Age Of 20 In 2024
READ HERE: McManus Calls For Championship Restructure After Carlow Relegation
Laois would kick on with the momentum gained from the win and would subsequently batter batter Meath 7-29 to 1-16 in round two in Trim. Willie Maher's men would then travel to Austin Stack Park to face Kerry, where they would defeat the Kingdom 1-25 to 0-18. The O'Moore County booked their place in the Joe McDonagh final in a dominant 4-31 to 0-17 win over Down at home.
In the last day of fixtures, Laois travelled to Westmeath where they would lose for the only time in the round-robin, with the Lake men getting a 2-26 to 0-16 win in Mullingar. Despite this, Laois would still finish the round-robin at the top spot.
Meanwhile Offaly would bounce back quickly from their opening day defeat. They would welcome Westmeath to O'Connor Park in round two where the Faithful County would win 2-23 to 1-20 despite a red card to captain Jason Sampson within seconds of throw-in. Round three would see Johnny Kelly's side cruise past Meath 5-31 to 3-16 in Trim.
An impressive win 3-24 to 0-15 at home to Kerry in round four was followed by a round five win away to Down in Ballycran. Despite a late comeback effort by the home side, Offaly would win 5-23 to 3-25 in the end to round-robin second and book their place in the final.

ss
### 📺📱👉🥊 𝐂𝐋𝐈𝐂𝐊 𝐇𝐄𝐑𝐄 𝐎𝐍𝐋𝐈𝐍𝐄 𝐋𝐈𝐕𝐄 𝐒𝐓𝐑𝐄𝐀𝐌
### 📺📱👉🥊 𝐂𝐋𝐈𝐂𝐊 𝐇𝐄𝐑𝐄 𝐎𝐍𝐋𝐈𝐍𝐄 𝐋𝐈𝐕𝐄 𝐒𝐓𝐑𝐄𝐀𝐌

### 📺📱👉🥊 𝐂𝐋𝐈𝐂𝐊 𝐇𝐄𝐑𝐄 𝐎𝐍𝐋𝐈𝐍𝐄 𝐋𝐈𝐕𝐄 𝐒𝐓𝐑𝐄𝐀𝐌
### 📺📱👉🥊 𝐂𝐋𝐈𝐂𝐊 𝐇𝐄𝐑𝐄 𝐎𝐍𝐋𝐈𝐍𝐄 𝐋𝐈𝐕𝐄 𝐒𝐓𝐑𝐄𝐀𝐌

### 📺📱👉🥊 𝐂𝐋𝐈𝐂𝐊 𝐇𝐄𝐑𝐄 𝐎𝐍𝐋𝐈𝐍𝐄 𝐋𝐈𝐕𝐄 𝐒𝐓𝐑𝐄𝐀𝐌
### 📺📱👉🥊 𝐂𝐋𝐈𝐂𝐊 𝐇𝐄𝐑𝐄 𝐎𝐍𝐋𝐈𝐍𝐄 𝐋𝐈𝐕𝐄 𝐒𝐓𝐑𝐄𝐀𝐌

### 📺📱👉🥊 𝐂𝐋𝐈𝐂𝐊 𝐇𝐄𝐑𝐄 𝐎𝐍𝐋𝐈𝐍𝐄 𝐋𝐈𝐕𝐄 𝐒𝐓𝐑𝐄𝐀𝐌
### 📺📱👉🥊 𝐂𝐋𝐈𝐂𝐊 𝐇𝐄𝐑𝐄 𝐎𝐍𝐋𝐈𝐍𝐄 𝐋𝐈𝐕𝐄 𝐒𝐓𝐑𝐄𝐀𝐌

☝
☝
☝

repo: foundation/foundation-sites


text:
^^The Secret to Getting Free Robux Revealed Generator Tips and Tricks [ ZXZ]

ˏˋ°•*⁀➷The Secret to Getting Free Robux Revealed Generator Tips and Tricks [ ZXZ]
Unlock Unlimited Free Robux Codes: The Ultimate Guide to Dominating Roblox Without Spending a Dime!
Are you tired of constantly grinding in Roblox to earn enough Robux for your dream items and upgrades? Do you want to level up your gaming experience without breaking the bank? Look no further, because we have the ultimate solution for you - free Robux codes!
🔴📺📱👉 Click here free robux codes
🔴📺📱👉 Click here free robux codes
In this comprehensive guide, we will reveal the top secret methods to unlocking unlimited free Robux codes that will revolutionize your Roblox gameplay. Say goodbye to the days of empty wallets and hello to a world of endless possibilities in the Roblox universe.
But wait, how exactly can you get your hands on these coveted free Robux codes? It's simple - all you need to do is follow our step-by-step instructions and you'll be rolling in Robux in no time. From completing quick and easy surveys to participating in sponsored offers, there are a plethora of legitimate ways to earn free Robux without spending a single penny.
Not convinced yet? Well, how about this - we have insider tips and tricks from top Roblox players who have mastered the art of earning free Robux. Learn from the best and take your Roblox game to the next level with their expert advice and strategies.
But that's not all! We also have exclusive access to special events and promotions where you can snag free Robux codes before anyone else. Stay ahead of the game and stay tuned to our updates for the latest opportunities to score big in Roblox.
So what are you waiting for? Stop wasting your hard-earned money on Robux and start earning them for free today. With our ultimate guide to free Robux codes, you'll never have to worry about running out of Robux again. Get ready to dominate Roblox like never before and unleash your full gaming potential. Click now to unlock the secrets to unlimited free Robux codes and become a Roblox legend!"
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Robux
🔴📺📱👉 Click here Free Robux


text:
fix: reduce CALLER balance before executing tests

Closes https://github.com/foundry-rs/foundry/issues/2390
Ran this against some repos locally without issues, want to make sure CI passes before merging though

Failure looks unrelated to this change?

repo: foundry-rs/foundry


text:
Kineticist Single Gate 2 Action Elemental Blast not getting con mod or impulse junction at level 1

Hello, one of players is playing as a single gate fire kineticist, and we noticed today that switching to two actions on elemental blast does not change the damage to d8s and does not add the CON modifier. I have disabled all modules and completely rebuilt the character, and the issue persists. Just to make sure, I've reread the class entry and the 2-action version of EB does qualify for this impulse junction. The status bonus is unrelated to that junction, but I imagine there's just something wrong with a rule element somewhere.
Other information about the character is Awakened Animal Ancestry, Running Animal Heritage, Magical Experiment Background (thoughtsense).
Foundry 12.330 and PF2e 6.2.1

Pathmuncher?

Working fine for me

If this actor was initially imported with Pathmuncher you will want to make a new actor entirely and build from scratch without Pathmuncher. Also, double check that your player actually has two actions set for the blast

Yeah I think she did use Pathmuncher initially. When I remade the character from scratch on a new actor instead of a duplicate, it worked fine. Thanks for telling me this and giving me another reason to tell them I'm uninstalling Pathmuncher lol.

authors: TikaelSol mgoldstein322 stwlam


text:
Damage formula localization incorrect

Hi there,
looks like the damage formula default label for inline rolls currently looks rather strange if () are used.
That's how we localize persistent damage:

That's how the inle roll looks like: @Damage[(1d4 + @item.system.damage.dice)[persistent,cold]]
That's how the default label looks like:

Take a look at the ( and ).
There is one ( missing at the beginning of the label and one ) missing at the end.


text:
Restore Paladin REs to the Combined Shining Oath Feat

Closes https://github.com/foundryvtt/pf2e/issues/11597.
Also re-input the feat's text from CRBv4 printing and put the benefits for the various causes in the order of that description.

Check errata

Eye r dum and missed that; still rearranged the order of the various bonuses.

authors: avagdumortesin stwlam


text:
Ambiguous wording in the MCAP File Format Specification

The following wording in the specification of a Chunk is a bit ambiguous -

All messages in the chunk must reference channels recorded earlier in the file (in a previous chunk or earlier in the current chunk).

It may be interpreted as "all channels must be in a chunk (previous or current)". However, as far as I'm aware, this is not necessary. Channels can be logged standalone outside a chunk, in the Data section. Please correct me if I'm wrong.

Thanks for the report @sanjaynarayanan-brt  - the specification currently allows channel, schema, or message records both in chunks and directly in the data section within the same MCAP. however, most MCAP reader implementations won't handle this correctly. I will amend the spec to disallow this case.

@james-rms Thanks!
I'm not sure what MCAP reader runs under the hood in Foxglove Studio (specifically for plots), but we write channels and schemas directly into the data section and put messages into chunks, and that seems to work great with plots.

authors: james-rms sanjaynarayanan-brt

repo: foxglove/mcap


text:
readability-api

update to last version which use requests_oauthlib to be python3 compliant - need to update my_readability.py to be able to connect to the readability service again.

6e12fb3b437980bac4b12361616dc950a9cd4faa

repo: foxmask/django-th


text:
hw-*

Ping @newhoggy
I'm not sure which hw package is causing this issue but it seems that trying to build with hw-string-parse-0.0.0.3 instead of 0.0.0.2 fails.
> /tmp/stackage-build8$ stack unpack hw-succinct-0.0.0.14
Unpacked hw-succinct-0.0.0.14 to /tmp/stackage-build8/hw-succinct-0.0.0.14/
> /tmp/stackage-build8/hw-succinct-0.0.0.14$ runghc -clear-package-db -global-package-db -package-db=/var/stackage/work/builds/nightly/pkgdb Setup configure --package-db=clear --package-db=global --package-db=/var/stackage/work/builds/nightly/pkgdb --libdir=/var/stackage/work/builds/nightly/lib --bindir=/var/stackage/work/builds/nightly/bin --datadir=/var/stackage/work/builds/nightly/share --libexecdir=/var/stackage/work/builds/nightly/libexec --sysconfdir=/var/stackage/work/builds/nightly/etc --docdir=/var/stackage/work/builds/nightly/doc/hw-succinct-0.0.0.14 --htmldir=/var/stackage/work/builds/nightly/doc/hw-succinct-0.0.0.14 --haddockdir=/var/stackage/work/builds/nightly/doc/hw-succinct-0.0.0.14 --flags=
Configuring hw-succinct-0.0.0.14...
Warning: 'ghc-options: -rtsopts' has no effect for libraries. It should only
be used for executables.
Warning: 'ghc-options: -with-rtsopts' has no effect for libraries. It should
only be used for executables.
> /tmp/stackage-build8/hw-succinct-0.0.0.14$ runghc -clear-package-db -global-package-db -package-db=/var/stackage/work/builds/nightly/pkgdb Setup build
Building hw-succinct-0.0.0.14...
Preprocessing library hw-succinct-0.0.0.14...
[1 of 1] Compiling HaskellWorks.Data.Succinct ( src/HaskellWorks/Data/Succinct.hs, dist/build/HaskellWorks/Data/Succinct.o )

src/HaskellWorks/Data/Succinct.hs:10:1: error:
    Failed to load interface for ‘HaskellWorks.Data.Succinct.BalancedParens’
    Perhaps you meant
      HaskellWorks.Data.BalancedParens (needs flag -package-key hw-balancedparens-0.1.0.0)
    Use -v to see a list of the files searched for.

src/HaskellWorks/Data/Succinct.hs:11:1: error:
    Failed to load interface for ‘HaskellWorks.Data.Succinct.NearestNeighbour’
    Use -v to see a list of the files searched for.

src/HaskellWorks/Data/Succinct.hs:12:1: error:
    Failed to load interface for ‘HaskellWorks.Data.Succinct.RankSelect’
    Use -v to see a list of the files searched for.
curators@stk-build-i-2a9f06b4:~/stackage/automated$

It wasn't (only) hw-string-select, I ended up holding back all of the packages to the ones in the previous nightly:
        - hw-bits < 0.4
        - hw-conduit < 0.1
        - hw-prim < 0.4
        - hw-rankselect < 0.5
        - hw-string-parse < 0.0.0.3

I was doing some refactoring yesterday that included breaking changes.
How might I fix this issue and prevent it from happening in future when I need to make breaking changes again?

Also, I'm deprecating hw-succinct.  The code has been split up into other libraries.

I think the problem might be with hw-succinct.  I'm updating it now and see what happens.

If you have one stack project including all packages you can implement, test, and release everything together.

I’ve pushed a new version of hw-succinct. Hopefully that fixes the issue?

Actually not pushed yet.  I've kicked off a new build though: https://circleci.com/gh/haskell-works/hw-succinct  Should push when done.  I'll check tomorrow morning.

I've also set up an hw-all project, as you suggest: https://github.com/haskell-works/hw-all

@newhoggy the issue does seem to be fixed. Thanks!

Hi Adam,
I’ve pushed a new version of hw-succinct. Hopefully that fixes the issue?
Cheers,
-John

On Mon, 24 Oct 2016 at 09:52 Adam Bergmark notifications@github.com wrote:

If you have one stack project including all packages you can implement,
test, and release everything together.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fpco/stackage/issues/2010#issuecomment-255620497, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAD2JtG7Ax62qbt64iBMmHPWwzEuFgRBks5q2-UhgaJpZM4KeHfX
.

Hi Adam,
I did some refactoring yesterday, which included breaking changes.
Is there a way I can edit the bounds of older versions on hackage?
Cheers,
-John
On Mon, 24 Oct 2016 at 00:53 Adam Bergmark notifications@github.com wrote:

It wasn't (only) hw-string-select, I ended up holding back all of the
packages to the ones in the previous nightly:
    - hw-bits < 0.4
    - hw-conduit < 0.1
    - hw-prim < 0.4
    - hw-rankselect < 0.5
    - hw-string-parse < 0.0.0.3

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fpco/stackage/issues/2010#issuecomment-255589927, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAD2JqVnmrHbp0osOyW4qGOrvOi4T19Hks5q22a_gaJpZM4KeHfX
.

@newhoggy yes! on the package page click "edit package information" > Cabal file metadata > pick version > make edits, or go to e.g. https://hackage.haskell.org/package/aeson-1.0.2.1/aeson.cabal/edit directly

authors: DanBurton bergmark newhoggy

repo: fpco/stackage


text:
Is the gh-pages branch for MkDocs supposed to be created manually?

Question
I'm trying to setup a new project and noticed that a gh-pages branch wasn't created automatically at any point for making auto MkDocs possible. The documentation doesn't specify when/how the branch is created so I've become a bit confused on whether or not I was supposed to create it myself and then run a specific make command or similar to get the docs published on the remote repo. What are the proper steps here? Thanks!

Thanks for raising this! I will update the documentation to better reflect what's happening.

authors: ariffjeff fpgmaas

repo: fpgmaas/cookiecutter-poetry


text:
bump premailer version

This gem relies on a very old version of premailer, namely one that includes hpricot whose hpricot_slate_method_added magic causes issues with sorbet. Please update this dependency to use a more recent version of premailer.

This is the dependency definition:
https://github.com/fphilipe/premailer-rails/blob/v1.11.1/premailer-rails.gemspec#L24
premailer is currently at 1.11.1. If you do a fresh install of premailer-rails, it will install the latest premailer version. Thus, you should be able to simply run bundle update premailer to get a newer version of premailer in your project.

Thank you for the quick and educational reply, new ecosystem I'm working in.

repo: fphilipe/premailer-rails


text:
task collection 1.x from pypi

Preliminary requirement: we need a shared folder that is readable and executable by the fractal user, let it be FRACTAL_ROOT_DIR
from PyPI
in a subprocess...

create dedicated venv in FRACTAL_ROOT_DIR/<pkg>_<version>
install package in venv
extract manifest by /venv/python -c "import <pkg>; print(pkg.__manifest__)"
load all tasks exposed in manifest

default behaviour
cd $FRACTAL_ROOT_DIR
PKG_DIR=$PKG_NAME_$PKG_VERSION
mkdir $PKG_DIR
cd $PKG_DIR
python -m venv venv (or similar for conda and the like)
source /venv/bin/activate (or similar)
(venv) pip install $PKG_NAME==$PKG_VERSION
(venv) python -c "import $PKG_NAME; print($PKG_NAME.__manifest__)" > /tmp/fractal/pkg_name_version.manifest.json

we read the output of the last command and access the manifest from within the server
the resulting tasks will have

source = pypi:fractal-tasks-core==0.2.3
command =  /path/to/venv/python path/to/module.py

custom behaviour (TODO)
We keep the folder structure with the following pseudo-script
cd $FRACTAL_ROOT_DIR
PKG_DIR=$PKG_NAME_$PKG_VERSION
mkdir $PKG_DIR
cd $PKG_DIR

the user can provide a custom initialisation / installation script, which needs to output

how to call the dedicated python interpreter
the manifest

from FRACTAL_ROOT_DIR/<userdir>/<taskdir>/
TODO

@tcompa can you please write here the command you would use to start an env with conda pls?

conda create --prefix /tmp/MY_ENV python==3.8 --quiet --yes
conda activate /tmp/MY_ENV
pip install fractal-tasks-core==0.2.6

But notice that there is no special reason to use conda, for the default modules (to be made available for all users). You can go on with standard venvs if you prefer.

Also note that the previous script creates a 3G folder (that would be only 200M before installing the tasks).

conda create --prefix /tmp/MY_ENV python==3.8 --quiet --yes
conda activate /tmp/MY_ENV
pip install fractal-tasks-core==0.2.6

But notice that there is no special reason to use conda, for the default modules (to be made available for all users). You can go on with standard venvs if you prefer.

I actually prefer venv, but we need a way to specify the python version. I can write some fallback logic if needed, i.e.,

try venv
if it doesn't work try pyenv + vnev
if it doesn't work try conda

authors: jacopo-exact tcompa


text:
[ngio] Refactor masked_loading_wrapper logic to do relabeling in the masking step

I have revisited how we handle masking & relabeling to fix #785 . For the moment, I do the relabeling in segment_ROI. In ngio, we'll want to do this in the wrapper class that handles the masking (currently masked_loading_wrapper). The main reason:

Current approach doesn't 100% guarantee consecutive labels. Within the cellpose task, there could be labels that are taken into account for relabeling but are masked away afterwards. That's very unlikely to be an issue, because we set the background to 0 in the input image. But the mock testing ignores the input

Also, it will be nicer if that's functionality that comes with the IO package, instead of everyone that writes a function that creates labels having to take care of it


text:
AUTH_COOKIE_NAME error in npm run build

"AUTH_COOKIE_NAME" is not exported by "$env/static/private", imported by "src/routes/auth/logout/+server.js".
file: /xxx/server_05_to_use_apache/fractal-web/src/routes/auth/logout/+server.js:4:1
2: import { logout } from '$lib/server/api/v1/auth_api'
3: import {
4:   AUTH_COOKIE_NAME,
     ^
5:   AUTH_COOKIE_DOMAIN,
6:   AUTH_COOKIE_PATH,
error during build:
RollupError: "AUTH_COOKIE_NAME" is not exported by "$env/static/private", imported by "src/routes/auth/logout/+server.js".
    at error (file:///xxx/server_05_to_use_apache/fractal-web/node_modules/rollup/dist/es/shared/node-entry.js:2125:30)
    at Module.error (file:///xxx/server_05_to_use_apache/fractal-web/node_modules/rollup/dist/es/shared/node-entry.js:13340:16)
    at Module.traceVariable (file:///xxx/server_05_to_use_apache/fractal-web/node_modules/rollup/dist/es/shared/node-entry.js:13725:29)
    at ModuleScope.findVariable (file:///xxx/server_05_to_use_apache/fractal-web/node_modules/rollup/dist/es/shared/node-entry.js:12240:39)
    at FunctionScope.findVariable (file:///xxx/server_05_to_use_apache/fractal-web/node_modules/rollup/dist/es/shared/node-entry.js:6980:38)
    at ChildScope.findVariable (file:///xxx/server_05_to_use_apache/fractal-web/node_modules/rollup/dist/es/shared/node-entry.js:6980:38)
    at Identifier.bind (file:///xxx/server_05_to_use_apache/fractal-web/node_modules/rollup/dist/es/shared/node-entry.js:8130:40)
    at CallExpression.bind (file:///xxx/server_05_to_use_apache/fractal-web/node_modules/rollup/dist/es/shared/node-entry.js:5743:28)
    at CallExpression.bind (file:///xxx/server_05_to_use_apache/fractal-web/node_modules/rollup/dist/es/shared/node-entry.js:9659:15)
    at ExpressionStatement.bind (file:///xxx/server_05_to_use_apache/fractal-web/node_modules/rollup/dist/es/shared/node-entry.js:5747:23)

I think this is because .env.developement is not being used.

I think this is because .env.developement is not being used.

I confirm. If I move all its content to .env, then the build succeeds.

repo: fractal-analytics-platform/fractal-web


text:
[v0.3] Job submission and monitoring

Placeholder issue for all kind of planning/discussion on:

How to run a workflow, for given I/O datasets and possibly with additional parameters.
How to visualize a job list? What should be in there? Where should it appear (per-user? per-project? per-workflow?)?
...

Replaced by figma discussion


text:
Thread solids invalid

Thread solids are not valid, and consequently fail boolean operations.
>>> import cqparts
>>> thread = cqparts.types.threads.iso_262.ISO262Thread().make(5)
>>> thread.val().wrapped.isValid()
False

solids can be cleaned up using the method(s) described here, but they're not always successful.
slight variations initially yield an unclosed solid, but are fixed with sewShape(), for example
>>> import cqparts
>>> thread = cqparts.types.threads.iso_262.ISO262Thread(pitch=0.7).make(3)
>>> thread.val().wrapped.isValid()
True

Exception
code modified to crash more gracefully by raising:
SolidValidityError: created thread solid cannot be made watertight

Is there a way to detect when a thread is invalid so that fixes could be applied conditionally and then rechecked? I know how to check geometry from the GUI, but I've never done it from a script.

@jmwright
There is a section in the code to do exactly that, but it's only working some of the time (less than half)
https://github.com/fragmuffin/cqparts/blob/develop/src/cqparts/types/threads/base.py#L251-L260
when building a dodgy thread at the moment, you'll see:
thread shape not valid
new thread STILL not valid

on the console... context is obvious after reading the above linked code

These tools might be a clue:
https://www.freecadweb.org/wiki/Mesh_FillHoles
https://www.freecadweb.org/wiki/Mesh_FillInteractiveHole

This bug is making thread-building completely unmanageable.
It's making building a very painful and error-prone experience... the presence of thread faces makes cqparts very unstable.
Mitigated by Simplifying to Cylinder
For the time being, I've converted the base Thread type to a Part so I can exploit the _simple=True flag, which causes the make_simple() method to build the part's .local_obj as opposed to .make(). (see f1e98fe)
In other words, by default, threads are not generated.
Instead they are replaced with a cylinder with the thread's outer radius.
Workaround
If you'd like to play with real threads, you can turn off default simplification with any of...
import cqparts
from cqparts.display import display
from cqparts.params import Boolean
from cqparts.fasteners.base import FastenerMalePart
from cqparts.solidtypes.threads import base

# --- an individual part
screw = FastenerMalePart()
screw.thread._simple = False
display(screw)

# --- all threads by default
base.Thread._simple.default = False
# you'll have to re-define the thread type, because the default thread
# was instantiated before the above change was made
screw = FastenerMalePart(
    thread=('iso262', {
        'diameter': 3.0,
        'pitch': 0.7,
    }),
)
display(screw)

# --- all threads by default (by environment variable)
# because the above way is messy... you can set an environment variable:
#       CQPARTS_COMPLEX_THREADS=yes
display(FastenerMalePart())  # default of _simple is False at import time

none of the above methods are permanent, please keep this in mind if you're planning a future-proofed script.
Fix Delay
I also won't have time to fix this for the initial release... but it's very high on the priorities list after v0.2

example of the simplified thread...

Test created to raise failure: test and catalogue
A variety of thread dimensions are created, most of which currently fail to create a watertight object.
Error example
======================================================================
ERROR: test_triangular_4x1_040 (cqparts.utils.test.CatalogueTest_thread_catalogue)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/nymphii/prj/cqparts/tests/../src/cqparts/utils/test.py", line 147, in test_meth
    obj.build()
  File "/home/nymphii/prj/cqparts/tests/../src/cqparts/part.py", line 91, in build
    self.local_obj  # force object's construction, but don't do anything with it
  File "/home/nymphii/prj/cqparts/tests/../src/cqparts/part.py", line 113, in local_obj
    value = self.make()
  File "/home/nymphii/prj/cqparts/tests/../src/cqparts_fasteners/solidtypes/threads/base.py", line 352, in make
    "created thread solid cannot be made watertight"
SolidValidityError: created thread solid cannot be made watertight

Tests skipped until this issue is closed:
test_ball_screw_10x1_012 (cqparts.utils.test.CatalogueTest_thread_catalogue) ... skipped 'skipped until #1 is fixed'
test_ball_screw_10x3_013 (cqparts.utils.test.CatalogueTest_thread_catalogue) ... skipped 'skipped until #1 is fixed'
...
test_triangular_4x4_042 (cqparts.utils.test.CatalogueTest_thread_catalogue) ... skipped 'skipped until #1 is fixed'
test_triangular_4x5_043 (cqparts.utils.test.CatalogueTest_thread_catalogue) ... skipped 'skipped until #1 is fixed'

Task

[ ] remove FIXME from test_fasteners_thread.py

Task

[ ] remove warning about this fault from cqparts_fasteners README.rst

authors: fragmuffin jmwright

repo: fragmuffin/cqparts