Jump in the discussion.

No email address required.

I don't see a problem. Ask them politely to stop wasting your bandwidth, when they refuse block them--and suddenly it's 100% their problem and they have an epic headache because they are harassed by their dependencies and contributors complaining that nothing even builds any more. So then they are forced to add some sensible cashing/mirroring and beg you to unblock them.

I just don't see why they play the victim and blame Microsoft (for some reason, when FFmpreg was the culprit) when they hold all the cards. I guess it's some of the old pimple eyed open sores fanatics fighting the Man since the nineties lmao.

Jump in the discussion.

No email address required.

Well, it's not so much ffmpeg's fault as the many ffmpeg forks automatically pulling in ffmpeg's ci settings. Really, the way CI systems tend to be designed is fricking insane - why are we literally redownloading all our dependencies, including basic os components, from scratch every time we do a ci run? Why not just cache the vm image at the stage immediately before installing the software under test? But, it works so I don't complain about it.

Jump in the discussion.

No email address required.

They tell you to cache the dependencies but most devops engineers are r-slurred bros who just chase fads. They read FAANG engineer blog posts to maxx their career but completely lack foundational knowledge and the intelligence to understand whats going on.

This is causing a lot of small issues in the long run including gatekeeping the industry by filtering out competent tech guys in favor of their bro/hipster clones.

Jump in the discussion.

No email address required.

Well dependencies can change between ci runs. Though I guess there can be a check prior to that to see if dependencies have changed and only redownload if there is a change.

And I guess it's to ensure that access to those dependencies is still available. If a dependency suddenly becomes unavailable you would definitely like to know. But then again that could just be another workflow.

Jump in the discussion.

No email address required.

Yeah, what you need is a distinction between a "fast" run that happens on every commit and a "full" run that regenerates the cached images and happens on a dependency change or when preparing for a release.

Jump in the discussion.

No email address required.

There are but most devops and software engineers r-slurred and pull foreign dependencies constantly. You are r-slurred if you don't have a local cache.

Don't look at a website's JavaScript locations because many are pulling from elsewhere which means they'll break if those go down.

Jump in the discussion.

No email address required.

Why are the dependencies not locally hosted and version locked if you depend on it is the real question here

Jump in the discussion.

No email address required.

FFmpreg

https://i.rdrama.net/images/1688307987984256.webp

Jump in the discussion.

No email address required.

:#marseyxd: :#marseykingcrown:

Jump in the discussion.

No email address required.

>open sores

:#marseyxd:

Jump in the discussion.

No email address required.

Yeah the field sometimes attracts people so neurodivergent they can't even attempt to troubleshoot a problem with a social conponent. They just start screaming.

Jump in the discussion.

No email address required.

Link copied to clipboard
Action successful!
Error, please refresh the page and try again.