Love the function name. When asking for help it’s always appreciated to make life for your helpers as easy as possible. For instance by linking to the offending function directly (especially when the file is so large).
Love the function name. When asking for help it’s always appreciated to make life for your helpers as easy as possible. For instance by linking to the offending function directly (especially when the file is so large).
Could you provide a link to the documentation for the endpoint you want to access? I can’t find it. My guess is that you need to fetch a specific user via ${api}/user/124356
.
Docs here. My guess is wrong.
God, that documentation is annoying to read. I revise my revised opinion. Try providing a user ID or a username as query parameters in your API call.
const response = await fetch(`${api}/user?person_id=123456`, {
method: "GET",
headers: {
"Content-Type": "application/json",
"Authorization": `Bearer ${lemmyToken}`
}
});
Zangendeutsch ist zu hoch für mich.
If you’re using a descendant of Debian, you will find a line like this in your ~/.bashrc
file:
PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
The 32m
part controls the color of the username. (\u
). 1 is red, 2 is green (as seen in the user and host part, \u@\h
), 3 (as seen for the directory, \w
) is blue.
You can use this to distinguish different hosts by color.
Real coders program in assembly.
My bank (German, just like needanke’s probably is) requires that exact 2FA method once every 3 months or whenever you login via an unrecognized device. Also for every transaction you make and when you want to check bank statements more than 1 month in the past.
https://en.wikipedia.org/wiki/Transaction_authentication_number#ChipTAN_/_Sm@rt-TAN_/_CardTAN
Well, that happens when you don’t override the toString
method. Not worse than Java’s 0xf00cu
Naah, he’s spitting some fuel into the engine to win the race… or something.
Is this from the fireworks town Tom Scott talked about?
I didn’t know what XCode was, so I read the first three words of its Wikipedia article.
Xcode is Apple’s
And suddenly, all surprise vanished.
If the Mossad wants your data, they’re going to use a drone to replace your cellphone with a piece of uranium that’s shaped like a cellphone
That reads differently after 2024.
That’s the best thing I’ve read in a while, and I’m only on page 2!
Can you blame them? Last month my colleague (we’re both developers) pointed out how fucking deep we got into the woods of the “What if”s and “What should happen here”s of a feature that looked dead simple on its surface.
Yes, you can do crazy shit if you try hard enough, but every reasonable programmer would access foo->child->b
als foo->child->b
and not via that crazy LISPy expression.
By question was: Why would you have a pointer to a memory address that itself only holds a pointer somewhere else?
So far the only reasonable explanation is from @Victoria@lemmy.blahaj.zone:
- arrays of function pointers
- pass by reference of a pointer
linked lists, trees, objects with references to other objects
That’s not a pointer to another pointer, but a pointer to a data structure that happens to contain another pointer.
Why should the environment make a difference when it comes to receiving the SIGINT when the process gets killed?
Why do you even have pointers to pointers?
show you a GUI saying “you’re running low on memory, here are your running programs and how much they are using”
Good luck with this approach on a server.
If by ‘suspend’ you mean that the process will just halt, then: Which processes? All of them? Good luck displaying a message then. The last one that made a memory request? That might not be the true offender. The highest-consuming process? Same logic applies.
If by ‘suspend’ you mean moving the memory to disk, then a single misbehaving process, may end up eating all of memory and all remaining disk space.
I did try to catch all of these signals:
| "SIGABRT"
| "SIGALRM"
| "SIGBUS"
| "SIGCHLD"
| "SIGCONT"
| "SIGFPE"
| "SIGHUP"
| "SIGILL"
| "SIGINT"
| "SIGIO"
| "SIGIOT"
| "SIGKILL"
| "SIGPIPE"
| "SIGPOLL"
| "SIGPROF"
| "SIGPWR"
| "SIGQUIT"
| "SIGSEGV"
| "SIGSTKFLT"
| "SIGSTOP"
| "SIGSYS"
| "SIGTERM"
| "SIGTRAP"
| "SIGTSTP"
| "SIGTTIN"
| "SIGTTOU"
| "SIGUNUSED"
| "SIGURG"
| "SIGUSR1"
| "SIGUSR2"
| "SIGVTALRM"
| "SIGWINCH"
| "SIGXCPU"
| "SIGXFSZ"
| "SIGBREAK"
| "SIGLOST"
| "SIGINFO";
You need to provide the user ID (or username) of the account you want to fetch in the query parameters.