2024-04-23 13:37:50 +02:00
|
|
|
use std::{fs::File, path::PathBuf};
|
2024-04-21 14:36:26 +02:00
|
|
|
|
2024-04-25 00:40:39 +02:00
|
|
|
use nu_protocol::{PluginRegistryFile, PluginRegistryItem, PluginRegistryItemData};
|
2024-04-21 14:36:26 +02:00
|
|
|
use nu_test_support::{fs::Stub, nu, nu_with_plugins, playground::Playground};
|
|
|
|
|
|
|
|
fn example_plugin_path() -> PathBuf {
|
|
|
|
nu_test_support::commands::ensure_plugins_built();
|
|
|
|
|
|
|
|
let bins_path = nu_test_support::fs::binaries();
|
|
|
|
nu_path::canonicalize_with(
|
|
|
|
if cfg!(windows) {
|
|
|
|
"nu_plugin_example.exe"
|
|
|
|
} else {
|
|
|
|
"nu_plugin_example"
|
|
|
|
},
|
|
|
|
bins_path,
|
|
|
|
)
|
|
|
|
.expect("nu_plugin_example not found")
|
|
|
|
}
|
|
|
|
|
2024-06-21 13:27:09 +02:00
|
|
|
fn valid_plugin_item_data() -> PluginRegistryItemData {
|
|
|
|
PluginRegistryItemData::Valid {
|
|
|
|
metadata: Default::default(),
|
|
|
|
commands: vec![],
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2024-04-21 14:36:26 +02:00
|
|
|
#[test]
|
|
|
|
fn plugin_add_then_restart_nu() {
|
|
|
|
let result = nu_with_plugins!(
|
|
|
|
cwd: ".",
|
|
|
|
plugins: [],
|
|
|
|
&format!("
|
|
|
|
plugin add '{}'
|
|
|
|
(
|
|
|
|
^$nu.current-exe
|
|
|
|
--config $nu.config-path
|
|
|
|
--env-config $nu.env-path
|
|
|
|
--plugin-config $nu.plugin-path
|
Make `plugin list` read state from plugin registry file as well (#14085)
# Description
[Context on
Discord](https://discord.com/channels/601130461678272522/855947301380947968/1292279795035668583)
**This is a breaking change, due to the removal of `is_running`.**
Some users find the `plugin list` command confusing, because it doesn't
show anything different after running `plugin add` or `plugin rm`. This
modifies the `plugin list` command to also look at the plugin registry
file to give some idea of how the plugins in engine state differ from
those in the plugin registry file.
The following values of `status` are now produced instead of
`is_running`:
- `added`: The plugin is present in the plugin registry file, but not in
the engine.
- `loaded`: The plugin is present both in the plugin registry file and
in the engine, but is not running.
- `running`: The plugin is currently running, and the `pid` column
should contain its process ID.
- `modified`: The plugin state present in the plugin registry file is
different from the state in the engine.
- `removed`: The plugin is still loaded in the engine, but is not
present in the plugin registry file.
- `invalid`: The data in the plugin registry file couldn't be
deserialized, and the plugin most likely needs to be added again.
Example (`commands` omitted):
```
╭──────┬─────────────────────┬────────────┬───────────┬──────────┬─────────────────────────────────────────────────────┬─────────╮
│ # │ name │ version │ status │ pid │ filename │ shell │
├──────┼─────────────────────┼────────────┼───────────┼──────────┼─────────────────────────────────────────────────────┼─────────┤
│ 0 │ custom_values │ 0.1.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_custom_values │ │
│ 1 │ dbus │ 0.11.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_dbus │ │
│ 2 │ example │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_example │ │
│ 3 │ explore_ir │ 0.3.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_explore_ir │ │
│ 4 │ formats │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_formats │ │
│ 5 │ gstat │ 0.98.1 │ running │ 236662 │ /home/devyn/.cargo/bin/nu_plugin_gstat │ │
│ 6 │ inc │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_inc │ │
│ 7 │ polars │ 0.98.1 │ added │ │ /home/devyn/.cargo/bin/nu_plugin_polars │ │
│ 8 │ query │ 0.98.1 │ removed │ │ /home/devyn/.cargo/bin/nu_plugin_query │ │
│ 9 │ stress_internals │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_stress_internals │ │
╰──────┴─────────────────────┴────────────┴───────────┴──────────┴─────────────────────────────────────────────────────┴─────────╯
```
# User-Facing Changes
To `plugin list`:
* **Breaking:** The `is_running` column is removed and replaced with
`status`. Use `status == running` to filter equivalently.
* The `--plugin-config` from other plugin management commands is now
supported.
* Added an `--engine` flag which behaves more or less like before, and
doesn't load the plugin registry file at all.
* Added a `--registry` flag which only checks the plugin registry file.
All plugins appear as `added` since there is no state to compare with.
Because the default is to check both, the `plugin list` command might be
a little bit slower. If you don't need to check the plugin registry
file, the `--engine` flag does not load the plugin registry file at all,
so it should be just as fast as before.
# Tests + Formatting
Added tests for `added` and `removed` statuses. `modified` and `invalid`
are a bit more tricky so I didn't try.
# After Submitting
- [ ] update documentation that references the `plugin list` command
- [ ] release notes
2024-10-17 04:24:45 +02:00
|
|
|
--commands 'plugin list --engine | get name | to json --raw'
|
2024-04-21 14:36:26 +02:00
|
|
|
)
|
|
|
|
", example_plugin_path().display())
|
|
|
|
);
|
|
|
|
assert!(result.status.success());
|
|
|
|
assert_eq!(r#"["example"]"#, result.out);
|
|
|
|
}
|
|
|
|
|
2024-04-24 13:28:45 +02:00
|
|
|
#[test]
|
|
|
|
fn plugin_add_in_nu_plugin_dirs_const() {
|
|
|
|
let example_plugin_path = example_plugin_path();
|
|
|
|
|
|
|
|
let dirname = example_plugin_path.parent().expect("no parent");
|
|
|
|
let filename = example_plugin_path
|
|
|
|
.file_name()
|
|
|
|
.expect("no file_name")
|
|
|
|
.to_str()
|
|
|
|
.expect("not utf-8");
|
|
|
|
|
|
|
|
let result = nu_with_plugins!(
|
|
|
|
cwd: ".",
|
|
|
|
plugins: [],
|
|
|
|
&format!(
|
|
|
|
r#"
|
|
|
|
$env.NU_PLUGIN_DIRS = null
|
|
|
|
const NU_PLUGIN_DIRS = ['{0}']
|
|
|
|
plugin add '{1}'
|
|
|
|
(
|
|
|
|
^$nu.current-exe
|
|
|
|
--config $nu.config-path
|
|
|
|
--env-config $nu.env-path
|
|
|
|
--plugin-config $nu.plugin-path
|
Make `plugin list` read state from plugin registry file as well (#14085)
# Description
[Context on
Discord](https://discord.com/channels/601130461678272522/855947301380947968/1292279795035668583)
**This is a breaking change, due to the removal of `is_running`.**
Some users find the `plugin list` command confusing, because it doesn't
show anything different after running `plugin add` or `plugin rm`. This
modifies the `plugin list` command to also look at the plugin registry
file to give some idea of how the plugins in engine state differ from
those in the plugin registry file.
The following values of `status` are now produced instead of
`is_running`:
- `added`: The plugin is present in the plugin registry file, but not in
the engine.
- `loaded`: The plugin is present both in the plugin registry file and
in the engine, but is not running.
- `running`: The plugin is currently running, and the `pid` column
should contain its process ID.
- `modified`: The plugin state present in the plugin registry file is
different from the state in the engine.
- `removed`: The plugin is still loaded in the engine, but is not
present in the plugin registry file.
- `invalid`: The data in the plugin registry file couldn't be
deserialized, and the plugin most likely needs to be added again.
Example (`commands` omitted):
```
╭──────┬─────────────────────┬────────────┬───────────┬──────────┬─────────────────────────────────────────────────────┬─────────╮
│ # │ name │ version │ status │ pid │ filename │ shell │
├──────┼─────────────────────┼────────────┼───────────┼──────────┼─────────────────────────────────────────────────────┼─────────┤
│ 0 │ custom_values │ 0.1.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_custom_values │ │
│ 1 │ dbus │ 0.11.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_dbus │ │
│ 2 │ example │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_example │ │
│ 3 │ explore_ir │ 0.3.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_explore_ir │ │
│ 4 │ formats │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_formats │ │
│ 5 │ gstat │ 0.98.1 │ running │ 236662 │ /home/devyn/.cargo/bin/nu_plugin_gstat │ │
│ 6 │ inc │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_inc │ │
│ 7 │ polars │ 0.98.1 │ added │ │ /home/devyn/.cargo/bin/nu_plugin_polars │ │
│ 8 │ query │ 0.98.1 │ removed │ │ /home/devyn/.cargo/bin/nu_plugin_query │ │
│ 9 │ stress_internals │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_stress_internals │ │
╰──────┴─────────────────────┴────────────┴───────────┴──────────┴─────────────────────────────────────────────────────┴─────────╯
```
# User-Facing Changes
To `plugin list`:
* **Breaking:** The `is_running` column is removed and replaced with
`status`. Use `status == running` to filter equivalently.
* The `--plugin-config` from other plugin management commands is now
supported.
* Added an `--engine` flag which behaves more or less like before, and
doesn't load the plugin registry file at all.
* Added a `--registry` flag which only checks the plugin registry file.
All plugins appear as `added` since there is no state to compare with.
Because the default is to check both, the `plugin list` command might be
a little bit slower. If you don't need to check the plugin registry
file, the `--engine` flag does not load the plugin registry file at all,
so it should be just as fast as before.
# Tests + Formatting
Added tests for `added` and `removed` statuses. `modified` and `invalid`
are a bit more tricky so I didn't try.
# After Submitting
- [ ] update documentation that references the `plugin list` command
- [ ] release notes
2024-10-17 04:24:45 +02:00
|
|
|
--commands 'plugin list --engine | get name | to json --raw'
|
2024-04-24 13:28:45 +02:00
|
|
|
)
|
|
|
|
"#,
|
|
|
|
dirname.display(),
|
|
|
|
filename
|
|
|
|
)
|
|
|
|
);
|
|
|
|
assert!(result.status.success());
|
|
|
|
assert_eq!(r#"["example"]"#, result.out);
|
|
|
|
}
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
fn plugin_add_in_nu_plugin_dirs_env() {
|
|
|
|
let example_plugin_path = example_plugin_path();
|
|
|
|
|
|
|
|
let dirname = example_plugin_path.parent().expect("no parent");
|
|
|
|
let filename = example_plugin_path
|
|
|
|
.file_name()
|
|
|
|
.expect("no file_name")
|
|
|
|
.to_str()
|
|
|
|
.expect("not utf-8");
|
|
|
|
|
|
|
|
let result = nu_with_plugins!(
|
|
|
|
cwd: ".",
|
|
|
|
plugins: [],
|
|
|
|
&format!(
|
|
|
|
r#"
|
|
|
|
$env.NU_PLUGIN_DIRS = ['{0}']
|
|
|
|
plugin add '{1}'
|
|
|
|
(
|
|
|
|
^$nu.current-exe
|
|
|
|
--config $nu.config-path
|
|
|
|
--env-config $nu.env-path
|
|
|
|
--plugin-config $nu.plugin-path
|
Make `plugin list` read state from plugin registry file as well (#14085)
# Description
[Context on
Discord](https://discord.com/channels/601130461678272522/855947301380947968/1292279795035668583)
**This is a breaking change, due to the removal of `is_running`.**
Some users find the `plugin list` command confusing, because it doesn't
show anything different after running `plugin add` or `plugin rm`. This
modifies the `plugin list` command to also look at the plugin registry
file to give some idea of how the plugins in engine state differ from
those in the plugin registry file.
The following values of `status` are now produced instead of
`is_running`:
- `added`: The plugin is present in the plugin registry file, but not in
the engine.
- `loaded`: The plugin is present both in the plugin registry file and
in the engine, but is not running.
- `running`: The plugin is currently running, and the `pid` column
should contain its process ID.
- `modified`: The plugin state present in the plugin registry file is
different from the state in the engine.
- `removed`: The plugin is still loaded in the engine, but is not
present in the plugin registry file.
- `invalid`: The data in the plugin registry file couldn't be
deserialized, and the plugin most likely needs to be added again.
Example (`commands` omitted):
```
╭──────┬─────────────────────┬────────────┬───────────┬──────────┬─────────────────────────────────────────────────────┬─────────╮
│ # │ name │ version │ status │ pid │ filename │ shell │
├──────┼─────────────────────┼────────────┼───────────┼──────────┼─────────────────────────────────────────────────────┼─────────┤
│ 0 │ custom_values │ 0.1.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_custom_values │ │
│ 1 │ dbus │ 0.11.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_dbus │ │
│ 2 │ example │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_example │ │
│ 3 │ explore_ir │ 0.3.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_explore_ir │ │
│ 4 │ formats │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_formats │ │
│ 5 │ gstat │ 0.98.1 │ running │ 236662 │ /home/devyn/.cargo/bin/nu_plugin_gstat │ │
│ 6 │ inc │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_inc │ │
│ 7 │ polars │ 0.98.1 │ added │ │ /home/devyn/.cargo/bin/nu_plugin_polars │ │
│ 8 │ query │ 0.98.1 │ removed │ │ /home/devyn/.cargo/bin/nu_plugin_query │ │
│ 9 │ stress_internals │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_stress_internals │ │
╰──────┴─────────────────────┴────────────┴───────────┴──────────┴─────────────────────────────────────────────────────┴─────────╯
```
# User-Facing Changes
To `plugin list`:
* **Breaking:** The `is_running` column is removed and replaced with
`status`. Use `status == running` to filter equivalently.
* The `--plugin-config` from other plugin management commands is now
supported.
* Added an `--engine` flag which behaves more or less like before, and
doesn't load the plugin registry file at all.
* Added a `--registry` flag which only checks the plugin registry file.
All plugins appear as `added` since there is no state to compare with.
Because the default is to check both, the `plugin list` command might be
a little bit slower. If you don't need to check the plugin registry
file, the `--engine` flag does not load the plugin registry file at all,
so it should be just as fast as before.
# Tests + Formatting
Added tests for `added` and `removed` statuses. `modified` and `invalid`
are a bit more tricky so I didn't try.
# After Submitting
- [ ] update documentation that references the `plugin list` command
- [ ] release notes
2024-10-17 04:24:45 +02:00
|
|
|
--commands 'plugin list --engine | get name | to json --raw'
|
2024-04-24 13:28:45 +02:00
|
|
|
)
|
|
|
|
"#,
|
|
|
|
dirname.display(),
|
|
|
|
filename
|
|
|
|
)
|
|
|
|
);
|
|
|
|
assert!(result.status.success());
|
|
|
|
assert_eq!(r#"["example"]"#, result.out);
|
|
|
|
}
|
|
|
|
|
2024-04-21 14:36:26 +02:00
|
|
|
#[test]
|
|
|
|
fn plugin_add_to_custom_path() {
|
|
|
|
let example_plugin_path = example_plugin_path();
|
|
|
|
Playground::setup("plugin add to custom path", |dirs, _playground| {
|
|
|
|
let result = nu!(
|
|
|
|
cwd: dirs.test(),
|
|
|
|
&format!("
|
|
|
|
plugin add --plugin-config test-plugin-file.msgpackz '{}'
|
|
|
|
", example_plugin_path.display())
|
|
|
|
);
|
|
|
|
|
|
|
|
assert!(result.status.success());
|
|
|
|
|
2024-04-25 00:40:39 +02:00
|
|
|
let contents = PluginRegistryFile::read_from(
|
2024-04-21 14:36:26 +02:00
|
|
|
File::open(dirs.test().join("test-plugin-file.msgpackz"))
|
|
|
|
.expect("failed to open plugin file"),
|
|
|
|
None,
|
|
|
|
)
|
|
|
|
.expect("failed to read plugin file");
|
|
|
|
|
|
|
|
assert_eq!(1, contents.plugins.len());
|
|
|
|
assert_eq!("example", contents.plugins[0].name);
|
|
|
|
})
|
|
|
|
}
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
fn plugin_rm_then_restart_nu() {
|
2024-04-23 13:37:50 +02:00
|
|
|
let example_plugin_path = example_plugin_path();
|
|
|
|
Playground::setup("plugin rm from custom path", |dirs, playground| {
|
2024-05-04 02:53:15 +02:00
|
|
|
playground.with_files(&[
|
2024-04-23 13:37:50 +02:00
|
|
|
Stub::FileWithContent("config.nu", ""),
|
|
|
|
Stub::FileWithContent("env.nu", ""),
|
|
|
|
]);
|
|
|
|
|
|
|
|
let file = File::create(dirs.test().join("test-plugin-file.msgpackz"))
|
|
|
|
.expect("failed to create file");
|
2024-04-25 00:40:39 +02:00
|
|
|
let mut contents = PluginRegistryFile::new();
|
2024-04-23 13:37:50 +02:00
|
|
|
|
2024-04-25 00:40:39 +02:00
|
|
|
contents.upsert_plugin(PluginRegistryItem {
|
2024-04-23 13:37:50 +02:00
|
|
|
name: "example".into(),
|
|
|
|
filename: example_plugin_path,
|
|
|
|
shell: None,
|
2024-06-21 13:27:09 +02:00
|
|
|
data: valid_plugin_item_data(),
|
2024-04-23 13:37:50 +02:00
|
|
|
});
|
|
|
|
|
2024-04-25 00:40:39 +02:00
|
|
|
contents.upsert_plugin(PluginRegistryItem {
|
2024-04-23 13:37:50 +02:00
|
|
|
name: "foo".into(),
|
|
|
|
// this doesn't exist, but it should be ok
|
2024-07-12 04:43:10 +02:00
|
|
|
filename: dirs.test().join("nu_plugin_foo").into(),
|
2024-04-23 13:37:50 +02:00
|
|
|
shell: None,
|
2024-06-21 13:27:09 +02:00
|
|
|
data: valid_plugin_item_data(),
|
2024-04-23 13:37:50 +02:00
|
|
|
});
|
|
|
|
|
|
|
|
contents
|
|
|
|
.write_to(file, None)
|
|
|
|
.expect("failed to write plugin file");
|
|
|
|
|
|
|
|
assert_cmd::Command::new(nu_test_support::fs::executable_path())
|
|
|
|
.current_dir(dirs.test())
|
|
|
|
.args([
|
|
|
|
"--no-std-lib",
|
|
|
|
"--config",
|
|
|
|
"config.nu",
|
|
|
|
"--env-config",
|
|
|
|
"env.nu",
|
|
|
|
"--plugin-config",
|
|
|
|
"test-plugin-file.msgpackz",
|
|
|
|
"--commands",
|
|
|
|
"plugin rm example",
|
|
|
|
])
|
|
|
|
.assert()
|
|
|
|
.success()
|
|
|
|
.stderr("");
|
|
|
|
|
|
|
|
assert_cmd::Command::new(nu_test_support::fs::executable_path())
|
|
|
|
.current_dir(dirs.test())
|
|
|
|
.args([
|
|
|
|
"--no-std-lib",
|
|
|
|
"--config",
|
|
|
|
"config.nu",
|
|
|
|
"--env-config",
|
|
|
|
"env.nu",
|
|
|
|
"--plugin-config",
|
|
|
|
"test-plugin-file.msgpackz",
|
|
|
|
"--commands",
|
Make `plugin list` read state from plugin registry file as well (#14085)
# Description
[Context on
Discord](https://discord.com/channels/601130461678272522/855947301380947968/1292279795035668583)
**This is a breaking change, due to the removal of `is_running`.**
Some users find the `plugin list` command confusing, because it doesn't
show anything different after running `plugin add` or `plugin rm`. This
modifies the `plugin list` command to also look at the plugin registry
file to give some idea of how the plugins in engine state differ from
those in the plugin registry file.
The following values of `status` are now produced instead of
`is_running`:
- `added`: The plugin is present in the plugin registry file, but not in
the engine.
- `loaded`: The plugin is present both in the plugin registry file and
in the engine, but is not running.
- `running`: The plugin is currently running, and the `pid` column
should contain its process ID.
- `modified`: The plugin state present in the plugin registry file is
different from the state in the engine.
- `removed`: The plugin is still loaded in the engine, but is not
present in the plugin registry file.
- `invalid`: The data in the plugin registry file couldn't be
deserialized, and the plugin most likely needs to be added again.
Example (`commands` omitted):
```
╭──────┬─────────────────────┬────────────┬───────────┬──────────┬─────────────────────────────────────────────────────┬─────────╮
│ # │ name │ version │ status │ pid │ filename │ shell │
├──────┼─────────────────────┼────────────┼───────────┼──────────┼─────────────────────────────────────────────────────┼─────────┤
│ 0 │ custom_values │ 0.1.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_custom_values │ │
│ 1 │ dbus │ 0.11.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_dbus │ │
│ 2 │ example │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_example │ │
│ 3 │ explore_ir │ 0.3.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_explore_ir │ │
│ 4 │ formats │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_formats │ │
│ 5 │ gstat │ 0.98.1 │ running │ 236662 │ /home/devyn/.cargo/bin/nu_plugin_gstat │ │
│ 6 │ inc │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_inc │ │
│ 7 │ polars │ 0.98.1 │ added │ │ /home/devyn/.cargo/bin/nu_plugin_polars │ │
│ 8 │ query │ 0.98.1 │ removed │ │ /home/devyn/.cargo/bin/nu_plugin_query │ │
│ 9 │ stress_internals │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_stress_internals │ │
╰──────┴─────────────────────┴────────────┴───────────┴──────────┴─────────────────────────────────────────────────────┴─────────╯
```
# User-Facing Changes
To `plugin list`:
* **Breaking:** The `is_running` column is removed and replaced with
`status`. Use `status == running` to filter equivalently.
* The `--plugin-config` from other plugin management commands is now
supported.
* Added an `--engine` flag which behaves more or less like before, and
doesn't load the plugin registry file at all.
* Added a `--registry` flag which only checks the plugin registry file.
All plugins appear as `added` since there is no state to compare with.
Because the default is to check both, the `plugin list` command might be
a little bit slower. If you don't need to check the plugin registry
file, the `--engine` flag does not load the plugin registry file at all,
so it should be just as fast as before.
# Tests + Formatting
Added tests for `added` and `removed` statuses. `modified` and `invalid`
are a bit more tricky so I didn't try.
# After Submitting
- [ ] update documentation that references the `plugin list` command
- [ ] release notes
2024-10-17 04:24:45 +02:00
|
|
|
"plugin list --engine | get name | to json --raw",
|
2024-04-23 13:37:50 +02:00
|
|
|
])
|
|
|
|
.assert()
|
|
|
|
.success()
|
|
|
|
.stdout("[\"foo\"]\n");
|
|
|
|
})
|
2024-04-21 14:36:26 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
fn plugin_rm_not_found() {
|
|
|
|
let result = nu_with_plugins!(
|
|
|
|
cwd: ".",
|
|
|
|
plugins: [],
|
|
|
|
r#"
|
|
|
|
plugin rm example
|
|
|
|
"#
|
|
|
|
);
|
|
|
|
assert!(!result.status.success());
|
|
|
|
assert!(result.err.contains("example"));
|
|
|
|
}
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
fn plugin_rm_from_custom_path() {
|
|
|
|
let example_plugin_path = example_plugin_path();
|
|
|
|
Playground::setup("plugin rm from custom path", |dirs, _playground| {
|
|
|
|
let file = File::create(dirs.test().join("test-plugin-file.msgpackz"))
|
|
|
|
.expect("failed to create file");
|
2024-04-25 00:40:39 +02:00
|
|
|
let mut contents = PluginRegistryFile::new();
|
2024-04-21 14:36:26 +02:00
|
|
|
|
2024-04-25 00:40:39 +02:00
|
|
|
contents.upsert_plugin(PluginRegistryItem {
|
2024-04-21 14:36:26 +02:00
|
|
|
name: "example".into(),
|
|
|
|
filename: example_plugin_path,
|
|
|
|
shell: None,
|
2024-06-21 13:27:09 +02:00
|
|
|
data: valid_plugin_item_data(),
|
2024-04-21 14:36:26 +02:00
|
|
|
});
|
|
|
|
|
2024-04-25 00:40:39 +02:00
|
|
|
contents.upsert_plugin(PluginRegistryItem {
|
2024-04-21 14:36:26 +02:00
|
|
|
name: "foo".into(),
|
|
|
|
// this doesn't exist, but it should be ok
|
2024-07-12 04:43:10 +02:00
|
|
|
filename: dirs.test().join("nu_plugin_foo").into(),
|
2024-04-21 14:36:26 +02:00
|
|
|
shell: None,
|
2024-06-21 13:27:09 +02:00
|
|
|
data: valid_plugin_item_data(),
|
2024-04-21 14:36:26 +02:00
|
|
|
});
|
|
|
|
|
|
|
|
contents
|
|
|
|
.write_to(file, None)
|
|
|
|
.expect("failed to write plugin file");
|
|
|
|
|
|
|
|
let result = nu!(
|
|
|
|
cwd: dirs.test(),
|
|
|
|
"plugin rm --plugin-config test-plugin-file.msgpackz example",
|
|
|
|
);
|
|
|
|
assert!(result.status.success());
|
|
|
|
assert!(result.err.trim().is_empty());
|
|
|
|
|
|
|
|
// Check the contents after running
|
2024-04-25 00:40:39 +02:00
|
|
|
let contents = PluginRegistryFile::read_from(
|
2024-04-21 14:36:26 +02:00
|
|
|
File::open(dirs.test().join("test-plugin-file.msgpackz")).expect("failed to open file"),
|
|
|
|
None,
|
|
|
|
)
|
|
|
|
.expect("failed to read file");
|
|
|
|
|
|
|
|
assert!(!contents.plugins.iter().any(|p| p.name == "example"));
|
|
|
|
|
|
|
|
// Shouldn't remove anything else
|
|
|
|
assert!(contents.plugins.iter().any(|p| p.name == "foo"));
|
|
|
|
})
|
|
|
|
}
|
|
|
|
|
2024-04-24 13:28:45 +02:00
|
|
|
#[test]
|
|
|
|
fn plugin_rm_using_filename() {
|
|
|
|
let example_plugin_path = example_plugin_path();
|
|
|
|
Playground::setup("plugin rm using filename", |dirs, _playground| {
|
|
|
|
let file = File::create(dirs.test().join("test-plugin-file.msgpackz"))
|
|
|
|
.expect("failed to create file");
|
2024-04-25 00:40:39 +02:00
|
|
|
let mut contents = PluginRegistryFile::new();
|
2024-04-24 13:28:45 +02:00
|
|
|
|
2024-04-25 00:40:39 +02:00
|
|
|
contents.upsert_plugin(PluginRegistryItem {
|
2024-04-24 13:28:45 +02:00
|
|
|
name: "example".into(),
|
|
|
|
filename: example_plugin_path.clone(),
|
|
|
|
shell: None,
|
2024-06-21 13:27:09 +02:00
|
|
|
data: valid_plugin_item_data(),
|
2024-04-24 13:28:45 +02:00
|
|
|
});
|
|
|
|
|
2024-04-25 00:40:39 +02:00
|
|
|
contents.upsert_plugin(PluginRegistryItem {
|
2024-04-24 13:28:45 +02:00
|
|
|
name: "foo".into(),
|
|
|
|
// this doesn't exist, but it should be ok
|
2024-07-12 04:43:10 +02:00
|
|
|
filename: dirs.test().join("nu_plugin_foo").into(),
|
2024-04-24 13:28:45 +02:00
|
|
|
shell: None,
|
2024-06-21 13:27:09 +02:00
|
|
|
data: valid_plugin_item_data(),
|
2024-04-24 13:28:45 +02:00
|
|
|
});
|
|
|
|
|
|
|
|
contents
|
|
|
|
.write_to(file, None)
|
|
|
|
.expect("failed to write plugin file");
|
|
|
|
|
|
|
|
let result = nu!(
|
|
|
|
cwd: dirs.test(),
|
|
|
|
&format!(
|
|
|
|
"plugin rm --plugin-config test-plugin-file.msgpackz '{}'",
|
|
|
|
example_plugin_path.display()
|
|
|
|
)
|
|
|
|
);
|
|
|
|
assert!(result.status.success());
|
|
|
|
assert!(result.err.trim().is_empty());
|
|
|
|
|
|
|
|
// Check the contents after running
|
2024-04-25 00:40:39 +02:00
|
|
|
let contents = PluginRegistryFile::read_from(
|
2024-04-24 13:28:45 +02:00
|
|
|
File::open(dirs.test().join("test-plugin-file.msgpackz")).expect("failed to open file"),
|
|
|
|
None,
|
|
|
|
)
|
|
|
|
.expect("failed to read file");
|
|
|
|
|
|
|
|
assert!(!contents.plugins.iter().any(|p| p.name == "example"));
|
|
|
|
|
|
|
|
// Shouldn't remove anything else
|
|
|
|
assert!(contents.plugins.iter().any(|p| p.name == "foo"));
|
|
|
|
})
|
|
|
|
}
|
|
|
|
|
2024-04-21 14:36:26 +02:00
|
|
|
/// Running nu with a test plugin file that fails to parse on one plugin should just cause a warning
|
|
|
|
/// but the others should be loaded
|
|
|
|
#[test]
|
|
|
|
fn warning_on_invalid_plugin_item() {
|
|
|
|
let example_plugin_path = example_plugin_path();
|
|
|
|
Playground::setup("warning on invalid plugin item", |dirs, playground| {
|
2024-05-04 02:53:15 +02:00
|
|
|
playground.with_files(&[
|
2024-04-21 14:36:26 +02:00
|
|
|
Stub::FileWithContent("config.nu", ""),
|
|
|
|
Stub::FileWithContent("env.nu", ""),
|
|
|
|
]);
|
|
|
|
|
|
|
|
let file = File::create(dirs.test().join("test-plugin-file.msgpackz"))
|
|
|
|
.expect("failed to create file");
|
2024-04-25 00:40:39 +02:00
|
|
|
let mut contents = PluginRegistryFile::new();
|
2024-04-21 14:36:26 +02:00
|
|
|
|
2024-04-25 00:40:39 +02:00
|
|
|
contents.upsert_plugin(PluginRegistryItem {
|
2024-04-21 14:36:26 +02:00
|
|
|
name: "example".into(),
|
|
|
|
filename: example_plugin_path,
|
|
|
|
shell: None,
|
2024-06-21 13:27:09 +02:00
|
|
|
data: valid_plugin_item_data(),
|
2024-04-21 14:36:26 +02:00
|
|
|
});
|
|
|
|
|
2024-04-25 00:40:39 +02:00
|
|
|
contents.upsert_plugin(PluginRegistryItem {
|
2024-04-21 14:36:26 +02:00
|
|
|
name: "badtest".into(),
|
|
|
|
// this doesn't exist, but it should be ok
|
2024-07-12 04:43:10 +02:00
|
|
|
filename: dirs.test().join("nu_plugin_badtest").into(),
|
2024-04-21 14:36:26 +02:00
|
|
|
shell: None,
|
2024-04-25 00:40:39 +02:00
|
|
|
data: PluginRegistryItemData::Invalid,
|
2024-04-21 14:36:26 +02:00
|
|
|
});
|
|
|
|
|
|
|
|
contents
|
|
|
|
.write_to(file, None)
|
|
|
|
.expect("failed to write plugin file");
|
|
|
|
|
2024-04-23 13:37:50 +02:00
|
|
|
let result = assert_cmd::Command::new(nu_test_support::fs::executable_path())
|
2024-04-21 14:36:26 +02:00
|
|
|
.current_dir(dirs.test())
|
|
|
|
.args([
|
|
|
|
"--no-std-lib",
|
|
|
|
"--config",
|
|
|
|
"config.nu",
|
|
|
|
"--env-config",
|
|
|
|
"env.nu",
|
|
|
|
"--plugin-config",
|
|
|
|
"test-plugin-file.msgpackz",
|
|
|
|
"--commands",
|
Make `plugin list` read state from plugin registry file as well (#14085)
# Description
[Context on
Discord](https://discord.com/channels/601130461678272522/855947301380947968/1292279795035668583)
**This is a breaking change, due to the removal of `is_running`.**
Some users find the `plugin list` command confusing, because it doesn't
show anything different after running `plugin add` or `plugin rm`. This
modifies the `plugin list` command to also look at the plugin registry
file to give some idea of how the plugins in engine state differ from
those in the plugin registry file.
The following values of `status` are now produced instead of
`is_running`:
- `added`: The plugin is present in the plugin registry file, but not in
the engine.
- `loaded`: The plugin is present both in the plugin registry file and
in the engine, but is not running.
- `running`: The plugin is currently running, and the `pid` column
should contain its process ID.
- `modified`: The plugin state present in the plugin registry file is
different from the state in the engine.
- `removed`: The plugin is still loaded in the engine, but is not
present in the plugin registry file.
- `invalid`: The data in the plugin registry file couldn't be
deserialized, and the plugin most likely needs to be added again.
Example (`commands` omitted):
```
╭──────┬─────────────────────┬────────────┬───────────┬──────────┬─────────────────────────────────────────────────────┬─────────╮
│ # │ name │ version │ status │ pid │ filename │ shell │
├──────┼─────────────────────┼────────────┼───────────┼──────────┼─────────────────────────────────────────────────────┼─────────┤
│ 0 │ custom_values │ 0.1.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_custom_values │ │
│ 1 │ dbus │ 0.11.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_dbus │ │
│ 2 │ example │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_example │ │
│ 3 │ explore_ir │ 0.3.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_explore_ir │ │
│ 4 │ formats │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_formats │ │
│ 5 │ gstat │ 0.98.1 │ running │ 236662 │ /home/devyn/.cargo/bin/nu_plugin_gstat │ │
│ 6 │ inc │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_inc │ │
│ 7 │ polars │ 0.98.1 │ added │ │ /home/devyn/.cargo/bin/nu_plugin_polars │ │
│ 8 │ query │ 0.98.1 │ removed │ │ /home/devyn/.cargo/bin/nu_plugin_query │ │
│ 9 │ stress_internals │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_stress_internals │ │
╰──────┴─────────────────────┴────────────┴───────────┴──────────┴─────────────────────────────────────────────────────┴─────────╯
```
# User-Facing Changes
To `plugin list`:
* **Breaking:** The `is_running` column is removed and replaced with
`status`. Use `status == running` to filter equivalently.
* The `--plugin-config` from other plugin management commands is now
supported.
* Added an `--engine` flag which behaves more or less like before, and
doesn't load the plugin registry file at all.
* Added a `--registry` flag which only checks the plugin registry file.
All plugins appear as `added` since there is no state to compare with.
Because the default is to check both, the `plugin list` command might be
a little bit slower. If you don't need to check the plugin registry
file, the `--engine` flag does not load the plugin registry file at all,
so it should be just as fast as before.
# Tests + Formatting
Added tests for `added` and `removed` statuses. `modified` and `invalid`
are a bit more tricky so I didn't try.
# After Submitting
- [ ] update documentation that references the `plugin list` command
- [ ] release notes
2024-10-17 04:24:45 +02:00
|
|
|
"plugin list --engine | get name | to json --raw",
|
2024-04-21 14:36:26 +02:00
|
|
|
])
|
|
|
|
.output()
|
|
|
|
.expect("failed to run nu");
|
|
|
|
|
|
|
|
let out = String::from_utf8_lossy(&result.stdout).trim().to_owned();
|
|
|
|
let err = String::from_utf8_lossy(&result.stderr).trim().to_owned();
|
|
|
|
|
|
|
|
println!("=== stdout\n{out}\n=== stderr\n{err}");
|
|
|
|
|
|
|
|
// The code should still execute successfully
|
|
|
|
assert!(result.status.success());
|
|
|
|
// The "example" plugin should be unaffected
|
|
|
|
assert_eq!(r#"["example"]"#, out);
|
|
|
|
// The warning should be in there
|
2024-04-25 00:40:39 +02:00
|
|
|
assert!(err.contains("registered plugin data"));
|
2024-04-21 14:36:26 +02:00
|
|
|
assert!(err.contains("badtest"));
|
|
|
|
})
|
|
|
|
}
|
2024-04-23 13:37:50 +02:00
|
|
|
|
|
|
|
#[test]
|
|
|
|
fn plugin_use_error_not_found() {
|
|
|
|
Playground::setup("plugin use error not found", |dirs, playground| {
|
2024-05-04 02:53:15 +02:00
|
|
|
playground.with_files(&[
|
2024-04-23 13:37:50 +02:00
|
|
|
Stub::FileWithContent("config.nu", ""),
|
|
|
|
Stub::FileWithContent("env.nu", ""),
|
|
|
|
]);
|
|
|
|
|
|
|
|
// Make an empty msgpackz
|
|
|
|
let file = File::create(dirs.test().join("plugin.msgpackz"))
|
|
|
|
.expect("failed to open plugin.msgpackz");
|
2024-04-25 00:40:39 +02:00
|
|
|
PluginRegistryFile::default()
|
2024-04-23 13:37:50 +02:00
|
|
|
.write_to(file, None)
|
2024-04-25 00:40:39 +02:00
|
|
|
.expect("failed to write empty registry file");
|
2024-04-23 13:37:50 +02:00
|
|
|
|
|
|
|
let output = assert_cmd::Command::new(nu_test_support::fs::executable_path())
|
|
|
|
.current_dir(dirs.test())
|
|
|
|
.args(["--config", "config.nu"])
|
|
|
|
.args(["--env-config", "env.nu"])
|
|
|
|
.args(["--plugin-config", "plugin.msgpackz"])
|
|
|
|
.args(["--commands", "plugin use custom_values"])
|
|
|
|
.output()
|
|
|
|
.expect("failed to run nu");
|
|
|
|
let stderr = String::from_utf8_lossy(&output.stderr);
|
|
|
|
assert!(stderr.contains("Plugin not found"));
|
|
|
|
})
|
|
|
|
}
|
|
|
|
|
Make `plugin list` read state from plugin registry file as well (#14085)
# Description
[Context on
Discord](https://discord.com/channels/601130461678272522/855947301380947968/1292279795035668583)
**This is a breaking change, due to the removal of `is_running`.**
Some users find the `plugin list` command confusing, because it doesn't
show anything different after running `plugin add` or `plugin rm`. This
modifies the `plugin list` command to also look at the plugin registry
file to give some idea of how the plugins in engine state differ from
those in the plugin registry file.
The following values of `status` are now produced instead of
`is_running`:
- `added`: The plugin is present in the plugin registry file, but not in
the engine.
- `loaded`: The plugin is present both in the plugin registry file and
in the engine, but is not running.
- `running`: The plugin is currently running, and the `pid` column
should contain its process ID.
- `modified`: The plugin state present in the plugin registry file is
different from the state in the engine.
- `removed`: The plugin is still loaded in the engine, but is not
present in the plugin registry file.
- `invalid`: The data in the plugin registry file couldn't be
deserialized, and the plugin most likely needs to be added again.
Example (`commands` omitted):
```
╭──────┬─────────────────────┬────────────┬───────────┬──────────┬─────────────────────────────────────────────────────┬─────────╮
│ # │ name │ version │ status │ pid │ filename │ shell │
├──────┼─────────────────────┼────────────┼───────────┼──────────┼─────────────────────────────────────────────────────┼─────────┤
│ 0 │ custom_values │ 0.1.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_custom_values │ │
│ 1 │ dbus │ 0.11.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_dbus │ │
│ 2 │ example │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_example │ │
│ 3 │ explore_ir │ 0.3.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_explore_ir │ │
│ 4 │ formats │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_formats │ │
│ 5 │ gstat │ 0.98.1 │ running │ 236662 │ /home/devyn/.cargo/bin/nu_plugin_gstat │ │
│ 6 │ inc │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_inc │ │
│ 7 │ polars │ 0.98.1 │ added │ │ /home/devyn/.cargo/bin/nu_plugin_polars │ │
│ 8 │ query │ 0.98.1 │ removed │ │ /home/devyn/.cargo/bin/nu_plugin_query │ │
│ 9 │ stress_internals │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_stress_internals │ │
╰──────┴─────────────────────┴────────────┴───────────┴──────────┴─────────────────────────────────────────────────────┴─────────╯
```
# User-Facing Changes
To `plugin list`:
* **Breaking:** The `is_running` column is removed and replaced with
`status`. Use `status == running` to filter equivalently.
* The `--plugin-config` from other plugin management commands is now
supported.
* Added an `--engine` flag which behaves more or less like before, and
doesn't load the plugin registry file at all.
* Added a `--registry` flag which only checks the plugin registry file.
All plugins appear as `added` since there is no state to compare with.
Because the default is to check both, the `plugin list` command might be
a little bit slower. If you don't need to check the plugin registry
file, the `--engine` flag does not load the plugin registry file at all,
so it should be just as fast as before.
# Tests + Formatting
Added tests for `added` and `removed` statuses. `modified` and `invalid`
are a bit more tricky so I didn't try.
# After Submitting
- [ ] update documentation that references the `plugin list` command
- [ ] release notes
2024-10-17 04:24:45 +02:00
|
|
|
#[test]
|
|
|
|
fn plugin_shows_up_in_default_plugin_list_after_add() {
|
|
|
|
let example_plugin_path = example_plugin_path();
|
|
|
|
let result = nu_with_plugins!(
|
|
|
|
cwd: ".",
|
|
|
|
plugins: [],
|
|
|
|
&format!(r#"
|
|
|
|
plugin add '{}'
|
|
|
|
plugin list | get status | to json --raw
|
|
|
|
"#, example_plugin_path.display())
|
|
|
|
);
|
|
|
|
assert!(result.status.success());
|
|
|
|
assert_eq!(r#"["added"]"#, result.out);
|
|
|
|
}
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
fn plugin_shows_removed_after_removing() {
|
|
|
|
let example_plugin_path = example_plugin_path();
|
|
|
|
let result = nu_with_plugins!(
|
|
|
|
cwd: ".",
|
|
|
|
plugins: [],
|
|
|
|
&format!(r#"
|
|
|
|
plugin add '{}'
|
|
|
|
plugin list | get status | to json --raw
|
|
|
|
(
|
|
|
|
^$nu.current-exe
|
|
|
|
--config $nu.config-path
|
|
|
|
--env-config $nu.env-path
|
|
|
|
--plugin-config $nu.plugin-path
|
|
|
|
--commands 'plugin rm example; plugin list | get status | to json --raw'
|
|
|
|
)
|
|
|
|
"#, example_plugin_path.display())
|
|
|
|
);
|
|
|
|
assert!(result.status.success());
|
|
|
|
assert_eq!(r#"["removed"]"#, result.out);
|
|
|
|
}
|
|
|
|
|
2024-04-23 13:37:50 +02:00
|
|
|
#[test]
|
|
|
|
fn plugin_add_and_then_use() {
|
|
|
|
let example_plugin_path = example_plugin_path();
|
|
|
|
let result = nu_with_plugins!(
|
|
|
|
cwd: ".",
|
|
|
|
plugins: [],
|
|
|
|
&format!(r#"
|
|
|
|
plugin add '{}'
|
|
|
|
(
|
|
|
|
^$nu.current-exe
|
|
|
|
--config $nu.config-path
|
|
|
|
--env-config $nu.env-path
|
|
|
|
--plugin-config $nu.plugin-path
|
Make `plugin list` read state from plugin registry file as well (#14085)
# Description
[Context on
Discord](https://discord.com/channels/601130461678272522/855947301380947968/1292279795035668583)
**This is a breaking change, due to the removal of `is_running`.**
Some users find the `plugin list` command confusing, because it doesn't
show anything different after running `plugin add` or `plugin rm`. This
modifies the `plugin list` command to also look at the plugin registry
file to give some idea of how the plugins in engine state differ from
those in the plugin registry file.
The following values of `status` are now produced instead of
`is_running`:
- `added`: The plugin is present in the plugin registry file, but not in
the engine.
- `loaded`: The plugin is present both in the plugin registry file and
in the engine, but is not running.
- `running`: The plugin is currently running, and the `pid` column
should contain its process ID.
- `modified`: The plugin state present in the plugin registry file is
different from the state in the engine.
- `removed`: The plugin is still loaded in the engine, but is not
present in the plugin registry file.
- `invalid`: The data in the plugin registry file couldn't be
deserialized, and the plugin most likely needs to be added again.
Example (`commands` omitted):
```
╭──────┬─────────────────────┬────────────┬───────────┬──────────┬─────────────────────────────────────────────────────┬─────────╮
│ # │ name │ version │ status │ pid │ filename │ shell │
├──────┼─────────────────────┼────────────┼───────────┼──────────┼─────────────────────────────────────────────────────┼─────────┤
│ 0 │ custom_values │ 0.1.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_custom_values │ │
│ 1 │ dbus │ 0.11.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_dbus │ │
│ 2 │ example │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_example │ │
│ 3 │ explore_ir │ 0.3.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_explore_ir │ │
│ 4 │ formats │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_formats │ │
│ 5 │ gstat │ 0.98.1 │ running │ 236662 │ /home/devyn/.cargo/bin/nu_plugin_gstat │ │
│ 6 │ inc │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_inc │ │
│ 7 │ polars │ 0.98.1 │ added │ │ /home/devyn/.cargo/bin/nu_plugin_polars │ │
│ 8 │ query │ 0.98.1 │ removed │ │ /home/devyn/.cargo/bin/nu_plugin_query │ │
│ 9 │ stress_internals │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_stress_internals │ │
╰──────┴─────────────────────┴────────────┴───────────┴──────────┴─────────────────────────────────────────────────────┴─────────╯
```
# User-Facing Changes
To `plugin list`:
* **Breaking:** The `is_running` column is removed and replaced with
`status`. Use `status == running` to filter equivalently.
* The `--plugin-config` from other plugin management commands is now
supported.
* Added an `--engine` flag which behaves more or less like before, and
doesn't load the plugin registry file at all.
* Added a `--registry` flag which only checks the plugin registry file.
All plugins appear as `added` since there is no state to compare with.
Because the default is to check both, the `plugin list` command might be
a little bit slower. If you don't need to check the plugin registry
file, the `--engine` flag does not load the plugin registry file at all,
so it should be just as fast as before.
# Tests + Formatting
Added tests for `added` and `removed` statuses. `modified` and `invalid`
are a bit more tricky so I didn't try.
# After Submitting
- [ ] update documentation that references the `plugin list` command
- [ ] release notes
2024-10-17 04:24:45 +02:00
|
|
|
--commands 'plugin use example; plugin list --engine | get name | to json --raw'
|
2024-04-23 13:37:50 +02:00
|
|
|
)
|
|
|
|
"#, example_plugin_path.display())
|
|
|
|
);
|
|
|
|
assert!(result.status.success());
|
|
|
|
assert_eq!(r#"["example"]"#, result.out);
|
|
|
|
}
|
|
|
|
|
2024-04-24 13:28:45 +02:00
|
|
|
#[test]
|
|
|
|
fn plugin_add_and_then_use_by_filename() {
|
|
|
|
let example_plugin_path = example_plugin_path();
|
|
|
|
let result = nu_with_plugins!(
|
|
|
|
cwd: ".",
|
|
|
|
plugins: [],
|
|
|
|
&format!(r#"
|
|
|
|
plugin add '{0}'
|
|
|
|
(
|
|
|
|
^$nu.current-exe
|
|
|
|
--config $nu.config-path
|
|
|
|
--env-config $nu.env-path
|
|
|
|
--plugin-config $nu.plugin-path
|
Make `plugin list` read state from plugin registry file as well (#14085)
# Description
[Context on
Discord](https://discord.com/channels/601130461678272522/855947301380947968/1292279795035668583)
**This is a breaking change, due to the removal of `is_running`.**
Some users find the `plugin list` command confusing, because it doesn't
show anything different after running `plugin add` or `plugin rm`. This
modifies the `plugin list` command to also look at the plugin registry
file to give some idea of how the plugins in engine state differ from
those in the plugin registry file.
The following values of `status` are now produced instead of
`is_running`:
- `added`: The plugin is present in the plugin registry file, but not in
the engine.
- `loaded`: The plugin is present both in the plugin registry file and
in the engine, but is not running.
- `running`: The plugin is currently running, and the `pid` column
should contain its process ID.
- `modified`: The plugin state present in the plugin registry file is
different from the state in the engine.
- `removed`: The plugin is still loaded in the engine, but is not
present in the plugin registry file.
- `invalid`: The data in the plugin registry file couldn't be
deserialized, and the plugin most likely needs to be added again.
Example (`commands` omitted):
```
╭──────┬─────────────────────┬────────────┬───────────┬──────────┬─────────────────────────────────────────────────────┬─────────╮
│ # │ name │ version │ status │ pid │ filename │ shell │
├──────┼─────────────────────┼────────────┼───────────┼──────────┼─────────────────────────────────────────────────────┼─────────┤
│ 0 │ custom_values │ 0.1.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_custom_values │ │
│ 1 │ dbus │ 0.11.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_dbus │ │
│ 2 │ example │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_example │ │
│ 3 │ explore_ir │ 0.3.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_explore_ir │ │
│ 4 │ formats │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_formats │ │
│ 5 │ gstat │ 0.98.1 │ running │ 236662 │ /home/devyn/.cargo/bin/nu_plugin_gstat │ │
│ 6 │ inc │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_inc │ │
│ 7 │ polars │ 0.98.1 │ added │ │ /home/devyn/.cargo/bin/nu_plugin_polars │ │
│ 8 │ query │ 0.98.1 │ removed │ │ /home/devyn/.cargo/bin/nu_plugin_query │ │
│ 9 │ stress_internals │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_stress_internals │ │
╰──────┴─────────────────────┴────────────┴───────────┴──────────┴─────────────────────────────────────────────────────┴─────────╯
```
# User-Facing Changes
To `plugin list`:
* **Breaking:** The `is_running` column is removed and replaced with
`status`. Use `status == running` to filter equivalently.
* The `--plugin-config` from other plugin management commands is now
supported.
* Added an `--engine` flag which behaves more or less like before, and
doesn't load the plugin registry file at all.
* Added a `--registry` flag which only checks the plugin registry file.
All plugins appear as `added` since there is no state to compare with.
Because the default is to check both, the `plugin list` command might be
a little bit slower. If you don't need to check the plugin registry
file, the `--engine` flag does not load the plugin registry file at all,
so it should be just as fast as before.
# Tests + Formatting
Added tests for `added` and `removed` statuses. `modified` and `invalid`
are a bit more tricky so I didn't try.
# After Submitting
- [ ] update documentation that references the `plugin list` command
- [ ] release notes
2024-10-17 04:24:45 +02:00
|
|
|
--commands 'plugin use '{0}'; plugin list --engine | get name | to json --raw'
|
2024-04-24 13:28:45 +02:00
|
|
|
)
|
|
|
|
"#, example_plugin_path.display())
|
|
|
|
);
|
|
|
|
assert!(result.status.success());
|
|
|
|
assert_eq!(r#"["example"]"#, result.out);
|
|
|
|
}
|
|
|
|
|
2024-04-23 13:37:50 +02:00
|
|
|
#[test]
|
|
|
|
fn plugin_add_then_use_with_custom_path() {
|
|
|
|
let example_plugin_path = example_plugin_path();
|
|
|
|
Playground::setup("plugin add to custom path", |dirs, _playground| {
|
|
|
|
let result_add = nu!(
|
|
|
|
cwd: dirs.test(),
|
|
|
|
&format!("
|
|
|
|
plugin add --plugin-config test-plugin-file.msgpackz '{}'
|
|
|
|
", example_plugin_path.display())
|
|
|
|
);
|
|
|
|
|
|
|
|
assert!(result_add.status.success());
|
|
|
|
|
|
|
|
let result_use = nu!(
|
|
|
|
cwd: dirs.test(),
|
|
|
|
r#"
|
|
|
|
plugin use --plugin-config test-plugin-file.msgpackz example
|
Make `plugin list` read state from plugin registry file as well (#14085)
# Description
[Context on
Discord](https://discord.com/channels/601130461678272522/855947301380947968/1292279795035668583)
**This is a breaking change, due to the removal of `is_running`.**
Some users find the `plugin list` command confusing, because it doesn't
show anything different after running `plugin add` or `plugin rm`. This
modifies the `plugin list` command to also look at the plugin registry
file to give some idea of how the plugins in engine state differ from
those in the plugin registry file.
The following values of `status` are now produced instead of
`is_running`:
- `added`: The plugin is present in the plugin registry file, but not in
the engine.
- `loaded`: The plugin is present both in the plugin registry file and
in the engine, but is not running.
- `running`: The plugin is currently running, and the `pid` column
should contain its process ID.
- `modified`: The plugin state present in the plugin registry file is
different from the state in the engine.
- `removed`: The plugin is still loaded in the engine, but is not
present in the plugin registry file.
- `invalid`: The data in the plugin registry file couldn't be
deserialized, and the plugin most likely needs to be added again.
Example (`commands` omitted):
```
╭──────┬─────────────────────┬────────────┬───────────┬──────────┬─────────────────────────────────────────────────────┬─────────╮
│ # │ name │ version │ status │ pid │ filename │ shell │
├──────┼─────────────────────┼────────────┼───────────┼──────────┼─────────────────────────────────────────────────────┼─────────┤
│ 0 │ custom_values │ 0.1.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_custom_values │ │
│ 1 │ dbus │ 0.11.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_dbus │ │
│ 2 │ example │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_example │ │
│ 3 │ explore_ir │ 0.3.0 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_explore_ir │ │
│ 4 │ formats │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_formats │ │
│ 5 │ gstat │ 0.98.1 │ running │ 236662 │ /home/devyn/.cargo/bin/nu_plugin_gstat │ │
│ 6 │ inc │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_inc │ │
│ 7 │ polars │ 0.98.1 │ added │ │ /home/devyn/.cargo/bin/nu_plugin_polars │ │
│ 8 │ query │ 0.98.1 │ removed │ │ /home/devyn/.cargo/bin/nu_plugin_query │ │
│ 9 │ stress_internals │ 0.98.1 │ loaded │ │ /home/devyn/.cargo/bin/nu_plugin_stress_internals │ │
╰──────┴─────────────────────┴────────────┴───────────┴──────────┴─────────────────────────────────────────────────────┴─────────╯
```
# User-Facing Changes
To `plugin list`:
* **Breaking:** The `is_running` column is removed and replaced with
`status`. Use `status == running` to filter equivalently.
* The `--plugin-config` from other plugin management commands is now
supported.
* Added an `--engine` flag which behaves more or less like before, and
doesn't load the plugin registry file at all.
* Added a `--registry` flag which only checks the plugin registry file.
All plugins appear as `added` since there is no state to compare with.
Because the default is to check both, the `plugin list` command might be
a little bit slower. If you don't need to check the plugin registry
file, the `--engine` flag does not load the plugin registry file at all,
so it should be just as fast as before.
# Tests + Formatting
Added tests for `added` and `removed` statuses. `modified` and `invalid`
are a bit more tricky so I didn't try.
# After Submitting
- [ ] update documentation that references the `plugin list` command
- [ ] release notes
2024-10-17 04:24:45 +02:00
|
|
|
plugin list --engine | get name | to json --raw
|
2024-04-23 13:37:50 +02:00
|
|
|
"#
|
|
|
|
);
|
|
|
|
|
|
|
|
assert!(result_use.status.success());
|
|
|
|
assert_eq!(r#"["example"]"#, result_use.out);
|
|
|
|
})
|
|
|
|
}
|