text:
Issue with timepicker library

Hey I been have a issue with timepicker on kivymd library so I came here hoping someone can help me out So basically the issue is when i try use the timepicker a error appears saying the textcolor on object has to be declared in string format but i dont now how change that (im a student and this is my final paper project and is for mobile devices maybe not run as well on desktop)
Code and Logs
from kivy.lang import Builder
from kivy.uix.screenmanager import Screen, ScreenManager
from kivy.properties import ObjectProperty
from kivymd.app import MDApp
from kivy.core.window import Window
from kivymd.uix.boxlayout import MDBoxLayout
from kivymd.uix.card import MDCard
from kivymd.uix.label import MDLabel
from kivymd.uix.button import MDRoundFlatButton
from kivymd.uix.button import MDIconButton
from kivymd.uix.textfield import MDTextField
from kivymd.uix.button import MDRaisedButton
from kivy.properties import BooleanProperty
from kivy.clock import Clock
from kivy.uix.textinput import TextInput
from kivymd.uix.pickers import MDTimePicker

class MyScreenManager(ScreenManager):
    pass

class JanelaPrincipal(Screen):
    pass

# Cadastro
class Cadastro(Screen):
    pass

class Login(Screen):
    pass

class Janela3(Screen):
    pass

class Janela4(Screen):
    pass

class Janela5(Screen):
    pass

class Principal(Screen):
    pass

class Janela7(Screen):
    pass

class Janela8(Screen):
    pass

class Janela9(Screen):
    pass

class Janela10(Screen):
	pass

class Janela11(Screen):
	pass

class MainApp(MDApp):
    def build(self):
    	return Builder.load_file("newfile.kv")

    def add_card_and_show_time_picker(self, **kwargs):
        card = MDCard(
            size_hint=(None, None),
            size=("280dp", "180dp"),
            pos_hint={"center_x": 0.5},
            orientation='vertical',
            md_bg_color="#EADFFE",
            line_color="black",
        )

        card_layout = MDBoxLayout(
            orientation='vertical',
        )
        card.add_widget(card_layout)
        card_layout.add_widget(MDBoxLayout(size_hint_y=None, height="10dp"))
        card_box = self.root.get_screen('principal').ids.card_box
        card_box.add_widget(card)

        card_button = MDRoundFlatButton(
            text="Escolher horário",
            pos_hint={"center_x": 0.5, "center_y": 0.8},
            md_bg_color="#B186FF",
            line_color='#8D55F8',
            text_color="black",
            on_release=self.show_time_picker,
        )
        card_box.add_widget(card_button)

    def show_time_picker(self, intance, **kwargs):
        MDTimePicker(
    		primary_color="white",
    		accent_color="blue",
    		text_button_color="white",
    		text_color="black",
		).open()

    def on_time_selected(self):
        print("Hora selecionada:", time)

if __name__ == '__main__':
    MainApp().run()

```Kivy File
MyScreenManager:
    JanelaPrincipal:
    Cadastro:
    Login:
    Janela3:
    Janela4:
    Janela5:
    Principal:
    Janela7:
    Janela8:
    Janela9:
    Janela10:
    Janela11:

<JanelaPrincipal>:
	#tela provisoria
	   name: "janelaprincipal"
    FloatLayout:
    MDCard:
       	md_bg_color:'#c2a3fd'
        size_hint_x:50
        size_hint_y:50
        pos_hint:{'center_x' : .50, 'center_y': .5}

    MDIconButton:
        icon:"logoofc.png"
        icon_size:"250dp"
        pos_hint:{'center_x' : .50, 'center_y': .6}
    on_release: app.root.current = "login"
   	    #q gambiarra mal feita vai ficar assim msm
    Image:
        source:"ChildCare.png"
        size_hint_x:1
        size_hint_y:.3
        halign:'center'
        pos_hint:{'center_x' : .5, 'center_y': .37}

<Cadastro>:
    name: 'cadastro'
    FloatLayout:
        MDCard:
            md_bg_color:'#c2a3fd'
            size_hint_x:50
            size_hint_y:50

        MDIconButton:
            icon:'seta-esquerda.png'
            pos_hint:{'center_x' : .08, 'center_y': .95}
            on_release: app.root.current = "login"
        Image:
            source:'logov2.png'
            pos_hint:{'center_x' : .5, 'center_y': .85}
            size_hint_x: .30
            size_hint_y: .30

        FitImage:
            source:'Cadastre-se.png'
            halign: "center"
            pos_hint: {'center_x': .5, 'center_y': 0.75}
            size_hint_x: .45
            size_hint_y: .03

        MDTextField:
            size_hint_x: .9
            hint_text: 'Digite seu nome'
            mode: "round"
            pos_hint: {'center_x': .5, 'center_y': 0.65}
            fill_color_normal: '#EBE0FF'
            line_color_normal: "white"

 #email
        MDTextField:
            size_hint_x: .9
            icon_left: "email-outline"
            mode: 'round'
            fill_color_normal: '#EBE0FF'
            hint_text: 'Email'
            pos_hint: {'center_x': .5, 'center_y': 0.55}
            line_color_normal: "white"

#senha
        MDTextField:
            id: password_input
            size_hint_x: .9
            icon_left: 'lock-outline'
            hint_text: 'Digite a senha'
            mode: 'round'
            max_text_length: 10
            password: True
            multiline: False
            pos_hint: {'center_x': .5, 'center_y': 0.45}
            line_color_normal: "white"
            fill_color_normal: '#EBE0FF'

        MDTextField:
            id: confirm_password_input
            size_hint_x: .9
            icon_left: 'lock-outline'
            hint_text: 'Confirme a senha'
            mode: 'round'
            max_text_length: 10
            password: True
            multiline: False
            pos_hint: {'center_x': .5, 'center_y': 0.35}
            line_color_normal: "white"
            fill_color_normal: '#EBE0FF'

        MDFillRoundFlatButton:
            font_size: 40
            text:'Criar conta'
            pos_hint:{'center_x' : .5, 'center_y': .23}
            size_hint_x: .2
            md_bg_color:'#EBE0FF'
            text_color:'black'
            on_release: app.root.current = "principal"
<Login>:
	#tela de login
	name:"login"
	FloatLayout:
    	MDCard:
        	md_bg_color:'#c2a3fd'
        	size_hint_x:50
        	size_hint_y:50
        	pos_hint:{'center_x' : .50, 'center_y': .5}
    #ordem na linha de codigo toda bagunçada arrumo dps

    Image:
        source:'logov2.png'
        pos_hint:{'center_x' : .5, 'center_y': .75}
        size_hint_x: .35
        size_hint_y: .35

    MDTextField:
        size_hint_x: .90
        icon_left: "email-outline"
        mode:'round'
        fill_color_normal:'#EBE0FF'
        hint_text: 'Email'
        pos_hint:{'center_x' : .5, 'center_y': .53}
        line_color_normal: "white"

    MDTextField:
        id: password_input
        size_hint_x: .9
        icon_left: 'lock-outline'
        hint_text: 'Digite a senha'
        mode: 'round'
        max_text_length: 10
        password: True
        multiline: False
        pos_hint: {'center_x': .5, 'center_y': 0.45}
        line_color_normal: "white"
        fill_color_normal: '#EBE0FF'

    MDFillRoundFlatButton:
    	text:'Entrar'
    	font_size: 45
    	pos_hint:{'center_x' : .5, 'center_y': .30}
        size_hint_x: .3
        md_bg_color:'#EBE0FF'
        text_color:'black'
    	on_release: app.root.current = "principal"

    MDFillRoundFlatButton:
        font_size:45
        text: "Esqueci minha senha"
        md_bg_color:'#c2a3fd'
        text_color:'black'
        pos_hint:{'center_x' : .5, 'center_y':.4}
        custom_color: "white"
        size_hint_x: .3
    	on_release: app.root.current = "janela3"

    MDFillRoundFlatButton:
    	font_size: 45
    	text:'Criar conta'
    	pos_hint:{'center_x' : .5, 'center_y': .23}
    	size_hint_x: .3
        md_bg_color:'#EBE0FF'
        text_color:'black'
    	on_release: app.root.current = "cadastro"

<Janela3>:
	# tela de esqueci a senha
	name:"janela3"
	FloatLayout:
	    MDCard:
        	md_bg_color:'#c2a3fd'
        	size_hint_x:50
        	size_hint_y:50
        	pos_hint:{'center_x' : .50, 'center_y': .5}

    MDFillRoundFlatButton:
    	text:'obter codigo de recuperação'
    	pos_hint:{'center_x' : .5, 'center_y': .23}
        size_hint_x: .15
        size_hint_y: .05
        md_bg_color:'#FFFFFF'
        text_color:'black'
        on_release: app.root.current = "janela4"

   	     #precisa dos modelo e os dados problema segue ate a <Janela5>

<Janela4>:
    name:"janela4"
    FloatLayout:
	    MDCard:
        	md_bg_color:'#c2a3fd'
        	size_hint_x:50
        	size_hint_y:50
        	pos_hint:{'center_x' : .50, 'center_y': .5}

    MDFillRoundFlatButton:
    	text:'Recuperar senha'
    	pos_hint:{'center_x' : .5, 'center_y': .23}
        size_hint_x: .15
        size_hint_y: .05
        md_bg_color:'#FFFFFF'
        text_color:'black'
        on_release: app.root.current = "janela5"

#sem informacao

<Janela5>:
    name:"janela5"
    FloatLayout:
	    MDCard:
        	md_bg_color:'#c2a3fd'
        	size_hint_x:50
        	size_hint_y:50
        	pos_hint:{'center_x' : .50, 'center_y': .5}
    MDFillRoundFlatButton:
    	text:'voltar para a tela de login'
    	pos_hint:{'center_x' : .5, 'center_y': .23}
        size_hint_x: .15
        size_hint_y: .05
        md_bg_color:'#FFFFFF'
        text_color:'black'
        on_release: app.root.current = "login"

<Principal>:
#Janelas principais do app
    name: "principal"
    MDScreen:
        #nao encontrei nenhuma maneira de aumentar os icones de baixo :(

        MDBottomNavigation:
            selected_color_background: "#c2a3fd"
            #text_color_active: "lightgrey" linha inutil

            MDBottomNavigationItem:
    		# Aba da Criança
    			name: 'screen 2'
    			icon: 'crianca.png'
    			md_bg_color: '#C2A3FD'
    			MDLabel:
        			halign: 'center'
        			text: "Conteúdo da aba da criança"

			MDBottomNavigationItem:
    		# Aba Alimentação
    			name: 'screen 1'
    			icon: 'aliment.png'
    			md_bg_color: '#c2a3fd'
    			BoxLayout:
        			orientation: 'vertical'
        			ScrollView:
            			MDBoxLayout:
                			id: card_box
                			orientation: 'vertical'
                			spacing: dp(10)
                			adaptive_height: True
        			MDIconButton:
            			icon:"plus"
            			icon_color:"00000"
            			pos_hint: {"center_x": .9, "center_y": .20}
            			md_bg_color:'#8D55F8'
            			on_release:	app.add_card_and_show_time_picker()

			MDBottomNavigationItem:
    			name: 'screen 3'
    			icon: 'calendario.png'
    			md_bg_color: '#C2A3FD'
    			MDLabel:
        			halign: 'center'
     		   	text: "Conteúdo da aba de calendário"

			MDBottomNavigationItem:
    		# Aba de Vacinação
    			name: 'screen 4'
    			icon: 'vacina.png'
    			md_bg_color: '#C2A3FD'
    			BoxLayout:
        			orientation: 'vertical'
        			FitImage:
       		 		source: "registro.png"
        				size_hint_y: .043942
        				size_hint_x: .62
        				pos_hint: {'center_x': .5, 'center_y': .70}
        			ScrollView:
            			size_hint: (1, 1)
            			do_scroll_x: False
            			do_scroll_y: True
            			MDList:
                			id: list_container
                			padding: dp(10)
                			spacing: dp(10)
                			size_hint_y: None
                			height: self.minimum_height

                			Image:
                   		 	source: 'carteira.png'
                    			size_hint_y: None
                    			height: dp(380)
                    			allow_stretch: True
                    			pos_hint: {'center_x': .5}

                			Image:
                    			source: 'carteira2.png'
                    			size_hint_y: None
                    			height: dp(380)
                    			allow_stretch: True
                    			pos_hint: {'center_x': .5}

                			Image:
                    			source: 'carteira3.png'
                    			size_hint_y: None
                    			height: dp(380)
                    			allow_stretch: True
                    			pos_hint: {'center_x': .5}
                            Image:
                    			source: 'carteira4.png'
                    			size_hint_y: None
                    			height: dp(380)
                    			allow_stretch: True
                    			pos_hint: {'center_x': .5}

                            Image:
                    			source: 'carteira5.png'
                    			size_hint_y: None
                    			height: dp(380)
                    			allow_stretch: True
                    			pos_hint: {'center_x': .5}

            MDBottomNavigationItem:
                name: 'screen 5'
                icon: 'logoicon.png'
                md_bg_color: '#C2A3FD'
                MDScreen:
                	MDLabel:
                    	text: "Olá usuário"
                    	halign: "center"
                    	pos_hint:{'center_x' : .5, 'center_y': .92}
                    	font_size: 55
                	Image:
                    	source:'logoofc.png'
                    	size_hint_x:.25
                    	size_hint_y:.25
                    	pos_hint:{'center_x' : .5, 'center_y': .84}

                	MDLabel:
                    	text: "Central da conta"
                    	halign: "center"
                    	pos_hint:{'center_x' : .5, 'center_y': .75}
                    	font_size: 65

         #nao me orgulho de codar isso mas funciona ent...

                	FitImage:
                    	source:'widget.png'
                    	pos_hint: {'center_x': .49, 'center_y': .60}
                    	size_hint_y: .25
                    	size_hint_x: 1

                #informacoes da conta
                	MDFlatButton:
                    	md_bg_color:"#00000000"
                    	pos_hint:{'center_x' : .5, 'center_y': .70}
                    	size_hint_x: .99
                    	size_hint_y: .01
                #Redefinir senha
                	MDFlatButton:
                    	md_bg_color:"#00000000"
                    	pos_hint:{'center_x' : .5, 'center_y': .65}
                    	size_hint_x: .99
                    	size_hint_y: .01
                    	on_release:
   	                 	app.root.current = "janela3"

                #compartilhar esse app
                	MDFlatButton:
                    	md_bg_color:"#00000000"
                    	pos_hint:{'center_x' : .5, 'center_y': .60}
                    	size_hint_x: .99
                    	size_hint_y: .01

               #Sair da conta
                	MDFlatButton:
                    	md_bg_color:"#00000000"
                    	pos_hint:{'center_x' : .5, 'center_y': .55}
                    	size_hint_x: .99
                    	size_hint_y: .01
                    	on_release: app.root.current = "login"

                #fale conosco
                	MDFlatButton:
                    	md_bg_color:"#00000000"
                    	pos_hint:{'center_x' : .5, 'center_y': .50}
                    	size_hint_x: .99
                    	size_hint_y: .01
                    	on_release:

                	MDFlatButton:
                    	text: "Desenvolvedores"
                   	 theme_text_color: "Custom"
                 	   text_color: "black"
                    	pos_hint:{'center_x' : .17, 'center_y': .45}
                    	on_release: app.root.current = "janela9"

   	         	MDFlatButton:
   	             	text:"Versão 0.1"
   	             	text_color: "black"
   	             	pos_hint:{'center_x' : .9, 'center_y': .45}

<Janela7>:
    #cadastro do responsavel
    name:"janela7"
    FloatLayout:
    MDCard:
        md_bg_color:'#c2a3fd'
    MDFillRoundFlatButton:
    	text:'Sim, desejo'
    	pos_hint:{'center_x' : .3, 'center_y': .23}
        size_hint_x: 0.35
        size_hint_y: 0.05
        md_bg_color:'#FFFFFF'
        text_color:'black'
        on_release: app.root.current = "janela8"

    MDFillRoundFlatButton:
    	text:'Não, obrigado '
    	pos_hint:{'center_x' : .7, 'center_y': .23}
        size_hint_x: 0.35
        size_hint_y: 0.05
        md_bg_color:'#FFFFFF'
        text_color:'black'
        on_release: app.root.current = "principal"

    MDLabel:
        text:'Deseja cadastrar a criança agora ? '
        font_size: 30
        halign:'center'
        pos_hint:{'center_x' : .5, 'center_y': .30}

    MDLabel:
        text:' Bem-vindo usuario! '
        font_size: 30
        halign:'center'
        pos_hint:{'center_x' : .5, 'center_y': .45}

    MDLabel:
        text:' Cadastro realizado com sucesso :) '
        font_size: 40
        halign:'center'
        pos_hint:{'center_x' : .5, 'center_y': .80}

    Image:
        source:'CORRETO.png'
        size_hint_x:.1
        size_hint_y:.1
        halign:'center'
        pos_hint:{'center_x' : .5, 'center_y': .90}

    Image:
        source:'perfil.png'
        size_hint_x:.1
        size_hint_y:.1
        halign:'center'
        pos_hint:{'center_x' : .5, 'center_y': .55}

<Janela8>:
#Cadastro da crianca
    name:"janela8"
    FloatLayout:
    	#vai precisar de uma implementacao melhor pode ocorrer falhas no funcionamento

	    MDCard:
        	md_bg_color:'#c2a3fd'
        	size_hint_x:50
        	size_hint_y:50
        	pos_hint:{'center_x' : .50, 'center_y': .5}

    MDFillRoundFlatButton:
        text: "Voltar"
        md_bg_color:'#c2a3fd'
        text_color:'white'
        pos_hint:{'center_x' : .15, 'center_y': .95}
    	on_release: app.root.current = "janela7"

    MDIconButton:
	    pos_hint:{'center_x' : .07, 'center_y': .95}
        icon:'arrow-left'
        icon_size: "20sp"
        on_release: app.root.current = "janela7"

    MDLabel:
        text:'Cadastro da criança'
        font_size: 40
        halign:'center'
        pos_hint:{'center_x' : .5, 'center_y': .90}

    MDFillRoundFlatButton:
    	text:'proximo'
    	pos_hint:{'center_x' : .5, 'center_y': .15}
        size_hint_x: .15
        size_hint_y: .05
        md_bg_color:'#c2a3fd'
        text_color:'white'
        on_release: app.root.current = "janela6"

    Image:
        source:'prancheta.png'
        size_hint_x:.13
        size_hint_y:.13
        halign:'center'
        pos_hint:{'center_x' : .5, 'center_y': .82}
    MDTextField:
        size_hint_x: .9
        hint_text: 'Digite nome da criança'
        mode: "round"
        pos_hint:{'center_x' : .5, 'center_y': .65}
        line_color_normal: "white"
        fill_color_normal:"white"

    MDTextField:
        size_hint_x: .9
        hint_text: 'DD/MM/AAAA'
        mode: "round"
        pos_hint:{'center_x' : .5, 'center_y': .55}
        line_color_normal: "white"
        fill_color_normal: "white"

    MDLabel:
        text:' Informações Pessoais '
        font_size: 25
        halign:'center'
        pos_hint:{'center_x' : .5, 'center_y': .74}

    MDLabel:
        text:' Caracteristicas Fisicas '
        font_size: 25
        halign:'center'
        pos_hint:{'center_x' : .5, 'center_y': .48}

    MDTextField:
        mode: "round"
    	pos_hint:{'center_x' : .7, 'center_y': .23}
        size_hint_x: .2
        md_bg_color:'#FFFFFF'
        text_color:'black'
        line_color_normal: "white"
        fill_color_normal:"white"

    MDTextField:
        mode: "round"
    	pos_hint:{'center_x' : .3, 'center_y': .23}
        size_hint_x: .2
        md_bg_color:'#FFFFFF'
        text_color:'black'
        line_color_normal: "white"
        fill_color_normal:"white"

    MDTextField:
        mode: "round"
    	pos_hint:{'center_x' : .7, 'center_y': .38  }
        size_hint_x: .2
        md_bg_color:'#FFFFFF'
        text_color:'black'
        line_color_normal: "white"
        fill_color_normal:"white"

    MDTextField:
        mode: "round"
    	pos_hint:{'center_x' : .3, 'center_y': .38}
        size_hint_x: .2
        md_bg_color:'#FFFFFF'
        text_color:'black'
        line_color_normal: "white"
        fill_color_normal:"white"

    MDLabel:
        text:' Tipo sanguineo '
        font_size: 20
        halign:'center'
        pos_hint:{'center_x' : .3, 'center_y': .28}

    MDLabel:
        text:' Sexo '
        font_size: 20
        halign:'center'
        pos_hint:{'center_x' : .7, 'center_y': .28}

    MDLabel:
        text:' Altura da criança '
        font_size: 20
        halign:'center'
        pos_hint:{'center_x' : .7, 'center_y': .43}

    MDLabel:
        text:' Peso da criança '
        font_size: 20
        halign:'center'
        pos_hint:{'center_x' : .3, 'center_y': .43}

    #ordem das janelas estao desconexas mas da pra entender... eu espero

<Janela9>:
    name:"janela9"
    FloatLayout:

	    MDCard:
        	md_bg_color:'#c2a3fd'
        	size_hint_x:50
        	size_hint_y:50
        	pos_hint:{'center_x' : .50, 'center_y': .5}

        MDCard:
        	md_bg_color:"#EBE0FF"
            pos_hint: {'center_x': .5, 'center_y': .6}
            size_hint_x: .50
            size_hint_y: .40
            style: 'elevated'
            padding: '10dp'
            MDLabel:
                text:'Devs: '

        MDFlatButton:
            text: "Voltar"
            text_color:'white'
            pos_hint:{'center_x' : .8, 'center_y': .95}
        	on_release: app.root.current = "principal"

<Janela9>:
	name:"janela9"
	FloatLayout:

<Janela10>:
	name:"janela10"
	FloatLayout:

Log
kivy.lang.builder.BuilderException: Parser: File "<inline>", line 149:
 ...
     147:        num_type: "minute"
     148:        pos: dp(120), 0
 >>  149:        text_color: root.text_color
     150:        disabled: root.disabled
     151:        on_text: root.dispatch("on_time_input")
 ...
 ValueError: TimeInputTextField.text_color accept only str

Versions

OS:
Python:
Kivy:
KivyMD:

Attach detailed instructions for reproducing this error. Also specify the versions of the libraries you use.

Attach detailed instructions for reproducing this error. Also specify the versions of the libraries you use.

I been use the version 1.2.0 of Kivymd
And the version 2.2.1 of the Kivy

The library version 1.2.0 is not supported

So what version of kivymd will make the timepicker work? I already try the version 1.1.1 , 1.1.0, 0.1.2 and no one of than work

already

https://kivymd.readthedocs.io/en/latest/components/timepicker/


text:
All links in FAQ article content open in new tab

All links that are somewhere in the content of an FAQ article must be opened in new tab.

I tried to do this the proper way - https://github.com/markdown-it/markdown-it/blob/master/docs/architecture.md#renderer but I could not get it to work :(

this issue is close by this pr https://github.com/kiwicom/smart-faq/pull/344

source: gharchive/issue

authors: dinodsaurus jalbertsr jaroslav-kubicek

repo: kiwicom/smart-faq

license: MIT

license_type: permissive

license_source: github-api


text:
Migrate away from Microsoft GitHub

UPDATE: joke turning into hot topic: https://techcrunch.com/2018/06/05/gitlabs-high-end-plans-are-now-free-for-open-source-projects-and-schools/?guccounter=1

🤣

wtf guys

😭

authors: MRTNKCR git-toni jalbertsr jaroslav-kubicek vborszeki


text:
Consider adding external BOMs such as Jackson, Dropwizard, JDBI, etc.

Per @chrisrohr 's suggestion, consider adding external BOMs into our BOM, e.g. the same way that Dropwizard pulls in Jackson's BOM.

Added Dropwizard BOM in #210

Also could import the Spring BOM, and maybe Spring Data. Jersey? Netty? JUnit Jupiter?

We've added Dropwizard, Jackson, and JDBI BOMs. Leaving open in case we want to add more, like Spring, Spring Data, Jersey, Netty, Jupiter, etc. as mentioned in my comment above.

Just added the Netty BOM in version 0.12.0

Just added the Spring BOM for version 0.14.0 in #274

The last two bigs ones to include are probably Jersey and Jetty.

https://mvnrepository.com/artifact/org.eclipse.jetty/jetty-bom
https://mvnrepository.com/artifact/org.glassfish.jersey/jersey-bom

Closing this as "done" now that all the major frameworks/libraries that actually have BOMs have been converted.

repo: kiwiproject/kiwi-bom


text:
🛑 Sangharaja is down

In 07f9aab, Sangharaja (https://sangharaja.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sangharaja is back up in 472d1c1 after 2 hours, 2 minutes.

repo: kizzna/uptime


text:
On/off sensor

I’ve successfully configured  my H series and the power switch automatically states “on” when the TV is on.
Would it be possible to create a sensor based on TV power?

Hi @picto3000, can you please elaborate? What do you mean to create a sensor? Are you referring to some automation options in Home.app?

I'm attempting to create automation based on the state (on or off) of the TV. The TV is being turned on by the TV remote.
eg.
Turn TV on = Amp turns on automatically
Turn TV off = Amp turns off automatically
I can create automation of the amp in Home, but the TV's state (the switch), is only checked when someone opens the Home app.
I'm looking into other ways of doing this via Homebridge or Home Assistant but everything seems to hinge on a sensor being used and not a switch. Happy to be proved wrong.

repo: kkapitan/homebridge-homesung


text:
fix: refactor timeline

请提交PR之前确认一下已通过

看过这个贡献者说明  中文
测试通过
如果有相关的issue，记得关联上

example正序倒序切换无效

涉及到是否存在Fragment节点的问题 我晚上提交

source: gharchive/pull-request


text:
gatsby blog로 변경하는 문제 검토

gatsby (no ts)
{MarkdownRemark.frontmatter__slug}.js 대신 gatsby-node.js 와 blogTemplate을 사용해서 구축하는 것으로 작업

gatsby + mui blog 환경 설정 및 빌드 완료

개선사항

방문자 수
utterance 댓글
로딩 애니메이션

로딩 애니메이션 성능상 추가 안하는 걸로
share api는 렌더 시점이 달라 오작동함. 개발하는 방향으로


text:
dev: move TRANSACTION_MAX_RETRIES to env

Describe the enhancement request
Currently, we assign a fixed value to TRANSACTION_MAX_RETRIES of 10. It could be interesting to have this as an env variable which can be customised based on the demand on the network. Thus, modify TRANSACTION_MAX_RETRIES to load it from the env.
Don't forget to update the .env.example, as well as the various Docker Compose and Dockerfiles!

Hi, can I take this?

Hi, I want to take this issue, please
!

authors: greged93 jbmkahdeksan stevencartavia

repo: kkrt-labs/kakarot-rpc


text:
fix: fix docker buildx publish error for docker image

current publishing of the rpc image fails in build_and_publish job,  it seems to be an authentication error, might be we should try to publish it in our new org name for auth to pass, i.e kkrt-labs.
Closes #161
Pull Request type
Please check the type of change your PR introduces:

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Testing
[ ] Other (please describe):

What is the current behavior?
publish fails on build_and_publish probably because of auth failure.
Issue Number: #161
What is the new behavior?
it should probably pass as the assumption is that it arrives from the change in org name.
Does this introduce a breaking change?

[ ] Yes
[X] No

lgtm 🚀


text:
🧑💻 Migrate klas-helper original repo to improve build process

기존의 유저 스크립트 방식에서 브라우저 확장 플러그인 방식으로 완전히 옮겨감에 따라 https://github.com/klas-helper/klas-helper 레포의 소스코드 및 히스토리를 이 레포로 통합하려고 합니다. 분리되어 있던 레포, 이슈, PR 등이 통합되어 트래킹이 더 쉬워지고 배포 프로세스가 간편해지는 이점을 기대할 수 있을 것 같습니다. 통합 작업이 완료된 후에는 유저 스크립트 지원을 완전히 종료할 예정입니다.
레포 통합에는 https://blog.devgenius.io/how-to-merge-two-repositories-on-git-b0ed5e3b4448 방법을 사용했습니다. 커밋 히스토리를 유지하는 것이 좋을 것 같아서 해당 PR을 머지할 때 "Squash merge" 방식만 사용하지 않으면 될 것 같습니다.
확장 플러그인 정상 작동 여부

[x] Windows 11 (Chrome)
[x] macOS (MacBook Air M2, Chrome)

main-ext.js의 변경 사항을 확인해 봤지만, 변수 이름이나 공백 정도의 수정이 있어서 큰 문제는 없어 보입니다. 하지만 혹시 모르니 한 번 더 검증해 보는 것이 좋을 것 같습니다.
통합 후 진행하면 좋은 작업

[ ] 기존 레포 이름을 klas-helper-userscript로 변경하고, archived 처리
[ ] 현재 레포 이름을 klas-helper로 변경하고, 설명 업데이트
[ ] 기존 레포의 이슈, 스타 등의 메타데이터를 현재 레포와 통합 (이건 가능할지 모르겠네요.)
[ ] README.md 업데이트
[ ] 유저 스크립트 지원 완전 종료 (브라우저 확장 플러그인을 이용해달라고 안내 문구 넣어놓기)
[ ] 웹팩 설정 변경해서 의존성 자동으로 주입될 수 있게 수정

고생하셨습니다!
제가 버그 잡으면서 미처 전달드리지 않은 구현 부분이 있는데, 언제부턴가 KLAS의 CSP 보안 정책이 바뀌어서 외부 js 라이브러리를 가져올 수 없게 되었습니다.
이로인해서 Chart.js, jQuery 등 Userscript에서 사용하는 라이브러리를 Extension으로 빼서 확장 프로그램 단에서 인젝션 시키도록 수정했고, 그렇기에 사실 차트와 jQuery 기능은 유저스크립트에서 사용이 불가능한 상황입니다
이를 해결하기 위해서는

공식적으로 유저스크립트 지원을 종료하거나
Webpack에서 Chart.js, jQuery 등 외부 라이브러리를 같이 압축해 배포하거나

해야 될듯 합니다.
후자의 경우 제가 웹팩 이해도가 낮아서 제대로 해보진 못했습니다ㅠㅠ 의견 부탁드리겠습니다

보안 정책이 강화됨에 따라서 말씀하신 문제가 발생하고 있기도 하고 지금은 확장 프로그램이 메인이 된 상황이라 유저 스크립트 지원을 완전히 종료해도 문제가 없을 것 같습니다!
웹팩으로 사용하는 라이브러리를 묶어서 main-ext.js에 같이 넣고 배포하는 작업도 불가능하지는 않을 테니까 한번 찾아보고 적용시켜보도록 하겠습니다. 유저 스크립트가 없어도 이 작업이 완료되면 배포할 때 의존성 신경 쓸 일이 줄어들어서 조금 편해지지 않을까 싶어요.
PR 본문의 통합 후 진행하면 좋은 작업에 위의 작업들을 체크리스트로 만들어 두고 이 PR이 머지된 이후에 하나씩 진행해 보도록 하겠습니다.

해당 버전으로 윈도우와 맥북 크롬에서 테스트를 해봤는데 정상 동작했습니다! PR 확인하시고 문제될 부분 없으면 머지해도 괜찮을 것 같아요.

제가 요즘 과제때문에 바빠서 주말에 확인후에 머지하도록 하겠습니다ㅠㅠ

repo: klas-helper/klas-helper-extension


text:
I installed it but get a blank page

When I visit the directory holding my gitlist install I get presented with a blank page. I followed the install steps presented as text on that page.

I have set permissions and all.

Do I have to install to /var/www/gitlist? As I chose a different directory.

A blank page may be result of a 500 Internal Server Error. You could check the server's log for information about what went wrong. In case of a php-error, you may look what file/line caused the error and this may help you finding out what you did wrong.

authors: SkeletonEye deavmi

repo: klaussilveira/gitlist

license_source: bigquery


text:
Court stats: same data for Min Stake and Vote Stake seems incorrect

fixed on PR #1200

authors: jaybuidl kemuru


text:
Crosshair magnet mode

Feature Description
Hi, it would be nice to configure the horizontal crosshair to magnet to the price line. I would like to replace the horizontal crosshair with the lastPrice built-in price line if possible, since it has a price marker and coloring. Is it possible to make an overlay or figure follow the mouse, rather than being fixed in place?
To Do
Crosshair.magnet = “strong_magnet”
Or
Priceline.last = false
Priceline.follow = true

Hello, we tried to solve the issue.
This is what we did:
Add a new option 'magnetToPriceLine' to the Chart component and implement the functionality in the CandleWidget to make the horizontal crosshair follow the last price line when enabled.
You can review changes in this commit: https://github.com/kkpo4553/klinecharts-KLineChart-618/commit/5f6d29cd471260f991770c01f49d39a4cfd6b88d.

[!CAUTION]
Disclaimer: The concept of solution was created by AI and you should never copy paste this code before you check the correctness of generated code. Solution might not be complete, you should use this code as an inspiration only.

If you no longer want Latta AI to attempt solving issues on your repository, you can block this account.

repo: klinecharts/KLineChart


text:
When does kluctl render helm charts?

Operating system
Ubuntu
Kluctl Version
2.25.0
Kubernetes Version
v1.27.3
kubectl Version
v1.28.4
Bug description
When does kluctl render helm charts?
I am trying to install cilium and install and wait for the gateway CRDs however when the helm chart for cilium runs it seems to not find the gateway CRDs
see https://github.com/cilium/cilium/blob/main/install/kubernetes/cilium/templates/cilium-gateway-api-class.yaml
If I rerun the deployment then cilium helm chart will add the GatewayClass. So I assume its being rendered before the CRDs are installed.
How would one get around this issue?
Steps to reproduce
example deployment yaml
deployments:
  - path: gateway-api
    waitReadiness: true
  - barrier: true
    message: "Waiting for gateway-apis"
  - barrier: true
    waitReadinessObjects:
    - kind: CustomResourceDefinition
      name: gatewayclasses.gateway.networking.k8s.io
    - kind: CustomResourceDefinition
      name: gateways.gateway.networking.k8s.io
    - kind: CustomResourceDefinition
      name: tlsroutes.gateway.networking.k8s.io
    - kind: CustomResourceDefinition
      name: grpcroutes.gateway.networking.k8s.io
    - kind: CustomResourceDefinition
      name: httproutes.gateway.networking.k8s.io
  - path: cilium
    waitReadiness: true

Relevant log output
No response

Helm Charts are always rendered right before the deployment stage begins. This happens for all Helm Charts in one go. This unfortunately leads to such situations where one Helm Chart can not know about another Helm Chart deploying some CRDs.
So far, I have not come up with an idea how to properly solve this issue. Changing the rendering order is not an option unfortunately as it would break many assumptions in other places. What I was considering is to add a capabilities field into helm-chart.yaml which allows to force signalling of some capabilities.

Thanks for the clarification

FYI, I added an issue to track the feature I mentioned: https://github.com/kluctl/kluctl/issues/1128

authors: codablock hsight

repo: kluctl/kluctl


text:
Bug in max shear strain rate calculation

Hey @kmaterna I introduced a bug in the max shear strain rate code by propagating a bug from my last code. The current syntax is
(1) tau_{max} = sqrt((e_{11}-e_{22})^2 + e_{12}^2)
but after some extensive work with Kaj Johnson we figured out that the formula should actually be
(2) tau_{max} = sqrt((e_{11}-e_{22})^2 + 4*e_{12}^2).
The factor of 4 is missing from the current formulation. It can make a difference of a factor of 1-2 depending on the tensor.
The way we worked this out was to analytically calculate the principal strains and take the difference. Max shear strain rate is just the difference between e1 and e2. Solving for the eigenvalues of the strain rate tensor and taking the difference results in Eq. 2 above.
See here for line in question.

@jlmaurer awesome.  This fix is supported by Savage and Simpson 1997 Equation 2.   They have tau_max exactly as you and Kaj suggested.

authors: jlmaurer kmaterna


text:
mingw support

Bug report by lazarou.
"Maybe I'm asking something very silly, but here goes. I get this error when trying to install the package (using Win 7 64-bit and the latest version of mingw):
C:\MinGW\bin\gcc.exe -mdll -O -Wall -Ilib -IC:\Python32\include -IC:\Python32\PC -c lib/marisa/grimoire/io\mapper.cc -o build\temp.win32-3.2\Release\lib\marisa\grimoire\io\mapper.o
lib/marisa/grimoire/io\mapper.cc: In member function 'void marisa::grimoire::io::Mapper::open_(const char*)':
lib/marisa/grimoire/io\mapper.cc:110:19: error: aggregate 'marisa::grimoire::io::Mapper::open(const char*)::_stat64 st' has incomplete type and cannot be defined
lib/marisa/grimoire/io\mapper.cc:111:3: error: '::_stat64' has not been declared
error: command 'gcc' failed with exit status 1
```"

I'm not sure but this might be due to the file mode.

_write
https://msdn.microsoft.com/ja-jp/library/1570wh78.aspx

When the file is opened in Unicode translation mode—for example,
if fd is opened by using _open or _sopen and a mode parameter that
includes _O_WTEXT, _O_U16TEXT, or _O_U8TEXT, or if it is opened
by using fopen and a mode parameter that includes ccs=UNICODE,
ccs=UTF-16LE, or ccs=UTF-8, or if the mode is changed to a Unicode
translation mode by using _setmode—buffer is interpreted as a pointer
to an array of wchar_t that contains UTF-16 data.An attempt to write
an odd number of bytes in this mode causes a parameter validation error.

Sorry, the above comment was wrong.
I found a suspicious decrement that is enabled when _MSC_VER.
I've removed it in the following commit.
https://github.com/s-yata/marisa-trie/commit/1ff7ee975574861d6037ca53a9814bbfce312fdc

This won't be an issue once we do #21.

Fixed by updating to the latest marisa-trie.

authors: kmike s-yata superbobry

repo: kmike/marisa-trie

license: mit


text:
Logger for non-saml2 authentication attempts from error to info

We use both the django modelbackend and the saml2 backend in the project to allow multiple ways of logging in. So in our settings we have
AUTHENTICATION_BACKENDS = (
    'django.contrib.auth.backends.ModelBackend',
    'djangosaml2.backends.Saml2Backend',
)

Due to the way Django works, it will try a fallthrough to the Saml2Backend if the ModelBackend fails. This means that normal username/password attempts end up in the Saml2Backend as well. This leads to our logs being flooded unnecessary with error-level logs. It is in fact simply not a request from a Saml2 flow, which is passed to it, and should just be discarded without logging an error. We cannot simply discard all error-logs from djangosaml2, as some of them are actual errors which we should keep.
This PR therefor changes that loglevel from error to info.

Yes, that's a good point. If session_info or attribute_mapping are not set, then this authentication request is obviously not meant for djangosaml2 backend and should be silently ignored. I'd perhaps even consider making it just a debug level log if not removing it completely.
Thanks for your contribution!

authors: knaperek mhindery


text:
[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-extensions/eventing-writers
/assign knative-extensions/eventing-writers
Produced by: knative-extensions/knobots/actions/update-deps

/lgtm
/approve

authors: aliok knative-automation

repo: knative-extensions/eventing-gitlab


text:
[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-sandbox/eventing-writers
/assign knative-sandbox/eventing-writers
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/pkg 4d62e1d...e2b4d74:
  > e2b4d74 Update community files (# 2486)
bumping golang.org/x/oauth2 d3ed0bb...ee48083:
  > ee48083 go.mod: update vulnerable net library
bumping knative.dev/hack 0e0784b...02c525c:
  > 02c525c Update community files (# 167)
bumping knative.dev/eventing 58865af...bb76b30:
  > bb76b30 Update community files (# 6310)
  > 5accb7a Update actions (# 6303)
  > 2ff606c upgrade to latest dependencies (# 6307)
bumping knative.dev/serving f4ea3ac...e73e83b:
  > e73e83b Update community files (# 12837)
  > e38c4cf Fix tag to digest resolution with K8s secrets (# 12836)
  > a01b639 fix double import (# 12832)
  > b4d1391 upgrade to latest dependencies (# 12831)

/lgtm
/approve

authors: knative-automation lionelvillard

repo: knative-sandbox/eventing-github


text:
Use retention from spec for topic creation

Fixes #

Proposed Changes

Use retention from spec for topic creation

Release Note

Docs

=== RUN   TestBrokerControlPlane/1
=== CONT  TestBrokerControlPlane/1
    test_runner.go:163: Couldn't initialize clients: unable to find available namespace
    --- FAIL: TestBrokerControlPlane/1 (7.06s)

This should be fixed in https://github.com/knative-sandbox/eventing-kafka-broker/pull/1191
/retest

/test pull-knative-sandbox-eventing-kafka-broker-integration-tests

authors: aliok pierDipi

repo: knative-sandbox/eventing-kafka-broker


text:
[Release 1.2] Run channel Rekt tests

Fixes #

Proposed Changes

Same as https://github.com/knative-sandbox/eventing-kafka-broker/pull/1825 but for 1.2 branch

Release Note

:gift: KafkaChannel becomes conformant with spec. Conformance tests are now run with every code change.

Docs

/retest-required

I moved the base branch to 1.2 since I guess that's you wanted 😄

Doh! Thanks!
Could you lgtm?


text:
builder short name constants etc throughout

:broom: Full adoption of builder short name constants throughout.

Pulls out builder names, validators and error types into their own package.
Moves validators of builder names into main, which is closest to where knowledge of the correct set resides.
/kind chore

Thanks @lace for the review.  All comments should now have been processed

@lkingland needs rebase - otherwise lgtm

authors: lance lkingland

repo: knative-sandbox/kn-plugin-func


text:
Replace Nacho channel with actual channel

Changes

:broom: Update Knative-gcp notification settings

/kind

/lgtm

/hold

/unhold

/lgtm

authors: grantr zhongduo

repo: knative-sandbox/knobots


text:
Better handling for Multiple Functions in a Single Repository

Goal:
I'm working on supporting multiple functions, primarily Spring Boot applications, in a single repository. This includes being able to share common code like domain classes and defining dependencies only once. Ultimately, these functions should be able to be deployed as individual functions into the Kubernetes cluster.
Current Approach:
Currently, I'm splitting the functions into separate modules, with a main pom.xml and each module having its own module pom.xml. By specifying BP_MAVEN_BUILT_MODULE in the func.yaml, I can indicate the module to be built and it is correctly deployed.
├── module-core
│   ├── src
│   │   ├── ...
│   ├── pom.xml
├── module-func-1
│   ├── src
│   │   ├── ...
│   │   |   ├── Application.java
│   ├── pom.xml
├── module-func-1
│   ├── src
│   │   ├── ...
│   │   |   ├── Application.java
│   ├── pom.xml
├── pom.xml
├── func.yaml

Problem:
The main problem is that I have to adjust the func.yaml each time, as it has to be located next to the main pom.xml. However, I need a separate func.yaml for each function.
Possible Solution Approach:
One possible solution could be to use the path option provided by pack. With this, one can refer to a main folder from a subfolder. Another possibility could be to allow multiple functions in the func.yaml, similar to how the Serverless Framework allows for AWS Lambda.
I look forward to feedback and potential solutions to this problem. Thanks

Hello @darthkali,
This seems like it could perhaps be something that needs to change in the way Spring Boot functions are built and deployed.
There is a 1:1 correlation between a Function and its func.yaml.  The yaml is the metadata for a single Function.
However, there should be no need for this to reside at the repository root.  Functions can be defined to reside within a subdirectory of a repository.
This may be anathema to the way you are trying to set up your project, but note that a Funciton is conceptually a completely separate, independent service.  As such it should not share any build-time dependencies with other Functions unless those are structured as independent projects importing each-other as dependencies.  So this might be a situation that doesn't quite fit your desired setup.

authors: darthkali lkingland

repo: knative/func


text:
Clarify --registry-insecure flag description

Changes

:broom: Clarify --registry-insecure flag description

/kind documentation
Related to #2335, where we discovered that the description of registry-insecure flag was not really accurate/clear.
After investigation, I've found that enabling this flag just means "skip TLS certificate verification when communicating to the registry", not "allow plain HTTP registries", as the current description ("Disable HTTPS when communicating to the registry") can let users think.

Today, the RegistryInsecure boolean in the config (filled from the flag) is used at two places:

In the build command: https://github.com/knative/func/blob/1e7dd33/cmd/build.go#L389

The value is simply forwarded to the Pusher, and is used to configure InsecureSkipVerify: https://github.com/knative/func/blob/1e7dd33/pkg/oci/pusher.go#L129-L135:
        if p.Insecure {
		t := remote.DefaultTransport.(*http.Transport).Clone()
		t.TLSClientConfig = &tls.Config{
			InsecureSkipVerify: true,
		}
		oo = append(oo, remote.WithTransport(t))
	}

In the deploy command: https://github.com/knative/func/blob/1e7dd33/cmd/deploy.go#L282

The value is simply forwarded to the fn.Client (through NewClient): https://github.com/knative/func/blob/1e7dd33/cmd/client.go#L58, and then used to create the transport with InsecureSkipVerify:
https://github.com/knative/func/blob/1e7dd33/cmd/client.go#L96-L98
func newTransport(insecureSkipVerify bool) fnhttp.RoundTripCloser {
	return fnhttp.NewRoundTripper(fnhttp.WithInsecureSkipVerify(insecureSkipVerify), fnhttp.WithOpenShiftServiceCA())
}

I'm pretty confident it's not used elsewhere, but I'm not familiar with the codebase, so tell me if I've missed something.

Note: To me, a better solution would be to completely rename this flag, to something like --insecure-skip-verify or --registry-insecure-skip-verify, as it's effectively only used to configure the InsecureSkipVerify booleans in HTTP transport-related parts of the code.
However, since renaming is a breaking change, I'm not sure if it can be done easily. Another approach, if we want to rename, would be to just 1) add a new flag --insecure-skip-verify, 2) deprecate the existing --registry-insecure, and 3) eventually sunset --registry-insecure.
Internally changing the variable name from RegistryInsecure to InsecureSkipVerify, without touching the flag name, is also possible though. Tell me what you think of this.
In the meantime, changing the description is a good first step IMO to help users figuring out what this flag really means.
Release Note
/
Docs
/

I can't really understand why the integration test is failing (logs seems ok to me, but I have trouble reading the logs).
I'm assuming the test is just flaky and will work after a few retries :wrench:

@norbjd for some reason tests run out of space in the GH action.

@dsimansk would you please override the test?

/override "Integration Test (ubuntu-latest)"

/approve

authors: dsimansk matejvasek norbjd


text:
Inconsistency when creating ENUM for MSSQL

As you can see in this line, the enums are casted to normal varchars in mssql dialect.
This should deserve at least a warning from knex itself, or an enum implementation if possible.
I've found an elegant solution on SO and I've tried implementing inside knex, but I can't figure out how to put the CHECK IN at the very bottom of the sql string.

This is how its done with postgresql https://github.com/tgriesser/knex/blob/master/src/dialects/postgres/schema/columncompiler.js#L34

Yeah but it conflicts with possible .notNullable() calls, and possibly other chainable methods as well

You might need to override https://github.com/tgriesser/knex/blob/master/src/schema/columncompiler.js#L39
in dialect which decides in which order different parts of query are constructed.

This issue is not solved yet, let's re-open it.

authors: beenotung elhigu neslinesli93

repo: knex/knex


text:
Knex insert with * only returns id

Environment
node: docker 12-alpine
Knex version:^0.21.2
Database + version: sqlite 3
OS: linux
Bug
When i use knex('table').insert(data,'*') this dont returns all inserted data. The return is only id
My table
import knex from "knex";

export async function up(knex: knex) {
    return knex.schema.createTable('subjects',table => {
        table.increments('id').primary()
        table.string('name').notNullable()
        //timestamps
        table.timestamp('created_at').defaultTo('now()')
        table.timestamp('updated_at')
    })
}

export async function down(knex: knex) {
    return knex.schema.dropTableIfExists('subjects')
}

my insert command
import db from "../../database/connection";

export class SubjectRepository implements ISubjectRepository {
    async save(data: CreateSubjectDTO) : Promise<Subject> {
        let returns: Array<number> = await db('subjects').insert(data,'*')
        console.log(returns)
        return new Subject({
            id: returns[0],
            name: data.name
        })
    }
}

The should return object with all data in row inserted. But only return ids
example of console.log
[ 2 ]

https://knexjs.org/#Builder-returning
sqlite does not support returning.

MySQL also doesn't support returning. If you use it, it will do nothing.

yep... that is also even mentioned in documentation.


text:
1.更换数据库连接池 c3p0 => durid

2.修改配置文件为本地环境

Coverage remained the same at 43.042% when pulling 7112b9543af8d198503e213af9487a106093bae4 on lysongfei:master into 2ac5c8275ad8cdc101522ad01a8ba87e53b73b68 on knightliao:master.

Coverage remained the same at 43.042% when pulling 4412e30706cdb11bb9918ae96dbcdcb88948f959 on lysongfei:master into 2ac5c8275ad8cdc101522ad01a8ba87e53b73b68 on knightliao:master.

authors: coveralls lysongfei

repo: knightliao/disconf


text:
Ability to add port details as a label to a link

The plugin is fantastic and i've used it widely over the last few weeks, however it would be hugely beneficial to add a label to the A and Z side of each link to denote the physical port.

Would you mind being more specific by what you mean by this? Do you mean a label visible at all times, or one that just shows up when you hover over the link?

Either would work to be fair. The problem I face with the plugin at the moment is when modelling a large environment it becomes quite cumbersome to quickly work out what physical interfaces a specific link is using.

My preference would be one that is there all the time, but rotated on the link. Here's an example of how I used to do this in the old PHP Weathermap.

authors: jasonyates-thg knightss27 sjthespian


text:
Change styles to improve aesthetic

I've made a few changes to the styles of the page.

I changed the color for the social icons on the sidebar to white:

I changed how the instructor profile is presented:

I changed how the tutors profile is presented:

I resized Chenyang's photo.

Great job!

authors: knmnyn nexolute


text:
Efficient way of publishing IP?

Nick, Thanks for the great library
I was wondering if there is a more efficient way (than I curently use) to publish the local ip address
Currently I get my local ip address  with Ethernet.localIP() which is an array.
I then add the 0-3 elements from the array to a string variable "MyIp"
MyIp=String (Ethernet.localIP()[0]);
MyIp=MyIp+".";
MyIp=MyIp+String (Ethernet.localIP()[1]);
etcetera etcetera
I then publish that as follows:
mqttClient.publish("topic/ip",MyIp.c_str());
That works well, but was wondering if there is a more efficient method. Adding strings is memory hungry
I was hoping ofcourse that:
mqttClient.publish("topic/ip",Ethernet.localIP());
would work but it doesnt, just publishes gibberish.

Hi @consolacion, this is how I publish my IP:
     mqttClient.publish("topic/ip", WiFi.localIP().toString().c_str());
However, if efficiency is the main question, then I don't know whether this method is more efficient than yours or not.
I used the library ESP8266WiFi (https://github.com/esp8266/Arduino/tree/master/libraries/ESP8266WiFi) in the example above.

Marcel, thanks. I will check what takes more memory, but my example came from a UNO, so the ESP8266WiFi lib may not work there. Nevertheless good to know

Works on a Wemos D1 R1, ie, ESP8288:
mqttClient.publish(out_topic_2, WiFi.localIP().toString().c_str(),
true);

authors: consolacion gns5280 marcelops

repo: knolleary/pubsubclient


text:
Overwriting knp_menu.html.twig in the 'normal' way

At the moment, this file ships with KnpMenu, not KnpMenuBundle, and thus is not overwritable by using the documented method to overwrite a template. Overwriting the renderer should not be necessary for this step.
I should be able to provide a app/Resources/KnpMenuBundle/views/knp_menu.html.twig file to overwrite the template.

Here's the parameter format. It wasn't completely obvious.
Put new knp_menu.html.twig in Test\AcmeBundle\Resources\views\Menu
parameters:
knp_menu.renderer.twig.template: TestAcmeBundle:Menu:knp_menu.html.twig

was this ever resolved? I'm trying to override the template using jdewitt's method, but placing the parameters directive in the services.yml doesn't work

@jaitsu87
that work for me(with menu translation):

config.yml
knp_menu: ~

Acme\AcmeBundle\Menu\MenuBuilder.php
use Knp\Menu\FactoryInterface;
use Symfony\Component\HttpFoundation\Request;
use Symfony\Component\Routing\Router;
use Symfony\Component\Translation\Translator;
class MenuBuilder
{
private $factory;
/**

@param \Knp\Menu\FactoryInterface $factory
*/
public function __construct(FactoryInterface $factory)
{
$this->factory = $factory;
}

public function createMainMenu(Request $request, Translator $translator)
{
$menu = $this->factory->createItem('root');
$menu->setCurrentUri($request->getRequestUri());
 $menu->addChild($translator->trans('menu.home', array(), 'AcmeBundle'), array('route' => 'homepage'));
 $menu->addChild($translator->trans('menu.blog', array(), 'AcmeBundle'), array('route' => 'blog'));
 $menu->addChild($translator->trans('menu.contact', array(), 'AcmeBundle'), array('route' => 'contact'));

 return $menu;

}
}

Acme\AcmeBundle\Resurces\config\services.yml
services:
acme_acme.menu_builder:
class: Acme\AcmeBundle\Menu\MenuBuilder
arguments: ["@knp_menu.factory"]
acme_acme.menu.main:
class: Knp\Menu\MenuItem # the service definition requires setting the class
factory_service: acme_acme.menu_builder
factory_method: createMainMenu
arguments: [@request, @translator]
scope: request # needed as we have the request as a dependency here
tags:
- { name: knp_menu.menu, alias: main } # The alias is what is used to retrieve the menu

Extend/copy template vendor\KnpMenu\src\Knp\Menu\Resources\views\knp_menu.html.twig
place it in your Acme\AcmeBundle\Resources\views\Menu\knp_menu.html.twig

use menu in your main layout:
{{ knp_menu_render('main', {'template': 'AcmeBundle:Menu:knp_menu.html.twig'}) }}

@jacobmaster you could do the translation in the template instead of doing it in the menu builder. But @jaitsu87's request was about overwriting the template globally, not only for a rendering
@jaitsu87 I worked on other bundles instead of KnpMenuBundle so the refactoring of the configuration is not done yet. I'm a bit busy this week so it will need to wait until Friday. But I up it in my todo-list.

@stof no worries man, it's not urgent or anything I'm just starting out on the project so just give me a heads up when you've pushed the commit, thanks a lot

authors: jacobmaster jaitsu87 jdewit merk stof

repo: knplabs/KnpMenuBundle


text:
Add lexicon for Japanese

Resources
Tokenizer - https://github.com/ikawaha/kagome
Lexicon - <googling it>, perhaps if you know of a lexicon that is available

I have no knowledge of Japanese, so adapting the lexicon requires a good understanding of the language. Sagan lexicons are different then the original VADER implementation.
Another point is that most of the lexicons available on the internet for languages other than English are translations that lack careful analysis.

repo: knuppe/vader


text:
[RFC] [PoC] target-side env_logger-like env filter

This PR implements an alternative approach to disabling/enabling logging in crates. Currently we use Cargo features.
This PR removes the need for those Cargo features and replaces them with the env variable: DEFMT_LOG.
The DEFMT_LOG env var specifies which crates should emit defmt logs and at which level. Its syntax is the same as the syntax used by the env_logger crate.
The DEFMT_LOG env var parser currently rejects paths that include modules: so DEFMT_LOG=krate=info is OK, but DEFMT_LOG=krate::module=info is rejected. This is intentional and should let us accept module paths and filter based on modules in the future (as in add module support in a backwards compatible fashion). No longer true, DEFMT_LOG now supports module paths.
One of the main advantages of DEFMT_LOG is that allows filtering logs with module level granularity. The current Cargo features based approach is more coarse grained and only supports enabling / disabling entire crates.
NOTE this is a target side emit filter and orthogonal to the host side display filter proposed in knurling-rs/probe-run#74. Disabling logs with the target filter makes the target program smaller (, maybe also slightly faster) and it reduces the amount of data sent from the target to the host. Disabling logs with the host filter does not change the target program at all not it changes the amount of data transmitted from the target to the host.
Changing the value of the DEFMT_LOG env var causes all crates that transitively depend on the defmt_macros crate to be recompiled.
Example usage:
$ bat src/bin/hello.rs

fn main() -> ! {
    defmt::info!("hello");
    foo::foo();
    bar::bar();
    app::exit()
}

mod foo {
    pub fn foo() {
        defmt::info!("foo");
    }
}

mod bar {
    pub fn bar() {
        defmt::info!("bar");
    }
}

$ DEFMT_LOG=hello::foo cargo r --bin hello
0 INFO  foo
└─ hello::foo::foo @ src/bin/hello.rs:16

$ DEFMT_LOG=hello::bar cargo r --bin hello
0 INFO  bar
└─ hello::bar::bar @ src/bin/hello.rs:22

$ DEFMT_LOG=hello::foo,hello::bar cargo r --bin hello
0 INFO  foo
└─ hello::foo::foo @ src/bin/hello.rs:16
1 INFO  bar
└─ hello::bar::bar @ src/bin/hello.rs:22

$ DEFMT_LOG=hello cargo r --bin hello
0 INFO  hello
└─ hello::__cortex_m_rt_main @ src/bin/hello.rs:8
1 INFO  foo
└─ hello::foo::foo @ src/bin/hello.rs:16
2 INFO  bar
└─ hello::bar::bar @ src/bin/hello.rs:22

$ rg '\[features' Cargo.toml || echo no Cargo features
no Cargo features

how to test this
as this is not even merged into the main branch and breaking changes (with respect to defmt v0.2.0) have landed into defmt, the whole process is quite involved

install a probe-run that uses the decoder in this branch

$ git clone https://github.com/knurling-rs/probe-run
$ cd probe-run
$ # change the `#[dependencies]` section
$ edit Cargo.toml

 colored = "2.0"
-defmt-decoder = { version = "=0.2.2", features = ['unstable'] }
+defmt-decoder = { git = "https://github.com/knurling-rs/defmt", branch = "env-filter", features = ['unstable'] }
 difference = "2.0"

$ cargo install --path .

use [patch.crates-io] in Cargo.toml (the one in the root of the workspace) to use the git version of defmt instead of v0.2.x. The app-template already includes this section in its Cargo.toml

[patch.crates-io]
defmt = { git = "https://github.com/knurling-rs/defmt", branch = "env-filter" }
defmt-rtt = { git = "https://github.com/knurling-rs/defmt", branch = "env-filter" }
defmt-test = { git = "https://github.com/knurling-rs/defmt", branch = "env-filter" }
panic-probe = { git = "https://github.com/knurling-rs/defmt", branch = "env-filter" }

IMPORTANT use branch = "env-filter" instead of rev = "somehash"

set the PROBE_RUN_IGNORE_VERSION env variable before you run your firmware e.g.

$ PROBE_RUN_IGNORE_VERSION=1 cargo run --bin hello

try setting / changing the value of the DEFMT_LOG env variable!

$ export PROBE_RUN_IGNORE_VERSION=1
$ DEFMT_LOG=hello=trace cargo run --bin hello
0 INFO  Hello, world!
└─ hello::__cortex_m_rt_main @ src/bin/hello.rs:8

As there's other breaking-change work currently ongoing (#508) I plan to leave this work on hold for now -- but will be answering to feedback! -- and resume it when that's concluded.
Unresolved questions

rename DEFMT_LOG to DEFMT_CAPTURE or DEFMT_TARGET_CAPTURE? if we keep the DEFMT_LOG name, what should we name the env var to be used in knurling-rs/probe-run#74?

TODO list

[ ] RFC approval
[x] address inline TODO comments
[x] support log level without module path e.g. DEFMT_LOG=info
[x] support the off pseudo log-level (disables logging)
[x] fix module path handling so that DEFMT_LOG=krate::module doesn't match krate::module1, krate::module2, etc.
[ ] fix CI
[ ] documentation. important changes in behavior to note

default log level is error (when DEFTM_LOG is not set)
compilation profile (dev / profile) has no effect on the log level filter
"this removes the ability to set a default log level"

closes #183
closes #255
closes #459

one big difference between this approach and the current one is that: which profile (dev vs release) is used to compile the code has no effect on the target-side filtering with the env_logger approach. Unsure if that's good or bad but it's different.
$ # see issue description example

$ # defmt 0.2.0
$ cargo r --bin hello
0 ERROR a
1 WARN  b
2 INFO  c
3 DEBUG d
4 TRACE e

$ # defmt 0.2.0
$ cargo r --bin hello --release
0 ERROR a
1 WARN  b
2 INFO  c

$ # this PR
$ cargo r --bin hello
0 ERROR a

$ # this PR
$ cargo r --bin hello --release
0 ERROR a

I think another important thing to note is that this removes the ability to set a default log level. This is potentially useful when writing tests, when you don't want to set the same environment variable all the time. (something like dotenv can work around this, but that seems suboptimal, since it's a third-party tool)

Looks great! Could you please elaborate how the default levels and following line fit together? I am a bit confused by this 🙈
https://github.com/knurling-rs/defmt/blob/688f3ebcc6e5cc1320854f3c57e85522ff2dd776/macros/src/lib.rs#L479

I think another important thing to note is that this removes the ability to set a default log level. This is potentially useful when writing tests, when you don't want to set the same environment variable all the time. (something like dotenv can work around this, but that seems suboptimal, since it's a third-party tool)

You mean that one can't set a default for your own crate? Cause afai understand there are still some default levels. Do you see any other use cases where this would be a "problem" (or annoyance), except testing?

Right, there's a fixed default to error messages. Previously you could set default Cargo features to configure any default you like (and when testing it's useful to enable more than just errors, for example the defmt-test progress messages are at info level).

Could you please elaborate how the default levels and following line fit together? I am a bit confused by this

that line of code means log at this level or higher "severity". For instance if you set DEFMT_LOG=info you get info, warn and error level logs. If you don't set the env var you get only error level logs. In code, the "severity" in defined in the enum declaration (note the derive(PartialOrd)):
https://github.com/knurling-rs/defmt/blob/fde2aab0bc541081d7def42fb049a36fa793a2bc/parser/src/lib.rs#L137-L144
So trace < debug < info < warn < error in terms of severity. This is the same as the log crate.

I think another important thing to note is that this removes the ability to set a default log level.

good point. I have noted this down in the issue description as a reminder to add it to the documentation.
thinking about the case of testing, in std code one can use the following code as a "setup" for unit tests:
std::env::set_var("RUST_LOG", "my_crate=trace");
env_logger::init();

this is not possible with DEFMT_LOG because the filtering happens at compile time, not runtime.
in the particular case, of testing embedded code the only way to set DEFMT_LOG I can think of is setting it in xtasks. So cargo xtask test target would do DEFMT_LOG=my_crate=trace cargo test -p fw-tests; cargo xtask test host-target could do DEFMT_LOG=my_crate=trace cargo run -p firmware; cargo test -p host-target-tests etc. Using xtasks it's certainly more heavyweight than what one can do today but if you already set up xtask for testing your embedded code then it doesn't seem that much extra work.

Could you please elaborate how the default levels and following line fit together? I am a bit confused by this

that line of code means log at this level or higher "severity". For instance if you set DEFMT_LOG=info you get info, warn and error level logs. If you don't set the env var you get only error level logs. In code, the "severity" in defined in the enum declaration (note the derive(PartialOrd)):
https://github.com/knurling-rs/defmt/blob/fde2aab0bc541081d7def42fb049a36fa793a2bc/parser/src/lib.rs#L137-L144
So trace < debug < info < warn < error in terms of severity. This is the same as the log crate.

Okay, I think I got it now:

if you don't mention your crate in DEFMT_LOG you only get error logs
if you just mention it without setting an explicit level you get trace
if you mention it with a level you get this one

Correct? I guess I was mainly confused about the two different defaults.

Correct? I guess I was mainly confused about the two different defaults.

yes, that is correct. The "defaults" match the behavior of the env_logger crate. (TBH I didn't know about the trace default when you specify only the crate name nor the off pseudo-level until I started writing tests for this feature and had to read the env_logger docs in more detail though I have used the crate several times before)

pushed very WIP module path support. This works:
fn main() -> ! {
    defmt::info!("hello");
    foo::foo();
    bar::bar();
    app::exit()
}

mod foo {
    pub fn foo() {
        defmt::info!("foo");
    }
}

mod bar {
    pub fn bar() {
        defmt::info!("bar");
    }
}

$ DEFMT_LOG=hello::foo cargo r --bin hello
0 INFO  foo
└─ hello::foo::foo @ src/bin/hello.rs:16

$ DEFMT_LOG=hello::bar cargo r --bin hello
0 INFO  bar
└─ hello::bar::bar @ src/bin/hello.rs:22

$ DEFMT_LOG=hello::foo,hello::bar cargo r --bin hello
0 INFO  foo
└─ hello::foo::foo @ src/bin/hello.rs:16
1 INFO  bar
└─ hello::bar::bar @ src/bin/hello.rs:22

$ DEFMT_LOG=hello cargo r --bin hello
0 INFO  hello
└─ hello::__cortex_m_rt_main @ src/bin/hello.rs:8
1 INFO  foo
└─ hello::foo::foo @ src/bin/hello.rs:16
2 INFO  bar
└─ hello::bar::bar @ src/bin/hello.rs:22

status update: jonas-schievink pointed out that with this change, the defmt-test test-runner will not print its progress unless the DEFMT_LOG var is set to info, which is a regression in functionality of the default behavior.
To address the issue, I have proposed adding a println! macro that cannot be filtered in RFC #541. This would be used in defmt-test to preserve the progress output. Until a decision is made on that (by accepting it or proposing a different solution) this PR is blocked.

Update: I have fleshed out the RFC text in the PR description and moved it to issue #571. This PR is blocked on that RFC being approved and defmt::println! being implemented.

update: rebased the PR and addressed inline comments. this is still missing the defmt_test update indicated in the RFC (#571); that update requires println! (PR #569). The other thing that's missing is fixing the snapshot tests, which requires changes to the xtask (setting DEFMT_LOG there)

bors r=Urhengulas

rebased
bors r=Urhengulas

authors: Urhengulas japaric jonas-schievink

repo: knurling-rs/defmt


text:
Context not working in decorator after await action

I'm using Typescript, Koa version is 2.13.4, Node js is 16.11.1
First of all, I am using decorator to replace middleware.
So I wrote down below code.
Decorator:
// hasPermission decorator

export function hasPermission(
    type: PermissionType,
    action: PermissionAction,
): MethodDecorator {
    return function (
        target: Object,
        props: string | symbol,
        descriptor: PropertyDescriptor,
    ) {
        let original = descriptor.value;

        descriptor.value = async function (...args: [HttpContext, ...any]) {
            const ctx = args[0];

            const hasPermission = await ctx.state.user?.hasPermission(type, action);

            if (hasPermission) return await original.apply(this, args);
            else ctx.body = ctx.__('error.needPermission');
        };
    };
}

// hasRole decorator

export function hasRole(role: UserRole | UserRole[]) {
    return function (target: any, props: string, descriptor: PropertyDescriptor) {
        let original = descriptor.value;

        descriptor.value = function (...args: [HttpContext, ...any]) {
            const ctx = args[0];

            if (ctx.state.user?.hasRole(role)) return original.apply(this, args);
            else ctx.body = ctx.__('error.needRole');
        };
    };
}

Controller:
@hasRole([UserRole.Administrator, UserRole.Supporter])
@hasPermission(PermissionType.Shop, PermissionAction.Read)
async all(ctx: HttpContext) {
    const shops = await Shop.find({
        select: ['id', 'name', 'domain', 'endedAt'],
    });

    ctx.body = shops;
}

hasRole has no problem, but hasPermission does.
I want to check user has permission. and it is saved on database.
To check it, I have to using async/await function to get data.
But, a matter occured in this part.
in (1), context works perfectly, however (2) doesn't.
in (2), I can't manipulate any response - status code, returning body and so on.
due to this reason, if user wasn't permitted, just returning 404 error.
I don't understand why can't change context after await action.
// hasPermission

descriptor.value = async function (...args: [HttpContext, ...any]) {
    const ctx = args[0];

    // (1) ctx.body = 'in here, ctx works!'

    const hasPermission = await ctx.state.user?.hasPermission(type, action);

    // (2) ctx.body = 'in here, ctx doesn't work!'

    if (hasPermission) return await original.apply(this, args);
    else ctx.body = ctx.__('error.needPermission'); // Thus, This code doesn't work. only return default error (404).
};

How can I resolve this problem?
Please understand that my English is short and Thanks for reading.

I resolved. next() in middleware is not set 'await', so context doesn't work.

repo: koajs/koa


text:
AE2d test() throws exception on non-GPU environment

Hello. I tried to run test.sh of Dimensionality_Reduction/AE2d on my PC which doesn't have GPU, but failed with the below error message.
terminate called after throwing an instance of 'c10::Error'
  what():  No CUDA GPUs are available

It's because test() in AE2d/test.cpp calls torch::cuda::synchronize() regardless of device type. I think it should be called only on GPU environment. For example:
        if (!device.is_cpu()) torch::cuda::synchronize();

Thank you for reporting the bug and solution.
I changed the source code and confirmed that it works normally.
I reflected it in master branch, and the modified code was archived as support/v1.10.1.
https://github.com/koba-jon/pytorch_cpp/tree/support/v1.10.1
Thank you so much!

authors: koba-jon wagavulin


text:
X86Assembler::align() returns kErrorInvalidArgument when trying to create a single byte constant with newByteConst/newConst

Example Code (CStr() returns 1):
String str = value;

asmjit::X86Mem val = compiler.newConst(asmjit::kConstScopeLocal, str.CStr(), str.GetLength());

asmjit::X86GpVar pval = compiler.newIntPtr("pval");
compiler.lea(pval, val);

call = compiler.addCall(asmjit::imm_ptr(&JitNewValueString), asmjit::FuncBuilder3<void, const char *, size_t, Value *>(asmjit::kCallConvHost));
call->setArg(0, pval);
call->setArg(1, asmjit::imm(str.GetLength()));
call->setArg(2, res);`

This causes the check in x86assembler.cpp:411  to fail:
asmjit.dll!asmjit::X86Assembler::align(unsigned int alignMode, unsigned int offset) Line 411	C++
asmjit.dll!asmjit::X86Context::serialize(asmjit::Assembler * assembler_, asmjit::HLNode * start, asmjit::HLNode * stop) Line 5679	C++
asmjit.dll!asmjit::X86Compiler::finalize() Line 293	C++

The offset argument for the align() call is 1:
 if (alignMode > kAlignZero || offset <= 1 || !Utils::isPowerOf2(offset) || offset > 64)

This problem does not occur when I create at least one other constant in the same scope, i.e. it only seems to occur when the entire constant pool's size is 1.

Thanks! The alignment check needs to be relaxed. I have never hit this before.

Fixed, thanks!

authors: gunnarbeutner kobalicek

repo: kobalicek/asmjit

license: Zlib


text:
Custom Mongo.Encoder protocol

Hi,
This PR adds a feature: Mongo.Encoder protocol.
In our project, we very often spot a case when we need to insert map, generated from some struct into the mongo database. With that PR, instead of writing a custom glue code, we can simply implement Mongo.Encoder protocol. Which in turns results in clearer, more idiomatic Elixir code.

I like the idea. How you do decoding back to domain structs?

@deadtrickster thanks! Right now, we're decoding them manually - and there is no such elixir idiomatic way of doing that, such as here.

yeah I think it is ecto territory.  we should look into it.

authors: deadtrickster esse

repo: kobil-systems/mongodb


text:
Write more thorough explanation of what NFTs are

It would be good to have one page in  where NFTs would be explained thoroughly. It's also easier for explaining to newcomers who are just getting started.
Referring to:
https://github.com/kodadot/nft-gallery/issues/648

Current version of more broad explanation what nfts are is running at: https://docs.kodadot.xyz/how-to-make-nft.html#create-a-piece-of-art

repo: kodadot/docs

license: Unlicense


text:
feat: add new prelaoder graphic

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR type

[ ] Bugfix
[x] Feature
[ ] Refactoring

What's new?

[x] PR closes #2014
[x] added new preloader graphic and slightly adjusted size to fill empty space

Before submitting Pull Request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[ ] I've tested PR on mobile and everything seems works
[ ] I found edge cases
[ ] I've written some unit tests 🧪

Had issue bounty label?

[x] Fill up your KSM address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.

pay 100 usd

😍 Perfect, I’ve sent the payout
💵 $100 @ 184.78 USD/KSM ~ 0.541 $KSM
🧗 EqdyzrzVmeHwMdMwvPeCMnNdbuQDbD3YrjY93xq9Ln3jUGW
🔗 0x54ec6bf420e768e8414c35dce21fbe2ddfefa15511c3390fbcf53ca4420baad6
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues

authors: kkukelka yangwao

repo: kodadot/nft-gallery


text:
feat: Show rmrk version in item description

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR Type

[ ] Bugfix
[x] Feature
[ ] Refactoring

Context

[x] Closes #5681
[ ] Requires deployment <>

Before submitting pull request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </bsx/collection>
[ ] I've tested PR on mobile
[ ] I've written unit tests 🧪
[ ] I've found edge cases

Had issue bounty label?

[x] Fill up your KSM address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot 📸

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.
/ksm/gallery/13328952-54bbd380dc3baaa27b-EVRSOULS-Ranger-00000922

/rmrk/gallery/17483893-9AFFD71D65E3DBBF29-KODA_VILLA-KODA_VILLAGE_2-0000000000000002

it shows 1.0.0 on my end, is that alright? (The 3 digit version format)
for rmrk2 as well

Yup It's correct

pay 10 usd

😍 Perfect, I’ve sent the payout
💵 $10 @ 36.61 USD/KSM ~ 0.273 $KSM
🧗 Caiv9TbPz68q5dC8EcHu5xKYPRnremimGzqmEejDFNpWWLG
🔗 0xb6e8c99ead509daf936ca3932f1c9798ad2f7579f951c1820dea24b6f0dbcc15
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues

authors: Jarsen136 exezbcz vikiival yangwao


text:
stack "flickers" after a new window is added to the stack and focus is moved back and forth

Hi,
I have a little problem with stacks, which I hope can be solved because it's quite annoying
Let me try to describe how to reproduce it.
Let's suppose a space, with only 3 terminal windows, side by side.
Let's call them w1, w2 and w3

go into w1, and stack it on top of w2, with (supposing 39410 is the id of w2)

yabai -m window 39410 --stack `yabai -m query --windows --window | jq '.id'`

The 2 windows are "merged", and the focus is in the new stack
So now we have one stack with w1 (visible) and w2 ("behind"), and a single w3 window next to it

from the same w1 window (now in the stack), move the focus to the other window left (w3)

yabai -m window --focus east

The focus moves and you're now in w3. You see w1 (unfocused) and w3 on the screen

finally, move the focus back to the stack

yabai -m window --focus west

Here the problem happens. When the focus changes, back to the stack, w1 disappears and w2 is shown instead.
w2 became the "front window of the stack", all by itself.
This is the 'flicker' effect I'm trying to describe here
Note that this does NOT happen if the focus is moved back and forth using the mouse
It happens only when the focus is moved using command-line calls (or keyboards bindings for the same commands in skhd)
is it only me, or can others reproduce it too?
Thanks!

same issues here.

I run into the same issue, but it seems to happen only with iTerm for me.

Duplicate of  #1311 and fixed on master.

authors: grozan koekeishiya mikalcallahan tshu-w

repo: koekeishiya/yabai


text:
Layer border in v90

The wiki page on today's new update states that Framer now support border per side, however I haven't been able to get this to work with the code below:
layerA = new Layer
    border:
        left: 1
        right: 1
        bottom: 0
        top: 0

Please let me know if I'm missing something

Hmm. We could discuss if we want to enable this shortcut, but the current syntax is:
new Layer
	borderWidth:
		left: 1
		right: 1
		bottom: 0
		top: 0

Ah, i see, thank you! I thought I tried that.

repo: koenbok/Framer


text:
Change hierarchy API: superLayer/subLayers → parent/children

We are going to change the superLayer/subLayers keywords to parent/children. The words look less intimidating and are more descriptive of what they do.
I often noticed that beginning programmers don't get the terminology of super/sub, whereas everyone understands parent/children right away.
Old methods will continue to work for a while so old tutorials and prototypes continue to work.
List of changed methods:
.superLayer -> parent
.superLayers -> parents
.subLayers -> children
.siblingLayers -> siblings

addSubLayer: (layer) -> @addChild(layer)
removeSubLayer: (layer) -> @removeChild(layer)
subLayersByName: (name) -> @childrenByName(name)
siblingLayersByName: (name) -> @siblingsByName(name)
subLayersAbove: (point, originX=0, originY=0) -> @childrenAbove(point, originX, originY)
subLayersBelow: (point, originX=0, originY=0) -> @childrenBelow(point, originX, originY)
subLayersLeft: (point, originX=0, originY=0) -> @childrenLeft(point, originX, originY)
subLayersRight: (point, originX=0, originY=0) -> @childrenRight(point, originX, originY)
_superOrParentLayer: -> @_parentOrContext()

I'd prefer "ancestors" over "parents", cause factually there can be only one parent, and it maps nicer to "siblings" that we use elsewhere.

authors: edwinvanrijkom koenbok


text:
Add basic CSS styles

Something to start with? Very subjective to taste, though.

@jacobhamblin thanks! I moved variables into a separate file.

authors: jacobhamblin koistya

repo: koistya/react-static-boilerplate


text:
OpenAPI file upload generates incorrect Api interface.

Operation with a file upload generates incorrect Api interface.
openapi.yaml
      requestBody:
        content:
          application/octet-stream:
            schema:
              type: string
              format: binary

see http://spec.openapis.org/oas/v3.0.3#considerations-for-file-uploads
Generated interface:
Object someOperation(@io.micronaut.http.annotation.Body File body);
The param should be of type byte[].
I hope this can get fixed because we need this in an application we're developing.
Thanks!

Or even better StreamingFileUpload, but I think this requires multipart/form-data.

I cannot reproduce this issue, see 07e94de. Which version of this codegen did you used?

I've implemented fileupload. Is this sufficient for your usecase?

Hi, thanks for the reply & fix! The MediatypeController.mediatypePostMultipart example is exactly what I was looking for. I'll test it next week with our openapi.yaml. Thanks again.

Please try version 1.6.3.

authors: TrisTronNL stephanschnabel

repo: kokuwaio/micronaut-openapi-codegen


text:
Freewall Flex layout not Auto-Resizing.

Freewall Flex layout grid not working properly, means its not taking height as per inner content that cause to hide the inner elements.

Same issue here

authors: gerharddt ghost

repo: kombai/freewall


text:
The type of the path parameter is set to the value of the example if example is provided

If the following annotation is added @ApiParam(example = "asdf.png") @PathParam("media") String media, the generated swagger.json has this part:
{           "name" : "media",           "in" : "path",           "required" : true,           "type" : "asdf.png",           "pattern" : ".+",           "x-example" : "asdf.png"         }
If I remove @ApiParam, the correct JSON has "type" : "string"

Fixed in 3.1.4

repo: kongchen/swagger-maven-plugin


text:
[BUG] The effort for tackle-testapp with openJDK17 target seems low

Is there an existing issue for this?

[X] I have searched the existing issues

Konveyor version
main
Priority
Major
Current Behavior
Using Tackle-Testapp
Analysis configuration:
Analysis mode: Source code + dependencies
Targets: OpenJDK 17
scope: Application and all dependencies, including known Open Source libraries
No additional advanced options

Expected Behavior
No response
How Reproducible
Always (Default)
Steps To Reproduce
No response
Environment
- **Analyzer Image SHA**
- **JDTLS  base image SHA**
- **Provider Settings JSON**

Anything else?
No response

@kpunwatk Are you sure you used the exact same options in both analyses? I am unable to reproduce this with latest images

Closing as this is not reproducible. @kpunwatk Please feel free to re-open when you have a reproducer

authors: kpunwatk pranavgaikwad

repo: konveyor/analyzer-lsp


text:
MIG-832: Document migplan persistent volume fields

Description
Check each of the following when appropriate to help reviewers verify work is complete.
Modifying an existing version

[ ] I modified operator permissions in the OLM CSV and operator.yml
[ ] I modified the operator deployment in the OLM CSV and operator.yml
[ ] I modified operand permissions in the OLM CSV and ansible role
[ ] I modified CRDS in the OLM CSV and ansible role

Adding a new release version

[ ] I created a new z release directory in deploy/olm-catalog/crane-operator
[ ] I updated channels in the crane-operator.package.yaml
[ ] I created a new release directory in deploy/non-olm
[ ] I created or updated the major.minor link in deploy/non-olm
[ ] I updated the spec.skips parameter in the CSV

@apinnick Apparently when I said the PR was updated last week I was wrong. I forgot to commit my local changes before force-pushing the branch again. It's updated now.

@apinnick updated it one more time -- I realized that I didn't address the empty storageClass selection use case originally.

repo: konveyor/mig-operator


text:
Cannot start mig-ui locally

I want to start this project locally, and then execute it as described in the document
yarn, yarn build, yarn start
have been executed before cp config/config.dev.json.example config/config.dev.json, but when I open the browser, such an error will be reported：

I did not make any changes to the default config.dev.json

If local start is not supported (no server); please notify me and consider whether to update the document

@jwangyangls Local is supported - you must provide a clusterApi & a discoveryApi value in the config file to a running cluster.

repo: konveyor/mig-ui


text:
Support ussage of HTTPS with self-hosted S3 providers by accepting CA certs

Tried to use address of
https://http://minio-gpte-minio.apps.cluster-jwm.jwm.mg.example.com
Connection failed: The Backup storage cloudprovider test failed [RequestError: send request failed caused by: Put https://minio-gpte-minio.apps.cluster-jwm.jwm.mg.example.com/jwmbucket/a3965eba-bfb4-11e9-b678-0a580a830011: x509: certificate signed by unknown authority]. | TestFailed
How do we handle CA for this?
Can we also allow an insecure mode, check box perhaps from ui?

Closed via #606


text:
Support specify download url

Zig releases the toolchain at a specific commit at https://ziglang.org/builds/zig-xxx.
We currently support specifying the toolchain with released versions or master, but it can be an advanced requirement to hardcode the download URL.
We can factor out the steps to resolve the URL and support passing user-define URLs via input.
I don't have time to work on it now and it seems no real-world user requirement for it. Thus I tend to leave it as help wanted good first issue until a real-world use case is reported or someone takes it up.

Closing...
After a closer look, I notice that it's hard to define the cache key of such a URL. Postpone to any real-world requirement.

No. The cache key can be constructed with commit id + platform.

https://ziglang.org/builds/zig-linux-x86_64-0.11.0-dev.2912+d65b42e07.tar.xz
It seems now the upstream file server doesn't contain the old URL anymore. Closing...

repo: korandoru/setup-zig


text:
Using mypy to verify check_str_format_call?

@ThibaultLemaire Recently I found mypy.checkexpr.ExpressionChecker.check_str_format_call method.
I think that is basically what you did as part of #43, right? If that's exactly same thing would you mind replacing your code with the one referenced.

I think that is basically what you did as part of #43, right?

Correct. visit_call_expr calls visit_call_expr_inner which in turn calls check_str_format_call. I even found some of my old breakpoints in there which means I must have been aware of its existence.
I believe I had a good reason not to call it directly, but I can't recall and I don't see anything important in visit_call_expr_inner now. Maybe visit_call_expr was too big and I was too happy that my code worked to dig any deeper :man_shrugging:
Well spotted, feel free to change it if you want :+1:

I think that is basically what you did as part of #43, right?

Correct. visit_call_expr calls visit_call_expr_inner which in turn calls check_str_format_call. I even found some of my old breakpoints in there which means I must have been aware of its existence.
I believe I had a good reason not to call it directly, but I can't recall and I don't see anything important in visit_call_expr_inner now. Maybe visit_call_expr was too big and I was too happy that my code worked to dig any deeper :man_shrugging:
Well spotted, feel free to change it if you want :+1:

If I get some time, I will give it a shot.

If I get some time, I will give it a shot.

authors: ThibaultLemaire kornicameister

repo: kornicameister/loguru-mypy


text:
swayipc error: invalid integer, expected i32

I've been having a very sporadic issue where sway-overfocus will suddenly stop working; issuing any typical command in a shell returns:
$ sway-overfocus split-lt float-lt output-ls

swayipc error: invalid value: integer `4294967240`, expected i32 at line 1 column 9997

This problem persists for a while, then sporadically fixes itself, making it hard to test. Do you have any advice on what I could do to get more information when this happens again?
I got curious and looked through recent issues and PRs in swayipc-rs and found a possible clue: this PR fixes a possibly similar issue in i3status. Since sway-overfocus uses swayipc version 3.0.0, and as far as I can tell the aforementioned PR has not yet been included in a new tag of swayipc, I suppose asking the swayipc developers to tag a new release and push to crates.io would be a good idea; then the swayipc dependency could be updated here and hopefully this problem will be solved.

There are three places where swayipc can error in my program:

Starting a connection (unlikely).
Retrieving the tree.
Running the resulting focus command.

If you can reproduce the error, run RUST_LOG=info sway-overfocus <...> to figure out which it is.
Are you using i3? Looking at the last issue you mentioned, it might make sense to check whether your i3 version is up to date as well.
I'm a bit tied up with finishing my master's right now, but that'll be done in a week or so. I'll look into it then.

I almost forgot, sway-overfocus needs to be built in debug mode to enable logging. So you would run something like RUST_LOG=info cargo run -- <...> to get more info.

If you can reproduce the error, run RUST_LOG=info sway-overfocus <...> to figure out which it is.
I almost forgot, sway-overfocus needs to be built in debug mode to enable logging. So you would run something like RUST_LOG=info cargo run -- <...> to get more info.

Thanks! Now I hope it happens again...

Are you using i3? Looking at the last issue you mentioned, it might make sense to check whether your i3 version is up to date as well.

Version 4.14.1, so I should probably update

In any case, the issue seems to be with swayipc-rs or i3wm. You can try upgrading i3, and if the problem reappears, nudging the swayipc-rs devs to make a patch release.

authors: c-dilks korreman

repo: korreman/sway-overfocus


text:
APC UPS Daemon (No USB) where and how can I define the UPS IP address

Hi
I have an APC SMT750I UPS with UPS Network Management Card 2 (AP9631)
I can reach the UPS from browser / telnet / SNMP. IP address is: 192.168.252
I wanted to use this addon but I don't know where and how can I define the card's IP address in the addon.
I tried to setup in the config:
name: APC UPS
cable: ether
type: net
device: 192.168.252
extra: []

I tried too:
device: '192.168.252:user:password'
and
device: '192.168.252:*user*:password'
But I got the same error every time:
Feb 12 22:26:06 a722577e-apcupsd-net syslog.info syslogd started: BusyBox v1.30.1
Feb 12 22:26:06 a722577e-apcupsd-net daemon.notice apcupsd[6]: apcupsd 3.14.14 (31 May 2016) unknown startup succeeded
Feb 12 22:26:06 a722577e-apcupsd-net daemon.info apcupsd[6]: NIS server startup succeeded
Feb 12 22:26:21 a722577e-apcupsd-net daemon.warn apcupsd[6]: Communications with UPS lost.
send-mail: account default not found: no configuration file available

The USB version is works fine anyway.
Any idea?
Thanks
T

I've never dealt myself with an APC network UPS.
I'm not sure if it's a typo, but 192.168.252 is not an IP address. You should have 4 numbers, not 3.
Beyond that, I recommend you read through this thread which seems to have a lot of different troubleshooting advice.
A few tidbits:

net is used for connecting to another apcupsd instance. snmp is for connecting to SNMP UPSes (which I think yours is)
The username/password is not necessarily what the web username/password is

Try checking those things, and read through that thread, and if you still can't get it working, come back here.

There haven't been any updates to this issue so I'm closing it.

authors: korylprince redskinhu

repo: korylprince/hassio-apcupsd


text:
Can you please update the documentation?

I can only explain my issues as https://github.com/kotlin-graphics/imgui/wiki/Using-libGDX being outdated.

LwjglGlfw and ImplGL3 don't have any INSTANCE members.
Nothing about the docs say you have to install uno-sdk.
And even once installed, it says GlfwWindow(long) (the constructor of the class with the window handle) is private.
GlfwWindow(GlfwWindowHandle) is public, but GlfwWindowHandle(long) doesn't exist. How do you initialize the window?
LwjglGlfw.init() doesn't even exist.

So what you actually have to do is something like this:
import com.badlogic.gdx.ApplicationAdapter;
import com.badlogic.gdx.Gdx;
import com.badlogic.gdx.backends.lwjgl3.Lwjgl3Graphics;
import com.badlogic.gdx.graphics.GL20;
import glm_.vec2.Vec2i;
import imgui.Context;
import imgui.ImGui;
import imgui.impl.ImplGL3;
import imgui.impl.LwjglGlfw;
import uno.glfw.GlfwWindow;
import uno.glfw.GlfwWindowHandle;

public class Game extends ApplicationAdapter {
    private GlfwWindow window;
    private LwjglGlfw lwjglGlfw;
    private ImplGL3 implGL3;
    private ImGui imGui = ImGui.INSTANCE;
    private Context context;

    @Override
    public void create() {
        window = new GlfwWindow(((Lwjgl3Graphics) Gdx.graphics).getWindow().getWindowHandle());
        // What does the Vec2i param do?
        lwjglGlfw = new LwjglGlfw(window, true, LwjglGlfw.GlfwClientApi.OpenGL, new Vec2i());
        implGL3 = new ImplGL3();
        context = new Context(null);

        imGui.styleColorsDark(null);
    }

    @Override
    public void render() {
        Gdx.gl.glClearColor(0, 0, 0, 1);
        Gdx.gl.glClear(GL20.GL_COLOR_BUFFER_BIT);

        lwjglGlfw.newFrame();

        imGui.begin("Demo_0", new boolean[]{true}, 0);
        imGui.text("Hello, world!");
        imGui.end();

        imGui.showDemoWindow(new boolean[]{true});

        imGui.render();
        implGL3.renderDrawData(imGui.getDrawData());
    }

    @Override
    public void dispose() {
        lwjglGlfw.shutdown();
        context.shutdown();
    }
}

And yet that still doesn't work because the GlfwWindow constructor with the long handle is private for some reason. Is there something I'm missing?

I can only explain my issues as https://github.com/kotlin-graphics/imgui/wiki/Using-libGDX being outdated.

Yep, you are right

* `LwjglGlfw` and `ImplGL3` don't have any `INSTANCE` members.

They are full valid classes now

* Nothing about the docs say you have to install uno-sdk.

No, it's true

* And even once installed, it says `GlfwWindow(long)` (the constructor of the class with the window handle) is private.

* `GlfwWindow(GlfwWindowHandle)` is public, but `GlfwWindowHandle(long)` doesn't exist. How do you initialize the window?

The constructor uses an inline class, which is still yet to come on java (Panama Project) and there is at the moment no compatibility from Kotlin side.
For this very reason, you have a static GlfwWindow.from(long)

* `LwjglGlfw.init()` doesn't even exist.

No, it's been refractored in the process of matching closely the original library
Anyway, this should pretty much underline that I alone have not the financial, time and working resources at all as the original author(/s, because right now they are even multiple people) of the library.
That's why I'm totally open to contributions and most of the time I try to tempt people to jump in and give a hand, like in your case :)  (I'll send you right away an invite to join the repo)
Feel free to close if you repute it ok

Sorry, I don't really have the time, and I don't really know Kotlin or this library much, so I don't think I would help. I'll look for someone who can.

repo: kotlin-graphics/imgui


text:
Support linuxArm64 Kotlin Native target

Description
We would like to support the linuxArm64 Kotlin Native target.
See the targets supported by Kotlin Native for more details about it.
Dependencies
This issue is blocked by the following ones:

[ ] Currently doesn't support running tests in Gradle.

Checklist

[ ] Add the target in our Multiplatform Gradle plugin, add the target in the integration and the delivery workflows, add badge in README and update the unreleased changelog.
[ ] Close this issue as completed and update tracking ones if present.

This target currently doesn't support running tests in Gradle.

repo: kotools/types


text:
Any plans for requestAnimationFrame ?

Nice plugin  but it does spike the timeline a bit when using multiple or large canvas. Do you mind adding requestAnimationFrame ?
https://github.com/rendro/easy-pie-chart/blob/97b5824bf423410c3c6a1e971860159f17ee6ee6/dist/easypiechart.js#L115-L125

That's very nice suggestion! I'll add it

:+1:

Back to requestAnimationFrame question.
Currently jquery-circle-progress is a jQuery plug-in and it uses jQuery.animate(...) for the circle animation. jQuery.animate(...) will use requestAnimationFrame in jQuery#3.x.
So I guess this issue is out of scope right now and I'm going to close it.
However I'm planning to refactor the library and remove jQuery dependency in future. In that case I will use some animation library that uses requestAnimationFrame or I'll create it by myself.

authors: danyj kottenator

repo: kottenator/jquery-circle-progress


text:
Document ds-search-in prop

The ds-search-in prop in Dataset.vue needs to be documented.

Fixed with 8e99680c39a492c9859e174a47af19b3f11425f6 and 2b92bce9d6477163fed425ced886c006ea194a13

repo: kouts/vue-dataset


text:
The "Close" Click does not work when code contains multiple Chests

There is a code aktive, that gives you 3 Gold Zorbus Chests.
The App stops here and does not know what to do. If i click on the button manually raltively fast the script runs on, otherewise it crashes.

fixed in https://github.com/kpa23/idle_codes/releases/tag/0.1.5


text:
disable docllint in javadoc

javadoc as of JDK 8 runs doclint, which fails the build on javadoc errors.
There are quite a lot javadoc errors in this project, and so it's impossible to build it.
This PR is a quick fix (see here for more info), and helps to unblock a tenant ATM.
A more correct fix would be to correct all the javadoc errors.

closing old pr

repo: kpn-dsh/dsh-sdk-platform-java


text:
#10 fix

#10

とりあえずドラフト作成

devにマージするためclose


text:
Sned Walk

TL;DR
Send Walk (#5)
Related Tasks
Create ./connect.lua (#2)
[FEATURE} Socket Connection (#1)

LG

repo: kqnade/CHaserLua