I hate a lot of the things that reddit has been doing but I still think not all of them are on purpose. I ran into this issue myself before it was widely discussed and my first thought was that it had simply failed to delete some comments or deleted only from some cache.
So far every exampe I’ve seen of this can still be explained by bad engineering and I see no reason to think it is “undeleting” stuff by design, since it seems to happen to very random content that has no general value (like restoring 20 random comments out of 900 that were deleted).
So what do the permissions look like on that file? Does it work if you enter the container as that user and try it yourself? If you have selinux enforcing, have you checked its audit log?
It has same user:group as files that could be copied before I started having bugs, And that’s the user: group I need. I have this problem with multiple files, downloaded at different times, trying to copy them on different locations on my mount. So my guess as a beginner is that the problem is at the destination. I don’t have selinux.
I never really understood the point of Lambda calculus. Why have an anonymous function? I thought it was good practice to meticulously segment code into functions and subroutines and call them as needed, rather than have some psuedo-function embedded somewhere.
I think you’re confusing lambdas with lambda calculus. Lambda calculus is more than just anonymous functions.
To put it extremely simply, let’s just say functional programming (the implementation of lambda calculus) is code with functions as data and without shared mutable state (or side effects).
The first one increases expressiveness tremendously, the second one increases safety and optimization. Of course, you don’t need to write anonymous functions in a functional language if you don’t want to.
As for why those “pseudo-functions” are useful, you’re probably thinking of closures, which capture state from the context they are defined in. That is pretty useful. But it’s not the whole reason lambda calculus exists.
See the other comments about lambdas vs. lambda calculus, but lambdas are supposed to be for incredibly simple tasks that don’t need a full function definition, things that could be done in a line or two, like simple comparisons or calling another function. This is most useful for abstractions like list filtering, mapping, folding/reducing, etc. where you usually don’t need a very advanced function call.
I was always taught in classes that if your lambda needs more than just the return statement, it should probably be its own function.
The ending / wasn’t a problem a few weeks back, but I tried to remove it anyway with no luck. The share is mounted and I can browse it from source machine and container.
I know it’s linux and you never reboot it and yadda yadda, but have you tried rebooting both machines?
For what it’s worth, that’s my fstab entry (it’s mounted with a normal user, which is the same which the containers use). I seem to remember I had to change ownership of the /mnt/nasdownload folder (before the mount) to the user used to mount it.
I did games technology at university. We had a module that was just playing board games and eventually making one. Also did an unreal engine module that ended with making a game and a cinematic.
What do the permissions look like on newly created files and directories from the qBittorrent container? Run ls -al and check to see, this sounds like a simple fix.
You can try adding file_mode and dir_mode to your fstab mount as well.
I know you marked this as SOLVED, however I just noticed (dunno how I missed it before) that your umask is 022 for qBittorrent but it is 002 for Radar. Even though you have the same UID/GID on both systems I’d still recommend setting 002 umask in the qBittorrent compose file
Mine are staying delete now after initially a few popping back up. What’s more concerning is that I requested my data a few weeks after I deleted my content. I was fully expecting to get empty files but nope ALL of my content. Dating back 10 years is still there! It’s not on my Reddit profile but they clearly kept it somewhere and can recall it whenever they want to. They do not delete the data.
Mine are staying delete now after initially a few popping back up.
Something like this happened for me too, but I believe these were comments that I didn’t yet delete, they just weren’t visible anymore. The older ones started to pop up once there was new space for them after deleting the newer ones. (On your profile not all comments you ever made are visible, only the newest/top/most-controversial ones, depending on what you sort for).
For example in my profile my very first post was visible, but none of the comments I made there. Before deleting the posts I went through each one and deleted my comments that way. There probably still are many comments from me laying around undeleted…
Here’s one, set an alarm to go off in the middle of a date, pretend it’s a phone call and if the date is going badly “take the call” and say you’ve got to leave. I could say my roommate has forgot their keys and accidentally locked themselves out for example.
I’m glad you like it! I like how it’s made up of three common and easily-identifiable components: it uses the same root as verify meaning true, the same root as similar meaning “like”, with tude being a common suffix like -ness. Basically “true-likeness”.
Yes, this is almost certainly a technical issue. The way reddit caches things probably isn’t the standard way you’re thinking of, like a short-term cache that expires and refreshes itself. There are multiple layers of “cached” listings and items for almost everything, and a lot of these caches are actually data that’s stored permanently and kept up to date individually.
There are also multiple other places and ways that comments are cached—comment trees are cached (order and nesting of comments on a comments page, for all the different sorting methods), rendered HTML versions of comments are cached, API data is probably cached, and so on.
All of these issues are probably just some combination of all of your posts being difficult to find and access due to the listing limits or certain cached representations of posts not being cleared or updated properly.
This isn’t really a good excuse though. Right to be forgotten doesn’t me the right to be forgotten except in a cache loop. Sometimes this stuff is time sensitive.
heck I can't even get my data to begin with. When it did not show they sent me bakc an email saying it would take up to 30 days. today I emailed back that it has been well over 30 days.
I would try this and say “I’m about to die” by accident and then spend five minutes explaining the mistake and five days thinking about it. No thanks,.
lemmy.ml
Oldest