I fucking hate online editors for recruitment challanges!!

2 fucking hours I spend on developing a architectural problem but nothing came up on stdout!!

Why? Because the runtime added some functions to HELP me with stdin and stdouts. They were being called by the driverscripts and reading everything up beforehand!!
I was reading empty stdin from there!!!

Worst part is the code was kept at the last of the editor space hidden as a gray shade with no indication that there was code minimized.
After fucking my brain so long, realised the issue when I had 2 mins left!
Ended up with a compilation error while hurrying to change!!
I hate the hackerrank platform!!🤬🤬🤬😡🤯

Hexdump oneliner

php -r 'for(;$r=fread(STDIN,16);)printf("%08x %s $r\n",$i++*16,join(unpack("h*",$r)));'

Unicode's biggest problem is that it isn't a streamable format. Given a section of a Unicode string, it's impossible to assert that the next character won't be an accent or zwj or other modifier. This means that it's impossible to convert stdin into an iterator over canonicalized Unicode graphemes.

Does somebody know how to send data to the PHP CGI executable directly and how to receive it (stdin/stdout)?
Or point me to a useful resource?
In a side project (just for fun) I try to implement the interface on NodeJS so I could process PHP through ExpressJS (long story).
I've been able to send and receive stuff, but the PHP CGI always tells me that I am "not allowed" to use this interface...
Docs/mailinglists seem reeeally old and don't want to go through the Apache source code 😅
Or does Node not have enough privileges for communicatig with PHP CGI exe?

"hey, write us a simple interface for this shell script.."
script:
- input must be a file, does not accept loading through stdin/redirect
- accepts relative path input from one specific directory only
- fails if provided absolute path
- even though it fails, it still returns return code 0

and every time we've tried to open up a topic of programming practices we got slammed with "we're ops. you should be glad they're doing at least some scripting"

WTF, Rust. You are so fucking hard to write, and TBH, your docs are not understandable. Please writte your docs to be understandable, and make it fun to read, like golang does.

WTF, Rust. I am now looking, for 5 hours straight, for a solution for reading stdin into a variable. Nothing. 6 fucking solutions for 6 different rust versions of which not one works. Nothing is readable. Explain the philosophy of you language! What the hell is this?! Is your language based on the C family? On which is it based?! fucking idiots

>finally gets around to installing vsftpd on home server RPi
>doesn't work
hmm.mp2
>configurating
>confusing as fuck template documentation
>man page isn't much better
>gets it working
>goes to log in
User: pi
Password: a
(What? It's a home file/command server isolated from the Internet. Sue me.)
nope.avi
>why
>tries again
nope.svg
>FUCK
>sees small raw-command log in bottom-right of phone FTP client
hmm.flac
>tries again, watches log
PASS *****
>the fuck
>goes to change user pass over SSH
# passwd
"Current password?"
about half a second later
"passwd: auth token manipulation denied"
>the delay tho
>WAIT A SECOND
one time i got past some parental software bullshit on a tablet by abusing the delay between opening a banned app and the redirect to the normal software at like age 7. (Doing so let me enable remote wipe through Google. bye bye software!)
>*inner 7 year old has autistic screech*
# nano temp
a
abcdefghi
abcdefghi
^O Y ^X
# passwd < temp
>fucking works
>logs in to FTP server successfully
>does the one file download that was needed

why and how did that fucking work

Dumb question time!
I'm writing a bash script that outputs some progress info to stdout (stuff like "Doing this... ok", "Doing that... ok") before outputing a list of names (to stdout too).

I'd like to be able to pipe this list of names to a second script for processing, by doing a simple :
~$ script1 | script2

Unfortunately, as you may have guessed, the progress info is piped as well, and is not displayed on the screen.
Is it considered a bad practice to redirect that progress info to stderr so it is not sent into the pipe ?

Is there any "design pattern" for this kind of usecase, where you want to be able to choose what to display and what to pipe to a program that accepts input from stdin ?

So I have somehow created schrödinger's cat in my program. If you observe what is happening, it works. But if you stop observing it, it starts corrupting.

If I put any print statement in it, it works. But if I have no print statements at all, it produces corrupted data. Doesn't matter what or when I'm printing.

I'm guessing its there's some fuckery going on with stdin/stdout and buffers. Even though the data coming to and from stdin/stdout should not affect the output.

I don't understand how I/O streams work. I mean as a userspace developer i saw the stdin/stdout streams as magical objects that i could read or output infinetely in a continuous way, without caring how much data i write or read (ok, not entirely true because overflows)... But now i'm making an os kernel and i really don't know how i'll implement them..... :(

Okay I got a genius/exceptionally stupid idea.
Some of you may know Xi. If not, it's an, in development, text editor backend, written in Rust.
It does all the heavy lifting and communicates changes with the Frontend over an rpc-api, typically on stdin/stdout.

Now, why don't we do this, but for other kinds of applications, that have been reinvented a million times, because a feature is missing or the ui has been shit.
Cross-Platform backends for file-managers, web browsers, password managers, media players,...

So i'm trying to upload a file to an SSH server using node. First I try the obvious putFile method provided by the obvious node-ssh package. On any other server this would work fine but this server doesn't have sftp installed so that doesn't work.

OK, so next I learn how scp works (it runs the command "scp -t" on the remote server, and sends to stdin a command like "C0666 1234 file.txt" and then sends the contents of the file) and I write some javascript code to do this. It's pretty finicky, the first few tries I forget to close the stream right or detect the program finishing. I add some logging and that helps me figure out what the problem is, and finally I get it to not output any errors.

So I log into the server and check and the file isn't there. I try again several times, file still isn't there. I try running scp -t manually on the server, typing in exactly what my program is sending, and it works. This goes on for a while until I realize that I've been sending a file to one server and logging into a different server to check if the file was sent. grrr

>>>generateRant()
Traceback (most recent call last):
File "<stdin>", line 1, in <module> NameError: name 'generateRant' is not defined
>>>

My search for a solution to mintty terminal compatibility seems to be coming to a close (thank god). I know now that having compatibility with cygwin doesn't make sense as far as I can see. Because it's about mintty not cygwin.

But now I have to figure out how to interface with mintty for setting the non-canonical flag and switching stdin to non blocking mode

Oh boy... It's getting closer!

To you CPP-devs,
I want to write a small ask-password tool, like systemd-ask-password, but tty-only and non-systemd.
I use termios to switch the terminal into noncanonical mode and disable echo of stdin.
Now I want to read chars from cin and append them to a string, until I read an endl or an error occurs.
In C, I could use an input-loop with getchar, but how could I do this the CPP-way, since cin.get() is nonblocking?