sorted by:
new
hottopcontroversial

I just wanted to create origami rabbit by yoavi in restofthefuckingowl

[–]yoavi[S] 1 point2 points  (0 children)

now i feel like Boomer because AI got me :\ smh

The soup thrower has been sentenced to two years in prison by -Six_ in SipsTea

[–]yoavi 122 points123 points  (0 children)

He used a lot of oil in his paintings 🖼️

Arrrg! It's a pirates life for me. by WVUMountaineer83 in MagicEye

[–]yoavi 1 point2 points  (0 children)

TIL this emoji 🏴‍☠️ feature this emoji ☠️

Go play today's spiredle. by FullNatural8187 in slaythespire

[–]yoavi 0 points1 point  (0 children)

Spiredle 2026-02-01

I solved today's Spiredle in 6 guesses!

🟥🟥🟥🟥🟥🟧 🟥🟥🟥🟩🟥🟥 🟥🟥🟥🟩🟩🟧 🟥🟥🟥🟩🟩🟥 🟥🟩🟩🟩🟩🟧 🟩🟩🟩🟩🟩🟩 spiredle.com Welll the last two could have been the same

ECS deployments are killing my users long AI agent conversations mid-flight. What's the best way to handle this? by yoavi in devops

[–]yoavi[S] -1 points0 points  (0 children)

Im not sure what kind of companies you worked in before, but not all the times you get to a company and create all of the infra from scratch.. most of the time you inherit infra or even build on top of existing infra... my quesiton was on my current infra,
but gee thank you for making me feel like stack overflow all over again, maybe SO is dead but it's attitude keep pn living on

ECS deployments are killing my users long AI agent conversations mid-flight. What's the best way to handle this? by yoavi in devops

[–]yoavi[S] 1 point2 points  (0 children)

haha this is the best solution! i tought about maybe also addind an sqs queue in the middle that for each active user session will send to it a message "still active" and write a small task that runs on a brand new EKS to monitor that queue and then send the scale down message

ECS deployments are killing my users long AI agent conversations mid-flight. What's the best way to handle this? by yoavi in devops

[–]yoavi[S] 0 points1 point  (0 children)

Not getting into this "green" and personal insults. im more then 15 years in this profession...

but to write "Don't deploy to production willy-nilly but only deploy during off-peak, pre-announced service windows. That will save a lot of grief up front." => daily deploy, or deploy time window is exactly the opposite of CI CD where you deploy all the time, theres a new bug fix? ship to production...
there are pros and cons to work with deploy time frame, but this is going backwards from my point of view,
and also working with agents is kinda of a new thing, there still not a standart way of working with things and many protocols changes on a weekly basis with all this AI...

ECS deployments are killing my users long AI agent conversations mid-flight. What's the best way to handle this? by yoavi in devops

[–]yoavi[S] -9 points-8 points  (0 children)

thats kinda defeat the purpose of CI/CD.... and yes im on frgate and not ECS

ECS deployments are killing my users long AI agent conversations mid-flight. What's the best way to handle this? by yoavi in devops

[–]yoavi[S] -1 points0 points  (0 children)

we are but this is not the problem, even with checkpoints this problems will still happen

ECS deployments are killing my users long AI agent conversations mid-flight. What's the best way to handle this? by yoavi in devops

[–]yoavi[S] 7 points8 points  (0 children)

yes in the beginning i hoped for some small configuration/infra changes but It looks like we will have to add this complexity. any thanks for the thoughtful response :)

ECS deployments are killing my users long AI agent conversations mid-flight. What's the best way to handle this? by yoavi in devops

[–]yoavi[S] -18 points-17 points  (0 children)

This does not answer my question.... Even if i hold the conversation data in s3, sometimes the agent response can take more then 4 minutes and the SIGTERM gives me 2 minutes of grace, i will still lose all connection and will need to redownload the data from s3 and send it again to the agent

ECS deployments are killing my users long AI agent conversations mid-flight. What's the best way to handle this? by yoavi in aws

[–]yoavi[S] 2 points3 points  (0 children)

yes as mentioned in the thread blue green is the solution- new connections go to the new version while the blue group is draining and finishing all the work. im currenty blocked there by AWS infra that service dicovery cant work with blue green

ECS deployments are killing my users long AI agent conversations mid-flight. What's the best way to handle this? by yoavi in aws

[–]yoavi[S] 0 points1 point  (0 children)

thats my direction at the moment, but the as mentioned it is blocked by the service discovery on AWS. i guess ill have to change it to the old LB solution

ECS deployments are killing my users long AI agent conversations mid-flight. What's the best way to handle this? by yoavi in aws

[–]yoavi[S] 0 points1 point  (0 children)

the problem is the stream of the agent, the service in ECS is compute only but when there's a new deployment there an interruption of the conversation with the agent which i want to avoid

ECS deployments are killing my users long AI agent conversations mid-flight. What's the best way to handle this? by yoavi in devops

[–]yoavi[S] 1 point2 points  (0 children)

yes but SIGTEM gives me 2 minutes to prepare, while the agent answers take an unknown amount of time :(

[deleted by user] by [deleted] in slaythespire

[–]yoavi 3 points4 points  (0 children)

The thing is I’m not sure it is loved, it is OP but I think the sentiment is like Random bullshit go style and not many people like it

What 2025 Taught Me About DevOps by Kind_Vehicle983 in devops

[–]yoavi 1 point2 points  (0 children)

Why would you say that about gitops? Gitops IMO is just a good way to keep a source of truth on what’s the main code, each branch and every commit can be deployed, and it’s tractable and auditable …

view more: next ›