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
Search - "package cache"
-
!rant
Me: sudo apt-get update
PC: Noope. There is a problem with a package.
Me: Ugh... ok I'll fix it. *20 minutes later* Fixed. Sudo apt-get update
PC: Noope, the package cache file is corrupted.
Me: GO FUCK YOURSELF LINUX OMFG.
Oh, I fixed it.
I LOVE YOU LINUX.11 -
Vodafone India is so shit omfg
Run npm install, ERROR json parse error due to ssl exception
Run pip install, again ssl exception
Run gradle build, again ssl exception!!!
Now everytime i gotta make a new project or install a dependency in anything, i have to pray to the blood god that cache contains a valid/uncorrupted package dependency or else ill have to nuke cache and borrow internet from someone else.
Once i port it to some other operator, i am gonna incinerate this mf sim.12 -
Spent about 3 hours yesterday trying to update ArchLinux (I wanted to update a certain package). Something to do with slow/failed mirrors timing out. Updated the mirrors in a not ideal way (https://gist.github.com/vodik/...). Then got package conflicts, of course. Then something about package cache. Then used `reflector` to update the mirrors. Then got another problem with the PGP keys. And finally, the update completed and now I can open vlc to watch the office...5
-
Dear xcode,
you fckn bitch did it again. I really wanted to do some iOS development, I swear. But you are like an abusive relationship, I have this weird habit of coming back to you even though I am getting fucked in the ass in parallel.
I love Swift but I despise you xcode. Randomly fucking up my workflow, and then it is clean build folder, reset package cache, restart xcode. Again and again and again you fuck things up out of nowhere. And from time to time, you just have to install the newest version of xcode because its so fucked up its easier to download this MASSIVE asshole than to even try to fix anything if you know its just xcode again.
Yeah, fuck extensions and formatting. Just fuck humanly tolerable build time. Fuck you xcode.
I am not an experienced dev with iOS nor am I a common Mac user but this is just wrong. I feel violated and the joy of development sucked out of my soul while I try to navigate through the overloaded interface.
I am not even going into details about iOS development, its just that xcode is the gatekeeper to get me the fuck out of this miserable place that is native iOS development.
Arrivederci, suckers.4 -
Do anyone of you use a npm registry server like verdaccio for caching of packages from npmjs.org?
Today I tried verdaccio within a local docker container.
I successfully connected via npm --registry <registry-url> install
There where no errors, but verdaccio kept delivering packages with 200.
Shouldn't it be 304 since the packages already exist in the storage folder of verdacio?14 -
TL;DR When talking about caching, is it even worth considering try and br as memory efficient as possible?
Context:
I recently chatted with a developer who wanted to improve a frameworks memory usage. It's a framework creating discord bots, providing hooks to events such as message creation. He compared it too 2 other frameworks, where is ranked last with 240mb memory usage for a bot with around 10.5k users iirc. The best framework memory wise used around 120mb, all running on the same amount of users.
So he set out to reduce the memory consumption of that framework. He alone reduced the memory usage by quite some bit. Then he wanted to try out ttl for the cache or rather cache with expirations times, adding no overhead, besides checking every interval of there are so few records that should be deleted. (Somebody in the chat called that sort of cache a meme. Would be happy , if you coukd also explain why that is so😅).
Afterwards the memory usage droped down to 100mb after a Around 3-5 minutes.
The maintainer of the package won't merge his changes, because sone of them really introduce some stuff that might be troublesome later on, such as modifying the default argument for processes, something along these lines. Haven't looked at these changes.
So I'm asking myself whether it's worth saving that much memory. Because at the end of the day, it's cache. Imo cache can be as big as it wants to be, but should stay within borders and of course return memory of needed. Otherwise there should be no problem.
But maybe I just need other people point of view to consider. The other devs reasoning was simple because "it shouldn't consume that much memory", which doesn't really help, so I'm seeking you guys out😁 -
Seriously !!!! I did not agreed for any data collection.
Welcome to .NET Core!
---------------------
Learn more about .NET Core @ https://aka.ms/dotnet-docs. Use dotnet --help to see available commands or go to https://aka.ms/dotnet-cli-docs.
Telemetry
--------------
The .NET Core tools collect usage data in order to improve your experience. The data is anonymous and does not include commandline arguments. The data is collected by Microsoft and shared with the community.
You can opt out of telemetry by setting a DOTNET_CLI_TELEMETRY_OPTOUT environment variable to 1 using your favorite shell.
You can read more about .NET Core tools telemetry @ https://aka.ms/dotnet-cli-telemetry.
Configuring...
-------------------
A command is running to initially populate your local package cache, to improve restore speed and enable offline access. This command will take up to a minute to complete and will only happen once.
Decompressing 100% 3803 ms
Expanding 100% 17279 ms