nushell/crates/nu-command/tests/commands/network/port.rs

50 lines
1.4 KiB
Rust
Raw Normal View History

use nu_test_support::{nu, pipeline};
use std::net::TcpListener;
use std::sync::mpsc;
#[test]
fn port_with_invalid_range() {
let actual = nu!("port 4000 3999");
assert!(actual.err.contains("Invalid range"))
}
#[test]
fn port_with_already_usage() {
let retry_times = 10;
for _ in 0..retry_times {
let (tx, rx) = mpsc::sync_channel(0);
// let system pick a free port for us.
let free_port = {
let listener = TcpListener::bind("127.0.0.1:0").expect("failed to pick a port");
listener.local_addr().unwrap().port()
};
let handler = std::thread::spawn(move || {
let _listener = TcpListener::bind(format!("127.0.0.1:{free_port}"));
let _ = rx.recv();
});
let actual = nu!(pipeline(&format!("port {free_port} {free_port}")));
let _ = tx.send(true);
// make sure that the thread is closed and we release the port.
handler.join().unwrap();
// check for error kind str.
Fix capacity overflow caused by large range of ports (#11210) <!-- if this PR closes one or more issues, you can automatically link the PR with them by using one of the [*linking keywords*](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword), e.g. - this PR should close #xxxx - fixes #xxxx you can also mention related issues, PRs or discussions! --> # Description <!-- Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes. Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience. --> Try to fix capacity overflow caused by large range of ports. ``` $ port 1024 999999999999999999 12/02/23 20:03:14 PM thread 'main' panicked at 'capacity overflow', library/alloc/src/raw_vec.rs:524:5 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ``` # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting <!-- Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass (on Windows make sure to [enable developer mode](https://learn.microsoft.com/en-us/windows/apps/get-started/developer-mode-features-and-debugging)) - `cargo run -- -c "use std testing; testing run-tests --path crates/nu-std"` to run the tests for the standard library > **Note** > from `nushell` you can also use the `toolkit` as follows > ```bash > use toolkit.nu # or use an `env_change` hook to activate it automatically > toolkit check pr > ``` --> # After Submitting <!-- If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date. -->
2023-12-02 16:17:14 +01:00
if actual
.err
.contains("Every port has been tried, but no valid one was found")
{
return;
}
}
panic!("already check port report AddrInUse for several times, but still failed.");
}
#[test]
fn port_from_system_given() {
let actual = nu!("port");
// check that we can get an integer port from system.
assert!(actual.out.parse::<u16>().unwrap() > 0)
}