zig 0.14.x -> 0.15.x was mostly easy, but some gremlins floating around still where release-safe causes some segfaults but release fast/small does not?
will continue to chip away... slowly 🤓
zig 0.14.x -> 0.15.x was mostly easy, but some gremlins floating around still where release-safe causes some segfaults but release fast/small does not?
will continue to chip away... slowly 🤓
* examples for py/go (same ones, in both langs)
* knocked out some old netconf related todos
* ???
1/2
* examples for py/go (same ones, in both langs)
* knocked out some old netconf related todos
* ???
1/2
turns out I wasn’t forwarding acks from the “outer” session to the proxied connection, so the server just stopped sending mid-stream.
1/2
turns out I wasn’t forwarding acks from the “outer” session to the proxied connection, so the server just stopped sending mid-stream.
1/2
proxy jump stuff is *mostly* working w/ libssh2, cli is fine, but netconf just stalls out when receiving capabilities
feels real bad when you think you’re checking something off the list then realize... not quite!
proxy jump stuff is *mostly* working w/ libssh2, cli is fine, but netconf just stalls out when receiving capabilities
feels real bad when you think you’re checking something off the list then realize... not quite!
not quite as easy as -J w/ openssh, but it does the trick!
thinking its time for docs and examples... closign in on an rc i think!
not quite as easy as -J w/ openssh, but it does the trick!
thinking its time for docs and examples... closign in on an rc i think!
tldr some folks were unhappy about storage ballooning on launcher pods a bit. i never cared cuz storage is cheap :P
1/3
tldr some folks were unhappy about storage ballooning on launcher pods a bit. i never cared cuz storage is cheap :P
1/3
i did manage to make some progress porting some scrapli community things into the new unified zig/go/py yaml format though 😎
i did manage to make some progress porting some scrapli community things into the new unified zig/go/py yaml format though 😎
to them i say: kick rocks 🪨
its fun, funny, and it literally describes what the thing is
go fork (it) yourself if hate the name 🤷♂️
to them i say: kick rocks 🪨
its fun, funny, and it literally describes what the thing is
go fork (it) yourself if hate the name 🤷♂️
i think this is/was because i used to python a lot more and typing being a suggestion meant docs were (imo) even more important
1/2
i think this is/was because i used to python a lot more and typing being a suggestion meant docs were (imo) even more important
1/2
scrapli(py) test kills a netconf session, lazy me didnt free it. test passes locally, but fails 100% of the time in ci
root cause: the killed session was trying to log something to a logger that has been gc'd 😇
scrapli(py) test kills a netconf session, lazy me didnt free it. test passes locally, but fails 100% of the time in ci
root cause: the killed session was trying to log something to a logger that has been gc'd 😇
tmate, strace, lsof, gdb and a lot of pain later... i was unlocking + signaling *before* setting the stop flag. thread kept running. join hung forever.
computers are hard
tmate, strace, lsof, gdb and a lot of pain later... i was unlocking + signaling *before* setting the stop flag. thread kept running. join hung forever.
computers are hard
guess you are supposed to do clickybaity stuff or like nicely format things or whatever
im just gunna (try to) keep posting nerd stuff im into. if you like that, neat, we can be friends!
if not... meh?
guess you are supposed to do clickybaity stuff or like nicely format things or whatever
im just gunna (try to) keep posting nerd stuff im into. if you like that, neat, we can be friends!
if not... meh?
it was. as nobody could have foreseen.
user error 😇
so yeah, epoll/kqueue things are looking mighty nice for libscrapli... will play more this weekend
it was. as nobody could have foreseen.
user error 😇
so yeah, epoll/kqueue things are looking mighty nice for libscrapli... will play more this weekend
attempting to replace tight loop over non blocking reads (w/ sleeps ofc) with kqueue
maybe (probably?) user error but not as performant as i was hoping, gotta spend some more time poking about
also need to check out io_uring 🫠
attempting to replace tight loop over non blocking reads (w/ sleeps ofc) with kqueue
maybe (probably?) user error but not as performant as i was hoping, gotta spend some more time poking about
also need to check out io_uring 🫠
blog.jetbrains.com/team/2025/04...
I always enjoy looking at the results, more data more good. go do it
blog.jetbrains.com/team/2025/04...
I always enjoy looking at the results, more data more good. go do it
static analysis stuff is such low effort for varying amounts of reward
the payoff doesnt really have to be much though.
this one feels like a cool tool to keep in the toolbelt
static analysis stuff is such low effort for varying amounts of reward
the payoff doesnt really have to be much though.
this one feels like a cool tool to keep in the toolbelt
bit of faffing about w/ extensions and getting settings where i want, but its quite snappy, simple, and generally nice to use.
bonus points for non m$-ness of it all 😇
bit of faffing about w/ extensions and getting settings where i want, but its quite snappy, simple, and generally nice to use.
bonus points for non m$-ness of it all 😇
be REALLY careful with `git filter-repo` -- I made some dumb mistakes (decisions?) and wanted to clean some history and... yeah I mean they say be careful but, like... really be careful :)
in the end, history cleaned, nothing destroyed. go team.
be REALLY careful with `git filter-repo` -- I made some dumb mistakes (decisions?) and wanted to clean some history and... yeah I mean they say be careful but, like... really be careful :)
in the end, history cleaned, nothing destroyed. go team.
I am obviously a potato 🥔, but I thought mcp was very... not sane? this post got traction on hacker news and I very much agree with it.
"resulting in some very strange design decisions, poor documentation, and an even worse specification of the actual protocols"
I am obviously a potato 🥔, but I thought mcp was very... not sane? this post got traction on hacker news and I very much agree with it.
"resulting in some very strange design decisions, poor documentation, and an even worse specification of the actual protocols"
ctypes are kinda painful, but work. cffi seemed no more performant (small sample) and would be an extra dep, so have been just sticking to ctypes.
netconf things getting bound into scrapli(py)... progress!
ctypes are kinda painful, but work. cffi seemed no more performant (small sample) and would be an extra dep, so have been just sticking to ctypes.
netconf things getting bound into scrapli(py)... progress!
tried to faff about with xcode instrumentation and i *think* it can be super powerful but it was too much for my short attention span
but yeah, would be clutch to have a better darwin native setup since im a fanboy and all that
tried to faff about with xcode instrumentation and i *think* it can be super powerful but it was too much for my short attention span
but yeah, would be clutch to have a better darwin native setup since im a fanboy and all that
its pretty much idiot proof w/ the mcp package
its neat i guess. stdin/out stream instead of just a rest or grpc feels strange. 1/2
its pretty much idiot proof w/ the mcp package
its neat i guess. stdin/out stream instead of just a rest or grpc feels strange. 1/2
i used calver for scrapli (till now?) because... you can pin, you can see commits, and ill release on schedule to make my life easy 🤷♂️
a bad idea. one of many! i still dont think semver is all its cracked up to be though
i used calver for scrapli (till now?) because... you can pin, you can see commits, and ill release on schedule to make my life easy 🤷♂️
a bad idea. one of many! i still dont think semver is all its cracked up to be though