1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
|
#[cfg(feature = "backend-std")]
#[test]
fn test_cat_std() {
use std::io::{Read as _, Write as _};
let pty = pty_process::std::Pty::new().unwrap();
pty.resize(pty_process::Size::new(24, 80)).unwrap();
let mut child = pty_process::std::Command::new("cat").spawn(pty).unwrap();
child.pty().write_all(b"foo\n").unwrap();
// the pty will echo the written bytes back immediately, but the
// subprocess needs to generate its own output, which takes time, so we
// can't just read immediately (we may just get the echoed bytes). because
// the output generation is happening in the subprocess, we also don't
// have any way to know when (or if!) the subprocess will decide to send
// its output, so sleeping is the best we can do.
std::thread::sleep(std::time::Duration::from_secs(1));
let mut buf = [0u8; 1024];
let bytes = child.pty().read(&mut buf).unwrap();
assert_eq!(&buf[..bytes], b"foo\r\nfoo\r\n");
child.pty().write_all(&[4u8]).unwrap();
let status = child.wait().unwrap();
assert_eq!(status.code().unwrap(), 0);
}
#[cfg(feature = "backend-smol")]
#[test]
fn test_cat_smol() {
use smol::io::{AsyncReadExt as _, AsyncWriteExt as _};
let status = smol::block_on(async {
let pty = pty_process::smol::Pty::new().unwrap();
pty.resize(pty_process::Size::new(24, 80)).unwrap();
let mut child =
pty_process::smol::Command::new("cat").spawn(pty).unwrap();
child.pty().write_all(b"foo\n").await.unwrap();
// the pty will echo the written bytes back immediately, but the
// subprocess needs to generate its own output, which takes time, so
// we can't just read immediately (we may just get the echoed bytes).
// because the output generation is happening in the subprocess, we
// also don't have any way to know when (or if!) the subprocess will
// decide to send its output, so sleeping is the best we can do.
smol::Timer::after(std::time::Duration::from_secs(1)).await;
let mut buf = [0u8; 1024];
let bytes = child.pty().read(&mut buf).await.unwrap();
assert_eq!(&buf[..bytes], b"foo\r\nfoo\r\n");
child.pty().write_all(&[4u8]).await.unwrap();
child.status().await.unwrap()
});
assert_eq!(status.code().unwrap(), 0);
}
#[cfg(feature = "backend-async-std")]
#[test]
fn test_cat_async_std() {
use async_std::io::prelude::WriteExt as _;
use async_std::io::ReadExt as _;
let status = async_std::task::block_on(async {
let pty = pty_process::async_std::Pty::new().unwrap();
pty.resize(pty_process::Size::new(24, 80)).unwrap();
let mut child = pty_process::async_std::Command::new("cat")
.spawn(pty)
.unwrap();
child.pty().write_all(b"foo\n").await.unwrap();
// the pty will echo the written bytes back immediately, but the
// subprocess needs to generate its own output, which takes time, so
// we can't just read immediately (we may just get the echoed bytes).
// because the output generation is happening in the subprocess, we
// also don't have any way to know when (or if!) the subprocess will
// decide to send its output, so sleeping is the best we can do.
async_std::task::sleep(std::time::Duration::from_secs(1)).await;
let mut buf = [0u8; 1024];
let bytes = child.pty().read(&mut buf).await.unwrap();
assert_eq!(&buf[..bytes], b"foo\r\nfoo\r\n");
child.pty().write_all(&[4u8]).await.unwrap();
child.status().await.unwrap()
});
assert_eq!(status.code().unwrap(), 0);
}
#[cfg(feature = "backend-tokio")]
#[test]
fn test_cat_tokio() {
use tokio::io::{AsyncReadExt as _, AsyncWriteExt as _};
async fn async_test_cat_tokio() {
let pty = pty_process::tokio::Pty::new().unwrap();
pty.resize(pty_process::Size::new(24, 80)).unwrap();
let mut child =
pty_process::tokio::Command::new("cat").spawn(pty).unwrap();
child.pty_mut().write_all(b"foo\n").await.unwrap();
// the pty will echo the written bytes back immediately, but the
// subprocess needs to generate its own output, which takes time, so
// we can't just read immediately (we may just get the echoed bytes).
// because the output generation is happening in the subprocess, we
// also don't have any way to know when (or if!) the subprocess will
// decide to send its output, so sleeping is the best we can do.
tokio::time::sleep(std::time::Duration::from_secs(1)).await;
let mut buf = [0u8; 1024];
let bytes = child.pty_mut().read(&mut buf).await.unwrap();
assert_eq!(&buf[..bytes], b"foo\r\nfoo\r\n");
child.pty_mut().write_all(&[4u8]).await.unwrap();
let status = child.wait().await.unwrap();
assert_eq!(status.code().unwrap(), 0);
}
tokio::runtime::Runtime::new().unwrap().block_on(async {
async_test_cat_tokio().await;
});
}
|
