Exec calls
See original GitHub issueWhenever I try to open an exec call I get:
{
"kind":"Status",
"apiVersion":"v1",
"metadata":{},
"status":"Failure",
"message":"Upgrade request required",
"reason":"BadRequest","code":400
}
Which is related with the fact that requests
is not SPDY compatible. Are you going to support this kind of requests in the near future?
Issue Analytics
- State:
- Created 7 years ago
- Comments:72 (28 by maintainers)
Top Results From Across the Web
exec (system call) - Wikipedia
In computing, exec is a functionality of an operating system that runs an executable file in the context of an already existing process,...
Read more >Linux Exec System Call
The exec system call is used to execute a file which is residing in an active process. When exec is called the previous...
Read more >Difference between fork() and exec() - GeeksforGeeks
1. It is a system call in the C programming language, It is a system call of operating system ; 2. It is...
Read more >The exec family of system calls :: Operating systems 2018
The exec family of system calls replaces the program executed by a process. When a process calls exec, all code (text) and data...
Read more >exec(3) - Linux manual page - man7.org
The exec() family of functions replaces the current process image with ... variable environ in the calling process. p - execlp(), execvp(), ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Well I don’t mind creating a new issue for post work. The access to stderr and stdout separately was one of my comments on original PR too. The majority part of the task is done so I will leave it to you and @dims if you want to close this and create a new issue, but I don’t think our work on exec calls is done until we solve those issues. I would like to have a similar approach to Watch here. Will try something today.
assert_hostname is not in config package, I understand the confusion though, we should clear that up.
on a side note, you don’t need to pass kube config location if it is in the default location (as I see it is for your case).