abbas ali chezgi
abbas ali chezgi
in this sample: ``` header: version: 10 repos: meta-test: url: https://192.168.1.1/test/meta-test layers: meta-test-core: ``` we have a self signed git server at 192.168.1.1 this error happens when running: ``` kas...
@jan-kiszka it is before running bitbake. it is in `kas checkout` phase. not build phase. it has nothing with bitbake.
bitbake uses my home .gitconfig and .git-ceedentials but kas creates its home tmp dir and a simple .gitconfig. in my system bitbake works with adding some configs to my .gitconfig...
all ci systems can maintain users configs with scripts. therefore using user's configs can be reproducible. creating git configs is not responsibility of kas or any tool. this must be...
i am not active on kas.
or maybe we can add another connection type: `Pipe` and we can limit connection type of user to it
@kozlovic my usage: i want to use my authorization callout user to be in process. therefore my jwt must limit this user for only in process connection, or 127.0.0.1 must...
@kozlovic if i can limit user jwt to only IN_PROCESS connection type, it works for me.
this happens for me also. smaple project structure: - testgo.code-workspace - moda/[ go.mod, a.go ] - modb/[ go.mod, main.go] testgo.code-workspace: ``` { "folders": [ { "path": "moda" }, { "path":...
condition it happens: - custom OS build using Yocto - tun/tap interfaces