To be honest I don't understand how this works e.g. even with LineageOS' PrivacyGuard I still see some background processes in cache that had no permission to run on boot.
But it's absolutely necessary. I can't upgrade until I have that. I want full control of what runs on startup and what should be allowed to keep running on background (manually closed by me, I'm not asking for a skynet AI to guess).
Another one is blocking internet access but that will never happen because of their business model and ads. I guess I'll have to risk my personal data by using an open source firewall (not like I'm not going to review all the code) and unlocking bootloader/root.
Android is a disgrace because of these "small" things that they refuse to fix. But I'm glad it's slowly getting better.
This submission should be removed. Not only it wasn't read for public access https://github.com/php-plus/engine but they are merging with another preprocessor project.
This was after I reported that my 72 year old mother was asked to get out of the car by the driver after sitting in it, because he learned of the destination after starting the trip and did not want to take her there. Uber does not show the destination to the driver before starting the trip.
I was probably speaking to a bot, or nobody had the patience to fix the problem.
There was a good year or so period where I ran into 4 or 5 critical bugs that stopped me using the service entirely for days or weeks at a time. One of the dumbest was being unable to enter a credit card because the form required a field that wasn't being rendered. 6 months later I switch credit cards and again can't use the app for weeks because it wants a 5 digit postcode even after setting the country to 'Australia', but the server side check was still working and 86'd any combination of bs 5-digit code that was working.
Several times I've had something go wrong with the ordering system itself (on the UberEats side). Once an order was put through twice and two meals showed up on my doorstep. Another time I copped a cryptic error message followed by a Javascript crash and my card was charged but no order was logged upon refreshing the page (which indicates to me that something wasn't properly atomic and maybe some business logic was happening on the front end that shouldn't be? Presumably fixed now, I hope)
Even right now, as I type this, there's a bug on UberEats introduced in the last few days or weeks that's leaking variable names through to the front-end. I've got 'components.BadgeSoldOut.message' and 'components.CartItemCustomization.upTo' all over the place. I'm sure when that gets fixed another one will crop up next week.
Not the default hence not well tested. AND you still have a Docker daemon running. Furthermore, last time I checked, Docker does not support user namespacing in a released version yet.
I maintain the "duh fix your script dummy" is not the right attitude. The author clearly states it's used for a build farm. That is bound to fail ...
I read "Docker daemon was using 100% CPU" to be the recurring incident; not a given script. And when that happens, it ends up cascading and stuff get OOM-killed before you know it.
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/m...