Vladimir Pouzanov
Vladimir Pouzanov
I'm facing a very similar issue with tailscale (which uses L3 interface as well, a variant of wireguard), getting `UnknownEthernetType` errors when I try to connect to the service-ip over...
Actually never mind, my issue was fixed with `bpf.lbExternalClusterIP=true`
@erikschul I don't have the cluster config at hand, but it's a tailscale server running on the node. There are no `devices` settings, if I remember it correctly.
I intend to move zinc into a direction where you'd just define HAL (ioregs + peripheral traits) in a crate, add it as a dependency and call it a day....
Not sure about the CI failure as it's in the file I didn't touch.
That's fair. My reasoning was that it was easier to have specific rust dependencies and to have a sidecar postgres in the shell (given lemmy doesn't work without postgres at...
@xyhp915 tentative ping, I suppose.
It actually makes sense: there's a single graph (the latest opened) that git looks at: https://github.com/logseq/logseq/blob/master/src/electron/electron/state.cljs#L12
I made a [patch to npm's liveserver](https://github.com/farcaller/metanotes-legacy/blob/feature/v2/patches/live-server%2B1.2.1.patch) that [allows to use it with ibazel](https://github.com/farcaller/metanotes-legacy/blob/feature/v2/src/frontend/web/BUILD.bazel#L51). I bundled it all with rollup.