Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@halfflat I don't mind asynchronous execution. I'm all in for it. As long as I can check the task's state at any given time!
With kube client this is not the case. IDK where they got that OKHttp lib from (can't find that class in their GH), but they are using THAT: https://github.com/wangweijun123/... . Deep deep inside. Behind a static context.
Sooo.. my current workaround - connect to the pod in a separate websocket and monitor the data stream in the shell. As soon as no data is received in last 5seconds poll - call it a complete data push.
ffs..... I want to kick someone
Related Rants
Coworker's whiteboard today
Building a wheel is great.
Building a steering wheel is also great
Building a brakes pedal is amazing.
Making them work asynchronously - not that good of an idea is it...
Who the fuck thought separating data stream (copying bytes) from stream control (when does the stream start/end) is a good idea...?
- open a connection
- send data to the stream
- send() returns
- close the connection
Apparently, the send() does not copy the data and returns. Instead, it enqueues the data copying task end returns. When does the actual copying start? IDK. When does it end? IDK. Can I close the conn? NO!
This thing is UNUSABLE. And I'd riddle it with reflection-based workarounds if it weren't for the static methods.
Fuck!
rant
async
kubernetes
java